
From nobody Thu Jun  1 10:45:38 2017
Return-Path: <calle@tail-f.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 540BF12EAAE; Thu,  1 Jun 2017 10:45:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carl Moberg <calle@tail-f.com>
To: <yang-doctors@ietf.org>
Cc: draft-ietf-lime-yang-connectionless-oam.all@ietf.org, lime@ietf.org, ietf@ietf.org
Subject: Yangdoctors early review of draft-ietf-lime-yang-connectionless-oam-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149633912226.22293.8696121484014821225@ietfa.amsl.com>
Date: Thu, 01 Jun 2017 10:45:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TKdGrVAZSzlyHp4qlmD1h2kZMAg>
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 17:45:22 -0000

Reviewer: Carl Moberg
Review result: On the Right Track

I am the assigned YANG Doctor for the LIME YANG modules, this is the
notes from my initial review of
draft-ietf-lime-yang-connectionless-oam done with the authors on a
call last week:

The module is intended to be implemented as a service model, per the
module classification draft
(https://tools.ietf.org/html/draft-ietf-netmod-yang-model-classification-05)
with augments to topologies, I suggest it needs more description on
the general concepts and how to use it.

I suggest to remove the 'OAM data hierarchy' section. It does not add
any information.

The current version YANG module is all configuration except the 'oper'
subtree. And there are no mandatory nodes (except list keys) which
seems to allow for many, many combinations that likely make no sense.
Please re-review and make sure this is an informed choice.

Suggest to rename tp-address-type-value to
tp-address-technology-type.

Why does 'grouping tp-technology' only allow 'technology-null' or
'technology-string'/'leaf ipv4-icmp' and what is the meaning of the
leaf ipv4-icmp content?

There are a couple of occasions of 'ordered-by user' that does not
have a description of the meaning of the order. Please review.

Add an if-feature on path-discovery in *-methods draft.

Generally I'd suggest adding more information about the various types
and which specifications you are picking them up from (e.g. RD, LSP
ID, etc)

The specification defines a typedef that is a path in another module
("routing-instance-ref"). Suggest to reach out to authors of
draft-ietf-rtgwg-ni-model-02 to see if they want the -ref type in that
module for reuse.

Generally check whitespace and comments. Use the '-f yang' option to
YANG to fix whitespace.

Downcase "IPv4-Multicast-Group-Address", and
"IPv6-Multicast-Group-Address", "IP-Multicast-Group-Address"

Name of top container ('oper') not very helpful, suggest renaming to
'session-statistics'?

Spelling of grouping (and uses) cc-session-statsitics

Filename should include revision in CODE BEGINS

Don't reference drafts, pleas check RFC6087 bis and well-formed drafts
for header stmts
  
https://datatracker.ietf.org/doc/html/draft-ietf-netmod-rfc6087bis#section-4.9'



From nobody Thu Jun  1 18:20:31 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 AE298129B7A; Thu,  1 Jun 2017 18:20:30 -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-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149636643064.31792.16688057457126291788@ietfa.amsl.com>
Date: Thu, 01 Jun 2017 18:20:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kYc3RPyjxd-7mpvtQR1ZUZ9ypVo>
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, 02 Jun 2017 01:20:31 -0000

Reviewer: Dale Worley
Review result: Ready

I am the assigned Gen-ART reviewer for this draft.  The General Area
Review Team (Gen-ART) reviews all IETF documents being processed by
the IESG for the IETF Chair.  Please 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-08
Reviewer:  Dale R. Worley
Review Date:  2017-06-01
IETF LC End Date:  2017-04-18
IESG Telechat date:  2017-06-08

Summary:  This draft is ready for publication as a Standards Track
RFC.

[END]



From nobody Thu Jun  1 21:53:23 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 4505C127419 for <ietf@ietfa.amsl.com>; Thu,  1 Jun 2017 21:53:22 -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 T6fnjUubjaZT for <ietf@ietfa.amsl.com>; Thu,  1 Jun 2017 21:53:20 -0700 (PDT)
Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2D727127011 for <ietf@ietf.org>; Thu,  1 Jun 2017 21:53:20 -0700 (PDT)
Received: from pps.filterd (m0098396.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v524nJQ5071800 for <ietf@ietf.org>; Fri, 2 Jun 2017 00:53:18 -0400
Received: from e33.co.us.ibm.com (e33.co.us.ibm.com [32.97.110.151]) by mx0a-001b2d01.pphosted.com with ESMTP id 2ats3sd4d6-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 02 Jun 2017 00:53:17 -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, 1 Jun 2017 22:53:17 -0600
Received: from b03cxnp08026.gho.boulder.ibm.com (9.17.130.18) by e33.co.us.ibm.com (192.168.1.133) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Thu, 1 Jun 2017 22:53:14 -0600
Received: from b03ledav004.gho.boulder.ibm.com (b03ledav004.gho.boulder.ibm.com [9.17.130.235]) by b03cxnp08026.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v524rEgD9699588 for <ietf@ietf.org>; Thu, 1 Jun 2017 21:53:14 -0700
Received: from b03ledav004.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id F280178041 for <ietf@ietf.org>; Thu,  1 Jun 2017 22:53:13 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav004.gho.boulder.ibm.com (Postfix) with ESMTPS id D71647804D for <ietf@ietf.org>; Thu,  1 Jun 2017 22:53:13 -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 v524rCQr006292 for <ietf@ietf.org>; Fri, 2 Jun 2017 00:53:12 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v524rBR5006275 for ietf@ietf.org; Fri, 2 Jun 2017 00:53:11 -0400
From: narten@us.ibm.com
Date: Fri, 02 Jun 2017 00:53:11 -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: 17060204-0008-0000-0000-000007ECF6B0
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007156; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000212; SDB=6.00868904; UDB=6.00431915; IPR=6.00648868;  BA=6.00005393; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015675; XFM=3.00000015; UTC=2017-06-02 04:53:15
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17060204-0009-0000-0000-0000426C3766
Message-Id: <201706020453.v524rBR5006275@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-02_02:, , 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-1706020090
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ikqTGvc-tjSi-wfoLVXLRaQZBHA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jun 2017 04:53:22 -0000

Total of 35 messages in the last 7 days.
 
script run at: Fri Jun  2 00:53:11 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.57% |    3 | 14.73% |    47448 | spencerdawkins.ietf@gmail.com
  5.71% |    2 |  5.28% |    17014 | housley@vigilsec.com
  5.71% |    2 |  3.63% |    11689 | ron.even.tlv@gmail.com
  2.86% |    1 |  3.80% |    12246 | akatlas@gmail.com
  2.86% |    1 |  3.74% |    12062 | melinda.shore@gmail.com
  2.86% |    1 |  3.47% |    11188 | daniel.migault@ericsson.com
  2.86% |    1 |  3.46% |    11147 | brian.e.carpenter@gmail.com
  2.86% |    1 |  3.44% |    11085 | stewart@g3ysx.org.uk
  2.86% |    1 |  3.43% |    11039 | jinmei@wide.ad.jp
  2.86% |    1 |  3.39% |    10925 | peter@akayla.com
  2.86% |    1 |  3.28% |    10560 | narten@us.ibm.com
  2.86% |    1 |  3.17% |    10205 | amorris@amsl.com
  2.86% |    1 |  3.10% |    10002 | ietf-secretariat@ietf.org
  2.86% |    1 |  3.09% |     9947 | ynir.ietf@gmail.com
  2.86% |    1 |  3.04% |     9794 | lorenzo@google.com
  2.86% |    1 |  2.91% |     9368 | lloyd.wood@yahoo.co.uk
  2.86% |    1 |  2.85% |     9174 | chair@ietf.org
  2.86% |    1 |  2.81% |     9066 | alexandru.petrescu@gmail.com
  2.86% |    1 |  2.80% |     9014 | nomcom-chair-2017@ietf.org
  2.86% |    1 |  2.65% |     8536 | alissa@cooperw.in
  2.86% |    1 |  2.65% |     8529 | mnot@mnot.net
  2.86% |    1 |  2.64% |     8496 | suresh.krishnan@gmail.com
  2.86% |    1 |  2.51% |     8098 | john-ietf@jck.com
  2.86% |    1 |  2.17% |     7003 | calle@tail-f.com
  2.86% |    1 |  2.00% |     6459 | tore@fud.no
  2.86% |    1 |  1.71% |     5514 | barryleiba@computer.org
  2.86% |    1 |  1.69% |     5454 | rjsparks@nostrum.com
  2.86% |    1 |  1.69% |     5440 | jmh@joelhalpern.com
  2.86% |    1 |  1.68% |     5404 | worley@ariadne.com
  2.86% |    1 |  1.65% |     5300 | carlosm3011@gmail.com
  2.86% |    1 |  1.54% |     4971 | bwietf@bwijnen.net
--------+------+--------+----------+------------------------
100.00% |   35 |100.00% |   322177 | Total


From nobody Fri Jun  2 00:57:45 2017
Return-Path: <calle@tail-f.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 BE23C12ACAF; Fri,  2 Jun 2017 00:57:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carl Moberg <calle@tail-f.com>
To: <yang-doctors@ietf.org>
Cc: lime@ietf.org, ietf@ietf.org, draft-ietf-lime-yang-oam-model.all@ietf.org
Subject: Yangdoctors early review of draft-ietf-lime-yang-oam-model-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149639025372.31882.14301747353948788147@ietfa.amsl.com>
Date: Fri, 02 Jun 2017 00:57:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aJ2fCqaSqWP8rkrj0R93z2jA6zA>
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, 02 Jun 2017 07:57:34 -0000

Reviewer: Carl Moberg
Review result: On the Right Track

I am the assigned YANG Doctor for the LIME YANG modules, this is the
notes from my initial review of draft-ietf-lime-yang-oam-model done
with the authors:

First of all, would suggest we rename draft and the module itself:
OLD:
 draft-ietf-lime-yang-oam-model

NEW:
 draft-ietf-lime-yang-connection-oriented-oam-model


OLD:
 ietf-conn-oam

NEW:
 ietf-connection-oriented-oam

There are several uses of 'ordered-by system;'. Unless there is a
specific, and
documented reason for pointing out this default behavior, I suggest we
simply
remove them entirely.

Please review the use of case, e.g. the 'Interval' typedef should
likely be all
lowercase.

The description fields will need some language editing before release,
e.g. the
"Indicate whether the CC enable." description string for the 'MEP'
list.


From nobody Fri Jun  2 01:15:20 2017
Return-Path: <calle@tail-f.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 844B71314CD; Fri,  2 Jun 2017 01:15:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Carl Moberg <calle@tail-f.com>
To: <yang-doctors@ietf.org>
Cc: draft-ietf-lime-yang-connectionless-oam-methods.all@ietf.org, lime@ietf.org, ietf@ietf.org
Subject: Yangdoctors early review of draft-ietf-lime-yang-connectionless-oam-methods-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.52.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149639131942.31784.1129546145558830296@ietfa.amsl.com>
Date: Fri, 02 Jun 2017 01:15:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w9ET9J5YNn8cGwnOzcN_I05jgm8>
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, 02 Jun 2017 08:15:19 -0000

Reviewer: Carl Moberg
Review result: On the Right Track

I am the assigned YANG Doctor for the LIME YANG modules, this is the
notes from my initial review of draft-ietf-lime-yang-oam-model done
with the authors:

The CODE BEGINS statement has a date designation in the file name for
ietf-connectionless-oam-methods but not for
ietf-connectionless-oam-persistent-methods. Pick one.



From nobody Fri Jun  2 01:46:20 2017
Return-Path: <calle@tail-f.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 86AAF12E048; Fri,  2 Jun 2017 01:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.721
X-Spam-Level: 
X-Spam-Status: No, score=0.721 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RP_MATCHES_RCVD=-0.001, SPF_PASS=-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 n3Cjdl0nWt75; Fri,  2 Jun 2017 01:46:16 -0700 (PDT)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 285C1127A91; Fri,  2 Jun 2017 01:46:13 -0700 (PDT)
Received: from [10.147.40.118] (unknown [173.38.220.56]) by mail.tail-f.com (Postfix) with ESMTPSA id 6C4821AE00B6; Fri,  2 Jun 2017 10:46:11 +0200 (CEST)
Subject: Re: [yang-doctors] Yangdoctors early review of draft-ietf-lime-yang-connectionless-oam-methods-03
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Content-Type: text/html; charset=us-ascii
X-Apple-Auto-Saved: 1
X-Apple-Mail-Plain-Text-Draft: yes
From: Carl Moberg <calle@tail-f.com>
X-Apple-Mail-Remote-Attachments: YES
X-Apple-Base-Url: x-msg://6/
In-Reply-To: <149639131942.31784.1129546145558830296@ietfa.amsl.com>
X-Apple-Windows-Friendly: 1
Date: Fri, 2 Jun 2017 10:24:35 +0200
Cc: Carl Moberg <calle@tail-f.com>
X-Apple-Mail-Signature: SKIP_SIGNATURE
Content-Transfer-Encoding: quoted-printable
Message-Id: <470C83DE-49C0-41DF-9305-54946A0BB076@tail-f.com>
References: <149639131942.31784.1129546145558830296@ietfa.amsl.com>
X-Uniform-Type-Identifier: com.apple.mail-draft
To: yang-doctors@ietf.org, draft-ietf-lime-yang-connectionless-oam-methods.all@ietf.org, lime@ietf.org, ietf@ietf.org
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bXgkjDIw-iT49a0PsBG7zpvuLdM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 02 Jun 2017 08:46:17 -0000

<html><head></head><body dir=3D"auto" style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"ApplePlainTextBody"><div dir=3D"auto" style=3D"word-wrap: =
break-word; -webkit-nbsp-mode: space; -webkit-line-break: =
after-white-space;" class=3D"ApplePlainTextBody"><div =
class=3D"ApplePlainTextBody"><br><br><br><blockquote type=3D"cite">On =
Jun 2, 2017, at 10:15 AM, Carl Moberg &lt;calle@tail-f.com&gt; =
wrote:<br><br>Reviewer: Carl Moberg<br>Review result: On the Right =
Track<br><br>I am the assigned YANG Doctor for the LIME YANG modules, =
this is the<br>notes from my initial review of =
draft-ietf-lime-yang-oam-model done<br></blockquote><br>Should say: =
draft-ietf-lime-yang-connectionless-oam-methods<br><br><blockquote =
type=3D"cite">with the authors:<br><br>The CODE BEGINS statement has a =
date designation in the file name for<br>ietf-connectionless-oam-methods =
but not for<br>ietf-connectionless-oam-persistent-methods. Pick =
one.<br><br><br>_______________________________________________<br>yang-do=
ctors mailing =
list<br>yang-doctors@ietf.org<br>https://www.ietf.org/mailman/listinfo/yan=
g-doctors<br></blockquote><br></div></div></body></html>=


From nobody Sun Jun  4 09:09:24 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 5FE35128B37 for <ietf@ietfa.amsl.com>; Sun,  4 Jun 2017 09:09:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] 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 MBQ2hryCNdfO for <ietf@ietfa.amsl.com>; Sun,  4 Jun 2017 09:09:21 -0700 (PDT)
Received: from mail.smeinc.net (x-bolt-wan.smeinc.net [209.135.219.146]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 256DE120727 for <ietf@ietf.org>; Sun,  4 Jun 2017 09:09:21 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 4A7DC300494 for <ietf@ietf.org>; Sun,  4 Jun 2017 12:09:20 -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 Hp2dupgFtauX for <ietf@ietf.org>; Sun,  4 Jun 2017 12:09:18 -0400 (EDT)
Received: from a860b60074bd.home (pool-108-45-101-150.washdc.fios.verizon.net [108.45.101.150]) by mail.smeinc.net (Postfix) with ESMTPSA id 4C955300265; Sun,  4 Jun 2017 12:09:18 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [Curdle] Genart last call review of draft-ietf-curdle-cms-ecdh-new-curves-07
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <149570983670.8681.5001417855088402577@ietfa.amsl.com>
Date: Sun, 4 Jun 2017 12:09:18 -0400
Cc: IETF Gen-ART <gen-art@ietf.org>, curdle <curdle@ietf.org>, IETF <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <B182B0C5-DDB8-4CC7-9E64-2A8A5DD43C15@vigilsec.com>
References: <149570983670.8681.5001417855088402577@ietfa.amsl.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ub4HdGyIa2EZ40ofAWzsNw0cAuA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 04 Jun 2017 16:09:22 -0000

Roni:

Thanks for the review.  I believe that -09 resolves your comments.

Russ


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


From nobody Mon Jun  5 07:27:51 2017
Return-Path: <lists@digitaldissidents.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 B58DB129AA4 for <ietf@ietfa.amsl.com>; Mon,  5 Jun 2017 07:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 sHsrJt2W5DIV for <ietf@ietfa.amsl.com>; Mon,  5 Jun 2017 07:27:47 -0700 (PDT)
Received: from smarthost1.greenhost.nl (smarthost1.greenhost.nl [195.190.28.81]) (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 857D5129A9D for <ietf@ietf.org>; Mon,  5 Jun 2017 07:27:47 -0700 (PDT)
Received: from smtp.greenhost.nl ([213.108.104.138]) by smarthost1.greenhost.nl with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <lists@digitaldissidents.org>) id 1dHsyu-0001e4-UN for ietf@ietf.org; Mon, 05 Jun 2017 16:27:45 +0200
To: ietf@ietf.org
From: Niels ten Oever <lists@digitaldissidents.org>
Subject: Guidelines for Human Rights Considerations
Message-ID: <8bae88ce-ff3b-18cc-64dd-51cf5e8f2cb6@digitaldissidents.org>
Date: Mon, 5 Jun 2017 16:27:44 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Authenticated-As-Hash: 29cc722430e8f1f6ed904119444c0d49b0f3ee91
X-Virus-Scanned: by clamav at smarthost1.samage.net
X-Scan-Signature: 8b3222cd26cce149ddb9ffa05c4da76e
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/I4qDg7twsGDRhiCHsa41AFaZJcI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jun 2017 14:27:49 -0000

Dear all,

I hope this email finds you all very well. As a follow-up to the
technical plenary at IETF98 about human rights [0] I would like to
invite people who are working on Internet Drafts to use the Guidelines
for Human Rights Considerations [1] to review their draft.

Within the hrpc research group [2] we're very interested in your
findings and hear the outcomes of your review, answer questions, or use
your suggestions on how to make the guidelines better or otherwise more
relevant.

Feel free to send me an email off-list, post to the hrpc list [3] or
discuss it here. You might even be interested to present your findings
at the hrpc session in Prague.

Best,

Niels


[0] https://www.youtube.com/watch?v=qvgIX3-pAZE&feature=youtu.be&t=1h3m34s

[1] https://tools.ietf.org/html/draft-irtf-hrpc-research-13#section-6.2

[2] https://irtf.org/hrpc

[3] https://www.irtf.org/mailman/listinfo/hrpc

-- 
Niels ten Oever
Head of Digital

Article 19
www.article19.org

PGP fingerprint    8D9F C567 BEE4 A431 56C4
                     678B 08B5 A0F2 636D 68E9


From nobody Mon Jun  5 13:51:26 2017
Return-Path: <peter@filament.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 428581294E7 for <ietf@ietfa.amsl.com>; Mon,  5 Jun 2017 13:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=filament-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 UkbDc-BvUPSj for <ietf@ietfa.amsl.com>; Mon,  5 Jun 2017 13:51:23 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::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 995D1129408 for <ietf@ietf.org>; Mon,  5 Jun 2017 13:51:23 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id m62so74425225itc.0 for <ietf@ietf.org>; Mon, 05 Jun 2017 13:51:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=filament-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Fyf29xjVdadQ/A1qPiRvpJSTIExvLYJK2lb+FCzTP4M=; b=AOcbW9/YfTO/KmrL4qFTZdgsHSpkpmnHQYSERdsupGrLvb++AVYXvM6a12yN3CYJ81 9IQOJfKYNN1q87FrYzN5YEN8WYP8Ve9XOCs9yFGeeMF4j95yzzx1F1oWHjXxJfi6b+mU fEWHR4Gh9psTUfJK/EXFKOOT8xdNZGzgHyJQzNlDh3/qknd55WQpL8o+DmFNLDFzrdKu nqEokQ6QDj4bXOL3llE887+ptIVNa2oagBWfAvC8jiJOlpNtE3oidN0s6b12EmVWwmnU baIHSe3m+L8fN1N9knDt/xt2AOrWyyE9NFF+KNyaPSW0UJAScGgUoMZhkGprRwBvr/tC F4gQ==
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=Fyf29xjVdadQ/A1qPiRvpJSTIExvLYJK2lb+FCzTP4M=; b=G8CJ4ULo3AiRy/hHaPG8rdiLyquXiDOdEzbLjBfRbJFcRyhIy1OfMvbpoyhMv91eXI zSX4YY3QQ7j1c1wwUZ+sp2D8LJZnY/EnQRVE1RH8wWZlIP+6ej3ri1o4Iy+ZPL5D+ust jQ2dy1RZd5A6ZZx1323o2rTION0Kn14N0jAspPp0yNtSiPidzvyNUhlqrZqAN+iMyRri p29xB579PjyuSg4fcXzhRSmD20PMOPffk+6g861k3mOuiBG3sSvdgDCLQCJNVWF5ZhnE D73DhX01XQJ8p5reGPN7nDRchSsdIb6nidzoLVDmE284dLIO4KcAxWxbGpXSHMF14bir 4E3w==
X-Gm-Message-State: AODbwcDsh9NOoUfZyF+01FxxmhCW90rWOtZmjhewG+soHAbaQCEoYSVl 5QuFIBD34yOHO/7El+3Dvw==
X-Received: by 10.107.147.86 with SMTP id v83mr23927796iod.233.1496695883000;  Mon, 05 Jun 2017 13:51:23 -0700 (PDT)
Received: from aither.local (c-98-245-40-52.hsd1.co.comcast.net. [98.245.40.52]) by smtp.gmail.com with ESMTPSA id e73sm2168056ioj.17.2017.06.05.13.51.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 05 Jun 2017 13:51:22 -0700 (PDT)
Subject: Re: Genart last call review of draft-ietf-precis-7700bis-07
To: Russ Housley <housley@vigilsec.com>, gen-art@ietf.org
References: <149626145570.19916.16628797750334932421@ietfa.amsl.com>
Cc: precis@ietf.org, ietf@ietf.org, draft-ietf-precis-7700bis.all@ietf.org
From: Peter Saint-Andre - Filament <peter@filament.com>
Message-ID: <322a3c4f-24d7-f971-663e-50d4e64eb25d@filament.com>
Date: Mon, 5 Jun 2017 14:51:20 -0600
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: <149626145570.19916.16628797750334932421@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/quP2DuYA1teyZATK3SNGQEG2qnQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 05 Jun 2017 20:51:25 -0000

Hi Russ, thanks for your review and my apologies for the delayed reply.

On 5/31/17 2:10 PM, Russ Housley wrote:
> 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?

That seems better, yes!

Peter



From nobody Tue Jun  6 08:36:15 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 1ED42129512 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 08:36:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yM9w9lpytLEK for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 08:36:12 -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 D51561294F3 for <ietf@ietf.org>; Tue,  6 Jun 2017 08:36:12 -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 1dIGWg-0001O7-VM for ietf@ietf.org; Tue, 06 Jun 2017 15:36:11 +0000
Date: Tue, 06 Jun 2017 21:36:07 +0600
Message-ID: <m27f0pqgbc.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Rinse Repeat <ietf@ietf.org>
Subject: wireless geolocation
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/gOy11kbr-PKCE9eWaB2Qmq5Mqws>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 15:36:14 -0000

you may have noticed, when you get to an ietf meeting and get on the
wireless, you will often geolocate to the last city on the eternal tour.
this is because access point bssids are recorded by a number of
geolocation providers and those location data are then used by
application providers.

the noc tries to deal with this, but it is a manual mess involving
trying to convince geoloc providers to do complex things such as answer
their frelling email.  the pain is not congruent with the fix.

the ietf is far from the only event with this problem.  but it is kind
of in our purview to automate it.  the noc is not the place to work on
protocols and databases; the noc is just the customer/user.  a bof or
some existing wg might be.

oh, and warning.  there is a significant chance we will see the issue in
praha as we have been unable to get a response from one major geoloc
provider (not google; they were wonderfully responsive).

randy


From nobody Tue Jun  6 09:35:39 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BF561292F5 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 09:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7lh-NCluHwHn for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 09:35:36 -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 B2371126DCA for <ietf@ietf.org>; Tue,  6 Jun 2017 09:35:36 -0700 (PDT)
Received: by mail-qt0-x22e.google.com with SMTP id u19so78526931qta.3 for <ietf@ietf.org>; Tue, 06 Jun 2017 09:35:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=5EJQhGpgXTlUNmVlGPpoRErOcekqAx9RBL6JKZjGJO0=; b=E+gSrDPglAmnNXge4bL353BSmcxAx1Nv5JQSHDcpEFqW2rMzabQYUi5HvTfA+isTWn 0evqCct4I+J9SC3O4oeYXKnIG0FFzcU8J/plSG1NKcm2agJb+D0agmRS+8G9NtcSH8O3 QTb0cB1lnKjMkN1B35dnIULD/Ep5P1MECri24zPQjMjq16kw+JXrRiAXZrZUaOVHElIo CM8h8jvmPoRf1LM6S5mDMiRtI+hZUjyvRukvjIu4YaQwc2LOS931zjtnStjqw04nXIIP wNBkTdcsUT+biOH2NMeiPpUAW/wkBhY/dRAKNEZlppDhMuzrs81sp0BIpXVP55oMJuuX kqJQ==
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=5EJQhGpgXTlUNmVlGPpoRErOcekqAx9RBL6JKZjGJO0=; b=Khfsvh4FZ1PwQ9C4aigfC6GKhakcHRqzYj5BMYWHqjCx3NPkS3tQuOGTesjxXKxx2S PEld970pN/hwS0uFNB/yVbMqaAm7oww5cOVqD/fGH44uSy25uy/IcrZa4etTNQKU+ngZ brBWp2sx4IoiBmel9Sv/mwx61FLND6A1PEDBG3053GwsISqJqLw7whImWej8k1MaWral mZ9ve9f72ZzYMtS9d+km7AycqidfetsUXMgA8VBx5KN4UokKfkO2meNJC/iRnZxZ6mln otJaXRDoor8CWSyR2UTr7ycKKwT1wbhu7sX9x02hrpt0wO+1pEmHAF5MBnRIizk97gHp VypQ==
X-Gm-Message-State: AODbwcB/e4gqQxGNEitpkz1XKJys91X/CDQHKqTUEP7Tq5xiHQnmhL/b pEB25ztkx/56WrSO
X-Received: by 10.237.36.154 with SMTP id t26mr31405485qtc.180.1496766935431;  Tue, 06 Jun 2017 09:35:35 -0700 (PDT)
Received: from [10.0.30.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id 34sm5553070qtn.45.2017.06.06.09.35.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jun 2017 09:35:31 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: wireless geolocation
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <m27f0pqgbc.wl-randy@psg.com>
Date: Tue, 6 Jun 2017 12:35:30 -0400
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <50E30AF8-6D05-4698-AC71-70A0179F703E@fugue.com>
References: <m27f0pqgbc.wl-randy@psg.com>
To: Randy Bush <randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xQ_-zaWbiHnD667LgJB8sehrj7I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 16:35:38 -0000

Why do we even have a stable IP address range anymore?   It seems like =
an unnecessary lift.   If we just take what the ISP offers (IPv4 and =
IPv6) and use that, why is that not good enough?


From nobody Tue Jun  6 09:48:48 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 41A48126DCA for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 09:48:47 -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 Lpy4meVH6eYM for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 09:48:45 -0700 (PDT)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::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 A2D23128D69 for <ietf@ietf.org>; Tue,  6 Jun 2017 09:48:45 -0700 (PDT)
Received: by mail-ua0-x22f.google.com with SMTP id q15so11733681uaa.2 for <ietf@ietf.org>; Tue, 06 Jun 2017 09:48:45 -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=4qEWrqnpIEHxF1uZAedL5mRxRzm9fgwXsewc8SpvzjE=; b=XkpM031GsjeWiweOed9oMgsNUAez6vD/YnpkX2NW0K/0+8zFs/HaID+6KZlXPLlFbn h+RJYQ6RUCkOD6Kdtpjxdqp7p0JF/+0KwTJaiN/NM7Caks5uPNV+8Gp0UlyfySdhlZba TM2sFqL9e1vqwWloZxq+JAodxT5UhtZFNRaX8xUFVH6mK+n/iJk2xptsJXPQFslzhTf4 B755/m3HNo6CsuWZZlpx5bO39gPNqS4AZwtVorrg0wk8k6GJNP3kb05lcbPsGbo8eaSP ZoNpLvPXkcf7wqVIf8HpuopE48wj1hp6iFCkqeHRXUssbcdtxZ+WrFzMWVATvtNNeJXW cQlw==
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=4qEWrqnpIEHxF1uZAedL5mRxRzm9fgwXsewc8SpvzjE=; b=la8Aiy5eAwUZrklKgdq+eJJnTSfzTVKEst3Y7Wye/atIghMQCLCxLCjABZgGvDfOAK 5VTdknnAJ241uOF3GS9+o3TLWFx8SbS9ATjM9+YXBjyI193b9aT/tF4XGndDir0SKKJV hT+EMVD/uwPzEhovNnD9WVy8eOCTY4Kbk1oQ9OgoNHBDDsuX5EPIWmqT9zjhXti9hTAq 87dkz7bDzcnLZQ3l10+rGDQWCkOAaovDxRAR5cD/dDkm0AdQSt5VLropQYxmSjPAABO/ WxjfouGhiY8GLoAH5Z/bZT8rgtrqfjSAgm3XoqyYBUophGycbB/Fo7BZTaPZCfdwc4/Y e53g==
X-Gm-Message-State: AODbwcBO4JBV6eIZlAuILjshSc65gnwNQYKNPlJfAkNTiBsWw4sOrAlK u5R6JPp6wRvtiTdYv7lNuTVzjpAldF8BFW6RjQ==
X-Received: by 10.159.59.94 with SMTP id j30mr13114861uah.72.1496767724645; Tue, 06 Jun 2017 09:48:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.82.198 with HTTP; Tue, 6 Jun 2017 09:48:04 -0700 (PDT)
In-Reply-To: <50E30AF8-6D05-4698-AC71-70A0179F703E@fugue.com>
References: <m27f0pqgbc.wl-randy@psg.com> <50E30AF8-6D05-4698-AC71-70A0179F703E@fugue.com>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 6 Jun 2017 12:48:04 -0400
Message-ID: <CAHw9_iKpKJA4ruNSR=Zq3ocu7ORwHVrNCnF3H0LJqDL5FrPMuA@mail.gmail.com>
Subject: Re: wireless geolocation
To: Ted Lemon <mellon@fugue.com>
Cc: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iErPr_JyPHjHx5ndjqmeDXSpok0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 16:48:47 -0000

On Tue, Jun 6, 2017 at 12:35 PM, Ted Lemon <mellon@fugue.com> wrote:
> Why do we even have a stable IP address range anymore?   It seems like an unnecessary lift.   If we just take what the ISP offers (IPv4 and IPv6) and use that, why is that not good enough?

Because we use a *large* amount of address space - we (currently) give
everyone a public IP address, we have multiple SSIDs / networks, etc.
ISPs would be quite unlikely to be willing to give us a big enough
block, we (often) also have multiple providers, etc. We would also
need to renumber all of our infrastructure, redo DNS, etc.

We currently publish geo-location info in
https://tools.ietf.org/html/draft-google-self-published-geofeeds-02
format -- noc.ietf.org/geo/google.csv. This gets updated (assuming I /
we don't forget :-)) before each meeting, and should be imported by
google in advance of the meeting...

But, much of the issue is location being tied to the MAC address of
the APs, not just the source IP. There are lots of geo providers, and
they all need to be updated, etc.


W

-- 
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 Tue Jun  6 09:56:01 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B9C7129AF3 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 09:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DuosyHz8L5FI for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 09:55:58 -0700 (PDT)
Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::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 8BA48129B0D for <ietf@ietf.org>; Tue,  6 Jun 2017 09:55:57 -0700 (PDT)
Received: by mail-qt0-x22f.google.com with SMTP id c10so82365465qtd.1 for <ietf@ietf.org>; Tue, 06 Jun 2017 09:55:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=kVvYMIBQc/4BFBLLNHIWM6kR0vLqwqqkf+fcmgss/dg=; b=LZEc21C0kvLIP3IWOqiBo6umih8ek6Ld2cdrcAkcEEoKnsjMrcxKacq2Xkdk6u/TUm 5WjBrx1WevTEkzSuutLzB5rPRS77lGxRUoQBARb2EOTST1p9tORyBWatsNSkplnV6IOC 8n0prFa5hO+rJ246+ALdr6iec1rYu1lLCDUXKVgiKeMD62+T5bI812LbBq2A4+8rYnqX k64qx5sbTvGsjq0H+L3lcRrlyfJjOE+TXoNSz94DO23MnasLIAhbSSU76mQ865572KFD TTNzHScZUn5dukTwrGPJ93NNTRNmAp6a7HqRlckA/6xH9nBat+Zsq0AmMFgHkqZehsNc Nbmw==
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=kVvYMIBQc/4BFBLLNHIWM6kR0vLqwqqkf+fcmgss/dg=; b=p7+4XwB4LYwrxhjdfxbuKksu57aUCy8/BU4SqYOuDY1DxOMalnYqEUOWGSl+emFnmh GFP/yyBrmbXDl0pPgWba0wjc+D98NEnRmYv8AgQT9ceLKH63kc6FzwL4VP6oy4Lwr8ns 1q0tV/BYJ/ZR5//Hg3hdAhgDiJSaGxynRbMZuV/YkSEhvVNiiupSugChssZ/KeC9lPaN R3bBRENXnqprvlC7+OENVT9mTgztXFLKxarmKC6iYhaY7la8Uhem6S5Z/VeMHhIE8lHY CRe294p7/6c4RIhu3N5pmnoREaS5zpnvGX9XUFNqaxj1f3cp9rpK5afwUrcV7yRKNX81 DU5A==
X-Gm-Message-State: AODbwcCc6veHii7yerZ4J3DkbmBQmnzHIkjJYI7PRg84unv4whqHbPwt 5D6dtQKuB9apAALMjdC6nQ==
X-Received: by 10.200.45.83 with SMTP id o19mr25250803qta.43.1496768156616; Tue, 06 Jun 2017 09:55:56 -0700 (PDT)
Received: from [10.0.30.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id t13sm8807771qtc.22.2017.06.06.09.55.55 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jun 2017 09:55:55 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <6E9EEE15-1A71-485C-9321-4068AB39AE0F@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A1B4F366-C542-4E1B-ACBB-8404A1592F35"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: wireless geolocation
Date: Tue, 6 Jun 2017 12:55:54 -0400
In-Reply-To: <CAHw9_iKpKJA4ruNSR=Zq3ocu7ORwHVrNCnF3H0LJqDL5FrPMuA@mail.gmail.com>
Cc: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
To: Warren Kumari <warren@kumari.net>
References: <m27f0pqgbc.wl-randy@psg.com> <50E30AF8-6D05-4698-AC71-70A0179F703E@fugue.com> <CAHw9_iKpKJA4ruNSR=Zq3ocu7ORwHVrNCnF3H0LJqDL5FrPMuA@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nX9deLT_93fGTOE9LnTcxDedWUM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 16:56:00 -0000

--Apple-Mail=_A1B4F366-C542-4E1B-ACBB-8404A1592F35
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jun 6, 2017, at 12:48 PM, Warren Kumari <warren@kumari.net> wrote:
> Because we use a *large* amount of address space - we (currently) give
> everyone a public IP address, we have multiple SSIDs / networks, etc.
> ISPs would be quite unlikely to be willing to give us a big enough
> block, we (often) also have multiple providers, etc. We would also
> need to renumber all of our infrastructure, redo DNS, etc.

Please understand when I say this that I am not proposing an unfunded =
mandate on the backs of volunteers here, but (a) it doesn't seem to me =
that we need to continue providing everyone with a routable IPv4 =
address, and (b) if renumbering is that hard, maybe that's worth =
thinking about, because renumbering is not generally all that hard, and =
we have developed a lot of technology in the IETF to _make_ it not hard.

E.g., if everything is numbered using IPv6, and the reason it needs =
numbered is so that it can be managed, wouldn't a ULA prefix for =
numbering managed devices solve that problem?   Or are we still managing =
them using stone knives and IPv4?

> We currently publish geo-location info in
> https://tools.ietf.org/html/draft-google-self-published-geofeeds-02 =
<https://tools.ietf.org/html/draft-google-self-published-geofeeds-02>
> format -- noc.ietf.org/geo/google.csv =
<http://noc.ietf.org/geo/google.csv>. This gets updated (assuming I /
> we don't forget :-)) before each meeting, and should be imported by
> google in advance of the meeting...

Apparently that's not solving the problem, though.   Google maps always =
seems to redirect me to the previous country, every IETF.   I think this =
is more of an operational problem than not having a routable IPv4 =
address would be=E2=80=94I don't assume when I'm traveling that I will =
have a routable IPv4 address.

> But, much of the issue is location being tied to the MAC address of
> the APs, not just the source IP. There are lots of geo providers, and
> they all need to be updated, etc.

Can't APs have their user-facing MAC addresses changed/randomized?   =
Again, I realize that that potentially another unfunded mandate, but I'm =
just asking whether this is something that can be done, not saying you =
should do it.


--Apple-Mail=_A1B4F366-C542-4E1B-ACBB-8404A1592F35
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jun 6, 2017, at 12:48 PM, Warren Kumari &lt;<a =
href=3D"mailto:warren@kumari.net" class=3D"">warren@kumari.net</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Because we use a =
*large* amount of address space - we (currently) give</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">everyone a public IP address, we have multiple =
SSIDs / networks, etc.</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">ISPs would be quite =
unlikely to be willing to give us a big enough</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">block, we (often) also have multiple providers, =
etc. We would also</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">need to renumber =
all of our infrastructure, redo DNS, etc.</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote><div><br class=3D""></div>Please =
understand when I say this that I am not proposing an unfunded mandate =
on the backs of volunteers here, but (a) it doesn't seem to me that we =
need to continue providing everyone with a routable IPv4 address, and =
(b) if renumbering is that hard, maybe that's worth thinking about, =
because renumbering is not generally all that hard, and we have =
developed a lot of technology in the IETF to _make_ it not =
hard.</div><div><br class=3D""></div><div>E.g., if everything is =
numbered using IPv6, and the reason it needs numbered is so that it can =
be managed, wouldn't a ULA prefix for numbering managed devices solve =
that problem? &nbsp; Or are we still managing them using stone knives =
and IPv4?</div><div><br class=3D""></div><div><blockquote type=3D"cite" =
class=3D""><div class=3D""><span style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">We currently publish geo-location info =
in</span><br style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><a =
href=3D"https://tools.ietf.org/html/draft-google-self-published-geofeeds-0=
2" style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; orphans: auto; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; widows: auto; word-spacing: =
0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;" =
class=3D"">https://tools.ietf.org/html/draft-google-self-published-geofeed=
s-02</a><br style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">format --<span =
class=3D"Apple-converted-space">&nbsp;</span></span><a =
href=3D"http://noc.ietf.org/geo/google.csv" style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">noc.ietf.org/geo/google.csv</a><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">. This gets updated (assuming I =
/</span><br style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">we don't forget :-)) before each meeting, =
and should be imported by</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">google in advance =
of the meeting...</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""></div></blockquote><div><br class=3D""></div>Apparently =
that's not solving the problem, though. &nbsp; Google maps always seems =
to redirect me to the previous country, every IETF. &nbsp; I think this =
is more of an operational problem than not having a routable IPv4 =
address would be=E2=80=94I don't assume when I'm traveling that I will =
have a routable IPv4 address.</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">But, much of the issue is location being =
tied to the MAC address of</span><br style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">the APs, not just =
the source IP. There are lots of geo providers, and</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">they all need to be updated, =
etc.</span></div></blockquote></div><br class=3D""><div class=3D"">Can't =
APs have their user-facing MAC addresses changed/randomized? &nbsp; =
Again, I realize that that potentially another unfunded mandate, but I'm =
just asking whether this is something that can be done, not saying you =
should do it.</div><div class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_A1B4F366-C542-4E1B-ACBB-8404A1592F35--


From nobody Tue Jun  6 10:45:58 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 2283A129B16 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 10:45:57 -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, HTML_MESSAGE=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 6cjLyZpuUZyh for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 10:45:54 -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 A34E8129415 for <ietf@ietf.org>; Tue,  6 Jun 2017 10:45:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 6A8201CA392; Tue,  6 Jun 2017 10:45:51 -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 jysSoOr1Y2jX; Tue,  6 Jun 2017 10:45:51 -0700 (PDT)
Received: from [10.149.48.22] (guest-wifi.norwich.edu [192.149.109.217]) by c8a.amsl.com (Postfix) with ESMTPSA id D823D1CA42D; Tue,  6 Jun 2017 10:45:50 -0700 (PDT)
From: Alexa Morris <amorris@amsl.com>
Message-Id: <5A9F7925-D251-4DD1-9E5B-109334A2CE0D@amsl.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_DE52976D-E66A-41A2-8694-497D153939B1"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IPv10, KRP, and RRP IDs Removal.
Date: Tue, 6 Jun 2017 10:45:52 -0700
In-Reply-To: <AM4PR0401MB22412175971281B33515B7B7BDFC0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
To: Khaled Omar <eng.khaled.omar@hotmail.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> <313AD8B1-7D69-4C8C-A750-97004D26BE34@amsl.com> <AM4PR0401MB22412175971281B33515B7B7BDFC0@AM4PR0401MB2241.eurprd04.prod.outlook.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oUwC8jVo8pI0HQ7lx734RXTAVec>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 17:45:57 -0000

--Apple-Mail=_DE52976D-E66A-41A2-8694-497D153939B1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Khaled,

The IESG has denied your request to remove your Internet-Draft. There is =
no legal right to remove your Internet-Draft from the I-D repository. =
Draft draft-omar-krp-01 contains the statement "This Internet-Draft is =
submitted in full conformance with the provisions of BCP 78 and BCP =
79.=E2=80=9D The complete text of BCP 78 is can be found at =
https://datatracker.ietf.org/doc/rfc5378 =
<https://datatracker.ietf.org/doc/rfc5378> but I will specifically point =
out section 5.3, below:

"5.3.  Rights Granted by Contributors to the IETF Trust

To the extent that a Contribution or any portion thereof is protected by =
copyright or other rights of authorship, the Contributor and each named =
co-Contributor grant a perpetual, irrevocable, non-exclusive, =
royalty-free, world-wide, sublicensable right and license to the IETF =
Trust under all such copyrights and other rights in the Contribution:

a. to copy, publish, display, and distribute the Contribution, in whole =
or in part,

b. to prepare translations of the Contribution into languages other than =
English, in whole or in part, and to copy, publish, display, and =
distribute such translations or portions thereof,

c. to modify or prepare derivative works (in addition to translations) =
that are based on or incorporate all or part of the Contribution, and to =
copy, publish, display, and distribute such derivative works, or =
portions thereof unless explicitly disallowed in the notices contained =
in a Contribution (in the form specified by the Legend Instructions), =
and

d. to reproduce any trademarks, service marks, or trade names which are =
included in the Contribution solely in connection with the  =
reproduction, distribution, or publication of the Contribution and =
derivative works thereof as permitted by this Section 5.3, provided that =
when reproducing Contributions, trademark and service mark identifiers =
used in the Contribution, including TM and (R), will be preserved."

By submitting an Internet-Draft to the IETF, you have granted the IETF =
Trust perpetual, irrevocable rights to publish it. I regret to inform =
you that you cannot retract these rights. However, provided that you do =
not submit a new version of the draft, it will expire on November 8, =
2017 and at that point will no longer appear as an active =
Internet-Draft.

Regards,

Alexa =20
IETF Executive Director


> On May 26, 2017, at 9:02 AM, Khaled Omar <eng.khaled.omar@hotmail.com> =
wrote:
>=20
> Hi,
>=20
>> 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.
>=20
> I didn't mention any reason for the request to remove my uploaded IDs, =
I'm the only author of these drafts, I made a request 6 months ago for =
uploading the 1st draft (IPv10) and now I'm requesting to remove them =
all, I'm not requesting someone else draft removal, the mentioned IDs =
are not of interest of the ietf members or participants, no reviewer(s) =
assigned officially for them, no wg created, and there was even no =
respect for the remote presentation where the microphone was muted =
during the presentation and didn't get the chance to continue the IPv10 =
presentation, this is one of the main reasons I asked for removing, they =
must not represent the ietf anymore.
>=20
> We shouldn't wait for the drafts to be expired and be useless as I'll =
not update them again on the ietf repository.
>=20
> Again, I repeat my request with full respect to all ietf and iesg =
members to remove my drafts and they must not be stored without =
informing the author of these drafts, full removal requested and nothing =
bad with it.
>=20
> Regards,
>=20
> Khaled Omar
>=20
>=20
> -----Original Message-----
> From: Alexa Morris [mailto:amorris@amsl.com]=20
> Sent: Friday, May 26, 2017 5:03 PM
> To: Khaled Omar
> Cc: ietf@ietf.org
> Subject: Re: IPv10, KRP, and RRP IDs Removal.
>=20
> Khaled,
>=20
> The IESG has reviewed your request and the drafts will not be removed. =
Their response directly below:
>=20
> ---------
> Alexa,
>=20
> 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.
>=20
> Regards,
> The IESG
>=20
> --------
> On May 22, 2017, at 5:54 PM, Khaled Omar <eng.khaled.omar@hotmail.com> =
wrote:
>=20
>> 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]
>> 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
>=20
> ----------
> Alexa Morris / Executive Director / IETF
> +1.510.492.4001
> Email: amorris@amsl.com
>=20
>=20
>=20


--Apple-Mail=_DE52976D-E66A-41A2-8694-497D153939B1
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"">Khaled,<div class=3D""><br class=3D""></div><div class=3D"">The=
 IESG has denied your request to remove your Internet-Draft. There is no =
legal right to remove your Internet-Draft from the I-D repository. Draft =
draft-omar-krp-01 contains the statement "This Internet-Draft is =
submitted in full conformance with the provisions of BCP 78 and BCP =
79.=E2=80=9D The complete text of BCP 78 is can be found at&nbsp;<a =
href=3D"https://datatracker.ietf.org/doc/rfc5378" =
class=3D"">https://datatracker.ietf.org/doc/rfc5378</a>&nbsp;but I will =
specifically point out section 5.3, below:</div><div class=3D""><br =
class=3D""></div><div class=3D"">"5.3. &nbsp;Rights Granted by =
Contributors to the IETF Trust<br class=3D""><br class=3D""><div =
class=3D"">To the extent that a Contribution or any portion thereof is =
protected by copyright or other rights of authorship, the Contributor =
and each named co-Contributor grant a perpetual, irrevocable, =
non-exclusive, royalty-free, world-wide, sublicensable right and license =
to the IETF Trust under all such copyrights and other rights in the =
Contribution:</div><div class=3D""><br class=3D""></div><div class=3D"">a.=
 to copy, publish, display, and distribute the Contribution, in whole or =
in part,</div><div class=3D""><br class=3D""></div><div class=3D"">b. to =
prepare translations of the Contribution into languages other than =
English, in whole or in part, and to copy, publish, display, and =
distribute such translations or portions thereof,</div><div class=3D""><br=
 class=3D""></div><div class=3D"">c. to modify or prepare derivative =
works (in addition to translations) that are based on or incorporate all =
or part of the Contribution, and to copy, publish, display, and =
distribute such derivative works, or portions thereof unless explicitly =
disallowed in the notices contained in a Contribution (in the form =
specified by the Legend Instructions), and</div><div class=3D""><br =
class=3D""></div><div class=3D"">d. to reproduce any trademarks, service =
marks, or trade names which are included in the Contribution solely in =
connection with the &nbsp;reproduction, distribution, or publication of =
the Contribution and derivative works thereof as permitted by this =
Section 5.3, provided that when reproducing Contributions, trademark and =
service mark identifiers used in the Contribution, including TM and (R), =
will be preserved."</div></div><div class=3D""><br class=3D""></div><div =
class=3D"">By submitting an Internet-Draft to the IETF, you have granted =
the IETF Trust perpetual, irrevocable rights to publish it. I regret to =
inform you that you cannot retract these rights. However, provided that =
you do not submit a new version of the draft, it will expire on November =
8, 2017 and at that point will no longer appear as an active =
Internet-Draft.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Regards,</div><div class=3D""><br class=3D""></div><div =
class=3D"">Alexa &nbsp;</div><div class=3D"">IETF Executive =
Director</div><div class=3D""><br class=3D""></div><div class=3D""><br =
class=3D""></div><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On May 26, 2017, at 9:02 AM, Khaled Omar &lt;<a =
href=3D"mailto:eng.khaled.omar@hotmail.com" =
class=3D"">eng.khaled.omar@hotmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div class=3D"">Hi,<br=
 class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">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.<br class=3D""></blockquote><br class=3D"">I didn't mention any =
reason for the request to remove my uploaded IDs, I'm the only author of =
these drafts, I made a request 6 months ago for uploading the 1st draft =
(IPv10) and now I'm requesting to remove them all, I'm not requesting =
someone else draft removal, the mentioned IDs are not of interest of the =
ietf members or participants, no reviewer(s) assigned officially for =
them, no wg created, and there was even no respect for the remote =
presentation where the microphone was muted during the presentation and =
didn't get the chance to continue the IPv10 presentation, this is one of =
the main reasons I asked for removing, they must not represent the ietf =
anymore.<br class=3D""><br class=3D"">We shouldn't wait for the drafts =
to be expired and be useless as I'll not update them again on the ietf =
repository.<br class=3D""><br class=3D"">Again, I repeat my request with =
full respect to all ietf and iesg members to remove my drafts and they =
must not be stored without informing the author of these drafts, full =
removal requested and nothing bad with it.<br class=3D""><br =
class=3D"">Regards,<br class=3D""><br class=3D"">Khaled Omar<br =
class=3D""><br class=3D""><br class=3D"">-----Original Message-----<br =
class=3D"">From: Alexa Morris [<a href=3D"mailto:amorris@amsl.com" =
class=3D"">mailto:amorris@amsl.com</a>] <br class=3D"">Sent: Friday, May =
26, 2017 5:03 PM<br class=3D"">To: Khaled Omar<br class=3D"">Cc: <a =
href=3D"mailto:ietf@ietf.org" class=3D"">ietf@ietf.org</a><br =
class=3D"">Subject: Re: IPv10, KRP, and RRP IDs Removal.<br class=3D""><br=
 class=3D"">Khaled,<br class=3D""><br class=3D"">The IESG has reviewed =
your request and the drafts will not be removed. Their response directly =
below:<br class=3D""><br class=3D"">---------<br class=3D"">Alexa,<br =
class=3D""><br class=3D"">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.<br class=3D""><br class=3D"">Regards,<br =
class=3D"">The IESG<br class=3D""><br class=3D"">--------<br class=3D"">On=
 May 22, 2017, at 5:54 PM, Khaled Omar &lt;<a =
href=3D"mailto:eng.khaled.omar@hotmail.com" =
class=3D"">eng.khaled.omar@hotmail.com</a>&gt; wrote:<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">As mentioned in the =
provided link:<br class=3D""><br class=3D"">"Internet-Drafts have no =
formal status, and are subject to change or removal at any time."<br =
class=3D""><br class=3D""><blockquote type=3D"cite" class=3D"">which =
explains that IESG consensus is required in order to remove an Internet =
Draft from the I-D Repository.<br class=3D""></blockquote><br =
class=3D"">=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.<br class=3D""><br class=3D"">I'm waiting for =
the IESG response ... I hope they can make a decision soon.<br =
class=3D""><br class=3D"">"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."<br class=3D""><br class=3D"">This of course doesn't gives =
the ietf the right of making any usage of these I-Ds after its =
removal.<br class=3D""><br class=3D""><br class=3D""><br =
class=3D"">-----Original Message-----<br class=3D"">From: Alexa Morris =
[<a href=3D"mailto:amorris@amsl.com" =
class=3D"">mailto:amorris@amsl.com</a>]<br class=3D"">Sent: Tuesday, May =
23, 2017 2:27 AM<br class=3D"">To: Khaled Omar<br class=3D"">Cc: Ole J. =
Jacobsen; <a href=3D"mailto:ietf@ietf.org" class=3D"">ietf@ietf.org</a><br=
 class=3D"">Subject: Re: IPv10, KRP, and RRP IDs Removal.<br =
class=3D""><br class=3D"">Khaled,<br class=3D""><br class=3D"">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 <a =
href=3D"https://www.ietf.org/iesg/statement/removal-of-an-internet-draft.h=
tml" =
class=3D"">https://www.ietf.org/iesg/statement/removal-of-an-internet-draf=
t.html</a>, which explains that IESG consensus is required in order to =
remove an Internet Draft from the I-D Repository.<br class=3D""><br =
class=3D"">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. <br class=3D""><br =
class=3D"">Regards,<br class=3D"">Alexa<br class=3D""><br class=3D"">On =
May 22, 2017, at 7:09 PM, Khaled Omar &lt;<a =
href=3D"mailto:eng.khaled.omar@hotmail.com" =
class=3D"">eng.khaled.omar@hotmail.com</a>&gt; wrote:<br class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D"">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.<br class=3D""><br =
class=3D"">-----Original Message-----<br class=3D"">From: Ole Jacobsen =
[<a href=3D"mailto:olejacobsen@me.com" =
class=3D"">mailto:olejacobsen@me.com</a>]<br class=3D"">Sent: Tuesday, =
May 23, 2017 1:02 AM<br class=3D"">To: Khaled Omar<br class=3D"">Subject: =
Re: IPv10, KRP, and RRP IDs Removal.<br class=3D""><br class=3D""><br =
class=3D"">You really have no idea how the IETF works, do you?<br =
class=3D""><br class=3D""><br class=3D"">On Mon, 22 May 2017, Khaled =
Omar wrote:<br class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D"">Hi Jasmine,<br class=3D""><br class=3D"">As I'm the only =
author of the following IDs:<br class=3D""><br class=3D""><br =
class=3D"">1) Internet Protocol version 10 (IPv10): <br class=3D""><a =
href=3D"https://datatracker.ietf.org/doc/draft-omar-ipv10/" =
class=3D"">https://datatracker.ietf.org/doc/draft-omar-ipv10/</a><br =
class=3D""><br class=3D""><br class=3D"">2) KHALED Routing Protocol =
(KRP): <br class=3D"">https://datatracker.ietf.org/doc/draft-omar-krp/<br =
class=3D""><br class=3D""><br class=3D"">3) Regional Routing Protocol =
(RRP): <br class=3D"">https://datatracker.ietf.org/doc/draft-omar-rrp/<br =
class=3D""><br class=3D""><br class=3D"">Please remove them all from the =
ietf database or repository.<br class=3D""><br class=3D"">If the ideas =
explained on these drafts will be used, discussed or <br =
class=3D"">published by the ietf, legal actions will be taken.<br =
class=3D""><br class=3D"">Regards,<br class=3D""><br class=3D"">Khaled =
Omar<br class=3D""><br class=3D""></blockquote><br =
class=3D""></blockquote><br class=3D"">----------<br class=3D"">Alexa =
Morris / Executive Director / IETF<br class=3D"">+1.510.492.4001<br =
class=3D"">Email: <a href=3D"mailto:amorris@amsl.com" =
class=3D"">amorris@amsl.com</a><br class=3D""><br class=3D""><br =
class=3D""><br class=3D""></blockquote><br class=3D"">----------<br =
class=3D"">Alexa Morris / Executive Director / IETF<br =
class=3D"">+1.510.492.4001<br class=3D"">Email: <a =
href=3D"mailto:amorris@amsl.com" class=3D"">amorris@amsl.com</a><br =
class=3D""><br class=3D""><br class=3D""><br =
class=3D""></div></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_DE52976D-E66A-41A2-8694-497D153939B1--


From nobody Tue Jun  6 11:13:11 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 93A76127BA3; Tue,  6 Jun 2017 11:12:56 -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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=vplGmdHt; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Za9v/Egn
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dJDNoppfk77b; Tue,  6 Jun 2017 11:12:53 -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 D6D4F1242F5; Tue,  6 Jun 2017 11:12:52 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id DD4F520821; Tue,  6 Jun 2017 14:12:51 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Tue, 06 Jun 2017 14:12:51 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :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=gx8qZYoKR+PMwo8CqWAogQbUUT4n/maXg2H+ImIx9 VI=; b=vplGmdHt+abCapLr1QDlpmOXkFH961rBRpf1muIu/Bxq9bk+nZzO62YuX mjW7hlC2FnhogS3HkqEV/ylen+WqSPty1QUCxHeulGGyJ4D5lTtFZNeMjzUMLCcl 3uD7L67RTB4UFNQZXz6G9dL+wD/YLKUbBSWcFKUlEb941ja3wXMdMMlmFNVc2tn3 QGSVxoj/0ctHADbw8jLpgWGYqbsbw9iYGyy9UK0aoenqmSrRnXS+f0yp7IAk3XbL panCH8xvGDGL9ZBJYk9YYoYEG3rf4QXz3cQWAf+ETkDi1oQif7UR6JAqcjzP5Q6h 3ixzCUrY3MMMAnzwDlWGSRK8oqmhw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=gx8qZYoKR+PMwo8CqW AogQbUUT4n/maXg2H+ImIx9VI=; b=Za9v/EgndVMKDcTBo+kh4uLAOuULVhEbxu 6JMYsby6OleNXd7OnUGxtuyPMA4sd4GKUdpS3y6DAGFlq0FHsk9PBBJwJ65lTTXU 63H+TM9f2ZkljnqUD5NyCdhsofZaL4Ta9avNTTqsG0BZWtz8ynnpgnBhA2FcT7Z0 kd8ro8Plcf2SQjQbn7WAknABdXumbRHpYV3auz+sEHu5vHSUeQaiuJ5pCEjaeRht m/LIX4peD8Hcx5U7I7k9fjRTSniP2Rb6N8yVfqe6pGZTELf6gWIqA8WdMvqLVKfT 6Q1eSIv3Pue2GAEKoCOaPhp1KOpLAU+sA2RxP+dODqoXo5gXE7xA==
X-ME-Sender: <xms:o_A2WX0_ahMtPfMfozKAUm_DycEHqTaIgsapABnVd9NbDz6RiJEl6Q>
X-Sasl-enc: cQ9Uq0c5zZYD+e2cdxlNqNCpUa/+HORSx/4U+gVTixSH 1496772771
Received: from dhcp-10-150-9-191.cisco.com (unknown [173.38.117.92]) by mail.messagingengine.com (Postfix) with ESMTPA id BE1397E7B1; Tue,  6 Jun 2017 14:12:50 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_534FDD10-75CE-4BB3-9794-DF6F12FD0D9D"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [Gen-art] Genart last call review of draft-ietf-bmwg-vswitch-opnfv-03
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CAFgnS4UAfMe5L7k=zwCqfUjgz14ArBpTE_bz675dCf0_Jk21fg@mail.gmail.com>
Date: Tue, 6 Jun 2017 14:12:50 -0400
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "bmwg@ietf.org" <bmwg@ietf.org>, Dan Romascanu <dromasca@gmail.com>
Message-Id: <21148194-B135-4FF6-9283-5459830671B0@cooperw.in>
References: <149450075072.16690.14546662616864459158@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CF25F9B072@njmtexg4.research.att.com> <CAFgnS4UAfMe5L7k=zwCqfUjgz14ArBpTE_bz675dCf0_Jk21fg@mail.gmail.com>
To: "MORTON, ALFRED C (AL)" <acmorton@att.com>, "draft-ietf-bmwg-vswitch-opnfv.all@ietf.org" <draft-ietf-bmwg-vswitch-opnfv.all@ietf.org>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Z9E8KG8JaiE_98NHzBot-9o4AuI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 18:12:57 -0000

--Apple-Mail=_534FDD10-75CE-4BB3-9794-DF6F12FD0D9D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Authors/shepherd/WG: any further responses to Dan?

Thanks,
Alissa


> On May 11, 2017, at 2:52 PM, Dan Romascanu <dromasca@gmail.com> wrote:
>=20
> Hi,=20
>=20
> Please see in-line.=20
>=20
> Regards,
>=20
> Dan
>=20
>=20
> On Thu, May 11, 2017 at 8:00 PM, MORTON, ALFRED C (AL) =
<acmorton@att.com <mailto:acmorton@att.com>> wrote:
> Hi Dan,
> please see replies, [ACM], below.
>=20
> > -----Original Message-----
> > From: Dan Romascanu [mailto:dromasca@gmail.com =
<mailto:dromasca@gmail.com>]
> > Sent: Thursday, May 11, 2017 7:06 AM
> > To: gen-art@ietf.org <mailto:gen-art@ietf.org>
> > Cc: draft-ietf-bmwg-vswitch-opnfv.all@ietf.org =
<mailto:draft-ietf-bmwg-vswitch-opnfv.all@ietf.org>; ietf@ietf.org =
<mailto:ietf@ietf.org>;
> > bmwg@ietf.org <mailto:bmwg@ietf.org>; dromasca@gmail.com =
<mailto: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=3Dhttps- =
<https://urldefense.proofpoint.com/v2/url?u=3Dhttps->
> > 3A__trac.ietf.org_trac_gen_wiki_GenArtfaq&d=3DDwICaQ&c=3DLFYZ-
> > o9_HUMeMTSQicvjIg&r=3DOfsSu8kTIltVyD1oL72cBw&m=3DNTVlLBN-
> > L3u9zGPHm_CNVcXW7_OGX8_18CtaAalZin0&s=3D2Hr-
> > dhKaDHIguY7W97z33RlKjqPDtmoYmM2-jWrbS-o&e=3D >.
> >
> > 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.
>=20
> >
> >
> > 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.
>=20
> > 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 =
<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).
>=20
> 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.
>=20
> This draft constitutes one of several follow-on efforts, approaching
> the problem exactly as we described in the last sentence above.
>=20
> How? What last sentence?=20
>=20
> Is it:=20
>=20
> '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.'
>=20
> 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?=20
>=20
> Will the WG write similar documents for all (or several) other =
organizations that implement VNFs one way or another? Should it?
>=20
>=20
> 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.
>=20
>=20
>=20
> >
> > 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 =
<https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-3.4>
>=20
> 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 =
<https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-3.3>
>=20
>=20
> > 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.
>=20
> > 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 =
<https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-4.2>
>=20
> 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.
>=20
> 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. =20
>=20
> > 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 =
<https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-4.1>
>=20
> 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.
>=20
>=20
> Measuring the same benchmarks is a good goal. I believe that the claim =
of repeatability needs to be better argued.=20
> =20
>=20
> >
> > 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.
>=20
> https://tools.ietf.org/html/rfc6413 =
<https://tools.ietf.org/html/rfc6413> examined Control Plane/Dataplane
> interactions, for example.
>=20
> https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-3.3 =
<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.
>=20
>=20
> Please provide references for each in text.=20
> =20
> Every network interface with an ASIC is an example of acceleration,
> one that we've characterized in physical network devices for years.
>=20
>=20
> 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?)
> =20
> > 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 =
<https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section-3.2>
>=20
> Section 4 summarizes the VSPERF Level Test Design document,
> of which these deployment scenarios are a key part.
>=20
> Yes, but this seams to belong to configurations of SUTs, even if they =
are called 'Deployment scenarios' in OPNFV-speak, and they impact =
repeatibility.=20
>  =20
>=20
> thanks for your comments; hopefully this detailed reply
> will reduce your reservations about publication.
>=20
> Al
> (for the co-authors)
>=20
> [0] =
https://www.opnfv.org/announcements/2014/09/30/telecom-industry-and-vendor=
s-unite-to-build-common-open-platform-to-accelerate-network-functions-virt=
ualization =
<https://www.opnfv.org/announcements/2014/09/30/telecom-industry-and-vendo=
rs-unite-to-build-common-open-platform-to-accelerate-network-functions-vir=
tualization>
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_534FDD10-75CE-4BB3-9794-DF6F12FD0D9D
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""><div class=3D"">Authors/shepherd/WG: any further responses to =
Dan?</div><div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D"">Alissa</div><div class=3D""><br =
class=3D""></div><br class=3D""><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On May 11, 2017, at 2:52 PM, Dan Romascanu =
&lt;<a href=3D"mailto:dromasca@gmail.com" =
class=3D"">dromasca@gmail.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D""><div class=3D""><div class=3D"">Hi, <br =
class=3D""><br class=3D""></div>Please see in-line. <br class=3D""><br =
class=3D""></div>Regards,<br class=3D""><br class=3D""></div>Dan<br =
class=3D""><br class=3D""><div class=3D""><div class=3D""><div =
class=3D""><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote">On Thu, May 11, 2017 at 8:00 PM, MORTON, ALFRED C =
(AL) <span dir=3D"ltr" class=3D"">&lt;<a href=3D"mailto:acmorton@att.com" =
target=3D"_blank" class=3D"">acmorton@att.com</a>&gt;</span> wrote:<br =
class=3D""><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 =
Dan,<br class=3D"">
please see replies, [ACM], below.<br class=3D"">
<span class=3D"gmail-"><br class=3D"">
&gt; -----Original Message-----<br class=3D"">
&gt; From: Dan Romascanu [mailto:<a href=3D"mailto:dromasca@gmail.com" =
class=3D"">dromasca@gmail.com</a>]<br class=3D"">
&gt; Sent: Thursday, May 11, 2017 7:06 AM<br class=3D"">
&gt; To: <a href=3D"mailto:gen-art@ietf.org" =
class=3D"">gen-art@ietf.org</a><br class=3D"">
&gt; Cc: <a href=3D"mailto:draft-ietf-bmwg-vswitch-opnfv.all@ietf.org" =
class=3D"">draft-ietf-bmwg-vswitch-opnfv.<wbr class=3D"">all@ietf.org</a>;=
 <a href=3D"mailto:ietf@ietf.org" class=3D"">ietf@ietf.org</a>;<br =
class=3D"">
&gt; <a href=3D"mailto:bmwg@ietf.org" class=3D"">bmwg@ietf.org</a>; <a =
href=3D"mailto:dromasca@gmail.com" class=3D"">dromasca@gmail.com</a><br =
class=3D"">
&gt; Subject: Genart last call review of =
draft-ietf-bmwg-vswitch-opnfv-<wbr class=3D"">03<br class=3D"">
&gt;<br class=3D"">
&gt; Reviewer: Dan Romascanu<br class=3D"">
&gt; Review result: Almost Ready<br class=3D"">
&gt;<br class=3D"">
&gt; I am the assigned Gen-ART reviewer for this draft. The General =
Area<br class=3D"">
&gt; Review Team (Gen-ART) reviews all IETF documents being processed<br =
class=3D"">
&gt; by the IESG for the IETF Chair.&nbsp; Please treat these comments =
just<br class=3D"">
&gt; like any other last call comments.<br class=3D"">
&gt;<br class=3D"">
&gt; For more information, please see the FAQ at<br class=3D"">
&gt;<br class=3D"">
</span>&gt; &lt;<a =
href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-" =
rel=3D"noreferrer" target=3D"_blank" class=3D"">https://urldefense.<wbr =
class=3D"">proofpoint.com/v2/url?u=3Dhttps-</a><br class=3D"">
&gt; 3A__trac.ietf.org_trac_gen_<wbr =
class=3D"">wiki_GenArtfaq&amp;d=3DDwICaQ&amp;c=3D<wbr class=3D"">LFYZ-<br =
class=3D"">
&gt; o9_HUMeMTSQicvjIg&amp;r=3D<wbr =
class=3D"">OfsSu8kTIltVyD1oL72cBw&amp;m=3D<wbr class=3D"">NTVlLBN-<br =
class=3D"">
&gt; L3u9zGPHm_CNVcXW7_OGX8_<wbr class=3D"">18CtaAalZin0&amp;s=3D2Hr-<br =
class=3D"">
&gt; dhKaDHIguY7W97z33RlKjqPDtmoYmM<wbr class=3D"">2-jWrbS-o&amp;e=3D =
&gt;.<br class=3D"">
&gt;<br class=3D"">
&gt; Document: draft-ietf-bmwg-vswitch-opnfv-<wbr class=3D"">03<br =
class=3D"">
<span class=3D"gmail-">&gt; Reviewer: Dan Romascanu<br class=3D"">
&gt; Review Date: 2017-05-11<br class=3D"">
&gt; IETF LC End Date: 2017-05-15<br class=3D"">
&gt; IESG Telechat date: Not scheduled for a telechat<br class=3D"">
&gt;<br class=3D"">
&gt; Summary:<br class=3D"">
&gt;<br class=3D"">
&gt; Almost Ready.<br class=3D"">
&gt;<br class=3D"">
&gt; This document describes describes the progress of the Open =
Platform<br class=3D"">
&gt; for NFV (OPNFV) project on virtual switch performance "VSPERF". =
That<br class=3D"">
&gt; project reuses the BMWG framework and specifications to =
benchmark<br class=3D"">
&gt; virtual switches implemented in general-purpose hardware. Some<br =
class=3D"">
&gt; differences with the benchmarking of specialized HW platforms =
are<br class=3D"">
&gt; identified and they may become work items for BMWG in the future. =
It's<br class=3D"">
&gt; a well written and clear document, but I have reservations about =
it<br class=3D"">
&gt; being published as an RFC, and I cannot find coverage for it in the =
WG<br class=3D"">
&gt; charter. I also have concerns that parts of the methodology used =
by<br class=3D"">
&gt; OPNFV break the BMWG principles, especially repeatability and<br =
class=3D"">
&gt; 'black-box', and this is not clear enough articulated in the =
document.<br class=3D"">
</span>[ACM]<br class=3D"">
Ok, let's address your specific issues, and come back to your =
reservations.<br class=3D"">
<span class=3D"gmail-"><br class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; Major issues:<br class=3D"">
&gt;<br class=3D"">
&gt; 1. It is not clear to me why this document needs to be published as =
an<br class=3D"">
&gt; RFC. The introduction says: 'This memo describes the progress of =
the<br class=3D"">
&gt; Open Platform for NFV (OPNFV) project on virtual switch =
performance<br class=3D"">
&gt; "VSPERF".&nbsp; This project intends to build on the current and =
completed<br class=3D"">
&gt; work of the Benchmarking Methodology Working Group in IETF, by<br =
class=3D"">
&gt; referencing existing literature.' Why should the WG and the IESG<br =
class=3D"">
&gt; invest resources in publishing this, why an I-D or an =
Independent<br class=3D"">
&gt; Stream RFC is not sufficient?<br class=3D"">
</span>[ACM]<br class=3D"">
The WG considered and discussed this document over 3 revisions<br =
class=3D"">
and a year of time before reaching consensus to develop it further<br =
class=3D"">
as a chartered item, so this decision was not taken lightly.<br =
class=3D"">
See more below.<br class=3D"">
<span class=3D"gmail-"><br class=3D"">
&gt; The WG charter says something about:<br class=3D"">
&gt; 'VNF and Related Infrastructure Benchmarking: Benchmarking<br =
class=3D"">
&gt; Methodologies have reliably characterized many physical devices. =
This<br class=3D"">
&gt; work item extends and enhances the methods to virtual network<br =
class=3D"">
&gt; functions (VNF) and their unique supporting infrastructure. A =
first<br class=3D"">
&gt; deliverable from this activity will be a document that considers =
the<br class=3D"">
&gt; new benchmarking space to ensure that common issues are =
recognized<br class=3D"">
&gt; from the start, using background materials from industry and =
SDOs<br class=3D"">
&gt; (e.g., IETF, ETSI NFV).'. I do not believe that this document =
covers<br class=3D"">
&gt; the intent of the charter, as it focused on one organization =
only.<br class=3D"">
</span>[ACM]<br class=3D"">
I'm sorry, but here you are mistaken. The document that satisfied<br =
class=3D"">
the "first deliverable ... document that considers the new benchmarking =
space"<br class=3D"">
is: <a href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05"=
 rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/<wbr =
class=3D"">draft-ietf-bmwg-virtual-net-05</a><br class=3D"">
titled: Considerations for Benchmarking Virtual Network Functions and =
Their Infrastructure<br class=3D"">
which has been submitted to IESG and approved for publication.<br =
class=3D"">
Further, the current draft (draft-ietf-bmwg-vswitch-<wbr =
class=3D"">opnfv-03)<br class=3D"">
references the approved "Considerations" draft in Section 3<br class=3D"">=

(as does almost every related Industry spec I'm aware of).<br class=3D"">
<br class=3D"">
The BMWG Charter continues:<br class=3D"">
&nbsp; Benchmarks for platform capacity and performance characteristics =
of<br class=3D"">
&nbsp; virtual routers, switches, and related components will follow, =
including<br class=3D"">
&nbsp; comparisons between physical and virtual network functions. In =
many cases,<br class=3D"">
&nbsp; the traditional benchmarks should be applicable to VNFs, but the =
lab<br class=3D"">
&nbsp; set-ups, configurations, and measurement methods will likely need =
to<br class=3D"">
&nbsp; be revised or enhanced.<br class=3D"">
<br class=3D"">
This draft constitutes one of several follow-on efforts, approaching<br =
class=3D"">
the problem exactly as we described in the last sentence above.<br =
class=3D""></blockquote><div class=3D""><br class=3D""></div><div =
class=3D"">How? What last sentence? <br class=3D""><br =
class=3D""></div><div class=3D"">Is it: <br class=3D""></div><div =
class=3D""><br class=3D"">'In many cases,<br class=3D"">
&nbsp; the traditional benchmarks should be applicable to VNFs, but the =
lab<br class=3D"">
&nbsp; set-ups, configurations, and measurement methods will likely need =
to<br class=3D"">
&nbsp; be revised or enhanced.'<br class=3D""><br class=3D""></div><div =
class=3D"">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? <br class=3D""><br =
class=3D""></div><div class=3D"">Will the WG write similar documents for =
all (or several) other organizations that implement VNFs one way or =
another? Should it?<br class=3D""></div><div class=3D""><br class=3D""> =
</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 class=3D"">
An aspect of Industry collaboration that we did not anticipate in the<br =
class=3D"">
BMWG Charter is our current interactions with Open Source =
Communities.<br class=3D"">
The current Charter was approved in June 2014, then OPNFV was founded<br =
class=3D"">
on September 30, 2014 [0] and the VSPERF Project was created on<br =
class=3D"">
Dec 16, 2014, so we did not anticipate extensive collaboration on<br =
class=3D"">
this and other benchmarking topics.<br class=3D"">
<span class=3D"gmail-"><br class=3D"">
<br class=3D"">
<br class=3D"">
&gt;<br class=3D"">
&gt; 2. In section 3 there 'repeatability' is mentioned, while<br =
class=3D"">
&gt; acknowledging that in a virtual environment there is no guarantee =
and<br class=3D"">
&gt; actually no way to know what other applications are being run.<br =
class=3D"">
</span>[ACM]<br class=3D"">
See:<br class=3D"">
<a =
href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section=
-3.4" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/<wbr =
class=3D"">draft-ietf-bmwg-virtual-net-<wbr =
class=3D"">05#section-3.4</a><br class=3D"">
<br class=3D"">
There are certainly ways to assess the current set of processes<br =
class=3D"">
at a particular time. The Software configuration parameters in<br =
class=3D"">
Section 3.3 are intended to capture this aspect as part of set-up.<br =
class=3D"">
At the same time, there will be challenges to assess the DUT<br =
class=3D"">
performance when resources are fully shared, and new testing<br =
class=3D"">
strategies will be needed:<br class=3D"">
<a =
href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section=
-3.3" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/<wbr =
class=3D"">draft-ietf-bmwg-virtual-net-<wbr =
class=3D"">05#section-3.3</a><br class=3D"">
<span class=3D"gmail-"><br class=3D"">
<br class=3D"">
&gt; Measuring parameters as the ones listed in 3.3 provides just part =
of<br class=3D"">
&gt; the answer, and they are internal parameters to the SUT.<br =
class=3D"">
</span>[ACM]<br class=3D"">
Yes, knowing the tested configuration is a critical pillar<br class=3D"">
supporting repeatability (these items are not measured, but =
configured),<br class=3D"">
and why we provided this section.<br class=3D"">
<span class=3D"gmail-"><br class=3D"">
&gt; Also, the<br class=3D"">
&gt; different deployment scenarios in section 4 require different<br =
class=3D"">
&gt; configurations for the SUT, thus breaking the 'black-box' =
principle.<br class=3D"">
</span>[ACM]<br class=3D"">
Specifying DUT configuration does not break any part of the<br class=3D"">=

black-box principle, which establishes that benchmark measurements<br =
class=3D"">
will be based on externally observable phenomena. See:<br class=3D"">
<a =
href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section=
-4.2" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/<wbr =
class=3D"">draft-ietf-bmwg-virtual-net-<wbr =
class=3D"">05#section-4.2</a><br class=3D"">
<br class=3D"">
Previous BMWG RFCs have identified the critical configuration<br =
class=3D"">
parameters of the DUT, such as the number and type of<br class=3D"">
network interfaces, the arrangement of DUTs in a SUT, etc.<br =
class=3D""></blockquote><div class=3D""><br class=3D""></div><div =
class=3D"">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.&nbsp; <br class=3D""></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 class=3D"gmail-"><br class=3D"">
&gt; I believe that there is a need for a more clear explanation of why =
BMWG<br class=3D"">
&gt; specifications are appropriate and how comparison can be made =
while<br class=3D"">
&gt; repeatability cannot be ensured, and measurements are dependent =
upon<br class=3D"">
&gt; parameters internal to the SUT.<br class=3D"">
</span>[ACM]<br class=3D"">
I believe that draft-ietf-bmwg-virtual-net-05 already<br class=3D"">
indicates why the existing BMWG RFCs are a reasonable<br class=3D"">
starting place for NFV benchmarks, in part because<br class=3D"">
we want to measure the same benchmarks of physical<br class=3D"">
network functions in many cases. See<br class=3D"">
<a =
href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section=
-4.1" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/<wbr =
class=3D"">draft-ietf-bmwg-virtual-net-<wbr =
class=3D"">05#section-4.1</a><br class=3D"">
<br class=3D"">
Repeatability is a goal of all experiments, and we understand<br =
class=3D"">
that there is more work to do in this regard, but what<br class=3D"">
we know now (documented in this draft) should<br class=3D"">
be a valuable contribution to the Industry.<br class=3D"">
<span class=3D"gmail-"><br class=3D""></span></blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">Measuring the same =
benchmarks is a good goal. I believe that the claim of repeatability =
needs to be better argued. <br class=3D"">&nbsp;<br =
class=3D""></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 class=3D"gmail-">
<br class=3D"">
&gt;<br class=3D"">
&gt; Minor issues:<br class=3D"">
&gt;<br class=3D"">
&gt; 1. Some of the tests mentioned in Section 4 have no prior or in<br =
class=3D"">
&gt; progress work in the IETF: Control Path and Datapath Coupling =
Tests,<br class=3D"">
&gt; Noisy Neighbour Tests, characterization of acceleration =
technologies.<br class=3D"">
</span>[ACM]<br class=3D"">
I'm sorry, but that's not an accurate portrayal of BMWG's literature.<br =
class=3D"">
<br class=3D"">
<a href=3D"https://tools.ietf.org/html/rfc6413" rel=3D"noreferrer" =
target=3D"_blank" class=3D"">https://tools.ietf.org/html/<wbr =
class=3D"">rfc6413</a> examined Control Plane/Dataplane<br class=3D"">
interactions, for example.<br class=3D"">
<br class=3D"">
<a =
href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section=
-3.3" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/<wbr =
class=3D"">draft-ietf-bmwg-virtual-net-<wbr =
class=3D"">05#section-3.3</a><br class=3D"">
item 2 specifically included Noisy Neighbour among the new<br class=3D"">
testing strategies.<br class=3D"">
<br class=3D""></blockquote><div class=3D""><br class=3D""></div><div =
class=3D"">Please provide references for each in text. <br =
class=3D"">&nbsp;<br class=3D""></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 =
class=3D"">
one that we've characterized in physical network devices for years.<br =
class=3D"">
<span class=3D"gmail-"><br class=3D""></span></blockquote><div =
class=3D""><br class=3D""></div><div class=3D"">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?)<br class=3D"">&nbsp;<br class=3D""></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 class=3D"gmail-">
&gt; If new work is needed / proposed to be added for the BMWG scope =
and<br class=3D"">
&gt; framework it would be useful for BMWG to list these separately.<br =
class=3D"">
&gt;<br class=3D"">
&gt;<br class=3D"">
&gt; Nits/editorial comments:<br class=3D"">
&gt;<br class=3D"">
&gt; 1. What is called 'Deployment scenarios' from VS perspective in<br =
class=3D"">
&gt; Section 4 describe in fact different configurations of the SUT in =
BMWG<br class=3D"">
&gt; terms. It seems better to separate this second part of section 4 in =
a<br class=3D"">
&gt; separate section. If it belongs to an existing section it rather<br =
class=3D"">
&gt; belongs in 3 than in 4.<br class=3D"">
&gt;<br class=3D"">
</span>[ACM]<br class=3D"">
Section 3 is more about extending the configuration guidance<br =
class=3D"">
from <a =
href=3D"https://tools.ietf.org/html/draft-ietf-bmwg-virtual-net-05#section=
-3.2" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://tools.ietf.org/html/<wbr =
class=3D"">draft-ietf-bmwg-virtual-net-<wbr =
class=3D"">05#section-3.2</a><br class=3D"">
<br class=3D"">
Section 4 summarizes the VSPERF Level Test Design document,<br class=3D"">=

of which these deployment scenarios are a key part.<br =
class=3D""></blockquote><div class=3D""><br class=3D""></div><div =
class=3D"">Yes, but this seams to belong to configurations of SUTs, even =
if they are called 'Deployment scenarios' in OPNFV-speak, and they =
impact repeatibility. <br class=3D"">&nbsp; <br =
class=3D""></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 class=3D"">
thanks for your comments; hopefully this detailed reply<br class=3D"">
will reduce your reservations about publication.<br class=3D"">
<br class=3D"">
Al<br class=3D"">
(for the co-authors)<br class=3D"">
<br class=3D"">
[0] <a =
href=3D"https://www.opnfv.org/announcements/2014/09/30/telecom-industry-an=
d-vendors-unite-to-build-common-open-platform-to-accelerate-network-functi=
ons-virtualization" rel=3D"noreferrer" target=3D"_blank" =
class=3D"">https://www.opnfv.org/<wbr =
class=3D"">announcements/2014/09/30/<wbr =
class=3D"">telecom-industry-and-vendors-<wbr =
class=3D"">unite-to-build-common-open-<wbr =
class=3D"">platform-to-accelerate-<wbr class=3D"">network-functions-<wbr =
class=3D"">virtualization</a><br class=3D"">
<br class=3D"">
</blockquote></div><br class=3D""></div></div></div></div></div>
_______________________________________________<br class=3D"">Gen-art =
mailing list<br class=3D""><a href=3D"mailto:Gen-art@ietf.org" =
class=3D"">Gen-art@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/gen-art<br =
class=3D""></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_534FDD10-75CE-4BB3-9794-DF6F12FD0D9D--


From nobody Tue Jun  6 12:36:18 2017
Return-Path: <leifj@mnt.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 12F74129536 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 12:36:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29VvMyWYMtHf for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 12:36:14 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E8CE7129411 for <ietf@ietf.org>; Tue,  6 Jun 2017 12:36:13 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id o83so42389235lff.3 for <ietf@ietf.org>; Tue, 06 Jun 2017 12:36:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=SL6Qn1KWVb3NZVuIFcxQGP78Bz2TDKTbBkKpYFqxPXg=; b=VkHnPDwuDaXoh3XehmWQyKUVdCYcSCOZ+YdQpzmcQPHb/26wTA+RfvltQNslbp+pjg MtVdSAg52mAoCTJwsMmwfV0nDyj2DeBHSeRU27YtJ/FTZsubJj6lJf8s9cXHsMijPLy3 XPmnyFpfEG01c0WcWmph70n+XWxv0TZ6CD/3+eJXoVc7u2BGBgrsyiUt3lXa7kqktn+F n6yS9WjeSFcOQcraUCcI7DGLfloTjfkU63a+7jElibsaZqQ77IBCnd7s7n6xZRhv4OON K0W38XpWiLYtP/MDMtqjjAf61y+lhnM4Eo00iE+GfXmRdRP0nsV914sCdXoCafRIQ43y nBJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=SL6Qn1KWVb3NZVuIFcxQGP78Bz2TDKTbBkKpYFqxPXg=; b=BJ4J6owJ8PBBKzYQM0eMa3pt33D/5QF1EuQM/3ZFUvPXDvd3N7QOzS/gFbEmoMr4l6 m3xpxq/2dSIDIXPjJjG6WSjqYxGkZOhvnQMTgDetXCPVteBEZPzIbW58h7in8+B4GtAy dTKt/bqWWT3zX3VPfKOiWmRVrDk8KuoqFsP6iZur7Gd0fFcSqJkqWoZX2++z2ia6V6j0 4mhsS9dIPX4B12qbKogmoEg4bUVho13CQIl6TGdZg75Z6eDixJQwmbA4hMOUCk905ZLo u08NbfVX6+uhTKqUvsIR6lhXehwRjh1aiVZXpDm3Uz9dGvkvPwViuYpZgu0NB6LvCwxW GEXQ==
X-Gm-Message-State: AODbwcA8MUAlB9dc6NYzKoTOZGGP/OcpiX72w0br9v8cIYDLE1HaUfT6 hJiaKMICHXLwRQhwOMSgIw==
X-Received: by 10.25.196.88 with SMTP id u85mr4400071lff.9.1496777771949; Tue, 06 Jun 2017 12:36:11 -0700 (PDT)
Received: from [10.0.0.129] (h-155-4-129-189.NA.cust.bahnhof.se. [155.4.129.189]) by smtp.gmail.com with ESMTPSA id 22sm1921453ljv.62.2017.06.06.12.36.10 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jun 2017 12:36:11 -0700 (PDT)
Subject: Re: wireless geolocation
To: ietf@ietf.org
References: <m27f0pqgbc.wl-randy@psg.com>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se>
Date: Tue, 6 Jun 2017 21:36:10 +0200
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: <m27f0pqgbc.wl-randy@psg.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/zS5NIIWws_OlLy2RqPgW9I-LYr8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 19:36:16 -0000

> oh, and warning.  there is a significant chance we will see the issue in
> praha as we have been unable to get a response from one major geoloc
> provider (not google; they were wonderfully responsive).
> 
> randy
> 

Just came back from TNC2017 - a significantly less sophisticated network
setup - that regularly runs into the same issue for the same reasons.

	Cheers Leif


From nobody Tue Jun  6 13:15:40 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 51FCB128854 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 13:15:39 -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 RLwFN4ydV_pp for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 13:15:38 -0700 (PDT)
Received: from mail-pg0-x241.google.com (mail-pg0-x241.google.com [IPv6:2607:f8b0:400e:c05::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 E6A0C12009C for <ietf@ietf.org>; Tue,  6 Jun 2017 13:15:37 -0700 (PDT)
Received: by mail-pg0-x241.google.com with SMTP id v14so10258262pgn.1 for <ietf@ietf.org>; Tue, 06 Jun 2017 13:15:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=JfYvMbBwNE2j94ly8TcX6FU1J4t8pApyjvD/x5PBqDQ=; b=o2liye3LOBSXCLsNvoGUAp1SWY9LfxnTu/9Gp5+oEOzelEntixRmmcGhZl9QO2wUV4 nP4el888cqVYGYe5KBptHSECWTVUi1Tr6sXHOFdTN3/dJ8NzT+Qp7bqdKJ5G3nNMC9bn nLhVHMT5h6cKnThcsj2df3eOwvLrJIHqWgbkMVdhP3NM0l6m+a+y+ZNo0daF6nn+JvL3 GMiGFY63xn4BWIFeS7drWDotzhVHKKgjgVukKqxrq+6iokkRdwzue1+3J1iR2mJLFZw5 /3IyeiHOvy685AwXlAutFJVv3X7YzpvCWhgdll/GTBCQMzvyvnkwnUFU93Lm6Ke0rWgC 3FHQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=JfYvMbBwNE2j94ly8TcX6FU1J4t8pApyjvD/x5PBqDQ=; b=GFFeAQ1V053Q9HZ84cMe5ORJTyAEDU9yjuZk0bfTTTIgUWPUfwh7OxcXC+QEjlAWV2 wmyzMkSpF5FPWU7DDZ5tCjNWhQHJRKF9xoZhFJdx5LHBCcPlH9fUqrCwOSbciZdb8AFy kEHpm9Z+ESgUjMuLECQXWyYlr2DV+J4B7OxpQUS2Kjn7GIy3gDdT6SdFSE2w8NScP2yD zk98YXu/yeFZaYMD7GJ0r6pmdmRaGXTQazG0IkcykezcTd0tz9D2W1be2qUJtFDGTGUV 9u1i4tyJ+sXgYq0o9KcuibXHa7YsQtyTyiKv54EeLTwPGpQlM6r3X+MBIbyZySNDkqS0 d4pw==
X-Gm-Message-State: AODbwcDD5YOSN2XHt4f6u95Tu67evCsGtkGnQRUHt+roITUqppjvqbtX N7sw9jC9Xi1omf59eg4=
X-Received: by 10.98.138.16 with SMTP id y16mr14338710pfd.131.1496780137324; Tue, 06 Jun 2017 13:15:37 -0700 (PDT)
Received: from ?IPv6:2406:e007:40bc:1:28cc:dc4c:9703:6781? ([2406:e007:40bc:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id u194sm59778894pgc.2.2017.06.06.13.15.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jun 2017 13:15:36 -0700 (PDT)
Subject: Re: wireless geolocation
To: Leif Johansson <leifj@mnt.se>, ietf@ietf.org
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com>
Date: Wed, 7 Jun 2017 08:15:37 +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: <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HRdPnn4hXPRqiI6DP4nQfK6T2JM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 20:15:39 -0000

On 07/06/2017 07:36, Leif Johansson wrote:
> 
>> oh, and warning.  there is a significant chance we will see the issue in
>> praha as we have been unable to get a response from one major geoloc
>> provider (not google; they were wonderfully responsive).
>>
>> randy
>>
> 
> Just came back from TNC2017 - a significantly less sophisticated network
> setup - that regularly runs into the same issue for the same reasons.

Does it matter?

Geolocation via topologically defined addresses is silly. Why do we
care about fixing it?

    Brian


From nobody Tue Jun  6 13:17:55 2017
Return-Path: <leifj@mnt.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 649C712943E for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 13:17:53 -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=mnt-se.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dWUw0HVvVUQj for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 13:17:52 -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 EA9FF1294CE for <ietf@ietf.org>; Tue,  6 Jun 2017 13:17:51 -0700 (PDT)
Received: by mail-wr0-x236.google.com with SMTP id v111so52382983wrc.3 for <ietf@ietf.org>; Tue, 06 Jun 2017 13:17:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=summiNJWuhodwHayh1D5WFSgTmGAC+McMfrcjBjiIFY=; b=buisDkr5boBP2EGwQsoRXzfpSFBdAQvddqqGkaGHE7sQT/o0PCaBID65PnWlOuRd3k ai4x6M4wGsQAYpSAxDZikETANsy3XpDASLXM9r4lkfS9wENJrx2k8u4clDO5qXO5JiTZ NvX/PjaMUDsIN2QIJtMKP/VAxRsnYtnLKDS1gfS23GzVpeHGyXOOZ4ZVikfzN2iLptlw QOu0YGR2od3nXhCJxp1k43rZWB8i3vdoRpF0N/2Ir8hmtDDipxyNvXZATGtPh7MR4eRP 1atJNeO6NlfLcogmksWeiFFhkoN3ooLbARkrT7UOZFnHNmbO3DIxoae/4lphrQm1Zf70 splw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=summiNJWuhodwHayh1D5WFSgTmGAC+McMfrcjBjiIFY=; b=QdF1iz0Fr687wr/QHl8Ty07qkT645vuaTvbIMQ7ENTiQGnfC3OFMsi3Sn1+sPSmFfU PfuNNoHWDlP9/lX/YlkaM18BRJjJAbxzIWC36TOVSCqnEeij5Cm5UoRjUV4AiuZxQ3JP Mb4gD066nENr444rOD4g6ICxGTfT3uUWOWOD6r/Mej7wH/137qeBcq/jCp9CYV6p2b9B 3KHnIggOH3kQC6WGEtEQdIXRFzeOT84uF159NeGq/JtXNm8/ceZOrtEyX6VItsk11aTW j0X/ds+nDE4zJE5l64BLmilV/L8a3M0Ltz5aBhDk5nPqr+7rn2GwTClF0qrDMCxoOrPG k5Sw==
X-Gm-Message-State: AODbwcBdz/yPKOQsLdKFY06FRGl759zm0499V1R+rHqDwo/ywU+CqN/R MDlQFNUi9RVUYeA9joFfTA==
X-Received: by 10.46.76.1 with SMTP id z1mr8307060lja.128.1496780270162; Tue, 06 Jun 2017 13:17:50 -0700 (PDT)
Received: from [10.0.0.129] (h-155-4-129-189.NA.cust.bahnhof.se. [155.4.129.189]) by smtp.gmail.com with ESMTPSA id i24sm537488ljb.63.2017.06.06.13.17.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jun 2017 13:17:49 -0700 (PDT)
Subject: Re: wireless geolocation
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf@ietf.org
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <469de3fc-a7c4-9d9f-9c36-a3cd69680e43@mnt.se>
Date: Tue, 6 Jun 2017 22:17:48 +0200
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: <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tuLvbG8JG1FVTivqoRatojnDkDc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 20:17:53 -0000

On 2017-06-06 22:15, Brian E Carpenter wrote:
> On 07/06/2017 07:36, Leif Johansson wrote:
>>
>>> oh, and warning.  there is a significant chance we will see the issue in
>>> praha as we have been unable to get a response from one major geoloc
>>> provider (not google; they were wonderfully responsive).
>>>
>>> randy
>>>
>>
>> Just came back from TNC2017 - a significantly less sophisticated network
>> setup - that regularly runs into the same issue for the same reasons.
> 
> Does it matter?

It is a source of irritation, certainly not more than that...

> 
> Geolocation via topologically defined addresses is silly. Why do we
> care about fixing it?

Because it is a widely deployed technology that gets used a lot?

> 
>     Brian
> 


From nobody Tue Jun  6 13:29:37 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 1730412953B for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 13:29:32 -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=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 c4cO900rEMMh for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 13:29:29 -0700 (PDT)
Received: from mail-ua0-x22a.google.com (mail-ua0-x22a.google.com [IPv6:2607:f8b0:400c:c08::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 82EFA1294E2 for <ietf@ietf.org>; Tue,  6 Jun 2017 13:29:26 -0700 (PDT)
Received: by mail-ua0-x22a.google.com with SMTP id q15so14408401uaa.2 for <ietf@ietf.org>; Tue, 06 Jun 2017 13:29:26 -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=ivK+tqRUc1yRwdFWJXrbWJKo4XldWDBk5aT2SmoLTgU=; b=MnB/DLARGBn4C50Ftj1NZ/U6CKoR+PzZijHSuj+Xi5lYArAiCojvdHYPHHjyeo4GTD hMTCCH+BS+IlBvhksPpaUqRU7lfmkLwgkZbvUFPK71voqht9QYzV31fvIo0/5fAiNRBZ qM4YVkVZj8nO0a1n2hOL8gTwjPrtwgY7y1CO0eDTNilSV2CF9+IbM28awnO1CbejgyKZ LSAUWul4Aa4/4VwPGhGiAEofft7xYIZeSU5ozsMvqJlZFx6A3S0YNAzxg6Yzb6Kty9eL GTzg8tx4t70IimLnNrH60Qr5A3yVp/OZMWm1JDIi8P0GunLFy/fR4mFF47QhUgZ7oToV bdlA==
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=ivK+tqRUc1yRwdFWJXrbWJKo4XldWDBk5aT2SmoLTgU=; b=bT70UTP/Z5v3xi6uGmvbiMs9c4fagExvTT02e91o8b2yMXzw28SZpwvvpDGBLqFDq1 WilYPSbmmJmvhYX7gltIvRvdBZgZJa+4BPlmbIReErRZ3z7sMccEzn/5HQmSzEVcuA1K 1TZUMTp2WN3a0zG77RMidmJZSO3MwpkTmvvPwWVA9wvajj4aqJNUw6SWmNzNOwoI9miX 8cjinkmteOuD1iabk/Y2yNU+ma4sdsKjjUwR9xfZK3lX1gTyMXWstLma2fUU3lS6Qys+ 5N35HSx5M7m7N+PbuWfK1hu5fD/EhdeaDNPKhwI2DayNaUncKaotGn2WpPAiEYQBUPC4 k7Og==
X-Gm-Message-State: AODbwcCRxJTW2J1fMTUe6w8GUBgjZD2h3yHFKgX+5ad7pFsu/e7M0m+M 7wdf0NUeXnISdhqFJS2Hwm+R4atdhZNf
X-Received: by 10.159.60.162 with SMTP id s34mr3715981uai.89.1496780965569; Tue, 06 Jun 2017 13:29:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.82.198 with HTTP; Tue, 6 Jun 2017 13:28:45 -0700 (PDT)
In-Reply-To: <CAFgnS4UAfMe5L7k=zwCqfUjgz14ArBpTE_bz675dCf0_Jk21fg@mail.gmail.com>
References: <149450075072.16690.14546662616864459158@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CF25F9B072@njmtexg4.research.att.com> <CAFgnS4UAfMe5L7k=zwCqfUjgz14ArBpTE_bz675dCf0_Jk21fg@mail.gmail.com>
From: Warren Kumari <warren@kumari.net>
Date: Tue, 6 Jun 2017 16:28:45 -0400
Message-ID: <CAHw9_iKZxmmYszcketrLwLQOq8wnVWZceLF=eXTudepODoBRHQ@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-bmwg-vswitch-opnfv-03
To: Dan Romascanu <dromasca@gmail.com>
Cc: "MORTON, ALFRED C (AL)" <acmorton@att.com>, "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: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mgWycgwK3lMP7s8GPyvv_WDsuJ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 20:29:32 -0000

On Thu, May 11, 2017 at 2:52 PM, Dan Romascanu <dromasca@gmail.com> wrote:
> 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?
>

Apologies for the delay, which is my almost entirely fault.

>From the Shepherds write-up:
"There has been a fair amount of work done on this draft, and progress
made on revisions, feedback, and comments. Several presentations have
been made in the room during IETF meetings, and followup and
discussion taken to the BMWG list. This draft is particularly useful,
given the popularity of VNF's within the industry."

I believe that there is value in the IETF publishing this as an
Informational document - the document provides useful information for
the Internet community (especially those folk benchmarking VNFs :-)).
The OPNFV virtual switch performance characterization work is very
closely related and relevant to the BMWG work, and I think that having
a collaboration type document (written fom the IETF viewpoint, and
informing IETF participants) is useful.
This *could* have been an Independent Stream doc, but it was discussed
and worked on in the WG, and so having it be a WG document feels much
more correct to me.

W

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



-- 
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 Tue Jun  6 13:50:35 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C6741200B9 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 13:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vt-L9w4nl6Fe for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 13:50:28 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E50812762F for <ietf@ietf.org>; Tue,  6 Jun 2017 13:50:28 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id a70so31304518pge.3 for <ietf@ietf.org>; Tue, 06 Jun 2017 13:50:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1T4YsgMlRv76swaAZ7T667TPDsRS8Zh/tUaSd/MBrzc=; b=onq0q4bLf1VxyFWTHZ7D/XFP+XtsGjxLth6be8GmWf6/zCeNzSN0+Xx+EA9G5ESstR TxtOt8W1ndY2hd2bR9S7PLPhpmihClAnvviSmpzCSuGz7dbHK1CYNWCOQ++2MRnj67ug DlVPCRFPNj9uo1ogh3qr5H5i0QISRhZnKpPYj2iJS2LKXc5zqOJCDfQX1SlTJ3rkOjj6 LjRM/+k5CJQXMFh8UxkZX0cwgP/Ab9uczo4O26sIbKDEOC3vFaZuOyMqvShcndJzQpv/ ehIJ+OtNq4InFhk02Z1NVBCIisMLjiJDljmfs9Xkt4LKFj7xAnhB3cr0kve50H8BkavB mp4A==
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=1T4YsgMlRv76swaAZ7T667TPDsRS8Zh/tUaSd/MBrzc=; b=HLSNkUJsgPuzqgSePHI6Y+IJNAVn2DjQpuVBoSNPirBXYMQCceagIbrckXrv6Ovjo4 OOwPzRiScg0NJh+eXqRgdZS26ISvivLbYyZTqjJw2pItIRaiQq00aH2lj6MRJ4FSB42O t2HRCh+LsdG4fuSJA5llCsVun+jCbkiAlCC0425Dk5rUsq1rii/Lov/X3WaIDqwwt8X4 rpjmJVCG8U03RdDIGnAp5ABvXeb7IPYhdPNazxZcrcjYip1UDl+T7NzEoP+hK339KHm4 z9ciGdA9887pV3sJ+AYNUhujZdIbgUaZprsBapZ981BqJsKzKknaJOYBdhroiXFL/nhj GAqg==
X-Gm-Message-State: AODbwcC6m7Layy65KJ1lRGufyULGDwCEm/HiH3VwcqqgcpX3gJYxU4+C jFTy5AE0p9AG/a/cEVS2BZcm7UVx302l
X-Received: by 10.84.195.129 with SMTP id j1mr23937591pld.122.1496782227810; Tue, 06 Jun 2017 13:50:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.178.2 with HTTP; Tue, 6 Jun 2017 13:50:27 -0700 (PDT)
Received: by 10.100.178.2 with HTTP; Tue, 6 Jun 2017 13:50:27 -0700 (PDT)
In-Reply-To: <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Tue, 6 Jun 2017 16:50:27 -0400
Message-ID: <CAPt1N1ni9Z12gfNArK4GaJpXdp2OMoZXv_wKrHYCcCG2wom=tw@mail.gmail.com>
Subject: Re: wireless geolocation
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: ietf <ietf@ietf.org>, Leif Johansson <leifj@mnt.se>
Content-Type: multipart/alternative; boundary="94eb2c0ef362fec3fb055150c405"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/U-maLfM9iA7eXmzVyzyhI8d58R4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 20:50:32 -0000

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

Because it makes it very difficult to use various services if they think we
are 7000 miles away from where we are. Latency can be bad, and using maps
can be impossible. I don't love the fact that the internet works this way,
but since it does, if we don't account for that, ux is significantly
degraded.

On Jun 6, 2017 4:15 PM, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
wrote:

> On 07/06/2017 07:36, Leif Johansson wrote:
> >
> >> oh, and warning.  there is a significant chance we will see the issue in
> >> praha as we have been unable to get a response from one major geoloc
> >> provider (not google; they were wonderfully responsive).
> >>
> >> randy
> >>
> >
> > Just came back from TNC2017 - a significantly less sophisticated network
> > setup - that regularly runs into the same issue for the same reasons.
>
> Does it matter?
>
> Geolocation via topologically defined addresses is silly. Why do we
> care about fixing it?
>
>     Brian
>
>

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

<div dir=3D"auto">Because it makes it very difficult to use various service=
s if they think we are 7000 miles away from where we are. Latency can be ba=
d, and using maps can be impossible. I don&#39;t love the fact that the int=
ernet works this way, but since it does, if we don&#39;t account for that, =
ux is significantly degraded.=C2=A0</div><div class=3D"gmail_extra"><br><di=
v class=3D"gmail_quote">On Jun 6, 2017 4:15 PM, &quot;Brian E Carpenter&quo=
t; &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gma=
il.com</a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">On 07/06/2017 07:36, Leif Johansson wrote:<br>
&gt;<br>
&gt;&gt; oh, and warning.=C2=A0 there is a significant chance we will see t=
he issue in<br>
&gt;&gt; praha as we have been unable to get a response from one major geol=
oc<br>
&gt;&gt; provider (not google; they were wonderfully responsive).<br>
&gt;&gt;<br>
&gt;&gt; randy<br>
&gt;&gt;<br>
&gt;<br>
&gt; Just came back from TNC2017 - a significantly less sophisticated netwo=
rk<br>
&gt; setup - that regularly runs into the same issue for the same reasons.<=
br>
<br>
Does it matter?<br>
<br>
Geolocation via topologically defined addresses is silly. Why do we<br>
care about fixing it?<br>
<br>
=C2=A0 =C2=A0 Brian<br>
<br>
</blockquote></div></div>

--94eb2c0ef362fec3fb055150c405--


From nobody Tue Jun  6 13:51:17 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 B879012762F for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 13:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cYCKzjmn2L8t for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 13:51:15 -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 E35931200B9 for <ietf@ietf.org>; Tue,  6 Jun 2017 13:51:14 -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 1dILRY-00043Q-Ua; Tue, 06 Jun 2017 20:51:13 +0000
Date: Wed, 07 Jun 2017 02:51:10 +0600
Message-ID: <m21sqwrgap.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ted Lemon <mellon@fugue.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
In-Reply-To: <50E30AF8-6D05-4698-AC71-70A0179F703E@fugue.com>
References: <m27f0pqgbc.wl-randy@psg.com> <50E30AF8-6D05-4698-AC71-70A0179F703E@fugue.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/n9t22iHBwoTEMCcfgn5gZBJWyhQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 20:51:16 -0000

> Why do we even have a stable IP address range anymore?

red herring.  reread my message.  they are geolocating by AP BSSID

randy


From nobody Tue Jun  6 14:30:07 2017
Return-Path: <prvs=2330dcf6e2=jonathan@vidyo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A0E7128BB6; Tue,  6 Jun 2017 14:29:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.101
X-Spam-Level: 
X-Spam-Status: No, score=-1.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-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 zZIKklfqlck1; Tue,  6 Jun 2017 14:29:51 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com [67.231.157.197]) (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 4C46F1286AB; Tue,  6 Jun 2017 14:29:51 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net [127.0.0.1]) by mx0b-00198e01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v56LOVoc021442; Tue, 6 Jun 2017 17:29:47 -0400
Received: from mail.vidyo.com (mail2.vidyo.com [162.209.16.214]) by mx0b-00198e01.pphosted.com with ESMTP id 2auqv5hw5d-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Tue, 06 Jun 2017 17:29:47 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Tue, 6 Jun 2017 16:29:46 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Roni Even <ron.even.tlv@gmail.com>
CC: General Area Review Team <gen-art@ietf.org>, "avtext@ietf.org" <avtext@ietf.org>, "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMA
Date: Tue, 6 Jun 2017 21:29:46 +0000
Message-ID: <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com>
In-Reply-To: <149629998360.19813.14889515687249184753@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5924C4BD17D7B24286A72B3867D63104@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-06_14:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706060372
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eVD-SITkfUj6aFfFXlSk3_Gmuec>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 21:29:53 -0000

SGksIFJvbmkg4oCUIHRoYW5rcyBmb3IgeW91ciByZXZpZXcuICBSZXNwb25zZXMgaW5saW5lLg0K
DQo+IE9uIEp1biAxLCAyMDE3LCBhdCAyOjUzIEFNLCBSb25pIEV2ZW4gPHJvbi5ldmVuLnRsdkBn
bWFpbC5jb20+IHdyb3RlOg0KPiANCj4gUmV2aWV3ZXI6IFJvbmkgRXZlbg0KPiBSZXZpZXcgcmVz
dWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KPiANCj4gSSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCBy
ZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVyYWwgQXJlYQ0KPiBSZXZpZXcgVGVhbSAo
R2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkDQo+IGJ5
IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4gIFBsZWFzZSB0cmVhdCB0aGVzZSBjb21tZW50
cyBqdXN0DQo+IGxpa2UgYW55IG90aGVyIGxhc3QgY2FsbCBjb21tZW50cy4NCj4gDQo+IEZvciBt
b3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4gDQo+IDxodHRwczovL3Ry
YWMuaWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KPiANCj4gRG9jdW1lbnQ6IGRy
YWZ0LWlldGYtYXZ0ZXh0LWxyci0/Pw0KPiBSZXZpZXdlcjogUm9uaSBFdmVuDQo+IFJldmlldyBE
YXRlOiAyMDE3LTA1LTMxDQo+IElFVEYgTEMgRW5kIERhdGU6IDIwMTctMDYtMDgNCj4gSUVTRyBU
ZWxlY2hhdCBkYXRlOiBOb3Qgc2NoZWR1bGVkIGZvciBhIHRlbGVjaGF0DQo+IA0KPiBTdW1tYXJ5
Og0KPiBUaGUgZG9jdW1lbnQgaXMgcmVhZHkgd2l0aCBpc3N1ZXMgZm9yIGEgc3RhbmRhcmQgdHJh
Y2sgUkZDDQo+IE1ham9yIGlzc3VlczoNCj4gDQo+IE1pbm9yIGlzc3VlczoNCj4gDQo+IDEuIENh
biB5b3Ugc3BlY2lmeSBib3RoIFRUSUQgYW5kIFRMSUQgaW4gdGhlIHNhbWUgRkNJLg0KDQpTeW50
YWN0aWNhbGx5LCB0aGV5IG11c3QgYm90aCBvY2N1ci4NCg0KSWYgeW91IG1lYW4gY2FuIHlvdSBy
ZXF1ZXN0IGFuIHVwZ3JhZGUgaW4gYm90aCBhdCBvbmNlLCB5ZXM7IEnigJl2ZSBhZGRlZCB0ZXh0
IHRvIGNsYXJpZnkgdGhpcy4NCg0KPiAyLiBXaGF0IGlzIHRoZSBtZWFuaW5nIG9mIHZhbHVlIDAg
Zm9yIFRUSUQgYW5kIFRMSUQgLSBUSUQgb3IgTElEID0wIGluDQo+IGZyYW1lIG1hcmtpbmcgZHJh
ZnQgbWVhbnMgYmFzZSBsYXllciBpZiB0aGVyZSBpcyBzY2FsYWJpbGl0eS4NCj4gICAgIFRoaXMg
cmVsYXRlcyB0byB0aGUgcHJldmlvdXMgcXVlc3Rpb24uIA0KDQpJ4oCZbSBub3Qgc3VyZSBJIHVu
ZGVyc3RhbmQgdGhpcyBxdWVzdGlvbi4NCg0KSeKAmXZlIGFkZGVkIHRleHQgdGhhdCBpZiBDPTEs
IGF0IGxlYXN0IG9uZSBvZiA8VFRJRCwgVExJRD4gTVVTVCBiZSBncmVhdGVyIHRoYW4gPENUSUQs
IENMSUQ+LCBhbmQgYm90aCBNVVNUIGJlIGdyZWF0ZXIgdGhhbiBvciBlcXVhbCB0byB0aGVpciBj
b3VudGVycGFydCwgc28gdGhlIExSUiBpcyBhY3R1YWxseSByZXF1ZXN0aW5nIGEgbGF5ZXIgdXBn
cmFkZS4gIElzIHRoYXQgd2hhdCB5b3Ugd2VyZSBhc2tpbmcgYWJvdXQ/DQoNCj4gMy4gIFdoYXQg
d291bGQgYW4gRkNJIHdpdGggYm90aCBUVElEIGFuZCBUTElEIGVxdWFsIDAgbWVhbi4NCg0KSXQg
bWVhbnMgeW91IHdhbnQgYSByZWZyZXNoIG9mIHRoZSBiYXNlIHRlbXBvcmFsL3NwYXRpYWwgbGF5
ZXIsIG9ubHkuDQoNCj4gTml0cy9lZGl0b3JpYWwgY29tbWVudHM6IA0KPiANCj4gMS4gU2VjdGlv
biAzICJhbiBSZWFsLVRpbWUgVHJhbnNwb3J0IENvbnRyb2wgUHJvdG9jb2wiIHNob3VsZCBiZSAi
YQ0KPiBSZWFs4oCmIi4NCg0KQ29saW4gcG9pbnRlZCBvdXQgdGhhdCBpdCBzaG91bGQgc2F5IOKA
nGFuIFJUUCBDb250cm9sIFByb3RvY29s4oCdIGFueXdheS4NCg0KPiAyLiBJbiBzZWN0aW9uIDMg
IiBbUkZDNTEwNF0oU2VjdGlvbiAzLjUuMSkiIHRoZXJlIGlzIGEgbGluayB0byBzZWN0aW9uDQo+
IDMuNS4xIGJ1dCBpdCBkb2VzIG5vdCB3b3JrLg0KDQp4bWwycmZjIGRvZXNu4oCZdCBoYXZlIGFu
eSB3YXkgdG8gbGluayB0byBzZWN0aW9ucyBvZiBvdGhlciBkb2N1bWVudHMsIHNvIHRoZSDigJwo
U2VjdGlvbiAzLjUuMSnigJ0gcGFydCBpcyBqdXN0IGEgY29tbWVudC4NCg0KSSB0aGluayB0aGUg
aW50ZXJuZXQtZHJhZnQgdG9vbGluZyBtYXkgaGF2ZSB0aG91Z2h0IEkgd2FzIHRyeWluZyB0byBs
aW5rIHRvIGEgbm9uLWV4aXN0ZW50IHNlY3Rpb24gMy41LjEgb2YgdGhpcyBkb2N1bWVudCwgYnV0
IHRoYXTigJlzIG91dHNpZGUgbXkgY29udHJvbC4NCg0KPiAzLiBJbiBzZWN0aW9uIDMuMiAiKHNl
ZSBzZWN0aW9uIFNlY3Rpb24gMi4xKSIgc2VjdGlvbiBhcHBlYXJzIHR3aWNlLg0KDQpGaXhlZC4=


From nobody Tue Jun  6 14:42:20 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 E5DE6128CD5 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 14:42:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aesBjM5QBzTb for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 14:42:18 -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 194571286AB for <ietf@ietf.org>; Tue,  6 Jun 2017 14:42:18 -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 1dIMEy-0004VG-BP; Tue, 06 Jun 2017 21:42:16 +0000
Date: Wed, 07 Jun 2017 03:42:14 +0600
Message-ID: <m2o9u0pzd5.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
In-Reply-To: <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@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/gl6aakM9v49zMuv1iGPZ2-z1HZs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 21:42:19 -0000

> Geolocation via topologically defined addresses is silly. Why do we
> care about fixing it?

i was not aware that bssid/macs were topologically assigned.  i thought
they were mfr based.  i guess slaac can be used to confuddle the two. :)

randy


From nobody Tue Jun  6 14:53:27 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 F397E129408 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 14:53:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Xwvi886_D4d for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 14:53: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 D18A81271FD for <ietf@ietf.org>; Tue,  6 Jun 2017 14:53: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 1dIMPi-0004j9-LM for ietf@ietf.org; Tue, 06 Jun 2017 21:53:23 +0000
Date: Wed, 07 Jun 2017 03:53:20 +0600
Message-ID: <m2k24opyun.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
In-Reply-To: <m27f0pqgbc.wl-randy@psg.com>
References: <m27f0pqgbc.wl-randy@psg.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/DrD5Xnu-Fja2sEAjJHmH99r0JYo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 21:53:25 -0000

fwiw, various folk who run intl wandering events have written to say
"yes, please."

randy


From nobody Tue Jun  6 15:38:19 2017
Return-Path: <d3e3e3@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 494DA126B71 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 15:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 K4Pgr9haK7F9 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 15:38:17 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001: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 E416A120454 for <ietf@ietf.org>; Tue,  6 Jun 2017 15:38:16 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id k93so420770ioi.2 for <ietf@ietf.org>; Tue, 06 Jun 2017 15:38:16 -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=ENEETcZkdhQy5bXYN+MYH9xyK37kZAIpC68NiiM7ZKo=; b=aHR8bL0xnlT7nA6CO5RTne3p4J6if34CMyUU21hkCCh9WYL83gZyp7RPSjmr6yJtUh mRIXc8YQTTShsbmmoCn2ty9VpHHBZ3sjy3anezwuHBX5JFqDaSAOPAg/o34wmwjdPkAp BcrUHIyrsgIP/3x5ZdCPKlso+PyMDdwvN/rHPufJUGz/jJ8FBcDOLPPLDZR4lFnxmiam qyzZlyRRhDpwIjXOZ3JOOx2zyNCLjDJiSVJKLTA/je/zwzgvdG1IUUh8eRW7ZEtqOFsf jqjtTtCrg1vpI1uDrCeLI446axO11dvYnwWbndBVDIr/qTXhwQOUiLxqJVhMnZYWgkXO bHRQ==
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=ENEETcZkdhQy5bXYN+MYH9xyK37kZAIpC68NiiM7ZKo=; b=HispDu00xTBGpJVPzzEwEYgBLgRYC2X1NHVsgUEvrMywTNwOI4HnRAhD3Fd9wilq27 p5EZpecqHqANgtRFNFOJeS0KGRw6vGeONmru+ZO3BYF3XfLP6VYFb8dzs6q+I7I6ENTd x+W4+N0F0oVtljgjz6ghnncAOS+iEQZ8GGM+eF4xb3Cw7eQSjl0Szm2LOpp+0hP/KPDJ m4ieLQxuMorzSIL8SfO3tqylTXQ8KTgjFONwnFESTgn21YdH2j8beR/8l+rHbNieqxzt PmnARpsWYWvHboxLY5QxlWQFdrTil6QouQwNq4WEf6rTV4xD3nMVNaaEoqYe/kmOZ/RS 41QA==
X-Gm-Message-State: AODbwcB/7dwG2u1LGhLSIBWFkqXljoLI0xUqxxq6tuQlmPmCaa+ZgRv/ EdkdOPqXXU63okxKD3dpFkUCyk0YkQ==
X-Received: by 10.107.52.19 with SMTP id b19mr17361550ioa.216.1496788696161; Tue, 06 Jun 2017 15:38:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.164.30 with HTTP; Tue, 6 Jun 2017 15:38:00 -0700 (PDT)
In-Reply-To: <m2o9u0pzd5.wl-randy@psg.com>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Tue, 6 Jun 2017 18:38:00 -0400
Message-ID: <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com>
Subject: Re: wireless geolocation
To: Randy Bush <randy@psg.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11440dce89e9ea055152463d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HSOhBholUlaREZJDW-4AQwsPgKc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 22:38:18 -0000

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

bssid/macs are manufacturer based but there are companies that provide
positioning services based on learning where those MACs are -- typically
combining such MAC based Wi-Fi/Bluetooth information with IP, GPS, ...
information to try to get an accurate location. If you happen to be in a
hotel function room and can only see meeting provided APs, so you can't see
any fixed local APs, you can easily get Geolocated to the previous meeting
site.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Tue, Jun 6, 2017 at 5:42 PM, Randy Bush <randy@psg.com> wrote:

> > Geolocation via topologically defined addresses is silly. Why do we
> > care about fixing it?
>
> i was not aware that bssid/macs were topologically assigned.  i thought
> they were mfr based.  i guess slaac can be used to confuddle the two. :)
>
> randy
>
>

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

<div dir=3D"ltr">bssid/macs are manufacturer based but there are companies =
that provide positioning services based on learning where those MACs are --=
 typically combining such MAC based Wi-Fi/Bluetooth information with IP, GP=
S, ... information to try to get an accurate location. If you happen to be =
in a hotel function room and can only see meeting provided APs, so you can&=
#39;t see any fixed local APs, you can easily get Geolocated to the previou=
s meeting site.<div class=3D"gmail_extra"><br clear=3D"all"><div><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature">Thanks,<br>Donald<b=
r>=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>=C2=A0Donald E. Eastlake 3rd =C2=A0 +1-508-333-227=
0 (cell)<br>=C2=A0155 Beaver Street, Milford, MA 01757 USA<br>=C2=A0<a href=
=3D"mailto:d3e3e3@gmail.com" target=3D"_blank">d3e3e3@gmail.com</a></div></=
div>
<br><div class=3D"gmail_quote">On Tue, Jun 6, 2017 at 5:42 PM, Randy Bush <=
span dir=3D"ltr">&lt;<a href=3D"mailto:randy@psg.com" target=3D"_blank">ran=
dy@psg.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"><span cl=
ass=3D"">&gt; Geolocation via topologically defined addresses is silly. Why=
 do we<br>
&gt; care about fixing it?<br>
<br>
</span>i was not aware that bssid/macs were topologically assigned.=C2=A0 i=
 thought<br>
they were mfr based.=C2=A0 i guess slaac can be used to confuddle the two. =
:)<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
randy<br>
<br>
</font></span></blockquote></div><br></div></div>

--001a11440dce89e9ea055152463d--


From nobody Tue Jun  6 16:15:54 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 81F5E126579 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 16:15: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 ivTLXVHEHCLr for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 16:15:51 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::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 5325C126557 for <ietf@ietf.org>; Tue,  6 Jun 2017 16:15:51 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id 9so102699419pfj.1 for <ietf@ietf.org>; Tue, 06 Jun 2017 16:15:51 -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=7M5J6LNSmn+kzFmwrJ7Urna43pn8+HB2o4feoqi8cwM=; b=WWXfVWrATQvVFWwkhGTYslCj8lz6dFwvhRX7VnceO8UVj379765dKlrBsTEz4p72/e jmrR9AtYqxdIRcuG5F1D4INrNVdMqoie+W59S4dejeFUhFjmo0bxy+E58TLPH6430ulT pY9IVMaF3NtGzN0AexUW8lO4Vz+SBSvIBQaPng5K5ONBsT458GDVogdCxNpq9EsaWmRD 0wiYqM8vTCWSmqKAF8CaC64U/YaVoV1xL1eyTN3CeNiu7ggCz47D4rkJzF+PnEo/0ZjW kYVMuC6/FotfXRebV7lvXCaud+uP/vOfJ3na5+0lx2+3S2RbKx8tvrPBqoFhbGbYY/HI JFXw==
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=7M5J6LNSmn+kzFmwrJ7Urna43pn8+HB2o4feoqi8cwM=; b=pXzFUHokxwx5QeiP70VVHmJd/uKED+urxDx/67nnGz+nY/lweHQhBemzZLCNqGn038 GJvg2Xxqp7Mut96G7FPyxH31AsGw9eUeFBaToHr49qlA18BcXz58clNFWwoNJT7yopU4 SzDqU2WFbXdhWCplZGLIy+mQF0VZPEv3wgP6BdvpB0vq651yw6xhTmGt8Y1IGHElVSt1 PBN/f9f1P8nLRtNxPWTaqJUWlSj7O4Yo4Qc2YcWIX7IHpCcyAs2b7tYMlm0A5OfbzL99 XRqN0qRITbzk9gsFX2sUmvkAxl8l0lA3+EbeFwkOZCsW7dFW4fM/dNze9A/+ccnk06rx 8A/g==
X-Gm-Message-State: AODbwcDPPGr+HWzDjDaYChI1HZhB5H/PlnyfnAVQRhI3cBdZj3pTl80K /k4ys+rBxDmpnAdH
X-Received: by 10.84.143.195 with SMTP id 61mr20139009plz.47.1496790950612; Tue, 06 Jun 2017 16:15:50 -0700 (PDT)
Received: from [130.216.38.7] (sc-cs-316051.cs.auckland.ac.nz. [130.216.38.7]) by smtp.gmail.com with ESMTPSA id a28sm27585835pfl.25.2017.06.06.16.15.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Jun 2017 16:15:50 -0700 (PDT)
Subject: Re: wireless geolocation
To: Randy Bush <randy@psg.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <71fff966-8767-fbfb-acb8-cede6a4f8a96@gmail.com>
Date: Wed, 7 Jun 2017 11:15:49 +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: <m2o9u0pzd5.wl-randy@psg.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/rZJnVvQc4ATIl1vD8_9AQ3tuTNY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 23:15:52 -0000

On 07/06/2017 09:42, Randy Bush wrote:
>> Geolocation via topologically defined addresses is silly. Why do we
>> care about fixing it?
> 
> i was not aware that bssid/macs were topologically assigned.  i thought
> they were mfr based.  i guess slaac can be used to confuddle the two. :)
 
A fair hit, but topologically- or physical device- based are
both broken solutions IMNSHO. I understand that the IETF NOC
has to deal with it pragmatically, but let's not imagine that
there's any real fix for intrinsic breakage.

   Brian


From nobody Tue Jun  6 16:31:12 2017
Return-Path: <tytso@thunk.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 41B7912704B for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 16:31:11 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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=thunk.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 44HJw6J973PP for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 16:31:09 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) (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 CED08126579 for <ietf@ietf.org>; Tue,  6 Jun 2017 16:31:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org;  s=ef5046eb;  h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=hu8amo1HzUntSF76tYP35Entj69AwMQCbCgM3kmiiN8=;  b=F3ITw64Pdh16bmtAt0951DYjIky7TgoIV6yPUGGFkChrn1S2iXAJZdrHJMIC3tDh2xjZEc+OtPsxL1Ap283r4gy0rTNSzb1HWZbAfX8GvQ4D9uMvnA+ddzct1a0XMOL1nfvKmeDFbVvAkRe29bBTOE/tP3X7RW6ECj04GoI35Qw=;
Received: from root (helo=callcc.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.84_2) (envelope-from <tytso@thunk.org>) id 1dINwJ-00055S-Cw; Tue, 06 Jun 2017 23:31:07 +0000
Received: by callcc.thunk.org (Postfix, from userid 15806) id D6059C00F21; Tue,  6 Jun 2017 19:31:06 -0400 (EDT)
Date: Tue, 6 Jun 2017 19:31:06 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
Message-ID: <20170606233106.yeyugzneqa4tjr44@thunk.org>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com>
User-Agent: NeoMutt/20170113 (1.7.2)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/z5jf2078cGr1pAUNiUhNMPTAesk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 23:31:11 -0000

On Tue, Jun 06, 2017 at 06:38:00PM -0400, Donald Eastlake wrote:
> bssid/macs are manufacturer based but there are companies that provide
> positioning services based on learning where those MACs are -- typically
> combining such MAC based Wi-Fi/Bluetooth information with IP, GPS, ...
> information to try to get an accurate location. If you happen to be in a
> hotel function room and can only see meeting provided APs, so you can't see
> any fixed local APs, you can easily get Geolocated to the previous meeting
> site.

What really surprises me is that it should be relatively easy for
these geolocation services to detect that BSSID/MAC's for the Access
Points belong to conference / rental services.  The pattern is pretty
obvious, even if the conference isn't kind enough to provide the
BSSID/MAC list to geolocation service.

The IETF AP's go active for a short-time, and then go dark, and when
they come back, they are obviously in a different location --- users
who geolocate to those AP's quickly shown to be in the "wrong" place,
in that when they get Cell Tower information, it conflicts with the
geolocation hint associated with the AP.  If they are rental AP's,
perhaps the only go dark for a day or two before they come up in a
different location, but the pattern of "these AP does not have a
stable geolocation" should be really easy to spot.  (At least, until
Star Trek style transporters or some other matter teleporter comes a
Thing.)

The service could keep them on a list of AP's where after they go dark
for say, 24 hours, when they come back on-line the system should try
to use location services based on cell tower, GPS, etc., to figure out
where they are on a real-time basis.  And if the system isn't able to
do that kind of automatical location deduction on a real-time basis,
it could simply blacklist those AP's for use as a geolocation hint.

This doesn't seem hard....

						- Ted


From nobody Tue Jun  6 16:44:19 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77F87128961 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 16:44:18 -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_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, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GP4JQKjLTjan for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 16:44:17 -0700 (PDT)
Received: from homiemail-a66.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 9E8CF120721 for <ietf@ietf.org>; Tue,  6 Jun 2017 16:44:17 -0700 (PDT)
Received: from homiemail-a66.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTP id 62AB2C002827; Tue,  6 Jun 2017 16:44:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=hEeJKu5UkqsQ7H KIAumOaIhzS00=; b=sMw8Vc6XHcFCqFLAaV7slmyXooWSfDGKHTs6WpcGZR7CHb narIVvYDLgpys96NsVWfUumdrtsITi8AqXo0Zgo5SH1w+ZQIyiECUBhgwmAi1kSD iccxbpJpA0ugvjgm9RPKr7GfgllDUFAQU6mttl6Fm4iA8HWNpB7zp/OJ3eNdA=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTPSA id 10658C002824; Tue,  6 Jun 2017 16:44:16 -0700 (PDT)
Date: Tue, 6 Jun 2017 18:44:14 -0500
From: Nico Williams <nico@cryptonector.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: Randy Bush <randy@psg.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
Message-ID: <20170606234413.GD3432@localhost>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t-9LSKQ6fHnoc9Q9zRDO5TCBhWw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 23:44:18 -0000

On Tue, Jun 06, 2017 at 06:38:00PM -0400, Donald Eastlake wrote:
> bssid/macs are manufacturer based but there are companies that provide
> positioning services based on learning where those MACs are -- typically
> combining such MAC based Wi-Fi/Bluetooth information with IP, GPS, ...
> information to try to get an accurate location. If you happen to be in a
> hotel function room and can only see meeting provided APs, so you can't see
> any fixed local APs, you can easily get Geolocated to the previous meeting
> site.

Can the BSSIDs be changed?  I know, that might be disruptive in that
users will have to re-teach their devices about trusted APs, but that
seems like a decent trade-off.


From nobody Tue Jun  6 16:53:00 2017
Return-Path: <clint.chaplin@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 6F931120721 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 16:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 5_SQChCKg05O for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 16:52:57 -0700 (PDT)
Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::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 9E93E126DED for <ietf@ietf.org>; Tue,  6 Jun 2017 16:52:56 -0700 (PDT)
Received: by mail-ua0-x234.google.com with SMTP id m31so7217386uam.1 for <ietf@ietf.org>; Tue, 06 Jun 2017 16:52: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=QkI4yin19QGw0Yub67r9eCfvX/ac17HsE3FcdPKorSs=; b=kStisjIdiO2e6m7KyQfC4kcYhpvLKij0nncaFkY6FqA+mvsJqh5ViS34ih66yMzTae 6IsvMhmsZGrucnZtL4V9vUvWR6UGEsCcvi+bQFhmpd7+QSzutD6oaS0mCf5vCxQcd2AT 1Ty6UvEm7iRopqmd/n+Y4yBiq+w74cn9wipwCuHzxIW2g7NhSbUmBA40AKgf8CXVtXRb Fwg1n9PFiqNdvBoAgjJGHYcfamp0X+O2h1Uc8AlCRpIZRmqXuZCrXvPPgo9LDVewEzXU M1HIInYKgTxVOuWvTbvPup3nkoXlOgxIEcCWAjemWmOhuwIcuNSItgebXYJNq931OlgP 4GtQ==
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=QkI4yin19QGw0Yub67r9eCfvX/ac17HsE3FcdPKorSs=; b=eV0VOhswCR/HBrcuF4K3XD8Tmjgdime1aQYbuXS+q2Oo0DJaj3Zrlk+F6Ns0F4hegu IJzPqivTTrLoOcDQcYRIaigCCP1Hu+0NAMgAPJhLah8R3oc9oID4S/SuBsLMblQd3KDz N5QvegfrPTQ+yHMlwmxGZo1VHiDqypstkkXyneFT2DCGADAOdQVHmOhzsgCpL+4z9wsB jKtW61mPmnyvEWVfq798f4fcHOEHJv7EffMIVd5CIZIOmRquXy1X0+Jep8v4sOwSOsOc FxJMCgk2kyC/RU8It9Z3To6GO5zhkHhd/qfMmbU5bOhNa/IYxeRnuxoB8CiJP5Z53OW0 HtPg==
X-Gm-Message-State: AODbwcDKUqnulG1/BNmPowyW8r150Mkzn7AQgkxQ1UlgVfGf02AD/ow3 urlmyDyDH+8Kcs7LhS0M4EN4WzA/hA==
X-Received: by 10.176.9.234 with SMTP id e42mr4022912uah.52.1496793175794; Tue, 06 Jun 2017 16:52:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.57.75 with HTTP; Tue, 6 Jun 2017 16:52:55 -0700 (PDT)
In-Reply-To: <20170606234413.GD3432@localhost>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost>
From: Clint Chaplin <clint.chaplin@gmail.com>
Date: Tue, 6 Jun 2017 16:52:55 -0700
Message-ID: <CADn-GtiLu4Fd3WDMYdP+N+LEJXixq-_iWJQ06BAe_WALsVQJrg@mail.gmail.com>
Subject: Re: wireless geolocation
To: Nico Williams <nico@cryptonector.com>
Cc: Donald Eastlake <d3e3e3@gmail.com>, IETF Rinse Repeat <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403043ee2148bad5005515351d5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/94ahQRG_yaCQBIU4R0j4nkKwjDA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 23:52:58 -0000

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

I guess they could be changed to Locally Administered.  Not sure the AP's
UI supports that.

On Tue, Jun 6, 2017 at 4:44 PM, Nico Williams <nico@cryptonector.com> wrote:

> On Tue, Jun 06, 2017 at 06:38:00PM -0400, Donald Eastlake wrote:
> > bssid/macs are manufacturer based but there are companies that provide
> > positioning services based on learning where those MACs are -- typically
> > combining such MAC based Wi-Fi/Bluetooth information with IP, GPS, ...
> > information to try to get an accurate location. If you happen to be in a
> > hotel function room and can only see meeting provided APs, so you can't
> see
> > any fixed local APs, you can easily get Geolocated to the previous
> meeting
> > site.
>
> Can the BSSIDs be changed?  I know, that might be disruptive in that
> users will have to re-teach their devices about trusted APs, but that
> seems like a decent trade-off.
>
>


-- 
Clint Chaplin
Principal Standards Engineer
Samsung Research America

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

<div dir=3D"ltr">I guess they could be changed to Locally Administered.=C2=
=A0 Not sure the AP&#39;s UI supports that.</div><div class=3D"gmail_extra"=
><br><div class=3D"gmail_quote">On Tue, Jun 6, 2017 at 4:44 PM, Nico Willia=
ms <span dir=3D"ltr">&lt;<a href=3D"mailto:nico@cryptonector.com" target=3D=
"_blank">nico@cryptonector.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"><span class=3D"">On Tue, Jun 06, 2017 at 06:38:00PM -0400, Do=
nald Eastlake wrote:<br>
</span><span class=3D"">&gt; bssid/macs are manufacturer based but there ar=
e companies that provide<br>
&gt; positioning services based on learning where those MACs are -- typical=
ly<br>
&gt; combining such MAC based Wi-Fi/Bluetooth information with IP, GPS, ...=
<br>
&gt; information to try to get an accurate location. If you happen to be in=
 a<br>
&gt; hotel function room and can only see meeting provided APs, so you can&=
#39;t see<br>
&gt; any fixed local APs, you can easily get Geolocated to the previous mee=
ting<br>
&gt; site.<br>
<br>
</span>Can the BSSIDs be changed?=C2=A0 I know, that might be disruptive in=
 that<br>
users will have to re-teach their devices about trusted APs, but that<br>
seems like a decent trade-off.<br>
<br>
</blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr"><d=
iv><div dir=3D"ltr"><div><div dir=3D"ltr"><div>Clint Chaplin<br>Principal S=
tandards Engineer<br>Samsung Research America</div></div></div></div></div>=
</div></div>
</div>

--f403043ee2148bad5005515351d5--


From nobody Tue Jun  6 16:56:44 2017
Return-Path: <ggm@algebras.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 C005E126DD9 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 16:56: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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.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 r9KZ-rsM25P3 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 16:56:40 -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 74491120721 for <ietf@ietf.org>; Tue,  6 Jun 2017 16:56:40 -0700 (PDT)
Received: by mail-ua0-x22d.google.com with SMTP id m31so7241064uam.1 for <ietf@ietf.org>; Tue, 06 Jun 2017 16:56:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=Jq6NYS/q/AxO0KAE8l4o7bPz/9QmheErxJPFLM2QVi8=; b=SB+ijSy7POqc9u0M0kZRZvtF+3cbt/TeCC1+colp6q6zrSQ/ScRy9YtAZgZVKm5DFj XqFHd4XUZV7WiaS8tejE6IoNzaN/os4uBiqjR+1fCO+Z9YBJmdDJmnxIVENDOPBlI/Ux hKXdG6Tw907R5XIlrQNIDN22zsMOEr2Sn5ldEqbatrJ/Vpe/i8bP7EWmVtQ113VpJkvo AhP3zheVc2zGhap9FUSHA0xUGmpVThQQEIsWeTJSR7LdTx8HtmEnjk1ZeH5zT57Q+oaJ UW0/o+dYVuA7cg93JBY14OoW1D0MOWdWtUiWBHHVB/2HvChwujYAx+5/A97ePO9sLOfU Tw4Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=Jq6NYS/q/AxO0KAE8l4o7bPz/9QmheErxJPFLM2QVi8=; b=A2nx0gZS4Eldl2PF18bLqZ1cHvXPHUkOQWZWkOX1FxFsw+FejO9xkCeUoCHzCjBYn6 Bt5uxpHsGXqrHTYRNh0Hb+zkZDV4MkxWDKFiqWb9fa0LoOrgarslcdkR7ouDjqNQv+Sr rXZnxND1Kp9VDVNGFsKMlpuLiJVmRCuiwIZlxdiIl+0s9hw3OhFcpcp5QLdpdt/TqVYC KwOpXxXONf6vmJbNhOnvXI/N2tdu54tcl7ex6xaF7uMYu8OJ+nIYNqIrkRHCNqtTXRNY 6IAmC2UMzaUdzn8LhTjU7M4SHD7nDZWjO94kbmkvEajWjpKMoKtme+RlrxzkyEPH2r5E 5SiQ==
X-Gm-Message-State: AODbwcCIWZixihCQyyndOZPfakVln6bXFkdxfvSgRoZP3evj0fREJcB0 unRHPT8EHepPVTgqGscQiDWUanVsFqueAEk=
X-Received: by 10.159.41.196 with SMTP id s62mr3112342uas.136.1496793399367; Tue, 06 Jun 2017 16:56:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.72.214 with HTTP; Tue, 6 Jun 2017 16:56:38 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:809a:c802:beae:b900]
In-Reply-To: <20170606234413.GD3432@localhost>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost>
From: George Michaelson <ggm@algebras.org>
Date: Wed, 7 Jun 2017 09:56:38 +1000
Message-ID: <CAKr6gn19_c=-SfmFY4+zqozXBoR2y6votkT0ubwh8-wtLGutGQ@mail.gmail.com>
Subject: Re: wireless geolocation
To: IETF Rinse Repeat <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IRNPBu0dul-tc5LHTzk2oY0M8Qc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 06 Jun 2017 23:56:43 -0000

I feel pretty odd about this. On the one hand, I think GeoLoc is
counter to <whimsy, belief, emotion> but I also recognize that it
happens, and a lot of things now depend on it. Stupid things like DRM
region lock, but also other things like optimal content source
selection, or language for an interface.

What do I want? I want less stupid. So I want either the DRM to die
(gonna happen. can I have a chocolate pony too?) or the Geo selection
method to work better.

But what my day job tells me, is that adding 'more' people to offer
ways to declare Geo, doesn't "fix" this problem. We, the RIR tried. We
didn't entirely help. Lots of reasons this turns out not to be
entirely useful. Some people say they don't want to believe what we
declare. They don't want to believe what Internet Address holders
self-declare. They only want to believe what they can measure,
triangulate, learn from <secret sauce> like BGP (oooooh! super
secret!!!) in ways which we don't understand. Or, from what websites
say. or DNS says. I know, lets put it in crypto, in the DNS...

And it also tells me that people have strong motivations to "mislead"
about their Geo, because of .. well.. basically the dynamics of the US
content industry and consumer choices. When it comes down to it if you
can demonstrate that a caribbean island resort hotel secured a
financial advantage having US located IP addresses and customer-choice
drove it up the price table (story I was told) then.. you know this is
a "thing" you can't control.

Really, I think if we stepped back, "geo information" is pretty
interesting. It feels like something we should have some ownership of.
But stepping forward, its been a tar pit, the entire time I've engaged
in it. Nobody can point me to a subject more likely to descend into
hell. Ok. maybe the DNS. And routing. or operations. I dunno. Its more
political than SNMP.

If something as simple as changing the BSSID stops the stupid, I'd say
add it to the playsheet. But it sucks this is likely to be workable,
and it sucks that something as silly as a Layer-2 device unique ID is
being tied to a location, for an agency which moves around the world.

Model be broken. Have no fix.

PS on a personal level I like more specifics in WHOIS, and
self-declared in the DNS and websites, I don't like super-secret sauce
methods, and I dont like people who re-publish public data as
privately tuned data, but are non-responsive on their 'fix problems'
email address. You know who you are...

On Wed, Jun 7, 2017 at 9:44 AM, Nico Williams <nico@cryptonector.com> wrote:
> On Tue, Jun 06, 2017 at 06:38:00PM -0400, Donald Eastlake wrote:
>> bssid/macs are manufacturer based but there are companies that provide
>> positioning services based on learning where those MACs are -- typically
>> combining such MAC based Wi-Fi/Bluetooth information with IP, GPS, ...
>> information to try to get an accurate location. If you happen to be in a
>> hotel function room and can only see meeting provided APs, so you can't see
>> any fixed local APs, you can easily get Geolocated to the previous meeting
>> site.
>
> Can the BSSIDs be changed?  I know, that might be disruptive in that
> users will have to re-teach their devices about trusted APs, but that
> seems like a decent trade-off.
>


From nobody Tue Jun  6 18:48:21 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 5DFAD129564; Tue,  6 Jun 2017 18:48:20 -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 TUnk6VoGK47r; Tue,  6 Jun 2017 18:48:16 -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 39458129576; Tue,  6 Jun 2017 18:48:16 -0700 (PDT)
Received: from pps.filterd (m0053301.ppops.net [127.0.0.1]) by mx0a-00191d01.pphosted.com (8.16.0.17/8.16.0.17) with SMTP id v571j541028010; Tue, 6 Jun 2017 21:48:11 -0400
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by mx0a-00191d01.pphosted.com with ESMTP id 2ax37e6t9x-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 06 Jun 2017 21:48:10 -0400
Received: from enaf.dadc.sbc.com (localhost [127.0.0.1]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id v571m9H9103516; Tue, 6 Jun 2017 20:48:09 -0500
Received: from dalint01.pst.cso.att.com (dalint01.pst.cso.att.com [135.31.133.159]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id v571m3Bx103503 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 6 Jun 2017 20:48:03 -0500
Received: from clpi183.sldc.sbc.com (clpi183.sldc.sbc.com [135.41.1.46]) by dalint01.pst.cso.att.com (RSA Interceptor); Wed, 7 Jun 2017 01:47:47 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 v571lliM017316; Tue, 6 Jun 2017 20:47:47 -0500
Received: from mail-green.research.att.com (mail-green.research.att.com [135.207.255.15]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id v571lhOR017126; Tue, 6 Jun 2017 20:47:43 -0500
Received: from exchange.research.att.com (njmtcas2.research.att.com [135.207.255.47]) by mail-green.research.att.com (Postfix) with ESMTP id 62EDEE1097; Tue,  6 Jun 2017 21:47:37 -0400 (EDT)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njmtcas2.research.att.com ([fe80::d550:ec84:f872:cad9%15]) with mapi id 14.03.0319.002; Tue, 6 Jun 2017 21:47:42 -0400
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Warren Kumari <warren@kumari.net>, "alissa@cooperw.in" <alissa@cooperw.in>
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>, "dromasca@gmail.com" <dromasca@gmail.com>
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+tr7bcWy3KHvK1EQgACSnQCAKPeQgP//5Opg
Date: Wed, 7 Jun 2017 01:47:41 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CF25FD64E2@njmtexg5.research.att.com>
References: <149450075072.16690.14546662616864459158@ietfa.amsl.com> <4D7F4AD313D3FC43A053B309F97543CF25F9B072@njmtexg4.research.att.com> <CAFgnS4UAfMe5L7k=zwCqfUjgz14ArBpTE_bz675dCf0_Jk21fg@mail.gmail.com> <CAHw9_iKZxmmYszcketrLwLQOq8wnVWZceLF=eXTudepODoBRHQ@mail.gmail.com>
In-Reply-To: <CAHw9_iKZxmmYszcketrLwLQOq8wnVWZceLF=eXTudepODoBRHQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [73.178.187.36]
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-06-06_15:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706070030
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E9NBTBt8cL2-rOIN1DQnsV7JEfo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 01:48:20 -0000

QWxpc3NhIGFuZCBXYXJyZW4sDQoNCkFmdGVyIFdhcnJlbidzIG1lc3NhZ2UsIGEgZmV3IG1vcmUg
cmVwbGllcyBpbi1saW5lLCBiZWxvdywNCg0KQWwgKGZvciB0aGUgY28tYXV0aG9ycykNCj4gLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogV2FycmVuIEt1bWFyaSBbbWFpbHRvOndh
cnJlbkBrdW1hcmkubmV0XQ0KPiBTZW50OiBUdWVzZGF5LCBKdW5lIDA2LCAyMDE3IDQ6MjkgUE0N
Cj4gVG86IERhbiBSb21hc2NhbnUNCj4gQ2M6IE1PUlRPTiwgQUxGUkVEIEMgKEFMKTsgZ2VuLWFy
dEBpZXRmLm9yZzsgZHJhZnQtaWV0Zi1ibXdnLXZzd2l0Y2gtDQo+IG9wbmZ2LmFsbEBpZXRmLm9y
ZzsgaWV0ZkBpZXRmLm9yZzsgYm13Z0BpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogR2VuYXJ0IGxh
c3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1ibXdnLXZzd2l0Y2gtb3BuZnYtMDMNCj4gDQo+
IE9uIFRodSwgTWF5IDExLCAyMDE3IGF0IDI6NTIgUE0sIERhbiBSb21hc2NhbnUgPGRyb21hc2Nh
QGdtYWlsLmNvbT4NCj4gd3JvdGU6DQo+ID4gSGksDQo+ID4NCj4gPiBQbGVhc2Ugc2VlIGluLWxp
bmUuDQo+ID4NCj4gPiBSZWdhcmRzLA0KPiA+DQo+ID4gRGFuDQo+ID4NCj4gPg0KPiA+IE9uIFRo
dSwgTWF5IDExLCAyMDE3IGF0IDg6MDAgUE0sIE1PUlRPTiwgQUxGUkVEIEMgKEFMKQ0KPiA8YWNt
b3J0b25AYXR0LmNvbT4NCj4gPiB3cm90ZToNCj4gPj4NCj4gPj4gSGkgRGFuLA0KPiA+PiBwbGVh
c2Ugc2VlIHJlcGxpZXMsIFtBQ01dLCBiZWxvdy4NCj4gPj4NCj4gPj4gPiAtLS0tLU9yaWdpbmFs
IE1lc3NhZ2UtLS0tLQ0KPiA+PiA+IEZyb206IERhbiBSb21hc2NhbnUgW21haWx0bzpkcm9tYXNj
YUBnbWFpbC5jb21dDQo+ID4+ID4gU2VudDogVGh1cnNkYXksIE1heSAxMSwgMjAxNyA3OjA2IEFN
DQo+ID4+ID4gVG86IGdlbi1hcnRAaWV0Zi5vcmcNCj4gPj4gPiBDYzogZHJhZnQtaWV0Zi1ibXdn
LXZzd2l0Y2gtb3BuZnYuYWxsQGlldGYub3JnOyBpZXRmQGlldGYub3JnOw0KPiA+PiA+IGJtd2dA
aWV0Zi5vcmc7IGRyb21hc2NhQGdtYWlsLmNvbQ0KPiA+PiA+IFN1YmplY3Q6IEdlbmFydCBsYXN0
IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYm13Zy12c3dpdGNoLW9wbmZ2LQ0KPiAwMw0KPiA+
PiA+DQo+ID4+ID4gUmV2aWV3ZXI6IERhbiBSb21hc2NhbnUNCj4gPj4gPiBSZXZpZXcgcmVzdWx0
OiBBbG1vc3QgUmVhZHkNCj4gPj4gPg0KPiA+PiA+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQg
cmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENCj4gPj4gPiBSZXZpZXcg
VGVhbSAoR2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2Vk
DQo+ID4+ID4gYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRo
ZXNlIGNvbW1lbnRzIGp1c3QNCj4gPj4gPiBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVu
dHMuDQo+ID4+ID4NCj4gPj4gPiBGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUg
RkFRIGF0DQo+ID4+ID4NCj4gPj4gPiA8aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29t
L3YyL3VybD91PWh0dHBzLT4+ID4NCj4gM0FfX3RyYWMuaWV0Zi5vcmdfdHJhY19nZW5fd2lraV9H
ZW5BcnRmYXEmZD1Ed0lDYVEmYz1MRllaLQ0KPiA+PiA+IG85X0hVTWVNVFNRaWN2aklnJnI9T2Zz
U3U4a1RJbHRWeUQxb0w3MmNCdyZtPU5UVmxMQk4tDQo+ID4+ID4gTDN1OXpHUEhtX0NOVmNYVzdf
T0dYOF8xOEN0YUFhbFppbjAmcz0ySHItDQo+ID4+ID4gZGhLYURISWd1WTdXOTd6MzNSbEtqcVBE
dG1vWW1NMi1qV3JiUy1vJmU9ID4uDQo+ID4+ID4NCj4gPj4gPiBEb2N1bWVudDogZHJhZnQtaWV0
Zi1ibXdnLXZzd2l0Y2gtb3BuZnYtMDMNCj4gPj4gPiBSZXZpZXdlcjogRGFuIFJvbWFzY2FudQ0K
PiA+PiA+IFJldmlldyBEYXRlOiAyMDE3LTA1LTExDQo+ID4+ID4gSUVURiBMQyBFbmQgRGF0ZTog
MjAxNy0wNS0xNQ0KPiA+PiA+IElFU0cgVGVsZWNoYXQgZGF0ZTogTm90IHNjaGVkdWxlZCBmb3Ig
YSB0ZWxlY2hhdA0KPiA+PiA+DQo+ID4+ID4gU3VtbWFyeToNCj4gPj4gPg0KPiA+PiA+IEFsbW9z
dCBSZWFkeS4NCj4gPj4gPg0KPiA+PiA+IFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzIGRlc2NyaWJl
cyB0aGUgcHJvZ3Jlc3Mgb2YgdGhlIE9wZW4gUGxhdGZvcm0NCj4gPj4gPiBmb3IgTkZWIChPUE5G
VikgcHJvamVjdCBvbiB2aXJ0dWFsIHN3aXRjaCBwZXJmb3JtYW5jZSAiVlNQRVJGIi4NCj4gVGhh
dA0KPiA+PiA+IHByb2plY3QgcmV1c2VzIHRoZSBCTVdHIGZyYW1ld29yayBhbmQgc3BlY2lmaWNh
dGlvbnMgdG8gYmVuY2htYXJrDQo+ID4+ID4gdmlydHVhbCBzd2l0Y2hlcyBpbXBsZW1lbnRlZCBp
biBnZW5lcmFsLXB1cnBvc2UgaGFyZHdhcmUuIFNvbWUNCj4gPj4gPiBkaWZmZXJlbmNlcyB3aXRo
IHRoZSBiZW5jaG1hcmtpbmcgb2Ygc3BlY2lhbGl6ZWQgSFcgcGxhdGZvcm1zIGFyZQ0KPiA+PiA+
IGlkZW50aWZpZWQgYW5kIHRoZXkgbWF5IGJlY29tZSB3b3JrIGl0ZW1zIGZvciBCTVdHIGluIHRo
ZSBmdXR1cmUuDQo+IEl0J3MNCj4gPj4gPiBhIHdlbGwgd3JpdHRlbiBhbmQgY2xlYXIgZG9jdW1l
bnQsIGJ1dCBJIGhhdmUgcmVzZXJ2YXRpb25zIGFib3V0IGl0DQo+ID4+ID4gYmVpbmcgcHVibGlz
aGVkIGFzIGFuIFJGQywgYW5kIEkgY2Fubm90IGZpbmQgY292ZXJhZ2UgZm9yIGl0IGluIHRoZQ0K
PiBXRw0KPiA+PiA+IGNoYXJ0ZXIuIEkgYWxzbyBoYXZlIGNvbmNlcm5zIHRoYXQgcGFydHMgb2Yg
dGhlIG1ldGhvZG9sb2d5IHVzZWQgYnkNCj4gPj4gPiBPUE5GViBicmVhayB0aGUgQk1XRyBwcmlu
Y2lwbGVzLCBlc3BlY2lhbGx5IHJlcGVhdGFiaWxpdHkgYW5kDQo+ID4+ID4gJ2JsYWNrLWJveCcs
IGFuZCB0aGlzIGlzIG5vdCBjbGVhciBlbm91Z2ggYXJ0aWN1bGF0ZWQgaW4gdGhlDQo+IGRvY3Vt
ZW50Lg0KPiA+PiBbQUNNXQ0KPiA+PiBPaywgbGV0J3MgYWRkcmVzcyB5b3VyIHNwZWNpZmljIGlz
c3VlcywgYW5kIGNvbWUgYmFjayB0byB5b3VyDQo+ID4+IHJlc2VydmF0aW9ucy4NCj4gPj4NCj4g
Pj4gPg0KPiA+PiA+DQo+ID4+ID4gTWFqb3IgaXNzdWVzOg0KPiA+PiA+DQo+ID4+ID4gMS4gSXQg
aXMgbm90IGNsZWFyIHRvIG1lIHdoeSB0aGlzIGRvY3VtZW50IG5lZWRzIHRvIGJlIHB1Ymxpc2hl
ZCBhcw0KPiBhbg0KPiA+PiA+IFJGQy4gVGhlIGludHJvZHVjdGlvbiBzYXlzOiAnVGhpcyBtZW1v
IGRlc2NyaWJlcyB0aGUgcHJvZ3Jlc3Mgb2YNCj4gdGhlDQo+ID4+ID4gT3BlbiBQbGF0Zm9ybSBm
b3IgTkZWIChPUE5GVikgcHJvamVjdCBvbiB2aXJ0dWFsIHN3aXRjaCBwZXJmb3JtYW5jZQ0KPiA+
PiA+ICJWU1BFUkYiLiAgVGhpcyBwcm9qZWN0IGludGVuZHMgdG8gYnVpbGQgb24gdGhlIGN1cnJl
bnQgYW5kDQo+IGNvbXBsZXRlZA0KPiA+PiA+IHdvcmsgb2YgdGhlIEJlbmNobWFya2luZyBNZXRo
b2RvbG9neSBXb3JraW5nIEdyb3VwIGluIElFVEYsIGJ5DQo+ID4+ID4gcmVmZXJlbmNpbmcgZXhp
c3RpbmcgbGl0ZXJhdHVyZS4nIFdoeSBzaG91bGQgdGhlIFdHIGFuZCB0aGUgSUVTRw0KPiA+PiA+
IGludmVzdCByZXNvdXJjZXMgaW4gcHVibGlzaGluZyB0aGlzLCB3aHkgYW4gSS1EIG9yIGFuIElu
ZGVwZW5kZW50DQo+ID4+ID4gU3RyZWFtIFJGQyBpcyBub3Qgc3VmZmljaWVudD8NCj4gPj4gW0FD
TV0NCj4gPj4gVGhlIFdHIGNvbnNpZGVyZWQgYW5kIGRpc2N1c3NlZCB0aGlzIGRvY3VtZW50IG92
ZXIgMyByZXZpc2lvbnMNCj4gPj4gYW5kIGEgeWVhciBvZiB0aW1lIGJlZm9yZSByZWFjaGluZyBj
b25zZW5zdXMgdG8gZGV2ZWxvcCBpdCBmdXJ0aGVyDQo+ID4+IGFzIGEgY2hhcnRlcmVkIGl0ZW0s
IHNvIHRoaXMgZGVjaXNpb24gd2FzIG5vdCB0YWtlbiBsaWdodGx5Lg0KPiA+PiBTZWUgbW9yZSBi
ZWxvdy4NCj4gPj4NCj4gPj4gPiBUaGUgV0cgY2hhcnRlciBzYXlzIHNvbWV0aGluZyBhYm91dDoN
Cj4gPj4gPiAnVk5GIGFuZCBSZWxhdGVkIEluZnJhc3RydWN0dXJlIEJlbmNobWFya2luZzogQmVu
Y2htYXJraW5nDQo+ID4+ID4gTWV0aG9kb2xvZ2llcyBoYXZlIHJlbGlhYmx5IGNoYXJhY3Rlcml6
ZWQgbWFueSBwaHlzaWNhbCBkZXZpY2VzLg0KPiBUaGlzDQo+ID4+ID4gd29yayBpdGVtIGV4dGVu
ZHMgYW5kIGVuaGFuY2VzIHRoZSBtZXRob2RzIHRvIHZpcnR1YWwgbmV0d29yaw0KPiA+PiA+IGZ1
bmN0aW9ucyAoVk5GKSBhbmQgdGhlaXIgdW5pcXVlIHN1cHBvcnRpbmcgaW5mcmFzdHJ1Y3R1cmUu
IEEgZmlyc3QNCj4gPj4gPiBkZWxpdmVyYWJsZSBmcm9tIHRoaXMgYWN0aXZpdHkgd2lsbCBiZSBh
IGRvY3VtZW50IHRoYXQgY29uc2lkZXJzDQo+IHRoZQ0KPiA+PiA+IG5ldyBiZW5jaG1hcmtpbmcg
c3BhY2UgdG8gZW5zdXJlIHRoYXQgY29tbW9uIGlzc3VlcyBhcmUgcmVjb2duaXplZA0KPiA+PiA+
IGZyb20gdGhlIHN0YXJ0LCB1c2luZyBiYWNrZ3JvdW5kIG1hdGVyaWFscyBmcm9tIGluZHVzdHJ5
IGFuZCBTRE9zDQo+ID4+ID4gKGUuZy4sIElFVEYsIEVUU0kgTkZWKS4nLiBJIGRvIG5vdCBiZWxp
ZXZlIHRoYXQgdGhpcyBkb2N1bWVudA0KPiBjb3ZlcnMNCj4gPj4gPiB0aGUgaW50ZW50IG9mIHRo
ZSBjaGFydGVyLCBhcyBpdCBmb2N1c2VkIG9uIG9uZSBvcmdhbml6YXRpb24gb25seS4NCj4gPj4g
W0FDTV0NCj4gPj4gSSdtIHNvcnJ5LCBidXQgaGVyZSB5b3UgYXJlIG1pc3Rha2VuLiBUaGUgZG9j
dW1lbnQgdGhhdCBzYXRpc2ZpZWQNCj4gPj4gdGhlICJmaXJzdCBkZWxpdmVyYWJsZSAuLi4gZG9j
dW1lbnQgdGhhdCBjb25zaWRlcnMgdGhlIG5ldw0KPiBiZW5jaG1hcmtpbmcNCj4gPj4gc3BhY2Ui
DQo+ID4+IGlzOiBodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0
cHMtDQo+IDNBX190b29scy5pZXRmLm9yZ19odG1sX2RyYWZ0LTJEaWV0Zi0yRGJtd2ctMkR2aXJ0
dWFsLTJEbmV0LQ0KPiAyRDA1JmQ9RHdJQmFRJmM9TEZZWi0NCj4gbzlfSFVNZU1UU1FpY3ZqSWcm
cj1PZnNTdThrVElsdFZ5RDFvTDcyY0J3Jm09aG9IV1h2NThheTNXZ0xjMTE1WFlycHJWbUY5DQo+
IDE0enBpaUdDQTZNUWtuYnMmcz1fbWdKT3JETEszM056X3M5T0E0bVNHY2JrWkFrUVNMalBOSjVx
RElFQXU0JmU9DQo+ID4+IHRpdGxlZDogQ29uc2lkZXJhdGlvbnMgZm9yIEJlbmNobWFya2luZyBW
aXJ0dWFsIE5ldHdvcmsgRnVuY3Rpb25zIGFuZA0KPiA+PiBUaGVpciBJbmZyYXN0cnVjdHVyZQ0K
PiA+PiB3aGljaCBoYXMgYmVlbiBzdWJtaXR0ZWQgdG8gSUVTRyBhbmQgYXBwcm92ZWQgZm9yIHB1
YmxpY2F0aW9uLg0KPiA+PiBGdXJ0aGVyLCB0aGUgY3VycmVudCBkcmFmdCAoZHJhZnQtaWV0Zi1i
bXdnLXZzd2l0Y2gtb3BuZnYtMDMpDQo+ID4+IHJlZmVyZW5jZXMgdGhlIGFwcHJvdmVkICJDb25z
aWRlcmF0aW9ucyIgZHJhZnQgaW4gU2VjdGlvbiAzDQo+ID4+IChhcyBkb2VzIGFsbW9zdCBldmVy
eSByZWxhdGVkIEluZHVzdHJ5IHNwZWMgSSdtIGF3YXJlIG9mKS4NCj4gPj4NCj4gPj4gVGhlIEJN
V0cgQ2hhcnRlciBjb250aW51ZXM6DQo+ID4+ICAgQmVuY2htYXJrcyBmb3IgcGxhdGZvcm0gY2Fw
YWNpdHkgYW5kIHBlcmZvcm1hbmNlIGNoYXJhY3RlcmlzdGljcyBvZg0KPiA+PiAgIHZpcnR1YWwg
cm91dGVycywgc3dpdGNoZXMsIGFuZCByZWxhdGVkIGNvbXBvbmVudHMgd2lsbCBmb2xsb3csDQo+
IGluY2x1ZGluZw0KPiA+PiAgIGNvbXBhcmlzb25zIGJldHdlZW4gcGh5c2ljYWwgYW5kIHZpcnR1
YWwgbmV0d29yayBmdW5jdGlvbnMuIEluIG1hbnkNCj4gPj4gY2FzZXMsDQo+ID4+ICAgdGhlIHRy
YWRpdGlvbmFsIGJlbmNobWFya3Mgc2hvdWxkIGJlIGFwcGxpY2FibGUgdG8gVk5GcywgYnV0IHRo
ZQ0KPiBsYWINCj4gPj4gICBzZXQtdXBzLCBjb25maWd1cmF0aW9ucywgYW5kIG1lYXN1cmVtZW50
IG1ldGhvZHMgd2lsbCBsaWtlbHkgbmVlZA0KPiB0bw0KPiA+PiAgIGJlIHJldmlzZWQgb3IgZW5o
YW5jZWQuDQo+ID4+DQo+ID4+IFRoaXMgZHJhZnQgY29uc3RpdHV0ZXMgb25lIG9mIHNldmVyYWwg
Zm9sbG93LW9uIGVmZm9ydHMsIGFwcHJvYWNoaW5nDQo+ID4+IHRoZSBwcm9ibGVtIGV4YWN0bHkg
YXMgd2UgZGVzY3JpYmVkIGluIHRoZSBsYXN0IHNlbnRlbmNlIGFib3ZlLg0KPiA+DQo+ID5bRGFu
IHdyb3RlXQ0KPiA+IEhvdz8gV2hhdCBsYXN0IHNlbnRlbmNlPw0KPiA+DQo+ID4gSXMgaXQ6DQo+
ID4NCj4gPiAnSW4gbWFueSBjYXNlcywNCj4gPiAgIHRoZSB0cmFkaXRpb25hbCBiZW5jaG1hcmtz
IHNob3VsZCBiZSBhcHBsaWNhYmxlIHRvIFZORnMsIGJ1dCB0aGUgbGFiDQo+ID4gICBzZXQtdXBz
LCBjb25maWd1cmF0aW9ucywgYW5kIG1lYXN1cmVtZW50IG1ldGhvZHMgd2lsbCBsaWtlbHkgbmVl
ZCB0bw0KPiA+ICAgYmUgcmV2aXNlZCBvciBlbmhhbmNlZC4nDQo+ID4NCltBQ01dIFllcw0KDQo+
ID4gSG93IGRvZXMgdGhpcyBkb2N1bWVudCBhcHByb2FjaCB0aGlzIHByb2JsZW0/IA0KW0FDTV0g
DQpMYWIgc2V0dXBzIChtZW50aW9uZWQgaW4gdGhlIHNlbnRlbmNlKSBhcmUgaWxsdXN0cmF0ZWQg
aW4gU2VjdGlvbiA0Lg0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtYm13
Zy12c3dpdGNoLW9wbmZ2LTAzI3BhZ2UtMTINCg0KQ29uZmlndXJhdGlvbiBwYXJhbWV0ZXJzICht
ZW50aW9uZWQgaW4gdGhlIHNlbnRlbmNlKSBhcmUgbGlzdGVkIGluIFNlY3Rpb24gMy4zDQpodHRw
czovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1ibXdnLXZzd2l0Y2gtb3BuZnYtMDMj
c2VjdGlvbi0zLjMNCg0KPiA+IElmIHRoZXJlIGlzIGEgbmVlZCB0byByZXZpc2UNCj4gPiBvciBl
bmhhbmNlIGV4aXN0aW5nIEJNV0cgd29yaywgd2hhdCBpcyBuZWVkZWQgaXMgc3BlY2lmaWMgcmV2
aXNpb25zIG9mDQo+ID4gZG9jdW1lbnRzLiBUaGlzIGluZm9ybWF0aW9uYWwgZG9jdW1lbnQgb25s
eSBkb2N1bWVudHMgd29yayBpbiBvbmUgZXh0ZXJuYWwNCj4gPiBvcmdhbml6YXRpb24uIEkgaGF2
ZSByZXNlcnZhdGlvbnMgdGhhdCB0aGlzIGlzIGEgV0cgdGFzayB0byBhZHZhbmNlIHRoaXMNCj4g
PiBkb2N1bWVudCwgYW5kIG9mIHRoZSBJRVNHIHRvIGFwcHJvdmUgaXQuIFdoeSBjYW4ndCBpdCBz
dGFuZCBhcyBhbiBJLUQgdW50aWwNCj4gPiB0aGUgV0cgZGVjaWRlcyB3aGF0ZXZlciB3b3JrIG5l
ZWRzIHRvIGJlIHVuZGVydGFrZW4gKGlmIGFueSkgdG8gbWVldCB0aGUNCj4gPiBPUE5GViBuZWVk
cz8gT3IgaWYgdGhleSB3aXRoIHRvIGhhdmUgYW4gUkZDLCB3aHkgY2FuJ3QgaXQgYmUgSW5kZXBl
bmRlbnQNCj4gPiBTdHJlYW0/DQo+ID4NCj4gPiBXaWxsIHRoZSBXRyB3cml0ZSBzaW1pbGFyIGRv
Y3VtZW50cyBmb3IgYWxsIChvciBzZXZlcmFsKSBvdGhlciBvcmdhbml6YXRpb25zDQo+ID4gdGhh
dCBpbXBsZW1lbnQgVk5GcyBvbmUgd2F5IG9yIGFub3RoZXI/IFNob3VsZCBpdD8NCj4gPg0KPiBb
V2FycmVuIHdyb3RlXQ0KPiBBcG9sb2dpZXMgZm9yIHRoZSBkZWxheSwgd2hpY2ggaXMgbXkgYWxt
b3N0IGVudGlyZWx5IGZhdWx0Lg0KPiANCj4gRnJvbSB0aGUgU2hlcGhlcmRzIHdyaXRlLXVwOg0K
PiAiVGhlcmUgaGFzIGJlZW4gYSBmYWlyIGFtb3VudCBvZiB3b3JrIGRvbmUgb24gdGhpcyBkcmFm
dCwgYW5kIHByb2dyZXNzDQo+IG1hZGUgb24gcmV2aXNpb25zLCBmZWVkYmFjaywgYW5kIGNvbW1l
bnRzLiBTZXZlcmFsIHByZXNlbnRhdGlvbnMgaGF2ZQ0KPiBiZWVuIG1hZGUgaW4gdGhlIHJvb20g
ZHVyaW5nIElFVEYgbWVldGluZ3MsIGFuZCBmb2xsb3d1cCBhbmQNCj4gZGlzY3Vzc2lvbiB0YWtl
biB0byB0aGUgQk1XRyBsaXN0LiBUaGlzIGRyYWZ0IGlzIHBhcnRpY3VsYXJseSB1c2VmdWwsDQo+
IGdpdmVuIHRoZSBwb3B1bGFyaXR5IG9mIFZORidzIHdpdGhpbiB0aGUgaW5kdXN0cnkuIg0KPiAN
Cj4gSSBiZWxpZXZlIHRoYXQgdGhlcmUgaXMgdmFsdWUgaW4gdGhlIElFVEYgcHVibGlzaGluZyB0
aGlzIGFzIGFuDQo+IEluZm9ybWF0aW9uYWwgZG9jdW1lbnQgLSB0aGUgZG9jdW1lbnQgcHJvdmlk
ZXMgdXNlZnVsIGluZm9ybWF0aW9uIGZvcg0KPiB0aGUgSW50ZXJuZXQgY29tbXVuaXR5IChlc3Bl
Y2lhbGx5IHRob3NlIGZvbGsgYmVuY2htYXJraW5nIFZORnMgOi0pKS4NCj4gVGhlIE9QTkZWIHZp
cnR1YWwgc3dpdGNoIHBlcmZvcm1hbmNlIGNoYXJhY3Rlcml6YXRpb24gd29yayBpcyB2ZXJ5DQo+
IGNsb3NlbHkgcmVsYXRlZCBhbmQgcmVsZXZhbnQgdG8gdGhlIEJNV0cgd29yaywgYW5kIEkgdGhp
bmsgdGhhdCBoYXZpbmcNCj4gYSBjb2xsYWJvcmF0aW9uIHR5cGUgZG9jdW1lbnQgKHdyaXR0ZW4g
Zm9tIHRoZSBJRVRGIHZpZXdwb2ludCwgYW5kDQo+IGluZm9ybWluZyBJRVRGIHBhcnRpY2lwYW50
cykgaXMgdXNlZnVsLg0KPiBUaGlzICpjb3VsZCogaGF2ZSBiZWVuIGFuIEluZGVwZW5kZW50IFN0
cmVhbSBkb2MsIGJ1dCBpdCB3YXMgZGlzY3Vzc2VkDQo+IGFuZCB3b3JrZWQgb24gaW4gdGhlIFdH
LCBhbmQgc28gaGF2aW5nIGl0IGJlIGEgV0cgZG9jdW1lbnQgZmVlbHMgbXVjaA0KPiBtb3JlIGNv
cnJlY3QgdG8gbWUuDQo+IA0KPiBXDQo+IA0KPiA+Pg0KPiA+PiBBbiBhc3BlY3Qgb2YgSW5kdXN0
cnkgY29sbGFib3JhdGlvbiB0aGF0IHdlIGRpZCBub3QgYW50aWNpcGF0ZSBpbiB0aGUNCj4gPj4g
Qk1XRyBDaGFydGVyIGlzIG91ciBjdXJyZW50IGludGVyYWN0aW9ucyB3aXRoIE9wZW4gU291cmNl
IENvbW11bml0aWVzLg0KPiA+PiBUaGUgY3VycmVudCBDaGFydGVyIHdhcyBhcHByb3ZlZCBpbiBK
dW5lIDIwMTQsIHRoZW4gT1BORlYgd2FzIGZvdW5kZWQNCj4gPj4gb24gU2VwdGVtYmVyIDMwLCAy
MDE0IFswXSBhbmQgdGhlIFZTUEVSRiBQcm9qZWN0IHdhcyBjcmVhdGVkIG9uDQo+ID4+IERlYyAx
NiwgMjAxNCwgc28gd2UgZGlkIG5vdCBhbnRpY2lwYXRlIGV4dGVuc2l2ZSBjb2xsYWJvcmF0aW9u
IG9uDQo+ID4+IHRoaXMgYW5kIG90aGVyIGJlbmNobWFya2luZyB0b3BpY3MuDQo+ID4+DQo+ID4+
DQo+ID4+DQo+ID4+ID5bRGFuIHdyb3RlXQ0KPiA+PiA+IDIuIEluIHNlY3Rpb24gMyB0aGVyZSAn
cmVwZWF0YWJpbGl0eScgaXMgbWVudGlvbmVkLCB3aGlsZQ0KPiA+PiA+IGFja25vd2xlZGdpbmcg
dGhhdCBpbiBhIHZpcnR1YWwgZW52aXJvbm1lbnQgdGhlcmUgaXMgbm8gZ3VhcmFudGVlIGFuZA0K
PiA+PiA+IGFjdHVhbGx5IG5vIHdheSB0byBrbm93IHdoYXQgb3RoZXIgYXBwbGljYXRpb25zIGFy
ZSBiZWluZyBydW4uDQo+ID4+IFtBQ01dDQo+ID4+IFNlZToNCj4gPj4gaHR0cHM6Ly91cmxkZWZl
bnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLQ0KPiAzQV9fdG9vbHMuaWV0Zi5vcmdf
aHRtbF9kcmFmdC0yRGlldGYtMkRibXdnLTJEdmlydHVhbC0yRG5ldC0yRDA1LQ0KPiAyM3NlY3Rp
b24tMkQzLjQmZD1Ed0lCYVEmYz1MRllaLQ0KPiBvOV9IVU1lTVRTUWljdmpJZyZyPU9mc1N1OGtU
SWx0VnlEMW9MNzJjQncmbT1ob0hXWHY1OGF5M1dnTGMxMTVYWXJwclZtRjkNCj4gMTR6cGlpR0NB
Nk1Ra25icyZzPXRLZ1lXcEpVMUpBMklnLVVyWEQ1Q2xVZFhYRDlXVVZzdnUzVWNXdjVDYXcmZT0N
Cj4gPj4NCj4gPj4gVGhlcmUgYXJlIGNlcnRhaW5seSB3YXlzIHRvIGFzc2VzcyB0aGUgY3VycmVu
dCBzZXQgb2YgcHJvY2Vzc2VzDQo+ID4+IGF0IGEgcGFydGljdWxhciB0aW1lLiBUaGUgU29mdHdh
cmUgY29uZmlndXJhdGlvbiBwYXJhbWV0ZXJzIGluDQo+ID4+IFNlY3Rpb24gMy4zIGFyZSBpbnRl
bmRlZCB0byBjYXB0dXJlIHRoaXMgYXNwZWN0IGFzIHBhcnQgb2Ygc2V0LXVwLg0KPiA+PiBBdCB0
aGUgc2FtZSB0aW1lLCB0aGVyZSB3aWxsIGJlIGNoYWxsZW5nZXMgdG8gYXNzZXNzIHRoZSBEVVQN
Cj4gPj4gcGVyZm9ybWFuY2Ugd2hlbiByZXNvdXJjZXMgYXJlIGZ1bGx5IHNoYXJlZCwgYW5kIG5l
dyB0ZXN0aW5nDQo+ID4+IHN0cmF0ZWdpZXMgd2lsbCBiZSBuZWVkZWQ6DQo+ID4+IGh0dHBzOi8v
dXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0NCj4gM0FfX3Rvb2xzLmll
dGYub3JnX2h0bWxfZHJhZnQtMkRpZXRmLTJEYm13Zy0yRHZpcnR1YWwtMkRuZXQtMkQwNS0NCj4g
MjNzZWN0aW9uLTJEMy4zJmQ9RHdJQmFRJmM9TEZZWi0NCj4gbzlfSFVNZU1UU1FpY3ZqSWcmcj1P
ZnNTdThrVElsdFZ5RDFvTDcyY0J3Jm09aG9IV1h2NThheTNXZ0xjMTE1WFlycHJWbUY5DQo+IDE0
enBpaUdDQTZNUWtuYnMmcz1lb3BXM3hlaWEybE5FRkpTQ0NsMlBiLS01YXpXZlJlVzVJN2tjaGt0
ZzNZJmU9DQo+ID4+DQo+ID4+IFtEYW4gd3JvdGVdDQo+ID4+ID4gTWVhc3VyaW5nIHBhcmFtZXRl
cnMgYXMgdGhlIG9uZXMgbGlzdGVkIGluIDMuMyBwcm92aWRlcyBqdXN0IHBhcnQgb2YNCj4gPj4g
PiB0aGUgYW5zd2VyLCBhbmQgdGhleSBhcmUgaW50ZXJuYWwgcGFyYW1ldGVycyB0byB0aGUgU1VU
Lg0KPiA+PiBbQUNNXQ0KPiA+PiBZZXMsIGtub3dpbmcgdGhlIHRlc3RlZCBjb25maWd1cmF0aW9u
IGlzIGEgY3JpdGljYWwgcGlsbGFyDQo+ID4+IHN1cHBvcnRpbmcgcmVwZWF0YWJpbGl0eSAodGhl
c2UgaXRlbXMgYXJlIG5vdCBtZWFzdXJlZCwgYnV0IGNvbmZpZ3VyZWQpLA0KPiA+PiBhbmQgd2h5
IHdlIHByb3ZpZGVkIHRoaXMgc2VjdGlvbi4NCj4gPj4gW0RhbiB3cm90ZV0NCj4gPj4gPiBBbHNv
LCB0aGUNCj4gPj4gPiBkaWZmZXJlbnQgZGVwbG95bWVudCBzY2VuYXJpb3MgaW4gc2VjdGlvbiA0
IHJlcXVpcmUgZGlmZmVyZW50DQo+ID4+ID4gY29uZmlndXJhdGlvbnMgZm9yIHRoZSBTVVQsIHRo
dXMgYnJlYWtpbmcgdGhlICdibGFjay1ib3gnIHByaW5jaXBsZS4NCj4gPj4gW0FDTV0NCj4gPj4g
U3BlY2lmeWluZyBEVVQgY29uZmlndXJhdGlvbiBkb2VzIG5vdCBicmVhayBhbnkgcGFydCBvZiB0
aGUNCj4gPj4gYmxhY2stYm94IHByaW5jaXBsZSwgd2hpY2ggZXN0YWJsaXNoZXMgdGhhdCBiZW5j
aG1hcmsgbWVhc3VyZW1lbnRzDQo+ID4+IHdpbGwgYmUgYmFzZWQgb24gZXh0ZXJuYWxseSBvYnNl
cnZhYmxlIHBoZW5vbWVuYS4gU2VlOg0KPiA+PiBodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2lu
dC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX3Rvb2xzLmlldGYub3JnX2h0bWxfZHJhZnQtMkRpZXRm
LTJEYm13Zy0yRHZpcnR1YWwtMkRuZXQtMkQwNS0yM3NlY3Rpb24tMkQ0LjImZD1Ed0lCYVEmYz1M
RllaLW85X0hVTWVNVFNRaWN2aklnJnI9T2ZzU3U4a1RJbHRWeUQxb0w3MmNCdyZtPWhvSFdYdjU4
YXkzV2dMYzExNVhZcnByVm1GOTE0enBpaUdDQTZNUWtuYnMmcz1RRmFJb3piT2VsSm5PaDIwNEdK
Q0xseEEyTVJMbkhseFFKTk83QlprY3FVJmU9DQo+ID4+DQo+ID4+IFByZXZpb3VzIEJNV0cgUkZD
cyBoYXZlIGlkZW50aWZpZWQgdGhlIGNyaXRpY2FsIGNvbmZpZ3VyYXRpb24NCj4gPj4gcGFyYW1l
dGVycyBvZiB0aGUgRFVULCBzdWNoIGFzIHRoZSBudW1iZXIgYW5kIHR5cGUgb2YNCj4gPj4gbmV0
d29yayBpbnRlcmZhY2VzLCB0aGUgYXJyYW5nZW1lbnQgb2YgRFVUcyBpbiBhIFNVVCwgZXRjLg0K
PiA+DQo+ID5bRGFuIHdyb3RlXQ0KPiA+IEkgbWF5IGhhdmUgbm90IGJlZW4gY2xlYXIgZW5vdWdo
LiBUaGUgZG9jdW1lbnQgdGFsa3MgYWJvdXQgcmVwZWF0YWJpbGl0eSBhbmQNCj4gPiBhYm91dCBj
b21wYXJpbmcgYmVuY2htYXJrcyB3aXRoIHRoZSBvbmVzIG9mIHNwZWNpYWxpemVkIEhXIGltcGxl
bWVudGF0aW9ucy4NCj4gPiBUaGVuIGl0IGdvZXMgaW50byBhIGxvbmcgYnV0IHN0aWxsIHBhcnRp
YWwgbGlzdCBvZiBmYWN0b3JzIHRoYXQgY2FuDQo+ID4gaW5mbHVlbmNlIHRoZSBiZW5jaG1hcmtp
bmcsIHRoZSBtYWpvcml0eSBvZiB0aGVtIGRlcGVuZCBvbiB0aGUgSFcgYW5kIFNXDQo+ID4gbWVh
c3VyZW1lbnRzIGFuZCBwYXJhbWV0ZXJzIG9mIHRoZSBpbnRlcm5hbCBzeXN0ZW1zLiBIb3cgY2Fu
IHRoaXMgYmUNCj4gPiBjb21wYXJlZCB3aXRoIGEgbnVtYmVyIG9mIHNtYWxsIGFuZCBpbmRlZWQg
ZXh0ZXJuYWxseSBvYnNlcnZhYmxlDQo+ID4gY29uZmlndXJhdGlvbiBwYXJhbWV0ZXJzIGxpa2Ug
dGhlIG51bWJlciBhbmQgdHlwZSBvZiBuZXR3b3JrIGludGVyZmFjZXMuDQo+ID4gVGhpcyBpcyBz
ZXZlcmFsIGRlZ3JlZXMgb2YgbWFnbml0dWRlIGFwYXJ0IGluIGNvbXBsZXhpdHkuDQo+ID4+DQpb
QUNNXSBUaGVzZSBhcmUgcHJlZG9taW5hbnRseSBjb25maWd1cmVkIHBhcmFtZXRlcnMgaW4gU2Vj
dGlvbiAzLjMuDQpGcmFua2x5LCBJIGRvbid0IHNlZSBhbnl0aGluZyBsaXN0ZWQgdGhhdCBpcyBt
ZWFzdXJlZC4NCg0KQk1XRyBoYXMgb2Z0ZW4gc3BlY2lmaWVkIGNvbmZpZ3VyYXRpb24gcGFyYW1l
dGVycyB0aGF0DQphcmUgbm90IGRpcmVjdGx5IG9ic2VydmFibGUsIHN1Y2ggYXMgdGhlIHJvdXRp
bmcgcHJvdG9jb2wgDQpjb25maWd1cmF0aW9uIHBhcmFtZXRlcnMgaW4gcGFydHMgb2YgDQpodHRw
czovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNjQxMyNzZWN0aW9uLTUNCmZvciBleGFtcGxlLg0K
DQpFdmVyeW9uZSBhY3R1YWxseSB3b3JraW5nIHRoaXMgcHJvYmxlbSBhcHByZWNpYXRlcyB0aGUg
ZGlmZmljdWx0eQ0KYW5kIGluY3JlYXNlIG9mIGFib3V0IDMgb3JkZXJzIG9mIG1hZ25pdHVkZSBp
biBjb25maWd1cmF0aW9uIA0KY29tcGxleGl0eS4gIE5ldmVydGhlbGVzcywgdGhpcyBpcyB0aGUg
cmVhbGl0eSBvZiBuZXR3b3JraW5nDQp3aXRoIGdlbmVyYWwgcHVycG9zZSBjb21wdXRlcnMsIGFu
ZCB3ZSBoYXZlIHRvIHNvbHZlIHRoaXMgcHJvYmxlbQ0KdG8gYmVuY2htYXJrIHRoZSBwZXJmb3Jt
YW5jZSBpbiBhIHNjaWVudGlmaWMgd2F5Lg0KDQo+ID4+IHtEYW4gd3JvdGVdDQo+ID4+ID4gSSBi
ZWxpZXZlIHRoYXQgdGhlcmUgaXMgYSBuZWVkIGZvciBhIG1vcmUgY2xlYXIgZXhwbGFuYXRpb24g
b2Ygd2h5IEJNV0cNCj4gPj4gPiBzcGVjaWZpY2F0aW9ucyBhcmUgYXBwcm9wcmlhdGUgYW5kIGhv
dyBjb21wYXJpc29uIGNhbiBiZSBtYWRlIHdoaWxlDQo+ID4+ID4gcmVwZWF0YWJpbGl0eSBjYW5u
b3QgYmUgZW5zdXJlZCwgYW5kIG1lYXN1cmVtZW50cyBhcmUgZGVwZW5kZW50IHVwb24NCj4gPj4g
PiBwYXJhbWV0ZXJzIGludGVybmFsIHRvIHRoZSBTVVQuDQo+ID4+IFtBQ01dDQo+ID4+IEkgYmVs
aWV2ZSB0aGF0IGRyYWZ0LWlldGYtYm13Zy12aXJ0dWFsLW5ldC0wNSBhbHJlYWR5DQo+ID4+IGlu
ZGljYXRlcyB3aHkgdGhlIGV4aXN0aW5nIEJNV0cgUkZDcyBhcmUgYSByZWFzb25hYmxlDQo+ID4+
IHN0YXJ0aW5nIHBsYWNlIGZvciBORlYgYmVuY2htYXJrcywgaW4gcGFydCBiZWNhdXNlDQo+ID4+
IHdlIHdhbnQgdG8gbWVhc3VyZSB0aGUgc2FtZSBiZW5jaG1hcmtzIG9mIHBoeXNpY2FsDQo+ID4+
IG5ldHdvcmsgZnVuY3Rpb25zIGluIG1hbnkgY2FzZXMuIFNlZQ0KPiA+PiBodHRwczovL3VybGRl
ZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtDQo+IDNBX190b29scy5pZXRmLm9y
Z19odG1sX2RyYWZ0LTJEaWV0Zi0yRGJtd2ctMkR2aXJ0dWFsLTJEbmV0LTJEMDUtDQo+IDIzc2Vj
dGlvbi0yRDQuMSZkPUR3SUJhUSZjPUxGWVotDQo+IG85X0hVTWVNVFNRaWN2aklnJnI9T2ZzU3U4
a1RJbHRWeUQxb0w3MmNCdyZtPWhvSFdYdjU4YXkzV2dMYzExNVhZcnByVm1GOQ0KPiAxNHpwaWlH
Q0E2TVFrbmJzJnM9dWlMSTBXaWxOSFJHeDRRbmlKX0E3SkZha2JGdXdhb2xXUVBMNl9jV09ZNCZl
PQ0KPiA+Pg0KPiA+PiBSZXBlYXRhYmlsaXR5IGlzIGEgZ29hbCBvZiBhbGwgZXhwZXJpbWVudHMs
IGFuZCB3ZSB1bmRlcnN0YW5kDQo+ID4+IHRoYXQgdGhlcmUgaXMgbW9yZSB3b3JrIHRvIGRvIGlu
IHRoaXMgcmVnYXJkLCBidXQgd2hhdA0KPiA+PiB3ZSBrbm93IG5vdyAoZG9jdW1lbnRlZCBpbiB0
aGlzIGRyYWZ0KSBzaG91bGQNCj4gPj4gYmUgYSB2YWx1YWJsZSBjb250cmlidXRpb24gdG8gdGhl
IEluZHVzdHJ5Lg0KPiA+Pg0KPiA+W0RhbiB3cm90ZV0NCj4gPiBNZWFzdXJpbmcgdGhlIHNhbWUg
YmVuY2htYXJrcyBpcyBhIGdvb2QgZ29hbC4gSSBiZWxpZXZlIHRoYXQgdGhlIGNsYWltIG9mDQo+
ID4gcmVwZWF0YWJpbGl0eSBuZWVkcyB0byBiZSBiZXR0ZXIgYXJndWVkLg0KPiA+DQpbQUNNXSAN
CkkgZGlzYWdyZWUsIHRoZSByZXBlYXRhYmlsaXR5IHByb2JsZW0gbmVlZHMgdG8gYmUgc29sdmVk
LCANCmFuZCBtYW55IG9mIHVzIGFyZSB3b3JraW5nIG9uIGl0Lg0KDQo+ID4+DQo+ID4+DQo+ID4+
ID4NCj4gPj4gPiBNaW5vciBpc3N1ZXM6DQo+ID4+ID4NCj4gPj4gPiAxLiBTb21lIG9mIHRoZSB0
ZXN0cyBtZW50aW9uZWQgaW4gU2VjdGlvbiA0IGhhdmUgbm8gcHJpb3Igb3IgaW4NCj4gPj4gPiBw
cm9ncmVzcyB3b3JrIGluIHRoZSBJRVRGOiBDb250cm9sIFBhdGggYW5kIERhdGFwYXRoIENvdXBs
aW5nDQo+IFRlc3RzLA0KPiA+PiA+IE5vaXN5IE5laWdoYm91ciBUZXN0cywgY2hhcmFjdGVyaXph
dGlvbiBvZiBhY2NlbGVyYXRpb24NCj4gdGVjaG5vbG9naWVzLg0KPiA+PiBbQUNNXQ0KPiA+PiBJ
J20gc29ycnksIGJ1dCB0aGF0J3Mgbm90IGFuIGFjY3VyYXRlIHBvcnRyYXlhbCBvZiBCTVdHJ3Mg
bGl0ZXJhdHVyZS4NCj4gPj4NCj4gPj4gaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29t
L3YyL3VybD91PWh0dHBzLQ0KPiAzQV9fdG9vbHMuaWV0Zi5vcmdfaHRtbF9yZmM2NDEzJmQ9RHdJ
QmFRJmM9TEZZWi0NCj4gbzlfSFVNZU1UU1FpY3ZqSWcmcj1PZnNTdThrVElsdFZ5RDFvTDcyY0J3
Jm09aG9IV1h2NThheTNXZ0xjMTE1WFlycHJWbUY5DQo+IDE0enBpaUdDQTZNUWtuYnMmcz1GZnd1
T3VZY0lGT3NKWFZySUgtcjRxMkp5T21MUDhXcXQ2X3NqR0RuUGU0JmU9DQo+IGV4YW1pbmVkIENv
bnRyb2wgUGxhbmUvRGF0YXBsYW5lDQo+ID4+IGludGVyYWN0aW9ucywgZm9yIGV4YW1wbGUuDQo+
ID4+DQo+ID4+IGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRw
cy0NCj4gM0FfX3Rvb2xzLmlldGYub3JnX2h0bWxfZHJhZnQtMkRpZXRmLTJEYm13Zy0yRHZpcnR1
YWwtMkRuZXQtMkQwNS0NCj4gMjNzZWN0aW9uLTJEMy4zJmQ9RHdJQmFRJmM9TEZZWi0NCj4gbzlf
SFVNZU1UU1FpY3ZqSWcmcj1PZnNTdThrVElsdFZ5RDFvTDcyY0J3Jm09aG9IV1h2NThheTNXZ0xj
MTE1WFlycHJWbUY5DQo+IDE0enBpaUdDQTZNUWtuYnMmcz1lb3BXM3hlaWEybE5FRkpTQ0NsMlBi
LS01YXpXZlJlVzVJN2tjaGt0ZzNZJmU9DQo+ID4+IGl0ZW0gMiBzcGVjaWZpY2FsbHkgaW5jbHVk
ZWQgTm9pc3kgTmVpZ2hib3VyIGFtb25nIHRoZSBuZXcNCj4gPj4gdGVzdGluZyBzdHJhdGVnaWVz
Lg0KPiA+Pg0KPiA+W0RhbiB3cm90ZV0NCj4gPiBQbGVhc2UgcHJvdmlkZSByZWZlcmVuY2VzIGZv
ciBlYWNoIGluIHRleHQuDQo+ID4NCltBQ01dIA0KSSdtIHNvcnJ5LCBidXQgdGhlc2UgcmVmZXJl
bmNlcyB3ZXJlIGZvciB5b3UsIGFuZCANCm9ubHkgdG8gcmVtaW5kIHlvdSBvZiBCTVdHJ3Mgc2Nv
cGUgb2Ygd29yay4NClRoZSBJR1AgYmVuY2htYXJraW5nIHJlZmVyZW5jZSBpcyBub3QgYXBwcm9w
cmlhdGUgaGVyZSwgYW5kIA0KdGhlIG90aGVyIEJNV0cgZHJhZnQgaGFzIGJlZW4gc3VmZmljaWVu
dGx5IHJlZmVyZW5jZWQgZWFybGllci4NCg0KPiA+Pg0KPiA+PiBFdmVyeSBuZXR3b3JrIGludGVy
ZmFjZSB3aXRoIGFuIEFTSUMgaXMgYW4gZXhhbXBsZSBvZiBhY2NlbGVyYXRpb24sDQo+ID4+IG9u
ZSB0aGF0IHdlJ3ZlIGNoYXJhY3Rlcml6ZWQgaW4gcGh5c2ljYWwgbmV0d29yayBkZXZpY2VzIGZv
ciB5ZWFycy4NCj4gPj4NCj4gPg0KPiA+IFllcywgYnV0IHdlIGRvIG5vdCBkZWFsIGhlcmUgd2l0
aCBleHRlcm5hbGx5IG9ic2VydmFibGUgaW50ZXJmYWNlcyBvbmx5LCBhbmQNCj4gPiBpZiB0aGUg
Y2hhcmFjdGVyaXphdGlvbiBvZiB0aGUgYWNjZWxlcmF0aW9uIHRlY2hub2xvZ2llcyBtYXR0ZXJz
IHRoYW4geW91DQo+ID4gbmVlZCBhIHdheSB0byBleHByZXNzIGl0ICh3aGVyZSBjYW4gd2UgZmlu
ZCBpdCBpbiBleGlzdGluZyBCTVdHIHdvcms/IG5ldw0KPiA+IHdvcms/KQ0KW0FDTV0gDQpJIHRo
aW5rIHlvdSBtaXN1bmRlcnN0b29kIG15IHJlcGx5LiBUaGUgYWNjZWxlcmF0aW9uIHRlY2hub2xv
Z2llcw0Kd2UncmUgY2FsbGluZy1vdXQgcGVyZm9ybSBzcGVjaWZpYyBmdW5jdGlvbnMsIHN1Y2gg
YXMgZGUvZW5jYXBzdWxhdGlvbg0Kb3IgZW5jcnlwdGlvbi9kZWNyeXB0aW9uLiBBbiBleHRlcm5h
bC9ibGFjay1ib3ggdGVzdCBzaG91bGQgbWVhc3VyZQ0KcGVyZm9ybWFuY2UgaW1wcm92ZW1lbnRz
IGluIGEgd2F5IHRoYXQgY2FuIGJlIGNvbXBhcmVkIHRvIHN5c3RlbXMNCnVuZGVyIHRlc3QgdGhh
dCBkbyBub3QgaGF2ZSB0aGUgYmVuZWZpdCBvZiBhY2NlbGVyYXRpb24uDQpTbywgbGlrZSBJIHNh
aWQgYWJvdmUsIHdoZW4gcm91dGVyIHZlbmRvcnMgYWRkZWQgQVNJQ3Mgb24gaW50ZXJmYWNlcywN
Cml0IGRpZG7igJl0IGNoYW5nZSB0aGUgZnVuZGFtZW50YWwgYmVuY2htYXJrcywgYnV0IHRoZSBw
ZXJmb3JtYW5jZSANCmltcHJvdmVkLg0KDQo+ID4NCj4gPj4NCj4gPj4gPiBJZiBuZXcgd29yayBp
cyBuZWVkZWQgLyBwcm9wb3NlZCB0byBiZSBhZGRlZCBmb3IgdGhlIEJNV0cgc2NvcGUgYW5kDQo+
ID4+ID4gZnJhbWV3b3JrIGl0IHdvdWxkIGJlIHVzZWZ1bCBmb3IgQk1XRyB0byBsaXN0IHRoZXNl
IHNlcGFyYXRlbHkuDQo+ID4+ID4NCj4gPj4gPg0KPiA+PiA+IE5pdHMvZWRpdG9yaWFsIGNvbW1l
bnRzOg0KPiA+PiA+DQo+ID4+ID4gMS4gV2hhdCBpcyBjYWxsZWQgJ0RlcGxveW1lbnQgc2NlbmFy
aW9zJyBmcm9tIFZTIHBlcnNwZWN0aXZlIGluDQo+ID4+ID4gU2VjdGlvbiA0IGRlc2NyaWJlIGlu
IGZhY3QgZGlmZmVyZW50IGNvbmZpZ3VyYXRpb25zIG9mIHRoZSBTVVQgaW4NCj4gQk1XRw0KPiA+
PiA+IHRlcm1zLiBJdCBzZWVtcyBiZXR0ZXIgdG8gc2VwYXJhdGUgdGhpcyBzZWNvbmQgcGFydCBv
ZiBzZWN0aW9uIDQgaW4NCj4gYQ0KPiA+PiA+IHNlcGFyYXRlIHNlY3Rpb24uIElmIGl0IGJlbG9u
Z3MgdG8gYW4gZXhpc3Rpbmcgc2VjdGlvbiBpdCByYXRoZXINCj4gPj4gPiBiZWxvbmdzIGluIDMg
dGhhbiBpbiA0Lg0KPiA+PiA+DQo+ID4+IFtBQ01dDQo+ID4+IFNlY3Rpb24gMyBpcyBtb3JlIGFi
b3V0IGV4dGVuZGluZyB0aGUgY29uZmlndXJhdGlvbiBndWlkYW5jZQ0KPiA+PiBmcm9tDQo+ID4+
IGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0NCj4gM0Ff
X3Rvb2xzLmlldGYub3JnX2h0bWxfZHJhZnQtMkRpZXRmLTJEYm13Zy0yRHZpcnR1YWwtMkRuZXQt
MkQwNS0NCj4gMjNzZWN0aW9uLTJEMy4yJmQ9RHdJQmFRJmM9TEZZWi0NCj4gbzlfSFVNZU1UU1Fp
Y3ZqSWcmcj1PZnNTdThrVElsdFZ5RDFvTDcyY0J3Jm09aG9IV1h2NThheTNXZ0xjMTE1WFlycHJW
bUY5DQo+IDE0enBpaUdDQTZNUWtuYnMmcz1Md3Q5U2FwcGdLUUlsMnhCYlVYOXhFV3BVcnQwUVY0
MUI0M25TZWYwQnhNJmU9DQo+ID4+DQo+ID4+IFNlY3Rpb24gNCBzdW1tYXJpemVzIHRoZSBWU1BF
UkYgTGV2ZWwgVGVzdCBEZXNpZ24gZG9jdW1lbnQsDQo+ID4+IG9mIHdoaWNoIHRoZXNlIGRlcGxv
eW1lbnQgc2NlbmFyaW9zIGFyZSBhIGtleSBwYXJ0Lg0KPiA+DQo+ID5bRGFuIHdyb3RlXQ0KPiA+
IFllcywgYnV0IHRoaXMgc2VhbXMgdG8gYmVsb25nIHRvIGNvbmZpZ3VyYXRpb25zIG9mIFNVVHMs
IGV2ZW4gaWYgdGhleSBhcmUNCj4gPiBjYWxsZWQgJ0RlcGxveW1lbnQgc2NlbmFyaW9zJyBpbiBP
UE5GVi1zcGVhaywgYW5kIHRoZXkgaW1wYWN0IHJlcGVhdGliaWxpdHkuDQpbQUNNXSANCllvdSBj
YW4gb25seSBjb21wYXJlIHRoZSBwZXJmb3JtYW5jZSBvZiBkaWZmZXJlbnQgY29tcHV0ZXIgU1VU
cyB3aGVuIHRoZXkNCmltcGxlbWVudCB0aGUgc2FtZSB2U3dpdGNoIChhbmQgVk1zKSBhbmQgZGVw
bG95bWVudCBzY2VuYXJpby4NCkNvbnNpc3RlbnQgb25maWd1cmF0aW9uIHBhcmFtZXRlcnMgYW5k
IHRlc3Qgc2V0dXBzIGFyZSBhbGwgaW1wb3J0YW50IA0KY29tcG9uZW50cyBvZiBhY2hpZXZpbmcg
cmVwZWF0YWJsZSByZXN1bHRzLg0KDQo+ID4NCj4gPj4NCj4gPj4NCj4gPj4gdGhhbmtzIGZvciB5
b3VyIGNvbW1lbnRzOyBob3BlZnVsbHkgdGhpcyBkZXRhaWxlZCByZXBseQ0KPiA+PiB3aWxsIHJl
ZHVjZSB5b3VyIHJlc2VydmF0aW9ucyBhYm91dCBwdWJsaWNhdGlvbi4NCj4gPj4NCj4gPj4gQWwN
Cj4gPj4gKGZvciB0aGUgY28tYXV0aG9ycykNCj4gPj4NCj4gPj4gWzBdDQo+ID4+IGh0dHBzOi8v
dXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0NCj4gM0FfX3d3dy5vcG5m
di5vcmdfYW5ub3VuY2VtZW50c18yMDE0XzA5XzMwX3RlbGVjb20tMkRpbmR1c3RyeS0yRGFuZC0N
Cj4gMkR2ZW5kb3JzLTJEdW5pdGUtMkR0by0yRGJ1aWxkLTJEY29tbW9uLTJEb3Blbi0yRHBsYXRm
b3JtLTJEdG8tDQo+IDJEYWNjZWxlcmF0ZS0yRG5ldHdvcmstMkRmdW5jdGlvbnMtMkR2aXJ0dWFs
aXphdGlvbiZkPUR3SUJhUSZjPUxGWVotDQo+IG85X0hVTWVNVFNRaWN2aklnJnI9T2ZzU3U4a1RJ
bHRWeUQxb0w3MmNCdyZtPWhvSFdYdjU4YXkzV2dMYzExNVhZcnByVm1GOQ0KPiAxNHpwaWlHQ0E2
TVFrbmJzJnM9dXZHb0kxMGpiVm90MS1FQWp4MFNDVDBmeTBSekV3VGxXeVc2RFdyZTRJVSZlPQ0K
PiA+Pg0KPiA+DQo+IA0KPiANCj4gDQo+IC0tDQo+IEkgZG9uJ3QgdGhpbmsgdGhlIGV4ZWN1dGlv
biBpcyByZWxldmFudCB3aGVuIGl0IHdhcyBvYnZpb3VzbHkgYSBiYWQNCj4gaWRlYSBpbiB0aGUg
Zmlyc3QgcGxhY2UuDQo+IFRoaXMgaXMgbGlrZSBwdXR0aW5nIHJhYmlkIHdlYXNlbHMgaW4geW91
ciBwYW50cywgYW5kIGxhdGVyIGV4cHJlc3NpbmcNCj4gcmVncmV0IGF0IGhhdmluZyBjaG9zZW4g
dGhvc2UgcGFydGljdWxhciByYWJpZCB3ZWFzZWxzIGFuZCB0aGF0IHBhaXINCj4gb2YgcGFudHMu
DQo+ICAgIC0tLW1hZg0K


From nobody Tue Jun  6 18:56:16 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 EE6F0129564 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 18:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aSYiSy3Dj8tc for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 18:56:13 -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 8107D12960D for <ietf@ietf.org>; Tue,  6 Jun 2017 18:56:13 -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 1dIQCh-0006zV-Bd; Wed, 07 Jun 2017 01:56:11 +0000
Date: Wed, 07 Jun 2017 07:56:08 +0600
Message-ID: <m2d1agpnlz.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Donald Eastlake <d3e3e3@gmail.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
In-Reply-To: <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@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/AnWgKfuLsV1QP-R4oUNoRqeq6Tw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 01:56:15 -0000

> bssid/macs are manufacturer based but there are companies that provide
> positioning services based on learning where those MACs are -- typically
> combining such MAC based Wi-Fi/Bluetooth information with IP, GPS, ...
> information to try to get an accurate location. If you happen to be in a
> hotel function room and can only see meeting provided APs, so you can't see
> any fixed local APs, you can easily get Geolocated to the previous meeting
> site.

yes, that is what i thought i was trying to say


From nobody Tue Jun  6 18:58:02 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 EE7DD129ADA for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 18:58:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R42Mcaupts5E for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 18:58:00 -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 EAFE11296B3 for <ietf@ietf.org>; Tue,  6 Jun 2017 18:57: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 1dIQEQ-00071I-JF; Wed, 07 Jun 2017 01:57:59 +0000
Date: Wed, 07 Jun 2017 07:57:56 +0600
Message-ID: <m2bmq0pniz.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
In-Reply-To: <71fff966-8767-fbfb-acb8-cede6a4f8a96@gmail.com>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <71fff966-8767-fbfb-acb8-cede6a4f8a96@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/VSGfzNvEJq1RPeUX4pOSzR1Cfuk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 01:58:01 -0000

>>> Geolocation via topologically defined addresses is silly. Why do we
>>> care about fixing it?
>> 
>> i was not aware that bssid/macs were topologically assigned.  i thought
>> they were mfr based.  i guess slaac can be used to confuddle the two. :)
>  
> A fair hit, but topologically- or physical device- based are
> both broken solutions IMNSHO. I understand that the IETF NOC
> has to deal with it pragmatically, but let's not imagine that
> there's any real fix for intrinsic breakage.

we have a text database of our bssid/macs.  we could prod the geoloc
provider to pull it and the new location.  would need authentication,
authorization, etc. of course.

randy


From nobody Tue Jun  6 18:58:38 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 456121296B3 for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 18:58:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GPrh_9UJksjm for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 18:58:35 -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 AD8F5129AD7 for <ietf@ietf.org>; Tue,  6 Jun 2017 18:58:33 -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 1dIQEx-00071Z-J2; Wed, 07 Jun 2017 01:58:31 +0000
Date: Wed, 07 Jun 2017 07:58:29 +0600
Message-ID: <m2a85kpni2.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Nico Williams <nico@cryptonector.com>
Cc: Donald Eastlake <d3e3e3@gmail.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
In-Reply-To: <20170606234413.GD3432@localhost>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost>
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/xYyPebdl_Ni6MI-r38HN0KE5x_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: Wed, 07 Jun 2017 01:58:36 -0000

> Can the BSSIDs be changed?

many mfrs do not support


From nobody Tue Jun  6 19:07:40 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 6CF521296CD for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 19:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1yrA3ItlQZYW for <ietf@ietfa.amsl.com>; Tue,  6 Jun 2017 19:07:38 -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 3E66D127275 for <ietf@ietf.org>; Tue,  6 Jun 2017 19:07:38 -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 1dIQNk-00078D-As; Wed, 07 Jun 2017 02:07:36 +0000
Date: Wed, 07 Jun 2017 08:07:34 +0600
Message-ID: <m28tl4pn2x.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
In-Reply-To: <20170606233106.yeyugzneqa4tjr44@thunk.org>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606233106.yeyugzneqa4tjr44@thunk.org>
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/NGuY_hHADrOKC3SIxfW3ratmyqY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 02:07:39 -0000

> The IETF AP's go active for a short-time, and then go dark, and when
> they come back, they are obviously in a different location

how does the geoloc provider detect that they are in a new locatio?
i assume, but do not know, that google drives by, but not very often.
i have no ideas how others do it.  gsm comparison?  phone gps?  but does
my phone give them those data; i might not like that.

> users who geolocate to those AP's quickly shown to be in the "wrong"
> place, in that when they get Cell Tower information, it conflicts with
> the geolocation hint associated with the AP.

my phone gets the conflict, but does the geoloc provider?  does my phone
give them those data; i might not like that.

> The service could keep them on a list of AP's where after they go dark
> for say, 24 hours, when they come back on-line the system should try
> to use location services based on cell tower, GPS, etc., to figure out
> where they are on a real-time basis.

i suspect they already do some sort of thing such as this.  after all,
it's their business.  unfortunately, roaming APs are probably a
negligible percent of their targets; which is why they do not even
answer our email.

randy


From nobody Tue Jun  6 22:17:28 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 1828A129C6B; Tue,  6 Jun 2017 22:17:09 -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 KnZWc9RP8aUu; Tue,  6 Jun 2017 22:17:07 -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 40A7E129C5F; Tue,  6 Jun 2017 22:17:06 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DOO50670; Wed, 07 Jun 2017 05:17:03 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 7 Jun 2017 06:15:56 +0100
Received: from DGGEMM402-HUB.china.huawei.com (10.3.20.210) by nkgeml412-hub.china.huawei.com (10.98.56.73) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 7 Jun 2017 13:15:53 +0800
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; Wed, 7 Jun 2017 13:15:50 +0800
From: Roni Even <roni.even@huawei.com>
To: Jonathan Lennox <jonathan@vidyo.com>, Roni Even <ron.even.tlv@gmail.com>
CC: "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>,  General Area Review Team <gen-art@ietf.org>, "avtext@ietf.org" <avtext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMAgAAtEkA=
Date: Wed, 7 Jun 2017 05:15:49 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com>
In-Reply-To: <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.201.114.24]
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.0A020201.59378C50.007D, 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: 3d74a58d2d494a58a26607d3ea3a4b57
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uhUsY2o4cina6Nkzsz346dXvYN8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 05:17:09 -0000

SGkgSm9uYXRoYW4sDQpJIGRpZCBub3Qgc2VlIHRoZSB0ZXh0IHlvdSBhZGRlZCB5ZXQgYXMgYSBy
ZXNwb25zZSB0byBteSBmaXJzdCBxdWVzdGlvbg0KU28gdG8gYmV0dGVyIGNsYXJpZnkgbXkgcXVl
c3Rpb24gLiBJZiB0aGUgRkNJIGhhcyBUVElEPTAgYW5kIFRMSUQ9MiAuIGRvZXMgaXQgbWVhbiB0
aGF0IGl0IGlzIGEgcmVxdWVzdCB0byB1cGRhdGUgYm90aD8NClRoaXMgd2FzIGFsc28gdGhlIHJl
YXNvbiBmb3IgdGhlIHF1ZXN0aW9uIGFib3V0IGJvdGggVFRJRD0wIGFuZCBUTElEPTAsIHdoaWNo
IGxheWVyIG5lZWQgdXBkYXRlIG9yIGlzIGl0IGJvdGg/DQpDYW4geW91IHNheSB0aGF0IHlvdSB3
YW50IGp1c3QgdG8gdXBkYXRlIHRlbXBvcmFsIG9yIHNwYXRpYWw/DQoNClJvbmkNCg0KPiAtLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBHZW4tYXJ0IFttYWlsdG86Z2VuLWFydC1i
b3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSm9uYXRoYW4NCj4gTGVubm94DQo+IFNlbnQ6
INeZ15XXncKg15MgMDcg15nXldeg15kgMjAxNyAwMDozMA0KPiBUbzogUm9uaSBFdmVuDQo+IENj
OiBkcmFmdC1pZXRmLWF2dGV4dC1scnIuYWxsQGlldGYub3JnOyBHZW5lcmFsIEFyZWEgUmV2aWV3
IFRlYW07DQo+IGF2dGV4dEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTog
W0dlbi1hcnRdIEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0ZXh0LWxy
ci0wNQ0KPiANCj4gSGksIFJvbmkg4oCUIHRoYW5rcyBmb3IgeW91ciByZXZpZXcuICBSZXNwb25z
ZXMgaW5saW5lLg0KPiANCj4gPiBPbiBKdW4gMSwgMjAxNywgYXQgMjo1MyBBTSwgUm9uaSBFdmVu
IDxyb24uZXZlbi50bHZAZ21haWwuY29tPiB3cm90ZToNCj4gPg0KPiA+IFJldmlld2VyOiBSb25p
IEV2ZW4NCj4gPiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KPiA+DQo+ID4gSSBh
bSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVy
YWwgQXJlYQ0KPiA+IFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3Vt
ZW50cyBiZWluZyBwcm9jZXNzZWQgYnkNCj4gPiB0aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIu
ICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMganVzdCBsaWtlDQo+ID4gYW55IG90aGVyIGxh
c3QgY2FsbCBjb21tZW50cy4NCj4gPg0KPiA+IEZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ug
c2VlIHRoZSBGQVEgYXQNCj4gPg0KPiA+IDxodHRwczovL3RyYWMuaWV0Zi5vcmcvdHJhYy9nZW4v
d2lraS9HZW5BcnRmYXE+Lg0KPiA+DQo+ID4gRG9jdW1lbnQ6IGRyYWZ0LWlldGYtYXZ0ZXh0LWxy
ci0/Pw0KPiA+IFJldmlld2VyOiBSb25pIEV2ZW4NCj4gPiBSZXZpZXcgRGF0ZTogMjAxNy0wNS0z
MQ0KPiA+IElFVEYgTEMgRW5kIERhdGU6IDIwMTctMDYtMDgNCj4gPiBJRVNHIFRlbGVjaGF0IGRh
dGU6IE5vdCBzY2hlZHVsZWQgZm9yIGEgdGVsZWNoYXQNCj4gPg0KPiA+IFN1bW1hcnk6DQo+ID4g
VGhlIGRvY3VtZW50IGlzIHJlYWR5IHdpdGggaXNzdWVzIGZvciBhIHN0YW5kYXJkIHRyYWNrIFJG
QyBNYWpvcg0KPiA+IGlzc3VlczoNCj4gPg0KPiA+IE1pbm9yIGlzc3VlczoNCj4gPg0KPiA+IDEu
IENhbiB5b3Ugc3BlY2lmeSBib3RoIFRUSUQgYW5kIFRMSUQgaW4gdGhlIHNhbWUgRkNJLg0KPiAN
Cj4gU3ludGFjdGljYWxseSwgdGhleSBtdXN0IGJvdGggb2NjdXIuDQo+IA0KPiBJZiB5b3UgbWVh
biBjYW4geW91IHJlcXVlc3QgYW4gdXBncmFkZSBpbiBib3RoIGF0IG9uY2UsIHllczsgSeKAmXZl
IGFkZGVkIHRleHQNCj4gdG8gY2xhcmlmeSB0aGlzLg0KPiANCj4gPiAyLiBXaGF0IGlzIHRoZSBt
ZWFuaW5nIG9mIHZhbHVlIDAgZm9yIFRUSUQgYW5kIFRMSUQgLSBUSUQgb3IgTElEID0wIGluDQo+
ID4gZnJhbWUgbWFya2luZyBkcmFmdCBtZWFucyBiYXNlIGxheWVyIGlmIHRoZXJlIGlzIHNjYWxh
YmlsaXR5Lg0KPiA+ICAgICBUaGlzIHJlbGF0ZXMgdG8gdGhlIHByZXZpb3VzIHF1ZXN0aW9uLg0K
PiANCj4gSeKAmW0gbm90IHN1cmUgSSB1bmRlcnN0YW5kIHRoaXMgcXVlc3Rpb24uDQo+IA0KPiBJ
4oCZdmUgYWRkZWQgdGV4dCB0aGF0IGlmIEM9MSwgYXQgbGVhc3Qgb25lIG9mIDxUVElELCBUTElE
PiBNVVNUIGJlIGdyZWF0ZXIgdGhhbg0KPiA8Q1RJRCwgQ0xJRD4sIGFuZCBib3RoIE1VU1QgYmUg
Z3JlYXRlciB0aGFuIG9yIGVxdWFsIHRvIHRoZWlyIGNvdW50ZXJwYXJ0LA0KPiBzbyB0aGUgTFJS
IGlzIGFjdHVhbGx5IHJlcXVlc3RpbmcgYSBsYXllciB1cGdyYWRlLiAgSXMgdGhhdCB3aGF0IHlv
dSB3ZXJlDQo+IGFza2luZyBhYm91dD8NCj4gDQo+ID4gMy4gIFdoYXQgd291bGQgYW4gRkNJIHdp
dGggYm90aCBUVElEIGFuZCBUTElEIGVxdWFsIDAgbWVhbi4NCj4gDQo+IEl0IG1lYW5zIHlvdSB3
YW50IGEgcmVmcmVzaCBvZiB0aGUgYmFzZSB0ZW1wb3JhbC9zcGF0aWFsIGxheWVyLCBvbmx5Lg0K
PiANCj4gPiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4gPg0KPiA+IDEuIFNlY3Rpb24gMyAi
YW4gUmVhbC1UaW1lIFRyYW5zcG9ydCBDb250cm9sIFByb3RvY29sIiBzaG91bGQgYmUgImENCj4g
PiBSZWFs4oCmIi4NCj4gDQo+IENvbGluIHBvaW50ZWQgb3V0IHRoYXQgaXQgc2hvdWxkIHNheSDi
gJxhbiBSVFAgQ29udHJvbCBQcm90b2NvbOKAnSBhbnl3YXkuDQo+IA0KPiA+IDIuIEluIHNlY3Rp
b24gMyAiIFtSRkM1MTA0XShTZWN0aW9uIDMuNS4xKSIgdGhlcmUgaXMgYSBsaW5rIHRvIHNlY3Rp
b24NCj4gPiAzLjUuMSBidXQgaXQgZG9lcyBub3Qgd29yay4NCj4gDQo+IHhtbDJyZmMgZG9lc27i
gJl0IGhhdmUgYW55IHdheSB0byBsaW5rIHRvIHNlY3Rpb25zIG9mIG90aGVyIGRvY3VtZW50cywg
c28gdGhlDQo+IOKAnChTZWN0aW9uIDMuNS4xKeKAnSBwYXJ0IGlzIGp1c3QgYSBjb21tZW50Lg0K
PiANCj4gSSB0aGluayB0aGUgaW50ZXJuZXQtZHJhZnQgdG9vbGluZyBtYXkgaGF2ZSB0aG91Z2h0
IEkgd2FzIHRyeWluZyB0byBsaW5rIHRvIGENCj4gbm9uLWV4aXN0ZW50IHNlY3Rpb24gMy41LjEg
b2YgdGhpcyBkb2N1bWVudCwgYnV0IHRoYXTigJlzIG91dHNpZGUgbXkgY29udHJvbC4NCj4gDQo+
ID4gMy4gSW4gc2VjdGlvbiAzLjIgIihzZWUgc2VjdGlvbiBTZWN0aW9uIDIuMSkiIHNlY3Rpb24g
YXBwZWFycyB0d2ljZS4NCj4gDQo+IEZpeGVkLg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fXw0KPiBHZW4tYXJ0IG1haWxpbmcgbGlzdA0KPiBHZW4tYXJ0
QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZ2VuLWFy
dA0K


From nobody Wed Jun  7 00:23:21 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 0FB0212EAE2 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 00:23:20 -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 7aAopUTo6pd3 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 00:23:18 -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 9335112EAE4 for <ietf@ietf.org>; Wed,  7 Jun 2017 00:23:18 -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 1dIVJE-0005UW-V9 for ietf@ietf.org; Wed, 07 Jun 2017 09:23:17 +0200
Received: from [10.5.2.15] (helo=xmail05.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 1dIVJC-0008LW-La for ietf@ietf.org; Wed, 07 Jun 2017 03:23:15 -0400
Received: (qmail 6056 invoked from network); 7 Jun 2017 07:23:12 -0000
Received: from unknown (HELO [10.243.34.188]) (Authenticated-user:_huitema@huitema.net@[89.202.203.52]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 7 Jun 2017 07:23:11 -0000
To: ietf@ietf.org
References: <m27f0pqgbc.wl-randy@psg.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <3e926ca5-36ed-2274-f1ce-77830a359995@huitema.net>
Date: Wed, 7 Jun 2017 09:23:13 +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: <m27f0pqgbc.wl-randy@psg.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Subject: Re: wireless geolocation
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.05)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJYWea6pBBugJdVQWCV6zgcsND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA23nkjdCd3dHitGnPFsiJOYSOoI9GlgXFbGvhvB 71hlmrputuSwpg7CI7YTlcOvrga+YOEkjsX7F8KmpUaZQHV+SU9tg6wnJ2lrZSUCZrKFYsG2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpKrrXdhf8mmRqp8CWMEqUPf6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGyWM9VwrHi6OdejEV17c+GbXeNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj236N2IVdgBdepwvDBBcDOz9LNdSMuNhZC3X/nGdDKYyg+xII1yJ8udUSd8siDlV+9cBL pGLKbiMLMKI7KIsgfDrl6J1fhOzjF0b4LXcjJZ5lorSoCYRNcdNYFM9Dkt7piwO7IVXITpPh1qZI 46Rz116sNzwwlSLmm3E2ZLQS++ZzHF9e6qt4y0llDRDaFA2tZcPw1eMmeklA3MQEw0NwP6IDPa8Q GWJY81iEsidlXaP4/sbpzuwjGHyC+YDvAYilEDOxBm1FmeLkxn4IHfZH9cZYxFsYxzp73yKmZ7FG FxtqMg==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FWJRMLULq4cPtjcBafjvwzwCsXI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 07:23:20 -0000

On 6/6/2017 5:36 PM, Randy Bush wrote:

> the ietf is far from the only event with this problem.  but it is kind
> of in our purview to automate it.  the noc is not the place to work on
> protocols and databases; the noc is just the customer/user.  a bof or
> some existing wg might be.

Another argument for MAC Address randomization...

-- Christian Huitema


From nobody Wed Jun  7 00:39:32 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 8840912EAF0; Wed,  7 Jun 2017 00:39:25 -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 bvuX8M425-Ch; Wed,  7 Jun 2017 00:39:23 -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 9210912EAEC; Wed,  7 Jun 2017 00:39:22 -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 DIA89554; Wed, 07 Jun 2017 07:39:20 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 7 Jun 2017 08:38:21 +0100
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by nkgeml412-hub.china.huawei.com (10.98.56.73) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 7 Jun 2017 15:38:18 +0800
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.49]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0301.000; Wed, 7 Jun 2017 15:38:11 +0800
From: Roni Even <roni.even@huawei.com>
To: Roni Even <roni.even@huawei.com>, Jonathan Lennox <jonathan@vidyo.com>, Roni Even <ron.even.tlv@gmail.com>
CC: "avtext@ietf.org" <avtext@ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMAgAAtEkCAACiLwA==
Date: Wed, 7 Jun 2017 07:38:10 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7CFF80@DGGEMM506-MBX.china.huawei.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.201.114.24]
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.0A020203.5937ADA8.0169, 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: e2a6e4c8b8332e96d28b21904c02d2cb
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dEfjRb4276ePYtXjQgFch5F-PsU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 07:39:26 -0000

SGkgSm9uYXRoYW4sDQpKdXN0IGFub3RoZXIgY2xhcmlmaWNhdGlvbiBmb3IgYm90aCBUVElEPTAg
YW5kIFRMSUQ9MCAsIEkgdW5kZXJzdGFuZCB0aGF0IHRoZXJlIGlzIG9uZSBiYXNlIGxheWVyLCBi
dXQgZG9lcyB0aGlzIGNhc2UgaGF2ZSBhbnkgc3BlY2lhbCBtZWFuaW5nPw0KUm9uaQ0KDQo+IC0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEdlbi1hcnQgW21haWx0bzpnZW4tYXJ0
LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBSb25pIEV2ZW4NCj4gU2VudDog15nXlded
wqDXkyAwNyDXmdeV16DXmSAyMDE3IDA4OjE2DQo+IFRvOiBKb25hdGhhbiBMZW5ub3g7IFJvbmkg
RXZlbg0KPiBDYzogYXZ0ZXh0QGlldGYub3JnOyBHZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW07IGRy
YWZ0LWlldGYtYXZ0ZXh0LQ0KPiBscnIuYWxsQGlldGYub3JnOyBpZXRmQGlldGYub3JnDQo+IFN1
YmplY3Q6IFJlOiBbR2VuLWFydF0gR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0
Zi1hdnRleHQtbHJyLTA1DQo+IA0KPiBIaSBKb25hdGhhbiwNCj4gSSBkaWQgbm90IHNlZSB0aGUg
dGV4dCB5b3UgYWRkZWQgeWV0IGFzIGEgcmVzcG9uc2UgdG8gbXkgZmlyc3QgcXVlc3Rpb24gU28g
dG8NCj4gYmV0dGVyIGNsYXJpZnkgbXkgcXVlc3Rpb24gLiBJZiB0aGUgRkNJIGhhcyBUVElEPTAg
YW5kIFRMSUQ9MiAuIGRvZXMgaXQgbWVhbg0KPiB0aGF0IGl0IGlzIGEgcmVxdWVzdCB0byB1cGRh
dGUgYm90aD8NCj4gVGhpcyB3YXMgYWxzbyB0aGUgcmVhc29uIGZvciB0aGUgcXVlc3Rpb24gYWJv
dXQgYm90aCBUVElEPTAgYW5kIFRMSUQ9MCwNCj4gd2hpY2ggbGF5ZXIgbmVlZCB1cGRhdGUgb3Ig
aXMgaXQgYm90aD8NCj4gQ2FuIHlvdSBzYXkgdGhhdCB5b3Ugd2FudCBqdXN0IHRvIHVwZGF0ZSB0
ZW1wb3JhbCBvciBzcGF0aWFsPw0KPiANCj4gUm9uaQ0KPiANCj4gPiAtLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KPiA+IEZyb206IEdlbi1hcnQgW21haWx0bzpnZW4tYXJ0LWJvdW5jZXNAaWV0
Zi5vcmddIE9uIEJlaGFsZiBPZiBKb25hdGhhbg0KPiA+IExlbm5veA0KPiA+IFNlbnQ6INeZ15XX
ncKg15MgMDcg15nXldeg15kgMjAxNyAwMDozMA0KPiA+IFRvOiBSb25pIEV2ZW4NCj4gPiBDYzog
ZHJhZnQtaWV0Zi1hdnRleHQtbHJyLmFsbEBpZXRmLm9yZzsgR2VuZXJhbCBBcmVhIFJldmlldyBU
ZWFtOw0KPiA+IGF2dGV4dEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZw0KPiA+IFN1YmplY3Q6IFJl
OiBbR2VuLWFydF0gR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YNCj4gPiBkcmFmdC1pZXRmLWF2
dGV4dC1scnItMDUNCj4gPg0KPiA+IEhpLCBSb25pIOKAlCB0aGFua3MgZm9yIHlvdXIgcmV2aWV3
LiAgUmVzcG9uc2VzIGlubGluZS4NCj4gPg0KPiA+ID4gT24gSnVuIDEsIDIwMTcsIGF0IDI6NTMg
QU0sIFJvbmkgRXZlbiA8cm9uLmV2ZW4udGx2QGdtYWlsLmNvbT4gd3JvdGU6DQo+ID4gPg0KPiA+
ID4gUmV2aWV3ZXI6IFJvbmkgRXZlbg0KPiA+ID4gUmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBJ
c3N1ZXMNCj4gPiA+DQo+ID4gPiBJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZv
ciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhDQo+ID4gPiBSZXZpZXcgVGVhbSAoR2VuLUFS
VCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5DQo+ID4gPiB0
aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMg
anVzdCBsaWtlDQo+ID4gPiBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLg0KPiA+ID4NCj4g
PiA+IEZvciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4gPiA+DQo+
ID4gPiA8aHR0cHM6Ly90cmFjLmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPi4NCj4g
PiA+DQo+ID4gPiBEb2N1bWVudDogZHJhZnQtaWV0Zi1hdnRleHQtbHJyLT8/DQo+ID4gPiBSZXZp
ZXdlcjogUm9uaSBFdmVuDQo+ID4gPiBSZXZpZXcgRGF0ZTogMjAxNy0wNS0zMQ0KPiA+ID4gSUVU
RiBMQyBFbmQgRGF0ZTogMjAxNy0wNi0wOA0KPiA+ID4gSUVTRyBUZWxlY2hhdCBkYXRlOiBOb3Qg
c2NoZWR1bGVkIGZvciBhIHRlbGVjaGF0DQo+ID4gPg0KPiA+ID4gU3VtbWFyeToNCj4gPiA+IFRo
ZSBkb2N1bWVudCBpcyByZWFkeSB3aXRoIGlzc3VlcyBmb3IgYSBzdGFuZGFyZCB0cmFjayBSRkMg
TWFqb3INCj4gPiA+IGlzc3VlczoNCj4gPiA+DQo+ID4gPiBNaW5vciBpc3N1ZXM6DQo+ID4gPg0K
PiA+ID4gMS4gQ2FuIHlvdSBzcGVjaWZ5IGJvdGggVFRJRCBhbmQgVExJRCBpbiB0aGUgc2FtZSBG
Q0kuDQo+ID4NCj4gPiBTeW50YWN0aWNhbGx5LCB0aGV5IG11c3QgYm90aCBvY2N1ci4NCj4gPg0K
PiA+IElmIHlvdSBtZWFuIGNhbiB5b3UgcmVxdWVzdCBhbiB1cGdyYWRlIGluIGJvdGggYXQgb25j
ZSwgeWVzOyBJ4oCZdmUNCj4gPiBhZGRlZCB0ZXh0IHRvIGNsYXJpZnkgdGhpcy4NCj4gPg0KPiA+
ID4gMi4gV2hhdCBpcyB0aGUgbWVhbmluZyBvZiB2YWx1ZSAwIGZvciBUVElEIGFuZCBUTElEIC0g
VElEIG9yIExJRCA9MA0KPiA+ID4gaW4gZnJhbWUgbWFya2luZyBkcmFmdCBtZWFucyBiYXNlIGxh
eWVyIGlmIHRoZXJlIGlzIHNjYWxhYmlsaXR5Lg0KPiA+ID4gICAgIFRoaXMgcmVsYXRlcyB0byB0
aGUgcHJldmlvdXMgcXVlc3Rpb24uDQo+ID4NCj4gPiBJ4oCZbSBub3Qgc3VyZSBJIHVuZGVyc3Rh
bmQgdGhpcyBxdWVzdGlvbi4NCj4gPg0KPiA+IEnigJl2ZSBhZGRlZCB0ZXh0IHRoYXQgaWYgQz0x
LCBhdCBsZWFzdCBvbmUgb2YgPFRUSUQsIFRMSUQ+IE1VU1QgYmUNCj4gPiBncmVhdGVyIHRoYW4g
PENUSUQsIENMSUQ+LCBhbmQgYm90aCBNVVNUIGJlIGdyZWF0ZXIgdGhhbiBvciBlcXVhbCB0bw0K
PiA+IHRoZWlyIGNvdW50ZXJwYXJ0LCBzbyB0aGUgTFJSIGlzIGFjdHVhbGx5IHJlcXVlc3Rpbmcg
YSBsYXllciB1cGdyYWRlLg0KPiA+IElzIHRoYXQgd2hhdCB5b3Ugd2VyZSBhc2tpbmcgYWJvdXQ/
DQo+ID4NCj4gPiA+IDMuICBXaGF0IHdvdWxkIGFuIEZDSSB3aXRoIGJvdGggVFRJRCBhbmQgVExJ
RCBlcXVhbCAwIG1lYW4uDQo+ID4NCj4gPiBJdCBtZWFucyB5b3Ugd2FudCBhIHJlZnJlc2ggb2Yg
dGhlIGJhc2UgdGVtcG9yYWwvc3BhdGlhbCBsYXllciwgb25seS4NCj4gPg0KPiA+ID4gTml0cy9l
ZGl0b3JpYWwgY29tbWVudHM6DQo+ID4gPg0KPiA+ID4gMS4gU2VjdGlvbiAzICJhbiBSZWFsLVRp
bWUgVHJhbnNwb3J0IENvbnRyb2wgUHJvdG9jb2wiIHNob3VsZCBiZSAiYQ0KPiA+ID4gUmVhbOKA
piIuDQo+ID4NCj4gPiBDb2xpbiBwb2ludGVkIG91dCB0aGF0IGl0IHNob3VsZCBzYXkg4oCcYW4g
UlRQIENvbnRyb2wgUHJvdG9jb2zigJ0gYW55d2F5Lg0KPiA+DQo+ID4gPiAyLiBJbiBzZWN0aW9u
IDMgIiBbUkZDNTEwNF0oU2VjdGlvbiAzLjUuMSkiIHRoZXJlIGlzIGEgbGluayB0bw0KPiA+ID4g
c2VjdGlvbg0KPiA+ID4gMy41LjEgYnV0IGl0IGRvZXMgbm90IHdvcmsuDQo+ID4NCj4gPiB4bWwy
cmZjIGRvZXNu4oCZdCBoYXZlIGFueSB3YXkgdG8gbGluayB0byBzZWN0aW9ucyBvZiBvdGhlciBk
b2N1bWVudHMsDQo+ID4gc28gdGhlIOKAnChTZWN0aW9uIDMuNS4xKeKAnSBwYXJ0IGlzIGp1c3Qg
YSBjb21tZW50Lg0KPiA+DQo+ID4gSSB0aGluayB0aGUgaW50ZXJuZXQtZHJhZnQgdG9vbGluZyBt
YXkgaGF2ZSB0aG91Z2h0IEkgd2FzIHRyeWluZyB0bw0KPiA+IGxpbmsgdG8gYSBub24tZXhpc3Rl
bnQgc2VjdGlvbiAzLjUuMSBvZiB0aGlzIGRvY3VtZW50LCBidXQgdGhhdOKAmXMgb3V0c2lkZSBt
eQ0KPiBjb250cm9sLg0KPiA+DQo+ID4gPiAzLiBJbiBzZWN0aW9uIDMuMiAiKHNlZSBzZWN0aW9u
IFNlY3Rpb24gMi4xKSIgc2VjdGlvbiBhcHBlYXJzIHR3aWNlLg0KPiA+DQo+ID4gRml4ZWQuDQo+
ID4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gPiBH
ZW4tYXJ0IG1haWxpbmcgbGlzdA0KPiA+IEdlbi1hcnRAaWV0Zi5vcmcNCj4gPiBodHRwczovL3d3
dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dlbi1hcnQNCj4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gR2VuLWFydCBtYWlsaW5nIGxpc3QNCj4g
R2VuLWFydEBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv
L2dlbi1hcnQNCg==


From nobody Wed Jun  7 01:23:58 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 DABE112EB02 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 01:23:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.979
X-Spam-Level: 
X-Spam-Status: No, score=-0.979 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, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o-h2mCZhK4Ol for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 01:23:56 -0700 (PDT)
Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::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 BD96E12EAF7 for <ietf@ietf.org>; Wed,  7 Jun 2017 01:23:55 -0700 (PDT)
Received: by mail-wr0-x22e.google.com with SMTP id q97so2660063wrb.2 for <ietf@ietf.org>; Wed, 07 Jun 2017 01:23:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:cc:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=keBw80MFREHPrF+wIpuANYAwwIU/CDvmar4IOuNJvKk=; b=Q2jKJeADQi5n6g1PeyWZ7SpF3NNZte7LsEdJnkvch0DtzjsKKPG1wyduVZC+4Nu+87 UHxJnQN/8RejbNw+zEi8/7PS1Z6FawgdZaMXp7RkbvT9MyGW5742JvtNpU4xIFkfgSoc Gewc7SN+kvl3RcwBac9RCWo6ZHkcPorU+TywfpIBUHJeVzTWAXc/igBB9Gx8I2qRnhfm L2idIm/AZKSHejGtMK3mBNW9W9mMpdXGSxDC3jmKKhzY4pBETwQy654VnoP2B8rfXSS/ DO7laimM4/STmOdyivCpworNMOAo1cPC1a0lRQuDoPuLPU/PByEwd7T+BAwWyHd7A0GH 4Eow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=keBw80MFREHPrF+wIpuANYAwwIU/CDvmar4IOuNJvKk=; b=mQSoHiFAdHH1O3g9YMjZxgLHlSkG6QjXznCkvHPvUOnIXiAasi7xaL/Yb9CS/OcyXC REccLtRk/J7vzfvyiZOSTKLhPxqYlHO445RA27LChy6VnJQ+wFaHUap58Y34PdJxY8Px kJzflQE2gXHf65iSKTjXBfiu+n1/Q28sf0GTnoBrWtVy0ro5JjHQMtIjzFY01RLa3H8/ 2dxuYDNxoLikpbNTqrnlxO1YGj3OxtYHAiob0P4eLFYV13vW/PDcpXQk/YpQhtbCxRhz pKKvLvwTNa0/qT678xmRxhEiL+EvqqdmTTqP2iCS2LeJhFxeM+f22ePHx+Y2IegQn2vg gVfg==
X-Gm-Message-State: AODbwcCShPBtTLURNl/KLVEYumLLonbLIPpZDHtGvbxeoFN8FZ8i7Wwg RMAjE/2PL6TVWAxvqIQ=
X-Received: by 10.223.144.4 with SMTP id h4mr3584448wrh.182.1496823834073; Wed, 07 Jun 2017 01:23:54 -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 50sm747929wrw.32.2017.06.07.01.23.53 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Jun 2017 01:23:53 -0700 (PDT)
Subject: Re: wireless geolocation
Cc: IETF Rinse Repeat <ietf@ietf.org>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.com>
Date: Wed, 7 Jun 2017 09:23:51 +0100
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: <20170606234413.GD3432@localhost>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2xqXlxjhe27FRD_eBERPM3N-LbQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 08:23:57 -0000

 From an entirely personal perspective I would prefer that
geolocation be irretrievable broken so that it could never
work rather than fixed to work correctly.

- Stewart


From nobody Wed Jun  7 01:34:45 2017
Return-Path: <cdel@firsthand.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 68316129C50 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 01:34:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level: 
X-Spam-Status: No, score=-1.989 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=firsthand.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 gMGHNFn8fECN for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 01:34:41 -0700 (PDT)
Received: from tranquility.default.cdelarrinaga.uk0.bigv.io (tranquility.default.cdelarrinaga.uk0.bigv.io [213.138.114.184]) (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 B312212EB0E for <ietf@ietf.org>; Wed,  7 Jun 2017 01:34:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=firsthand.net; s=tranquility;  h=Content-Type:In-Reply-To:References:Subject:CC:To:MIME-Version:Reply-To:From:Date:Message-ID; bh=Y/oZZny7pSDs+ohPW5gPDkpKSkqZEYfMRJFypiRx3Ag=;  b=rdP2LbcwbAEFsNogHnrvlq9IoXs51k9q8u37RIwaUogLtg3YuAi8QyzTcn+tlJdDNGRD6ZoC7PmXLgYe30YAb222/R/AaJFJ9qSDTH+VaBWWYNy9+QVdp7gYgmOAMKbWBYq0+yeA6E+9qCPahUAfRHx1VLFtIIjMEIGoT9ckIyg=;
Received: from 60.88.155.90.in-addr.arpa ([90.155.88.60] helo=Christians-MacBook-Pro.local) by tranquility.default.cdelarrinaga.uk0.bigv.io with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <cdel@firsthand.net>) id 1dIWQE-00070M-9Y; Wed, 07 Jun 2017 09:34:34 +0100
Message-ID: <5937BA98.4000903@firsthand.net>
Date: Wed, 07 Jun 2017 09:34:32 +0100
From: Christian de Larrinaga <cdel@firsthand.net>
Reply-To: cdel@firsthand.net
User-Agent: Postbox 5.0.14 (Macintosh/20170515)
MIME-Version: 1.0
To: Stewart Bryant <stewart.bryant@gmail.com>
CC: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost> <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.com>
In-Reply-To: <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.com>
Content-Type: multipart/alternative; boundary="------------010901030804060400090909"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ht3GkBK73DF-JNfWQZOGX0kmDZI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 08:34:43 -0000

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

IETF perhaps via IAB could and I think probably ought to issue a health
warning on geolocation. It is too convenient for policy makers to assume
the snake oil is real - Christian

--------------010901030804060400090909
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

<HTML><HEAD><META content="text/html; charset=UTF-8" http-equiv="Content-Type"></HEAD><BODY style="font-size: 14pt;font-family: Helvetica Neue;"><div style="font-size: 14pt;font-family: Helvetica Neue;">IETF perhaps via IAB could and I think probably ought to issue a health warning on geolocation. It is too convenient for policy makers to assume the snake oil is real - Christian</div></BODY></HTML>

--------------010901030804060400090909--


From nobody Wed Jun  7 05:40:05 2017
Return-Path: <andy@hxr.us>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CE2C12EC01 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 05:40:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hxr-us.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 eXouQRhMwuCi for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 05:40:01 -0700 (PDT)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0495B12EBFF for <ietf@ietf.org>; Wed,  7 Jun 2017 05:40:01 -0700 (PDT)
Received: by mail-oi0-x232.google.com with SMTP id p7so4915099oif.2 for <ietf@ietf.org>; Wed, 07 Jun 2017 05:40:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hxr-us.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vgftrgunhbCnrEE6ZHYztfHA5o48suAmvqfjV+0obkA=; b=A203Apa5yHZ3BwJoxL1wSrmmpjX45In4gaDh/bNjIHYE9jH3qxjJO1APA2srck196d Q2CD0k1Xz7SrmDgfaNgYVXeIVll/YC3DQVxJvcIn1wgI03+CeXN/1TzddviqE5UZhzh+ 2af+sImpQPFm4Prci//gG75eUfH+hsSwo7NV3USlhlVJJLdLa7iDXHSEUY1i0t3caVOH HBU0i99jOe8Ml3GMLSL8WRpntVaVFsdFaCCAeaSsmw3Lf0I+b+sgLfrMzLy2SfmUVrP6 Qh2pStSs1FRpPVmWXPAkvoNh/CFWKWbCwISbwysC+OWXp/bv4xN3gidTOXkWfLqnfdq7 Jc3Q==
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=vgftrgunhbCnrEE6ZHYztfHA5o48suAmvqfjV+0obkA=; b=sCeQizNmLYQjDtZ34U5KuIluauUJ8yfK2a5RIQIfosJ0xVOHNDokOOLc7eGwgfmnte 7b5+H0oRqge24LTy7Mcd+0wWec6zCVib2pPgrZXSGQREw4xAz/8vA+im2KIAQtRSH3YC niqje0iFq2N/sAUg6CTuNc1KSh6sLECryAbMuwmedEA3COqP0FQDYZabSpwup4oYxol2 ZCg9r2J8Q9IZiiLfazynA3wMu2WsHbvNxd/bom2d/8BaiPCqW5Ay5DsM3KeXKNoZZuC/ IPwB0PYUEVpv//Y/dbqOrvCkiZPl4TVB2JXfQuElldqOv7OGI5zBYbA7MA95dcw8pz/o eQGQ==
X-Gm-Message-State: AODbwcAdijWxS/iEzGO3zIiDWpbDetFV+XNMLyoPRhrXl9LNwGKAoh80 YVrFYaFz5h2FuCEQsoZvcDFFumyCsUks
X-Received: by 10.202.87.213 with SMTP id l204mr13239142oib.163.1496839200384;  Wed, 07 Jun 2017 05:40:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.157.6.227 with HTTP; Wed, 7 Jun 2017 05:39:59 -0700 (PDT)
X-Originating-IP: [108.45.128.208]
In-Reply-To: <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.com>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost> <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.com>
From: Andrew Newton <andy@hxr.us>
Date: Wed, 7 Jun 2017 08:39:59 -0400
Message-ID: <CAAQiQReRxvbJ8=6OWxs_AM3r+YDzoOv5OA70jaw_Mz7v=n+z0A@mail.gmail.com>
Subject: Re: wireless geolocation
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TFQNzOjD5WeLZHqZlhlpNm_QJNY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 12:40:04 -0000

On Wed, Jun 7, 2017 at 4:23 AM, Stewart Bryant <stewart.bryant@gmail.com> wrote:
>
> From an entirely personal perspective I would prefer that
> geolocation be irretrievable broken so that it could never
> work rather than fixed to work correctly.
>
> - Stewart
>

You're not alone.

The IETF did have a WG called GEOPRIV that ran for over a decade. On
top of that, other various proposals for geoloc have been put through
the IETF, some reaching standardization and some not.

The "PRIV" part of GEOPRIV was about "privacy", and any "good-enough"
geoloc solution will smack into some very serious privacy
considerations.

-andy


From nobody Wed Jun  7 07:42:34 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9186B12EC8B for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 07:42:33 -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_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, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RALpGftZFz6v for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 07:42:32 -0700 (PDT)
Received: from homiemail-a105.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 8DB9F12EC97 for <ietf@ietf.org>; Wed,  7 Jun 2017 07:42:30 -0700 (PDT)
Received: from homiemail-a105.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a105.g.dreamhost.com (Postfix) with ESMTP id 2676630002A27; Wed,  7 Jun 2017 07:42:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=JXACQAXLemnkq8 BrvRcDIR1Z+NU=; b=ZYv2lz0tpR41OqX40TDp7+eOclXgMRI8lFb7U2GJxmWbjv sS4kz6O5pfs2HzLh4aHHaWW3sJjF3B96bxtNhKcYirHzCrT2I2xtzXrYWRssj8mY AMQSRrFMFTG25VCgjOdT3pFmLnc5O/hBwgQnD4XxuyM18vbUYX0UXfZ45ha+Y=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a105.g.dreamhost.com (Postfix) with ESMTPSA id CB84430002A26; Wed,  7 Jun 2017 07:42:29 -0700 (PDT)
Date: Wed, 7 Jun 2017 09:42:27 -0500
From: Nico Williams <nico@cryptonector.com>
To: Randy Bush <randy@psg.com>
Cc: Donald Eastlake <d3e3e3@gmail.com>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
Message-ID: <20170607144225.GE3432@localhost>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost> <m2a85kpni2.wl-randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <m2a85kpni2.wl-randy@psg.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OIzdpufKi0H2mKY_fcQ5aWxh7HQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 14:42:33 -0000

On Wed, Jun 07, 2017 at 07:58:29AM +0600, Randy Bush wrote:
> > Can the BSSIDs be changed?
> 
> many mfrs do not support

Yes, I figured that might be the case here, but since it might not I
thought it worth asking.


From nobody Wed Jun  7 08:01:18 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8F49128BA2 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 08:01:17 -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_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, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lmt6MLT_8PFw for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 08:01:16 -0700 (PDT)
Received: from homiemail-a105.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 7503012945B for <ietf@ietf.org>; Wed,  7 Jun 2017 08:01:15 -0700 (PDT)
Received: from homiemail-a105.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a105.g.dreamhost.com (Postfix) with ESMTP id 03CC130002A2B; Wed,  7 Jun 2017 08:01:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=gCED1LfSNWbaTi RXKBt4icubU3M=; b=NRnna0HDBJf9IEsE4x4/+m40Zg0aY65l136sbZgmCU7cfw KZ7NexLaKPbjfS9pnBUvUTttG4GWqnWvl+/0hasmLyBgmQah+dKN+LGA9MImRqkm 19+TDBq2njnodxtKMG+jAf8sbFCjhGYS55nf4EWFsyZGDoOZ/3/csmYgAaGcg=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a105.g.dreamhost.com (Postfix) with ESMTPSA id AD38130002A2A; Wed,  7 Jun 2017 08:01:14 -0700 (PDT)
Date: Wed, 7 Jun 2017 10:01:12 -0500
From: Nico Williams <nico@cryptonector.com>
To: Christian Huitema <huitema@huitema.net>
Cc: ietf@ietf.org
Subject: Re: wireless geolocation
Message-ID: <20170607150110.GF3432@localhost>
References: <m27f0pqgbc.wl-randy@psg.com> <3e926ca5-36ed-2274-f1ce-77830a359995@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3e926ca5-36ed-2274-f1ce-77830a359995@huitema.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BT9RM8Ium0cquxMo30HKsiCtmLI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 15:01:18 -0000

On Wed, Jun 07, 2017 at 09:23:13AM +0200, Christian Huitema wrote:
> On 6/6/2017 5:36 PM, Randy Bush wrote:
> > the ietf is far from the only event with this problem.  but it is kind
> > of in our purview to automate it.  the noc is not the place to work on
> > protocols and databases; the noc is just the customer/user.  a bof or
> > some existing wg might be.
> 
> Another argument for MAC Address randomization...

+1

Though that's likely to lead geoloc providers to use other methods over
which we'd have even less control.  But still, MAC address randomization
is a good thing all around.


From nobody Wed Jun  7 08:18:44 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 47B2B12ECAE for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 08:18:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.8
X-Spam-Level: 
X-Spam-Status: No, score=-3.8 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, URIBL_BLOCKED=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 d8mLuIl3FIpj for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 08:18:41 -0700 (PDT)
Received: from mta-p8.oit.umn.edu (mta-p8.oit.umn.edu [134.84.196.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D42712ECB0 for <ietf@ietf.org>; Wed,  7 Jun 2017 08:18:35 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mta-p8.oit.umn.edu (Postfix) with ESMTP id 0E47C992 for <ietf@ietf.org>; Wed,  7 Jun 2017 15:18:35 +0000 (UTC)
X-Virus-Scanned: amavisd-new at umn.edu
Received: from mta-p8.oit.umn.edu ([127.0.0.1]) by localhost (mta-p8.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLqg_-DcuB7f for <ietf@ietf.org>; Wed,  7 Jun 2017 10:18:34 -0500 (CDT)
Received: from mail-ua0-f199.google.com (mail-ua0-f199.google.com [209.85.217.199]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p8.oit.umn.edu (Postfix) with ESMTPS id B8D7724B for <ietf@ietf.org>; Wed,  7 Jun 2017 10:18:34 -0500 (CDT)
Received: by mail-ua0-f199.google.com with SMTP id k4so2196782uaa.0 for <ietf@ietf.org>; Wed, 07 Jun 2017 08:18:34 -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=2Ls8JFCVcpM2t0LE0Z4yhYMSHWfor7HmJbNM50x0+Ik=; b=oyntFuuTINaWxQRwh5NcYrHzAg5Vuh5xNiqF5PL283tKpCFT8rwUMsk/oqueq0JwOL E42l6d4E12o0h9hRUcp+N3fUFCcFe+HNiDZrCf/5oowfySyLDDbwR01a3zXTJFKKJsyt FZtjpLafPXd+wtci+Y4uKo1I8xCgj9UTntsNcfgCXPurTWOxe3FVs7aBiEZEfxbQuljE Hjryx1rssygoQ61xCJLBo0uLl17d1aBFehMRvCXNXxWAvG+X2bSPGi0xMuoEHCOP71AE AYO57wJdojJZG2BvwuVx/npJdP/JX9sPesnYX2reovkcB2ZQgFld88DbO1PY4B6zO0uv yRYg==
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=2Ls8JFCVcpM2t0LE0Z4yhYMSHWfor7HmJbNM50x0+Ik=; b=p8qE7JsyQbbowoOZN06+KrJkMpA54I1VYeyDaixCdsYxL/2GLgNoVMs9uzhdnaJ9jH 3UA3qxXwpjdKvw2+sXwW7p5icBhntNXH5bnS6KyXzKm8aIg8MjWI3ik/uLqa6kYScz4E tZX3rD1g+/rG0vcXTrL4Ue0I+JSYPz5oJTSqV79h0O0SuYK8GWRnvX3IMevG9JS1Ba3s cHgrG81Kp90b1CMr6Qe8dLJHvuVLLn3GYvlzsDnLTe6lvB8ha8EM7NpbhLNhJuIJZK1L OsamXOoQzdqJTPIULW5YgWo2xHMXgn4MUXUZAE2lqa3qtM0FtmP9bokEAj+WeI/m/WS0 Yr4Q==
X-Gm-Message-State: AODbwcABjFDV3jFHU/I1VkCyqVVhunIzb2G7ZE/OZnnoD7bBXZyydcHS JZvIl+oU6g1tcmEJCUnc295ISaUSm5/4VX3s8Sy1MTcridR/6uRNsFrAEadjSRuwHJC4It14/p7 rq+9J02ViWiXADZ4=
X-Received: by 10.31.171.3 with SMTP id u3mr14287526vke.22.1496848713871; Wed, 07 Jun 2017 08:18:33 -0700 (PDT)
X-Received: by 10.31.171.3 with SMTP id u3mr14287520vke.22.1496848713668; Wed, 07 Jun 2017 08:18:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.183.11 with HTTP; Wed, 7 Jun 2017 08:18:33 -0700 (PDT)
In-Reply-To: <20170607150110.GF3432@localhost>
References: <m27f0pqgbc.wl-randy@psg.com> <3e926ca5-36ed-2274-f1ce-77830a359995@huitema.net> <20170607150110.GF3432@localhost>
From: David Farmer <farmer@umn.edu>
Date: Wed, 7 Jun 2017 10:18:33 -0500
Message-ID: <CAN-Dau3frXb0B8xR1tZ8JJbXknVLoHVADMVrsuNp6=2DbUpJ0A@mail.gmail.com>
Subject: Re: wireless geolocation
To: Nico Williams <nico@cryptonector.com>
Cc: Christian Huitema <huitema@huitema.net>, IETF-Discussion Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11440008dc8d710551603fcb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2Wj__h1SfOnXbfelwv09-TvYFqk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 15:18:43 -0000

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

On Wed, Jun 7, 2017 at 10:01 AM, Nico Williams <nico@cryptonector.com>
wrote:

> On Wed, Jun 07, 2017 at 09:23:13AM +0200, Christian Huitema wrote:
> > On 6/6/2017 5:36 PM, Randy Bush wrote:
> > > the ietf is far from the only event with this problem.  but it is kind
> > > of in our purview to automate it.  the noc is not the place to work on
> > > protocols and databases; the noc is just the customer/user.  a bof or
> > > some existing wg might be.
> >
> > Another argument for MAC Address randomization...
>
> +1
>
> Though that's likely to lead geoloc providers to use other methods over
> which we'd have even less control.  But still, MAC address randomization
> is a good thing all around.
>

How would Client MAC address randomization help this situation? I not aware
of APs implementing MAC address (BSSID) randomization.



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

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Jun 7, 2017 at 10:01 AM, Nico Williams <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:nico@cryptonector.com" target=3D"_blank">nico@cryptonector.=
com</a>&gt;</span> wrote:<br><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">On Wed, Jun 07, 2017 at 09:23:13AM +0200, Christian Huitema wrote:<br>
&gt; On 6/6/2017 5:36 PM, Randy Bush wrote:<br>
&gt; &gt; the ietf is far from the only event with this problem.=C2=A0 but =
it is kind<br>
&gt; &gt; of in our purview to automate it.=C2=A0 the noc is not the place =
to work on<br>
&gt; &gt; protocols and databases; the noc is just the customer/user.=C2=A0=
 a bof or<br>
&gt; &gt; some existing wg might be.<br>
&gt;<br>
&gt; Another argument for MAC Address randomization...<br>
<br>
+1<br>
<br>
Though that&#39;s likely to lead geoloc providers to use other methods over=
<br>
which we&#39;d have even less control.=C2=A0 But still, MAC address randomi=
zation<br>
is a good thing all around.<br></blockquote><div><br></div><div>How would C=
lient MAC address randomization help this situation? I not aware of APs imp=
lementing MAC address (BSSID) randomization. =C2=A0</div></div><br><br clea=
r=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>Office of Information Technology<br>Un=
iversity of Minnesota=C2=A0=C2=A0 <br>2218 University Ave SE=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 Phone: 612-626-0815<br>Minneapolis, 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>

--001a11440008dc8d710551603fcb--


From nobody Wed Jun  7 08:30:10 2017
Return-Path: <prvs=2331e1a667=jonathan@vidyo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DCD4129521; Wed,  7 Jun 2017 08:30:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id goTmtq9BJp9d; Wed,  7 Jun 2017 08:29:58 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com [67.231.157.197]) (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 43EAB1294FD; Wed,  7 Jun 2017 08:29:58 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net [127.0.0.1]) by mx0b-00198e01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v57FT7W1001996; Wed, 7 Jun 2017 11:29:50 -0400
Received: from mail.vidyo.com (mail2.vidyo.com [162.209.16.214]) by mx0b-00198e01.pphosted.com with ESMTP id 2auqv5jd2d-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Wed, 07 Jun 2017 11:29:50 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Wed, 7 Jun 2017 10:29:49 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Roni Even <roni.even@huawei.com>
CC: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>, General Area Review Team <gen-art@ietf.org>, "avtext@ietf.org" <avtext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMAgAAtEkCAAQCzAA==
Date: Wed, 7 Jun 2017 15:29:49 +0000
Message-ID: <B9294064-4F4E-4FA1-A864-4F9790767B5C@vidyo.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B49CF8FA1513A14C8451222191EA2BF1@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-07_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706070285
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6_qnR5VMSxqO3a62jwbuLkJjX-4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Jun 2017 15:30:04 -0000

DQo+IE9uIEp1biA3LCAyMDE3LCBhdCAxOjE1IEFNLCBSb25pIEV2ZW4gPHJvbmkuZXZlbkBodWF3
ZWkuY29tPiB3cm90ZToNCj4gDQo+IEhpIEpvbmF0aGFuLA0KPiBJIGRpZCBub3Qgc2VlIHRoZSB0
ZXh0IHlvdSBhZGRlZCB5ZXQgYXMgYSByZXNwb25zZSB0byBteSBmaXJzdCBxdWVzdGlvbg0KPiBT
byB0byBiZXR0ZXIgY2xhcmlmeSBteSBxdWVzdGlvbiAuIElmIHRoZSBGQ0kgaGFzIFRUSUQ9MCBh
bmQgVExJRD0yIC4gZG9lcyBpdCBtZWFuIHRoYXQgaXQgaXMgYSByZXF1ZXN0IHRvIHVwZGF0ZSBi
b3RoPw0KPiBUaGlzIHdhcyBhbHNvIHRoZSByZWFzb24gZm9yIHRoZSBxdWVzdGlvbiBhYm91dCBi
b3RoIFRUSUQ9MCBhbmQgVExJRD0wLCB3aGljaCBsYXllciBuZWVkIHVwZGF0ZSBvciBpcyBpdCBi
b3RoPw0KPiBDYW4geW91IHNheSB0aGF0IHlvdSB3YW50IGp1c3QgdG8gdXBkYXRlIHRlbXBvcmFs
IG9yIHNwYXRpYWw/DQoNClllcywgaWYgdGhlIEZDSSBoYXMgVFRJRD0wIGFuZCBUTElEPTIsIGl0
4oCZcyBhIHJlcXVlc3QgdG8gdXBkYXRlIGJvdGggbGF5ZXJzIOKAlCBvciBtb3JlIHNwZWNpZmlj
YWxseSwgdG8gbWFrZSBzdXJlIHRoYXQgeW91IGNhbiBzdGFydCBkZWNvZGluZyB0aGUgc3Vic3Ry
ZWFtIHdpdGggVFRJRD0wIGFuZCBUTElEPTIuIChGb3IgbW9zdCBzY2FsYWJpbGl0eSBzdHJ1Y3R1
cmVzIHRoaXMgd291bGQgbWVhbiB1cGRhdGluZyBib3RoLCBidXQgZXhvdGljIHN0cnVjdHVyZXMg
YXJlIHBvc3NpYmxlLikNCg0KSWYgeW91IHdhbnQgdG8ganVzdCB1cGRhdGUgb25lIHBhcnQgb2Yg
dGhlIHN0cmVhbSwgdGhhdOKAmXMgd2hhdCBDVElEIGFuZCBDTElEIGFyZSBmb3IuICBJZiB5b3Ug
c2VudCBUVElEPTAgYW5kIFRMSUQ9MiwgYWNjb21wYW5pZWQgYnkgQ1RJRD0wIGFuZCBDTElEPTAs
IHRoYXQgbWVhbnMgdGhhdCB5b3UgYWxyZWFkeSBoYXZlIFRJRCAwLCBhbmQgeW91IGp1c3Qgd2Fu
dCB0byBpbmNyZWFzZSB0aGUgTElELg0KDQpUaGUgY3VycmVudCB0ZXh0IGlzIGF0IGh0dHBzOi8v
Z2l0aHViLmNvbS9qdWJlcnRpL2RyYXVnaHRzL3RyZWUvbWFzdGVyL2xyciAsIGlmIHlvdSB3YW50
IHRvIHRha2UgYSBsb29rIGF0IHRoZSBsYXRlc3QgcmV2aXNpb25zLCBvciBzdWdnZXN0IHRleHQg
dGhhdCB5b3UgdGhpbmsgd291bGQgbWFrZSBpdCBjbGVhbmVyLg0KDQoNCj4gUm9uaQ0KPiANCj4+
IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+PiBGcm9tOiBHZW4tYXJ0IFttYWlsdG86Z2Vu
LWFydC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSm9uYXRoYW4NCj4+IExlbm5veA0K
Pj4gU2VudDog15nXldedINeTIDA3INeZ15XXoNeZIDIwMTcgMDA6MzANCj4+IFRvOiBSb25pIEV2
ZW4NCj4+IENjOiBkcmFmdC1pZXRmLWF2dGV4dC1scnIuYWxsQGlldGYub3JnOyBHZW5lcmFsIEFy
ZWEgUmV2aWV3IFRlYW07DQo+PiBhdnRleHRAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj4+IFN1
YmplY3Q6IFJlOiBbR2VuLWFydF0gR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0
Zi1hdnRleHQtbHJyLTA1DQo+PiANCj4+IEhpLCBSb25pIOKAlCB0aGFua3MgZm9yIHlvdXIgcmV2
aWV3LiAgUmVzcG9uc2VzIGlubGluZS4NCj4+IA0KPj4+IE9uIEp1biAxLCAyMDE3LCBhdCAyOjUz
IEFNLCBSb25pIEV2ZW4gPHJvbi5ldmVuLnRsdkBnbWFpbC5jb20+IHdyb3RlOg0KPj4+IA0KPj4+
IFJldmlld2VyOiBSb25pIEV2ZW4NCj4+PiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vl
cw0KPj4+IA0KPj4+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9yIHRoaXMg
ZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENCj4+PiBSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2aWV3
cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5DQo+Pj4gdGhlIElFU0cgZm9y
IHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZQ0K
Pj4+IGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+Pj4gDQo+Pj4gRm9yIG1vcmUgaW5m
b3JtYXRpb24sIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPj4+IA0KPj4+IDxodHRwczovL3RyYWMu
aWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KPj4+IA0KPj4+IERvY3VtZW50OiBk
cmFmdC1pZXRmLWF2dGV4dC1scnItPz8NCj4+PiBSZXZpZXdlcjogUm9uaSBFdmVuDQo+Pj4gUmV2
aWV3IERhdGU6IDIwMTctMDUtMzENCj4+PiBJRVRGIExDIEVuZCBEYXRlOiAyMDE3LTA2LTA4DQo+
Pj4gSUVTRyBUZWxlY2hhdCBkYXRlOiBOb3Qgc2NoZWR1bGVkIGZvciBhIHRlbGVjaGF0DQo+Pj4g
DQo+Pj4gU3VtbWFyeToNCj4+PiBUaGUgZG9jdW1lbnQgaXMgcmVhZHkgd2l0aCBpc3N1ZXMgZm9y
IGEgc3RhbmRhcmQgdHJhY2sgUkZDIE1ham9yDQo+Pj4gaXNzdWVzOg0KPj4+IA0KPj4+IE1pbm9y
IGlzc3VlczoNCj4+PiANCj4+PiAxLiBDYW4geW91IHNwZWNpZnkgYm90aCBUVElEIGFuZCBUTElE
IGluIHRoZSBzYW1lIEZDSS4NCj4+IA0KPj4gU3ludGFjdGljYWxseSwgdGhleSBtdXN0IGJvdGgg
b2NjdXIuDQo+PiANCj4+IElmIHlvdSBtZWFuIGNhbiB5b3UgcmVxdWVzdCBhbiB1cGdyYWRlIGlu
IGJvdGggYXQgb25jZSwgeWVzOyBJ4oCZdmUgYWRkZWQgdGV4dA0KPj4gdG8gY2xhcmlmeSB0aGlz
Lg0KPj4gDQo+Pj4gMi4gV2hhdCBpcyB0aGUgbWVhbmluZyBvZiB2YWx1ZSAwIGZvciBUVElEIGFu
ZCBUTElEIC0gVElEIG9yIExJRCA9MCBpbg0KPj4+IGZyYW1lIG1hcmtpbmcgZHJhZnQgbWVhbnMg
YmFzZSBsYXllciBpZiB0aGVyZSBpcyBzY2FsYWJpbGl0eS4NCj4+PiAgICBUaGlzIHJlbGF0ZXMg
dG8gdGhlIHByZXZpb3VzIHF1ZXN0aW9uLg0KPj4gDQo+PiBJ4oCZbSBub3Qgc3VyZSBJIHVuZGVy
c3RhbmQgdGhpcyBxdWVzdGlvbi4NCj4+IA0KPj4gSeKAmXZlIGFkZGVkIHRleHQgdGhhdCBpZiBD
PTEsIGF0IGxlYXN0IG9uZSBvZiA8VFRJRCwgVExJRD4gTVVTVCBiZSBncmVhdGVyIHRoYW4NCj4+
IDxDVElELCBDTElEPiwgYW5kIGJvdGggTVVTVCBiZSBncmVhdGVyIHRoYW4gb3IgZXF1YWwgdG8g
dGhlaXIgY291bnRlcnBhcnQsDQo+PiBzbyB0aGUgTFJSIGlzIGFjdHVhbGx5IHJlcXVlc3Rpbmcg
YSBsYXllciB1cGdyYWRlLiAgSXMgdGhhdCB3aGF0IHlvdSB3ZXJlDQo+PiBhc2tpbmcgYWJvdXQ/
DQo+PiANCj4+PiAzLiAgV2hhdCB3b3VsZCBhbiBGQ0kgd2l0aCBib3RoIFRUSUQgYW5kIFRMSUQg
ZXF1YWwgMCBtZWFuLg0KPj4gDQo+PiBJdCBtZWFucyB5b3Ugd2FudCBhIHJlZnJlc2ggb2YgdGhl
IGJhc2UgdGVtcG9yYWwvc3BhdGlhbCBsYXllciwgb25seS4NCj4+IA0KPj4+IE5pdHMvZWRpdG9y
aWFsIGNvbW1lbnRzOg0KPj4+IA0KPj4+IDEuIFNlY3Rpb24gMyAiYW4gUmVhbC1UaW1lIFRyYW5z
cG9ydCBDb250cm9sIFByb3RvY29sIiBzaG91bGQgYmUgImENCj4+PiBSZWFs4oCmIi4NCj4+IA0K
Pj4gQ29saW4gcG9pbnRlZCBvdXQgdGhhdCBpdCBzaG91bGQgc2F5IOKAnGFuIFJUUCBDb250cm9s
IFByb3RvY29s4oCdIGFueXdheS4NCj4+IA0KPj4+IDIuIEluIHNlY3Rpb24gMyAiIFtSRkM1MTA0
XShTZWN0aW9uIDMuNS4xKSIgdGhlcmUgaXMgYSBsaW5rIHRvIHNlY3Rpb24NCj4+PiAzLjUuMSBi
dXQgaXQgZG9lcyBub3Qgd29yay4NCj4+IA0KPj4geG1sMnJmYyBkb2VzbuKAmXQgaGF2ZSBhbnkg
d2F5IHRvIGxpbmsgdG8gc2VjdGlvbnMgb2Ygb3RoZXIgZG9jdW1lbnRzLCBzbyB0aGUNCj4+IOKA
nChTZWN0aW9uIDMuNS4xKeKAnSBwYXJ0IGlzIGp1c3QgYSBjb21tZW50Lg0KPj4gDQo+PiBJIHRo
aW5rIHRoZSBpbnRlcm5ldC1kcmFmdCB0b29saW5nIG1heSBoYXZlIHRob3VnaHQgSSB3YXMgdHJ5
aW5nIHRvIGxpbmsgdG8gYQ0KPj4gbm9uLWV4aXN0ZW50IHNlY3Rpb24gMy41LjEgb2YgdGhpcyBk
b2N1bWVudCwgYnV0IHRoYXTigJlzIG91dHNpZGUgbXkgY29udHJvbC4NCj4+IA0KPj4+IDMuIElu
IHNlY3Rpb24gMy4yICIoc2VlIHNlY3Rpb24gU2VjdGlvbiAyLjEpIiBzZWN0aW9uIGFwcGVhcnMg
dHdpY2UuDQo+PiANCj4+IEZpeGVkLg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX18NCj4+IEdlbi1hcnQgbWFpbGluZyBsaXN0DQo+PiBHZW4tYXJ0QGll
dGYub3JnDQo+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dlbi1hcnQN
Cg0K


From nobody Wed Jun  7 08:33:05 2017
Return-Path: <prvs=2331e1a667=jonathan@vidyo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A5439129521; Wed,  7 Jun 2017 08:32:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bkJtbIYnNgfn; Wed,  7 Jun 2017 08:32:55 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0a-00198e01.pphosted.com [67.231.149.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 9909612ECA5; Wed,  7 Jun 2017 08:32:55 -0700 (PDT)
Received: from pps.filterd (m0073109.ppops.net [127.0.0.1]) by mx0a-00198e01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v57FTViQ024410; Wed, 7 Jun 2017 11:32:49 -0400
Received: from mail.vidyo.com (mail2.vidyo.com [162.209.16.214]) by mx0a-00198e01.pphosted.com with ESMTP id 2aup7jafst-2 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Wed, 07 Jun 2017 11:32:48 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Wed, 7 Jun 2017 10:32:47 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Roni Even <roni.even@huawei.com>
CC: Roni Even <ron.even.tlv@gmail.com>, "avtext@ietf.org" <avtext@ietf.org>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMAgAAtEkCAACiLwIAA2PuA
Date: Wed, 7 Jun 2017 15:32:46 +0000
Message-ID: <E940011C-3C97-40D8-942F-94A0F9F4E6AE@vidyo.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF80@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD7CFF80@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <CB91567F328BBC4A970647E9B5D869DD@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-07_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706070285
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/srV6YZaW6jcknymEC8Sf_RWoPTo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 15:32:57 -0000

SXTigJlzIG5vdCBhIHNwZWNpYWwgbWVhbmluZyDigJQgdGhpcyB3b3VsZCBtZWFuIGEgcmVxdWVz
dCB0byBicmVhayB0aGUgZGVwZW5kZW5jeSBjaGFpbiBmb3IgdGhlIGJhc2UgdGVtcG9yYWwgYW5k
IHNwYXRpYWwgbGF5ZXIsIHdoaWxlIGFsbG93aW5nIGhpZ2hlciBsYXllcnMgdG8gY29udGludWUg
dXNpbmcgcmVmZXJlbmNlIHBpY3R1cmVzIGFjcm9zcyB0aGlzIGJyZWFrLiAgRmlndXJlIDIgaXMg
YSByb3VnaCBhcHByb3hpbWF0aW9uIG9mIHdoYXTigJlzIGRlc2lyZWQsIGlmIHlvdSBpbWFnaW5l
IGl0IGZvciB0ZW1wb3JhbCBhbmQgc3BhdGlhbCBzaW11bHRhbmVvdXNseS4NCg0KDQo+IE9uIEp1
biA3LCAyMDE3LCBhdCAzOjM4IEFNLCBSb25pIEV2ZW4gPHJvbmkuZXZlbkBodWF3ZWkuY29tPiB3
cm90ZToNCj4gDQo+IEhpIEpvbmF0aGFuLA0KPiBKdXN0IGFub3RoZXIgY2xhcmlmaWNhdGlvbiBm
b3IgYm90aCBUVElEPTAgYW5kIFRMSUQ9MCAsIEkgdW5kZXJzdGFuZCB0aGF0IHRoZXJlIGlzIG9u
ZSBiYXNlIGxheWVyLCBidXQgZG9lcyB0aGlzIGNhc2UgaGF2ZSBhbnkgc3BlY2lhbCBtZWFuaW5n
Pw0KPiBSb25pDQo+IA0KPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+IEZyb206IEdl
bi1hcnQgW21haWx0bzpnZW4tYXJ0LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBSb25p
IEV2ZW4NCj4+IFNlbnQ6INeZ15XXnSDXkyAwNyDXmdeV16DXmSAyMDE3IDA4OjE2DQo+PiBUbzog
Sm9uYXRoYW4gTGVubm94OyBSb25pIEV2ZW4NCj4+IENjOiBhdnRleHRAaWV0Zi5vcmc7IEdlbmVy
YWwgQXJlYSBSZXZpZXcgVGVhbTsgZHJhZnQtaWV0Zi1hdnRleHQtDQo+PiBscnIuYWxsQGlldGYu
b3JnOyBpZXRmQGlldGYub3JnDQo+PiBTdWJqZWN0OiBSZTogW0dlbi1hcnRdIEdlbmFydCBsYXN0
IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci0wNQ0KPj4gDQo+PiBIaSBKb25h
dGhhbiwNCj4+IEkgZGlkIG5vdCBzZWUgdGhlIHRleHQgeW91IGFkZGVkIHlldCBhcyBhIHJlc3Bv
bnNlIHRvIG15IGZpcnN0IHF1ZXN0aW9uIFNvIHRvDQo+PiBiZXR0ZXIgY2xhcmlmeSBteSBxdWVz
dGlvbiAuIElmIHRoZSBGQ0kgaGFzIFRUSUQ9MCBhbmQgVExJRD0yIC4gZG9lcyBpdCBtZWFuDQo+
PiB0aGF0IGl0IGlzIGEgcmVxdWVzdCB0byB1cGRhdGUgYm90aD8NCj4+IFRoaXMgd2FzIGFsc28g
dGhlIHJlYXNvbiBmb3IgdGhlIHF1ZXN0aW9uIGFib3V0IGJvdGggVFRJRD0wIGFuZCBUTElEPTAs
DQo+PiB3aGljaCBsYXllciBuZWVkIHVwZGF0ZSBvciBpcyBpdCBib3RoPw0KPj4gQ2FuIHlvdSBz
YXkgdGhhdCB5b3Ugd2FudCBqdXN0IHRvIHVwZGF0ZSB0ZW1wb3JhbCBvciBzcGF0aWFsPw0KPj4g
DQo+PiBSb25pDQo+PiANCj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4+IEZyb206
IEdlbi1hcnQgW21haWx0bzpnZW4tYXJ0LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBK
b25hdGhhbg0KPj4+IExlbm5veA0KPj4+IFNlbnQ6INeZ15XXnSDXkyAwNyDXmdeV16DXmSAyMDE3
IDAwOjMwDQo+Pj4gVG86IFJvbmkgRXZlbg0KPj4+IENjOiBkcmFmdC1pZXRmLWF2dGV4dC1scnIu
YWxsQGlldGYub3JnOyBHZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW07DQo+Pj4gYXZ0ZXh0QGlldGYu
b3JnOyBpZXRmQGlldGYub3JnDQo+Pj4gU3ViamVjdDogUmU6IFtHZW4tYXJ0XSBHZW5hcnQgbGFz
dCBjYWxsIHJldmlldyBvZg0KPj4+IGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci0wNQ0KPj4+IA0KPj4+
IEhpLCBSb25pIOKAlCB0aGFua3MgZm9yIHlvdXIgcmV2aWV3LiAgUmVzcG9uc2VzIGlubGluZS4N
Cj4+PiANCj4+Pj4gT24gSnVuIDEsIDIwMTcsIGF0IDI6NTMgQU0sIFJvbmkgRXZlbiA8cm9uLmV2
ZW4udGx2QGdtYWlsLmNvbT4gd3JvdGU6DQo+Pj4+IA0KPj4+PiBSZXZpZXdlcjogUm9uaSBFdmVu
DQo+Pj4+IFJldmlldyByZXN1bHQ6IFJlYWR5IHdpdGggSXNzdWVzDQo+Pj4+IA0KPj4+PiBJIGFt
IHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJh
bCBBcmVhDQo+Pj4+IFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3Vt
ZW50cyBiZWluZyBwcm9jZXNzZWQgYnkNCj4+Pj4gdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWly
LiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZQ0KPj4+PiBhbnkgb3RoZXIg
bGFzdCBjYWxsIGNvbW1lbnRzLg0KPj4+PiANCj4+Pj4gRm9yIG1vcmUgaW5mb3JtYXRpb24sIHBs
ZWFzZSBzZWUgdGhlIEZBUSBhdA0KPj4+PiANCj4+Pj4gPGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90
cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQo+Pj4+IA0KPj4+PiBEb2N1bWVudDogZHJhZnQtaWV0
Zi1hdnRleHQtbHJyLT8/DQo+Pj4+IFJldmlld2VyOiBSb25pIEV2ZW4NCj4+Pj4gUmV2aWV3IERh
dGU6IDIwMTctMDUtMzENCj4+Pj4gSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wNi0wOA0KPj4+PiBJ
RVNHIFRlbGVjaGF0IGRhdGU6IE5vdCBzY2hlZHVsZWQgZm9yIGEgdGVsZWNoYXQNCj4+Pj4gDQo+
Pj4+IFN1bW1hcnk6DQo+Pj4+IFRoZSBkb2N1bWVudCBpcyByZWFkeSB3aXRoIGlzc3VlcyBmb3Ig
YSBzdGFuZGFyZCB0cmFjayBSRkMgTWFqb3INCj4+Pj4gaXNzdWVzOg0KPj4+PiANCj4+Pj4gTWlu
b3IgaXNzdWVzOg0KPj4+PiANCj4+Pj4gMS4gQ2FuIHlvdSBzcGVjaWZ5IGJvdGggVFRJRCBhbmQg
VExJRCBpbiB0aGUgc2FtZSBGQ0kuDQo+Pj4gDQo+Pj4gU3ludGFjdGljYWxseSwgdGhleSBtdXN0
IGJvdGggb2NjdXIuDQo+Pj4gDQo+Pj4gSWYgeW91IG1lYW4gY2FuIHlvdSByZXF1ZXN0IGFuIHVw
Z3JhZGUgaW4gYm90aCBhdCBvbmNlLCB5ZXM7IEnigJl2ZQ0KPj4+IGFkZGVkIHRleHQgdG8gY2xh
cmlmeSB0aGlzLg0KPj4+IA0KPj4+PiAyLiBXaGF0IGlzIHRoZSBtZWFuaW5nIG9mIHZhbHVlIDAg
Zm9yIFRUSUQgYW5kIFRMSUQgLSBUSUQgb3IgTElEID0wDQo+Pj4+IGluIGZyYW1lIG1hcmtpbmcg
ZHJhZnQgbWVhbnMgYmFzZSBsYXllciBpZiB0aGVyZSBpcyBzY2FsYWJpbGl0eS4NCj4+Pj4gICAg
VGhpcyByZWxhdGVzIHRvIHRoZSBwcmV2aW91cyBxdWVzdGlvbi4NCj4+PiANCj4+PiBJ4oCZbSBu
b3Qgc3VyZSBJIHVuZGVyc3RhbmQgdGhpcyBxdWVzdGlvbi4NCj4+PiANCj4+PiBJ4oCZdmUgYWRk
ZWQgdGV4dCB0aGF0IGlmIEM9MSwgYXQgbGVhc3Qgb25lIG9mIDxUVElELCBUTElEPiBNVVNUIGJl
DQo+Pj4gZ3JlYXRlciB0aGFuIDxDVElELCBDTElEPiwgYW5kIGJvdGggTVVTVCBiZSBncmVhdGVy
IHRoYW4gb3IgZXF1YWwgdG8NCj4+PiB0aGVpciBjb3VudGVycGFydCwgc28gdGhlIExSUiBpcyBh
Y3R1YWxseSByZXF1ZXN0aW5nIGEgbGF5ZXIgdXBncmFkZS4NCj4+PiBJcyB0aGF0IHdoYXQgeW91
IHdlcmUgYXNraW5nIGFib3V0Pw0KPj4+IA0KPj4+PiAzLiAgV2hhdCB3b3VsZCBhbiBGQ0kgd2l0
aCBib3RoIFRUSUQgYW5kIFRMSUQgZXF1YWwgMCBtZWFuLg0KPj4+IA0KPj4+IEl0IG1lYW5zIHlv
dSB3YW50IGEgcmVmcmVzaCBvZiB0aGUgYmFzZSB0ZW1wb3JhbC9zcGF0aWFsIGxheWVyLCBvbmx5
Lg0KPj4+IA0KPj4+PiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4+Pj4gDQo+Pj4+IDEuIFNl
Y3Rpb24gMyAiYW4gUmVhbC1UaW1lIFRyYW5zcG9ydCBDb250cm9sIFByb3RvY29sIiBzaG91bGQg
YmUgImENCj4+Pj4gUmVhbOKApiIuDQo+Pj4gDQo+Pj4gQ29saW4gcG9pbnRlZCBvdXQgdGhhdCBp
dCBzaG91bGQgc2F5IOKAnGFuIFJUUCBDb250cm9sIFByb3RvY29s4oCdIGFueXdheS4NCj4+PiAN
Cj4+Pj4gMi4gSW4gc2VjdGlvbiAzICIgW1JGQzUxMDRdKFNlY3Rpb24gMy41LjEpIiB0aGVyZSBp
cyBhIGxpbmsgdG8NCj4+Pj4gc2VjdGlvbg0KPj4+PiAzLjUuMSBidXQgaXQgZG9lcyBub3Qgd29y
ay4NCj4+PiANCj4+PiB4bWwycmZjIGRvZXNu4oCZdCBoYXZlIGFueSB3YXkgdG8gbGluayB0byBz
ZWN0aW9ucyBvZiBvdGhlciBkb2N1bWVudHMsDQo+Pj4gc28gdGhlIOKAnChTZWN0aW9uIDMuNS4x
KeKAnSBwYXJ0IGlzIGp1c3QgYSBjb21tZW50Lg0KPj4+IA0KPj4+IEkgdGhpbmsgdGhlIGludGVy
bmV0LWRyYWZ0IHRvb2xpbmcgbWF5IGhhdmUgdGhvdWdodCBJIHdhcyB0cnlpbmcgdG8NCj4+PiBs
aW5rIHRvIGEgbm9uLWV4aXN0ZW50IHNlY3Rpb24gMy41LjEgb2YgdGhpcyBkb2N1bWVudCwgYnV0
IHRoYXTigJlzIG91dHNpZGUgbXkNCj4+IGNvbnRyb2wuDQo+Pj4gDQo+Pj4+IDMuIEluIHNlY3Rp
b24gMy4yICIoc2VlIHNlY3Rpb24gU2VjdGlvbiAyLjEpIiBzZWN0aW9uIGFwcGVhcnMgdHdpY2Uu
DQo+Pj4gDQo+Pj4gRml4ZWQuDQo+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCj4+PiBHZW4tYXJ0IG1haWxpbmcgbGlzdA0KPj4+IEdlbi1hcnRAaWV0
Zi5vcmcNCj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dlbi1hcnQN
Cj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+PiBH
ZW4tYXJ0IG1haWxpbmcgbGlzdA0KPj4gR2VuLWFydEBpZXRmLm9yZw0KPj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9nZW4tYXJ0DQoNCg==


From nobody Wed Jun  7 08:33:45 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6084D12ECC2 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 08:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level: 
X-Spam-Status: No, score=-4.299 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, RCVD_IN_SORBS_SPAM=0.5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M_L88ffsRWA8 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 08:33:28 -0700 (PDT)
Received: from homiemail-a108.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 6E2FD12ECC5 for <ietf@ietf.org>; Wed,  7 Jun 2017 08:33:19 -0700 (PDT)
Received: from homiemail-a108.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a108.g.dreamhost.com (Postfix) with ESMTP id 2256B20047315; Wed,  7 Jun 2017 08:33:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=XcBNljGFwTyymg mPaOHFEf0ISW8=; b=uQtPX+e7gSAwBmcpMfugGdQWqlvXoNHL4H6UKwRB7XiOTs wtlPFViO5/Kmo3FtcSEPl9OKxENq2Fof7Q9jFQH/C6AcVhBtyhnSAjbvr2Vg/GvM 3mWQ+JG7KynuSc3y7O5yrUVRZStAbYwUgRN789j1OZ2OYwKpaS1En+siYJ8RY=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a108.g.dreamhost.com (Postfix) with ESMTPSA id C3B9820047310; Wed,  7 Jun 2017 08:33:18 -0700 (PDT)
Date: Wed, 7 Jun 2017 10:33:16 -0500
From: Nico Williams <nico@cryptonector.com>
To: David Farmer <farmer@umn.edu>
Cc: Christian Huitema <huitema@huitema.net>, IETF-Discussion Discussion <ietf@ietf.org>
Subject: Re: wireless geolocation
Message-ID: <20170607153314.GG3432@localhost>
References: <m27f0pqgbc.wl-randy@psg.com> <3e926ca5-36ed-2274-f1ce-77830a359995@huitema.net> <20170607150110.GF3432@localhost> <CAN-Dau3frXb0B8xR1tZ8JJbXknVLoHVADMVrsuNp6=2DbUpJ0A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAN-Dau3frXb0B8xR1tZ8JJbXknVLoHVADMVrsuNp6=2DbUpJ0A@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jJR5JR3ZwUp3ZjnuBqsn04YFAas>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 15:33:29 -0000

On Wed, Jun 07, 2017 at 10:18:33AM -0500, David Farmer wrote:
> On Wed, Jun 7, 2017 at 10:01 AM, Nico Williams <nico@cryptonector.com>
> wrote:
> > On Wed, Jun 07, 2017 at 09:23:13AM +0200, Christian Huitema wrote:
> > > Another argument for MAC Address randomization...
> >
> > +1
> >
> > Though that's likely to lead geoloc providers to use other methods over
> > which we'd have even less control.  But still, MAC address randomization
> > is a good thing all around.
> 
> How would Client MAC address randomization help this situation? I not aware
> of APs implementing MAC address (BSSID) randomization.

Neither Christian nor I said "client".  We're arguing that all MAC
addresses should be randomized.  As for BSSIDs, I'm not sure randomizing
them on boot is a good idea, but certainly on install/reset.

Nico
-- 


From nobody Wed Jun  7 08:33:50 2017
Return-Path: <prvs=324e79c2b=theodore.v.faber@aero.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1F7F12ECB9 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 08:33:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=aero.org header.b=lGSLqfo7; dkim=pass (1024-bit key) header.d=aerospacecloud.onmicrosoft.com header.b=KnEkYpb4
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aMmu9mdJKmOC for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 08:33:29 -0700 (PDT)
Received: from email6-west.aero.org (email6-west.aero.org [130.221.16.31]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 837E1129521 for <ietf@ietf.org>; Wed,  7 Jun 2017 08:33:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=aero.org; i=@aero.org; q=dns/txt; s=mailhub; t=1496849600; x=1528385600; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=MVal8/7BNdfLA7nh0sQGDvuNokxGs7uBByo+OD9kPIg=; b=lGSLqfo7szt1yxe/bTjubrrZRH3JtSKvzzQ+OXnsamHz+bqQPJSXIdEv 44EzhV1a3vSlZUgzPEtSl3ig2lBw84AXNGUZhSPh16Tqd4HVRTTQkFrnw uQZNuTKBOlO/XgjN5DnLMJ+xn9tjVBTeahaEU7cwU+m9qu7gKSaAQV7nK o=;
x-SBRS: 3.5
x-SenderGroup: Inbound_Office365
X-IronPort-AV: E=McAfee;i="5800,7501,8553"; a="842762"
X-IronPort-AV: E=Sophos;i="5.39,311,1493708400";  d="scan'208";a="842762"
X-IPAS-Result: =?us-ascii?q?A2EZAAC1GzhZhxDGZxdbAxwBAQQBAQoBAYNVZYENB44Ec5B?= =?us-ascii?q?1iCqNVoExBVoshXgCgzMYAQIBAQEBAQEBAxABAQEKCwkIKC+CZXIBAQEBAQEBA?= =?us-ascii?q?QEiKgItBzYBAQEBAgFAAQE3AQQLAgEIFTEhESUCBA4FCBKJeQMNCBCiQQKLBYM?= =?us-ascii?q?QgwkBAQWEMA0LhCcBAQEBAQEBAQEBAQEBAQEBAQEBAQEVAwWLYYJYghICHyaCe?= =?us-ascii?q?4IxAZBFOY0EO4cmhzWGS5ASi0KHaAGBPB+BQ1EwhUYfgXF2AYhEAYEMAQEB?=
Received: from mail-cy1gcc01lp0016.outbound.protection.outlook.com (HELO gcc01-CY1-obe.outbound.protection.outlook.com) ([23.103.198.16]) by email6-west.aero.org with ESMTP/TLS/AES256-SHA256; 07 Jun 2017 08:33:19 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aerospacecloud.onmicrosoft.com; s=selector1-aero-org; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=MVal8/7BNdfLA7nh0sQGDvuNokxGs7uBByo+OD9kPIg=; b=KnEkYpb4JXWwTgeAtlAKq5O/lKbzMRvLPS/dHF9hVUBhDGrLtyxAh1dzs91AEY7lmMkoXdEg+SbRo2Kdqu23GzMnpznSPr62pEUCh87LM4S3QV5ylzUE7GNTLFO44/Ha5splAK1iqPHVB4r+iLvvVmYMuf/6vsCSTiuOyMknlV4=
Received: from CY1PR09MB1147.namprd09.prod.outlook.com (10.166.196.27) by CY1PR09MB1147.namprd09.prod.outlook.com (10.166.196.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1157.12; Wed, 7 Jun 2017 15:33:17 +0000
Received: from CY1PR09MB1147.namprd09.prod.outlook.com ([10.166.196.27]) by CY1PR09MB1147.namprd09.prod.outlook.com ([10.166.196.27]) with mapi id 15.01.1157.012; Wed, 7 Jun 2017 15:33:17 +0000
From: Theodore V Faber <theodore.v.faber@aero.org>
To: Stewart Bryant <stewart.bryant@gmail.com>
CC: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
Thread-Topic: wireless geolocation
Thread-Index: AQHS3tq9JqFeixCQ+0qj+tuH0Q2rNqIYOpYAgAALBoCAABgzAIAAD5UAgAASgQCAAJEugIAAd5aE
Date: Wed, 7 Jun 2017 15:33:16 +0000
Message-ID: <CY1PR09MB11474DE1D33AE4EC9413BF52B9C80@CY1PR09MB1147.namprd09.prod.outlook.com>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost>, <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.com>
In-Reply-To: <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.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=aero.org;
x-originating-ip: [130.221.224.7]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR09MB1147; 7:Zo8v7ld4AEK0Iocc8EQUXfsQywulvZnk1KPY1crDjkKUUCRPMIoOpq6C6psGopmfV5akw3AMqmloymbctx6bL+wQlkSWoMD7k6f3QhPELaH2g4P5YyvzWVc023ZWnd2zQ+3IOUZSAw3H5Pm3W+O6ReKtjKGK0yB8EOYhadm4GPS9rq6gVwi9hfxS5LVTfiGuxSadcZCXNwAcYIzw9z2u2D6RvCLQo9XvaXGjZDMuZ3NBbhDiIT1MVvVGF0ZlEhfcscmS56eqHbJvhRzL2ord+Xur6nM9rg9o+ZhyNszfPNlILMAMkv/P0NE3bYXB4/d7XnmV8LKQRHrh5d2NRnw3Bg==
x-ms-traffictypediagnostic: CY1PR09MB1147:
x-ms-office365-filtering-correlation-id: dc545909-995a-4b8e-0b07-08d4adba84e7
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:CY1PR09MB1147; 
x-microsoft-antispam-prvs: <CY1PR09MB1147DE5423F984CFBB37F1A5B9C80@CY1PR09MB1147.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(100000703101)(100105400095)(3002001)(10201501046)(6055026)(6041248)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123560025)(20161123564025)(20161123562025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY1PR09MB1147; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY1PR09MB1147; 
x-forefront-prvs: 03319F6FEF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39860400002)(39410400002)(39450400003)(39840400002)(39400400002)(39850400002)(99286003)(55016002)(9686003)(7116003)(3660700001)(6246003)(189998001)(110136004)(38730400002)(7696004)(478600001)(966005)(6306002)(5660300001)(3280700002)(74316002)(6916009)(2950100002)(86362001)(305945005)(77096006)(39060400002)(3480700004)(6506006)(54356999)(50986999)(221733001)(76176999)(93886004)(53936002)(25786009)(229853002)(6436002)(122556002)(66066001)(7736002)(8676002)(8936002)(14454004)(6116002)(81166006)(33656002)(2906002)(102836003)(3846002)(2900100001)(4326008)(105384003)(111123002); DIR:OUT; SFP:1101; SCL:1; SRVR:CY1PR09MB1147; H:CY1PR09MB1147.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: aero.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Jun 2017 15:33:16.8436 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: c8294700-c5a4-4ca1-a876-1457d39899fd
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR09MB1147
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/d3jWiXWBBRW-rCTDEdA4d2rk6RY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 15:33:42 -0000

> From: ietf <ietf-bounces@ietf.org> on behalf of Stewart Bryant <stewart.b=
ryant@gmail.com>


> From an entirely personal perspective I would prefer that
>geolocation be irretrievable broken so that it could never
>work rather than fixed to work correctly.


I have good news for you, then: https://gimletmedia.com/episode/53-in-the-d=
esert/

--
Ted Faber <theodore.v.faber@aero.org>
Engineering Specialist
Computer Systems Research Department
The Aerospace Corporation
310-336-7373


From nobody Wed Jun  7 09:06:48 2017
Return-Path: <tytso@thunk.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 A00701293FF for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 09:06:47 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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=thunk.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iIWau-lXIYTz for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 09:06:45 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) (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 B2B72128B8E for <ietf@ietf.org>; Wed,  7 Jun 2017 09:06:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org;  s=ef5046eb;  h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=XsA9PdIj9g8yq7abINJVO4Bo1Zn9tomC8Jf6fEPLOh4=;  b=nWV65dahO1VDAl0U4OaPOnnBZcQYFWzuRg2F50yW+itiyabeX8FZ15efkLs6IkTLTEsIonMjWo67AUZ2kd5joQSvWEDStZ38ufnff7Qs3xSgsQE3IfwwbS9ipasLCMOrHBb/S1yDpbl/2eL1n9PsQCsHbrdgSXHDUSVIBXPxQaw=;
Received: from root (helo=callcc.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.84_2) (envelope-from <tytso@thunk.org>) id 1dIdTo-0002GM-0B; Wed, 07 Jun 2017 16:06:44 +0000
Received: by callcc.thunk.org (Postfix, from userid 15806) id D84F3C012E1; Wed,  7 Jun 2017 12:06:42 -0400 (EDT)
Date: Wed, 7 Jun 2017 12:06:42 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
Message-ID: <20170607160642.v6cu7ngbsw4cpg6p@thunk.org>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost> <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.com>
User-Agent: NeoMutt/20170113 (1.7.2)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/w7mZ5AVkYZKx9WuW9mj9PIVQxTI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 16:06:47 -0000

On Wed, Jun 07, 2017 at 09:23:51AM +0100, Stewart Bryant wrote:
> 
> From an entirely personal perspective I would prefer that
> geolocation be irretrievable broken so that it could never
> work rather than fixed to work correctly.

On many platforms you can turn off locaion services (such as those
that depend on sending which cell towers or WiFi AP's your phone can
see) off.  This is true for Android, IOS, and Windows 10.

     	   	   	    	     	  - Ted


From nobody Wed Jun  7 09:37:03 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A5281300CF for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 09:37: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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZnS_WcisnAJq for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 09:36:59 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3FAB912F5DB for <ietf@ietf.org>; Wed,  7 Jun 2017 09:36:59 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id w1so12189458qtg.2 for <ietf@ietf.org>; Wed, 07 Jun 2017 09:36:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=MGjnK1wh6UIcFz5zR1h5MBJmIuKdmw0ncsHMaXjXIGY=; b=WzWswmX487Gz+J2uxadrhohApcDglAHk6Y6V4oLxgWseTiX6WWmBzjDEorFcyBlani MfRjGZtL0eSkBc0kWyPA7IOIGpWfAuj/0zEeap1DmwX2qTGY+lyTjIZrcRPrYJ2ypu4e bQC1X+cdnLmLhbTtG7SlbYn+UQdF/hsieiHimB8DIETFVLXio+hWArHLI//VN/51NFYG 3VFkcN00hnPoptYegVm1n2NE4N4FMXCs/Zzy3L0ugB6HYY+A94bfYhpa8U1RMzcjLnzQ o/CSJVfql9FyYKmjVCMoTqDhX8m+zl/re2HLMCSNWV6IlEoC9mAkcT/eBW4J/Jf2pPwk 2XUA==
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=MGjnK1wh6UIcFz5zR1h5MBJmIuKdmw0ncsHMaXjXIGY=; b=VvYjhluXczgwAqeWPKfJgT1O7qSYoHkdU5Mq1GdkF78ljtRUWt31sS7ur+PmCNLf+a +0ndFA4A9IiYFSzjf/LpT5rCSGhRilpaWXs+yebp6C3X5qI7vssx5KTT2k424hyu+bre hZ37o3lGZnbwxREPvUye8IvpQDW22/qXGSzk+a330e4bxux91D1tJhb7mX7Xd2bK7I4a DfS2N/US/ioM34XBQB4ZuMIcWfYGoFRUxrVbIRRndxwd7nptukYf6gAsM8WxKHdhZesF AooEpgm9XJiDo4EY8HpzTea8K1/th3o6vsB+ZqsDeHwYHURj9OcHJLQ4D0CfZEXJkR4+ tfNA==
X-Gm-Message-State: AKS2vOy6T7R9OFBbDrBbbS4rle0BBfnlb1pno7pAfttlKnjJbACylEaz 98Epov8RpoD8yUEM
X-Received: by 10.55.18.218 with SMTP id 87mr38016642qks.202.1496853418421; Wed, 07 Jun 2017 09:36:58 -0700 (PDT)
Received: from [10.0.30.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id h38sm1337180qth.41.2017.06.07.09.36.57 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Jun 2017 09:36:57 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <4773EE0B-22D2-42F2-B8F3-463B1956B68B@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_A2726FE3-3EC8-40F6-BF9C-5BAAAB75BC06"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: wireless geolocation
Date: Wed, 7 Jun 2017 12:36:56 -0400
In-Reply-To: <20170607160642.v6cu7ngbsw4cpg6p@thunk.org>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, IETF Rinse Repeat <ietf@ietf.org>
To: Theodore Ts'o <tytso@mit.edu>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost> <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.com> <20170607160642.v6cu7ngbsw4cpg6p@thunk.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r6sPSLGXOJyY-9VAhzXS7QdXXoM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 16:37:01 -0000

--Apple-Mail=_A2726FE3-3EC8-40F6-BF9C-5BAAAB75BC06
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 7, 2017, at 12:06 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> On many platforms you can turn off locaion services (such as those
> that depend on sending which cell towers or WiFi AP's your phone can
> see) off.  This is true for Android, IOS, and Windows 10.

Unfortunately there is typically no way to turn off just the location =
service that's broken.   Also, web sites guess your location regardless =
of whether you have location services enabled: it only takes one person =
with a phone that's reporting the BSSID of its AP to something that does =
geolocation to leak it.   So asking people to shut this off on the =
client isn't going to improve the UX problem for anyone, unfortunately.


--Apple-Mail=_A2726FE3-3EC8-40F6-BF9C-5BAAAB75BC06
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jun 7, 2017, at 12:06 PM, Theodore Ts'o &lt;<a =
href=3D"mailto:tytso@mit.edu" class=3D"">tytso@mit.edu</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">On many platforms =
you can turn off locaion services (such as those</span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">that depend on sending which cell towers or WiFi =
AP's your phone can</span><br style=3D"font-family: Menlo-Regular; =
font-size: 18px; font-style: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">see) off. =
&nbsp;This is true for Android, IOS, and Windows =
10.</span></div></blockquote></div><br class=3D""><div =
class=3D"">Unfortunately there is typically no way to turn off just the =
location service that's broken. &nbsp; Also, web sites guess your =
location regardless of whether you have location services enabled: it =
only takes one person with a phone that's reporting the BSSID of its AP =
to something that does geolocation to leak it. &nbsp; So asking people =
to shut this off on the client isn't going to improve the UX problem for =
anyone, unfortunately.</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_A2726FE3-3EC8-40F6-BF9C-5BAAAB75BC06--


From nobody Wed Jun  7 09:58:49 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 020FC129489 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 09:58:47 -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_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, RCVD_IN_SORBS_SPAM=0.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cryptonector.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QDFgfMWgotn6 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 09:58:44 -0700 (PDT)
Received: from homiemail-a35.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 E056B12ECEB for <ietf@ietf.org>; Wed,  7 Jun 2017 09:58:43 -0700 (PDT)
Received: from homiemail-a35.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTP id DB33FC0028A9; Wed,  7 Jun 2017 09:58:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h=date :from:to:cc:subject:message-id:references:mime-version :content-type:in-reply-to; s=cryptonector.com; bh=KqYIy+SJ8Uf8fy jAfVPnmW5yfpo=; b=GHiTdzFCaQqv98H3sqvgaJDy0iqRLZ1QNgKFxORjxQ45BZ x7pjsGIX+hNc3j2G++E50e/HcVdO5d6cS+JtnMPwln1zEn6T05LogGwvGo+9bRFm TXif/UVWbnvpjSAeCMv4iHzKcQIixK1nITIl4FZTn8m7GY+UTyby2Bd77ziVU=
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a35.g.dreamhost.com (Postfix) with ESMTPSA id 7D0CBC0028A4; Wed,  7 Jun 2017 09:58:42 -0700 (PDT)
Date: Wed, 7 Jun 2017 11:58:39 -0500
From: Nico Williams <nico@cryptonector.com>
To: Ted Lemon <mellon@fugue.com>
Cc: Theodore Ts'o <tytso@mit.edu>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
Message-ID: <20170607165838.GH3432@localhost>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <m2o9u0pzd5.wl-randy@psg.com> <CAF4+nEETsJjjE=pH4xmUrmT4-weRRvKUfKtyThgt_s3wPFDFjg@mail.gmail.com> <20170606234413.GD3432@localhost> <e7322fdc-e794-55f1-1b67-3c4d5ef8c908@gmail.com> <20170607160642.v6cu7ngbsw4cpg6p@thunk.org> <4773EE0B-22D2-42F2-B8F3-463B1956B68B@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4773EE0B-22D2-42F2-B8F3-463B1956B68B@fugue.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/juC-TjLPlf4BXQcZD-1rRUbRQgQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 16:58:47 -0000

On Wed, Jun 07, 2017 at 12:36:56PM -0400, Ted Lemon wrote:
> On Jun 7, 2017, at 12:06 PM, Theodore Ts'o <tytso@mit.edu> wrote:
> > On many platforms you can turn off locaion services (such as those
> > that depend on sending which cell towers or WiFi AP's your phone can
> > see) off.  This is true for Android, IOS, and Windows 10.
> 
> Unfortunately there is typically no way to turn off just the location
> service that's broken.   Also, web sites guess your location
> regardless of whether you have location services enabled: it only
> takes one person with a phone that's reporting the BSSID of its AP to
> something that does geolocation to leak it.   So asking people to shut
> this off on the client isn't going to improve the UX problem for
> anyone, unfortunately.

Indeed.

This thread is ultimately caused by people wanting geoloc to at least
work correctly if it is used at all, not by people who prefer privacy.
Disabling location services on your devices will only make geoloc worse
for users who want geoloc to work.

If the gear allows it, just changes the BSSIDs and be done for now.

Maybe we need a WG to improve geoloc in general.  Though given some of
the issues described in this thread (e.g., geoloc providers not trusting
self-reported [by network providers] location information), I'm not sure
it can be done.  I'm OK with the idea that geoloc can't be improved.

Nico
-- 


From nobody Wed Jun  7 11:28:04 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7172B129AE3 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 11:28:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5HbHezjel8td for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 11:28:01 -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 BF6C2127866 for <ietf@ietf.org>; Wed,  7 Jun 2017 11:28:00 -0700 (PDT)
Received: (qmail 16145 invoked from network); 7 Jun 2017 18:27:59 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 7 Jun 2017 18:27:59 -0000
Date: 7 Jun 2017 18:27:37 -0000
Message-ID: <20170607182737.1395.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: adaptive wireless mis-geolocation
In-Reply-To: <CAPt1N1ni9Z12gfNArK4GaJpXdp2OMoZXv_wKrHYCcCG2wom=tw@mail.gmail.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3g61YTibi9u4XAv24WThveNjh6M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 18:28:02 -0000

In article <CAPt1N1ni9Z12gfNArK4GaJpXdp2OMoZXv_wKrHYCcCG2wom=tw@mail.gmail.com> you write:
>Because it makes it very difficult to use various services if they think we
>are 7000 miles away from where we are.

I find the benefits of a real non-NAT address vastly exceed the
inconvenience of some map application showing me a default view of the
city where I was three months ago.  

Also, I dunno about you, but for me it would be far more convenient to
be geolocated in the US for the week while I'm at a conference,
regardless of where I am physically, since that's where I live.  I
expect that's true for many people who live in other countries, too.

With that in mind, and understanding that the appropriate response to
"would someone do X" is "we're all volunteers here", it'd be cool to
permanently geolocate chunks of the IETF network to fixed countries,
then have a way to ask for an address in a country's chunk.  At IETF
98 the top ten countries were US, CN, CA, DE, JP, GB, FR, SE, NL, KR.

R's,
John


From nobody Wed Jun  7 11:31:37 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 916CF126C2F for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 11:31:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rUBCnFvaaje6 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 11:31:29 -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 F2B74129B2E for <ietf@ietf.org>; Wed,  7 Jun 2017 11:31:15 -0700 (PDT)
Received: (qmail 16435 invoked from network); 7 Jun 2017 18:31:15 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 7 Jun 2017 18:31:15 -0000
Date: 7 Jun 2017 18:30:53 -0000
Message-ID: <20170607183053.1423.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: tytso@mit.edu
Subject: Re: wireless geolocation
In-Reply-To: <20170606233106.yeyugzneqa4tjr44@thunk.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RRLRwXUZZFW63YAkGdZJdfZJLYo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 18:31:30 -0000

In article <20170606233106.yeyugzneqa4tjr44@thunk.org> you write:
>What really surprises me is that it should be relatively easy for
>these geolocation services to detect that BSSID/MAC's for the Access
>Points belong to conference / rental services. ...

>This doesn't seem hard....

You're making the unwarranted assumption that they care.  Remember how
hard it was to get Maxmind to stop sending a stream of angry people to
the farm that happened to be at the default location for unknown US
networks.

R's,
John


From nobody Wed Jun  7 11:50:31 2017
Return-Path: <fredbaker.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 84E57131464; Wed,  7 Jun 2017 11:50:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Fred Baker <fredbaker.ietf@gmail.com>
To: <ops-dir@ietf.org>
Cc: avtext@ietf.org, draft-ietf-avtext-lrr.all@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-avtext-lrr-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.53.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149686142937.2583.13332731633787220063@ietfa.amsl.com>
Date: Wed, 07 Jun 2017 11:50:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OPIGBvQBub-pxXHvlsiMUQfxFuU>
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, 07 Jun 2017 18:50:30 -0000

Reviewer: Fred Baker
Review result: Has Nits

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

My judgement: the document is ready.

Understand that my expertise is neither in codecs nor RTCP, and I have not
implemented the specification; there may be glaring issues in it from an
implementor's perspective for all I know. I'm looking at the issues a network
operator would face and need to deal with.

My biggest concern, from a network perspective, has to do with congestion. The
draft discusses congestion in passing, and calls for "consideration" of the
congestion issues and algorithms raised in RFC 5104. The word "consideration"
gives me some pause; Admiral Farragut famously "considered" a minefield between
his fleet and the harbor at Mobile Alabama, and gave the order "damn the
torpedoes, full speed ahead".  I'd hope for a stronger word there. Also, the
"consideration" in RFC 5104 is for congestion of the feedback path, but not the
forward data path (which, if it becomes congested by having too many layers
being sent, would reactively reduce its rate sometime later in response to loss
or delay in transit). I'm more concerned about the latter, as I suspect an
operator might be.

However, that ultimately comes down to capacity planning and rate negotiation
in SIP or whatever.

Ship it, Danno.

The authors replied, and we agreed on a text change. -06 should be "ready" from
my perspective.

Replace
  The sender MUST consider congestion control as outlined in section 5
  of [RFC5104], which MAY restrict its ability to send a layer refresh
  point quickly.

with

 The sender MUST respect bandwidth limits provided by the application of
 congestion control, as described in Section 5 of [RFC5104].  As layer refresh
 points will often be larger than non-refreshing frames, this may restrict a
 sender’s ability to send a layer refresh point quickly.

(Also fixing Ben Campbell’s comment that the MAY in this paragraph shouldn’t be
capitalized.)


From nobody Wed Jun  7 12:53:50 2017
Return-Path: <leifj@mnt.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 B3C0E129B38 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 12:53:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fOJaDN42vKn2 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 12:53:46 -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 59165124D37 for <ietf@ietf.org>; Wed,  7 Jun 2017 12:53:46 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id o83so9973267lff.3 for <ietf@ietf.org>; Wed, 07 Jun 2017 12:53:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=FUT7tb5nShqi4zpKQqq4hX+oiMEOVEgGwvIIRz2ht6Y=; b=gmaMDpD6gCkh/uYbgALMu90Yvxr9HDHtJncn0ZGuOo8Oke1twTMhGMi2Y1Gf64pvoj y9yKd+qZBttqYzReQw5BKQ2kPQD+YBfQNPpEFyOhpU3c15p2711xLSM0TOzXxRkBSKn5 quYbQ7b7vWIi6WQXWAVOfY5ahDOinLk4gteHnT/Mpe/euRSatIPAPaqM2LeFi4Yps7iV f6aIgt3hqiyhl5hAeNVNIPySN9yGF5242LZcpvRmQoW5D6x1FW14GQJ9rz5tSJ6J+F5C EVzRnyUCX1Phh0yWIOGDurv0zZUpdTSghM50N5rmS+jfAyQ8AMzo2y7V8v1zcWl/Ui60 C4ZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=FUT7tb5nShqi4zpKQqq4hX+oiMEOVEgGwvIIRz2ht6Y=; b=n6Xq0FCkODskFa5uZTxgzwMQN+uTfsWRN5Yc+uE/XHvt6OXN3UQ3mRuofQGuYzCMiM OdNzw4Jn/x/u0hW2mFCqJe/JCz9YZGzmAW+VtedLJjbJCRv+lpvYDYuO2oTwr4KYIlEH Dwumwl69fOuV5c/zP5gcE+dEfGAc40h+wwAJJwd7CHP69VtdI7Zv529KtIluPO1B7Jbn mY8RoGkPCrQ0A+Z7AJnFb6+XlY7QJAJblshSCRA4mpnrRwrsx8qZKpzdgMKC5xWgycB9 fviwu9+CX1fEd0QWfclu26uZF194GoM75KDzJ2/SXPWUvivFEVeCm1Le5+bDfJWo3t6P kx1A==
X-Gm-Message-State: AODbwcCECq0jsFm1IiqxYwRiCXpDS8yyNAyNjchIISmVo49SmIgi37Bu BvDFKmbGXHZ5BjNGgGAE7A==
X-Received: by 10.25.18.154 with SMTP id 26mr8787141lfs.176.1496865224352; Wed, 07 Jun 2017 12:53:44 -0700 (PDT)
Received: from [10.0.0.129] (h-155-4-129-189.NA.cust.bahnhof.se. [155.4.129.189]) by smtp.gmail.com with ESMTPSA id i76sm543964lfe.2.2017.06.07.12.53.42 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Jun 2017 12:53:43 -0700 (PDT)
Subject: Re: wireless geolocation
To: ietf@ietf.org
References: <m27f0pqgbc.wl-randy@psg.com>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se>
Date: Wed, 7 Jun 2017 21:53:42 +0200
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: <m27f0pqgbc.wl-randy@psg.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/wsE03hCwwkj-F0ZJmNxQo2RZrYU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 19:53:49 -0000

So to sum up:

"Here is a problem: ... "

"No its not and even if it was, its not a bug, its a feature and
besides you can turn it off in the settings and also we covered it
in 5 different working groups over the course of the last decade
and also email is broken and I like the way it worked in DOS."

Sounds about right?

	Cheers Leif


From nobody Wed Jun  7 14:24:49 2017
Return-Path: <christopher.morrow@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 3A4F3131493 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 14:24:36 -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, 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 3zRuyM0wjahG for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 14:24:34 -0700 (PDT)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65BDB129AD1 for <ietf@ietf.org>; Wed,  7 Jun 2017 14:24:34 -0700 (PDT)
Received: by mail-qt0-x229.google.com with SMTP id u12so21470188qth.0 for <ietf@ietf.org>; Wed, 07 Jun 2017 14:24:34 -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=amPGcDhbhCF3MjAGFrTVlTarM9OXgsRcrCbYRLq3de0=; b=fe9NbbVSPGZ5uT9gVXpljoACTs0aUNF3irtwuUu3ALeCYrFdAAC0tthlpDs+r9UizR DUAR0aNaNHpRy0aptYFc8uvTwXYOrSWDr60s2phHygkjhPCuHp/1AN5htYGSG7DNBG65 0oQJXNyH+sfRA68gS3eghkR+KfpQSXcpnx2TiE/skooo7qtRwu9ARrRdBmBohJsY4hXe 6qQ8jsCJ0mV8GE4cHwHETnz/lZpIKv9ChIFseHbx8PsFwOZqHUS9I+fOx1Uz/W3Xi9SP bDbyPNDVil9XuYigGYN1OZ0+eyCThwvCHpgnT+2m+EjTwC9j+EAFgFxvL6rqloq/Qr11 osZw==
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=amPGcDhbhCF3MjAGFrTVlTarM9OXgsRcrCbYRLq3de0=; b=pNT5P6ailiF03YRnOWHPoABaJlx+Gkx/n1gQkFcH4eKeFJ3KLfEoPTGRY6CZr9zdUD ISWxBxhZ9/6dWJlAonsSnN2zo9LYeH4J8Ov5aE6dHMODzblqR/oxcJ34Tgq8HFxuOd0Q aPy5WdHZ+tbjgIQfJTqm6+wVL+uh2KG6w9P2/cP+0ESkAkFj+XPnrA1vzhrwoZF1d29k taTKATzzN8/18ExbPLWREIbZZq8uAwgXq/q/abbLCdlT0ctwoW04VRydF9St2G3OWaZH wCktdtl8PybIoq3laGMAnH7bu/bu5TjCnLl54uKELhqzblwT5/URCTLUMw+0ooAzgkee vcFg==
X-Gm-Message-State: AODbwcAIJtyay/xKy/OUF+l3Oog/ZKe/pQcG27qPEXjKh7L/stOlowPN of1B4PEUGDFJdIdWkUDsN2IwH4KyJg==
X-Received: by 10.200.39.51 with SMTP id g48mr38381715qtg.163.1496870673628; Wed, 07 Jun 2017 14:24:33 -0700 (PDT)
MIME-Version: 1.0
Sender: christopher.morrow@gmail.com
Received: by 10.140.86.106 with HTTP; Wed, 7 Jun 2017 14:24:32 -0700 (PDT)
In-Reply-To: <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se>
References: <m27f0pqgbc.wl-randy@psg.com> <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se>
From: Christopher Morrow <morrowc.lists@gmail.com>
Date: Wed, 7 Jun 2017 17:24:32 -0400
X-Google-Sender-Auth: uQ59J4lk9q8t6JIya7weUBIlxAU
Message-ID: <CAL9jLaZf2-3Tf81SmNT17N55p4BnmutQLYgbTmHGZsFZ+sHVKA@mail.gmail.com>
Subject: Re: wireless geolocation
To: Leif Johansson <leifj@mnt.se>
Cc: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a11405fe2c6c6cf0551655c26"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N2fiZrOvDZyGwNDEa_E8PNtntlg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 21:24:36 -0000

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

On Wed, Jun 7, 2017 at 3:53 PM, Leif Johansson <leifj@mnt.se> wrote:

>
> So to sum up:
>
> "Here is a problem: ... "
>
> "No its not and even if it was, its not a bug, its a feature and
> besides you can turn it off in the settings and also we covered it
> in 5 different working groups over the course of the last decade
> and also email is broken and I like the way it worked in DOS."
>
> Sounds about right?
>
>
>
Isn't the OP's question really:
  "GEO is not working well for conference organizers, users seem to
actually want it to work (despite protestations of even the OP, at times),
 are there folk on-list who would like to gather and discuss making the
processing of changes a bit more automagical?"

yes, some folk 'do not want to give up their privacy', and some folk want
to 'order pizza near me'... welcome to the tubez dudez.

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

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Jun 7, 2017 at 3:53 PM, Leif Johansson <span dir=3D"ltr">&lt;<a=
 href=3D"mailto:leifj@mnt.se" target=3D"_blank">leifj@mnt.se</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex"><br>
So to sum up:<br>
<br>
&quot;Here is a problem: ... &quot;<br>
<br>
&quot;No its not and even if it was, its not a bug, its a feature and<br>
besides you can turn it off in the settings and also we covered it<br>
in 5 different working groups over the course of the last decade<br>
and also email is broken and I like the way it worked in DOS.&quot;<br>
<br>
Sounds about right?<br>
<br><br></blockquote><div><br></div><div>Isn&#39;t the OP&#39;s question re=
ally:<br>=C2=A0 &quot;GEO is not working well for conference organizers, us=
ers seem to actually want it to work (despite protestations of even the OP,=
 at times), =C2=A0are there folk on-list who would like to gather and discu=
ss making the processing of changes a bit more automagical?&quot;</div><div=
><br></div><div>yes, some folk &#39;do not want to give up their privacy&#3=
9;, and some folk want to &#39;order pizza near me&#39;... welcome to the t=
ubez dudez.</div></div><br></div></div>

--001a11405fe2c6c6cf0551655c26--


From nobody Wed Jun  7 14:27:47 2017
Return-Path: <leifj@mnt.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 83B27127180 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 14:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level: 
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id B1UglPgRcdpk for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 14:27:44 -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 E0A6B128CDB for <ietf@ietf.org>; Wed,  7 Jun 2017 14:27:43 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id p189so10816921lfe.2 for <ietf@ietf.org>; Wed, 07 Jun 2017 14:27:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vCNtEXznN+9SWGn5Edy4TGvGvjDz+qxhd07OdbpjE54=; b=nY2/MBCFQYsIamT2Jc6YjzSndNX4JuDskZrNYSEa/a0KIoycvoz31T6hWxO2HreWXG MJ/jKv/geq+TWb8wYNN652kyXSgEg2ZPZ/QVfS9mQMIcfDpt7z/UaFX1WUkTf6cPEui7 yT9qhZTyqHEEbGJ0JvifHt8OFRIEiC181UDRsA9Ja0jQa0INhsjYbHAL+Cc83NLI+3Yb t4evWvzVPXHYNnJ314yOIeZTFzsNGt6YalHIrfd92zEjiH/OKh3NdjCDc1zBsRmOFpeq mVyawUvXjDnfBhhUqUgB4wyf/HijeJiFdH9Mz+711Rvndd7tnOy7hRyRvPjD4vJofXF1 tRCw==
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=vCNtEXznN+9SWGn5Edy4TGvGvjDz+qxhd07OdbpjE54=; b=kwtpUOBUKKXQrYVz2/vlIm+6pgF+XTDpXZh1oppM2MGZGwcKw3Jg1ajaucgktY3KUE mbV02nLoUqnFy7idmbGfUcLZS6cL5NSVUrek28HbL8sXHGHhp5Pnky0aWooy6NH6cf8T gUnSv0Tx0vagEgf/T+eLy6fjpcq161kAb8XSlTXX5LEHMUG2FbTCmmUJa4cU75LyOXxf uIkkAHlcNtEwK6TCJWDVvRmyXW+ZJ8rjoolaoE75ijnAVDH7VlE9hOsfhrOgk6haW95i hdL1GixnrH/WywatfWyMq5Hc9RMsIRtdK/tdkminqKtEnv/WKHm8JDUD5En/M9wbnYtI wwiw==
X-Gm-Message-State: AODbwcCIfruv06zDZ5elvgR9diZFXecg+SrktmWS7JUvVEyjSV58w5Jr 88fYTSi9GsBpLHXEmVR3rw==
X-Received: by 10.46.20.77 with SMTP id 13mr5328309lju.14.1496870861708; Wed, 07 Jun 2017 14:27:41 -0700 (PDT)
Received: from [10.0.0.139] (h-155-4-129-189.NA.cust.bahnhof.se. [155.4.129.189]) by smtp.gmail.com with ESMTPSA id g13sm589853ljg.33.2017.06.07.14.27.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 07 Jun 2017 14:27:41 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-02463421-E2C5-43A1-BE28-F1918EC8D6F4
Mime-Version: 1.0 (1.0)
Subject: Re: wireless geolocation
From: Leif Johansson <leifj@mnt.se>
X-Mailer: iPhone Mail (14F89)
In-Reply-To: <CAL9jLaZf2-3Tf81SmNT17N55p4BnmutQLYgbTmHGZsFZ+sHVKA@mail.gmail.com>
Date: Wed, 7 Jun 2017 23:27:38 +0200
Cc: ietf <ietf@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <0F79B0EF-7E04-46A6-A1EA-652874D59E2D@mnt.se>
References: <m27f0pqgbc.wl-randy@psg.com> <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se> <CAL9jLaZf2-3Tf81SmNT17N55p4BnmutQLYgbTmHGZsFZ+sHVKA@mail.gmail.com>
To: Christopher Morrow <morrowc.lists@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FyWXQ32seAw82RnVTd_2xUIq_qc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 21:27:46 -0000

--Apple-Mail-02463421-E2C5-43A1-BE28-F1918EC8D6F4
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable



Skickat fr=C3=A5n min iPhone

> 7 juni 2017 kl. 23:24 skrev Christopher Morrow <morrowc.lists@gmail.com>:
>=20
>=20
>=20
>> On Wed, Jun 7, 2017 at 3:53 PM, Leif Johansson <leifj@mnt.se> wrote:
>>=20
>> So to sum up:
>>=20
>> "Here is a problem: ... "
>>=20
>> "No its not and even if it was, its not a bug, its a feature and
>> besides you can turn it off in the settings and also we covered it
>> in 5 different working groups over the course of the last decade
>> and also email is broken and I like the way it worked in DOS."
>>=20
>> Sounds about right?
>>=20
>>=20
>=20
> Isn't the OP's question really:
>   "GEO is not working well for conference organizers, users seem to actual=
ly want it to work (despite protestations of even the OP, at times),  are th=
ere folk on-list who would like to gather and discuss making the processing o=
f changes a bit more automagical?"

Yep


>=20
> yes, some folk 'do not want to give up their privacy', and some folk want t=
o 'order pizza near me'... welcome to the tubez dudez.
>=20

:-)=

--Apple-Mail-02463421-E2C5-43A1-BE28-F1918EC8D6F4
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><br><br>Skickat fr=C3=A5n min iPhone</=
div><div><br>7 juni 2017 kl. 23:24 skrev Christopher Morrow &lt;<a href=3D"m=
ailto:morrowc.lists@gmail.com">morrowc.lists@gmail.com</a>&gt;:<br><br></div=
><blockquote type=3D"cite"><div><div dir=3D"ltr"><br><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Wed, Jun 7, 2017 at 3:53 PM, Leif Joha=
nsson <span dir=3D"ltr">&lt;<a href=3D"mailto:leifj@mnt.se" target=3D"_blank=
">leifj@mnt.se</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
So to sum up:<br>
<br>
"Here is a problem: ... "<br>
<br>
"No its not and even if it was, its not a bug, its a feature and<br>
besides you can turn it off in the settings and also we covered it<br>
in 5 different working groups over the course of the last decade<br>
and also email is broken and I like the way it worked in DOS."<br>
<br>
Sounds about right?<br>
<br><br></blockquote><div><br></div><div>Isn't the OP's question really:<br>=
&nbsp; "GEO is not working well for conference organizers, users seem to act=
ually want it to work (despite protestations of even the OP, at times), &nbs=
p;are there folk on-list who would like to gather and discuss making the pro=
cessing of changes a bit more automagical?"</div></div></div></div></div></b=
lockquote><div><br></div>Yep<div><br></div><div><br><blockquote type=3D"cite=
"><div><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote=
"><div><br></div><div>yes, some folk 'do not want to give up their privacy',=
 and some folk want to 'order pizza near me'... welcome to the tubez dudez.<=
/div></div><br></div></div>
</div></blockquote><br></div><div>:-)</div></body></html>=

--Apple-Mail-02463421-E2C5-43A1-BE28-F1918EC8D6F4--


From nobody Wed Jun  7 15:10:06 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 2589B1293EC for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 15:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LpxGmSpS0Mwo for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 15:10:02 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 938E61270A7 for <ietf@ietf.org>; Wed,  7 Jun 2017 15:10:02 -0700 (PDT)
Received: (qmail 39016 invoked from network); 7 Jun 2017 22:10:01 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 7 Jun 2017 22:10:01 -0000
Date: 7 Jun 2017 22:09:39 -0000
Message-ID: <20170607220939.1990.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: wireless geolocation
In-Reply-To: <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v2zix9UtJCXB0W54PYMkOlgt50Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 22:10:04 -0000

In article <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se> you write:
>
>So to sum up:
>
>"Here is a problem: ... "
>
>"No its not and even if it was, ...

I'd say that summary is not even wrong.  Our problem is not technical.
Geolocation is handled by a handful of companies that have no
incentive to solve our problem.

How many wifi networks are there in the world?  I expect upward of a
hundred million.

How many wifi networks regularly move from one continent to another?
You can probably count them on your fingers.  We're not even a
rounding error, and we're not paying customers.  Why should Maxmind et
al. spend money to build a mechanism to deal with us and networks like
ours?

R's,
John


From nobody Wed Jun  7 15:27:43 2017
Return-Path: <nico@cryptonector.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7E06129453 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 15:27:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.419
X-Spam-Level: 
X-Spam-Status: No, score=-1.419 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, RCVD_IN_SORBS_SPAM=0.5, 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 SiT-nRag_qhM for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 15:27:40 -0700 (PDT)
Received: from hapkido.dreamhost.com (hapkido.dreamhost.com [66.33.216.122]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E10601270A7 for <ietf@ietf.org>; Wed,  7 Jun 2017 15:27:40 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (sub4.mail.dreamhost.com [69.163.253.135]) by hapkido.dreamhost.com (Postfix) with ESMTP id 8D8698A814; Wed,  7 Jun 2017 15:27:40 -0700 (PDT)
Received: from localhost (cpe-70-123-158-140.austin.res.rr.com [70.123.158.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id A2D311406B28; Wed,  7 Jun 2017 15:27:03 -0700 (PDT)
Date: Wed, 7 Jun 2017 17:27:00 -0500
From: Nico Williams <nico@cryptonector.com>
To: John Levine <johnl@taugh.com>
Cc: ietf@ietf.org
Subject: Re: wireless geolocation
Message-ID: <20170607222659.GI3432@localhost>
References: <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se> <20170607220939.1990.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170607220939.1990.qmail@ary.lan>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/00GfZrdAmYJDU_A_8-6qRONHZuQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 22:27:42 -0000

On Wed, Jun 07, 2017 at 10:09:39PM -0000, John Levine wrote:
> In article <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se> you write:
> >So to sum up:
> >
> >"Here is a problem: ... "
> >
> >"No its not and even if it was, ...
> 
> I'd say that summary is not even wrong.  Our problem is not technical.
> Geolocation is handled by a handful of companies that have no
> incentive to solve our problem.
> 
> How many wifi networks are there in the world?  I expect upward of a
> hundred million.
> 
> How many wifi networks regularly move from one continent to another?
> You can probably count them on your fingers.  We're not even a
> rounding error, and we're not paying customers.  Why should Maxmind et
> al. spend money to build a mechanism to deal with us and networks like
> ours?

See, now, this is why we need to put geoloc information into DNS and/or
BGP, thus cutting out the secret sauce makers for all cases where
services don't mind trusting DNS/BGP geoloc data.

I mean that half-facetiously, half-seriously.


From nobody Wed Jun  7 15:36:30 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9678B128BB6 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 15:36:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001,  URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=WkZNZX+G; dkim=pass (1536-bit key) header.d=taugh.com header.b=kLZOkBQb
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SKYioQjlgvlk for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 15:36:27 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC8F21271FD for <ietf@ietf.org>; Wed,  7 Jun 2017 15:36:26 -0700 (PDT)
Received: (qmail 41878 invoked from network); 7 Jun 2017 22:36:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=a394.59387fe9.k1705; bh=bMcZIwemxfpZc+VtSDP6xEMD1+bK9uBUvbE7LUxanEI=; b=WkZNZX+GLwgRjiY2jR428P+8CzT1RXpsWEG+UTN5mLri6C9q1JIJgg9r8YnbNiR31OFv4lvS0VCBp0f1FO05tnOGFLvavtuYaBoCZTZ6vDgOb/8ssACuy697y0MW2R6Lu3kqlP25/N5V3Xws1URb5+yTOKONuClM53f/dwb3m+CjGM17kN+TulFq88AmPxOv8aDdN/5n3uUOcnm2R6HtEUvyQgElrzEWu5aW/5qEBSTIJ9RogR4GYhox/BfzGfI4
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=a394.59387fe9.k1705; bh=bMcZIwemxfpZc+VtSDP6xEMD1+bK9uBUvbE7LUxanEI=; b=kLZOkBQbdhyPXoCbGvgYSa0V76ekf/JiZUcsVibBm+EmmpGl4+ApWCK23Pu+szVeTZqLP9lrxq5q7dAPXXZW787lJSX8l+ssYQqBiLCYb6osmj5bBIX0IHuUzH30bWRrRuICXW1GIoWAyltGDGV84P8MwqA0VUukVVDe4m8tu/Qlamwbs4hcIaPO+SlFvqjmfg95Fis94MI9Yp2qel1GW7YN5lNGzKBMb57jx2U7CpJR5AUl7JIUGdNiErrebey2
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; 07 Jun 2017 22:36:25 -0000
Date: 7 Jun 2017 18:36:25 -0400
Message-ID: <alpine.OSX.2.21.1706071832420.3025@ary.qy>
From: "John R Levine" <johnl@taugh.com>
To: "Nico Williams" <nico@cryptonector.com>
Cc: "IETF general list" <ietf@ietf.org>
Subject: Re: wireless geolocation
In-Reply-To: <20170607222659.GI3432@localhost>
References: <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se> <20170607220939.1990.qmail@ary.lan> <20170607222659.GI3432@localhost>
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/pwiNG8CaaZoRmR01Mig87Qcfc_Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 22:36:28 -0000

> See, now, this is why we need to put geoloc information into DNS and/or
> BGP, thus cutting out the secret sauce makers for all cases where
> services don't mind trusting DNS/BGP geoloc data.
>
> I mean that half-facetiously, half-seriously.

If you want a GPOS or LOC rrtype, you know where to find them.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly


From nobody Wed Jun  7 16:41:23 2017
Return-Path: <tytso@thunk.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 F2A3212EB62 for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 16:41:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=thunk.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MGo7Jdh_W4iK for <ietf@ietfa.amsl.com>; Wed,  7 Jun 2017 16:41:18 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) (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 CB128128CD5 for <ietf@ietf.org>; Wed,  7 Jun 2017 16:41:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org;  s=ef5046eb;  h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=/I5IG2CvyTKB2UwviIFwSkIFJ7/2+Fz/04sipWSfgwQ=;  b=ewrpi5eHwwVQQx436Y9x7kPiyJIlativVVBmfZ8QxxexVrxPNQjzY8XEUuG2G576+KIOmGvgrhKUOhxBvqLSlOQXZg1Q8OyIMwJTUBn1JOjcAjVw/KKtVZMHeI4dcdNHZO78bZGT2svh3Ip1IuoP1glXqQI5uHfFf0pVu+IIW18=;
Received: from root (helo=callcc.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.84_2) (envelope-from <tytso@thunk.org>) id 1dIkZh-0006HZ-OM; Wed, 07 Jun 2017 23:41:17 +0000
Received: by callcc.thunk.org (Postfix, from userid 15806) id 899E6C012E1; Wed,  7 Jun 2017 19:41:16 -0400 (EDT)
Date: Wed, 7 Jun 2017 19:41:16 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: John Levine <johnl@taugh.com>
Cc: ietf@ietf.org
Subject: Re: wireless geolocation
Message-ID: <20170607234116.kle7vflcjc7hzjpx@thunk.org>
References: <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se> <20170607220939.1990.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170607220939.1990.qmail@ary.lan>
User-Agent: NeoMutt/20170113 (1.7.2)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n_qlJpnEWLb3gLAtFla_UFGI-nQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 07 Jun 2017 23:41:21 -0000

On Wed, Jun 07, 2017 at 10:09:39PM -0000, John Levine wrote:
> How many wifi networks regularly move from one continent to another?
> You can probably count them on your fingers.  We're not even a
> rounding error, and we're not paying customers.  Why should Maxmind et
> al. spend money to build a mechanism to deal with us and networks like
> ours?

Well, it's said that conference/standards travellers often drop large
sums of money at many fine dining establishments.  And no one seems to
have a problem when concierges get referral fees for suggesting
restaurants to their clients.  There may be more money in getting this
geolocation thing as right as possible than you think.

It is interesting though that if someone picks up a phone and says,
"Hey Samantha[1], find a nice restaurant near me", and it does, (a) some
people think it's creepy, and (b) some people think it's somehow dirty
that the company that created "Samantha" might get paid for the
referral just like a hotel concierge.

[1] http://www.imdb.com/title/tt1798709/

Or does it cross the line when "Samantha" remembers that you've been
asking her questions about molecular gastronomy and tailors the
responses she sends back to you based on that?

It's really fascinating to me that somehow it's OK when a Nordstrum's
sales associate does basic research on his or her clients, or keeps a
notes in their notebooks of their client's likes and dislikes, and the
dates of their wedding anniversary, relative's birthdays, and suggests
gifts for their client.  Somehow *that*'s not creepy (in fact, some
find it flattering, or makes them feel important), but when a computer
does it, it's creep city....

					- Ted


From nobody Wed Jun  7 19:31:42 2017
Return-Path: <dafranke@akamai.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 10E51128B8D; Wed,  7 Jun 2017 19:31:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Daniel Franke <dafranke@akamai.com>
To: <secdir@ietf.org>
Cc: draft-ietf-bmwg-vswitch-opnfv.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
Subject: Secdir last call review of draft-ietf-bmwg-vswitch-opnfv-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.53.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149688909394.25708.7443355162118602638@ietfa.amsl.com>
Date: Wed, 07 Jun 2017 19:31:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ilzboaE9Ok3D5ESt6mpZ52Oxovo>
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, 08 Jun 2017 02:31:34 -0000

Reviewer: Daniel Franke
Review result: Ready

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.

This Informational draft outlines methodology for benchmarking switches,
carried out on isolated test networks. It defines no new protocols or device
capabilities in support of the recommended methodology, or anything else which
would introduce any new security considerations.


From nobody Thu Jun  8 00:43:32 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0E71126B7F for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 00:43:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i_piVCn6if8x for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 00:43:30 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97DFD129B71 for <ietf@ietf.org>; Thu,  8 Jun 2017 00:43:29 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id 63so10461818ywr.0 for <ietf@ietf.org>; Thu, 08 Jun 2017 00:43:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Kktms8etKebI4b1brRYVxKARtIrPejihab0yGxkWWBY=; b=fwnAdmMHOuJYurLKnSLayHB/XTCUxvXDruutpq1ytH9Z0x12cF0TmExX1tBKuY/CTw dL0pJcArqz/b+x/t4KKUP1GZeY2XoA1YAU3WpSHpeABXr+qM9otphMXIq5sxXfRt63lU 188l6srD0Tm5hbsb3hyQzDfKZkFl/hBcA8nX0=
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=Kktms8etKebI4b1brRYVxKARtIrPejihab0yGxkWWBY=; b=Cwh5km5XS4dgR6L2x71Q82zQCKTEeJOtT6mJy+zzl0Oc3hHcGd7ovEmGZCN8PvZL/j 9R7jCI1Ap+RHlp7QoLgPXu6nGFH1EQ2BXF3vClJY5t2HPEN6jfSp8ldnlYi8P1IMw32j 3Oxh7Skl2o9Y9OCOaAjk1s674ltXan7/ALAiKWRxdLjr06lGBqX3tBXG270nasFcBDUQ K8lVfdpOnT+UOJkptn2Bas4z9IGYUB6Ib2BHKCY5W7WDPHq10Ae3gZb+CojeOh9Q+50E c3VOPzzLUVYyAdj5fcKZDay3g9dsznbdlK6/JAcOBt75x4wHPGCj23iIgd5/3dMIuuM6 sIuw==
X-Gm-Message-State: AODbwcAHsQinSHK6f6hJzMxHX8c1wmbFvrnV6KnWuC9hXiROi1v1PCxx RAU1aVG58QaroltpLt0LllUchwDk6dDVVxc=
X-Received: by 10.129.75.196 with SMTP id y187mr10598464ywa.166.1496907808867;  Thu, 08 Jun 2017 00:43:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.25.195 with HTTP; Thu, 8 Jun 2017 00:43:28 -0700 (PDT)
In-Reply-To: <20170607222659.GI3432@localhost>
References: <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se> <20170607220939.1990.qmail@ary.lan> <20170607222659.GI3432@localhost>
From: Dave Cridland <dave@cridland.net>
Date: Thu, 8 Jun 2017 08:43:28 +0100
Message-ID: <CAKHUCzz4m9+rfzCroMt88575=YRd0+J5xvdYMAK7cqaLJG5vow@mail.gmail.com>
Subject: Re: wireless geolocation
To: Nico Williams <nico@cryptonector.com>
Cc: John Levine <johnl@taugh.com>, "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nBwGnNJd4qPRh9twyRALSsKTNtA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 07:43:32 -0000

On 7 June 2017 at 23:27, Nico Williams <nico@cryptonector.com> wrote:
> On Wed, Jun 07, 2017 at 10:09:39PM -0000, John Levine wrote:
>> In article <efebcd89-289d-2a3e-9246-6321c07bd255@mnt.se> you write:
>> >So to sum up:
>> >
>> >"Here is a problem: ... "
>> >
>> >"No its not and even if it was, ...
>>
>> I'd say that summary is not even wrong.  Our problem is not technical.
>> Geolocation is handled by a handful of companies that have no
>> incentive to solve our problem.
>>
>> How many wifi networks are there in the world?  I expect upward of a
>> hundred million.
>>
>> How many wifi networks regularly move from one continent to another?
>> You can probably count them on your fingers.  We're not even a
>> rounding error, and we're not paying customers.  Why should Maxmind et
>> al. spend money to build a mechanism to deal with us and networks like
>> ours?
>
> See, now, this is why we need to put geoloc information into DNS and/or
> BGP, thus cutting out the secret sauce makers for all cases where
> services don't mind trusting DNS/BGP geoloc data.
>
> I mean that half-facetiously, half-seriously.
>

I'll take you seriously, if I may.

First, I'd note that several WiFi networks move around on one
continent on a frequent basis, and many fly through the air between
continents. While a network that is physically bundled into boxes and
moved might be an edge-case, there are an ever increasing number of
access points on the move these days.

Given that the geoloc problem fits into one of two cases, I think you
have half the issue sorted there - a DNS record in the reverse-lookup
domain would satisfy the case where a service wants to go from only an
IP address to a location.

But much of the discussion revolved around a device complicitly
sharing its location based off the BSSID; in this case a DHCP
extension would surely be useful? We're working on the assumption,
here, that the device - and therefore hopefully its owner - is
deliberately providing a location, after all.

On the assumption that administrators of access points are often not
going to set this up, it might also be useful to have an extension
which simply indicated whether the network was fixed or mobile.

Dave.


From nobody Thu Jun  8 05:29:41 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 597E0129C6D; Thu,  8 Jun 2017 05:29:40 -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-dcbench-methodology.all@ietf.org, ietf@ietf.org, bmwg@ietf.org, dromasca@gmail.com
Subject: Genart last call review of draft-ietf-bmwg-dcbench-methodology-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.53.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149692498024.25760.14056448148418579949@ietfa.amsl.com>
Date: Thu, 08 Jun 2017 05:29:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tzU0B4Qc3uUsQ5DPKFr8_U6hC7c>
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, 08 Jun 2017 12:29:40 -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-bmwg-dcbench-methodology-??
Reviewer: Dan Romascanu
Review Date: 2017-06-08
IETF LC End Date: 2017-06-13
IESG Telechat date: Not scheduled for a telechat

Summary:

This Informational I-D describes test and evaluation methodology and
measurement techniques for physical network equipment in the data center. It's
an useful and clearly written document and it is ready for publication, after a
number of minor issues and nits will be addressed.

Major issues:

Minor issues:

1. There is one single mention of the scope being benchmarking of 'physical
network equipment in the data center'. I assume this is written as opposed to
virtual networking equipment. This is not included in the title or repeated any
place else. I suggest to make more clear the scope by mentioning 'physical
equipment' at least once more, for example in the Introduction section.

2. Section 1.2: I am a little concerned about adding additional interpretations
to the keywords in RFC2119.

Especially about:

'MAY: Comprehensive metric for the scenario described'

MAY has a different meaning in 2119, and the fact that a metric is
'comprehensive' (whatever this means) seems to me orthogonal to the 2119
semantics. The proposed interpretation makes little sense to me, if
'comprehensive' than why not required? or at least as a 'should'?

3. Section 6.2: 'The intensity of a microburst MAY be varied ...' It would be
useful to make clear what is meant by 'intensity'.

Nits/editorial comments:

1. The different formatting of the references [1], [2], etc. vs. [RFC2119],
etc. is slightly confusing. Unless there is some good reason I suggest to fix
this. Also use of references is inconsistent through the text, sometimes they
are mentioned, sometimes they are not.

2. Section 2.2: 'Alternatively when a traffic generator CAN NOT be connected '
- this capitalization is not conformant to RFC2119.

3. 'vlan ZZZ' is not consistent with 'vlan X' and 'vlan Y' previously used.

4. Missing reference - RFC 6985

5. Missing expansion and references for DSCP and COS

6. Sections 3.3 and 6.3: s/number of iteration/number of iterations/

7. The methodology (e.g. in section 5) makes an assumption that the DUT has at
least nine ports. This may be trivial in a DC, but it's worth being mentioned



From nobody Thu Jun  8 05:40:56 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 7F854126CF6 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 05:40:55 -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 QhI1w9KO76b0 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 05:40:54 -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 DEB8D1287A7 for <ietf@ietf.org>; Thu,  8 Jun 2017 05:40:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2443; q=dns/txt; s=iport; t=1496925654; x=1498135254; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=tH+UxB3uJtmdOLZrC2+lfY7dth4CcfcZdOXTopOXcjk=; b=kP7F/pHq7Az+Q9e4Wbba5lK/THgdllWhU/tK0x3Cv1VcieAOVOmByk2B yZ918BNuPUQEQ34rpp6OnBwNUB6Oh1iBIksygfsEsY3Dr9mHiaftUvofA yQBkujMrQflCkkqcqlRW2qGjeTuTUSr+1LO1MvTTn4dtCH7nhy24vp1aZ M=;
X-Files: signature.asc : 481
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DPAACLRDlZ/xbLJq1eGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBiTqKGHOQd5YCghEHhh0CgzYYAQIBAQEBAQEBayiFGQEFI2YjKgI?= =?us-ascii?q?CVwYBDAgBAYonsEmCJowAAQEBAQEBAQECAQEBAQEBARIPiGyCdYd8gmEBBJ46h?= =?us-ascii?q?BCCHY0Piw+GcpRoHziBCjAhCBsVhVEcgWc+ijcBAQE?=
X-IronPort-AV: E=Sophos;i="5.39,314,1493683200";  d="asc'?scan'208";a="694999817"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jun 2017 12:40:49 +0000
Received: from [10.61.82.63] (ams3-vpn-dhcp4672.cisco.com [10.61.82.63]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v58CenS2005436; Thu, 8 Jun 2017 12:40:49 GMT
Subject: remember incentives! Re: wireless geolocation
To: John Levine <johnl@taugh.com>, ietf@ietf.org
References: <20170607220939.1990.qmail@ary.lan>
From: Eliot Lear <lear@cisco.com>
Message-ID: <9aab234c-db44-9c89-d3eb-e5f571b52be9@cisco.com>
Date: Thu, 8 Jun 2017 14:40:48 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <20170607220939.1990.qmail@ary.lan>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="XtmGdX9jt6xb2Ehi12VhjUOqr0nithKuf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u3j6jMeKy_enVUbv9CbXv3Q9vxI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 12:40:55 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--XtmGdX9jt6xb2Ehi12VhjUOqr0nithKuf
Content-Type: multipart/mixed; boundary="XUeIDHddPsbc5hQwagEIVsEhvKLheo4wW";
 protected-headers="v1"
From: Eliot Lear <lear@cisco.com>
To: John Levine <johnl@taugh.com>, ietf@ietf.org
Message-ID: <9aab234c-db44-9c89-d3eb-e5f571b52be9@cisco.com>
Subject: remember incentives! Re: wireless geolocation
References: <20170607220939.1990.qmail@ary.lan>
In-Reply-To: <20170607220939.1990.qmail@ary.lan>

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

Hi John,


On 6/8/17 12:09 AM, John Levine wrote:
> I'd say that summary is not even wrong.  Our problem is not technical.
> Geolocation is handled by a handful of companies that have no
> incentive to solve our problem.

THIS.=20

Those companies make their business off of selling information, and that
information has to be accurate to within some degree.  The IETF is in
the noise.  How many roaming show networks are there really?  If this is
something that is really important to the IETF, then the organization
should use equipment where the BSSID is changed, and/or perhaps start to
rely on local facilities to provide the appropriate services.  Yes, that
might prove expensive.

Not only THIS, but developers are now actually being paid to link their
apps to certain libraries to invade consumer privacy (Egelman et al).=20
And that means that just rotating BSSIDs to protect privacy doesn't
actually do much for privacy, but it might do something for accuracy.

Eliot


--XUeIDHddPsbc5hQwagEIVsEhvKLheo4wW--

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

iQEcBAEBCAAGBQJZOUXRAAoJEIe2a0bZ0nozBLYIALAQ79I2jB7pijQZl0ysB7TU
XgECZnHVbZ/mDsZN/AaAYqn7YGvYGqTYrl6FEgn0YriwgSEyJp6JJGKvAd2V3LFg
9rdW9dK+n30/q0GQHSL3V0P44R7iva3AXsQZyKEFY/M3/577kY7Yqq86AWXGfmKC
o1zh0FgSbLXsBXRd8tilzZbHX3Qyv0WvmJcUoodEBf1MtJKmfB9gXPW2f0Nb25c8
w96J/YI5pRg/MdGZ/+7aT60x+s8v0xIVmy/V1ZQkovrmLqglZ61m577jgcKInC3e
aUMlf9KXdK6OKevZHtUv2GiEcWzrRYgjivfsu+QGVLizTymAB+G5STQjq5EcMXA=
=9vCi
-----END PGP SIGNATURE-----

--XtmGdX9jt6xb2Ehi12VhjUOqr0nithKuf--


From nobody Thu Jun  8 07:44:03 2017
Return-Path: <leifj@mnt.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 D16A6127B73 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 07:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XXjcGqxcaNJD for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 07:43:59 -0700 (PDT)
Received: from mail-lf0-x22b.google.com (mail-lf0-x22b.google.com [IPv6:2a00:1450:4010:c07::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F9E1127B60 for <ietf@ietf.org>; Thu,  8 Jun 2017 07:43:59 -0700 (PDT)
Received: by mail-lf0-x22b.google.com with SMTP id o83so18974486lff.3 for <ietf@ietf.org>; Thu, 08 Jun 2017 07:43:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=7uNpUdYFFBGRM2IvdWWLakpROebZX1laAQjPeY9CmlM=; b=0hun0erO5VboGmPWN8yJ8EYL7alNlRUFInyH3OsmSzomiGkyv/Ep0x7I7ALF46InDT xwSk7IIZO9XDC2aKqzH7u96Pw56GB5NPUISTqgYy1fs1o0053w6pju8xPUuEwjF1Z9gT w3nXWcuLQ7dz5JqQP9vKptSsRMGHNFEhdl92BK7LzkzoSr9KN1WvmV/7ZjdM8/k9K/sH BjlVdbFnkKJCDyxbG1DScWCBiU9Cjm08IZTIRcaZLSKs4JBk9ytOBDqOvfzZTFqXZjVb ALQxhgGxjyC327GhgDi+Gp+Gwgges0vZwCrUgROvzI/hNU8vIbNbxA5SDNP8OUN5UX9C Fx2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=7uNpUdYFFBGRM2IvdWWLakpROebZX1laAQjPeY9CmlM=; b=CZ1WWpCicxxo0xTeZWhCZd6ol54hoShvy1eSoCZeN8g8daUfAPFwpZXZQnp9dV69jT p+7b20PLXznFRwP7yaxKA9qQrmQRgfRmsBvzYk9tkx+dF1lh54EltgpkbhxMgqXyyMMt d0LFOsyCtSWI9kPd0iREQkYd4YBRauVPZwmgbPOnq9++1PpRx+y6pEICi6paTgyrWeWp uenHYaF/TErLIyEhfG1EJAH4ogwf7bTFjnNUZf7i9jOM/J5b64N2UBW1BcDMM6w7CWEU AI8UvkL8DsQO9mx8ylQyoFAwtk05lShy+i7l0IuPs6Ff/Ps+ZTt14VK4U98bp7jtkkv6 xGKg==
X-Gm-Message-State: AODbwcDuRkUMsVaC7iDwVP0lbvtFbEZNIqm0hEtI2VNOXB77bwCX7ejM GWUBfbLdEahloiaUHNggJA==
X-Received: by 10.46.21.16 with SMTP id s16mr11389135ljd.47.1496933037084; Thu, 08 Jun 2017 07:43:57 -0700 (PDT)
Received: from ?IPv6:2001:6b0:7:1:ac94:343e:2e3:bc8c? ([2001:6b0:7:1:ac94:343e:2e3:bc8c]) by smtp.gmail.com with ESMTPSA id n79sm1097246lje.12.2017.06.08.07.43.55 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Jun 2017 07:43:56 -0700 (PDT)
Subject: Re: remember incentives! Re: wireless geolocation
To: ietf@ietf.org
References: <20170607220939.1990.qmail@ary.lan> <9aab234c-db44-9c89-d3eb-e5f571b52be9@cisco.com>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <2954b530-687d-94d2-0749-004c56c52779@mnt.se>
Date: Thu, 8 Jun 2017 16:43:55 +0200
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: <9aab234c-db44-9c89-d3eb-e5f571b52be9@cisco.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/9Ez013vJqybdznB_0YtER4ZS_ao>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 14:44:02 -0000

On 2017-06-08 14:40, Eliot Lear wrote:
> Hi John,
> 
> 
> On 6/8/17 12:09 AM, John Levine wrote:
>> I'd say that summary is not even wrong.  Our problem is not technical.
>> Geolocation is handled by a handful of companies that have no
>> incentive to solve our problem.
> 
> THIS. 
> 
> Those companies make their business off of selling information, and that
> information has to be accurate to within some degree.  The IETF is in
> the noise.  How many roaming show networks are there really?  If this is
> something that is really important to the IETF, then the organization
> should use equipment where the BSSID is changed, and/or perhaps start to
> rely on local facilities to provide the appropriate services.  Yes, that
> might prove expensive.
> 
> Not only THIS, but developers are now actually being paid to link their
> apps to certain libraries to invade consumer privacy (Egelman et al). 
> And that means that just rotating BSSIDs to protect privacy doesn't
> actually do much for privacy, but it might do something for accuracy.
> 
> Eliot
> 

All right so the claim is now that it may be an issue but its not
worth spending time on since the "other side" won't want to play ball?

Fair enough, however I note that the OPs message claimed that the
NOC is /reasonably/ successful in dealing with this issue by
sending emails so its not inconceivable that an automated process
could work...

otoh it would require that the IETF manage to keep it simple... ;-)

	Cheers Leif


From nobody Thu Jun  8 08:27:27 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 3B9F9128B88 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 08:27:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dzO7pG6Zbu_M for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 08:27:25 -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 E68C0128B51 for <ietf@ietf.org>; Thu,  8 Jun 2017 08:27:24 -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 1dIzLG-0000i5-NO for ietf@ietf.org; Thu, 08 Jun 2017 15:27:23 +0000
Date: Thu, 08 Jun 2017 21:27:20 +0600
Message-ID: <m2tw3qmrdz.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: remember incentives! Re: wireless geolocation
In-Reply-To: <2954b530-687d-94d2-0749-004c56c52779@mnt.se>
References: <20170607220939.1990.qmail@ary.lan> <9aab234c-db44-9c89-d3eb-e5f571b52be9@cisco.com> <2954b530-687d-94d2-0749-004c56c52779@mnt.se>
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/0vmkuA7ULSCvetFCAkJzEFEQfPs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 15:27:26 -0000

had a convo with a very large and well known cdn provider who uses ip
address based geoloc.  they actually go to the noc web site to check if
our address ranges have changed, where our next meeting will be, and set
their database accordingly.

i would like to make their life easier.  i do not think on the wire
protocol is needed; i suspect it can be done with some sort of pre-
registered authorization and a signed well known data format.  ip
address and mac seem to be the two mobile meeting identifiers.  but
i am probably a bit premature to be in the solution space.

the following did have a certain ring to it.  welcome to the ietf.  

    "Here is a problem: ... "

    "No its not and even if it was, its not a bug, its a feature and
    besides you can turn it off in the settings and also we covered it
    in 5 different working groups over the course of the last decade
    and also email is broken and I like the way it worked in DOS."

of course i have never been guilty of such :)

randy


From nobody Thu Jun  8 08:53:46 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 E78E8129473; Thu,  8 Jun 2017 08:53:37 -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: draft-ietf-tcpm-dctcp.all@ietf.org, tcpm@ietf.org, ietf@ietf.org
Subject: Opsdir last call review of draft-ietf-tcpm-dctcp-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149693721791.15103.13571928856211954021@ietfa.amsl.com>
Date: Thu, 08 Jun 2017 08:53:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X6M_8eWgFn-b3cBrHGz72KLEJ1M>
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, 08 Jun 2017 15:53:38 -0000

Reviewer: Joe Clarke
Review result: Has Nits

Hello, WG and authors.  I have reviewed rev -07 of the draft-ietf-tcpm-dctcp as
requested by the OPS-DIR.  This review focuses on improving operational aspects
as well as any nits found in the text.

This document is an informational draft that describes Data Center TCP (DCTCP),
a congestion control mechanism for TCP in Data Center environments.

Overall, I believe this document to be ready, with some nits and perhaps small
areas for improved clarity and readability.  First, I'd like to say that I
appreciate the fact that this has been implemented on a number of kernels, and
the authors included real-world implementation results and thoughts.  From an
operational perspective, that is very helpful.  I also appreciated the fact
that there are interoperability challenges, and those were called out in the
document.  My specific comments are below.

There are a lot of abbreviations, variables and other terminology used
throughout this document.  It might be helpful for the reader to have an
expanded terminology section at the top that one can refer to for all of these
things.  Some of the abbreviations are called out in the description of the
algorithm, but not all (e.g., DCTCP.Alpha, CWR, RTT, etc.).

===

Section 3.2:

You refer to DCTCP.Alpha before defining it.  While you refer to Section 3.3
here, the impact of an incorrect Alpha value is not fully appreciated in this
text.  Perhaps this could be changed to reflect the impact the incorrect Alpha
value would have?

===

Section 3.2:

My abbreviating DCTCP.CE as CE in your state machine diagram, it is a bit
confusing as to the difference between CE and DCTCP.CE.  The description of the
state machine above requires the CE codepoint to have a certain value in order
for DCTCP.CE to change.  Perhaps you can use D.CE as an abbreviation to be a
bit clearer here.

===

Section 3.3:

It is not clear if 'g' can be inclusive of 0 and 1.

===

Section 3.3:

You define DCTCP.WindowEnd as the threshold for beginning a new observation
window, but maybe to complement the state variable name, you should define it
as the following:

The TCP sequence number threshold when one observation window ends and other is
to begin; initialized to SND.UNA.

===

Section 3.3:

You state:

Thus, when no bytes sent experienced congestion, DCTCP.Alpha equals
zero, and cwnd is left unchanged

But if I use a value of 1/16 for g, with DCTCP.Alpha initialized to 1 as you
say, I get a value of DCTCP.Alpha == 15/16 when there is no congestion (i.e., M
== 0).

===

Section 3.5:

You have an extra space here before the comma:

If SYN , SYN-ACK and RST packets for DCTCP connections have ECT set

This should be:

If SYN, SYN-ACK and RST packets for DCTCP connections have ECT set

===

Section 3.5:

You do not define ECT before using it.

===

Section 4.1:

Can you provide a reference for NewReno?

===

Section 5:

Can you reference or define AQM and RED?



From nobody Thu Jun  8 09:04:17 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 2421812708C for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 09:04:16 -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 JD6y28T5td3c for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 09:04:14 -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 6A17212932A for <ietf@ietf.org>; Thu,  8 Jun 2017 09:04:14 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 79D25E1D5; Thu,  8 Jun 2017 12:05:05 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C1385636BB; Thu,  8 Jun 2017 12:04:13 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@cisco.com>
cc: John Levine <johnl@taugh.com>, ietf@ietf.org
Subject: Re: remember incentives! Re: wireless geolocation
In-Reply-To: <9aab234c-db44-9c89-d3eb-e5f571b52be9@cisco.com>
References: <20170607220939.1990.qmail@ary.lan> <9aab234c-db44-9c89-d3eb-e5f571b52be9@cisco.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Thu, 08 Jun 2017 12:04:13 -0400
Message-ID: <4577.1496937853@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6tnL9ifVE4pP6C1BK5RKwnNWC80>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 16:04:16 -0000

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


Eliot Lear <lear@cisco.com> wrote:
    > On 6/8/17 12:09 AM, John Levine wrote:
    >> I'd say that summary is not even wrong.  Our problem is not technical.
    >> Geolocation is handled by a handful of companies that have no
    >> incentive to solve our problem.

    > THIS.

    > Those companies make their business off of selling information, and that
    > information has to be accurate to within some degree.  The IETF is in
    > the noise.  How many roaming show networks are there really?  If this is
    > something that is really important to the IETF, then the organization
    > should use equipment where the BSSID is changed, and/or perhaps start to
    > rely on local facilities to provide the appropriate services.  Yes, that
    > might prove expensive.

So, if we want to get their attention, we need to increase the noise until
the data is useless? :-)

--
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+93Q3WUFAlk5dX0ACgkQgItw+93Q
3WXNNwf/evsFN6G66EKi+muRL8/f+OVuLFAn0KSGAxtTL2X0Qci8ZDInl/MMUTDD
wS7x2fxZ4/en9aBlhm0hKek5jtKMbi0ZxpsLo5uRMIDqKTDWDHEXGOvSeQ1vpRZw
fXDYkBux2P7xeZ+GDmpjekUb2o06eACMjXNMEqQa8yHHJfZZShM+1ZMq2Cuk0eWi
eFXh2MPubnsMSATd9IxYEVNesQuOe2yCTfMykE+g7xnVxHJ6S428jOP3wLD2jui+
IXnVEmiBf8t3U3ePNF5CW0IlGgCyl68dUy9MkFuGXJ8zhkgMdc8fUJDVOieM+aWS
HroyACTqySSM+rYWKvaJVyOtKmYL1A==
=56hL
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Jun  8 09:51:26 2017
Return-Path: <rg+ietf@randy.pensive.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 EDB7F12944B for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 09:51:23 -0700 (PDT)
X-Quarantine-ID: <MUC5CV1CjhAb>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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] 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 MUC5CV1CjhAb for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 09:51:22 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 5EBE51293FF for <ietf@ietf.org>; Thu,  8 Jun 2017 09:51:22 -0700 (PDT)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 8 Jun 2017 09:54:01 -0700
Mime-Version: 1.0
Message-Id: <p06240601d55f30312789@[99.111.97.136]>
X-Mailer: Eudora for Mac OS X
Date: Thu, 8 Jun 2017 09:51:19 -0700
To: ietf-ecrit@ietf.org, ietf@ietf.org
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: IETF blog post about next-gen advanced automatic crash notification
Cc: Brian Rosen <Brian.Rosen@neustar.biz>, Alissa Cooper <alissa@cooperw.in>, Greg Wood <wood@isoc.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9qxKy3OqDzIUBlFND9GA4Nt0qxM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 16:51:24 -0000

Hi everyone,

Brian Rosen and I wrote a short blog entry introducing the recently 
published RFCs on next-generation advanced automatic crash 
notification:

https://www.ietf.org/blog/2017/06/advanced-automatic-crash-notifications/

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Our ability to reach unity in diversity will be the beauty and
test of our civilization.                     --Mahatma Gandhi


From nobody Thu Jun  8 09:58:06 2017
Return-Path: <rg+ietf@randy.pensive.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 282331294E8 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 09:58:05 -0700 (PDT)
X-Quarantine-ID: <ejkihMgH2c4N>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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] 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 ejkihMgH2c4N for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 09:58:04 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id F41A5129AC7 for <ietf@ietf.org>; Thu,  8 Jun 2017 09:58:03 -0700 (PDT)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 8 Jun 2017 10:00:43 -0700
Mime-Version: 1.0
Message-Id: <p06240602d55f31937a91@[99.111.97.136]>
In-Reply-To: <CAPt1N1ni9Z12gfNArK4GaJpXdp2OMoZXv_wKrHYCcCG2wom=tw@mail.gmail.com>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <CAPt1N1ni9Z12gfNArK4GaJpXdp2OMoZXv_wKrHYCcCG2wom=tw@mail.gmail.com>
X-Mailer: Eudora for Mac OS X
Date: Thu, 8 Jun 2017 09:58:01 -0700
To: Ted Lemon <mellon@fugue.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: wireless geolocation
Cc: ietf <ietf@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XlPtNoB99HP1GTFEHO5Ef50f9-4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Jun 2017 16:58:05 -0000

At 4:50 PM -0400 6/6/17, Ted Lemon wrote:

>  Because it makes it very difficult to use various services if they 
> think we are 7000 miles away from where we are. Latency can be bad, 
> and using maps can be impossible.

I personally find the effects more an amusing artifact that an actual 
hindrance, but that's just me.  However, when I'm traveling and not 
part of an IETF, I find that using a hotel provided IP address 
without a full VPN causes its own set of difficulties with web sites 
assuming the language and character set of the country I'm in.  In 
some cases I'm unable to use a Capcha since it's in a script I can't 
read, and I'm unable to select a language or country on the web site 
for the same reason.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Politics is the art of making the inevitable appear to be a
matter of wise human choice.                 --Quentin Crisp


From nobody Thu Jun  8 10:12:33 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D88B4129AF2 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 10:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N7uePog1gyJb for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 10:12:29 -0700 (PDT)
Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::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 5CFDF129666 for <ietf@ietf.org>; Thu,  8 Jun 2017 10:12:29 -0700 (PDT)
Received: by mail-qt0-x232.google.com with SMTP id c10so49120569qtd.1 for <ietf@ietf.org>; Thu, 08 Jun 2017 10:12:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=s/MPW/PE6D8HRY2FJqJk8KezbCsP/fEKgMSAvYBU8aI=; b=0PYGkKGqAc8AiPux5ZwxboroGzc5aHb96NDeKeDA5f0JWY4TZ49JlHHWhqbic7363X g1+Q5p6ZDO2mY9Dt9QnX3A9WLNLuLrC/NrwO9NX+ZPdCHwnum+0JdCLP60Xt/Yp0PXV6 RrUalGiqwXYeEUG+UDm1i7ApvVgdne5zEuxpI56ESayAkVPgQH/6wGYhIabSMtouAL5m jnEkunNzYR9w3wSLjaK11j5p8OCsdi6hx74LcHYhGKwGkW6Mm/GQs4KoiPFBK9FSy/q7 WMD1xpesGkhLh6o2cQEFuGXt5DimJSoAODI3UMPO18qMbwmR9zGCh6v/rCEwMkwUhl1T 6e/Q==
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=s/MPW/PE6D8HRY2FJqJk8KezbCsP/fEKgMSAvYBU8aI=; b=QPqkydEIc8Zcce/5jXC4oGH3VmzODPyBluVLu/aneGkd19m+SPztvUuvga1qKhezRv KOvmH2YBAJxKzmIyYGo3WVNRZ95uP65dphRAyj3MkiN5Nh8mcAdtl9/Im6yEAkGpn08u Ci0+7siG1uZcvmZv1ETLUz/X0YM454pfBeIGzI0VeXctvV+OhRCnlACqEcENaYS/J8ZO p9PP8KmdiLXGuDSUASXIuRWtNJ3lcjsfFeVXoTg60xR2hJW14MpB96TMRXk5jj0ObtS8 klDiOvefw+VaKlmoml7lV2QOw8ASobbp4lqf6SffPYO49dB2j4IosTOd133TVyrCbjoG Ilfw==
X-Gm-Message-State: AKS2vOxNda1zKkEdLYegidpKhpctb3NYK8JfeGHmtCwn7U7KKOeDBK7h ZJqFii/WJI+b/uK+
X-Received: by 10.55.25.41 with SMTP id k41mr42785531qkh.163.1496941948471; Thu, 08 Jun 2017 10:12:28 -0700 (PDT)
Received: from [10.0.30.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id o49sm3583830qta.34.2017.06.08.10.12.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Jun 2017 10:12:27 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <6959924D-BED3-4338-9113-297FECCA0DBD@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2A15AD93-16D6-46E6-B7EF-D214739EF0D4"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: wireless geolocation
Date: Thu, 8 Jun 2017 13:12:25 -0400
In-Reply-To: <p06240602d55f31937a91@[99.111.97.136]>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf <ietf@ietf.org>
To: Randall Gellens <rg+ietf@randy.pensive.org>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <CAPt1N1ni9Z12gfNArK4GaJpXdp2OMoZXv_wKrHYCcCG2wom=tw@mail.gmail.com> <p06240602d55f31937a91@[99.111.97.136]>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LXqnCfSTv-vovZ7opZq11XHcZrY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 17:12:32 -0000

--Apple-Mail=_2A15AD93-16D6-46E6-B7EF-D214739EF0D4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On Jun 8, 2017, at 12:58 PM, Randall Gellens <rg+ietf@randy.pensive.org> =
wrote:
> I personally find the effects more an amusing artifact that an actual=20=

> hindrance, but that's just me.

It made it a pain to schedule an IoTdir dinner in Chicago=E2=80=94I kept =
getting redirected to sites with similar names in Seoul.   I am =
embarrassed at how long it took me to realize that I could just use my =
phone's tethering capability to solve the problem.

That said, the artifact you are talking about actually happened to me in =
Chicago, because I was "in Seoul" as far as (some) geolocation services =
were concerned.   The way to prevent this behavior when in a foreign =
country is to use a VPN; this should work just fine from the IETF =
network, if not from the hotel network.

Of course, even better would be if geolocation information could be =
overridden from the browser; I'm not aware of such a possibility that =
actually generally works, however.


--Apple-Mail=_2A15AD93-16D6-46E6-B7EF-D214739EF0D4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jun 8, 2017, at 12:58 PM, Randall Gellens &lt;<a =
href=3D"mailto:rg+ietf@randy.pensive.org" =
class=3D"">rg+ietf@randy.pensive.org</a>&gt; wrote:<div><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Menlo-Regular; font-size: 18px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: =
inline !important;" class=3D"">I personally find the effects more an =
amusing artifact that an actual<span =
class=3D"Apple-converted-space">&nbsp;</span></span><br =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span style=3D"font-family: Menlo-Regular; font-size: 18px; =
font-style: normal; font-variant-caps: normal; font-weight: normal; =
letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; float: none; display: inline =
!important;" class=3D"">hindrance, but that's just =
me.</span></div></blockquote></div><br class=3D""><div class=3D"">It =
made it a pain to schedule an IoTdir dinner in Chicago=E2=80=94I kept =
getting redirected to sites with similar names in Seoul. &nbsp; I am =
embarrassed at how long it took me to realize that I could just use my =
phone's tethering capability to solve the problem.</div><div =
class=3D""><br class=3D""></div><div class=3D"">That said, the artifact =
you are talking about actually happened to me in Chicago, because I was =
"in Seoul" as far as (some) geolocation services were concerned. &nbsp; =
The way to prevent this behavior when in a foreign country is to use a =
VPN; this should work just fine from the IETF network, if not from the =
hotel network.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Of course, even better would be if geolocation information =
could be overridden from the browser; I'm not aware of such a =
possibility that actually generally works, however.</div><div =
class=3D""><br class=3D""></div></body></html>=

--Apple-Mail=_2A15AD93-16D6-46E6-B7EF-D214739EF0D4--


From nobody Thu Jun  8 10:22:50 2017
Return-Path: <johnl@taugh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 75C7A12952E for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 10:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EaL5aEv1-H1q for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 10:22:47 -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 A065F1293D9 for <ietf@ietf.org>; Thu,  8 Jun 2017 10:22:47 -0700 (PDT)
Received: (qmail 75604 invoked from network); 8 Jun 2017 17:22:46 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 8 Jun 2017 17:22:46 -0000
Date: 8 Jun 2017 17:22:24 -0000
Message-ID: <20170608172224.5739.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: tytso@mit.edu
Subject: Re: wireless geolocation
In-Reply-To: <20170607234116.kle7vflcjc7hzjpx@thunk.org>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uTpCdOMaxGuzSO3qFpWIK56vlb0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 17:22:49 -0000

In article <20170607234116.kle7vflcjc7hzjpx@thunk.org> you write:
>Well, it's said that conference/standards travellers often drop large
>sums of money at many fine dining establishments.  And no one seems to
>have a problem when concierges get referral fees for suggesting
>restaurants to their clients.  There may be more money in getting this
>geolocation thing as right as possible than you think.

Our phones geolocate just fine, so I think that part of the problem is
solved.

R's,
John


From nobody Thu Jun  8 10:24:07 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 EF9381296C9 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 10:24:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4jSPkFj39wuR for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 10:24:04 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E4E81293D9 for <ietf@ietf.org>; Thu,  8 Jun 2017 10:24:04 -0700 (PDT)
Received: (qmail 75896 invoked from network); 8 Jun 2017 17:24:03 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 8 Jun 2017 17:24:03 -0000
Date: 8 Jun 2017 17:23:41 -0000
Message-ID: <20170608172341.5760.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: remember incentives! Re: wireless geolocation
In-Reply-To: <m2tw3qmrdz.wl-randy@psg.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qwoxI-4a-vKkCMUJb_0LIzBEcOI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 17:24:06 -0000

In article <m2tw3qmrdz.wl-randy@psg.com> you write:
>had a convo with a very large and well known cdn provider who uses ip
>address based geoloc.  they actually go to the noc web site to check if
>our address ranges have changed, where our next meeting will be, and set
>their database accordingly.
>
>i would like to make their life easier.

If there are geoloc providers who would like our updates, that would
be dandy.  But my impression is that the problem is that there are
many (or at least some large ones) that don't.

R's,
John


From nobody Thu Jun  8 10:54:08 2017
Return-Path: <rg+ietf@randy.pensive.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 99D19126DCA for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 10:54:06 -0700 (PDT)
X-Quarantine-ID: <PVX3rZIEVhDC>
X-Virus-Scanned: amavisd-new at amsl.com
X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version"
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] 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 PVX3rZIEVhDC for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 10:54:05 -0700 (PDT)
Received: from turing.pensive.org (turing.pensive.org [99.111.97.161]) by ietfa.amsl.com (Postfix) with ESMTP id 69A8312EB0B for <ietf@ietf.org>; Thu,  8 Jun 2017 10:53:41 -0700 (PDT)
Received: from [99.111.97.136] (99.111.97.161) by turing.pensive.org with ESMTP (EIMS X 3.3.9); Thu, 8 Jun 2017 10:56:18 -0700
Mime-Version: 1.0
Message-Id: <p06240606d55f3e196a17@[99.111.97.136]>
In-Reply-To: <6959924D-BED3-4338-9113-297FECCA0DBD@fugue.com>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <CAPt1N1ni9Z12gfNArK4GaJpXdp2OMoZXv_wKrHYCcCG2wom=tw@mail.gmail.com> <p06240602d55f31937a91@[99.111.97.136]> <6959924D-BED3-4338-9113-297FECCA0DBD@fugue.com>
X-Mailer: Eudora for Mac OS X
Date: Thu, 8 Jun 2017 10:53:36 -0700
To: Ted Lemon <mellon@fugue.com>
From: Randall Gellens <rg+ietf@randy.pensive.org>
Subject: Re: wireless geolocation
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, ietf <ietf@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VplOqalifi5npzqbaQWnDxd6isE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 17:54:07 -0000

At 1:12 PM -0400 6/8/17, Ted Lemon wrote:

>  The way to prevent this behavior when in a foreign country is to 
> use a VPN; this should work just fine from the IETF network, if not 
> from the hotel network.

Indeed, VPNs solve the problem by changing where one appears to be to 
the web site, which is why I said the problem happens "without a full 
VPN."

Really, everything we're talking about in this thread is because of 
the various hacks that have grown up to guess at various things such 
as location, language, character set, etc.  The hacks work well 
enough enough of the time that people rely on them.

Because the hack works well enough enough of the time, it's common 
for people to assume that it's reliable, but as we're discussing 
here, it isn't.  Interestingly, in the U.S., there is work ongoing to 
develop a National Emergency Address Database (NEAD), which is 
designed to reliably and authoritatively provide a specific location, 
e.g., by having a venue owner specify the MAC addresses of Wi-Fi APs 
within the venue, as well as other sources and inputs.

-- 
Randall Gellens
Opinions are personal;    facts are suspect;    I speak for myself only
-------------- Randomly selected tag: ---------------
Badkruka (BAD-ruke-ah; Swedish; noun): Someone who refuses to enter
a body of water, no matter how warm.


From nobody Thu Jun  8 10:56:22 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 B58AC1200C5 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 10:56:20 -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] 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 Zlvdd59mbfGS for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 10:56:18 -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 A9C7C126DCA for <ietf@ietf.org>; Thu,  8 Jun 2017 10:56:18 -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 1dJ1fN-000OxQ-H2; Thu, 08 Jun 2017 13:56:17 -0400
Date: Thu, 08 Jun 2017 13:56:10 -0400
From: John C Klensin <john-ietf@jck.com>
To: Randall Gellens <rg+ietf@randy.pensive.org>
cc: ietf <ietf@ietf.org>
Subject: Re: wireless geolocation
Message-ID: <840150E29D6968A1244BAEAD@PSB>
In-Reply-To: <p06240602d55f31937a91@[99.111.97.136]>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <CAPt1N1ni9Z12gfNArK4GaJpXdp2OMoZXv_wKrHYCcCG2wom=tw@mail.gmail.com> <p06240602d55f31937a91@[99.111.97.136]>
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/AT081A229Io7gX77_mzgK-0TdbE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 17:56:21 -0000

--On Thursday, June 8, 2017 09:58 -0700 Randall Gellens
<rg+ietf@randy.pensive.org> wrote:

> I personally find the effects more an amusing artifact that an
> actual hindrance, but that's just me.  However, when I'm
> traveling and not part of an IETF, I find that using a hotel
> provided IP address without a full VPN causes its own set of
> difficulties with web sites assuming the language and
> character set of the country I'm in.  In some cases I'm unable
> to use a Capcha since it's in a script I can't read, and I'm
> unable to select a language or country on the web site for the
> same reason.

While I agree, I think this may be a different problem and one
that we (and/or W3C) could fix if we were motivated.  A
variation on the "incentives" theme is useful here too -- very
few actors have incentives to condition information being
provided to you based on bad choices of language or locale, even
if there are complex case-by-case decisions (or sheer laziness)
about whether the costs of getting things right in a larger
number of cases are worth it.    We've got machinery for
specifying preferences in cultural or locale information to web
browsers (and the SLIM WG has been working on somewhat parallel
arrangements for other kinds of real time communications).   Are
those options right?  Do they provide enough preference
information that you (or a typical user, or a heuristic) can
figure out whether to use the information they think you've
given a browser (or failed to provide), rather than what the
hotel, or the hotel network, or even the choice of computer if
you are using one you don't own) are telling them?

Those are actually not easy questions in terms of designing the
right sorts of tools and indicators.  Pursuing your example,
suppose you are in Lower Slobbovia, don't speak or read Lower
Slobbovian, but want to find a nearby pizza restaurant.
Probably you want to have the system communicate with you in
English, but you don't want the locale information to reflect,
e.g., California, because knowing where the nearest pizza
restaurant would be if you were in California would not be of
much interest. That, in turn, leads to another economic issue:
if the local, Lower Slobbovian, restaurant operators federation
has concluded that it isn't worth the costs of supplying
information in English,  then you don't even have a localization
issue any more, you simply have a choice between asking in Lower
Slobbovian (or some other language they want to support) or not
asking in any way that yields answers.

On can respond to that example by asking questions about
automated translation, etc., but I'd just make the example more
complicated.

It seems to me that set of issues has little to do with how the
servers that interact with the hotel network guess at language
or location and, in particular, whether they use the IP or MAC
address to get there.   But it does seems to me that it suggests
we should review whether our various means for explicitly
telling systems about locale information do what is wanted and
fix them if they don't.  Certainly, such fixes should recognize
the right of those who don't want accurate location information
under any circumstances to starve in the dark, but it is not
clear to me that they should be our primary audience. 

   john



From nobody Thu Jun  8 11:24:42 2017
Return-Path: <leifj@mnt.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 53A5812EB2F for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 11:24:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnt-se.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kYjIN1E2LRPV for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 11:24:38 -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 4B09012EB24 for <ietf@ietf.org>; Thu,  8 Jun 2017 11:24:38 -0700 (PDT)
Received: by mail-lf0-x22c.google.com with SMTP id a136so21331773lfa.0 for <ietf@ietf.org>; Thu, 08 Jun 2017 11:24:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnt-se.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language:content-transfer-encoding; bh=WLUEfSHEA46cUm0WUKknfTCoFwSUHL51R4nZbPWr+mA=; b=NPn1OTOnlrnUBSY1YYIMlEyJNFv5CWtkiQ3WBliG0IvJaohSYK6PXFlVdLslb/mMv8 azbfOGFZQHVpT3oftsJrrXvlRPZ6r8RzDFs9gVtzKXwZ6a/0Qv7vs3EPmqCchsJp1ezc Tt0LeTEQ0pPaG3KtquUdIcWOcUuN+Kw+Umb5CGk4/2velkcsJoj9nLjnHs2HeoRZEOcj ivYZ1hTH03iNJ5dnXBZzUSpUNTXe6uHw3A1VAYQb1ZUv18jD2L+t6vBCN4akpIE6tV/C 4UwQYHgf5YXm5Cew+LuQks4ddA/RyhB5HYiYZpCntqjzuDFuELaOjXI3bv8RDdzi/qGn T5qw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=WLUEfSHEA46cUm0WUKknfTCoFwSUHL51R4nZbPWr+mA=; b=kp4f23E5BssXEX7oXKqIe5czv+OJaOpSgAjWzggVgsJw9m+Cc1eJtH9jF0dUXwWRbo kpgT4QVm91+KtDegYmTCCvAJ7RyT9zU4lfV69fk4P4K+JZpgC+18oJgxHRa83+jD2z57 pgmL9iOH76+lZ2LrfAdBiGk0GvjeSYVCbKYOCwNqj4MKeEna6XBTXxJuMtfhtqoGPUHN D2DcNDAuMskkYBAK350Hpu4CPTXx9BPjaB6IDkOi2zD682P5I3M/tJMtPFP9DHzg13L1 09tDBV5IFltjLFyO8n3EuIGR7GAmKNZ6HC0F/kzyLvfAFbazrGTro2NS54bLh9R0rx65 njmg==
X-Gm-Message-State: AODbwcB1Pkz8jium1q8EsfSHJUWyg0E5S21hzx99qZ1O37SakfFGRjrB C4x0w8kPsJbBoax9fptqIA==
X-Received: by 10.25.196.197 with SMTP id u188mr3056526lff.159.1496946276345;  Thu, 08 Jun 2017 11:24:36 -0700 (PDT)
Received: from ?IPv6:2001:6b0:7:1:ac94:343e:2e3:bc8c? ([2001:6b0:7:1:ac94:343e:2e3:bc8c]) by smtp.gmail.com with ESMTPSA id h84sm1163719lfi.33.2017.06.08.11.24.35 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 08 Jun 2017 11:24:35 -0700 (PDT)
Subject: Re: remember incentives! Re: wireless geolocation
To: ietf@ietf.org
References: <20170608172341.5760.qmail@ary.lan>
From: Leif Johansson <leifj@mnt.se>
Message-ID: <91fe7044-7377-ea87-9d26-9b916b814f56@mnt.se>
Date: Thu, 8 Jun 2017 20:24:34 +0200
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: <20170608172341.5760.qmail@ary.lan>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hZAzShWpSwGXPSWRKLWwSR1QTAA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 18:24:40 -0000

On 2017-06-08 19:23, John Levine wrote:
> In article <m2tw3qmrdz.wl-randy@psg.com> you write:
>> had a convo with a very large and well known cdn provider who uses ip
>> address based geoloc.  they actually go to the noc web site to check if
>> our address ranges have changed, where our next meeting will be, and set
>> their database accordingly.
>>
>> i would like to make their life easier.
> 
> If there are geoloc providers who would like our updates, that would
> be dandy.  But my impression is that the problem is that there are
> many (or at least some large ones) that don't.

I didn't get that impression from the OP but maybe thats a topic for
a bar BoF... in Praha ... if we can find something close to the Loop.

	Cheers Leif


From nobody Thu Jun  8 13:56:53 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 C4B9C127876 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 13:56:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 ASyIofHOfbRd for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 13:56:39 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c: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 DCF7C127B52 for <ietf@ietf.org>; Thu,  8 Jun 2017 13:56:34 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id p85so21614632vkd.3 for <ietf@ietf.org>; Thu, 08 Jun 2017 13:56:34 -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=LOMO1IIVl8yVb/pVNVwrvGQOQTLpD+LrmINW7OLoqfE=; b=r89c+gmpNFPlz5RJhxrZLsRGZ3rt4ijdFtMF4tWn++nUdLKyTT63/j1fAu9nuilsJk exvJ38LpjEPgj5dyEk77sjgPe8EzILq6vdl1kc0L75e6tSm9rQ4vF4eyCY3Bf/A1l7Yr isagK83Lie3JlwJXR8HIcHGntWGQqFfKnnnxA+xKpdzc5IHhaKE52IR0zQ8n0wrThK1A Lh0//Frjwt/vJwTZvdO1uIMMpfzZKnq5Jq9eF8Y9ZhuCX85hmqs5I5yWVPSq4QzGKBHj LyZuTL38Y68qJAqWUNOklDxPANE4JMBnsqbGlvKKb9SEXXPPJbYZ+s6FfwEJqPef5wDA bK+Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=LOMO1IIVl8yVb/pVNVwrvGQOQTLpD+LrmINW7OLoqfE=; b=H6vFvJPnAfDWu7LwPKb6aKDRLEOPzIq0Iw2HQ5pjd6/2QFzPSVyej/SpfM0amVkMAN cwQrQU2BeRoNqZSvXBL2lt1cZZnJWisxU54rCL66oxefKr1XLvvFBXUpygjD5av3qgkn K3EiAwitppfhpqdkkwTGk3UvgmnyaIzNF0W7WDqFbZn2++pHWSP/KJn1kHDxleHcROc7 MApLZVkEUz41pIUukxIcaW0MP8D6M4yXf2mqwUDfau8JgynjZnpM8Rs8cYQ1wWIO3nfK ZvvxrE0PTbJxMyalBnH5OTahi63PUJwCynsYdHaGKMN6+K2nsgO1eii+FUthXjACfLU+ nOyg==
X-Gm-Message-State: AODbwcCY+BfDAc6dz5oiY85/N/v50At6QataGnsw/CGiLoT/ni0XY7Qw 7td3VqKM0VH6VaoPuidEtw+y/k0a637k
X-Received: by 10.31.96.150 with SMTP id u144mr12017937vkb.124.1496955393771;  Thu, 08 Jun 2017 13:56:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.176.82.198 with HTTP; Thu, 8 Jun 2017 13:55:53 -0700 (PDT)
In-Reply-To: <149693721791.15103.13571928856211954021@ietfa.amsl.com>
References: <149693721791.15103.13571928856211954021@ietfa.amsl.com>
From: Warren Kumari <warren@kumari.net>
Date: Thu, 8 Jun 2017 16:55:53 -0400
Message-ID: <CAHw9_iKdVYh15g9M9wtFr1-GPFNjywyvCAd0jkJPMAyO8=m-2g@mail.gmail.com>
Subject: Re: [OPS-DIR] Opsdir last call review of draft-ietf-tcpm-dctcp-07
To: Joe Clarke <jclarke@cisco.com>
Cc: ops-dir@ietf.org, draft-ietf-tcpm-dctcp.all@ietf.org, tcpm@ietf.org,  IETF Discuss <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8zT_ks221Xre9wmsctGHJVbYXhk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 20:56:41 -0000

On Thu, Jun 8, 2017 at 11:53 AM, Joe Clarke <jclarke@cisco.com> wrote:
> Reviewer: Joe Clarke
> Review result: Has Nits
>
> Hello, WG and authors.  I have reviewed rev -07 of the draft-ietf-tcpm-dctcp as
> requested by the OPS-DIR.  This review focuses on improving operational aspects
> as well as any nits found in the text.

... and I'd quickly like to thank Joe for his review. Fixing issues
like this make the documents progress through the IESG with much less
drama...

W


>
> This document is an informational draft that describes Data Center TCP (DCTCP),
> a congestion control mechanism for TCP in Data Center environments.
>
> Overall, I believe this document to be ready, with some nits and perhaps small
> areas for improved clarity and readability.  First, I'd like to say that I
> appreciate the fact that this has been implemented on a number of kernels, and
> the authors included real-world implementation results and thoughts.  From an
> operational perspective, that is very helpful.  I also appreciated the fact
> that there are interoperability challenges, and those were called out in the
> document.  My specific comments are below.
>
> There are a lot of abbreviations, variables and other terminology used
> throughout this document.  It might be helpful for the reader to have an
> expanded terminology section at the top that one can refer to for all of these
> things.  Some of the abbreviations are called out in the description of the
> algorithm, but not all (e.g., DCTCP.Alpha, CWR, RTT, etc.).
>
> ===
>
> Section 3.2:
>
> You refer to DCTCP.Alpha before defining it.  While you refer to Section 3.3
> here, the impact of an incorrect Alpha value is not fully appreciated in this
> text.  Perhaps this could be changed to reflect the impact the incorrect Alpha
> value would have?
>
> ===
>
> Section 3.2:
>
> My abbreviating DCTCP.CE as CE in your state machine diagram, it is a bit
> confusing as to the difference between CE and DCTCP.CE.  The description of the
> state machine above requires the CE codepoint to have a certain value in order
> for DCTCP.CE to change.  Perhaps you can use D.CE as an abbreviation to be a
> bit clearer here.
>
> ===
>
> Section 3.3:
>
> It is not clear if 'g' can be inclusive of 0 and 1.
>
> ===
>
> Section 3.3:
>
> You define DCTCP.WindowEnd as the threshold for beginning a new observation
> window, but maybe to complement the state variable name, you should define it
> as the following:
>
> The TCP sequence number threshold when one observation window ends and other is
> to begin; initialized to SND.UNA.
>
> ===
>
> Section 3.3:
>
> You state:
>
> Thus, when no bytes sent experienced congestion, DCTCP.Alpha equals
> zero, and cwnd is left unchanged
>
> But if I use a value of 1/16 for g, with DCTCP.Alpha initialized to 1 as you
> say, I get a value of DCTCP.Alpha == 15/16 when there is no congestion (i.e., M
> == 0).
>
> ===
>
> Section 3.5:
>
> You have an extra space here before the comma:
>
> If SYN , SYN-ACK and RST packets for DCTCP connections have ECT set
>
> This should be:
>
> If SYN, SYN-ACK and RST packets for DCTCP connections have ECT set
>
> ===
>
> Section 3.5:
>
> You do not define ECT before using it.
>
> ===
>
> Section 4.1:
>
> Can you provide a reference for NewReno?
>
> ===
>
> Section 5:
>
> Can you reference or define AQM and RED?
>
>
> _______________________________________________
> OPS-DIR mailing list
> OPS-DIR@ietf.org
> https://www.ietf.org/mailman/listinfo/ops-dir



-- 
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 Thu Jun  8 13:58:30 2017
Return-Path: <tytso@thunk.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 CE74E129440 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 13:58:28 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, 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=thunk.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zO4_IbIvOqbU for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 13:58:27 -0700 (PDT)
Received: from imap.thunk.org (imap.thunk.org [IPv6:2600:3c02::f03c:91ff:fe96:be03]) (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 4B154127B52 for <ietf@ietf.org>; Thu,  8 Jun 2017 13:58:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=thunk.org;  s=ef5046eb;  h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=mZ4VC93o/w5kfaKLGmSSakc7nF9eQEHlRXlIWYhESUc=;  b=QRc8G3hXqm1Oya5Lp2xEmrgD0AXBGrvczl7mH+aOE3W2P37MQnjv583lD/MxIBhm1Gx4AQ+AIqhBxWDa7dWhSQvGTOLhyvbt1f65XwdjlU7zryo+HH3k7cn69eRbLUOKPjvkG+2pgGda7k6eqKLXXEdQPalqkhsh3JeZ3XrEm/o=;
Received: from root (helo=callcc.thunk.org) by imap.thunk.org with local-esmtp (Exim 4.84_2) (envelope-from <tytso@thunk.org>) id 1dJ4Ve-0006cc-88; Thu, 08 Jun 2017 20:58:26 +0000
Received: by callcc.thunk.org (Postfix, from userid 15806) id 726A2C012E1; Thu,  8 Jun 2017 16:58:25 -0400 (EDT)
Date: Thu, 8 Jun 2017 16:58:25 -0400
From: Theodore Ts'o <tytso@mit.edu>
To: John Levine <johnl@taugh.com>
Cc: ietf@ietf.org
Subject: Re: wireless geolocation
Message-ID: <20170608205825.2bvwqxqlx4glhwxi@thunk.org>
References: <20170607234116.kle7vflcjc7hzjpx@thunk.org> <20170608172224.5739.qmail@ary.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170608172224.5739.qmail@ary.lan>
User-Agent: NeoMutt/20170113 (1.7.2)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: tytso@thunk.org
X-SA-Exim-Scanned: No (on imap.thunk.org); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s2cVwjBwNv-xqUWqV8f1P0dhM1Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 08 Jun 2017 20:58:29 -0000

On Thu, Jun 08, 2017 at 05:22:24PM -0000, John Levine wrote:
> In article <20170607234116.kle7vflcjc7hzjpx@thunk.org> you write:
> >Well, it's said that conference/standards travellers often drop large
> >sums of money at many fine dining establishments.  And no one seems to
> >have a problem when concierges get referral fees for suggesting
> >restaurants to their clients.  There may be more money in getting this
> >geolocation thing as right as possible than you think.
> 
> Our phones geolocate just fine, so I think that part of the problem is
> solved.

We should be clear what problem we're trying to solve.  Randy Bush's
original posting was about geolocation using BSSID's belonging to Wifi
AP's.  This is typically done on mobile devices, although I suppose
some browsers could be querying the OS for Wireless BSSID's.

Other people have broadened this discussion out to geolocation by IP
address, where the server may be trying to make inferences based on
the IP address of the web request as it appears to the front-end
server of the web service.

This is very different from the Browser providing HTML5 Gelocation
information, after asking permission of the user whether a particular
web site should be given visibility to whatever location information
the browser might posses.

So in classic IETF fashion, if this is something where someone wants
to start a wg or a BOF, it would be helpful if the scope of the
problem is very clearly defined.  :-)

						- Ted


From nobody Thu Jun  8 14:47:24 2017
Return-Path: <ynir.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 60BD612952D; Thu,  8 Jun 2017 14:47:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yoav Nir <ynir.ietf@gmail.com>
To: <secdir@ietf.org>
Cc: mpls@ietf.org, ietf@ietf.org, draft-ietf-mpls-app-aware-tldp.all@ietf.org
Subject: Secdir last call review of draft-ietf-mpls-app-aware-tldp-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149695844237.15142.17304755568511932911@ietfa.amsl.com>
Date: Thu, 08 Jun 2017 14:47:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/D6fCk1NCxVziODTshB5lEL9_yq8>
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, 08 Jun 2017 21:47:22 -0000

Reviewer: Yoav Nir
Review result: Has Nits

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written primarily for the benefit of the security area directors. Document
editors and WG chairs should treat these comments just like any other last call
comments.

My biggest issue with this document is that it is hard to read.  For example,
the Introduction expands tLDP to "targeted LDP", and the Introduction begins
with "LDP uses extended discovery...", but LDP itself is only expanded to
"label distribution protocol" in the IANA considerations section.  Similarly,
the much-overloaded term "application" is never explained except that some
applications are "targeted" and that "FEC 128 pseudowire" is an example of an
application.  I am sure this makes sense to participants of the MPLS working
group, but to others this is much harder. There needs to be at least a
reference to RFC 5036 where these terms are better explained (RFC 5036 is
referenced but only as the document where tLDP adjacency is described).

Nits:
The Security Considerations section begins with "The Capability procedure
described in this document will apply and does not introduce any change to LDP
Security Considerations".  The procedure will apply what?  Or will apply to
what?  I think the words "will apply and" are superfluous.

The second paragraph seems to be repeating part of the (rather extensive)
security considerations of RFC 5036, but it does not say why (or even whether)
that particular anti-DoS measure applies in particular to the mechanism
described in this document. IOW why is this measure singled out from among the
three pages of security considerations from RFC 5036?

The third paragraph is not clear to me. It talks about two nodes not
establishing a tLDP session if they don't support the same application. I don't
know why that belongs in the security considerations section. The SHOULD NOT
(establish a session) mandate definitely does not belong there.



From nobody Thu Jun  8 19:52:41 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 6AFF6129408 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 19:52:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7OEpeJ-Evss1 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 19:52:39 -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 3C6201242F7 for <ietf@ietf.org>; Thu,  8 Jun 2017 19:52:39 -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 1dJA2O-00069I-G2; Fri, 09 Jun 2017 02:52:36 +0000
Date: Fri, 09 Jun 2017 08:52:34 +0600
Message-ID: <m2efutna8d.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
In-Reply-To: <20170608205825.2bvwqxqlx4glhwxi@thunk.org>
References: <20170607234116.kle7vflcjc7hzjpx@thunk.org> <20170608172224.5739.qmail@ary.lan> <20170608205825.2bvwqxqlx4glhwxi@thunk.org>
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/N1EtlxCTFh_KuW3XyFIbsHh73ws>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jun 2017 02:52:40 -0000

> We should be clear what problem we're trying to solve.  Randy Bush's
> original posting was about geolocation using BSSID's belonging to Wifi
> AP's.  This is typically done on mobile devices, although I suppose
> some browsers could be querying the OS for Wireless BSSID's.
> ...
> So in classic IETF fashion, if this is something where someone wants
> to start a wg or a BOF, it would be helpful if the scope of the
> problem is very clearly defined.  :-)

i did try.  to be honest, the (to be polite) broad ranging discussion is
about what i expected.  i thought it worth the try.  the good side is
that it gave so many people an opportunity to show how smart they are.

in the meantime, the noc will work it as best we can.  as google has
already relocated, phones will generally work.  some cdns have
relocated.  as to the rest, you'll have to excuse me if i rofl when
anyone whines that they are in chicago or seoul or whatever.

randy


From nobody Thu Jun  8 19:54:28 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 480FC129408 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 19:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2eOT7Sezq0a4 for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 19:54:25 -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 0C4BF1242F7 for <ietf@ietf.org>; Thu,  8 Jun 2017 19:54:25 -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 1dJA47-00069x-QP; Fri, 09 Jun 2017 02:54:24 +0000
Date: Fri, 09 Jun 2017 08:54:22 +0600
Message-ID: <m2d1adna5d.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Randall Gellens <rg+ietf@randy.pensive.org>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: wireless geolocation
In-Reply-To: <p06240606d55f3e196a17@[99.111.97.136]>
References: <m27f0pqgbc.wl-randy@psg.com> <424cc44e-4e2d-2950-7112-c9c0f1f12b1f@mnt.se> <dce335ef-c395-f0a9-9f8f-10c74ef8a4fa@gmail.com> <CAPt1N1ni9Z12gfNArK4GaJpXdp2OMoZXv_wKrHYCcCG2wom=tw@mail.gmail.com> <p06240602d55f31937a91@[99.111.97.136]> <6959924D-BED3-4338-9113-297FECCA0DBD@fugue.com> <p06240606d55f3e196a17@[99.111.97.136]>
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/1DpdacE4Z4W6yEd__SHyMrD6FoQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jun 2017 02:54:26 -0000

> Indeed, VPNs solve the problem by changing where one appears to be to
> the web site

so, when in praha, a restaurant search will give me a recommendation in
tokyo.  this is great, as i prefer tokyo food.

randy


From nobody Thu Jun  8 22:12:05 2017
Return-Path: <lucienav@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 43F5B12946D for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 22:12:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 JLoUx1WyR9fQ for <ietf@ietfa.amsl.com>; Thu,  8 Jun 2017 22:12:00 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::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 CC7AD127275 for <ietf@ietf.org>; Thu,  8 Jun 2017 22:12:00 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id l89so24494999pfi.2 for <ietf@ietf.org>; Thu, 08 Jun 2017 22:12:00 -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=9SdCSEHUmSrPX3mnixqDt85cO9vDyNyOXZiZs1dyYq4=; b=gllOhCYTDj5kG89pXYKEEGwehJ5efAC2bhkKN2J++7KzFayZsmOaqFvsMqR6znvCMC c6EScU333T6Sujf94Xmi09QZO9nN7b72liMr0r9AtqAlrnTH8M0AMT1NNPfpZI18MFD6 EBZHxQCQPghvAxxGBVBDlBbgx+mz3aSkQBir7/yZVjZKrk4pL4n5HZzbwu1ElImQdxKh 5F7SpntTC6CRhR6xze2zvNngi3YPS9dSCGcBULomE6nnrO4eZgw3B2on3DXYZnPrAQT8 tZzc89U30LGTEgHwTI0/KgbcXD0zX5N8vEUOH85VMbi3D/DwlOCZXMD7DQk7DbvQg8gB qEag==
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=9SdCSEHUmSrPX3mnixqDt85cO9vDyNyOXZiZs1dyYq4=; b=R7XCeONzqQTGjf3vS0yVAFXBoWEnWm/4mRUyMRQIECt0Da3mtt9v5cyVN5nbDW27SW EUQyWtkTkFIAYhRjSnshd7QMlgzLAmxY2TdvOEaxPTmwrXh2f8eZZghh7EwEqQTplGnR j/Sa68z9ZBSKeZj1ts7aYudUj+5vD0qvb5AGNNhNhmurgaY2UtSgPFyh91Ojscs7dquC qmgPMd/EM5MlndlrnDU1AkiHNBLCht9yynueUeNuSQ2ZyOX+MndUFHZqlGGralB2SMjJ ovVZT11C9tX58d12/Kyt3ug1ZgIUmgCSa/3cvfSEeyD137uFtiFIHVJaVXpZoN0hbCJv j3Ew==
X-Gm-Message-State: AODbwcATX1pSZpTqPY7FPjTwxCc5dewcq+Yad05HxcWydjbnRol3m/D5 ald0cYjc5/d3cL3ljRhH+PNA9J5AB+2L
X-Received: by 10.98.19.16 with SMTP id b16mr16690518pfj.159.1496985120267; Thu, 08 Jun 2017 22:12:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.138.38 with HTTP; Thu, 8 Jun 2017 22:11:39 -0700 (PDT)
In-Reply-To: <149692498024.25760.14056448148418579949@ietfa.amsl.com>
References: <149692498024.25760.14056448148418579949@ietfa.amsl.com>
From: Lucien Avramov <lucienav@google.com>
Date: Thu, 8 Jun 2017 22:11:39 -0700
Message-ID: <CALTEt=DUhEVgSvYN+2XYUR8Ddq5n8HJtZW2RNj3DV3rSgH0YKQ@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-bmwg-dcbench-methodology-07
To: Dan Romascanu <dromasca@gmail.com>
Cc: gen-art@ietf.org, draft-ietf-bmwg-dcbench-methodology.all@ietf.org,  ietf@ietf.org, bmwg@ietf.org
Content-Type: multipart/alternative; boundary="001a114760f854781a05518002c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v1wQCj_XCrGuWVG4wxqdDL6Ah-k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jun 2017 05:12:03 -0000

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

Hi Dan,

Thank you very much for the comments. I addressed them and published
version -09.

Inline are some the comments / answer to your feedback. The parts without
answers mean they have been addressed.

Again, thank you for spending the time to read this in this fine detail.

Lucien



On Thu, Jun 8, 2017 at 5:29 AM, Dan Romascanu <dromasca@gmail.com> wrote:

> 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-bmwg-dcbench-methodology-??
> Reviewer: Dan Romascanu
> Review Date: 2017-06-08
> IETF LC End Date: 2017-06-13
> IESG Telechat date: Not scheduled for a telechat
>
> Summary:
>
> This Informational I-D describes test and evaluation methodology and
> measurement techniques for physical network equipment in the data center.
> It's
> an useful and clearly written document and it is ready for publication,
> after a
> number of minor issues and nits will be addressed.
>
> Major issues:
>
> Minor issues:
>
> 1. There is one single mention of the scope being benchmarking of 'physical
> network equipment in the data center'. I assume this is written as opposed
> to
> virtual networking equipment. This is not included in the title or
> repeated any
> place else. I suggest to make more clear the scope by mentioning 'physical
> equipment' at least once more, for example in the Introduction section.
>
> 2. Section 1.2: I am a little concerned about adding additional
> interpretations
> to the keywords in RFC2119.
>
> Especially about:
>
> 'MAY: Comprehensive metric for the scenario described'
>

*Thank you, MAY provides an optional metric, I have addressed your comment *

>
> MAY has a different meaning in 2119, and the fact that a metric is
> 'comprehensive' (whatever this means) seems to me orthogonal to the 2119
> semantics. The proposed interpretation makes little sense to me, if
> 'comprehensive' than why not required? or at least as a 'should'?
>
> 3. Section 6.2: 'The intensity of a microburst MAY be varied ...' It would
> be
> useful to make clear what is meant by 'intensity'.
>

The intensity of a microburst is defined in the definitions document [1] so
i referenced it that way


>
> Nits/editorial comments:
>
> 1. The different formatting of the references [1], [2], etc. vs. [RFC2119],
> etc. is slightly confusing. Unless there is some good reason I suggest to
> fix
> this. Also use of references is inconsistent through the text, sometimes
> they
> are mentioned, sometimes they are not.
>

Fixed it for [2] and [3], however kept [1] as [1], as this document is not
an RFC yet.


>
> 2. Section 2.2: 'Alternatively when a traffic generator CAN NOT be
> connected '
> - this capitalization is not conformant to RFC2119.
>
> 3. 'vlan ZZZ' is not consistent with 'vlan X' and 'vlan Y' previously used.
>
> 4. Missing reference - RFC 6985
>
> 5. Missing expansion and references for DSCP and COS
>
> 6. Sections 3.3 and 6.3: s/number of iteration/number of iterations/
>
> 7. The methodology (e.g. in section 5) makes an assumption that the DUT
> has at
> least nine ports. This may be trivial in a DC, but it's worth being
> mentioned
>
> Thanks added this in section 2.3 as it was making more sense to be
clarified there

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

<div dir=3D"ltr">Hi Dan,=C2=A0<div><br></div><div>Thank you very much for t=
he comments. I addressed them and published version -09.=C2=A0</div><div><b=
r></div><div>Inline are some the comments / answer to your feedback. The pa=
rts without answers mean they have been addressed.=C2=A0</div><div><br></di=
v><div>Again, thank you for spending the time to read this in this fine det=
ail.=C2=A0</div><div><br></div><div>Lucien</div><div><br></div><div><br></d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, Jun 8,=
 2017 at 5:29 AM, Dan Romascanu <span dir=3D"ltr">&lt;<a href=3D"mailto:dro=
masca@gmail.com" target=3D"_blank">dromasca@gmail.com</a>&gt;</span> wrote:=
<br><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">Reviewer: Dan Romasca=
nu<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.=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-bmwg-dcbench-method<wbr>ology-??<br>
Reviewer: Dan Romascanu<br>
Review Date: 2017-06-08<br>
IETF LC End Date: 2017-06-13<br>
IESG Telechat date: Not scheduled for a telechat<br>
<br>
Summary:<br>
<br>
This Informational I-D describes test and evaluation methodology and<br>
measurement techniques for physical network equipment in the data center. I=
t&#39;s<br>
an useful and clearly written document and it is ready for publication, aft=
er a<br>
number of minor issues and nits will be addressed.<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
1. There is one single mention of the scope being benchmarking of &#39;phys=
ical<br>
network equipment in the data center&#39;. I assume this is written as oppo=
sed to<br>
virtual networking equipment. This is not included in the title or repeated=
 any<br>
place else. I suggest to make more clear the scope by mentioning &#39;physi=
cal<br>
equipment&#39; at least once more, for example in the Introduction section.=
<br>
<br>
2. Section 1.2: I am a little concerned about adding additional interpretat=
ions<br>
to the keywords in RFC2119.<br>
<br>
Especially about:<br>
<br>
&#39;MAY: Comprehensive metric for the scenario described&#39;<br></blockqu=
ote><div><br></div><div><b><span style=3D"font-size:12.8px">Thank you, MAY =
provides an optional metric, I have addressed your comment</span>=C2=A0</b>=
</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>
MAY has a different meaning in 2119, and the fact that a metric is<br>
&#39;comprehensive&#39; (whatever this means) seems to me orthogonal to the=
 2119<br>
semantics. The proposed interpretation makes little sense to me, if<br>
&#39;comprehensive&#39; than why not required? or at least as a &#39;should=
&#39;?<br>
<br>
3. Section 6.2: &#39;The intensity of a microburst MAY be varied ...&#39; I=
t would be<br>
useful to make clear what is meant by &#39;intensity&#39;.<br></blockquote>=
<div><br></div><div><div style=3D"font-size:12.8px">The intensity of a micr=
oburst is defined in the definitions document [1] so i referenced it that w=
ay</div></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">
<br>
Nits/editorial comments:<br>
<br>
1. The different formatting of the references [1], [2], etc. vs. [RFC2119],=
<br>
etc. is slightly confusing. Unless there is some good reason I suggest to f=
ix<br>
this. Also use of references is inconsistent through the text, sometimes th=
ey<br>
are mentioned, sometimes they are not.<br></blockquote><div><br></div><div>=
Fixed it for [2] and [3], however kept [1] as [1], as this document is not =
an RFC yet.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
<br>
2. Section 2.2: &#39;Alternatively when a traffic generator CAN NOT be conn=
ected &#39;<br>
- this capitalization is not conformant to RFC2119.<br>
<br>
3. &#39;vlan ZZZ&#39; is not consistent with &#39;vlan X&#39; and &#39;vlan=
 Y&#39; previously used.<br>
<br>
4. Missing reference - RFC 6985<br>
<br>
5. Missing expansion and references for DSCP and COS<br>
<br>
6. Sections 3.3 and 6.3: s/number of iteration/number of iterations/<br>
<br>
7. The methodology (e.g. in section 5) makes an assumption that the DUT has=
 at<br>
least nine ports. This may be trivial in a DC, but it&#39;s worth being men=
tioned<br>
<br></blockquote><div><span style=3D"font-size:12.8px">Thanks added this in=
 section 2.3 as it was making more sense to be clarified there</span>=C2=A0=
</div></div><br></div></div>

--001a114760f854781a05518002c1--


From nobody Fri Jun  9 08:25:41 2017
Return-Path: <rharolde@umich.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 04F1E129B6D for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 08:25:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=umich.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 IbgMB619w4pY for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 08:25:28 -0700 (PDT)
Received: from mail-yb0-x233.google.com (mail-yb0-x233.google.com [IPv6:2607:f8b0:4002:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A5EE129B55 for <ietf@ietf.org>; Fri,  9 Jun 2017 08:25:26 -0700 (PDT)
Received: by mail-yb0-x233.google.com with SMTP id 202so16486767ybd.0 for <ietf@ietf.org>; Fri, 09 Jun 2017 08:25:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umich.edu; s=google-2016-06-03; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jHSWTteYqwWwJWraO8NTH/js/RuCO/kjOfXWQQEGOFk=; b=rO5Dmx5lgk/kHCCu3X2dwLHsJRk3yDv5RP5Ge0D5CaEdvYy5a65cH6k57NiMX9rHxM Tql+VNy3NLv+y7I5d/PCYp5UtIY7qjc7mfM9g3FAB2bx9KCv6RRFxIoHP4Whea+L8TE2 6LbgakE0kRzqs8qhy3IHW8wO0GDRrolskQJjGwR+Q53mSzUpsZbPhWrgELsyuHbWurVh s2MS/yKUMmpUxT8kV8QPDk/sGqtA+PDKicMa2ZU6Yab4WsU2+1Op4pVcKYOUsTeokp75 lQdXLHzWrQG1BISkM0HGcdXLZlFXp89ROO1CdK0gQDt1A9y5NTr67XuA4nGkINyKHZ+w 9+3w==
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=jHSWTteYqwWwJWraO8NTH/js/RuCO/kjOfXWQQEGOFk=; b=FIWaVnAvjZEn5fYFNvryBC6xbrswa1aEuaXVVA4ueFDmreJFDnK09UeMgRWNBYome9 nzdN5tAflOAzwbRGrCGluuvH1u+42ALvA53QIfZ41A2fhll1W/zgEy+9lPdfnAXdqYY7 SzmgKn7ZjqMmU40RtACiW10HOpYb75GOXVUUsQ5qK6Iu+So6WLbw8xQf/6SqjjNdKUqQ fPG6XXjO7v7Vl/07toIflT3p0C+SsVzbKZdUfSVBeami3otVz29wod8AK9fVS+OhNBGt M/QTR0/v65zQJ1zHSRcOPNy+3HUXxq0LxrQHb/PRbps0dgLAR8I8UJ1QS2PLB/ZTGzIy 7ceQ==
X-Gm-Message-State: AODbwcDZx66MhCFTiqBdBMfHLnxhI5kw1x+bcOExOSU5dK/7t1lHErOh Wn0vG0HCOzy/Y9ALLR9rQ+q5XM6D+PQxejQ=
X-Received: by 10.37.39.68 with SMTP id n65mr1453018ybn.91.1497021925447; Fri, 09 Jun 2017 08:25:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.221.77 with HTTP; Fri, 9 Jun 2017 08:25:24 -0700 (PDT)
In-Reply-To: <149678027581.3850.9197039878287017082.idtracker@ietfa.amsl.com>
References: <149678027581.3850.9197039878287017082.idtracker@ietfa.amsl.com>
From: Bob Harold <rharolde@umich.edu>
Date: Fri, 9 Jun 2017 11:25:24 -0400
Message-ID: <CA+nkc8AWrWe4+CQM6noRHk4_yxbafyshHH_WD53Q9SghB9=JEA@mail.gmail.com>
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-sutld-ps-05.txt> (Special-Use Domain Names Problem Statement) to Informational RFC
To: ietf@ietf.org
Cc: draft-ietf-dnsop-sutld-ps@ietf.org, IETF DNSOP WG <dnsop@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c134f8a166a6005518894e7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZG-dt-p3ah6Xo5Xk9NPMyyr0nfI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jun 2017 15:25:30 -0000

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

On Tue, Jun 6, 2017 at 4:17 PM, The IESG <iesg-secretary@ietf.org> wrote:

>
> The IESG has received a request from the Domain Name System Operations WG
> (dnsop) to consider the following document: - 'Special-Use Domain Names
> Problem Statement'
>   <draft-ietf-dnsop-sutld-ps-05.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-06-20. Exceptionally, comments may be
> sent to iesg@ietf.org instead. In either case, please retain the
> beginning of
> the Subject line to allow automated sorting.
>
> Abstract
>
>
>    The Special-Use Domain Names IANA registry policy defined in RFC 6761
>    has been shown through experience to present unanticipated
>    challenges.  This memo presents a list, intended to be comprehensive,
>    of the problems that have been identified.  In addition it reviews
>    the history of Domain Names and summarizes current IETF publications
>    and some publications from other organizations relating to Special-
>    Use Domain Names.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-sutld-ps/
>
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-ietf-dnsop-sutld-ps/ballot/
>
>
> No IPR declarations have been submitted directly on this I-D.


 Minor nit:

4.1.2.  Special-Use Domain Names

Last part of the last sentence:"they can only use the mDNS protocol be used
for resolving that Domain Name."
Looks like "be used" is redundant and should be removed.

-- 
Bob Harold

--94eb2c134f8a166a6005518894e7
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 Tue, Jun 6, 2017 at 4:17 PM, The IESG <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:iesg-secretary@ietf.org" target=3D"_blank">iesg-secretary@ietf.org</a=
>&gt;</span> wrote:<br><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"><b=
r>
The IESG has received a request from the Domain Name System Operations WG<b=
r>
(dnsop) to consider the following document: - &#39;Special-Use Domain Names=
<br>
Problem Statement&#39;<br>
=C2=A0 &lt;draft-ietf-dnsop-sutld-ps-05.<wbr>txt&gt; as Informational RFC<b=
r>
<br>
The IESG plans to make a decision in the next few weeks, and solicits final=
<br>
comments on this action. Please send substantive comments to the<br>
<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a> mailing lists by 2017-06=
-20. Exceptionally, comments may be<br>
sent to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a> instead. In eith=
er case, please retain the beginning of<br>
the Subject line to allow automated sorting.<br>
<br>
Abstract<br>
<br>
<br>
=C2=A0 =C2=A0The Special-Use Domain Names IANA registry policy defined in R=
FC 6761<br>
=C2=A0 =C2=A0has been shown through experience to present unanticipated<br>
=C2=A0 =C2=A0challenges.=C2=A0 This memo presents a list, intended to be co=
mprehensive,<br>
=C2=A0 =C2=A0of the problems that have been identified.=C2=A0 In addition i=
t reviews<br>
=C2=A0 =C2=A0the history of Domain Names and summarizes current IETF public=
ations<br>
=C2=A0 =C2=A0and some publications from other organizations relating to Spe=
cial-<br>
=C2=A0 =C2=A0Use Domain Names.<br>
<br>
<br>
<br>
<br>
The file can be obtained via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dnsop-sutld-ps/" rel=
=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>doc/dra=
ft-ietf-dnsop-sutld-ps/</a><br>
<br>
IESG discussion can be tracked via<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-dnsop-sutld-ps/ballo=
t/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/<wbr>=
doc/draft-ietf-dnsop-sutld-ps/<wbr>ballot/</a><br>
<br>
<br>
No IPR declarations have been submitted directly on this I-D.</blockquote><=
div><br></div><div>=C2=A0Minor nit:</div><div><br>4.1.2.=C2=A0 Special-Use =
Domain Names</div><div><br></div><div>Last part of the last sentence:&quot;=
they can only use the=C2=A0mDNS protocol be used for resolving that Domain =
Name.&quot;<br></div><div>Looks like &quot;be used&quot; is redundant and s=
hould be removed.</div><div><br></div><div>--=C2=A0</div><div>Bob Harold</d=
iv><div><br></div></div></div></div>

--94eb2c134f8a166a6005518894e7--


From nobody Fri Jun  9 08:31:40 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 27776129B6F for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 08:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fT318mI2Uoen for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 08:31:37 -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 9E996129B5E for <ietf@ietf.org>; Fri,  9 Jun 2017 08:31:37 -0700 (PDT)
Received: (qmail 25818 invoked from network); 9 Jun 2017 15:31:36 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 9 Jun 2017 15:31:36 -0000
Date: 9 Jun 2017 15:31:14 -0000
Message-ID: <20170609153114.9827.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: wireless geolocation
In-Reply-To: <m2efutna8d.wl-randy@psg.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N3RIdmeR2VfRu42IO_LC9gDL4Fo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jun 2017 15:31:39 -0000

>> So in classic IETF fashion, if this is something where someone wants
>> to start a wg or a BOF, it would be helpful if the scope of the
>> problem is very clearly defined.  :-)

Would it be useful to document the various ways the meeting network
gets geolocated so at least we have a reference for what's broken?

I'm thinking of an info RFC.

R's,
John


From nobody Fri Jun  9 09:22:16 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F35C124234 for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 09:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-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=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FQpwj0Jlu8ES for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 09:22:11 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0119.outbound.protection.outlook.com [104.47.1.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D86C5126C0F for <ietf@ietf.org>; Fri,  9 Jun 2017 09:22:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=b93h4cD+yNiNjrJq9EFiFsmLLFkXjVOYkLbfdADwsEk=; b=dTWQCECbz+shI18Xha7FrdlHmAePdmZ8m9VJAA9tuS69He/uLsM6OiJE0Upp+j6FQpA+gAyJA+qyB+HRezhLi3K3d7OlGGMssp6vXjYj01iCLvaE95Z8Va7cTPTZS/59wM1EBDZjft2MHf/xfuwfPVaEb5pcZSHfRcoEWN5GJZY=
Authentication-Results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.169.157.161) by DB5PR07MB1559.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::9) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1157.9; Fri, 9 Jun 2017 16:22:07 +0000
Message-ID: <01ed01d2e13c$13bff400$4001a8c0@gateway.2wire.net>
From: "tom p." <daedulus@btconnect.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>, "IETF discussion list" <ietf@ietf.org>, "Shishio Tsuchiya" <shtsuchi@arista.com>
References: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com> <cc4712b9-5922-2d1f-6c30-8add4ab60382@arista.com>
Subject: Re: Real DMARC damage
Date: Fri, 9 Jun 2017 17:00:59 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.169.157.161]
X-ClientProxiedBy: DB6PR1001CA0024.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:4:b7::34) To DB5PR07MB1559.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::9)
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: DB5PR07MB1559:
X-MS-Office365-Filtering-Correlation-Id: 0d6469f9-228f-40dd-d2c8-08d4af53accb
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(201703131423075)(201703031133081); SRVR:DB5PR07MB1559; 
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 3:6iWNbPjdKjsDGNdvptSONEHcY3Zs+IGJI53jmFxCHX4Cu4Z78a6Nv+PhooE+SJXwI4N14+l44kBlcxzX6fOT57kCbb1y6nt1wFeh2EpMcnJphStixNl+0aOiuIbSlNigrszGta0drMHwTwQ5Q7nBc4PsO8otDqHh1w/FD5mTl6xE4qseP0dbr2nX6tkLgCyDxsElbs8ykOAmMlQCplLPvS4jSpGLGzPOepB3iQpPnYe2T4mXaddFfMaCV3YM3W4Q86yxWSf9TG63PJtRfHhllx3Vlv/FmKuVXMVUWEbHZS4GX/KG58vCYeXlmJvKcWsPn3VW7JEeHeWNCUd3a9n8Sw==; 25:Vo/bqaQh7KQsMh8aIuXdASadnkgoQxkTWKcSlbusKyn17Ev0d6mx5A+1z/cKWFte4WJriXZ2/HA0Pp6QAu2SGgqwLMa3Y2Xvq/4+yvLpOheS/+pZSPY3k4x6AXI3M9GarCOfjM9ofOxFla8EaZz+eLnQ+9JS19ycsNER1dk4nZDwBjUrpYPEjTuVXKZqTahEE6IKyo2Nn9OyA2S/xDctgVdqcHGqrTFo86gqhfCbZfI39QXGPRFWRT7XbmNrnftYRlUHMhv9pG5D2pNSnvAvF2E7rK71IF3Zl2t4tyAvmrNle4vuY7CmLuOoFoM3f/NavO6C6cYdFq3jrj/0yLtDLu5AOwxd8ssY2zuevDCy9oqaPGrViLrnBT9TPytJKXPMPlxRb53QbzO48vuk13J3y56PpxJVhV+69LDeO0DB632O24sYEfxuaXzbQc8WXDCaMAC6CX6/MVGleZ6fEp1GmbZU/jlbUQH7sbs6HeCyT4M=
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 31:geiGp/v8gs7wgk7zB5udL2HfglwZhUP3JtCe/EJ2j2k+koVJCFNxqLmZSwQ95tLO0OWNYSUA2NcDaxdBEE9Tus9g8q4x4getzDT4mZSDwTOEfuSApi3BHyVWb1zzaskB26kt9Gg7sQiXNLkiDLA7hh0hrOkVE+fmI8lYrX1DUyjvT2b2aBjxCu8VfsKRtypbZ52cN97fycrLWa7pRnT1cr+OH8OKLFLcfgF3InUGPcme6yXJVh24aDqPsXsbvDqfht1GAho5xVc3emi4ZaDiow==; 20:4hO464SU7t9DVSPvfMe6aqVsms9OByuSk7650D01i/LYr9vQHUsrrkJrj3MN0/yZJk1QNXHe3/i3KOXcljNHDwpkLni9gi1TyFagYd+X+hXeK1M/wDLUQEqsibSXb/y4aCdpodq/hDPayJfc0q0DZ6Kwn0I+iHG/6C012Wq7pL8=
X-Microsoft-Antispam-PRVS: <DB5PR07MB15597DEFA75AE4C79FAFFEAFC6CE0@DB5PR07MB1559.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(149059832740258)(211936372134217)(201166117486090); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(100000703101)(100105400095)(10201501046)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123564025)(20161123560025)(20161123562025)(20161123555025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB5PR07MB1559; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB5PR07MB1559; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjVQUjA3TUIxNTU5OzQ6SVNnTXZlZ013em1TWEF6QTlRSmFHeXBNdGUr?= =?utf-8?B?Vm5QWkJKTmJCRTIzYWhwcG9YWDloaDdZd0JqeVZybjdwY3ZMQzZpc1p0amtV?= =?utf-8?B?eU5EVEFieWJZb0lFV21RTTUvbTA4MWl3S0dTcVpacVNkL2dSWFF3ZDdXQmYy?= =?utf-8?B?dU45OWZXT2RFQW55enZwZmJqdnorWjBXWXA5RlBTRjB3QWYvTElubjNyZEpR?= =?utf-8?B?L0RURzI2cVhYVlltOEZ6UUNOMkJVeTcwV3dGYUhGN0RLelBWY0xkVFgxd3dP?= =?utf-8?B?ZWlGdnJzM2NLYjZJcGNFeU1WdndzY05BSWZtTjg3VkZmdkp6QVVxaHFWRnZs?= =?utf-8?B?eHpoTVhnTFF3VHc3YlJWbFo4Zm1HU0dxbUg5djg0L0NINzFRakZTNnoySWMy?= =?utf-8?B?UVpmNFd0b1IwNGpzSnpjQWhGZ2srWUNxNmJ2ZkRMQTZrcEFrTEZsQjFWYnRZ?= =?utf-8?B?eXdsWFdCOXdHZkhjaHY2WUVCVXlXYXNxb2p1U1VmUy95bDV1MHFRR2pPdkJQ?= =?utf-8?B?azVFUVBYaVUwUFVrMDU4VWpyVmNla1M4akx4TmVMbHNhVjdqVllMWkFaZitt?= =?utf-8?B?Tk1Cc3hwRG05OEVkcjhKZHVxT3V3LzVYYUtHazVaOUlBb24wVXI1QURMRmpE?= =?utf-8?B?QUtKeTJYQzQ2SkdiQ3pybDJQek0vZ2RiL0tTblhzY3VtcllBSVhUYzRabm04?= =?utf-8?B?YnhQcjVzZi92My8wODN1cStvclBWVjdFY2dEenNCbjVRa25OckZ1NWp0TWtY?= =?utf-8?B?Z2ZKNkVPM0FZZDNPSUdQaTB1MmZjZXEzN3daUW1hRGJ6dE50cy8xM1pjN1dL?= =?utf-8?B?OXFHRGdFSHZyV0U0WHl1U0tzbnF1YlhVYnJJeWhUbCt2TTZoRXBVblZsTHJa?= =?utf-8?B?VUdwbnN3MS9EQ0M0cWEyc2dUMnBRUXBkVkxHbS9HMktncTBWQi8vWmNybkwv?= =?utf-8?B?SDZCaEpxSEtZS01SQXYwak1JTXM5eHQ2eVBYQllCSUE3UVZDTHYydUV6RDd5?= =?utf-8?B?R1dQR2JhUWMvQW5OV0IrOTM1NFBLYWU0QmhFRjJMcmVOQXloYUQvWFU1c05K?= =?utf-8?B?d1htQWwvS3BhUktoTG0rM0JjWmJpWFlBL2NkNzhCUXdnVjE4NVE1RER1ckFv?= =?utf-8?B?VzBpOGlmdkh1bWJ0eFZCWm5IaXlUZFdWcStKemJXK29aL0lRRmd0c3ZkeWhR?= =?utf-8?B?V1V1dXR2NE5qTzY0Q2ZJWmpKY1V4R3E1cU80azRlNnNPUGt6MlpVVzNQMzlX?= =?utf-8?B?UW9tQmU4MHZTMmNKbGtUMmp2WHNFcXM5VUQ5TG5aanF6RjUrVnk0ZjQweXc2?= =?utf-8?B?SkRJb2lvcTJoUktLeXQvc3lTZUFTa0lycjRraVdEUGNYbHpPeE92M3JUdDAw?= =?utf-8?B?WFk1SlRaVG9NbGRnY3RDSnlZM3NZbGY1b3Nsb0twRko1MVVDYlY1V3M4ZjhH?= =?utf-8?B?eEFreUpVTk9qNnp1Yk1IWHR2SkRDUGdJQzcwTXFrdWpDL09TemdQMDJWWVcx?= =?utf-8?B?bE82aXR4c2lWVVRVL0Jxck9KMis0dXVWN0tpNkdVSEVEV1RGS3lVTy9Edy9n?= =?utf-8?B?Z3ZqL1V5REQ0SzFoR0xMaE4vY2luYTlBVnkzVmRuekYrQTdUVnBRNTRPUXNY?= =?utf-8?B?LzVSYzFpTVZ2Q3JaR3drSVlRNWU2Zk1sWFFqYm9MUmF4TU93WkEvUU5NRGVF?= =?utf-8?Q?fct4IcThHGFAJhIlBl4/wkgCLFB0TVk52pERMm?=
X-Forefront-PRVS: 03333C607F
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(39850400002)(39400400002)(39860400002)(39840400002)(39450400003)(39410400002)(24454002)(13464003)(377454003)(45080400002)(53546009)(478600001)(33646002)(966005)(3846002)(61296003)(86362001)(81816999)(229853002)(81686999)(76176999)(23676002)(42186005)(62236002)(230700001)(47776003)(50986999)(44716002)(66066001)(6246003)(53936002)(6486002)(5660300001)(7116003)(6306002)(2906002)(84392002)(189998001)(9686003)(25786009)(305945005)(14496001)(7736002)(50226002)(6666003)(3480700004)(81166006)(8676002)(6496005)(4720700003)(38730400002)(74416001)(7726001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB5PR07MB1559; H:pc6; FPR:; SPF:None; MLV:sfv;  LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjVQUjA3TUIxNTU5OzIzOlUxVWFyUVU2eVRnRVVzM3pFVnhzV2k4aEtW?= =?utf-8?B?eDFHam9mbGs2NDRNNnp5RXlyQnREUkJDQy9qSWl6RDl4Mk0wUTY4TEhUU0pN?= =?utf-8?B?bkNCVUl6YWdTY0FrYnh0c3JRanJweW84RU0xUi93ZVI0ZXBPV1FQWS9RZ0s3?= =?utf-8?B?MjAvQU9xMG5SZDRSdmk4L1JPZjQ4T1diNC9VMWFZLzhFZG1YZGpuQmsxeThE?= =?utf-8?B?NWRXaER5bGZtTzBBNTQ5R0kwTkhEaG1LUTNvZWJZQTBLYTBMY1laaHlaV2VN?= =?utf-8?B?K1FkQ3VodlRhL2wrSlR6UVFJa3kxNHRXLzR5aVJvM1NpNjZjYzNVQW9xaGxU?= =?utf-8?B?MGdiRWFteFZ4bkFNL1NCK1FTY1VybVpFbWRpczdneG5MQlFMcUhJYTQxMnR3?= =?utf-8?B?S3VSVi93Wkh5cU1pSlRCVmlRdHQxMkZSczNRM0hucG9qUVF6V05xcnMvNDYx?= =?utf-8?B?YWZ6ZmNoT0JJQkE2WjV2S2Y2c1FadVkwMENjZGIxbmJsbzUyZFh1Y2NnSVdV?= =?utf-8?B?UHlrMG5GY1k1Wm5pOHVJTUQ0Z1EvMHBrYWFidnJrZVdyRnMvQU1yTTY0YUtx?= =?utf-8?B?SU84MnZrSm5ncHo0QndNRG9rc3VZSTJyS1ZKQnJiaGF5ZnVqT1BxQlpYY1NJ?= =?utf-8?B?bUxMZ0IxN3hnZWl1ZDM3cGtzKzVzN0VOeHVFNlRMdWpRTGlFL2JEMmxvNnFU?= =?utf-8?B?RkNYdWlmR2xWdWh2eG5hM2IyWTJNM0NWMWdHdmpmbnhyTFArT0IvZUhkU3FQ?= =?utf-8?B?VFRZd0xIYmJtZnZkLzFiRG9iS05QcDlWZ3p3YzJRT3QwUkxwemIyR1A1MmQx?= =?utf-8?B?MjZLNlFhdmtodFJ1alFqcHMxL2VDRFFIUWl4YXRlaE1UbUxDc1g3dC9GeFlH?= =?utf-8?B?OG0vdEVXRWNQRk5zdXFDWlJGNkNLZ0xnNW94ZDh2c09tbjk3VnFTQ016SEYw?= =?utf-8?B?U2piMDFFdzBiOCtLS1ljZDdwdWlXZHFRb2xFRXMvdXU2aFBGNit1TXlZSkxh?= =?utf-8?B?bFBEL3NkdldUdk93WkpZcFlqazJzaHFudFkyajNncnBkdWNPd0YwYVNGcWUw?= =?utf-8?B?NUVvNUtGZW1yVWVKUmMrYURJZEdGbGY4YnRRcXUvOXd5Qmt6SkhEeHMyYjhY?= =?utf-8?B?TXpVQ0dWcUl6T2lPQnlqbSs0RnN4RkxEQ3JUU0RBcTFGdnZWYVlFT2Q5d2hV?= =?utf-8?B?R1hBMlVETVp0UUxHa3VkV2R0R2pkcHVKb1FrRFBWaXlKbHJNQlJlSHdyMnVq?= =?utf-8?B?ZXRNdTdjekVQZTVNNEl4Q0krdjliT1p3Mis0R25wZnB2MWtMNlY3U01uZ0dS?= =?utf-8?B?MUlUb01BbGRGRWNZdnNXa292dTJMbmNac3J6dC9qMFoxSWR5YUllUHk4bDN1?= =?utf-8?B?YlVTSTJaMG5ncG12R28vdVJaTklGUWNvOHAybk9oT3VCL1lRS3J4c09pWTIw?= =?utf-8?B?RjNGQjVQTDdVREJmR2FHUG1rQ0tIbWQ3Mis5MlNSaU4wRC9VUlJ0ZXB6a0ZC?= =?utf-8?B?aFJnazVTTXBRNDBxRXBiQWlFS2VHTEp3N0JSblJYRXVwdWhTZFpOVGRpcjFC?= =?utf-8?B?bEM3UC84REpOanBKUzBtMDZnbGI5UGxDaFIwdGM5Z05QRHA0NTlIUW1pZGc4?= =?utf-8?B?TjZITmpNVXNyaDgxVHdZQVhBTkNIT0VFb2loSjF4OUl3Tyt4VHdqVzVSWkNI?= =?utf-8?B?eUJjY0xjQS9GcjJRMlpkY0dyQWxlQnhka3FzMVRUWDdUSW1obzl1TFFyT3Fz?= =?utf-8?B?SldEcXpkR1RKUVZHdDFvMjZhbW1WNS9HdzBTWWhPOTFTcnl5dk9na1RlREd4?= =?utf-8?Q?ZEjnDz5jb9a1X?=
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 6:khh0G+M1i+ddWwVlnj3wyrEUOA1bk8bfOV8alIKRKkHVPKvcV7Yw7I+Ed5d+0xmnUi/nS5NfHbyskTvVhd42HGTir7ACkzSRPNdnE/t9lnoGnO041AOH6nO8pnGzXEpHAvqApT0LXZearHXR+2uQsd6Twjg01/Q3Xyp0mxQcolCU2RL79Jco/MC5p/jrsVLORYetR9C5R4IfumLVbnHjsdsILsgiFqKZlYbCxCa4CFouf6KkDMD2dUgTTFTT/JdVQkIcmwvQVKLqpJg0qMUj5pNjlu+6w+za0exDFBE3ceBkoMms+QqlcYvdmj7r81ScximsfqsP6QewKc7FCkyFK0e0rp4ZoYlfado2wjZsnCAlvKkGxFREAl97ZBHASrTssJh+eBY78lHL+lFc/c8+zqcQ0vseMycgi518ijLcjfrc9czsdWn1T0ocPgj1vYw9xmLZ8v4QRPDZRps9AK5icvhzOWlDA3h9l9ysztWmEUUXj1yQVJ5KqWqqEheyXUlBOJ0yb/QeJ4h5jfQ3xreLdg==
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 5:6G0JbDHG0xOdveuqPqQIqdBvoNT2+ZXKF6Kx6pvgBDj20oIclVicbzw1OCSFX1JwuVWJCugIoz+KKosLat8PTCfkmJeIQEezB/QhWrs7nsM+yJm1x01dZ/H2ixSvyVfQhXBmE7z4GrXU2vg7+Z6sp0A4jgu73A5rQSNg4oBoxR4xfwsZi6be61WMYVx6AB08zIGksvWLuTAeM0/a7nRJAOOG1rXapEXOZPHubHZ+572wMmaOABxn0ThoGWOD63NVqJsvc7vDaZtF0eK3rBrCIfceZmHRL5LVN4nFIihspLi08b+ENh74g1Tiehd+j2vVJrSAZg2I5Ihl3Iul7aGbWfyJfskY8gGuN/UTiTIGlichLA8UzxxPZjiBypgcFu3Jmx/UHty+A0VrHnCYtDNcdyDTUpo3gewvSqBLDzoXlXN9UynEDTh9m18NAXFMOxALg3Fp/1qmz/oPe3ageTP3ysAVD6xtrkyVPO6Pbs7h+fMb6QBPTqBMc/7oh1sR5+eL; 24:rB03pYaZEoQkVPdyfDxYjyZexJf0Hrf5gf3U8yYgnnfTa9nKImOhPbFcAmuIAUNLzdBL3ugQU0o+MMMLGEUGZc/vyQdEDwodlIFHLgF70rI=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB5PR07MB1559; 7:rYb4wYv++PliG9bB/vhM/HxZA4M0O9Q/Tudja9AqsQd+vHgNb82J0p9PAXg/IO7NA6JXhaYJfh1np7SoV/qrueQ82v164u5hE8Dm8q0Tirl5GxPgPI+Ym5J+PeC5L81J1xcs/rhI/m/D8ZNPI6ldMm8CjL55B5I2YYFSH6Ixt5l0Yzil48zsL8GVlawkyTLdn8t002fYfbCR4MrLp3ECO/WzH7SjB+AtRGJCZODlDZMoHRQ0rEl0BS8F66K9j4OgSoaAvTUVebVPpeVwEMQ7KG4PtEdZ6wXET2oaInv6K7xsZrwspoSFFDJoIerqAvKa6t8tNQyKlGJKS2SFDu862w==
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 09 Jun 2017 16:22:07.9611 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1559
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yU4fvUED94qMbIAQYYIai9QJ0NU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jun 2017 16:22:14 -0000

Resurrecting an old thread ....

Something just changed.  In the past week, my ESP has decided that
anything with a domain name of 'google.com' in 'From:' is junk and
should not be
forwarded to me.

Previously, the only such mail to be wrongly classified as junk was that
from a
rival manufacturer (which had a certain logic to it:-).

I had been wondering why the discussion on the IPv6 list about 64-bit
boundaries was so disjointed and I now see that half of it, the
google.com half, was no longer reaching me.

AFAIK there is nothing I can do to influence the ESP to change its mind.
I have been reclassifying individual e-mail from that other manufacturer
as not-junk for years and my ESP takes not a blind bit of notice.

So yes, real damage to the IETF.

Tom Petch


----- Original Message -----
From: "Shishio Tsuchiya" <shtsuchi@arista.com>
To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>; "IETF discussion
list" <ietf@ietf.org>
Sent: Monday, May 01, 2017 3:42 AM

> As far as I know,
> google.com
> microsoft.com
> yahoo.com
> aol.com
> are already p=reject
>
> arista.com is p=quarantine.
>
> I think google.com is one of great contributor of ietf mailing list
but
> sometimes old mailing list suspect the mail as spam .
> I recovered some mail from my spam folder.
> I hope the mailman update to new one.
> https://wiki.list.org/DEV/DMARC
>
> Does this mail also suspect spam?
>
> Regards,
> -Shishio
>
>
> On 2017/04/30 6:01, Brian E Carpenter wrote:
> > Am I the only IETF list admin who's had to deal with genuine DMARC
damage today?
> >
> > gen-art@ietf.org had four subscriptions suspended for excessive
bounces, all caused
> > by mail from one participant whose sending domain has published a
p=reject policy
> >
> > Bizarrely, one of the subscriptions disabled was @gmane.org. It's a
very strange
> > choice for them to respect p=reject.
> >
> > Regards
> >    Brian Carpenter
> >
> >
> >
>


From nobody Fri Jun  9 09:40:24 2017
Return-Path: <MHammer@ag.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA879128799 for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 09:40:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCf7ltC5hVNy for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 09:40:21 -0700 (PDT)
Received: from agwhqht.amgreetings.com (agwhqht.amgreetings.com [207.58.192.41]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2F313124234 for <ietf@ietf.org>; Fri,  9 Jun 2017 09:40:21 -0700 (PDT)
Received: from USCLES544.agna.amgreetings.com ([fe80::f5de:4c30:bc26:d70a]) by USCLES531.agna.amgreetings.com ([::1]) with mapi id 14.03.0266.001;  Fri, 9 Jun 2017 12:40:20 -0400
From: "MH Michael Hammer (5304)" <MHammer@ag.com>
To: tom p. <daedulus@btconnect.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, IETF discussion list <ietf@ietf.org>, "Shishio Tsuchiya" <shtsuchi@arista.com>
Subject: RE: Real DMARC damage
Thread-Topic: Real DMARC damage
Thread-Index: AQHSwSwvGcQ+xdS/ykSF5e8th1rvUKHfCfkAgD3s3EqAAAS0UA==
Date: Fri, 9 Jun 2017 16:40:19 +0000
Message-ID: <CE39F90A45FF0C49A1EA229FC9899B0537173A17@USCLES544.agna.amgreetings.com>
References: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com> <cc4712b9-5922-2d1f-6c30-8add4ab60382@arista.com> <01ed01d2e13c$13bff400$4001a8c0@gateway.2wire.net>
In-Reply-To: <01ed01d2e13c$13bff400$4001a8c0@gateway.2wire.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.144.6.107]
x-kse-attachmentfiltering-interceptor-info: protection disabled
x-kse-serverinfo: USCLES531.agna.amgreetings.com, 9
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean, bases: 6/9/2017 3:48:00 PM
x-kse-dlp-scaninfo: Skipped
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NlDcqmXzvvsKHm51SOpGbSH5StE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jun 2017 16:40:24 -0000

VG9tLA0KDQpBYnNlbnQgcHJvdmlkaW5nIGFueSBvdGhlciBkYXRhIHBvaW50cywgaG93IGRvZXMg
dGhpcyB0aWUgaW4gd2l0aCBETUFSQyBkb2luZyBkYW1hZ2U/IA0KDQpNaWtlDQoNCj4gLS0tLS1P
cmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaWV0ZiBbbWFpbHRvOmlldGYtYm91bmNlc0Bp
ZXRmLm9yZ10gT24gQmVoYWxmIE9mIHRvbSBwLg0KPiBTZW50OiBGcmlkYXksIEp1bmUgMDksIDIw
MTcgMTI6MDEgUE0NCj4gVG86IEJyaWFuIEUgQ2FycGVudGVyOyBJRVRGIGRpc2N1c3Npb24gbGlz
dDsgU2hpc2hpbyBUc3VjaGl5YQ0KPiBTdWJqZWN0OiBSZTogUmVhbCBETUFSQyBkYW1hZ2UNCj4g
DQo+IFJlc3VycmVjdGluZyBhbiBvbGQgdGhyZWFkIC4uLi4NCj4gDQo+IFNvbWV0aGluZyBqdXN0
IGNoYW5nZWQuICBJbiB0aGUgcGFzdCB3ZWVrLCBteSBFU1AgaGFzIGRlY2lkZWQgdGhhdCBhbnl0
aGluZw0KPiB3aXRoIGEgZG9tYWluIG5hbWUgb2YgJ2dvb2dsZS5jb20nIGluICdGcm9tOicgaXMg
anVuayBhbmQgc2hvdWxkIG5vdCBiZQ0KPiBmb3J3YXJkZWQgdG8gbWUuDQo+IA0KPiBQcmV2aW91
c2x5LCB0aGUgb25seSBzdWNoIG1haWwgdG8gYmUgd3JvbmdseSBjbGFzc2lmaWVkIGFzIGp1bmsg
d2FzIHRoYXQgZnJvbSBhDQo+IHJpdmFsIG1hbnVmYWN0dXJlciAod2hpY2ggaGFkIGEgY2VydGFp
biBsb2dpYyB0byBpdDotKS4NCj4gDQo+IEkgaGFkIGJlZW4gd29uZGVyaW5nIHdoeSB0aGUgZGlz
Y3Vzc2lvbiBvbiB0aGUgSVB2NiBsaXN0IGFib3V0IDY0LWJpdA0KPiBib3VuZGFyaWVzIHdhcyBz
byBkaXNqb2ludGVkIGFuZCBJIG5vdyBzZWUgdGhhdCBoYWxmIG9mIGl0LCB0aGUgZ29vZ2xlLmNv
bQ0KPiBoYWxmLCB3YXMgbm8gbG9uZ2VyIHJlYWNoaW5nIG1lLg0KPiANCj4gQUZBSUsgdGhlcmUg
aXMgbm90aGluZyBJIGNhbiBkbyB0byBpbmZsdWVuY2UgdGhlIEVTUCB0byBjaGFuZ2UgaXRzIG1p
bmQuDQo+IEkgaGF2ZSBiZWVuIHJlY2xhc3NpZnlpbmcgaW5kaXZpZHVhbCBlLW1haWwgZnJvbSB0
aGF0IG90aGVyIG1hbnVmYWN0dXJlciBhcw0KPiBub3QtanVuayBmb3IgeWVhcnMgYW5kIG15IEVT
UCB0YWtlcyBub3QgYSBibGluZCBiaXQgb2Ygbm90aWNlLg0KPiANCj4gU28geWVzLCByZWFsIGRh
bWFnZSB0byB0aGUgSUVURi4NCj4gDQo+IFRvbSBQZXRjaA0KPiANCj4gDQo+IC0tLS0tIE9yaWdp
bmFsIE1lc3NhZ2UgLS0tLS0NCj4gRnJvbTogIlNoaXNoaW8gVHN1Y2hpeWEiIDxzaHRzdWNoaUBh
cmlzdGEuY29tPg0KPiBUbzogIkJyaWFuIEUgQ2FycGVudGVyIiA8YnJpYW4uZS5jYXJwZW50ZXJA
Z21haWwuY29tPjsgIklFVEYgZGlzY3Vzc2lvbiBsaXN0Ig0KPiA8aWV0ZkBpZXRmLm9yZz4NCj4g
U2VudDogTW9uZGF5LCBNYXkgMDEsIDIwMTcgMzo0MiBBTQ0KPiANCj4gPiBBcyBmYXIgYXMgSSBr
bm93LA0KPiA+IGdvb2dsZS5jb20NCj4gPiBtaWNyb3NvZnQuY29tDQo+ID4geWFob28uY29tDQo+
ID4gYW9sLmNvbQ0KPiA+IGFyZSBhbHJlYWR5IHA9cmVqZWN0DQo+ID4NCj4gPiBhcmlzdGEuY29t
IGlzIHA9cXVhcmFudGluZS4NCj4gPg0KPiA+IEkgdGhpbmsgZ29vZ2xlLmNvbSBpcyBvbmUgb2Yg
Z3JlYXQgY29udHJpYnV0b3Igb2YgaWV0ZiBtYWlsaW5nIGxpc3QNCj4gYnV0DQo+ID4gc29tZXRp
bWVzIG9sZCBtYWlsaW5nIGxpc3Qgc3VzcGVjdCB0aGUgbWFpbCBhcyBzcGFtIC4NCj4gPiBJIHJl
Y292ZXJlZCBzb21lIG1haWwgZnJvbSBteSBzcGFtIGZvbGRlci4NCj4gPiBJIGhvcGUgdGhlIG1h
aWxtYW4gdXBkYXRlIHRvIG5ldyBvbmUuDQo+ID4gaHR0cHM6Ly93aWtpLmxpc3Qub3JnL0RFVi9E
TUFSQw0KPiA+DQo+ID4gRG9lcyB0aGlzIG1haWwgYWxzbyBzdXNwZWN0IHNwYW0/DQo+ID4NCj4g
PiBSZWdhcmRzLA0KPiA+IC1TaGlzaGlvDQo+ID4NCj4gPg0KPiA+IE9uIDIwMTcvMDQvMzAgNjow
MSwgQnJpYW4gRSBDYXJwZW50ZXIgd3JvdGU6DQo+ID4gPiBBbSBJIHRoZSBvbmx5IElFVEYgbGlz
dCBhZG1pbiB3aG8ncyBoYWQgdG8gZGVhbCB3aXRoIGdlbnVpbmUgRE1BUkMNCj4gZGFtYWdlIHRv
ZGF5Pw0KPiA+ID4NCj4gPiA+IGdlbi1hcnRAaWV0Zi5vcmcgaGFkIGZvdXIgc3Vic2NyaXB0aW9u
cyBzdXNwZW5kZWQgZm9yIGV4Y2Vzc2l2ZQ0KPiBib3VuY2VzLCBhbGwgY2F1c2VkDQo+ID4gPiBi
eSBtYWlsIGZyb20gb25lIHBhcnRpY2lwYW50IHdob3NlIHNlbmRpbmcgZG9tYWluIGhhcyBwdWJs
aXNoZWQgYQ0KPiBwPXJlamVjdCBwb2xpY3kNCj4gPiA+DQo+ID4gPiBCaXphcnJlbHksIG9uZSBv
ZiB0aGUgc3Vic2NyaXB0aW9ucyBkaXNhYmxlZCB3YXMgQGdtYW5lLm9yZy4gSXQncyBhDQo+IHZl
cnkgc3RyYW5nZQ0KPiA+ID4gY2hvaWNlIGZvciB0aGVtIHRvIHJlc3BlY3QgcD1yZWplY3QuDQo+
ID4gPg0KPiA+ID4gUmVnYXJkcw0KPiA+ID4gICAgQnJpYW4gQ2FycGVudGVyDQo+ID4gPg0KPiA+
ID4NCj4gPiA+DQo+ID4NCg0K


From nobody Fri Jun  9 09:49:46 2017
Return-Path: <mcr@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 A35AB127419 for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 09:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wv1bW8ENgSaf for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 09:49:43 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3B6B124234 for <ietf@ietf.org>; Fri,  9 Jun 2017 09:49:42 -0700 (PDT)
Received: from dooku.sandelman.ca (CPE84948c92cd71-CM84948c92cd70.cpe.net.cable.rogers.com [173.35.93.96]) by relay.sandelman.ca (Postfix) with ESMTPS id A02761F906; Fri,  9 Jun 2017 16:49:41 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 47CC685C; Fri,  9 Jun 2017 12:49:40 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "John Levine" <johnl@taugh.com>
cc: ietf@ietf.org
Subject: Re: wireless geolocation
In-reply-to: <20170609153114.9827.qmail@ary.lan>
References: <20170609153114.9827.qmail@ary.lan>
Comments: In-reply-to "John Levine" <johnl@taugh.com> message dated "09 Jun 2017 15:31:14 -0000."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature"
Date: Fri, 09 Jun 2017 12:49:40 -0400
Message-ID: <27214.1497026980@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/og1Q-Y9N9JMkapWjS5J2hAugogU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jun 2017 16:49:45 -0000

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


John Levine <johnl@taugh.com> wrote:
    >>> So in classic IETF fashion, if this is something where someone wants
    >>> to start a wg or a BOF, it would be helpful if the scope of the
    >>> problem is very clearly defined.  :-)

    > Would it be useful to document the various ways the meeting network
    > gets geolocated so at least we have a reference for what's broken?

    > I'm thinking of an info RFC.

I think so.
    "A survey of failure cases for IP and BSSID based geolocation"
or maybe you can work in the word "Tragedy".
(cf: https://www.goodreads.com/book/show/555377.The_Tragedy_of_the_Moon )

I wonder if AMS runs over roaving conferences and could provide contacts to
others...


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




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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJZOtGkAAoJEJVM4Vb9/EKQdqcIAJygbDNUYIbgMayLbCyBGFSg
XOAVFzOogA9B6CEyX3F8mvnSsLIblajXVOyhLKjExr0TlmHRi/qxdc480RPaAjEo
Zx+1mgJFyMXW0w4u2BL1XBX/XvOBaBaFYFG5yQ0TA4LgILMa4m0pFSCtnnNKPbEu
KmPBVnOxIm9tUrnUNMqOUknp4yP48qsvRNWuS4pTHP/ag6vaRUXcZMqSYoomMjRY
0l/N2FwSwHqG5Tm19FMdg0ynzN98AxrEQK5Gb0w1Ey7yie4G+B7/GsSzyFS6MIhI
94tcIH6jWWF/xmO9FmOcvBn+zG/Yahciy89nQAm0m8Chs+RVh6MC8eTVwV0Zkng=
=NrcH
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Jun  9 13:48: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 2822D1292F4 for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 13:48: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, 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 9cog78ULgyje for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 13:48:44 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EAFF129406 for <ietf@ietf.org>; Fri,  9 Jun 2017 13:48:44 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id a70so29881281pge.3 for <ietf@ietf.org>; Fri, 09 Jun 2017 13:48:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=UzQnpWdqFOjn7ExkwvQwcvkjSqufnXTBF7AF+NbPwis=; b=L7cvmCO6Cu0NdrSAK2ilzncYUIrxOoEKKdrZNAV5M4qgoDwCERbTpyFaNUATxu7h1D BXnfNqX8VAViFh4YIb4hAfvkcO+Bg5mDhlqPUVbmfJi8iqv9QcZsBwnMsvld5ECXZi42 f36U/9LQgyEGUwLawaXgbYry16Q4e3qqJU0a0871LeeEqz3eBXon9/+FFdGZ3ytLWl+f JqUVM6aaWMurM/pl1c7kFQRi1RV6EpNB7iJupIIwN0JJHsMXrsta5a9SGfZcpTm+FB9F nWjCEQhIEiQtm+DI9F39FzcF/jZx3HlpqJR+26UK0vLkkYTxBIakUxi2hAVe78dZVu1/ ELSg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=UzQnpWdqFOjn7ExkwvQwcvkjSqufnXTBF7AF+NbPwis=; b=cOM/41QUp0l3gLo21zD2a/ywj/5ZGWEhdTpqE45ah9FIYNfzwJelHRju6g1wley6Cx 7nmNoTxXmFcUH2ih8lnAdy+5GoLJwewvO77mJVk2Bt58A6PRaSdqRnU6VnLQFEKVdV42 6TaYdT3/Y8lZvWU23vEnbpATh/FYGvIDTHSTKcCOuLq6rEg31SzH5+6JoLUFxDakfrfz IrPGgirUJWMTPzJzLvtH95MSgiyeVXoijiwvIu2Vg0j9Hs2LPKnQ4jpUcuY2msBjGpQv JuM7oinbJoOlTXyYIYekhncUtte5n1w1768byaxILm/+vuovR8MoMYmRYyC4y+gAF8bm NC6g==
X-Gm-Message-State: AODbwcAduOkEl4WTB8YAHsrmSNMeTw1Ph42xZPAZoVm3ugl+aUMt95rd /RWrl6k+NGp03Q==
X-Received: by 10.84.128.195 with SMTP id a61mr20078095pla.130.1497041323680;  Fri, 09 Jun 2017 13:48:43 -0700 (PDT)
Received: from [192.168.178.21] ([118.148.119.180]) by smtp.gmail.com with ESMTPSA id g78sm4875841pfb.122.2017.06.09.13.48.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 09 Jun 2017 13:48:43 -0700 (PDT)
Subject: Re: Real DMARC damage
To: "MH Michael Hammer (5304)" <MHammer@ag.com>, "tom p." <daedulus@btconnect.com>, IETF discussion list <ietf@ietf.org>, Shishio Tsuchiya <shtsuchi@arista.com>
References: <a3ca1374-663a-7f0b-6218-23ce2fda73aa@gmail.com> <cc4712b9-5922-2d1f-6c30-8add4ab60382@arista.com> <01ed01d2e13c$13bff400$4001a8c0@gateway.2wire.net> <CE39F90A45FF0C49A1EA229FC9899B0537173A17@USCLES544.agna.amgreetings.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <ad8e98ed-abb2-3965-c966-647400de567a@gmail.com>
Date: Sat, 10 Jun 2017 08:48:49 +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: <CE39F90A45FF0C49A1EA229FC9899B0537173A17@USCLES544.agna.amgreetings.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/VJLCEqzTaiox6-3HWFetkqEybk4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 09 Jun 2017 20:48:46 -0000

On 10/06/2017 04:40, MH Michael Hammer (5304) wrote:
> Tom,
> 
> Absent providing any other data points, how does this tie in with DMARC doing damage? 

Hard to tell without looking at the detailed mail headers after
btconnect has classified a message as junk.

    Brian

> 
> Mike
> 
>> -----Original Message-----
>> From: ietf [mailto:ietf-bounces@ietf.org] On Behalf Of tom p.
>> Sent: Friday, June 09, 2017 12:01 PM
>> To: Brian E Carpenter; IETF discussion list; Shishio Tsuchiya
>> Subject: Re: Real DMARC damage
>>
>> Resurrecting an old thread ....
>>
>> Something just changed.  In the past week, my ESP has decided that anything
>> with a domain name of 'google.com' in 'From:' is junk and should not be
>> forwarded to me.
>>
>> Previously, the only such mail to be wrongly classified as junk was that from a
>> rival manufacturer (which had a certain logic to it:-).
>>
>> I had been wondering why the discussion on the IPv6 list about 64-bit
>> boundaries was so disjointed and I now see that half of it, the google.com
>> half, was no longer reaching me.
>>
>> AFAIK there is nothing I can do to influence the ESP to change its mind.
>> I have been reclassifying individual e-mail from that other manufacturer as
>> not-junk for years and my ESP takes not a blind bit of notice.
>>
>> So yes, real damage to the IETF.
>>
>> Tom Petch
>>
>>
>> ----- Original Message -----
>> From: "Shishio Tsuchiya" <shtsuchi@arista.com>
>> To: "Brian E Carpenter" <brian.e.carpenter@gmail.com>; "IETF discussion list"
>> <ietf@ietf.org>
>> Sent: Monday, May 01, 2017 3:42 AM
>>
>>> As far as I know,
>>> google.com
>>> microsoft.com
>>> yahoo.com
>>> aol.com
>>> are already p=reject
>>>
>>> arista.com is p=quarantine.
>>>
>>> I think google.com is one of great contributor of ietf mailing list
>> but
>>> sometimes old mailing list suspect the mail as spam .
>>> I recovered some mail from my spam folder.
>>> I hope the mailman update to new one.
>>> https://wiki.list.org/DEV/DMARC
>>>
>>> Does this mail also suspect spam?
>>>
>>> Regards,
>>> -Shishio
>>>
>>>
>>> On 2017/04/30 6:01, Brian E Carpenter wrote:
>>>> Am I the only IETF list admin who's had to deal with genuine DMARC
>> damage today?
>>>>
>>>> gen-art@ietf.org had four subscriptions suspended for excessive
>> bounces, all caused
>>>> by mail from one participant whose sending domain has published a
>> p=reject policy
>>>>
>>>> Bizarrely, one of the subscriptions disabled was @gmane.org. It's a
>> very strange
>>>> choice for them to respect p=reject.
>>>>
>>>> Regards
>>>>    Brian Carpenter
>>>>
>>>>
>>>>
>>>
> 


From nobody Fri Jun  9 17:23:48 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 3E2251200FC for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 17:23:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ZxxQMP5cweI4 for <ietf@ietfa.amsl.com>; Fri,  9 Jun 2017 17:23:43 -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 70D40120454 for <ietf@ietf.org>; Fri,  9 Jun 2017 17:23:43 -0700 (PDT)
Received: (qmail 78330 invoked from network); 10 Jun 2017 00:23:42 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 10 Jun 2017 00:23:42 -0000
Date: 10 Jun 2017 00:23:20 -0000
Message-ID: <20170610002320.10969.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Subject: Re: Real DMARC damage
In-Reply-To: <CE39F90A45FF0C49A1EA229FC9899B0537173A17@USCLES544.agna.amgreetings.com>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tt0-RNn8PvO4J1QXepLoQHc1lfE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jun 2017 00:23:45 -0000

In article <CE39F90A45FF0C49A1EA229FC9899B0537173A17@USCLES544.agna.amgreetings.com> you write:
>Tom,
>
>Absent providing any other data points, how does this tie in with DMARC doing damage?

Google's "p=reject" makes mailing list mail from Google people disappear.  But you knew that.

On the other hand, it is true that they've been publishing p=reject
for quite a while so it's not obvious why some mail provider would
just start paying attention now.

R's,
John


From nobody Sat Jun 10 08:28:18 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 2F405129437; Sat, 10 Jun 2017 08:28:03 -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 1RmU7x4qxKK9; Sat, 10 Jun 2017 08:28:00 -0700 (PDT)
Received: from mail-qk0-x22c.google.com (mail-qk0-x22c.google.com [IPv6:2607:f8b0:400d:c09::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6A1A1200E5; Sat, 10 Jun 2017 08:28:00 -0700 (PDT)
Received: by mail-qk0-x22c.google.com with SMTP id d14so14867990qkb.1; Sat, 10 Jun 2017 08:28:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uA4EcL4Plhm1/Af6UUXZTzs4HmJ0cTgYxzmPEml63s4=; b=O1pI0YeVMjxy86XzjJicapWld37Gs9pif0aQtBP5lROdUYxOyL0B62VLKfe1l2v0sm Oa25sucd9IJRFHcsKqn3YOdlAcYfqXFv9AYnnQMI1jmPwzG8z5vdFk1/LYYE2N9gfW4j 5Km63mYIYUA7m0Tlv+TZ4r180CKMKWa2sayQ4bzHBUlsMxe2yWjRE10f6yKm6tCVqeN3 TlduPiSONBUvjTJyDbMVlnm8Fj2M3jE4+sYLe81Gmc/Fd5idLXoGEw5Q322TJb/iQ2a9 x/rTz9Dqu5dcr9Ep0k4eI1oAm30pLWfrme602Hi4fYfSsau811wkeQxLAOMHL/ke1Z8p Sd3Q==
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=uA4EcL4Plhm1/Af6UUXZTzs4HmJ0cTgYxzmPEml63s4=; b=Sofixyc4C1ZCBDiF+/kP50zu5SAtTHZkVOw1HVvCMwUmo5bKpmCoMf/ghb3ckYOQWH Q+ajF2ePZydTrVBQCXYCv/pQYP3U/a/vRPppbNGlIKPlm9k6k6IHR+vi0JA6yzi4g/mT ReNNtIOhJrOXT10gorAaarCVZo8SoREOie9kCOefjaUrAc6ukn8mkdoK8rb1o3GUpgZq 9dAl2lEX2IUZoApEYEWmuGsGLR7RQd2SYb7WctiEqJyZAWYLi3g+s6fPwY63KSErfEzI wfGVlV3Yjc8XwUtXwNh4WwDxk0IguiujpBmraRYu9DgmOktBoUHSNFKR5ohDdGvPEDg0 4mfA==
X-Gm-Message-State: AKS2vOwjHcRYqoIzUpc+d8hrBekPhGrIW3c1oJTMeuT5ZNkkL/aI67Pc 4qWoHzOPU7Qpr6Sq/u3K4i3l9emNyg==
X-Received: by 10.55.159.13 with SMTP id i13mr8952731qke.150.1497108479870; Sat, 10 Jun 2017 08:27:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.31.101 with HTTP; Sat, 10 Jun 2017 08:27:59 -0700 (PDT)
In-Reply-To: <CALTEt=DUhEVgSvYN+2XYUR8Ddq5n8HJtZW2RNj3DV3rSgH0YKQ@mail.gmail.com>
References: <149692498024.25760.14056448148418579949@ietfa.amsl.com> <CALTEt=DUhEVgSvYN+2XYUR8Ddq5n8HJtZW2RNj3DV3rSgH0YKQ@mail.gmail.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Sat, 10 Jun 2017 18:27:59 +0300
Message-ID: <CAFgnS4Vstv9zyg9rE4-K-q-6GH-P6noXCmoOLvdjTY+dU_uRHw@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-bmwg-dcbench-methodology-07
To: Lucien Avramov <lucienav@google.com>
Cc: gen-art <gen-art@ietf.org>, draft-ietf-bmwg-dcbench-methodology.all@ietf.org,  ietf <ietf@ietf.org>, bmwg@ietf.org
Content-Type: multipart/alternative; boundary="001a114d8aa0220ec305519cbbdd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7dPE8o0GqoAmw7tHM9WgRH2LIWo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jun 2017 15:28:03 -0000

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

Hi,

All answers are acceptable. Thanks for addressing my comments.

Regards,

Dan


On Fri, Jun 9, 2017 at 8:11 AM, Lucien Avramov <lucienav@google.com> wrote:

> Hi Dan,
>
> Thank you very much for the comments. I addressed them and published
> version -09.
>
> Inline are some the comments / answer to your feedback. The parts without
> answers mean they have been addressed.
>
> Again, thank you for spending the time to read this in this fine detail.
>
> Lucien
>
>
>
> On Thu, Jun 8, 2017 at 5:29 AM, Dan Romascanu <dromasca@gmail.com> wrote:
>
>> 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-bmwg-dcbench-methodology-??
>> Reviewer: Dan Romascanu
>> Review Date: 2017-06-08
>> IETF LC End Date: 2017-06-13
>> IESG Telechat date: Not scheduled for a telechat
>>
>> Summary:
>>
>> This Informational I-D describes test and evaluation methodology and
>> measurement techniques for physical network equipment in the data center.
>> It's
>> an useful and clearly written document and it is ready for publication,
>> after a
>> number of minor issues and nits will be addressed.
>>
>> Major issues:
>>
>> Minor issues:
>>
>> 1. There is one single mention of the scope being benchmarking of
>> 'physical
>> network equipment in the data center'. I assume this is written as
>> opposed to
>> virtual networking equipment. This is not included in the title or
>> repeated any
>> place else. I suggest to make more clear the scope by mentioning 'physical
>> equipment' at least once more, for example in the Introduction section.
>>
>> 2. Section 1.2: I am a little concerned about adding additional
>> interpretations
>> to the keywords in RFC2119.
>>
>> Especially about:
>>
>> 'MAY: Comprehensive metric for the scenario described'
>>
>
> *Thank you, MAY provides an optional metric, I have addressed your
> comment *
>
>>
>> MAY has a different meaning in 2119, and the fact that a metric is
>> 'comprehensive' (whatever this means) seems to me orthogonal to the 2119
>> semantics. The proposed interpretation makes little sense to me, if
>> 'comprehensive' than why not required? or at least as a 'should'?
>>
>> 3. Section 6.2: 'The intensity of a microburst MAY be varied ...' It
>> would be
>> useful to make clear what is meant by 'intensity'.
>>
>
> The intensity of a microburst is defined in the definitions document [1]
> so i referenced it that way
>
>
>>
>> Nits/editorial comments:
>>
>> 1. The different formatting of the references [1], [2], etc. vs.
>> [RFC2119],
>> etc. is slightly confusing. Unless there is some good reason I suggest to
>> fix
>> this. Also use of references is inconsistent through the text, sometimes
>> they
>> are mentioned, sometimes they are not.
>>
>
> Fixed it for [2] and [3], however kept [1] as [1], as this document is not
> an RFC yet.
>
>
>>
>> 2. Section 2.2: 'Alternatively when a traffic generator CAN NOT be
>> connected '
>> - this capitalization is not conformant to RFC2119.
>>
>> 3. 'vlan ZZZ' is not consistent with 'vlan X' and 'vlan Y' previously
>> used.
>>
>> 4. Missing reference - RFC 6985
>>
>> 5. Missing expansion and references for DSCP and COS
>>
>> 6. Sections 3.3 and 6.3: s/number of iteration/number of iterations/
>>
>> 7. The methodology (e.g. in section 5) makes an assumption that the DUT
>> has at
>> least nine ports. This may be trivial in a DC, but it's worth being
>> mentioned
>>
>> Thanks added this in section 2.3 as it was making more sense to be
> clarified there
>
>

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

<div dir=3D"ltr"><div><div><div>Hi,<br><br></div>All answers are acceptable=
. Thanks for addressing my comments. <br><br></div>Regards,<br><br></div>Da=
n<br><br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On=
 Fri, Jun 9, 2017 at 8:11 AM, Lucien Avramov <span dir=3D"ltr">&lt;<a href=
=3D"mailto:lucienav@google.com" target=3D"_blank">lucienav@google.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Hi Dan,=
=C2=A0<div><br></div><div>Thank you very much for the comments. I addressed=
 them and published version -09.=C2=A0</div><div><br></div><div>Inline are =
some the comments / answer to your feedback. The parts without answers mean=
 they have been addressed.=C2=A0</div><div><br></div><div>Again, thank you =
for spending the time to read this in this fine detail.=C2=A0</div><div><br=
></div><div>Lucien</div><div><br></div><div><br></div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote"><div><div class=3D"h5">On Thu, Jun 8, =
2017 at 5:29 AM, Dan Romascanu <span dir=3D"ltr">&lt;<a href=3D"mailto:drom=
asca@gmail.com" target=3D"_blank">dromasca@gmail.com</a>&gt;</span> wrote:<=
br><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">Reviewer: Dan Romascan=
u<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.=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-bmwg-dcbench-method<wbr>ology-??<br>
Reviewer: Dan Romascanu<br>
Review Date: 2017-06-08<br>
IETF LC End Date: 2017-06-13<br>
IESG Telechat date: Not scheduled for a telechat<br>
<br>
Summary:<br>
<br>
This Informational I-D describes test and evaluation methodology and<br>
measurement techniques for physical network equipment in the data center. I=
t&#39;s<br>
an useful and clearly written document and it is ready for publication, aft=
er a<br>
number of minor issues and nits will be addressed.<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
1. There is one single mention of the scope being benchmarking of &#39;phys=
ical<br>
network equipment in the data center&#39;. I assume this is written as oppo=
sed to<br>
virtual networking equipment. This is not included in the title or repeated=
 any<br>
place else. I suggest to make more clear the scope by mentioning &#39;physi=
cal<br>
equipment&#39; at least once more, for example in the Introduction section.=
<br>
<br>
2. Section 1.2: I am a little concerned about adding additional interpretat=
ions<br>
to the keywords in RFC2119.<br>
<br>
Especially about:<br>
<br>
&#39;MAY: Comprehensive metric for the scenario described&#39;<br></blockqu=
ote><div><br></div></div></div><div><b><span style=3D"font-size:12.8px">Tha=
nk you, MAY provides an optional metric, I have addressed your comment</spa=
n>=C2=A0</b></div><span class=3D""><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>
MAY has a different meaning in 2119, and the fact that a metric is<br>
&#39;comprehensive&#39; (whatever this means) seems to me orthogonal to the=
 2119<br>
semantics. The proposed interpretation makes little sense to me, if<br>
&#39;comprehensive&#39; than why not required? or at least as a &#39;should=
&#39;?<br>
<br>
3. Section 6.2: &#39;The intensity of a microburst MAY be varied ...&#39; I=
t would be<br>
useful to make clear what is meant by &#39;intensity&#39;.<br></blockquote>=
<div><br></div></span><div><div style=3D"font-size:12.8px">The intensity of=
 a microburst is defined in the definitions document [1] so i referenced it=
 that way</div></div><span class=3D""><div>=C2=A0</div><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">
<br>
Nits/editorial comments:<br>
<br>
1. The different formatting of the references [1], [2], etc. vs. [RFC2119],=
<br>
etc. is slightly confusing. Unless there is some good reason I suggest to f=
ix<br>
this. Also use of references is inconsistent through the text, sometimes th=
ey<br>
are mentioned, sometimes they are not.<br></blockquote><div><br></div></spa=
n><div>Fixed it for [2] and [3], however kept [1] as [1], as this document =
is not an RFC yet.</div><span class=3D""><div>=C2=A0</div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">
<br>
2. Section 2.2: &#39;Alternatively when a traffic generator CAN NOT be conn=
ected &#39;<br>
- this capitalization is not conformant to RFC2119.<br>
<br>
3. &#39;vlan ZZZ&#39; is not consistent with &#39;vlan X&#39; and &#39;vlan=
 Y&#39; previously used.<br>
<br>
4. Missing reference - RFC 6985<br>
<br>
5. Missing expansion and references for DSCP and COS<br>
<br>
6. Sections 3.3 and 6.3: s/number of iteration/number of iterations/<br>
<br>
7. The methodology (e.g. in section 5) makes an assumption that the DUT has=
 at<br>
least nine ports. This may be trivial in a DC, but it&#39;s worth being men=
tioned<br>
<br></blockquote></span><div><span style=3D"font-size:12.8px">Thanks added =
this in section 2.3 as it was making more sense to be clarified there</span=
>=C2=A0</div></div><br></div></div>
</blockquote></div><br></div>

--001a114d8aa0220ec305519cbbdd--


From nobody Sat Jun 10 08:52:42 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 263ED126CC7; Sat, 10 Jun 2017 08:52: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=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 orXXMv3bpcxp; Sat, 10 Jun 2017 08:52:35 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0085.outbound.protection.outlook.com [104.47.36.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A8161200E5; Sat, 10 Jun 2017 08:52:35 -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=l19r7l+V68c6wFSMY+KGEbD3MVqAgf7eyuqb8zNKy+4=; b=pILW/OFTInb0WmuVb7T/f7KU8RaY2jHLfmBl2B4vlOOouPMvSSaeqEyHNVFjtnvf4jGUm7srKSCvMt0anLzf7AnUfMeozVMtfbqcGFjVdnM9OIt35BMtfhLluZ8iJOGnxszzfPquTODNlQjLxNxVuK2SU0kOWUcAC2YL3xcd+Og=
Received: from BN6PR05MB3009.namprd05.prod.outlook.com (10.173.19.15) by BN6PR05MB3314.namprd05.prod.outlook.com (10.174.95.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1178.5; Sat, 10 Jun 2017 15:52:32 +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.1178.006; Sat, 10 Jun 2017 15:52:32 +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: AQHSyfQORpr0WT3BYUyvZqID9K0TvaH0MrUAgAFiy4CABEgMgIAArNYAgCNvfAA=
Date: Sat, 10 Jun 2017 15:52:31 +0000
Message-ID: <4E9FB8C0-2CC1-48C9-994F-BDE741BDD52C@vmware.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> <7BB57E2E-ED82-46A1-887B-91B088799FBD@cisco.com>
In-Reply-To: <7BB57E2E-ED82-46A1-887B-91B088799FBD@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
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: [24.7.2.81]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR05MB3314; 7:OOphSW34kOLwfotiAWwXH6A1xF5gMGZ+uXkT6OhxeJtybmV2ANhTGmrJnPItMyB89RTM+L2wMRcmAa24qO9PkdMnH+OhkKBZfAMyc0m+YmaC553TG6s8iKiWp3Jmz/nevWbPyC4Vjst3ZzsMHZlw4VHvR8FwUgk05SHuexEsOqTxaijh1s3p2yQ9ppoKWv2XBLxr3RNedLpo8oLXVRbK8NWwUmJzOsdRR7eNelzoI6wV3BCa6QbFIGNMv2EsNj1HkZ1fpTwXYKmqvaB5nTPJfYA5Zs0FSza3IrKN1cSgpjhGjv17lsrpTKgDso7lpHOXCjR90Mlj2MqefQYA70EN9g==; 20:bn1L070b7Bu9nBmZ2CozuAYOv7+FTJMWktS0yeI3bnmr/szEBOAmRA10vmpsJs97LAk0C5Tfit1unYxTDnNIwK9FM779OnydhQOzjkYn3ZBUvs1xxubur9dz0NMIt1zTS1R7dfV8L6/hGIcLg3EeibyzuTP5BWTcv4QSnBJoTow=
x-ms-office365-filtering-correlation-id: a0e2ceec-6a56-4801-1c7d-08d4b018b4ab
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:BN6PR05MB3314; 
x-ms-traffictypediagnostic: BN6PR05MB3314:
x-microsoft-antispam-prvs: <BN6PR05MB3314886138F541825B4D60F8BECF0@BN6PR05MB3314.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(61668805478150)(95692535739014);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(102415395)(6040450)(601004)(2401047)(5005006)(8121501046)(100000703101)(100105400095)(3002001)(10201501046)(93006095)(93001095)(6041248)(20161123558100)(20161123560025)(20161123564025)(20161123555025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN6PR05MB3314; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN6PR05MB3314; 
x-forefront-prvs: 0334223192
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(6009001)(39840400002)(39450400003)(39400400002)(39410400002)(39850400002)(24454002)(37854004)(377424004)(377454003)(229853002)(478600001)(6246003)(4326008)(82746002)(83716003)(38730400002)(53936002)(8936002)(2950100002)(81166006)(86362001)(66066001)(5660300001)(36756003)(8676002)(33656002)(99286003)(54906002)(6512007)(53546009)(5890100001)(76176999)(99936001)(54356999)(6506006)(6436002)(189998001)(3660700001)(14454004)(122556002)(50986999)(25786009)(2501003)(305945005)(2906002)(3846002)(230783001)(6116002)(3280700002)(102836003)(93886004)(2900100001)(6486002)(77096006)(7736002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:BN6PR05MB3314; H:BN6PR05MB3009.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/mixed; boundary="_002_4E9FB8C02CC148C9994FBDE741BDD52Cvmwarecom_"
MIME-Version: 1.0
X-OriginatorOrg: vmware.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jun 2017 15:52:31.9005 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b39138ca-3cee-4b4a-a4d6-cd83d9dd62f0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR05MB3314
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vg5H2l9hHzGXPJ6mL1vDIkhOnlk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jun 2017 15:52:40 -0000

--_002_4E9FB8C02CC148C9994FBDE741BDD52Cvmwarecom_
Content-Type: text/plain; charset="utf-8"
Content-ID: <2DEF1500EB32C94BB8C68E217A69507D@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64

SGkgUGF0cmljZSwNCg0KUGxlYXNlIGZpbmQgYXR0YWNoZWQgdGhlIGRyYWZ0IHVwZGF0ZWQsIHBs
ZWFzZSBsZXQgbWUga25vdyBpZiB0aGlzIGFkZHJlc3MgeW91ciBjb21tZW50cy4NCg0KDQoNClRo
YW5rcywNCg0KU2FtaQ0KT24gNS8xOC8xNywgMTI6NDQgUE0sICJQYXRyaWNlIEJyaXNzZXR0ZSAo
cGJyaXNzZXQpIiA8cGJyaXNzZXRAY2lzY28uY29tPiB3cm90ZToNCg0KPlRoYW5rIFNhbWkNCj4N
Cj5SZWdhcmRzLA0KPlBhdHJpY2UgQnJpc3NldHRlDQo+DQo+T24gMjAxNy0wNS0xOCwgMTI6MjUg
UE0sICJTYW1pIEJvdXRyb3MiIDxzYm91dHJvc0B2bXdhcmUuY29tPiB3cm90ZToNCj4NCj4gICAg
SGkgUGF0cmljZSwNCj4gICAgDQo+ICAgIA0KPiAgICANCj4gICAgDQo+ICAgIFBsZWFzZSBzZWUg
Y29tbWVudHMgaW5saW5lLg0KPiAgICANCj4gICAgPiAgICA+IA0KPiAgICA+ICAgID5IZXJlIGFy
ZSBteSDigJxkZXRhaWxlZOKAnSBjb21tZW50czoNCj4gICAgPiAgICA+IA0KPiAgICA+ICAgID5B
YnN0cmFjdCDigJQgV2hhdCBpcyB0aGUgcGx1cyB2YWx1ZSBvbiB0aGF0IGRyYWZ0PyBObyBjbGVh
cg0KPiAgICA+ICAgID4gDQo+ICAgID4gICAgPk1hbnkgTG9uZyBzZW50ZW5jZXMgaW4gdGhlIHRl
eHQuIHZlcnkgaGFyZCB0byB1bmRlcnN0YW5kIGFuZCBmb2xsb3cuDQo+ICAgID4gICAgPlN5bnRh
eCB0byBiZSBpbXByb3ZlZC4NCj4gICAgPg0KPiAgICA+PFBhdHJpY2U+IFRoaXMgY29tbWVudCBp
cyByZWdhcmRpbmcgdGhlIGRyYWZ0IGluIGdlbmVyYWwuIEl0IGRvZXNu4oCZdCBmbG93IHdlbGwu
IFlvdSBuZWVkIHRvIHJlYWQgaXQgbW9yZSB0aGFuIG9uY2UgdG8gc2VlIHRoZSBvdmVyYWxsIHBp
Y3R1cmUuIEl0IG1pZ2h0IGp1c3QgYmUgdG8gcmVzaHVmZmxlIHNvbWUgc2VjdGlvbnMuDQo+ICAg
ID4gICAgDQo+ICAgIA0KPiAgICBTdXJlIHdpbGwgbG9vayBpbnRvIHRoYXQuDQo+ICAgIA0KPiAg
ICA+ICAgIA0KPiAgICA+ICAgIEkgd2VudCBvdmVyIHRoZSBhYnN0cmFjdCwgSSBkaWRu4oCZdCBz
ZWUgYW55IGxvbmcgc2VudGVuY2VzLiBOb3Qgc3VyZSANCj4gICAgPiAgICBXaGF0IHRvIGltcHJv
dmU/IENhbiB5b3UgYmUgc3BlY2lmaWM/DQo+ICAgID4gICAgDQo+ICAgID4gICAgDQo+ICAgID4g
ICAgPiANCj4gICAgPiAgICA+SW50cm9kdWN0aW9uDQo+ICAgID4gICAgPlR5cG8gOiDigJxBIHJl
ZmVyZW5jZSBtb2RlbCBvciBhIFAyTVAgUFcgaXMgZGVwaWN0ZWQgaW4gRmlndXJlIDEgYmVsb3fi
gJ0NCj4gICAgPiAgICA+IA0KPiAgICA+ICAgID7igJxJbiB0aGlzIGRvY3VtZW50LCB3ZSBzcGVj
aWZ5IGEgbWV0aG9kIG9mIHNpZ25hbGluZyBQMk1QDQo+ICAgID4gICAgPiAgIFBXIHVzaW5nIExE
UC7igJ0g4oCUPiBzdWdnZXN0IHRvIG1vdmUgaXQgZnJvbSBpbnRybyB0byBhYnN0cmFjdA0KPiAg
ICA+ICAgIA0KPiAgICA+ICAgIE5vdCBzdXJlIGlmIHdlIGNhbiByZWZlcmVuY2UgYSBmaWd1cmUg
aW4gdGhlIGFic3RyYWN0LiBUaGUgYWJzdHJhY3QNCj4gICAgPiAgICBBbHJlYWR5IG1lbnRpb24g
dGhhdCB0aGUgc2Vjb25kIHNlbnRlbmNlLg0KPiAgICA+DQo+ICAgID48UGF0cmljZT4gVGhpcyBp
cyBOT1QgYSBmaWd1cmUgYnV0IHJhdGhlciB0aGUgZXhwbGFuYXRpb24uIFRoYXQgbGluZSBtYWtl
cyB0aGUgZG9jdW1lbnQgdmVyeSBjbGVhci4gSXQganVzdCBuZWVkIHRvIGJlIHNwZWxsZWQgb3V0
LiDigJxzcGVjaWZ5IGEgbWV0aG9kIG9mIHNpZ25hbGluZyBQMk1QIFBXIHVzaW5nIExEUOKAnS4N
Cj4gICAgDQo+ICAgIFRoaXMgaXMgZXhhY3RseSB3aGF0IHdlIGhhdmUgaW4gdGhlIGFic3RyYWN0
IGZpcnN0IHNlbnRlbmNlIOKAnFRoaXMgZG9jdW1lbnQgc3BlY2lmaWVzIGEgbWVjaGFuaXNtIHRv
IHNpZ25hbCBQb2ludC10by1NdWx0aXBvaW50DQo+ICAgICAgIChQMk1QKSBQc2V1ZG93aXJlcyAo
UFcpIHRyZWUgdXNpbmcgTERQLuKAnQ0KPiAgICAgDQo+ICAgID4NCj4gICAgPiAgICA+IA0KPiAg
ICA+ICAgID4gDQo+ICAgID4gICAgPkFsc28sIG1ha2Ugc3VyZSB0aGUgM3JkIHBlcnNvbiBpcyB1
c2VkLiBUcnkgdG8gYSB2b2lkIOKAnHdl4oCdIHVzYWdlDQo+ICAgID4gICAgDQo+ICAgID4gICAg
QWdyZWVkLCBJIHdpbGwgcmVtb3ZlIGFsbCB1c2FnZSBvZiDigJx3ZeKAnSBpbiB0aGUgZG9jdW1l
bnQuDQo+ICAgID4gICAgDQo+ICAgID4gICAgPiANCj4gICAgPiAgICA+TWF5IEkgc3VnZ2VzdCB0
byBoYXZlIGEgcmVxdWlyZW1lbnQgc2VjdGlvbi4gUmVxdWlyZW1lbnRzIGFyZSBhbGwgb3Zlcg0K
PiAgICA+ICAgID50aGUgZG9jdW1lbnQuDQo+ICAgID4gICAgDQo+ICAgID4gICAgVGhlcmUgaXMg
YWxyZWFkeSBhbiBSRkMgZm9yIHRoYXQuIFtSRkM3MzM4XSAgIEYuIEpvdW5heSwgZXQuIGFsLCAN
Cj4gICAgPiAgICAiUmVxdWlyZW1lbnRzIGZvciBQb2ludCB0byBNdWx0aXBvaW50IFBzZXVkb3dp
cmUiLCBSRkM3MzM4LCBTZXB0ZW1iZXIgMjAxNC4NCj4gICAgPiAgICANCj4gICAgPiAgICBUaGlz
IHNvbHV0aW9uIGRvY3VtZW50IGFkZHJlc3NlcyB0aGUgcmVxdWlyZW1lbnRzLg0KPiAgICA+DQo+
ICAgID48UGF0cmljZT4gWW91ciBkb2N1bWVudCBlbmhhbmNlcyB0aGF0IGJhc2VkIFJGQyBieSBw
cm92aWRpbmcgbW9yZSDigJxNVVNU4oCdLCDigJxTSE9VTETigJ0sIGV0Yy4gDQo+ICAgID5UaGV5
IGFyZSBhbGwgb3ZlciB0aGUgZG9jLiBUbyBtYWtlIGl0IGNsZWFyLCBncm91cGluZyB0aGVtIGlu
IGEgc2VjdGlvbiBtYXkgaGVscC4gQW5vdGhlciBpZGVhIGlzIHRvIGhhdmUgUmVxdWlyZW1lbnQg
c3ViLXNlY3Rpb25zIHBlciB0b3BpYy4NCj4gICAgDQo+ICAgIEl0IHNlZW1zIHRoYXQgdGhpcyBp
cyB0aGUgc2FtZSBhcyB5b3VyIGRvY3VtZW50IGZsb3cgY29tbWVudCBhYm92ZSwgSSB3aWxsIGxv
b2sgaW50byB0aGF0Lg0KPiAgICANCj4gICAgPg0KPiAgICA+ICAgIA0KPiAgICA+ICAgID4gDQo+
ICAgID4gICAgPuKAnCAgIEluIGNhc2Ugb2YgbUxEUCwgYSBMZWFmLVBFIGNhbiBkZWNpZGUgdG8g
am9pbiB0aGUgUDJNUCBMU1AgYXQgYW55DQo+ICAgID4gICAgPiAgIHRpbWU7IHdoZXJlYXMgaW4g
dGhlIGNhc2Ugb2YgUlNWUC1URSwgdGhlIFAyTVAgTFNQIGlzIHNldCB1cCBieQ0KPiAgICA+ICAg
ID50aGUNCj4gICAgPiAgICA+ICAgUi1QRSwgZ2VuZXJhbGx5IGF0IHRoZSBpbml0aWFsIHNlcnZp
Y2UgcHJvdmlzaW9uaW5nIHRpbWUuIEl0DQo+ICAgID4gICAgPnNob3VsZA0KPiAgICA+ICAgID4g
ICBiZSBub3RlZCB0aGF0IGxvY2FsIHBvbGljeSBjYW4gb3ZlcnJpZGUgYW55IGRlY2lzaW9uIHRv
IGpvaW4sIGFkZA0KPiAgICA+ICAgID5vcg0KPiAgICA+ICAgID4gICBwcnVuZSBleGlzdGluZyBv
ciBuZXcgTC1QRShzKSBmcm9tIHRoZSB0cmVlLiBJbiBhbnkgY2FzZSwgdGhlIFBXDQo+ICAgID4g
ICAgPiAgIHNldHVwIGNhbiBpZ25vcmUgdGhlc2UgZGlmZmVyZW5jZXMsIGFuZCBzaW1wbHkgYXNz
dW1lIHRoYXQgdGhlDQo+ICAgID4gICAgPlAyTVANCj4gICAgPiAgICA+ICAgUFNOIExTUCBpcyBh
dmFpbGFibGUgd2hlbiBuZWVkZWQNCj4gICAgPiAgICA+4oCcDQo+ICAgID4gICAgPlF1aXRlIGNv
bXBsZXggdG8gZm9sbG93LiBNaXNzaW5nIHRvIOKAnHdoeeKAnSAvIGV4cGxhbmF0aW9uLg0KPiAg
ICA+ICAgIA0KPiAgICA+ICAgIFN1cmUgSSBjYW4gY2xhcmlmeSB0aGlzIGEgbGl0dGxlIG1vcmUs
IHdpbGwgcmVtb3ZlIHNvbWUgc2VudGVuY2VzIA0KPiAgICA+ICAgIFRoYXQgbWFrZSBpdCBjb25m
dXNpbmcsIHdlIGFyZSBzaW1wbHkgaGVyZSBkaWZmZXJlbnRpYXRpbmcgbUxEUCBMU1AgZnJvbQ0K
PiAgICA+ICAgIHAybXAgTFNQIHcvIFJTVlAtVEUgYW5kIHNheWluZyB0aGF0IFBXIHNldHVwIGlz
IGFnbm9zdGljIG9mIHRoZSB0cmFuc3BvcnQgDQo+ICAgID4gICAgcDJtcCBMU1Agc2V0dXAuDQo+
ICAgID4gICAgDQo+ICAgID4gICAgPiANCj4gICAgPiAgICA+4oCcVGhlIExEUCBsaWJlcmFsIGxh
YmVsIHJldGVudGlvbiBtb2RlIGlzIHVzZWTigJwNCj4gICAgPiAgICA+QW5vdGhlciByZXF1aXJl
bWVudOKApiBpcyB0aGF0IGEgTUFZLCBTSE9VTEQsIE1VU1Q/DQo+ICAgID4gICAgDQo+ICAgID4g
ICAgSSB3aWxsIGNoYW5nZSBpdCB0byBhIE1VU1QuDQo+ICAgID4gICAgDQo+ICAgID4gICAgPiAN
Cj4gICAgPiAgICA+4oCcSW4gdGhpcyBjYXNlLCBhIFBXIHN0YXR1cyBtZXNzYWdlIHdpdGggc3Rh
dHVzDQo+ICAgID4gICAgPiAgIGNvZGUgb2YgMHgwMDAwMDAwOCAoTG9jYWwgUFNOLWZhY2luZyBQ
VyAoaW5ncmVzcykgUmVjZWl2ZSBGYXVsdCkNCj4gICAgPiAgICA+TVVTVA0KPiAgICA+ICAgID4g
ICBhbHNvIGJlIHNlbnQgdG8gdGhlIFItUEXigJwNCj4gICAgPiAgICA+IA0KPiAgICA+ICAgID5I
b3c/IFRoZSBMLVBFIGZhaWxzIHRvIGpvaW4gdGhlIFAyTVAgUFNOIExTUC4NCj4gICAgPiAgICAN
Cj4gICAgPiAgICBDb3JyZWN0IHRoZSBMLVBFIGhhdmUgdG8gc2lnbmFsIHRoaXMgZmFpbHVyZSB0
byB0aGUgcm9vdCBQRS4NCj4gICAgPg0KPiAgICA+PFBhdHJpY2U+IHF1ZXN0aW9uIHJlbWFpbnMs
IGhvdz8gSWYgTC1QRSBmYWlscyB0byBqb2luIHRoZSBMU1AsIFBXIHdpbGwgYmUgZG93bi4gSG93
IGNhbiBpdCBzaWduYWxzIHRoZSBmYWlsdXJlIHRvIHJvb3QgUEU/DQo+ICAgID4gICAgDQo+ICAg
IA0KPiAgICBMLVBFIHdpbGwgdXNlIHRoZSBQVyBzdGF0dXMgbWVzc2FnZSwgdG8gc2lnbmFsIHRv
IHJvb3QgUEUgdGhpcyBpcyB3aGF0IHRoZSB0ZXh0IGlzIHNheWluZy4NCj4gICAgDQo+ICAgID4g
ICAgPiANCj4gICAgPiAgICA+U2VjdGlvbiAyLjINCj4gICAgPiAgICA+4oCcICAgTm90ZSB0aGF0
IHNpbmNlIHRoZSBMRFAgbGFiZWwgbWFwcGluZyBtZXNzYWdlIGlzIG9ubHkgc2VudCBieSB0aGUN
Cj4gICAgPiAgICA+Ui0NCj4gICAgPiAgICA+ICAgUEUgdG8gYWxsIHRoZSBMLVBFcywgaXQgaXMg
bm90IHBvc3NpYmxlIHRvIG5lZ290aWF0ZSBhbnkgaW50ZXJmYWNlDQo+ICAgID4gICAgPiAgIHBh
cmFtZXRlcnMu4oCcDQo+ICAgID4gICAgPldoeSBpcyB0aGF0IG5vdGUgdGhlcmU/IElzIHRoYXQg
YWxyZWFkeSBiZWVuIG1lbnRpb25lZCBwcmV2aW91c2x5Lg0KPiAgICA+ICAgIA0KPiAgICA+ICAg
IFRoaXMgaXMgdGhlIG9ubHkgcmVmZXJlbmNlIGluIHRoZSBkb2N1bWVudC4NCj4gICAgPg0KPiAg
ICA+PFBhdHJpY2U+IEZvcmdvdCBteSB0aG91Z2h0cyBvbiB0aGF0IG9uZS4NCj4gICAgPiAgICAN
Cj4gICAgPiAgICA+RmlnLjQgbXVzdCAgYmUgbW92ZWQgdG8gcHJvcGVyIGluIHRoZSB0ZXh0IE9S
IGNyZWF0ZSAyIHN1YnNlY3Rpb24gaW4NCj4gICAgPiAgICA+Mi4yDQo+ICAgID4gICAgDQo+ICAg
ID4gICAgU29ycnkgZGlkbuKAmXQgZ2V0IHdoYXQgeW91IG1lYW4gaGVyZT8gQ2FuIHlvdSBlbGFi
b3JhdGU/DQo+ICAgID4NCj4gICAgPjxQYXRyaWNlPiBTb3JyeSDigKZMZXQgbWUgdHJ5IGFnYWlu
LiDigJxQMlAgUFcgRG93bnN0cmVhbSBGRUMgRWxlbWVudOKAnS4gSSB0aGluayB5b3Ugc2hvdWxk
IGhhdmUgYSBzZWN0aW9uIGp1c3Qgb24gdGhhdCB0b3BpYy4gQWN0dWFsbHksIG1heWJlIHlvdSBj
YW4gY3JlYXRlIGEgc3Vic2VjdGlvbiBmb3IgZWFjaCBkaWZmZXJlbnQgRkVDIGV4cGxhaW5lZCBp
biB0aGUgZG9jdW1lbnQuIA0KPiAgICA+ICAgIA0KPiAgICANCj4gICAgT2ssIEkgd2lsbCBhZGQg
c3Vic2VjdGlvbnMgZm9yIERvd25zdHJlYW0gYW5kIFVwc3RyZWFtLg0KPiAgICANCj4gICAgVGhh
bmtzLA0KPiAgICANCj4gICAgU2FtaQ0KPiAgICA+ICAgID4gDQo+ICAgID4gICAgPuKAnEFzIHN1
Y2gsIFBXIHN0YXR1cyBuZWdvdGlhdGlvbiBwcm9jZWR1cmUNCj4gICAgPiAgICA+ICAgZGVzY3Jp
YmVkIGluIFtSRkM0NDQ3YmlzXSBpcyBub3QgYXBwbGljYWJsZSB0byBQMk1QIFBXLiBBIG5vZGUN
Cj4gICAgPiAgICA+TVVTVA0KPiAgICA+ICAgID4gICBOT1QgY2xhaW0gdG8gYmUgIFAyTVAgUFcg
Y2FwYWJsZSBieSBzZW5kaW5nIGEgTERQIFAyTVAgUFcNCj4gICAgPiAgICA+Q2FwYWJpbGl0eQ0K
PiAgICA+ICAgID4gICBUTFYgIGlmIGl0IGlzIG5vdCBhbHNvIGNhcGFibGUgb2YgaGFuZGxpbmcg
UFcgc3RhdHVz4oCcDQo+ICAgID4gICAgPiANCj4gICAgPiAgICA+U2hvdWxkIGEgbm9kZSBzZW5k
IExEUCBQMk1QIFBXIENhcGFiaWxpdHkgVExWIG9yIG5vdD8gTm90IHdlbGwgZXhwbGFpbg0KPiAg
ICA+ICAgIA0KPiAgICA+ICAgIFdoYXQgaXMgc2FpZCBoZXJlLCB0aGF0IHlvdSBjYW7igJl0IGJl
IFAyTVAgUFcgY2FwYWJsZSB3aXRob3V0IGJlaW5nIFBXIHN0YXR1cyBjYXBhYmxlLg0KPiAgICA+
ICAgIE5vdCBzdXJlIGhvdyB0byBtYWtlIGl0IGNsZWFyZXIuDQo+ICAgID4NCj4gICAgPjxQYXRy
aWNlPiByaWdodOKApiBJIG11c3QgaGF2ZSBiZWVuIHRpcmVkLiBUb28gbWFueSBOT1QgDQo+ICAg
ID4gICAgDQo+ICAgID4gICAgPg0KPiAgICA+ICAgID4gDQo+ICAgID4gICAgPlRoZXJlIGlzIHNv
bWUgcmVmZXJlbmNlIHRvIExTUiBpbiB0aGUgdGV4dCB3aGVyZSB0aGUgbWFqb3IgcGFydCB1c2UN
Cj4gICAgPiAgICA+dGhlIHdvcmRpbmcg4oCcbm9kZeKAnS4NCj4gICAgPiAgICANCj4gICAgPiAg
ICBJIHdpbGwgbWFrZSBhbGwgY29uc2lzdGVudCwgYW5kIHVzZSBMU1IgaW5zdGVhZCBvZiBub2Rl
Lg0KPiAgICA+ICAgIA0KPiAgICA+ICAgIFRoYW5rcywNCj4gICAgPiAgICANCj4gICAgPiAgICBT
YW1pDQo+ICAgID4gICAgPiANCj4gICAgPiAgICA+Tml0czogDQo+ICAgID4gICAgPk4vQQ0KPiAg
ICA+ICAgID4gDQo+ICAgID4gICAgPlJlZ2FyZHMsDQo+ICAgID4gICAgPlBhdHJpY2UgQnJpc3Nl
dHRlDQo+ICAgID4gICAgPg0KPiAgICA+ICAgID4NCj4gICAgPiAgICA+DQo+ICAgID4gICAgPg0K
PiAgICA+ICAgIA0KPiAgICA+DQo+ICAgIA0KPg0K

--_002_4E9FB8C02CC148C9994FBDE741BDD52Cvmwarecom_
Content-Type: text/plain; name="draft-ietf-pals-p2mp-pw-03.txt"
Content-Description: draft-ietf-pals-p2mp-pw-03.txt
Content-Disposition: attachment; filename="draft-ietf-pals-p2mp-pw-03.txt";
	size=36822; creation-date="Sat, 10 Jun 2017 15:52:29 GMT";
	modification-date="Sat, 10 Jun 2017 15:52:29 GMT"
Content-ID: <DB1F9ADDD6F8E6478315E96AEC341A02@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64

IA0KDQoNCg0KSU5URVJORVQtRFJBRlQgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIFNhbWkgQm91dHJvcyhFZC4pDQpJbnRlbmRlZCBTdGF0dXM6IFN0YW5kYXJkIFRyYWNr
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBWTXdhcmUNCg0KVXBkYXRlczogUkZD
NzM4NSAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBTaXZhIFNpdmFiYWxhbihF
ZC4pDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIENpc2NvIFN5c3RlbXMNCg0KDQpFeHBpcmVzOiBEZWNlbWJlciAxMiwgMjAxNyAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIEp1bmUgMTAsIDIwMTcNCg0KDQogICBTaWduYWxp
bmcgUm9vdC1Jbml0aWF0ZWQgUG9pbnQtdG8tTXVsdGlwb2ludCBQc2V1ZG93aXJlIHVzaW5nIExE
UA0KICAgICAgICAgICAgICAgICAgICAgZHJhZnQtaWV0Zi1wYWxzLXAybXAtcHctMDMudHh0DQoN
Cg0KQWJzdHJhY3QNCg0KICAgVGhpcyBkb2N1bWVudCBzcGVjaWZpZXMgYSBtZWNoYW5pc20gdG8g
c2lnbmFsIFBvaW50LXRvLU11bHRpcG9pbnQNCiAgIChQMk1QKSBQc2V1ZG93aXJlcyAoUFcpIHRy
ZWUgdXNpbmcgTERQLiBTdWNoIGEgbWVjaGFuaXNtIGlzIHN1aXRhYmxlDQogICBmb3IgYW55IExh
eWVyIDIgVlBOIHNlcnZpY2UgcmVxdWlyaW5nIFAyTVAgY29ubmVjdGl2aXR5IG92ZXIgYW4gSVAg
b3INCiAgIE1QTFMgZW5hYmxlZCBQU04uIEEgUDJNUCBQVyBlc3RhYmxpc2hlZCB2aWEgdGhlIHBy
b3Bvc2VkIG1lY2hhbmlzbSBpcw0KICAgcm9vdCBpbml0aWF0ZWQuIFRoaXMgZG9jdW1lbnQgdXBk
YXRlcyBSRkM3Mzg1IGJ5IHJlLWFzc2lnbmluZw0KICAgcmVzZXJ2ZWQgdmFsdWUgMHhGRiB0byBi
ZSB0aGUgd2lsZGNhcmQgdHJhbnNwb3J0IHR1bm5lbCB0eXBlLg0KDQpTdGF0dXMgb2YgdGhpcyBN
ZW1vDQoNCiAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgaXMgc3VibWl0dGVkIHRvIElFVEYgaW4gZnVs
bCBjb25mb3JtYW5jZSB3aXRoIHRoZQ0KICAgcHJvdmlzaW9ucyBvZiBCQ1AgNzggYW5kIEJDUCA3
OS4NCg0KICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5nIGRvY3VtZW50cyBvZiB0aGUgSW50
ZXJuZXQgRW5naW5lZXJpbmcNCiAgIFRhc2sgRm9yY2UgKElFVEYpLCBpdHMgYXJlYXMsIGFuZCBp
dHMgd29ya2luZyBncm91cHMuICBOb3RlIHRoYXQNCiAgIG90aGVyIGdyb3VwcyBtYXkgYWxzbyBk
aXN0cmlidXRlIHdvcmtpbmcgZG9jdW1lbnRzIGFzDQogICBJbnRlcm5ldC1EcmFmdHMuDQoNCiAg
IEludGVybmV0LURyYWZ0cyBhcmUgZHJhZnQgZG9jdW1lbnRzIHZhbGlkIGZvciBhIG1heGltdW0g
b2Ygc2l4IG1vbnRocw0KICAgYW5kIG1heSBiZSB1cGRhdGVkLCByZXBsYWNlZCwgb3Igb2Jzb2xl
dGVkIGJ5IG90aGVyIGRvY3VtZW50cyBhdCBhbnkNCiAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJp
YXRlIHRvIHVzZSBJbnRlcm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlDQogICBtYXRlcmlhbCBvciB0
byBjaXRlIHRoZW0gb3RoZXIgdGhhbiBhcyAid29yayBpbiBwcm9ncmVzcy4iDQoNCiAgIFRoZSBs
aXN0IG9mIGN1cnJlbnQgSW50ZXJuZXQtRHJhZnRzIGNhbiBiZSBhY2Nlc3NlZCBhdA0KICAgaHR0
cDovL3d3dy5pZXRmLm9yZy8xaWQtYWJzdHJhY3RzLmh0bWwNCg0KICAgVGhlIGxpc3Qgb2YgSW50
ZXJuZXQtRHJhZnQgU2hhZG93IERpcmVjdG9yaWVzIGNhbiBiZSBhY2Nlc3NlZCBhdA0KICAgaHR0
cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbA0KDQoNCkNvcHlyaWdodCBhbmQgTGljZW5zZSBO
b3RpY2UNCg0KICAgQ29weXJpZ2h0IChjKSAyMDE3IElFVEYgVHJ1c3QgYW5kIHRoZSBwZXJzb25z
IGlkZW50aWZpZWQgYXMgdGhlDQogDQoNCg0KU2l2YWJhbGFuICYgQm91dHJvcyAgICBFeHBpcmVz
IERlY2VtYmVyIDEyLCAyMDE3ICAgICAgICAgICAgICAgIFtQYWdlIDFdDQoMDQpJTlRFUk5FVCBE
UkFGVCAgICAgICAgICAgICAgICAgIFAyTVAgUFcgICAgICAgICAgICAgICAgICAgIEp1bmUgMTAs
IDIwMTcNCg0KDQogICBkb2N1bWVudCBhdXRob3JzLiBBbGwgcmlnaHRzIHJlc2VydmVkLg0KDQog
ICBUaGlzIGRvY3VtZW50IGlzIHN1YmplY3QgdG8gQkNQIDc4IGFuZCB0aGUgSUVURiBUcnVzdCdz
IExlZ2FsDQogICBQcm92aXNpb25zIFJlbGF0aW5nIHRvIElFVEYgRG9jdW1lbnRzDQogICAoaHR0
cDovL3RydXN0ZWUuaWV0Zi5vcmcvbGljZW5zZS1pbmZvKSBpbiBlZmZlY3Qgb24gdGhlIGRhdGUg
b2YNCiAgIHB1YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuIFBsZWFzZSByZXZpZXcgdGhlc2Ug
ZG9jdW1lbnRzDQogICBjYXJlZnVsbHksIGFzIHRoZXkgZGVzY3JpYmUgeW91ciByaWdodHMgYW5k
IHJlc3RyaWN0aW9ucyB3aXRoIHJlc3BlY3QNCiAgIHRvIHRoaXMgZG9jdW1lbnQuIENvZGUgQ29t
cG9uZW50cyBleHRyYWN0ZWQgZnJvbSB0aGlzIGRvY3VtZW50IG11c3QNCiAgIGluY2x1ZGUgU2lt
cGxpZmllZCBCU0QgTGljZW5zZSB0ZXh0IGFzIGRlc2NyaWJlZCBpbiBTZWN0aW9uIDQuZSBvZg0K
ICAgdGhlIFRydXN0IExlZ2FsIFByb3Zpc2lvbnMgYW5kIGFyZSBwcm92aWRlZCB3aXRob3V0IHdh
cnJhbnR5IGFzDQogICBkZXNjcmliZWQgaW4gdGhlIFNpbXBsaWZpZWQgQlNEIExpY2Vuc2UuDQoN
Cg0KDQpUYWJsZSBvZiBDb250ZW50cw0KDQogICAxICBJbnRyb2R1Y3Rpb24gIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gIDMNCiAgICAgMS4xICBUZXJt
aW5vbG9neSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAg
NA0KICAgMi4gU2lnbmFsaW5nIFAyTVAgUFcgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuICA0DQogICAgIDIuMSBQVyBpbmdyZXNzIHRvIGVncmVzcyBpbmNvbXBh
dGliaWxpdHkgaXNzdWVzICAuIC4gLiAuIC4gLiAuIC4gIDYNCiAgICAgMi4yIFAyTVAgUFcgRkVD
ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAgNg0KICAg
ICAgIDIuMi4xIFAyTVAgUFcgVXBzdHJlYW0gRkVDIEVsZW1lbnQgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuICA2DQogICAgICAgMi4yLjIgUDJQIFBXIERvd25zdHJlYW0gRkVDIEVsZW1lbnQg
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTANCiAgICAgMi4zIFR5cGVkIFdpbGRjYXJkIEZF
QyBGb3JtYXQgZm9yIG5ldyBGRUMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMA0KICAgICAyLjQg
R3JvdXAgSUQgdXNhZ2UgLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIDExDQogICAgIDIuNSBHZW5lcmljIExhYmVsIFRMViAgLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gMTENCiAgIDMuIExEUCBDYXBhYmlsaXR5IE5lZ290aWF0aW9u
ICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMQ0KICAgNC4gUDJNUCBQVyBT
dGF0dXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEz
DQogICA1IFNlY3VyaXR5IENvbnNpZGVyYXRpb25zICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gMTMNCiAgIDYgQWNrbm93bGVkZ21lbnQgLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxMw0KICAgNyAgSUFOQSBDb25zaWRlcmF0
aW9ucyAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDEzDQogICAg
IDcuMS4gRkVDIFR5cGUgTmFtZSBTcGFjZSAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gMTMNCiAgICAgNy4yLiBMRFAgVExWIFR5cGUgIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAxNA0KICAgICA3LjMuIG1MRFAgT3BhcXVlIFZhbHVl
IEVsZW1lbnQgVExWIFR5cGUgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE0DQogICAgIDcuNC4g
U2VsZWN0aXZlIFRyZWUgSW50ZXJmYWNlIFBhcmFtZXRlciBzdWItVExWIFR5cGUgLiAuIC4gLiAu
IC4gMTQNCiAgICAgNy41LiBXaWxkQ2FyZCBQTVNJIHR1bm5lbCB0eXBlIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAuIC4gLiAxNA0KICAgOCAgUmVmZXJlbmNlcyAgLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE1DQogICAgIDguMS4gTm9ybWF0
aXZlIFJlZmVyZW5jZXMgIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTUN
CiAgICAgOC4yLiBJbmZvcm1hdGl2ZSBSZWZlcmVuY2VzICAuIC4gLiAuIC4gLiAuIC4gLiAuIC4g
LiAuIC4gLiAuIC4gLiAxNg0KICAgQ29udHJpYnV0b3JzIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAu
IC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIDE2DQogICBBdXRob3JzJyBBZGRyZXNzZXMg
LiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gLiAuIC4gMTcNCg0KDQoN
Cg0KDQoNCg0KIA0KDQoNClNpdmFiYWxhbiAmIEJvdXRyb3MgICAgRXhwaXJlcyBEZWNlbWJlciAx
MiwgMjAxNyAgICAgICAgICAgICAgICBbUGFnZSAyXQ0KDA0KSU5URVJORVQgRFJBRlQgICAgICAg
ICAgICAgICAgICBQMk1QIFBXICAgICAgICAgICAgICAgICAgICBKdW5lIDEwLCAyMDE3DQoNCg0K
MSAgSW50cm9kdWN0aW9uDQoNCiAgIEEgUG9pbnQtdG8tTXVsdGlwb2ludCAoUDJNUCkgUHNldWRv
d2lyZSAoUFcpIGVtdWxhdGVzIHRoZSBlc3NlbnRpYWwNCiAgIGF0dHJpYnV0ZXMgb2YgYSB1bmlk
aXJlY3Rpb25hbCBQMk1QIFRlbGVjb21tdW5pY2F0aW9ucyBzZXJ2aWNlIHN1Y2gNCiAgIGFzIFAy
TVAgQVRNIG92ZXIgUFNOLiBBIG1ham9yIGRpZmZlcmVuY2UgYmV0d2VlbiBhIFBvaW50LXRvLVBv
aW50DQogICAoUDJQKSBQVyBvdXRsaW5lZCBpbiBbUkZDMzk4NV0gYW5kIGEgUDJNUCBQVyBpcyB0
aGF0IHRoZSBmb3JtZXIgaXMNCiAgIGludGVuZGVkIGZvciBiaWRpcmVjdGlvbmFsIHNlcnZpY2Ug
d2hlcmVhcyB0aGUgbGF0dGVyIGlzIGludGVuZGVkIGZvcg0KICAgYm90aCB1bmlkaXJlY3Rpb25h
bCwgYW5kIG9wdGlvbmFsbHkgYmlkaXJlY3Rpb25hbCBzZXJ2aWNlLg0KICAgUmVxdWlyZW1lbnRz
IGZvciBQMk1QIFBXIGFyZSBkZXNjcmliZWQgaW4gW1JGQzczMzhdLiBQMk1QIFBXIGNhbiBiZQ0K
ICAgY29uc3RydWN0ZWQgYXMgZWl0aGVyIFNpbmdsZSBTZWdtZW50IChQMk1QIFNTLVBXKSBvciBN
dWx0aSBTZWdtZW50DQogICAoUDJNUCBNUy1QVykgUHNldWRvd2lyZXMgYXMgbWVudGlvbmVkIGlu
IFtSRkM3MzM4XS4gUDJNUCBNUy1QVyBpcw0KICAgb3V0c2lkZSB0aGUgc2NvcGUgb2YgdGhpcyBk
b2N1bWVudC4gQSByZWZlcmVuY2UgbW9kZWwgb3IgYSBQMk1QIFBXIGlzDQogICBkZXBpY3RlZCBp
biBGaWd1cmUgMSBiZWxvdy4gQSB0cmFuc3BvcnQgTFNQIGFzc29jaWF0ZWQgd2l0aCBhIFAyTVAN
CiAgIFNTLVBXIFNIT1VMRCBiZSBhIFAyTVAgTVBMUyBMU1AgKGkuZS4sIFAyTVAgVEUgdHVubmVs
IGVzdGFibGlzaGVkIHZpYQ0KICAgUlNWUC1URSBbUkZDNDg3NV0gb3IgUDJNUCBMU1AgZXN0YWJs
aXNoZWQgdmlhIG1MRFAgW1JGQzYzODhdKQ0KICAgc3Bhbm5pbmcgZnJvbSB0aGUgUm9vdC1QRSB0
byB0aGUgTGVhZi1QRShzKSBvZiB0aGUgUDJNUCBTUy1QVyB0cmVlLg0KICAgRm9yIGV4YW1wbGUs
IGluIEZpZ3VyZSAxLCBQVzEgY2FuIGJlIGFzc29jaWF0ZWQgd2l0aCBhIFAyTVAgVEUgdHVubmVs
DQogICBvciBQMk1QIExTUCBzZXR1cCB1c2luZyBtTERQIG9yaWdpbmF0aW5nIGZyb20gUEUxIGFu
ZCB0ZXJtaW5hdGluZyBhdA0KICAgUEUyLCBQRTMgYW5kIFBFNC4NCg0KDQogICAgICAgICAgICAg
ICAgIHw8LS0tLS0tLS0tLS0tLS1QMk1QIFBXLS0tLS0tLS0tLS0tLS0tLT58DQogICAgICAgICAg
TmF0aXZlIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8ICBOYXRpdmUN
CiAgICAgICAgIFNlcnZpY2UgfCAgICAgfDwtLVBTTjEtPnwgICAgICB8PC0tUFNOMi0+fCAgICAg
IHwgIFNlcnZpY2UNCiAgICAgICAgICAoQUMpICAgViAgICAgViAgICAgICAgIFYgICAgICBWICAg
ICAgICAgViAgICAgIFYgICAoQUMpDQogICAgICAgICAgICB8ICAgICstLS0tLSsgICAgICAgICAr
LS0tLS0tKyAgICAgICAgICstLS0tLS0rICAgIHwNCiAgICAgICAgICAgIHwgICAgfCAgICAgfCAg
ICAgICAgIHwgICBQMSB8PT09PT09PT09fFQtUEUyIHxBQzMgfCAgICArLS0tKw0KICAgICAgICAg
ICAgfCAgICB8ICAgICB8ICAgICAgICAgfCAgIC4uLi4uLi5QVzEuLi4uLi4uLi4+fC0tLS0tLS0t
PnxDRTN8DQogICAgICAgICAgICB8ICAgIHxULVBFMXw9PT09PT09PT18ICAgLiAgfD09PT09PT09
PXwgICAgICB8ICAgIHwgICAgKy0tLSsNCiAgICAgICAgICAgIHwgICAgfCAgLi4uLi4uLlBXMS4u
Li4uLi4uICB8ICAgICAgICAgKy0tLS0tLSsgICAgfA0KICAgICAgICAgICAgfCAgICB8ICAuICB8
PT09PT09PT09fCAgIC4gIHwgICAgICAgICArLS0tLS0tKyAgICB8DQogICAgICAgICAgICB8ICAg
IHwgIC4gIHwgICAgICAgICB8ICAgLiAgfD09PT09PT09PXxULVBFMyB8QUM0IHwgICAgKy0tLSsN
CiAgICArLS0tKyAgIHxBQzEgfCAgLiAgfCAgICAgICAgIHwgICAuLi4uLi4uUFcxLi4uLi4uLi4u
PnwtLS0tLS0tLT58Q0U0fA0KICAgIHxDRTF8LS0tLS0tLT58Li4uICB8ICAgICAgICAgfCAgICAg
IHw9PT09PT09PT18ICAgICAgfCAgICB8ICAgICstLS0rDQogICAgKy0tLSsgICB8ICAgIHwgIC4g
IHwgICAgICAgICArLS0tLS0tKyAgICAgICAgICstLS0tLS0rICAgIHwNCiAgICAgICAgICAgIHwg
ICAgfCAgLiAgfCAgICAgICAgICstLS0tLS0rICAgICAgICAgKy0tLS0tLSsgICAgfA0KICAgICAg
ICAgICAgfCAgICB8ICAuICB8PT09PT09PT09fCAgIFAyIHw9PT09PT09PT18VC1QRTQgfEFDNSB8
ICAgICstLS0rDQogICAgICAgICAgICB8ICAgIHwgIC4uLi4uLi5QVzEuLi4uLi4uLi4uLi4uLlBX
MS4uLi4uLi4uLj58LS0tLS0tLS0+fENFNXwNCiAgICAgICAgICAgIHwgICAgfCAgICAgfD09PT09
PT09PXwgICAgICB8PT09PT09PT09fCAgICAgIHwgICAgfCAgICArLS0tKw0KICAgICAgICAgICAg
fCAgICArLS0tLS0rICAgICAgICAgKy0tLS0tLSsgICAgICAgICArLS0tLS0tKyAgICB8DQoNCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEZpZ3VyZSAxOiBQMk1QIFBXDQoNCiAgIE1l
Y2hhbmlzbXMgZm9yIGVzdGFibGlzaGluZyBQMlAgU1MtUFcgdXNpbmcgTERQIGFyZSBkZXNjcmli
ZWQgaW4NCiAgIFtSRkM0NDQ3YmlzXS4gVGhpcyBkb2N1bWVudCBzcGVjaWZ5IGEgbWV0aG9kIG9m
IHNpZ25hbGluZyBQMk1QIFBXDQogICB1c2luZyBMRFAuIEluIHBhcnRpY3VsYXIsIHRoaXMgZG9j
dW1lbnQgZGVmaW5lcyBuZXcgRkVDLCBUTFZzLA0KICAgcGFyYW1ldGVycywgYW5kIHN0YXR1cyBj
b2RlcyB0byBmYWNpbGl0YXRlIExEUCB0byBzaWduYWwgYW5kIG1haW50YWluDQogICBQMk1QIFBX
cy4NCiANCg0KDQpTaXZhYmFsYW4gJiBCb3V0cm9zICAgIEV4cGlyZXMgRGVjZW1iZXIgMTIsIDIw
MTcgICAgICAgICAgICAgICAgW1BhZ2UgM10NCgwNCklOVEVSTkVUIERSQUZUICAgICAgICAgICAg
ICAgICAgUDJNUCBQVyAgICAgICAgICAgICAgICAgICAgSnVuZSAxMCwgMjAxNw0KDQoNCiAgIEFz
IG91dGxpbmVkIGluIFtSRkM3MzM4XSwgZXZlbiB0aG91Z2ggdGhlIHRyYWZmaWMgZmxvdyBmcm9t
IGEgUm9vdC1QRQ0KICAgKFItUEUpIHRvIExlYWYtUEUocykgKEwtUEVzKSBpcyBQMk1QIGluIG5h
dHVyZSwgaXQgbWF5IGJlIGRlc2lyYWJsZQ0KICAgZm9yIGFueSBMLVBFIHRvIHNlbmQgdW5pZGly
ZWN0aW9uYWwgUDJQIHRyYWZmaWMgZGVzdGluZWQgb25seSB0byB0aGUNCiAgIFItUEUuIFRoZSBw
cm9wb3NlZCBtZWNoYW5pc20gdGFrZXMgc3VjaCBvcHRpb24gaW50byBjb25zaWRlcmF0aW9uLg0K
DQogICBUaGUgUDJNUCBQVyByZXF1aXJlcyBhbiBNUExTIExTUCB0byBjYXJyeSB0aGUgUFcgdHJh
ZmZpYywgYW5kIHRoZQ0KICAgTVBMUyBwYWNrZXRzIGNhcnJ5aW5nIHRoZSBQVyB1cHN0cmVhbSBs
YWJlbCB3aWxsIGJlIGVuY2Fwc3VsYXRlZA0KICAgYWNjb3JkaW5nIHRvIHRoZSBtZXRob2RzIGRl
c2NyaWJlZCBpbiBbUkZDNTMzMl0uDQoNCg0KMS4xICBUZXJtaW5vbG9neQ0KDQogICBUaGUga2V5
IHdvcmRzICJNVVNUIiwgIk1VU1QgTk9UIiwgIlJFUVVJUkVEIiwgIlNIQUxMIiwgIlNIQUxMIE5P
VCIsDQogICAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5k
ICJPUFRJT05BTCIgaW4gdGhpcw0KICAgZG9jdW1lbnQgYXJlIHRvIGJlIGludGVycHJldGVkIGFz
IGRlc2NyaWJlZCBpbiBSRkMgMjExOSBbUkZDMjExOV0uDQoNCiAgIEZFQzogRm9yd2FyZGluZyBF
cXVpdmFsZW5jZSBDbGFzcw0KDQogICBMRFA6IExhYmVsIERpc3RyaWJ1dGlvbiBQcm90b2NvbA0K
DQogICBtTERQOiBMYWJlbCBEaXN0cmlidXRpb24gUHJvdG9jb2wgZm9yIFAyTVAvTVAyTVAgTFNQ
DQoNCiAgIExTUDogTGFiZWwgU3dpdGNoaW5nIFBhdGgNCg0KICAgTVMtUFc6IE11bHRpLVNlZ21l
bnQgUHNldWRvd2lyZQ0KDQogICBQMlA6IFBvaW50IHRvIFBvaW50DQoNCiAgIFAyTVA6IFBvaW50
IHRvIE11bHRpcG9pbnQNCg0KICAgUEU6IFByb3ZpZGVyIEVkZ2UNCg0KICAgUFNOOiBQYWNrZXQg
U3dpdGNoZWQgTmV0d29yaw0KDQogICBQVzogUHNldWRvd2lyZQ0KDQogICBTUy1QVzogU2luZ2xl
LVNlZ21lbnQgUHNldWRvd2lyZQ0KDQogICBTLVBFOiBTd2l0Y2hpbmcgUHJvdmlkZXIgRWRnZSBv
ZiBNUy1QVw0KDQogICBURTogVHJhZmZpYyBFbmdpbmVlcmluZw0KDQogICBSLVBFOiBSb290LVBF
IC0gaW5ncmVzcyBQRSwgUEUgaW5pdGlhdGluZyBQMk1QIFBXIHNldHVwLg0KDQogICBMLVBFOiBM
ZWFmLVBFIC0gZWdyZXNzIFBFLg0KDQoyLiBTaWduYWxpbmcgUDJNUCBQVw0KDQogDQoNCg0KU2l2
YWJhbGFuICYgQm91dHJvcyAgICBFeHBpcmVzIERlY2VtYmVyIDEyLCAyMDE3ICAgICAgICAgICAg
ICAgIFtQYWdlIDRdDQoMDQpJTlRFUk5FVCBEUkFGVCAgICAgICAgICAgICAgICAgIFAyTVAgUFcg
ICAgICAgICAgICAgICAgICAgIEp1bmUgMTAsIDIwMTcNCg0KDQogICBJbiBvcmRlciB0byBhZHZl
cnRpc2UgbGFiZWxzIGFzIHdlbGwgYXMgZXhjaGFuZ2UgUFcgcmVsYXRlZCBMRFANCiAgIG1lc3Nh
Z2VzLCBQRXMgbXVzdCBlc3RhYmxpc2ggTERQIHNlc3Npb25zIGFtb25nIHRoZW1zZWx2ZXMuIEEg
UEUNCiAgIGRpc2NvdmVycyBvdGhlciBQRXMgdGhhdCBhcmUgdG8gYmUgY29ubmVjdGVkIHZpYSBQ
Mk1QIFBXcyBlaXRoZXIgdmlhDQogICBtYW51YWwgY29uZmlndXJhdGlvbiBvciBhdXRvZGlzY292
ZXJ5IFtSRkM2MDc0XS4NCg0KICAgUi1QRSBhbmQgZWFjaCBMLVBFIE1VU1QgYmUgY29uZmlndXJl
ZCB3aXRoIHRoZSBzYW1lIEZFQyBhcyBkZWZpbmVkIGluDQogICB0aGUgZm9sbG93aW5nIHNlY3Rp
b24uDQoNCiAgIFAyTVAgUFcgcmVxdWlyZXMgdGhhdCB0aGVyZSBpcyBhbiBhY3RpdmUgUDJNUCBQ
U04gTFNQIHNldCB1cCBiZXR3ZWVuDQogICBSLVBFIGFuZCBMLVBFKHMpLiBOb3RlIHRoYXQgdGhl
IHByb2NlZHVyZSB0byBzZXQgdXAgdGhlIFAyTVAgUFNOIExTUA0KICAgaXMgZGlmZmVyZW50IGRl
cGVuZGluZyBvbiB0aGUgc2lnbmFsaW5nIHByb3RvY29sIHVzZWQgKFJTVlAtVEUgb3INCiAgIG1M
RFApLg0KDQogICBJbiBjYXNlIG9mIG1MRFAsIGEgTGVhZi1QRSBjYW4gZGVjaWRlIHRvIGpvaW4g
dGhlIFAyTVAgTFNQIGF0IGFueQ0KICAgdGltZS4gSW4gdGhlIGNhc2Ugb2YgUlNWUC1URSwgdGhl
IFAyTVAgTFNQIGlzIHNldCB1cCBieSB0aGUgUi1QRSwNCiAgIGdlbmVyYWxseSBhdCB0aGUgaW5p
dGlhbCBzZXJ2aWNlIHByb3Zpc2lvbmluZyB0aW1lLiBJdCBzaG91bGQgYmUNCiAgIG5vdGVkIHRo
YXQgbG9jYWwgcG9saWN5IGNhbiBvdmVycmlkZSBhbnkgZGVjaXNpb24gdG8gam9pbiwgYWRkIG9y
DQogICBwcnVuZSBleGlzdGluZyBvciBuZXcgTC1QRShzKSBmcm9tIHRoZSB0cmVlLiBJbiBhbnkg
Y2FzZSwgdGhlIFBXDQogICBzZXR1cCBjYW4gaWdub3JlIHRoZXNlIGRpZmZlcmVuY2VzLCBhbmQg
c2ltcGx5IGFzc3VtZSB0aGF0IHRoZSBQMk1QDQogICBQU04gTFNQIGlzIGF2YWlsYWJsZSB3aGVu
IG5lZWRlZC4NCg0KICAgUDJNUCBQVyBzaWduYWxpbmcgaXMgaW5pdGlhdGVkIGJ5IHRoZSBSLVBF
IHdoaWNoIHNlbmRzIGEgc2VwYXJhdGUNCiAgIFAyTVAtUFcgTERQIGxhYmVsIG1hcHBpbmcgbWVz
c2FnZSB0byBlYWNoIG9mIHRoZSB0aGUgTC1QRShzKQ0KICAgYmVsb25naW5nIHRvIHRoYXQgUDJN
UCBQVy4gVGhpcyBsYWJlbCBtYXBwaW5nIG1lc3NhZ2Ugd2lsbCBjb250YWluDQogICB0aGUgZm9s
bG93aW5nOg0KICAgICAgICAgMS4gQSBGRUMgVExWIGNvbnRhaW5pbmcgUDJNUCBQVyBVcHN0cmVh
bSBGRUMgZWxlbWVudCB0aGF0DQogICAgICAgICAgICBpbmNsdWRlcyBUcmFuc3BvcnQgTFNQIHN1
YiBUTFYuDQogICAgICAgICAyLiBBbiBJbnRlcmZhY2UgUGFyYW1ldGVycyBUTFYsIGFzIGRlc2Ny
aWJlZCBpbiBbUkZDNDQ0N2Jpc10uDQogICAgICAgICAzLiBBIFBXIEdyb3VwaW5nIFRMViwgYXMg
ZGVzY3JpYmVkIGluIFtSRkM0NDQ3YmlzXS4NCiAgICAgICAgIDQuIEEgbGFiZWwgVExWIGZvciB0
aGUgdXBzdHJlYW0tYXNzaWduZWQgbGFiZWwgdXNlZCBieSBSLVBFDQogICAgICAgICAgICBmb3Ig
dGhlIHRyYWZmaWMgZ29pbmcgZnJvbSBSLVBFIHRvIEwtUEUocykuDQoNCiAgIFRoZSBSLVBFIGlt
cG9zZXMgdGhlIHVwc3RyZWFtLWFzc2lnbmVkIFBXIGxhYmVsIG9uIHRoZSBvdXRib3VuZA0KICAg
cGFja2V0cyBzZW50IG92ZXIgdGhlIFAyTVAtUFcsIGFuZCB1c2luZyB0aGlzIGxhYmVsIGFuIEwt
UEUNCiAgIGlkZW50aWZpZXMgdGhlIGluYm91bmQgcGFja2V0cyBhcnJpdmluZyBvdmVyIHRoZSBQ
Mk1QIFBXLg0KDQogICBBZGRpdGlvbmFsbHksIHRoZSBSLVBFIE1BWSBzZW5kIGxhYmVsIG1hcHBp
bmcgbWVzc2FnZShzKSB0byBvbmUgb3INCiAgIG1vcmUgTC1QRShzKSB0byBzaWduYWwgdW5pZGly
ZWN0aW9uYWwgUDJQIFBXKHMpLiBUaGUgTC1QRShzKSBjYW4gdXNlDQogICBzdWNoIFBXKHMpIHRv
IHNlbmQgdHJhZmZpYyB0byB0aGUgUi1QRS4gVGhpcyBvcHRpb25hbCBsYWJlbCBtYXBwaW5nDQog
ICBtZXNzYWdlIHdpbGwgY29udGFpbiB0aGUgZm9sbG93aW5nOg0KDQogICAgICAgICAxLiBQMlAg
UFcgRG93bnN0cmVhbSBGRUMgZWxlbWVudC4NCiAgICAgICAgIDIuIEEgbGFiZWwgVExWIGZvciB0
aGUgZG93bi1zdHJlYW0gYXNzaWduZWQgbGFiZWwgdXNlZCBieSB0aGUNCiAgICAgICAgICAgIGNv
cnJlc3BvbmRpbmcgTC1QRSB0byBzZW5kIHRyYWZmaWMgdG8gdGhlIFItUEUuDQoNCiAgIFRoZSBM
RFAgbGliZXJhbCBsYWJlbCByZXRlbnRpb24gbW9kZSBNVVNUIGJlIHVzZWQsIGFuZCBwZXINCiAg
IHJlcXVpcmVtZW50cyBzcGVjaWZpZWQgaW4gW1JGQzUwMzZdLCB0aGUgTGFiZWwgUmVxdWVzdCBt
ZXNzYWdlIE1VU1QNCiAgIGFsc28gYmUgc3VwcG9ydGVkLg0KIA0KDQoNClNpdmFiYWxhbiAmIEJv
dXRyb3MgICAgRXhwaXJlcyBEZWNlbWJlciAxMiwgMjAxNyAgICAgICAgICAgICAgICBbUGFnZSA1
XQ0KDA0KSU5URVJORVQgRFJBRlQgICAgICAgICAgICAgICAgICBQMk1QIFBXICAgICAgICAgICAg
ICAgICAgICBKdW5lIDEwLCAyMDE3DQoNCg0KICAgVGhlIHVwc3RyZWFtLWFzc2lnbmVkIGxhYmVs
IGlzIGFsbG9jYXRlZCBhY2NvcmRpbmcgdG8gdGhlIHJ1bGVzIGluDQogICBbUkZDNTMzMV0uDQoN
CiAgIFdoZW4gYW4gTC1QRSByZWNlaXZlcyBhIFBXIExhYmVsIE1hcHBpbmcgTWVzc2FnZSwgaXQg
TVVTVCB2ZXJpZnkgdGhlDQogICBhc3NvY2lhdGVkIFAyTVAgUFNOIExTUCBpcyBpbiBwbGFjZS4g
SWYgdGhlIGFzc29jaWF0ZWQgUDJNUCBQU04gTFNQDQogICBpcyBub3QgaW4gcGxhY2UsIGFuZCBp
dHMgdHlwZSBpcyBMRFAgUDJNUCBMU1AsIHRoZSBMLVBFIE1VU1QgYXR0ZW1wdA0KICAgdG8gam9p
biB0aGUgUDJNUCBMU1AgYXNzb2NpYXRlZCB3aXRoIHRoZSBQMk1QIFBXLiBJZiB0aGUgYXNzb2Np
YXRlZA0KICAgUDJNUCBQU04gTFNQIGlzIG5vdCBpbiBwbGFjZSwgYW5kIGl0cyB0eXBlIGlzIFJT
VlAtVEUgUDJNUCBMU1AsIHRoZQ0KICAgTC1QRSBTSE9VTEQgd2FpdCB0aWxsIHRoZSBQMk1QIHRy
YW5zcG9ydCBMU1AgaXMgc2lnbmFsZWQuICBJZiBhbiBMLVBFDQogICBmYWlscyB0byBqb2luIHRo
ZSBQMk1QIFBTTiBMU1AsIHRoYXQgTC1QRSBNVVNUIG5vdCBlbmFibGUgdGhlIFBXLCBhbmQNCiAg
IE1VU1Qgbm90aWZ5IHRoZSB1c2VyLiBJbiB0aGlzIGNhc2UsIGEgUFcgc3RhdHVzIG1lc3NhZ2Ug
d2l0aCBzdGF0dXMNCiAgIGNvZGUgb2YgMHgwMDAwMDAwOCAoTG9jYWwgUFNOLWZhY2luZyBQVyAo
aW5ncmVzcykgUmVjZWl2ZSBGYXVsdCkgTVVTVA0KICAgYWxzbyBiZSBzZW50IHRvIHRoZSBSLVBF
Lg0KDQoyLjEgUFcgaW5ncmVzcyB0byBlZ3Jlc3MgaW5jb21wYXRpYmlsaXR5IGlzc3Vlcw0KDQog
ICBJZiBhbiBSLVBFIHNpZ25hbHMgYSBQVyB3aXRoIGEgcHcgdHlwZSwgQ1cgbW9kZSwgb3IgaW50
ZXJmYWNlDQogICBwYXJhbWV0ZXJzIHRoYXQgYSBwYXJ0aWN1bGFyIEwtUEUgY2Fubm90IGFjY2Vw
dCwgdGhlbiB0aGUgTC1QRSBNVVNUDQogICBub3QgZW5hYmxlIHRoZSBQVywgYW5kIG5vdGlmeSB0
aGUgdXNlci4gSW4gdGhpcyBjYXNlLCBhIFBXIHN0YXR1cw0KICAgbWVzc2FnZSB3aXRoIHN0YXR1
cyBjb2RlIG9mIDB4MDAwMDAwMDEgKFBzZXVkb3dpcmUgTm90IEZvcndhcmRpbmcpDQogICBNVVNU
IGFsc28gYmUgc2VudCB0byB0aGUgUi1QRS4NCg0KICAgTm90ZSB0aGF0IHRoaXMgcHJvY2VkdXJl
IGRvZXMgbm90IGFwcGx5IGlmIHRoZSBMLVBFIGhhZCBub3QgYmVlbg0KICAgcHJvdmlzaW9uZWQg
d2l0aCB0aGlzIHBhcnRpY3VsYXIgUDJNUCBQVy4gSW4gdGhpcyBjYXNlIGFjY29yZGluZyB0bw0K
ICAgdGhlIExEUCBsaWJlcmFsIGxhYmVsIHJldGVudGlvbiBydWxlcywgbm8gYWN0aW9uIGlzIHRh
a2VuLg0KDQoNCjIuMiBQMk1QIFBXIEZFQw0KDQogICBbUkZDNDQ0N2Jpc10gc3BlY2lmaWVzIHR3
byB0eXBlcyBvZiBMRFAgRkVDIGVsZW1lbnRzIGNhbGxlZCAiUFdpZCBGRUMNCiAgIEVsZW1lbnQi
IGFuZCAiR2VuZXJhbGl6ZWQgUFdpZCBGRUMgRWxlbWVudCIgdXNlZCB0byBzaWduYWwgUDJQIFBX
cy4NCiAgIFRoaXMgZG9jdW1lbnQgZGVmaW5lcyB0d28gbmV3IHR5cGVzIG9mIEZFQyBlbGVtZW50
cyBjYWxsZWQgIlAyTVAgUFcNCiAgIFVwc3RyZWFtIEZFQyBFbGVtZW50IiBhbmQgIlAyUCBQVyBE
b3duc3RyZWFtIEZFQyBFbGVtZW50Ii4gVGhlc2UgRkVDDQogICBlbGVtZW50cyBhcmUgYXNzb2Np
YXRlZCB3aXRoIGEgbWFuZGF0b3J5IHVwc3RyZWFtIGFzc2lnbmVkIGxhYmVsIGFuZA0KICAgYW4g
b3B0aW9uYWwgZG93bnN0cmVhbSBhc3NpZ25lZCBsYWJlbCByZXNwZWN0aXZlbHkuDQoNCjIuMi4x
IFAyTVAgUFcgVXBzdHJlYW0gRkVDIEVsZW1lbnQNCg0KICAgQSBuZXcgRkVDIHR5cGUgZm9yIHRo
ZSBQMk1QIFBXIFVwc3RyZWFtIEZFQyBFbGVtZW50IGlzIGVuY29kZWQgYXMNCiAgIGZvbGxvd3M6
DQoNCg0KDQoNCg0KDQoNCg0KIA0KDQoNClNpdmFiYWxhbiAmIEJvdXRyb3MgICAgRXhwaXJlcyBE
ZWNlbWJlciAxMiwgMjAxNyAgICAgICAgICAgICAgICBbUGFnZSA2XQ0KDA0KSU5URVJORVQgRFJB
RlQgICAgICAgICAgICAgICAgICBQMk1QIFBXICAgICAgICAgICAgICAgICAgICBKdW5lIDEwLCAy
MDE3DQoNCg0KICAgICAgIDAgICAgICAgICAgICAgICAgICAgMSAgICAgICAgICAgICAgICAgICAy
ICAgICAgICAgICAgICAgICAgIDMNCiAgICAgICAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMg
NCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDENCiAgICAgICstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQogICAg
ICB8UDJNUCBQVyBVcD0weDgyfEN8ICAgICAgICAgICBQVyBUeXBlICAgICAgICAgICB8IFBXIElu
Zm8gTGVuZ3RofA0KICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsNCiAgICAgIHwgICAgQUdJIFR5cGUgICB8ICAgICBM
ZW5ndGggICAgfCAgICAgICAgIEFHSSBWYWx1ZSAgICAgICAgICAgICB8DQogICAgICArLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Kw0KICAgICAgfiAgICAgICAgICAgICAgICAgICAgICAgQUdJIFZhbHVlIChjb250ZC4pICAgICAg
ICAgICAgICAgICAgICAgIH4NCiAgICAgIHwgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAgICArLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KICAgICAg
fCAgICBBSUkgVHlwZSAgIHwgICAgIExlbmd0aCAgICB8ICAgICAgICAgU0FJSSBWYWx1ZSAgICAg
ICAgICAgIHwNCiAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rDQogICAgICB+ICAgICAgICAgICAgICAgICAgICAgICBT
QUlJIFZhbHVlIChjb250ZC4pICAgICAgICAgICAgICAgICAgICAgfg0KICAgICAgfCAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwN
CiAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rDQogICAgICB8UE1TSSBUdW5uZWwgdHlwfCAgICAgTGVuZ3RoICAgIHwg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgICAgKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICsNCiAgICAgICsg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICArDQogICAgICB+ICAgICAgICAgICAgICAgICAgIFRyYW5zcG9ydCBMU1AgSUQgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgfg0KICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwNCiAgICAgICstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQog
ICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgfA0KICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgT3B0aW9uYWwgUGFy
YW1ldGVycyAgICAgICAgICAgICAgICAgICAgIHwNCiAgICAgIH4gICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB+DQogICAgICArLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKw0KDQoNCiAgICAgICAgICAgICAgICAgICBGaWd1cmUgMjogUDJNUCBQVyBVcHN0cmVhbSBG
RUMgRWxlbWVudA0KDQogICAqIFAyTVAgUFcgVXA6DQoNCiAgIDggYml0cyByZXByZXNlbnRhdGlv
biBmb3IgdGhlIFAyTVAgUFcgVXBzdHJlYW0gRkVDIHR5cGUuDQoNCiAgICogUFcgVHlwZToNCg0K
ICAgMTUgYml0cyByZXByZXNlbnRhdGlvbiBvZiBQVyB0eXBlIGFzIHNwZWNpZmllZCBpbiBbUkZD
NDQ0N10uDQoNCiAgICogQyBiaXQ6DQoNCiAgIEEgdmFsdWUgb2YgMSBvciAwIGluZGljYXRlcyB3
aGV0aGVyIGNvbnRyb2wgd29yZCBpcyBwcmVzZW50IG9yIGFic2VudA0KICAgZm9yIHRoZSBQMk1Q
IFBXLg0KDQogICAqIFBXIEluZm8gTGVuZ3RoOg0KDQogICBTdW0gb2YgdGhlIGxlbmd0aHMgb2Yg
QUdJLCBTQUlJLCBQTVNJIFR1bm5lbCBpbmZvLCBhbmQgT3B0aW9uYWwNCiAgIFBhcmFtZXRlcnMg
ZmllbGQgaW4gb2N0ZXRzLiBJZiB0aGlzIHZhbHVlIGlzIDAsIHRoZW4gaXQgcmVmZXJlbmNlcw0K
ICAgYWxsIFBXcyB1c2luZyB0aGUgc3BlY2lmaWVkIGdyb3VwaW5nIElELiBJbiB0aGlzIGNhc2Us
IHRoZXJlIGFyZQ0KICAgbmVpdGhlciBvdGhlciBGRUMgZWxlbWVudCBmaWVsZHMgKEFHSSwgU0FJ
SSwgZXRjLikgcHJlc2VudCwgbm9yIGFueQ0KIA0KDQoNClNpdmFiYWxhbiAmIEJvdXRyb3MgICAg
RXhwaXJlcyBEZWNlbWJlciAxMiwgMjAxNyAgICAgICAgICAgICAgICBbUGFnZSA3XQ0KDA0KSU5U
RVJORVQgRFJBRlQgICAgICAgICAgICAgICAgICBQMk1QIFBXICAgICAgICAgICAgICAgICAgICBK
dW5lIDEwLCAyMDE3DQoNCg0KICAgaW50ZXJmYWNlIHBhcmFtZXRlcnMgVExWcy4gQWx0ZXJuYXRp
dmVseSwgdHlwZWQgd2lsZGNhcmQgRkVDDQogICBkZXNjcmliZWQgaW4gc2VjdGlvbiAzLjMsIGNh
biBiZSB1c2VkIHRvIGFjaGlldmUgdGhlIHNhbWUgb3IgdG8gaGF2ZQ0KICAgYmV0dGVyIGZpbHRl
cmluZy4NCg0KICAgKiBBR0k6DQoNCiAgIEF0dGFjaG1lbnQgR3JvdXAgSWRlbnRpZmllciBjYW4g
YmUgdXNlZCB0byB1bmlxdWVseSBpZGVudGlmeSBWUE4gb3INCiAgIFZQTFMgaW5zdGFuY2UgYXNz
b2NpYXRlZCB3aXRoIHRoZSBQMk1QIFBXLiBUaGlzIGhhcyB0aGUgc2FtZSBmb3JtYXQNCiAgIGFz
IHRoZSBHZW5lcmFsaXplZCBQV2lkIEZFQyBlbGVtZW50IFtSRkM0NDQ3YmlzXS4NCg0KICAgKiBT
QUlJOg0KDQogICBTb3VyY2UgQXR0YWNobWVudCBJbmRpdmlkdWFsIElkZW50aWZpZXIgaXMgdXNl
ZCB0byBpZGVudGlmeSB0aGUgcm9vdA0KICAgb2YgdGhlIFAyTVAgUFcuIFRoZSByb290IGlzIHJl
cHJlc2VudGVkIHVzaW5nIEFJSSB0eXBlIDIgZm9ybWF0DQogICBzcGVjaWZpZWQgaW4gW1JGQzUw
MDNdLiAgTm90ZSB0aGF0IHRoZSBTQUlJIGNhbiBiZSBvbWl0dGVkIGJ5IHNpbXBseQ0KICAgc2V0
dGluZyB0aGUgbGVuZ3RoIGFuZCB0eXBlIHRvIHplcm8uDQoNCiAgIFAyTVAgUFcgaXMgaWRlbnRp
ZmllZCBieSB0aGUgU291cmNlIEF0dGFjaG1lbnQgSWRlbnRpZmllciAoU0FJKS4gSWYNCiAgIHRo
ZSBBR0kgaXMgbm9uLW51bGwsIHRoZSBTQUkgaXMgdGhlIGNvbWJpbmF0aW9uIG9mIHRoZSBTQUlJ
IGFuZCB0aGUNCiAgIEFHSSwgaWYgdGhlIEFHSSBpcyBudWxsLCB0aGUgU0FJIGlzIHRoZSBTQUlJ
Lg0KDQogICAqIFBNU0kgVHVubmVsIFR5cGUgYW5kIFRyYW5zcG9ydCBMU1AgSUQ6DQoNCiAgIEEg
UDJNUCBQVyBNVVNUIGJlIGFzc29jaWF0ZWQgd2l0aCBhIHRyYW5zcG9ydCBMU1Agd2hpY2ggY2Fu
IGJlDQogICBlc3RhYmxpc2hlZCB1c2luZyBSU1ZQLVRFIG9yIG1MRFAuDQoNCiAgICogUE1TSSBU
dW5uZWwgVHlwZToNCg0KICAgVGhlIFBNU0kgdHVubmVsIHR5cGUgaXMgZGVmaW5lZCBpbiBbUkZD
NjUxNF0uDQoNCiAgIFdoZW4gdGhlIHR5cGUgaXMgc2V0IHRvIG1MRFAgUDJNUCBMU1AsIHRoZSBU
dW5uZWwgSWRlbnRpZmllciBpcyBhDQogICBQMk1QIEZFQyBFbGVtZW50IGFzIGRlZmluZWQgaW4g
W1JGQzYzODhdLiBBIG5ldyBtTERQIE9wYXF1ZSBWYWx1ZQ0KICAgRWxlbWVudCB0eXBlIGZvciBM
MlZQTi1NQ0FTVCBhcHBsaWNhdGlvbiBhcyBzcGVjaWZpZWQgaW4gdGhlIElBTkENCiAgIGNvbnNp
ZGVyYXRpb25zIE1VU1QgYmUgdXNlZC4NCg0KICAgKiBUcmFuc3BvcnQgTFNQIElEOiBUaGlzIGlz
IHRoZSBUdW5uZWwgSWRlbnRpZmllciB3aGljaCBpcyBkZWZpbmVkIGluDQogICBbUkZDNjUxNF0u
DQoNCiAgIEFuIFItUEUgc2VuZHMgTGFiZWwgTWFwcGluZyBNZXNzYWdlIGFzIHNvb24gYXMgdGhl
IHRyYW5zcG9ydCBMU1AgSUQNCiAgIGFzc29jaWF0ZWQgd2l0aCB0aGUgUDJNUCBQVyBpcyBrbm93
biAoZS5nLiwgdmlhIGNvbmZpZ3VyYXRpb24pDQogICByZWdhcmRsZXNzIG9mIHRoZSBvcGVyYXRp
b25hbCBzdGF0ZSBvZiB0aGF0IHRyYW5zcG9ydCBMU1AuIFNpbWlsYXJseSwNCiAgIGFuIFItUEUg
ZG9lcyBub3Qgd2l0aGRyYXcgdGhlIGxhYmVscyB3aGVuIHRoZSBjb3JyZXNwb25kaW5nIHRyYW5z
cG9ydA0KICAgTFNQIGdvZXMgZG93bi4gRnVydGhlcm1vcmUsIGFuIEwtUEUgcmV0YWlucyB0aGUg
UDJNUCBQVyBsYWJlbHMNCiAgIHJlZ2FyZGxlc3Mgb2YgdGhlIG9wZXJhdGlvbmFsIHN0YXR1cyBv
ZiB0aGUgdHJhbnNwb3J0IExTUC4NCg0KICAgTm90ZSB0aGF0IGEgZ2l2ZW4gdHJhbnNwb3J0IExT
UCBjYW4gYmUgYXNzb2NpYXRlZCB3aXRoIG1vcmUgdGhhbiBvbmUNCiAgIFAyTVAgUFdzIGluIHdo
aWNoIGNhc2UgUDJNUCBQV3Mgd2lsbCBiZSBzaGFyaW5nIHRoZSBzYW1lIFItUEUgYW5kIEwtDQog
ICBQRShzKS4gQW4gUi1QRSBtYXkgYWxzbyBoYXZlIG1hbnkgUDJNUCBQV3Mgd2l0aCBkaXNqb2lu
dCBMLVBFIHNldHMuDQogDQoNCg0KU2l2YWJhbGFuICYgQm91dHJvcyAgICBFeHBpcmVzIERlY2Vt
YmVyIDEyLCAyMDE3ICAgICAgICAgICAgICAgIFtQYWdlIDhdDQoMDQpJTlRFUk5FVCBEUkFGVCAg
ICAgICAgICAgICAgICAgIFAyTVAgUFcgICAgICAgICAgICAgICAgICAgIEp1bmUgMTAsIDIwMTcN
Cg0KDQogICBJbiB0aGUgY2FzZSBvZiBMRFAgUDJNUCBMU1AsIHdoZW4gYW4gTC1QRSByZWNlaXZl
cyB0aGUgTGFiZWwgTWFwcGluZw0KICAgTWVzc2FnZSwgaXQgY2FuIGluaXRpYXRlIHRoZSBwcm9j
ZXNzIG9mIGpvaW5pbmcgdGhlIFAyTVAgTFNQIHRyZWUNCiAgIGFzc29jaWF0ZWQgd2l0aCB0aGUg
UDJNUCBQVy4NCg0KICAgSW4gdGhlIGNhc2Ugb2YgUlNWUC1URSBQMk1QIExTUCwgb25seSB0aGUg
Ui1QRSBpbml0aWF0ZXMgdGhlDQogICBzaWduYWxpbmcgb2YgUDJNUCBMU1AuDQoNCiAgICogT3B0
aW9uYWwgUGFyYW1ldGVyczoNCg0KICAgVGhlIE9wdGlvbmFsIFBhcmFtZXRlciBmaWVsZCBjYW4g
Y29udGFpbiBzb21lIFRMVnMgdGhhdCBhcmUgbm90IHBhcnQNCiAgIG9mIHRoZSBGRUMsIGJ1dCBh
cmUgbmVjZXNzYXJ5IGZvciB0aGUgb3BlcmF0aW9uIG9mIHRoZSBQVy4gVGhpcw0KICAgcHJvcG9z
ZWQgbWVjaGFuaXNtIHVzZXMgdHdvIHN1Y2ggVExWczogSW50ZXJmYWNlIFBhcmFtZXRlcnMgVExW
LCBhbmQNCiAgIEdyb3VwIElEIFRMVi4NCg0KICAgVGhlIEludGVyZmFjZSBQYXJhbWV0ZXJzIFRM
ViBhbmQgR3JvdXAgSUQgVExWIHNwZWNpZmllZCBpbg0KICAgW1JGQzQ0NDdiaXNdIGNhbiBhbHNv
IGJlIHVzZWQgaW4gY29uanVuY3Rpb24gd2l0aCBQMk1QIFBXIEZFQyBpbiBhDQogICBsYWJlbCBt
ZXNzYWdlLiBGb3IgR3JvdXAgSUQgVExWLCB0aGUgc2VuZGVyIGFuZCByZWNlaXZlciBvZiB0aGVz
ZQ0KICAgVExWcyBzaG91bGQgZm9sbG93IHRoZSBzYW1lIHJ1bGVzIGFuZCBwcm9jZWR1cmVzIHNw
ZWNpZmllZCBpbg0KICAgW1JGQzQ0NDdiaXNdLiBGb3IgSW50ZXJmYWNlIFBhcmFtZXRlcnMgVExW
LCB0aGUgcHJvY2VkdXJlIGRpZmZlcnMNCiAgIGZyb20gdGhlIG9uZSBzcGVjaWZpZWQgaW4gW1JG
QzQ0NDdiaXNdIGR1ZSB0byBzcGVjaWZpY3Mgb2YgUDJNUA0KICAgY29ubmVjdGl2aXR5LiBXaGVu
IHRoZSBpbnRlcmZhY2UgcGFyYW1ldGVycyBhcmUgc2lnbmFsZWQgYnkgYSBSLVBFLA0KICAgZWFj
aCBMLVBFIG11c3QgY2hlY2sgaWYgaXRzIGNvbmZpZ3VyZWQgdmFsdWUocykgaXMgbGVzcyB0aGFu
IG9yIGVxdWFsDQogICB0byB0aGUgdGhyZXNob2xkIHZhbHVlIHByb3ZpZGVkIGJ5IHRoZSBSLVBF
IChlLmcuIE1UVSBzaXplDQogICAoRXRoZXJuZXQpLCBtYXggbnVtYmVyIG9mIGNvbmNhdGVuYXRl
ZCBBVE0gY2VsbHMsIGV0YykpLiBGb3Igb3RoZXINCiAgIGludGVyZmFjZSBwYXJhbWV0ZXJzIGxp
a2UgQ0VQL1RETSBQYXlsb2FkIGJ5dGVzIChURE0pLCB0aGUgdmFsdWUgTVVTVA0KICAgZXhhY3Rs
eSBtYXRjaCB0aGUgdmFsdWVzIHNpZ25hbGVkIGJ5IHRoZSBSLVBFLg0KDQogICBNdWx0aWNhc3Qg
dHJhZmZpYyBzdHJlYW0gYXNzb2NpYXRlZCB3aXRoIGEgUDJNUCBQVyBjYW4gYmUgc2VsZWN0aXZl
DQogICBvciBpbmNsdXNpdmUuIFRvIHN1cHBvcnQgdGhlIGZvcm1lciwgdGhpcyBkb2N1bWVudCBk
ZWZpbmVzIGEgbmV3DQogICBvcHRpb25hbCBTZWxlY3RpdmUgVHJlZSBJbnRlcmZhY2UgUGFyYW1l
dGVyIHN1Yi1UTFYsIGFzIGRlc2NyaWJlZCBpbg0KICAgdGhlIElBTkEgY29uc2lkZXJhdGlvbnMg
YW5kIGFjY29yZGluZyB0byB0aGUgZm9ybWF0IGRlc2NyaWJlZCBpbg0KICAgW1JGQzQ0NDdiaXNd
LiBUaGUgdmFsdWUgb2YgdGhlIHN1Yi1UTFYgY29udGFpbnMgdGhlIHNvdXJjZSBhbmQgdGhlDQog
ICBncm91cCBmb3IgYSBnaXZlbiBtdWx0aWNhc3QgdHJlZSBhcyBzaG93biBpbiBGaWd1cmUgMy4g
QWxzbywgaWYgYQ0KICAgUDJNUCBQVyBpcyBhc3NvY2lhdGVkIHdpdGggbXVsdGlwbGUgc2VsZWN0
aXZlIHRyZWVzLCB0aGUNCiAgIGNvcnJlc3BvbmRpbmcgbGFiZWwgbWFwcGluZyBtZXNzYWdlIHdp
bGwgY2FycnkgbW9yZSB0aGFuIG9uZSBpbnN0YW5jZQ0KICAgb2YgdGhpcyBTdWItVExWLiBGdXJ0
aGVybW9yZSwgaW4gdGhlIGFic2VuY2Ugb2YgdGhpcyBzdWItVExWLCB0aGUNCiAgIFAyTVAgUFcg
aXMgYXNzb2NpYXRlZCB3aXRoIGFsbCBtdWx0aWNhc3QgdHJhZmZpYyBzdHJlYW0gb3JpZ2luYXRp
bmcNCiAgIGZyb20gdGhlIHJvb3QuDQoNCiAgICAgICAgICAgICAgICAgICAgICArLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gKw0KICAgICAgICAgICAgICAgICAgICAg
IHwgICAgICAgICAgICBTdWItVExWIFR5cGUgKDEgT2N0ZXQpICAgICAgICB8DQogICAgICAgICAg
ICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tICsN
CiAgICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICBMZW5ndGggKDEgT2N0ZXQpICAg
ICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLSArDQogICAgICAgICAgICAgICAgICAgICAgfCBNdWx0aWNhc3Qg
U291cmNlIExlbmd0aCAoMSBPY3RldCkgICAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAr
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gKw0KICAgICAgICAgICAg
ICAgICAgICAgIHwgTXVsdGljYXN0IFNvdXJjZSAodmFyaWFibGUgbGVuZ3RoKSAgICAgICB8DQog
ICAgICAgICAgICAgICAgICAgICAgKy0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tICsNCiANCg0KDQpTaXZhYmFsYW4gJiBCb3V0cm9zICAgIEV4cGlyZXMgRGVjZW1iZXIg
MTIsIDIwMTcgICAgICAgICAgICAgICAgW1BhZ2UgOV0NCgwNCklOVEVSTkVUIERSQUZUICAgICAg
ICAgICAgICAgICAgUDJNUCBQVyAgICAgICAgICAgICAgICAgICAgSnVuZSAxMCwgMjAxNw0KDQoN
CiAgICAgICAgICAgICAgICAgICAgICB8IE11bHRpY2FzdCBHcm91cCBMZW5ndGggKDEgT2N0ZXQp
ICAgICAgICAgfA0KICAgICAgICAgICAgICAgICAgICAgICstLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLSArDQogICAgICAgICAgICAgICAgICAgICAgfCBNdWx0aWNhc3Qg
R3JvdXAgKHZhcmlhYmxlIGxlbmd0aCkgICAgICAgIHwNCiAgICAgICAgICAgICAgICAgICAgICAr
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gKw0KDQoNCiAgICAgICAg
ICAgICAgRmlndXJlIDM6IFNlbGVjdGl2ZSBUcmVlIEludGVyZmFjZSBQYXJhbWV0ZXIgU3ViLVRM
ViBWYWx1ZQ0KDQogICBOb3RlIHRoYXQgc2luY2UgdGhlIExEUCBsYWJlbCBtYXBwaW5nIG1lc3Nh
Z2UgaXMgb25seSBzZW50IGJ5IHRoZSBSLQ0KICAgUEUgdG8gYWxsIHRoZSBMLVBFcywgaXQgaXMg
bm90IHBvc3NpYmxlIHRvIG5lZ290aWF0ZSBhbnkgaW50ZXJmYWNlDQogICBwYXJhbWV0ZXJzLg0K
DQoyLjIuMiBQMlAgUFcgRG93bnN0cmVhbSBGRUMgRWxlbWVudA0KDQogICBUaGUgb3B0aW9uYWwg
UDJQIFBXIERvd25zdHJlYW0gRkVDIEVsZW1lbnQgaXMgZW5jb2RlZCBhcyBmb2xsb3dzOg0KDQoN
CiAgICAgICAwICAgICAgICAgICAgICAgICAgIDEgICAgICAgICAgICAgICAgICAgMiAgICAgICAg
ICAgICAgICAgICAzDQogICAgICAgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2IDcg
OCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxDQogICAgICArLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KICAgICAgfFAyUCBQ
V0Rvd249MHg4M3xDfCAgICAgICAgICAgUFcgVHlwZSAgICAgICAgICAgfCBQVyBJbmZvIExlbmd0
aHwNCiAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rDQogICAgICB8ICAgIEFHSSBUeXBlICAgfCAgICAgTGVuZ3RoICAg
IHwgICAgICAgICBBR0kgVmFsdWUgICAgICAgICAgICAgfA0KICAgICAgKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsNCiAgICAg
IH4gICAgICAgICAgICAgICAgICAgICAgIEFHSSBWYWx1ZSAoY29udGQuKSAgICAgICAgICAgICAg
ICAgICAgICB+DQogICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgfA0KICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsNCiAgICAgIHwgICAgQUlJ
IFR5cGUgICB8ICAgICBMZW5ndGggICAgfCAgICAgICAgIFNBSUkgVmFsdWUgICAgICAgICAgICB8
DQogICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKw0KICAgICAgfiAgICAgICAgICAgICAgICAgICAgICAgU0FJSSBWYWx1
ZSAoY29udGQuKSAgICAgICAgICAgICAgICAgICAgIH4NCiAgICAgIHwgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8DQogICAgICAr
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKw0KDQogICAgICAgICAgICAgICAgICBGaWd1cmUgNDogUDJQIFBXIERvd25zdHJlYW0g
RkVDIEVsZW1lbnQNCg0KICAgVGhlIGRlZmluaXRpb24gb2YgdGhlIGZpZWxkcyBpbiB0aGUgUDJQ
IFBXIERvd25zdHJlYW0gRkVDIEVsZW1lbnQgaXMNCiAgIHRoZSBzYW1lIGFzIHRob3NlIG9mIFAy
TVAgUFcgVXBzdHJlYW0gRkVDIEVsZW1lbnQgc2hvd24gaW4gRmlndXJlIDIuDQoNCjIuMyBUeXBl
ZCBXaWxkY2FyZCBGRUMgRm9ybWF0IGZvciBuZXcgRkVDIA0KDQogICBbUkZDNTkxOF0gZGVmaW5l
cyB0aGUgZ2VuZXJhbCBub3Rpb24gb2YgYSAiVHlwZWQgV2lsZGNhcmQiIEZFQw0KICAgRWxlbWVu
dCwgYW5kIHJlcXVpcmVzIEZFQyBkZXNpZ25lciB0byBzcGVjaWZ5IGEgdHlwZWQgd2lsZGNhcmQg
RkVDDQogICBlbGVtZW50IGZvciBuZXdseSBkZWZpbmVkIEZFQyBlbGVtZW50IHR5cGVzLiBUaGlz
IGRvY3VtZW50IGRlZmluZXMNCiAgIHR3byBuZXcgRkVDIGVsZW1lbnRzLCAiUDJNUCBQVyBVcHN0
cmVhbSIgYW5kICJQMlAgUFcgRG93bnN0cmVhbSIgRkVDDQogICBlbGVtZW50LCBhbmQgaGVuY2Ug
cmVxdWlyZXMgdXMgdG8gZGVmaW5lIHRoZWlyIFR5cGVkIFdpbGRjYXJkIGZvcm1hdC4NCg0KICAg
W1JGQzY2NjddIGRlZmluZXMgVHlwZWQgV2lsZGNhcmQgRkVDIGVsZW1lbnQgZm9ybWF0IGZvciBv
dGhlciBQVyBGRUMNCiAgIEVsZW1lbnQgdHlwZXMgKFBXaWQgYW5kIEdlbi4gUFdpZCBGRUMgRWxl
bWVudCkgaW4gc2VjdGlvbiAyIGFzDQogDQoNCg0KU2l2YWJhbGFuICYgQm91dHJvcyAgICBFeHBp
cmVzIERlY2VtYmVyIDEyLCAyMDE3ICAgICAgICAgICAgICAgW1BhZ2UgMTBdDQoMDQpJTlRFUk5F
VCBEUkFGVCAgICAgICAgICAgICAgICAgIFAyTVAgUFcgICAgICAgICAgICAgICAgICAgIEp1bmUg
MTAsIDIwMTcNCg0KDQogICBmb2xsb3dzOg0KDQogICAgICAgMCAgICAgICAgICAgICAgICAgICAx
ICAgICAgICAgICAgICAgICAgIDIgICAgICAgICAgICAgICAgICAgMw0KICAgICAgIDAgMSAyIDMg
NCA1IDYgNyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMQ0K
ICAgICAgKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSsNCiAgICAgIHxUeXBlZCBXY2FyZD0weDV8VHlwZT1QVyBGRUMgICAgfCAg
IExlbiA9IDMgICAgIHxSfCAgIFBXIHR5cGUgICB8DQogICAgICArLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKw0KICAgICAgfCAg
ICAuIC4gLiAgICAgIHwgUE1TSSBUdW4gVHlwZSB8DQogICAgICArLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSsNCiAgICAgICAgICAgIEZpZ3VyZSA1OiBUeXBlZCBXaWxkY2FyZCBGb3Jt
YXQgZm9yIFAyTVAgUFcgRkVDIEVsZW1lbnRzDQoNCiAgIFtSRkM2NjY3XSBzcGVjaWZpZXMgdGhh
dCAiVHlwZSIgZmllbGQgY2FuIGJlIGVpdGhlciAiUFdpZCIgKDB4ODApIG9yDQogICAiR2VuZXJh
bGl6ZWQgUFdpZCIgKDB4ODEpIEZFQyBlbGVtZW50IHR5cGUuIFRoaXMgZG9jdW1lbnQgcmV1c2Vz
IHRoZQ0KICAgZXhpc3RpbmcgdHlwZWQgd2lsZGNhcmQgZm9ybWF0IGFzIHNwZWNpZmllZCBpbiBb
UkZDNjY2N10gYW5kDQogICBpbGx1c3RyYXRlZCBpbiBGaWd1cmUgNSBhbmQgZXh0ZW5kcyB0aGUg
ZGVmaW5pdGlvbiBvZiAiVHlwZSIgZmllbGQgdG8NCiAgIGFsc28gaW5jbHVkZSAiUDJNUCBQVyBV
cHN0cmVhbSIgYW5kICJQMlAgUFcgRG93bnN0cmVhbSIgRkVDIGVsZW1lbnQNCiAgIHR5cGVzLiBU
aGlzIGRvY3VtZW50IGFkZHMgYW4gYWRkaXRpb25hbCBmaWVsZCAiUE1TSSBUdW4gVHlwZSIuIFRo
aXMNCiAgIGRvY3VtZW50IHJlc2VydmVzIFBNU0kgdHVubmVsIFR5cGUgMHhGRiB0byBtZWFuICJ3
aWxkY2FyZCIgdHJhbnNwb3J0DQogICB0dW5uZWwgdHlwZS4gVGhlIFBNU0kgdHVubmVsIFR5cGUg
ZmllbGQgb25seSBhcHBsaWVzIHRvIFR5cGVkDQogICB3aWxkY2FyZCBQMk1QIFBXIFVwc3RyZWFt
IEZFQyBhbmQgTVVTVCBiZSBzZXQgdG8gIndpbGRjYXJkIiBmb3IgIlAyUA0KICAgUFcgRG93bnN0
cmVhbSBGRUMiIHR5cGVkIHdpbGRjYXJkIGVsZW1lbnQuDQoNCjIuNCBHcm91cCBJRCB1c2FnZQ0K
DQogICBUaGUgR3JvdXBpbmcgVExWIGFzIGRlZmluZWQgaW4gW1JGQzQ0NDdiaXNdIGNvbnRhaW5z
IGEgZ3JvdXAgSUQNCiAgIGNhcGFibGUgb2YgaW5kaWNhdGluZyBhbiBhcmJpdHJhcnkgZ3JvdXAg
bWVtYmVyc2hpcCBvZiBhIFAyTVAtUFcuDQogICBUaGlzIGdyb3VwIElEIGNhbiBiZSB1c2VkIGlu
IExEUCAid2lsZCBjYXJkIiBzdGF0dXMsIGFuZCB3aXRoZHJhdw0KICAgbGFiZWwgbWVzc2FnZXMs
IGFzIGRlc2NyaWJlZCBpbiBbUkZDNDQ0N2Jpc10uDQoNCjIuNSBHZW5lcmljIExhYmVsIFRMVg0K
DQogICBBcyBpbiB0aGUgY2FzZSBvZiBQMlAgUFcgc2lnbmFsaW5nLCBQMk1QIFBXIGxhYmVscyBh
cmUgY2FycmllZCB3aXRoaW4NCiAgIEdlbmVyaWMgTGFiZWwgVExWIGNvbnRhaW5lZCBpbiBMRFAg
TGFiZWwgTWFwcGluZyBNZXNzYWdlLiBBIEdlbmVyaWMNCiAgIExhYmVsIFRMViBpcyBmb3JtYXR0
ZWQgYW5kIHByb2Nlc3NlZCBhcyBwZXIgdGhlIHJ1bGVzIGFuZCBwcm9jZWR1cmVzDQogICBzcGVj
aWZpZWQgaW4gW1JGQzQ0NDdiaXNdLiBGb3IgYSBnaXZlbiBQMk1QIFBXLCBhIHNpbmdsZSB1cHN0
cmVhbS0NCiAgIGFzc2lnbmVkIGxhYmVsIGlzIGFsbG9jYXRlZCBieSB0aGUgUi1QRSwgYW5kIGlz
IGFkdmVydGlzZWQgdG8gYWxsIEwtDQogICBQRXMgdXNpbmcgdGhlIEdlbmVyaWMgTGFiZWwgVExW
IGluIGxhYmVsIG1hcHBpbmcgbWVzc2FnZSBjb250YWluaW5nDQogICB0aGUgUDJNUCBQVyBVcHN0
cmVhbSBGRUMgZWxlbWVudC4NCg0KICAgVGhlIFItUEUgY2FuIGFsc28gYWxsb2NhdGUgYSB1bmlx
dWUgbGFiZWwgZm9yIGVhY2ggTC1QRSBmcm9tIHdoaWNoIGl0DQogICBpbnRlbmRzIHRvIHJlY2Vp
dmUgUDJQIHRyYWZmaWMuIFN1Y2ggYSBsYWJlbCBpcyBhZHZlcnRpc2VkIHRvIHRoZSBMLQ0KICAg
UEUgdXNpbmcgR2VuZXJpYyBMYWJlbCBUTFYgYW5kIFAyUCBQVyBEb3duc3RyZWFtIEZFQyBpbiBs
YWJlbCBtYXBwaW5nDQogICBtZXNzYWdlLg0KDQoNCjMuIExEUCBDYXBhYmlsaXR5IE5lZ290aWF0
aW9uDQoNCiAgIFRoZSBjYXBhYmlsaXR5IG9mIHN1cHBvcnRpbmcgUDJNUCBQVyBNVVNUIGJlIGFk
dmVydGlzZWQgdG8gYWxsIExEUA0KIA0KDQoNClNpdmFiYWxhbiAmIEJvdXRyb3MgICAgRXhwaXJl
cyBEZWNlbWJlciAxMiwgMjAxNyAgICAgICAgICAgICAgIFtQYWdlIDExXQ0KDA0KSU5URVJORVQg
RFJBRlQgICAgICAgICAgICAgICAgICBQMk1QIFBXICAgICAgICAgICAgICAgICAgICBKdW5lIDEw
LCAyMDE3DQoNCg0KICAgcGVlcnMuIFRoaXMgaXMgYWNoaWV2ZWQgYnkgdXNpbmcgdGhlIG1ldGhv
ZHMgaW4gW1JGQzU1NjFdIHRvDQogICBhZHZlcnRpc2UgdGhlIExEUCAiUDJNUCBQVyBDYXBhYmls
aXR5IiBUTFYuIElmIGFuIExEUCBwZWVyIHN1cHBvcnRzDQogICB0aGUgZHluYW1pYyBjYXBhYmls
aXR5IGFkdmVydGlzZW1lbnQsIHRoaXMgY2FuIGJlIGRvbmUgYnkgc2VuZGluZyBhDQogICBuZXcg
Q2FwYWJpbGl0eSBtZXNzYWdlIHdpdGggdGhlIFMgYml0IHNldCBmb3IgdGhlIFAyTVAgUFcgY2Fw
YWJpbGl0eQ0KICAgVExWLiBJZiB0aGUgcGVlciBkb2VzIG5vdCBzdXBwb3J0cyBkeW5hbWljIGNh
cGFiaWxpdHkgYWR2ZXJ0aXNlbWVudCwNCiAgIHRoZW4gdGhlIFAyTVAgUFcgQ2FwYWJpbGl0eSBU
TFYgTVVTVCBiZSBpbmNsdWRlZCBpbiB0aGUgTERQDQogICBJbml0aWFsaXphdGlvbiBtZXNzYWdl
IGR1cmluZyB0aGUgc2Vzc2lvbiBlc3RhYmxpc2htZW50LiBBbiBMU1INCiAgIGhhdmluZyBQMk1Q
IFBXIGNhcGFiaWxpdHkgTVVTVCByZWNvZ25pemUgYm90aCBQMk1QIFBXIFVwc3RyZWFtIEZFQw0K
ICAgRWxlbWVudCBhbmQgUDJQIFBXIERvd25zdHJlYW0gRkVDIEVsZW1lbnQgaW4gTERQIGxhYmVs
IG1lc3NhZ2VzLg0KDQogICBJbiBsaW5lIHdpdGggcmVxdWlyZW1lbnRzIGxpc3RlZCBpbiBbUkZD
NTU2MV0sIHRoZSBmb2xsb3dpbmcgVExWIGlzDQogICBkZWZpbmVkIHRvIGluZGljYXRlIHRoZSBQ
Mk1QIFBXIGNhcGFiaWxpdHk6DQoNCiAgICAgICAwICAgICAgICAgICAgICAgICAgIDEgICAgICAg
ICAgICAgICAgICAgMiAgICAgICAgICAgICAgICAgICAzDQogICAgICAgMCAxIDIgMyA0IDUgNiA3
IDggOSAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxDQogICAgICAr
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKw0KICAgICAgfFV8RnwgUDJNUCBQVyBDYXBhYmlsaXR5IFRMViAgICB8ICAgICAgICAg
ICAgTGVuZ3RoICAgICAgICAgICAgIHwNCiAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rDQogICAgICB8U3wgUmVzZXJ2
ZWQgICAgfCAgICBSZXNlcnZlZCAgIHwNCiAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKw0KDQogICAgICAgICAgICAgICAgICAgICBGaWd1cmUgNzogTERQIFAyTVAgUFcgQ2Fw
YWJpbGl0eSBUTFYNCg0KICAgKiBVLWJpdDoNCg0KICAgICBTSE9VTEQgYmUgMSAoaWdub3JlIGlm
IG5vdCB1bmRlcnN0b29kKS4NCg0KICAgKiBGLWJpdDoNCg0KICAgICBTSE9VTEQgYmUgMCAoZG9u
J3QgZm9yd2FyZCBpZiBub3QgdW5kZXJzdG9vZCkuDQoNCiAgICogUDJNUCBQVyBDYXBhYmlsaXR5
IFRMViBDb2RlIFBvaW50Og0KDQogICAgIFRoZSBUTFYgdHlwZSwgd2hpY2ggaWRlbnRpZmllcyBh
IHNwZWNpZmljIGNhcGFiaWxpdHkuIFRoZSBQMk1QIFBXIA0KICAgY2FwYWJpbGl0eSBjb2RlIHBv
aW50IGlzIHJlcXVlc3RlZCBpbiB0aGUgSUFOQSBhbGxvY2F0aW9uIHNlY3Rpb24gDQogICBiZWxv
dy4NCg0KICAgKiBTLWJpdDoNCg0KICAgICBUaGUgU3RhdGUgQml0IGluZGljYXRlcyB3aGV0aGVy
IHRoZSBzZW5kZXIgaXMgYWR2ZXJ0aXNpbmcgb3IgDQogICB3aXRoZHJhd2luZyB0aGUgUDJNUCBQ
VyBjYXBhYmlsaXR5LiBUaGUgU3RhdGUgYml0IGlzIHVzZWQgYXMgDQogICBmb2xsb3dzOg0KICAg
ICAgICAgMSAtIFRoZSBUTFYgaXMgYWR2ZXJ0aXNpbmcgdGhlIGNhcGFiaWxpdHkgc3BlY2lmaWVk
IGJ5IHRoZQ0KICAgICAgICAgICAgIFRMViBDb2RlIFBvaW50Lg0KDQogICAgICAgICAwIC0gVGhl
IFRMViBpcyB3aXRoZHJhd2luZyB0aGUgY2FwYWJpbGl0eSBzcGVjaWZpZWQgYnkgdGhlDQogICAg
ICAgICAgICAgVExWIENvZGUgUG9pbnQuDQoNCiANCg0KDQpTaXZhYmFsYW4gJiBCb3V0cm9zICAg
IEV4cGlyZXMgRGVjZW1iZXIgMTIsIDIwMTcgICAgICAgICAgICAgICBbUGFnZSAxMl0NCgwNCklO
VEVSTkVUIERSQUZUICAgICAgICAgICAgICAgICAgUDJNUCBQVyAgICAgICAgICAgICAgICAgICAg
SnVuZSAxMCwgMjAxNw0KDQoNCiAgICogTGVuZ3RoOg0KDQogICAgIE1VU1QgYmUgc2V0IHRvIDIg
KG9jdGV0KS4NCg0KDQo0LiBQMk1QIFBXIFN0YXR1cyANCg0KICAgSW4gb3JkZXIgdG8gc3VwcG9y
dCB0aGUgcHJvcG9zZWQgbWVjaGFuaXNtLCBhbiBMU1IgTVVTVCBiZSBjYXBhYmxlIG9mDQogICBo
YW5kbGluZyBQVyBzdGF0dXMuIEFzIHN1Y2gsIFBXIHN0YXR1cyBuZWdvdGlhdGlvbiBwcm9jZWR1
cmUNCiAgIGRlc2NyaWJlZCBpbiBbUkZDNDQ0N2Jpc10gaXMgbm90IGFwcGxpY2FibGUgdG8gUDJN
UCBQVy4gQW4gTFNSIE1VU1QNCiAgIE5PVCBjbGFpbSB0byBiZSAgUDJNUCBQVyBjYXBhYmxlIGJ5
IHNlbmRpbmcgYSBMRFAgUDJNUCBQVyBDYXBhYmlsaXR5DQogICBUTFYgIGlmIGl0IGlzIG5vdCBh
bHNvIGNhcGFibGUgb2YgaGFuZGxpbmcgUFcgc3RhdHVzLg0KDQogICBPbmNlIGFuIEwtUEUgc3Vj
Y2Vzc2Z1bGx5IHByb2Nlc3NlcyBhIExhYmVsIE1hcHBpbmcgTWVzc2FnZSBmb3IgYQ0KICAgUDJN
UCBQVywgaXQgTVVTVCBzZW5kIGFwcHJvcHJpYXRlIFBXIHN0YXR1cyBhY2NvcmRpbmcgdG8gdGhl
DQogICBwcm9jZWR1cmUgc3BlY2lmaWVkIFtSRkM0NDQ3YmlzXSB0byByZXBvcnQgdGhlIFBXIHN0
YXR1cy4gSWYgbm8gUFcNCiAgIHN0YXR1cyBub3RpZmljYXRpb24gaXMgcmVxdWlyZWQsIHRoZW4g
bm8gUFcgc3RhdHVzIG5vdGlmaWNhdGlvbiBpcw0KICAgc2VudCAoZm9yIGV4YW1wbGUgaWYgdGhl
IFAyTVAgUFcgaXMgZXN0YWJsaXNoZWQgYW5kIG9wZXJhdGlvbmFsIHdpdGgNCiAgIGEgc3RhdHVz
IGNvZGUgb2YgU3VjY2VzcyAoMHgwMDAwMDAwMCksIGEgUFcgc3RhdHVzIG1lc3NhZ2UgaXMgbm90
DQogICBuZWNlc3NhcnkpLiBBIFBXIHN0YXR1cyBtZXNzYWdlIHNlbnQgZnJvbSBhbiBMLVBFIHRv
IFItUEUgTVVTVA0KICAgY29udGFpbiB0aGUgUDJQIFBXIERvd25zdHJlYW0gRkVDIHRvIGlkZW50
aWZ5IHRoZSBQVy4NCg0KICAgQW4gUi1QRSBhbHNvIHNlbmRzIFBXIHN0YXR1cyB0byBMLVBFKHMp
IHRvIHJlZmxlY3QgaXRzIHZpZXcgb2YgYSBQMk1QDQogICBQVyBzdGF0ZS4gU3VjaCBQVyBzdGF0
dXMgbWVzc2FnZSBjb250YWlucyBQMk1QIFBXIFVwc3RyZWFtIEZFQyB0bw0KICAgaWRlbnRpZnkg
dGhlIFBXLg0KDQogICBDb25uZWN0aXZpdHkgc3RhdHVzIG9mIHRoZSB1bmRlcmx5aW5nIFAyTVAg
TFNQIHRoYXQgUDJNUCBQVyBpcw0KICAgYXNzb2NpYXRlZCB3aXRoLCBjYW4gYmUgdmVyaWZpZWQg
dXNpbmcgTFNQIFBpbmcgYW5kIFRyYWNlcm91dGUNCiAgIHByb2NlZHVyZXMgZGVzY3JpYmVkIGlu
IFtSRkM2NDI1XS4NCg0KNSBTZWN1cml0eSBDb25zaWRlcmF0aW9ucw0KDQogICBUaGUgc2VjdXJp
dHkgbWVhc3VyZXMgZGVzY3JpYmVkIGluIFtSRkM0NDQ3YmlzXSBhcmUgYWRlcXVhdGUgZm9yIHRo
ZQ0KICAgcHJvcG9zZWQgbWVjaGFuaXNtLg0KDQo2IEFja25vd2xlZGdtZW50DQoNCiAgIEF1dGhv
cnMgd291bGQgbGlrZSB0aGFuayBBbmRyZSBQZWxsZXRpZXIgYW5kIFBhcmFnIEphaW4gZm9yIHRo
ZWlyDQogICB2YWx1YWJsZSBzdWdnZXN0aW9ucy4NCg0KNyAgSUFOQSBDb25zaWRlcmF0aW9ucw0K
DQo3LjEuIEZFQyBUeXBlIE5hbWUgU3BhY2UNCg0KICAgVGhpcyBkb2N1bWVudCB1c2VzIHR3byBu
ZXcgRkVDIGVsZW1lbnQgdHlwZXMsIG51bWJlciAweDgyIGFuZCAweDgzDQogICBhcmUgc3VnZ2Vz
dGVkIGZvciBhc3NpZ25tZW50IGZyb20gdGhlIHJlZ2lzdHJ5ICJGRUMgVHlwZSBOYW1lIFNwYWNl
Ig0KICAgZm9yIHRoZSBMYWJlbCBEaXN0cmlidXRpb24gUHJvdG9jb2wgKExEUCBSRkM1MDM2KToN
Cg0KIA0KDQoNClNpdmFiYWxhbiAmIEJvdXRyb3MgICAgRXhwaXJlcyBEZWNlbWJlciAxMiwgMjAx
NyAgICAgICAgICAgICAgIFtQYWdlIDEzXQ0KDA0KSU5URVJORVQgRFJBRlQgICAgICAgICAgICAg
ICAgICBQMk1QIFBXICAgICAgICAgICAgICAgICAgICBKdW5lIDEwLCAyMDE3DQoNCg0KICAgICAg
VmFsdWUgICAgSGV4ICAgIE5hbWUgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgUmVmZXJl
bmNlDQogICAgICAtLS0tLS0tICAtLS0tLSAgLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0g
ICAgICAtLS0tLS0tLS0NCiAgICAgICAxMzAgICAgIDB4ODIgICBQMk1QIFBXIFVwc3RyZWFtIEZF
QyBFbGVtZW50ICAgICAgIFJGQ3h4eHgNCiAgICAgICAxMzEgICAgIDB4ODMgICBQMlAgUFcgRG93
bnN0cmVhbSBGRUMgRWxlbWVudCAgICAgIFJGQ3h4eHgNCg0KNy4yLiBMRFAgVExWIFR5cGUNCg0K
ICAgVGhpcyBkb2N1bWVudCB1c2VzIGEgbmV3IExEUCBUTFYgdHlwZXMsIElBTkEgYWxyZWFkeSBt
YWludGFpbnMgYQ0KICAgcmVnaXN0cnkgb2YgbmFtZSAiVExWIFRZUEUgTkFNRSBTUEFDRSIgZGVm
aW5lZCBieSBSRkM1MDM2LiBUaGUNCiAgIGZvbGxvd2luZyB2YWx1ZXMgYXJlIHN1Z2dlc3RlZCBm
b3IgYXNzaWdubWVudDoNCg0KICAgICAgICAgVExWIHR5cGUgIERlc2NyaXB0aW9uOg0KDQogICAg
ICAgICAweDA3MDMgICBQMk1QIFBXIENhcGFiaWxpdHkgVExWDQoNCjcuMy4gbUxEUCBPcGFxdWUg
VmFsdWUgRWxlbWVudCBUTFYgVHlwZQ0KDQogICBUaGlzIGRvY3VtZW50IHJlcXVpcmVzIGFsbG9j
YXRpb24gb2YgYSBuZXcgbUxEUCBPcGFxdWUgVmFsdWUgRWxlbWVudA0KICAgVHlwZSBmcm9tICJM
RFAgTVAgT3BhcXVlIFZhbHVlIEVsZW1lbnQgYmFzaWMgdHlwZSIgbmFtZSBzcGFjZSBkZWZpbmVk
DQogICBpbiBbUkZDNjM4OF0uDQoNCiAgIFRoZSBmb2xsb3dpbmcgdmFsdWUgaXMgc3VnZ2VzdGVk
IGZvciBhc3NpZ25tZW50Og0KDQogICAgICAgICBUTFYgdHlwZSAgRGVzY3JpcHRpb24NCiAgICAg
ICAgIDB4MyAgICAgICBMMlZQTi1NQ0FTVCBhcHBsaWNhdGlvbiBUTFYNCg0KNy40LiBTZWxlY3Rp
dmUgVHJlZSBJbnRlcmZhY2UgUGFyYW1ldGVyIHN1Yi1UTFYgVHlwZQ0KDQogICBUaGlzIGRvY3Vt
ZW50IHJlcXVpcmVzIGFsbG9jYXRpb24gb2YgYSBzdWItVExWIGZyb20gdGhlIHJlZ2lzdHJ5DQog
ICAiUHNldWRvd2lyZSBJbnRlcmZhY2UgUGFyYW1ldGVycyBTdWItVExWIFR5cGUiIGRlZmluZWQg
aW4gW1JGQzQ0NDZdLg0KDQoNCiAgIFRoZSBmb2xsb3dpbmcgdmFsdWUgaXMgc3VnZ2VzdGVkIGZv
ciBhc3NpZ25tZW50Og0KDQogICAgICAgICBUTFYgdHlwZSAgRGVzY3JpcHRpb24NCiAgICAgICAg
IDB4MWIgICAgICBTZWxlY3RpdmUgVHJlZSBJbnRlcmZhY2UgUGFyYW1ldGVyLg0KDQo3LjUuIFdp
bGRDYXJkIFBNU0kgdHVubmVsIHR5cGUNCg0KICAgVGhpcyBkb2N1bWVudCByZXF1ZXN0cyB0aGF0
IElBTkEgbW9kaWZ5IHRoZSBmb2xsb3dpbmcgZW50cnkgaW4gdGhlDQogICAiUC1NdWx0aWNhc3Qg
U2VydmljZSBJbnRlcmZhY2UgVHVubmVsIChQTVNJIFR1bm5lbCkgVHVubmVsIFR5cGVzIg0KICAg
cmVnaXN0cnkgIHdpdGhpbiB0aGUgIkJvcmRlciBHYXRld2F5IFByb3RvY29sIChCR1ApIFBhcmFt
ZXRlcnMiDQogICBuYW1lc3BhY2UgcHJldmlvdXNseSBhc3NpZ25lZCBieSBSRkM3Mzg1IGFzICJy
ZXNlcnZlZCIuDQoNCiAgICAgVmFsdWUgICAgIE1lYW5pbmcgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIFJlZmVyZW5jZSANCiAgICAgMHhGRiAgICAgIHdpbGRjYXJkIHRyYW5zcG9ydCB0
dW5uZWwgdHlwZSAgICAgICAgIFtUaGlzIGRvY3VtZW50XQ0KDQoNCiANCg0KDQpTaXZhYmFsYW4g
JiBCb3V0cm9zICAgIEV4cGlyZXMgRGVjZW1iZXIgMTIsIDIwMTcgICAgICAgICAgICAgICBbUGFn
ZSAxNF0NCgwNCklOVEVSTkVUIERSQUZUICAgICAgICAgICAgICAgICAgUDJNUCBQVyAgICAgICAg
ICAgICAgICAgICAgSnVuZSAxMCwgMjAxNw0KDQoNCjggIFJlZmVyZW5jZXMNCg0KOC4xLiBOb3Jt
YXRpdmUgUmVmZXJlbmNlcw0KDQogICBbUkZDMjExOV0gIEJyYWRuZXIuIFMsICJLZXkgd29yZHMg
Zm9yIHVzZSBpbiBSRkNzIHRvIEluZGljYXRlDQogICBSZXF1aXJlbWVudCBMZXZlbHMiLCBSRkMg
MjExOSwgTWFyY2gsIDE5OTcuDQoNCiAgIFtSRkM0NDQ3YmlzXSAiUHNldWRvd2lyZSBTZXR1cCBh
bmQgTWFpbnRlbmFuY2UgdXNpbmcgdGhlIExhYmVsDQogICBEaXN0cmlidXRpb24gUHJvdG9jb2wi
LCBNYXJ0aW5pLCBMLiwgZXQgYWwuLCBkcmFmdC1pZXRmLXBhbHMtDQogICByZmM0NDQ3YmlzLTA1
LnR4dCwgSnVseSAyMDE2Lg0KDQogICBbUkZDNTAzNl0gIEFuZGVyc3NvbiwgTC4sIE1pbmVpLCBJ
LiwgYW5kIEIuIFRob21hcywgIkxEUA0KICAgU3BlY2lmaWNhdGlvbiIsIFJGQyA1MDM2LCBPY3Rv
YmVyIDIwMDcuDQoNCiAgIFtSRkM1MDAzXSBDLiBNZXR6LCBMLiBNYXJ0aW5pLCBGLiBCYWx1cywg
Si4gU3VnaW1vdG8sICJBdHRhY2htZW50DQogICBJbmRpdmlkdWFsIElkZW50aWZpZXIgKEFJSSkg
VHlwZXMgZm9yIEFnZ3JlZ2F0aW9uIiwgUkZDNTAwMywNCiAgIFNlcHRlbWJlciAyMDA3Lg0KDQog
ICBbUkZDNTMzMV0gUi4gQWdnYXJ3YWwsIFkuIFJla2h0ZXIsIEUuIFJvc2VuLCAiTVBMUyBVcHN0
cmVhbSBMYWJlbA0KICAgQXNzaWdubWVudCBhbmQgQ29udGV4dC1TcGVjaWZpYyBMYWJlbCBTcGFj
ZSIsIFJGQyA1MzMxLCBBdWd1c3QgMjAwOC4NCg0KICAgW1JGQzUzMzJdIFQuIEVja2VydCwgRS4g
Um9zZW4sIEVkLixSLiBBZ2dhcndhbCwgWS4gUmVraHRlciwgIk1QTFMNCiAgIE11bHRpY2FzdCBF
bmNhcHN1bGF0aW9ucyIsIFJGQyA1MzMyLCBBdWd1c3QgMjAwOC4NCg0KICAgW1JGQzYzODhdIEku
IE1pbmVpLCBLLiBLb21wZWxsYSwgSS4gV2lqbmFuZHMsIEIuIFRob21hcywgIkxhYmVsDQogICBE
aXN0cmlidXRpb24gUHJvdG9jb2wgRXh0ZW5zaW9ucyBmb3IgUG9pbnQtdG8tTXVsdGlwb2ludCBh
bmQNCiAgIE11bHRpcG9pbnQtdG8tTXVsdGlwb2ludCBMYWJlbCBTd2l0Y2hlZCBQYXRocyIsIFJG
QyA2Mzg4LCBOb3ZlbWJlcg0KICAgMjAxMS4NCg0KICAgW1JGQzQ4NzVdIFIuIEFnZ2Fyd2FsLCBF
ZC4sIEQuIFBhcGFkaW1pdHJpb3UsIEVkLiwgUy4gWWFzdWthd2EsIEVkLiwNCiAgICJFeHRlbnNp
b25zIHRvIFJlc291cmNlIFJlc2VydmF0aW9uIFByb3RvY29sIC0gVHJhZmZpYyBFbmdpbmVlcmlu
Zw0KICAgKFJTVlAtVEUpIGZvciBQb2ludC10by1NdWx0aXBvaW50IFRFIExhYmVsIFN3aXRjaGVk
IFBhdGhzIChMU1BzKS4iLA0KICAgUkZDIDQ4NzUsIE1heSAyMDA3Lg0KDQogICBbUkZDNjUxNF0g
Ui4gQWdnYXJ3YWwsIEUuIFJvc2VuLCBULiBNb3JpbiwgWS4gUmVraHRlciwgIkJHUCBFbmNvZGlu
Z3MNCiAgIGFuZCBQcm9jZWR1cmVzIGZvciBNdWx0aWNhc3QgaW4gTVBMUy9CR1AgSVAgVlBOcyIs
IFJGQzY1MTQsIEZlYnJ1YXJ5DQogICAyMDEyLg0KDQogICBbUkZDNTU2MV0gQi5UaG9tYXMsIEsu
UmF6YSwgUy5BZ2dhcndhbCwgUi5BZ2Fyd2FsLCBKTC4gTGUgUm91eCwgIkxEUA0KICAgQ2FwYWJp
bGl0aWVzIiwgUkZDIDU1NjEsIEp1bHkgMjAwOS4NCg0KICAgW1JGQzU5MThdIFIuIEFzYXRpLCBJ
LiBNaW5laSwgYW5kIEIuIFRob21hcywgIkxEUCBUeXBlZCBXaWxkY2FyZA0KICAgRm9yd2FyZGlu
ZyBFcXVpdmFsZW5jZSBDbGFzcyIsIFJGQyA1OTE4LCBBdWd1c3QgMjAxMC4NCg0KICAgW1JGQzY2
NjddIEsuIFJhemEsIFMuIEJvdXRyb3MsIGFuZCBDLiBQaWduYXRhcm8sICJMRFAgVHlwZWQgV2ls
ZGNhcmQNCiAgIEZFQyBmb3IgUFdpZCBhbmQgR2VuZXJhbGl6ZWQgUFdpZCBGRUMgRWxlbWVudHMi
LCBSRkMgNjY2NywgSnVseSAyMDEyLg0KDQoNCiANCg0KDQpTaXZhYmFsYW4gJiBCb3V0cm9zICAg
IEV4cGlyZXMgRGVjZW1iZXIgMTIsIDIwMTcgICAgICAgICAgICAgICBbUGFnZSAxNV0NCgwNCklO
VEVSTkVUIERSQUZUICAgICAgICAgICAgICAgICAgUDJNUCBQVyAgICAgICAgICAgICAgICAgICAg
SnVuZSAxMCwgMjAxNw0KDQoNCjguMi4gSW5mb3JtYXRpdmUgUmVmZXJlbmNlcw0KDQogICBbUkZD
Mzk4NV0gU3Rld2FydCBCcnlhbnQsIGV0IGFsLiwgIlBXRTMgQXJjaGl0ZWN0dXJlIiwgUkZDMzk4
NQ0KDQogICBbUkZDNjA3NF0gRS4gUm9zZW4sVy4gTHVvLEIuIERhdmllLFYuIFJhZG9hY2EgIlBy
b3Zpc2lvbmluZywgQXV0by0NCiAgIERpc2NvdmVyeSwgYW5kIFNpZ25hbGluZyBpbiBMYXllciAy
IFZpcnR1YWwgUHJpdmF0ZSBOZXR3b3Jrcw0KICAgKEwyVlBOcykiLCBSRkM2MDc0LCBKYW51YXJ5
IDIwMTEuDQoNCiAgIFtSRkM3MzM4XSAgIEYuIEpvdW5heSwgZXQuIGFsLCAiUmVxdWlyZW1lbnRz
IGZvciBQb2ludCB0byBNdWx0aXBvaW50DQogICBQc2V1ZG93aXJlIiwgUkZDNzMzOCwgU2VwdGVt
YmVyIDIwMTQuDQoNCiAgIFtSRkM2NDI1XSBBLiBGYXJyZWwsIFMuIFlhc3VrYXdhLCAiRGV0ZWN0
aW5nIERhdGEgUGxhbmUgRmFpbHVyZXMgaW4NCiAgIFBvaW50LXRvLU11bHRpcG9pbnQgTXVsdGlw
cm90b2NvbCBMYWJlbCBTd2l0Y2hpbmcgKE1QTFMpLSBFeHRlbnNpb25zDQogICB0byBMU1AgUGlu
ZyIsIFJGQzY0MjUsIE5vdmVtYmVyIDIwMTEuDQoNCg0KQ29udHJpYnV0b3JzDQoNCg0KICAgICAg
VGhlIGZvbGxvd2luZyBjby1hdXRob3JzIGhhdmUgYWxzbyBjb250cmlidXRlZCB0byB0aGlzIGRv
Y3VtZW50Og0KDQogICAgICBMdWNhIE1hcnRpbmkNCiAgICAgIENpc2NvIFN5c3RlbXMsIEluYy4N
CiAgICAgIEVtYWlsOiBsbWFydGluaUBjaXNjby5jb20NCg0KICAgICAgTWFjaWVrIEtvbnN0YW50
eW5vd2ljeg0KICAgICAgQ2lzY28gU3lzdGVtcywgSW5jLg0KICAgICAgZS1tYWlsOiBtYWNpZWtA
Y2lzY28uY29tDQoNCiAgICAgIEdpYW5uaSBEZWwgVmVjY2hpbw0KICAgICAgU3dpc3Njb20gDQog
ICAgICBFbWFpbDogR2lhbm5pLkRlbFZlY2NoaW9Ac3dpc3Njb20uY29tDQoNCiAgICAgIFRob21h
cyBELiBOYWRlYXUNCiAgICAgIEJyb2NhZGUNCiAgICAgIEVtYWlsOiB0bmFkZWF1QGx1Y2lkdmlz
aW9uLmNvbQ0KDQogICAgICBGcmVkZXJpYyBKb3VuYXkNCiAgICAgIE9yYW5nZSBDSA0KICAgICAg
RW1haWw6IEZyZWRlcmljLkpvdW5heUBzYWx0LmNoDQoNCiAgICAgIFBoaWxpcHBlIE5pZ2VyDQog
ICAgICBPcmFuZ2UgQ0gNCiAgICAgIEVtYWlsOiBwaGlsaXBwZS5uaWdlckBvcmFuZ2UuY29tDQoN
CiAgICAgIFl1amkgS2FtaXRlDQogICAgICBOVFQgQ29tbXVuaWNhdGlvbnMgQ29ycG9yYXRpb24N
CiAgICAgIEVtYWlsOiB5LmthbWl0ZUBudHQuY29tDQogDQoNCg0KU2l2YWJhbGFuICYgQm91dHJv
cyAgICBFeHBpcmVzIERlY2VtYmVyIDEyLCAyMDE3ICAgICAgICAgICAgICAgW1BhZ2UgMTZdDQoM
DQpJTlRFUk5FVCBEUkFGVCAgICAgICAgICAgICAgICAgIFAyTVAgUFcgICAgICAgICAgICAgICAg
ICAgIEp1bmUgMTAsIDIwMTcNCg0KDQogICAgICBMaXpob25nIEppbg0KICAgICAgRW1haWw6IGxp
emhvLmppbkBnbWFpbC5jb20NCg0KICAgICAgTWFydGluIFZpZ291cmV1eA0KICAgICAgTm9raWEN
CiAgICAgIEVtYWlsOiBtYXJ0aW4udmlnb3VyZXV4QG5va2lhLmNvbQ0KDQogICAgICBMYXVyZW50
IENpYXZhZ2xpYQ0KICAgICAgTm9raWENCiAgICAgIEVtYWlsOiBsYXVyZW50LmNpYXZhZ2xpYUBu
b2tpYS5jb20NCg0KDQogICAgICBTaW1vbiBEZWxvcmQNCiAgICAgIFRlbHN0cmENCiAgICAgIEUt
bWFpbDogc2ltb24uZGVsb3JkQGdtYWlsLmNvbQ0KDQogICAgICBLYW1yYW4gUmF6YQ0KICAgICAg
Q2lzY28gU3lzdGVtcw0KICAgICAgRW1haWw6IHNrcmF6YUBjaXNjby5jb20NCg0KQXV0aG9ycycg
QWRkcmVzc2VzDQoNCg0KICAgICAgU2FtaSBCb3V0cm9zDQogICAgICBWTXdhcmUgSW5jLg0KICAg
ICAgRW1haWw6IHNib3V0cm9zQHZtd2FyZS5jb20NCg0KICAgICAgU2l2YSBTaXZhYmFsYW4NCiAg
ICAgIENpc2NvIFN5c3RlbXMsIEluYy4NCiAgICAgIEVtYWlsOiBtc2l2YUBjaXNjby5jb20NCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNClNpdmFiYWxhbiAmIEJvdXRy
b3MgICAgRXhwaXJlcyBEZWNlbWJlciAxMiwgMjAxNyAgICAgICAgICAgICAgIFtQYWdlIDE3XQ0K

--_002_4E9FB8C02CC148C9994FBDE741BDD52Cvmwarecom_--


From nobody Sat Jun 10 10:26:28 2017
Return-Path: <lucienav@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 77650127076 for <ietf@ietfa.amsl.com>; Sat, 10 Jun 2017 10:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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 nJoNT6UKZx7J for <ietf@ietfa.amsl.com>; Sat, 10 Jun 2017 10:26:10 -0700 (PDT)
Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com [IPv6:2607:f8b0:400e:c05::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CC67127ABE for <ietf@ietf.org>; Sat, 10 Jun 2017 10:26:07 -0700 (PDT)
Received: by mail-pg0-x235.google.com with SMTP id k71so34574644pgd.2 for <ietf@ietf.org>; Sat, 10 Jun 2017 10:26:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZtGTPVNvFOUzYfWK8go3UQ72lUnqON4f8m60bYv6k4I=; b=BJ11Os8/GrHAUniJQNH47dCojHjE5bSsQEXCXNMhHIvuuHmbtmyuDMPdAW6SbYEXE4 VQveikwBtiMZRA3t459N5STf8sdLALORzhQvwqso5l4pTQgvduGCjiX/hdDpR+TIYYyy m9qWy/zxDcdadmcqxVe+0p1QeMqCe4B6wO5N3HfR0ZkGXuowxeKk9bvay1LswKO+H/hg eFa1chKPxNI3NtpHlvCaikWREe22eGmRCYQxrdkZfVH/PF4+xzAaKLymbFJZryZNtNho hPd4cKxX1cymUqV4as4cvyS0a5+GdQwMZjuSwzBl8obpn3eJPi+JtelcotByaaNvYjAw XfYg==
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=ZtGTPVNvFOUzYfWK8go3UQ72lUnqON4f8m60bYv6k4I=; b=K3oZxjl0oqinHek/g/pQC1D5XnxR/fEmlBGuMnBs3CZsYrmLJNSuU020al7XxSqzht TIarYc7kklmSnScDYy68QFF4Q3hvI5HtIRm3cXvNLGgeMzImtq5ZCrwhWWZJziwou0dv wlYdpCVQcESr5IuyKls0q95DV5pjdPFZcsuUBxL2ylQfSx4x3rlRt3kb8uwVPLMc84TQ zvTvDAr/jmaF4t22vLijvMG/UkvhsKSsLG82k/1CnRwhnxrN/kKq2jF5AL3m1LSg10Io rJv51TO6lSPhUseiN9VnadPye8yN4qvwY9gc7A16cXQgUKOeq70IeP5Sa1YpU4ZSIIfo TKBA==
X-Gm-Message-State: AODbwcDyy8FVbEWoQYuWY5UK5oqBiSlc6Ss4cUwnExvbBnHYrSZEEjoh WvDzkP6ZZn1qwLa7A8QmRA==
X-Received: by 10.98.80.140 with SMTP id g12mr17181420pfj.146.1497115566443; Sat, 10 Jun 2017 10:26:06 -0700 (PDT)
Received: from [10.0.1.76] (c-98-248-223-72.hsd1.ca.comcast.net. [98.248.223.72]) by smtp.gmail.com with ESMTPSA id k15sm4542588pfb.1.2017.06.10.10.26.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 10 Jun 2017 10:26:05 -0700 (PDT)
Content-Type: multipart/alternative; boundary=Apple-Mail-07F97384-E491-4FE1-AD34-2328613D6C54
Mime-Version: 1.0 (1.0)
Subject: Re: Genart last call review of draft-ietf-bmwg-dcbench-methodology-07
From: Lucien Avramov <lucienav@google.com>
X-Mailer: iPhone Mail (14E304)
In-Reply-To: <CAFgnS4Vstv9zyg9rE4-K-q-6GH-P6noXCmoOLvdjTY+dU_uRHw@mail.gmail.com>
Date: Sat, 10 Jun 2017 10:26:04 -0700
Cc: gen-art <gen-art@ietf.org>, draft-ietf-bmwg-dcbench-methodology.all@ietf.org, ietf <ietf@ietf.org>, bmwg@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <AC86F980-D9C1-4DE1-8296-70DB2A6482F9@google.com>
References: <149692498024.25760.14056448148418579949@ietfa.amsl.com> <CALTEt=DUhEVgSvYN+2XYUR8Ddq5n8HJtZW2RNj3DV3rSgH0YKQ@mail.gmail.com> <CAFgnS4Vstv9zyg9rE4-K-q-6GH-P6noXCmoOLvdjTY+dU_uRHw@mail.gmail.com>
To: Dan Romascanu <dromasca@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yDU6sz9VOgBkee3KV7bRyDKQ5fI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jun 2017 17:26:12 -0000

--Apple-Mail-07F97384-E491-4FE1-AD34-2328613D6C54
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Thank you Dan, much appreciative of your feedback.

Lucien

> On Jun 10, 2017, at 08:27, Dan Romascanu <dromasca@gmail.com> wrote:
>=20
> Hi,
>=20
> All answers are acceptable. Thanks for addressing my comments.=20
>=20
> Regards,
>=20
> Dan
>=20
>=20
>> On Fri, Jun 9, 2017 at 8:11 AM, Lucien Avramov <lucienav@google.com> wrot=
e:
>> Hi Dan,=20
>>=20
>> Thank you very much for the comments. I addressed them and published vers=
ion -09.=20
>>=20
>> Inline are some the comments / answer to your feedback. The parts without=
 answers mean they have been addressed.=20
>>=20
>> Again, thank you for spending the time to read this in this fine detail.=20=

>>=20
>> Lucien
>>=20
>>=20
>>=20
>>> On Thu, Jun 8, 2017 at 5:29 AM, Dan Romascanu <dromasca@gmail.com> wrote=
:
>>> Reviewer: Dan Romascanu
>>> Review result: Ready with Issues
>>>=20
>>> I am the assigned Gen-ART reviewer for this draft. The General Area
>>> Review Team (Gen-ART) reviews all IETF documents being processed
>>> by the IESG for the IETF Chair.  Please treat these comments just
>>> like any other last call comments.
>>>=20
>>> For more information, please see the FAQ at
>>>=20
>>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>>=20
>>> Document: draft-ietf-bmwg-dcbench-methodology-??
>>> Reviewer: Dan Romascanu
>>> Review Date: 2017-06-08
>>> IETF LC End Date: 2017-06-13
>>> IESG Telechat date: Not scheduled for a telechat
>>>=20
>>> Summary:
>>>=20
>>> This Informational I-D describes test and evaluation methodology and
>>> measurement techniques for physical network equipment in the data center=
. It's
>>> an useful and clearly written document and it is ready for publication, a=
fter a
>>> number of minor issues and nits will be addressed.
>>>=20
>>> Major issues:
>>>=20
>>> Minor issues:
>>>=20
>>> 1. There is one single mention of the scope being benchmarking of 'physi=
cal
>>> network equipment in the data center'. I assume this is written as oppos=
ed to
>>> virtual networking equipment. This is not included in the title or repea=
ted any
>>> place else. I suggest to make more clear the scope by mentioning 'physic=
al
>>> equipment' at least once more, for example in the Introduction section.
>>>=20
>>> 2. Section 1.2: I am a little concerned about adding additional interpre=
tations
>>> to the keywords in RFC2119.
>>>=20
>>> Especially about:
>>>=20
>>> 'MAY: Comprehensive metric for the scenario described'
>>=20
>> Thank you, MAY provides an optional metric, I have addressed your comment=
=20
>>>=20
>>> MAY has a different meaning in 2119, and the fact that a metric is
>>> 'comprehensive' (whatever this means) seems to me orthogonal to the 2119=

>>> semantics. The proposed interpretation makes little sense to me, if
>>> 'comprehensive' than why not required? or at least as a 'should'?
>>>=20
>>> 3. Section 6.2: 'The intensity of a microburst MAY be varied ...' It wou=
ld be
>>> useful to make clear what is meant by 'intensity'.
>>=20
>> The intensity of a microburst is defined in the definitions document [1] s=
o i referenced it that way
>> =20
>>>=20
>>> Nits/editorial comments:
>>>=20
>>> 1. The different formatting of the references [1], [2], etc. vs. [RFC211=
9],
>>> etc. is slightly confusing. Unless there is some good reason I suggest t=
o fix
>>> this. Also use of references is inconsistent through the text, sometimes=
 they
>>> are mentioned, sometimes they are not.
>>=20
>> Fixed it for [2] and [3], however kept [1] as [1], as this document is no=
t an RFC yet.
>> =20
>>>=20
>>> 2. Section 2.2: 'Alternatively when a traffic generator CAN NOT be conne=
cted '
>>> - this capitalization is not conformant to RFC2119.
>>>=20
>>> 3. 'vlan ZZZ' is not consistent with 'vlan X' and 'vlan Y' previously us=
ed.
>>>=20
>>> 4. Missing reference - RFC 6985
>>>=20
>>> 5. Missing expansion and references for DSCP and COS
>>>=20
>>> 6. Sections 3.3 and 6.3: s/number of iteration/number of iterations/
>>>=20
>>> 7. The methodology (e.g. in section 5) makes an assumption that the DUT h=
as at
>>> least nine ports. This may be trivial in a DC, but it's worth being ment=
ioned
>>>=20
>>=20
>> Thanks added this in section 2.3 as it was making more sense to be clarif=
ied there=20
>>=20
>=20

--Apple-Mail-07F97384-E491-4FE1-AD34-2328613D6C54
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>Thank you Dan, much appreciative of yo=
ur feedback.</div><div id=3D"AppleMailSignature"><br>Lucien</div><div><br>On=
 Jun 10, 2017, at 08:27, Dan Romascanu &lt;<a href=3D"mailto:dromasca@gmail.=
com">dromasca@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite=
"><div><div dir=3D"ltr"><div><div><div>Hi,<br><br></div>All answers are acce=
ptable. Thanks for addressing my comments. <br><br></div>Regards,<br><br></d=
iv>Dan<br><br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote=
">On Fri, Jun 9, 2017 at 8:11 AM, Lucien Avramov <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:lucienav@google.com" target=3D"_blank">lucienav@google.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">Hi Dan,&=
nbsp;<div><br></div><div>Thank you very much for the comments. I addressed t=
hem and published version -09.&nbsp;</div><div><br></div><div>Inline are som=
e the comments / answer to your feedback. The parts without answers mean the=
y have been addressed.&nbsp;</div><div><br></div><div>Again, thank you for s=
pending the time to read this in this fine detail.&nbsp;</div><div><br></div=
><div>Lucien</div><div><br></div><div><br></div><div class=3D"gmail_extra"><=
br><div class=3D"gmail_quote"><div><div class=3D"h5">On Thu, Jun 8, 2017 at 5=
:29 AM, Dan Romascanu <span dir=3D"ltr">&lt;<a href=3D"mailto:dromasca@gmail=
.com" target=3D"_blank">dromasca@gmail.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex">Reviewer: Dan Romascanu<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.&nbsp; 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"norefer=
rer" target=3D"_blank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq</a=
>&gt;.<br>
<br>
Document: draft-ietf-bmwg-dcbench-method<wbr>ology-??<br>
Reviewer: Dan Romascanu<br>
Review Date: 2017-06-08<br>
IETF LC End Date: 2017-06-13<br>
IESG Telechat date: Not scheduled for a telechat<br>
<br>
Summary:<br>
<br>
This Informational I-D describes test and evaluation methodology and<br>
measurement techniques for physical network equipment in the data center. It=
's<br>
an useful and clearly written document and it is ready for publication, afte=
r a<br>
number of minor issues and nits will be addressed.<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
1. There is one single mention of the scope being benchmarking of 'physical<=
br>
network equipment in the data center'. I assume this is written as opposed t=
o<br>
virtual networking equipment. This is not included in the title or repeated a=
ny<br>
place else. I suggest to make more clear the scope by mentioning 'physical<b=
r>
equipment' at least once more, for example in the Introduction section.<br>
<br>
2. Section 1.2: I am a little concerned about adding additional interpretati=
ons<br>
to the keywords in RFC2119.<br>
<br>
Especially about:<br>
<br>
'MAY: Comprehensive metric for the scenario described'<br></blockquote><div>=
<br></div></div></div><div><b><span style=3D"font-size:12.8px">Thank you, MA=
Y provides an optional metric, I have addressed your comment</span>&nbsp;</b=
></div><span class=3D""><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">
<br>
MAY has a different meaning in 2119, and the fact that a metric is<br>
'comprehensive' (whatever this means) seems to me orthogonal to the 2119<br>=

semantics. The proposed interpretation makes little sense to me, if<br>
'comprehensive' than why not required? or at least as a 'should'?<br>
<br>
3. Section 6.2: 'The intensity of a microburst MAY be varied ...' It would b=
e<br>
useful to make clear what is meant by 'intensity'.<br></blockquote><div><br>=
</div></span><div><div style=3D"font-size:12.8px">The intensity of a microbu=
rst is defined in the definitions document [1] so i referenced it that way</=
div></div><span class=3D""><div>&nbsp;</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">
<br>
Nits/editorial comments:<br>
<br>
1. The different formatting of the references [1], [2], etc. vs. [RFC2119],<=
br>
etc. is slightly confusing. Unless there is some good reason I suggest to fi=
x<br>
this. Also use of references is inconsistent through the text, sometimes the=
y<br>
are mentioned, sometimes they are not.<br></blockquote><div><br></div></span=
><div>Fixed it for [2] and [3], however kept [1] as [1], as this document is=
 not an RFC yet.</div><span class=3D""><div>&nbsp;</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">
<br>
2. Section 2.2: 'Alternatively when a traffic generator CAN NOT be connected=
 '<br>
- this capitalization is not conformant to RFC2119.<br>
<br>
3. 'vlan ZZZ' is not consistent with 'vlan X' and 'vlan Y' previously used.<=
br>
<br>
4. Missing reference - RFC 6985<br>
<br>
5. Missing expansion and references for DSCP and COS<br>
<br>
6. Sections 3.3 and 6.3: s/number of iteration/number of iterations/<br>
<br>
7. The methodology (e.g. in section 5) makes an assumption that the DUT has a=
t<br>
least nine ports. This may be trivial in a DC, but it's worth being mentione=
d<br>
<br></blockquote></span><div><span style=3D"font-size:12.8px">Thanks added t=
his in section 2.3 as it was making more sense to be clarified there</span>&=
nbsp;</div></div><br></div></div>
</blockquote></div><br></div>
</div></blockquote></body></html>=

--Apple-Mail-07F97384-E491-4FE1-AD34-2328613D6C54--


From nobody Sat Jun 10 13:43:28 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3727129431 for <ietf@ietfa.amsl.com>; Sat, 10 Jun 2017 13:43:26 -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_H4=-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=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uX72nh1kwaXr for <ietf@ietfa.amsl.com>; Sat, 10 Jun 2017 13:43:21 -0700 (PDT)
Received: from EUR03-DB5-obe.outbound.protection.outlook.com (mail-eopbgr40113.outbound.protection.outlook.com [40.107.4.113]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A02A126D85 for <ietf@ietf.org>; Sat, 10 Jun 2017 13:43:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=MuCXv9w1EsYulCZbck+970YTsYcgHRbU11U3LG/7vQA=; b=YB5kzuzlNaLi1W7jqZ/3HjGWjYmd5Rqb8Wc/W0odcQ9X565FrreMPk8RgeToNgSbTDzll7Wm7R84u7BVoF/2zTCOMlwOxPVwrLevDdQbNfS17wf0miAd9DvOiESW/HnHF1ITfVc/3nevwN0rk4aHmmAJ6Sx0a7YfbgmLLkDHSG4=
Authentication-Results: taugh.com; dkim=none (message not signed) header.d=none;taugh.com; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.169.157.161) by HE1PR07MB1563.eurprd07.prod.outlook.com (2a01:111:e400:7a2d::13) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1157.9; Sat, 10 Jun 2017 20:43:17 +0000
Message-ID: <007c01d2e229$b94662e0$4001a8c0@gateway.2wire.net>
From: "tom p." <daedulus@btconnect.com>
To: "John Levine" <johnl@taugh.com>, <ietf@ietf.org>
References: <20170610002320.10969.qmail@ary.lan>
Subject: Re: Real DMARC damage
Date: Sat, 10 Jun 2017 21:39:49 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.169.157.161]
X-ClientProxiedBy: VI1PR0401CA0013.eurprd04.prod.outlook.com (2603:10a6:800:4a::23) To HE1PR07MB1563.eurprd07.prod.outlook.com (2a01:111:e400:7a2d::13)
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: HE1PR07MB1563:
X-MS-Office365-Filtering-Correlation-Id: d1cf3ab7-d4c3-4460-18f1-08d4b0415325
X-Microsoft-Antispam: UriScan:(66228244568604); BCL:0; PCL:0; RULEID:(22001)(201703131423075)(201703031133081); SRVR:HE1PR07MB1563; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 3:u6/du7nF3GH+fGbviqI5b77djnhA8nEacpk8UCG66iUqAQXu7bD/P1gRTdhRdMdV7yI/DqjDxf6UB1d/iPTC226zpAgzcV04fx5Ab8+GwivV50cxIyUcfQYQfG3LAwAMj1zv5ZwrkFpd5Lt8He7FmqYW0ZK47KYHD+lZQwMVF1cb2zX0sbMe7q+PT5lU7VVYbm4l4JMLISo+i7WC5SNVqlQ07oHysHniCT6qU5HX2YLaDbyRZ88lW6r1R+tcNXkB5/sIa4PeZxcViRYjHJWj0hYtWAnzrqmAQwuVmjs+vQbs6XvR1A64DgSPZ1UWjtW9L1KEvJJi0x1QuDAB6icbT4Q8IIr2BAOszJ43UEVIcltlJ9c6HR6mdMLbOLp6K2Im; 25:e0Sk4EkxUKGs9N9OiNEVMzbGrwp06ovatSJaa29ztXR5vE/4AilVFj3VZ7lgki620KwfD8ktabEE50RJ1+bXaIJ0o/mqldbT2mdAOXKeyaxjj6CWMxu4S4frVa61W13WrXu3fmHssgjwqCRpi/6XdbPJfgiFNfklPX4OJ+qWKd4IZ30Gn1xmpSI7UB8UEgbwJ4USDHk4W3edlgrIPqI5a0FQNAuGNkvjerGspmbO2TMV0VPySokYqHvENwTBvn2xZFHI0cGOTK3GioHGeuDx9JrQmH1EpOPTCD62woOOw9uXWYnjGFWWIqhH9d/Hgzv/8B2s0/RD2Xfsvj9DN4CMbvoEKK2Ftpk5yPaoUomqWoTdvJyy56deQkYDLq6eCaHH2j2aHss8+ztueAO/p/Q2EVIu8t6lE5oET6vsLcfO+T9i1o/S124yNj8R3nRZrOVGrB8WxTZ/j76pfeiVvr6HEktfYC11zPD6B46shpgB0Fw=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 31:BXcZfVH4vNtxaPXwxNflGtrp5Sa8YzAyyx5oKwxCqsIQSx41Omfl+tdSXMWOpd1Zz1HLs9R8V1W4Uxy4jtGyIvLddEqX3510lu2pGtf3Gif1mpLu9H1MrbdWxNynbN/G773m5sNkGksqPlcusC4rydzatL3qlEy7CEtiQeAbkTRF+nZxmis9EBF1qNPVAmm2z0frF58Nbe+16D6NlCHkLX56ZbesSphohd1TGY+Hm4v7XnEK4yFLx428nHNgYEmbIQga2FvBT+oNFrA/hdwUIg==; 20:5NM4aPPDSPlBpkAZCf8GatChpvFfmA1OIjgEmXHnK4Sya0r4ZmMbQ+FiyVJROeYF5kMdUWxOUP8cjComfP3Mi9/0NVc0jD899Sl0wjplj+6nhl4aV6hjkgHIh05UEpLWQfhnOF5rviC4Kwx3HJa3bDJ8L7Es+xWNz/gzw2km0mA=
X-Microsoft-Antispam-PRVS: <HE1PR07MB15635D133BFCE5EF4CE95E8CC6CF0@HE1PR07MB1563.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(36002687640763)(178726229863574)(158342451672863)(66228244568604)(160011542660777)(189930954265078)(265634631926514)(2312100126823)(277809949798613)(211936372134217);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(10201501046)(3002001)(93006095)(93001095)(6041248)(20161123555025)(20161123560025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123564025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:HE1PR07MB1563; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:HE1PR07MB1563; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTYzOzQ6KytYVWFjSVpkdWFIK3RobmtsKzg3OG13S2Va?= =?utf-8?B?TTlGY3pTOWZSK2JscGJ6Q0Ruc3piMnVwR0pzZUNZWFFxVm5ZK1hnbzVoSE90?= =?utf-8?B?U3B5MXNYS2kzdUhNVFJIODZuclpTaUtLdnl6OEhlL2lXSHQ1TEdXNXJXdVFv?= =?utf-8?B?ZHREZVBlOCtHK1cwWDB3WWpLRHJyMENjYXdYTHZiR3UxNGZIMXFySzJSNVNy?= =?utf-8?B?TmJnWVFYTlFWQkM3RFFiVVI3V2NUOVJsUTdBWWUwaGxob1g1cy9JNDZsRkt1?= =?utf-8?B?NWJHa1l4VUhpVE5FS1h6K2cwSzlFQmw2cWZGWnVGUnJVdkZIN3BmZWNYb3A3?= =?utf-8?B?MW40OUFkRHY0SWFQMDBEZ3lreHI2ZTVtWk45VUhBc3BOSHVQdmNTT0I3Sk56?= =?utf-8?B?b0xSZlNJSllrL1grdzVGSUtHOS8zeHNZQVVyWThlQ0hISXRmTzdxSmJYZll1?= =?utf-8?B?OW9iVU5qNXhRZzhnTGxaTUM1RGp3MkVhKzlKRktmaXJXWGVsWEtTc2NBS2NF?= =?utf-8?B?M2FwcTVWZ2MzQ1JBdEJLTjVFeGdYSy9zTHpiWG5lczFBajZqNVVpQ3VPcElq?= =?utf-8?B?RDNGdkNoNzdxalNkSWV3Zy85amRiSnkza2E1SG1LWEcrdmVNQXJRSDBwbGlL?= =?utf-8?B?ekVpajB4SWcyclphc29mYklFRWVpSHA0NDhLbGxxYUF5UVc1SnBBeThxNSsw?= =?utf-8?B?SHZwOExsaEdBOFhxUkZUTHVnOUhnRXMzT3JvOHA1N2NhSzRrMDdUb3piaEkx?= =?utf-8?B?TTZkYnpBdjFzUXkxZHZlRnoyemd2TmNocnczdEJXZWtsTGxhbUl1VW9oUjl4?= =?utf-8?B?TjJDNkFjM3hGQTdETEszRnBOc2lIYkhlZEpWdHJtaUUxOHN5Z1BlWTV6eEVR?= =?utf-8?B?aVZNb1FxelpYblRKWHcvNDBKcm53M0Rnc2syMGFCeXNHZ2VmRDN5dUdtek1x?= =?utf-8?B?a3pydDBNWmVrYzd6N1FCd0ptc0RqOFFMa1ZCN0VUbnROUEJxYVJVRjcvWVB1?= =?utf-8?B?SFFCdDFtMVJFN0ZuMTg2SXFzMWpoMGx6NDdiTEw5Wjd0eDAyak5meEFpY1lJ?= =?utf-8?B?TjN5MThlZU4yZ0hSekh6V0dMMjh2OG56ZG5ERkJRVDF1aTF6eGhDMloxMElj?= =?utf-8?B?SVE4TnBDVVBhSSsvUU1VaE5NZ3BveWlOZUhNY1R1MmNnZ0lKaDByR3NLbmV4?= =?utf-8?B?R21ObjMwcklmQm9kZnNRZVREaSsxUUQ4NFlEbEhxdVZ0MXhqSU5vVTU0cWlQ?= =?utf-8?B?Ung4c2pYN1UzNDFhdFhuQ2ZnYURVSWlvVlkxbXdRVkxDY0JyeUQvOTFYMGdp?= =?utf-8?B?NU94cGNHK1lQNkg5Vy81Q2Z0clBDQXR4SGlMTGtwMjhhSEx1bjVkbmJVNm5o?= =?utf-8?B?M29UbC9Qc3hjN1hCcGUwWUZlK0xqcXRaL1ZqRlVremlTb3hWemo5UXVRVW1j?= =?utf-8?B?c1JrOGFoR2thUHN4ODhVSS9DcDl1MHpXVXp1UEp1S0ZxQmoxdmtxdUQ5akFr?= =?utf-8?B?NlRoM2NYT0JYNHg5UG93dTJOSGp6Qy80VDg4ZDJTbEphaXRSQ2VCRjJjSWgr?= =?utf-8?B?QUFaRnh2VjhzTXhnRmtpdFdNT0xzZlhaQzZaVFlSY2NLNSs2YUkyV3ljWFJz?= =?utf-8?B?L2ZIWklvbzRMVUM1VkIvUEgrL1JjZ1BLV2puMFMxeS9GczZRTnAvRE1xTzQ4?= =?utf-8?B?dndEZHV2T1pTdDd1c2lJK2tMOTlvendydTlwdlBpZE9LaVFVWTAxNE1HbUtY?= =?utf-8?B?NFU3WUd0RUt4b1FqSms3YVkySDhiZ2dVcUhuVkQ3S2Rkc0ZCcytnU1V3c1d5?= =?utf-8?B?OTh4cmtnZUEwbjJoU2hxRm04citzUEtFdE9BR09ENFZyUW9JK1RqZXhBUTdt?= =?utf-8?B?MEc0WVQvMUlYMjQyTmxpQW1vM2J3Mkx5QUFpSkhSQXJEM29qNHVHTXQweVBD?= =?utf-8?B?a0VQcDRqMXA2Rk5IbEk5UDBvd1NqLzZOVXhtbkkxN25oN0hxNzlzRG1IZG9H?= =?utf-8?B?c3dEMFkrc2orbUQ0Wkh6SkRERXVFYzBuMERDcksvclhpbW5HbWpOV1piTnMy?= =?utf-8?Q?UrA=3D?=
X-Forefront-PRVS: 0334223192
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(39850400002)(39400400002)(39860400002)(39840400002)(39450400003)(39410400002)(377454003)(13464003)(5660300001)(7116003)(229853002)(2906002)(81686999)(23676002)(4720700003)(76176999)(81816999)(84392002)(50986999)(6666003)(6306002)(53946003)(6496005)(9686003)(14496001)(25786009)(53936002)(3846002)(575784001)(86362001)(6486002)(230700001)(7736002)(38730400002)(6246003)(305945005)(33646002)(478600001)(61296003)(5890100001)(45080400002)(81166006)(50226002)(3480700004)(42186005)(189998001)(44716002)(62236002)(8676002)(47776003)(66066001)(74416001)(7726001)(299355004)(19627235001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1563; H:pc6; FPR:; SPF:None; MLV:sfv;  LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTYzOzIzOmtmVnpUbTFaWjRZbUF1dkRtQkZQTlJvM3E3?= =?utf-8?B?RXJCZ2NIOHNVYWxOMU9ROWQxazU0UEIrYnZlQ0dWYnNvWVBLMWNnWE54Z1M3?= =?utf-8?B?NlFFVkxpS1NRcWk2RkppUjdrREJsZG52eTFpSTRsNmZ3eVVQRG9zM1ZaVGdr?= =?utf-8?B?aHNVcmlLN05vTWpWSG42aldqNWszcVRGRTRoREEyQ2JSSHZMSjZ5a2gvTDg4?= =?utf-8?B?Uk0rRWNUekQvZ3hrTlExSlR3LzhEdmFKSmJWRyt5Z25uU1ZuRlZpTXMzVDlr?= =?utf-8?B?V2J1NDRaUWVheFpET1FCNzJZQ2ovMFRrTkFaUUxlVDN3aklJNGlieDJIWjhk?= =?utf-8?B?WEhuVGZ1amJGZ1RES0dvdVF1SWZQU2xDN20reUhrNUNzd1NHZnZrRjBib2ww?= =?utf-8?B?dWZXbmEzcWkzUjZSMkhxZUhLUkh4Si94di8zeExlYWZmYnpxMSsvQ0lzU1VK?= =?utf-8?B?RkhWMURSWUgzZ3F2Z0cvaTR4TmdrL052OGRxTFM4czZESXhXRXI5dVRnSDRE?= =?utf-8?B?WUkzbVgvWnp2aHExQmlSVzNmcWh2aVBBRXQzVnRFVVI0Um1sc2RKMlRwV1gx?= =?utf-8?B?YThCOGV1WDZSdWVaTS9LNlI3WFZONXNEdHJ3OCtpNEkxQ25ZQ091RGRyWHhs?= =?utf-8?B?RHJvTkRYaGxMK0xDRC9OR2t5bGZXUHNVK3BHb1FveU5ZNE1pYUF5WTFGQjhY?= =?utf-8?B?clVTOEw0ZmJlMzl2QUJoeDJzVU9ZT1VGY2dtS2hwUm9CL0J5cndnWkc5QnMy?= =?utf-8?B?VDFyT0k1OU8vcWIxNDlCanM5eHE5WWRWOEtXVENSeTBiOWxGeGFqdVByYUdB?= =?utf-8?B?ZWhxVEVpZ1djem9sUVZnSUNZSTVFMy84MU16NzVEWk1HdjZkVW1zdTlxY1dJ?= =?utf-8?B?S0lrL3R4dkRGdExNa0JLRGhaVlhUOFB0eVRLTFhkZE9jaUJxWjlIdVBjL0Iw?= =?utf-8?B?YXNQMVdLbFQxRnlNK210NHhQL0FMZ1k2dXZGMDdHUzNlRHc4VWZHQkYvV2NJ?= =?utf-8?B?dkxtVVZyYXBjVWNjcEZiVlp4dldJQlVvMEltaUdqVzhydXRTZXZxdUdoT0lk?= =?utf-8?B?K1JGWFoyZEZWWWoyV243SkYyRzgxQmNPTmJadC84N1BuTzFrQVA4bHd3ZmNU?= =?utf-8?B?V2ExV2RIeWtsemxqWnVQbDlTOE90U29wdDhpSWZlK2owWnVlbGVCZ0FxUlV2?= =?utf-8?B?Sk9oaWhMTGN5RFF0NmlOVUxSb204UmJsTm5CSVhFNWdxTE5FczR2TGs1Ni9Y?= =?utf-8?B?ZWNQNTFZbVFWUmhrRmxWNmIzYmRxeWFxNGQ2S21XdVBJb2VQMXB6c2hsWkpv?= =?utf-8?B?MDJvSVdUVWp5TjhURGRtM2t4eVh1ZmtVaW1HT09wLzhEY25mS3JUVlF2ZUpT?= =?utf-8?B?WXBlR2xSOTdlVE5ScTFFUG15SG5aaGZlQldrMFFHQlIwdDFrWnhaVFlpOU9r?= =?utf-8?B?K0lMTlN5b2VFbWJwczF3bWJIaXFnZHFaaUlwMVg1dUdmK2dsTDc3MUJyMnhX?= =?utf-8?B?eE1TR3NNcGZxTENUQXVSN1RpN3dtaFZKOWdOTUs3b2lwNVpROW1LT1V1YUVv?= =?utf-8?B?c0ZaTTl3YXBKQlRZWkp4QzdnUEdudGxTYVE3c3JaNmJaaEdWbWFoRFJRSkFL?= =?utf-8?B?Z1N1aG9nTnhqMG9yTS9uVXEzYXNzTi9wVlB0bGhKZ3R1QVV2UFdVWjdHRm9X?= =?utf-8?B?VGNETEVvdTB3KzNwME5NTml5S1VwZWdPZTVzUFJ6ODhGemkxeThXRDB5SWtz?= =?utf-8?B?SGw1UUVkcllzU1ZvQ2E5cGJ4NUNrKzdKbG5NMjVRVHI5b3dWdzJuV0p6UXFX?= =?utf-8?B?NkNNdzg5S1VHYWd5aG9TWjFBZnJGRDExNzRYd1RDNFM4L045T2xISVFHVW9Y?= =?utf-8?Q?8nC0cnwWPADuUiO04suJt9jGg3oz19+u?=
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTYzOzY6azJGenBWdFRjaW01SzVzaHJpSTh2NFduTU5s?= =?utf-8?B?OTYwYlBWcXB3aU9pQm51U1JkT2FuWEI1dG9yRk9NNDJvdjlJU2s3c2hqajl0?= =?utf-8?B?Y25OT0R5ZVM3RVBTTzFPWW5BOFJEWFQrSU5OM3RnWCtiUWxyRGdOTitJT2hG?= =?utf-8?B?UFdORlZMUnU2YnBkYnFKZWd3dklGN1NrZTY1SWsyNmMrMTRReUJ3UVdnOXY5?= =?utf-8?B?NGNwVzFQOEFuMmxaWit0TkYyNkI3ek9ZTDB3NjNIRWxpZ2hLUTRkTm5FbTha?= =?utf-8?B?MWNPbTJWUmlja1NDcE1adTJwK0FQSTVUbTVuMnk0a3JJOTRBOUpLOGJtVjhw?= =?utf-8?B?bDhQRFIwMWNJT0dLcUJBWTVWTVhQRGJ2NWIvSzc1UDNQS2NndHZ2SDV3WGFV?= =?utf-8?B?MDdCckRCMnlHc0pPOEowbVZTRGkwMEQwckw5cXp6Yi9PR2NocFhKM1lFUGJP?= =?utf-8?B?VjNGajBMR0xnM3pOY1ZVNUlZOFJxYXJCdWVnaTJmanRsY0ExZytYZGIrd3Nv?= =?utf-8?B?Y2cwTlNHZFQrS3hIL0h6dDVvdEhBQlpiOFVlVDkwMi9ENnV3SHNCdnRBOW5L?= =?utf-8?B?WkdUMFBMNFpCZkVPK0ROQ0pzSXl3TWxmRFpJNktZQlBpMXo2VmRuWk1nWDVi?= =?utf-8?B?amY3Z3F6aHorbWZsVHR6QlE3RVI0Um8xeVJiL2Zzek5TVlBvSlgwL09YUFdX?= =?utf-8?B?QWpWYUdmaDR1bFFNRDRISU03dVNZT2RuMS8xZkkrZER2SU9GVlF3WkxXcUJX?= =?utf-8?B?WkcwMXhyM1ROQitKbmZrUmpReU1la3dkbjVPWWNPWm9JUmI4TTI2c3VUTnIy?= =?utf-8?B?bGl0QXhvdmtjcmx5TjBYOTk0UGswSGhNQkI3QStLckIyaXEwa3dQV0lVWHoz?= =?utf-8?B?eGI0L3RoMGoyV3ArWDQ2ek91Z2FpcXc3bE1pVWNVQzN6a2dDbDc1bzhzazUy?= =?utf-8?B?V0xnbVFTU2JGYVZXTDhlSUViRjlMbWpUQ3pjYVk4WVR2WmhqQm5SU1JUcmVZ?= =?utf-8?B?cGs1Y3hqMUlNekdQTjFRWFZ0am1XSzM2N3diaDJJMXAvREYvTy9UdERBdDFN?= =?utf-8?B?K1R5eDl0aktTT21PYlBJckdSUEd3ejRUWExtRWpnSVA0V3Z4N09BZ29uc2Zl?= =?utf-8?B?SHZNWXZEOFZHTWRpYlovczhobXNTaGFXNFlQcDlIVzNWNEtreGlYL3FBSWk5?= =?utf-8?B?aFpwZkJUN3BzNUZhQ1dKK1RIYmlLTlROeDU3TUR0RjBnL21lbnFkQkVSaTlG?= =?utf-8?B?ck9vTS83M2VRUyszRlF4QythT2Y5TVI4WVdYKzM4Q2xnNXBTdTNlQlVQTTh2?= =?utf-8?Q?SV+s46UBErTshEbN8U9xBWXKQJpEyMg=3D?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 5:LNurFghR1ctG3gTXYFNTtMv6hllDnyFmuno1zr8O0MIEWLJmO6Q4s75i3gGCX7al+N0Bf3evQS3N9xECvJYayx0GfFW4wfNQLnUZlKS62hRGA+9fU4LTfgff+YMdBH7tvaKSqEhAP1N1smv+XtZKBmo+/cK1M0SZKzoBPD4IKHJiCRfptJ5n1CwVWG/NgJGfTJ4tIlCX+/LKTbF0IvlxjdeaNv/a8PeqkicXwpnKKXl0MtMSZwPVINiFw9kkZPZfmS1DbMvw6Rz/QKJRwE3ZFmEaapWw95cjVCZQuOzClixe2+NptqeuKRxSBhjH1aOZAxqa1j9kzdg+ua41FI2J0IVL5m4toFfYd9cc2tVL5xaTipOsn/eW4PAXQpfxizYx7Dy3sb2gLHguXza2I4877n4mnVfOknn8p4M0PnYUlALlPOeq2nJ8D0cW4qOZxze+8RRqxymAEUSKo72sxkJkJp2FIcWumDUgrLp2FikS3e0HtujkAqQGfJmhfSixtlCv; 24:cHqYrmfKS2FO0ZLHfixtZEA/pGk5X5NNN37/QSKRFFJiaxsSX9BUw6jMZo2uLyTqfYUCHNEI+t4+O/ZczHMrIRCObZ6d3wXXcRkcOujdcas=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1563; 7:BdddRgm8rqT/pjrt6UUDWDTtq4E3tUvSDSUKR7W2IaF0gZAs5sknmcN8ozjf39FhReoyhyCcCwWZ9ReiN04mdT01kpj25zpLuW6AuVOzKfyJyXarj9q+4x3zovGmE90WBBOPEgqnR0Y/ZpYL3ua7YzXTYefsy2g/1ApXTxwTdzLstUMr7imges3TxJv82JnY5esnuLpcTFRDi9SoQkSxcBdySMbl8wR/E9GOcLTV00UxhBKW2dCnMx4nd6YU0jMIJaB/0GlaakQ8k2JPL64oNXp5DP0esZ04DzOScEjayU+JZ6IGc7YnaS7LtYImHfkXJLk7D1vjxpSTfkEDat8AGt3o5XIYmLqZkaDMezCzpxLHHF4ZjXYpd4mSXRQaJ/0+0Inc4sxEbPl3o1ULe52bMqWD+gcfN97Te3DHKBNO1YUtWeVAr8NZpNoUDvb/Tk3DMZn783ULLLf8vgUtO10tzE9iruOzO0O/yUhgXnKUfIn+VWvhpQDmCS5ctS+gWmQ7t3d8p4rZBcL/tt6Oi9DAJM9gU9cj/k5dfOgynurJnwp1sW3ILd9BlVJ/ozTXCgduHvxPSvXVXTkSdpEDtAQI9vBg0Tl8Tmltbq4MAkMo+C/9DF4nhISXlqI116f+qJJR9TBzd+2Gbt1VXWpbEtOGVMFBswcM3oCHrybjSoVnDo8yXQnSGdEG44FXQLJ4t/Z/jLSYNT+MXCrcswzUIYa/RjV7miifTJ7Sp6vUBYi04R24TONcPlRqxDd9saWRN6yZ5KiAHjkf/t3OA2FoYil3+X5qL/gQaMSKTPcCr+31uJE=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Jun 2017 20:43:17.5541 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1563
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mEf7XIdrpNPXvikCXKzXVt2KTuc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 10 Jun 2017 20:43:27 -0000

----- Original Message -----
From: "John Levine" <johnl@taugh.com>
To: <ietf@ietf.org>
Sent: Saturday, June 10, 2017 1:23 AM
> In article
<CE39F90A45FF0C49A1EA229FC9899B0537173A17@USCLES544.agna.amgreetings.com
> you write:
> >Tom,
> >
> >Absent providing any other data points, how does this tie in with
DMARC doing damage?
>
> Google's "p=reject" makes mailing list mail from Google people
disappear.  But you knew that.
>
> On the other hand, it is true that they've been publishing p=reject
> for quite a while so it's not obvious why some mail provider would
> just start paying attention now.

Thank you, John, those are indeed my thoughts.

I am putting two and two together and getting a somewhat larger number
and so am fishing for ideas.

I wonder if the IETF e-mail system has been changed in a way that we are
not aware of that triggers my ESP.

Or my ESP has made an unannounced change - well, it rarely makes an
announced change:-(

I attach headers below from an e-mail that I unjunked and downloaded
with POP and notice the dmarc=fail among the masses of X-

Authentication-Results: spf=pass (sender IP is 4.31.198.44)
 smtp.mailfrom=ietf.org; btconnect.com; dkim=pass (signature was
verified)
 header.d=ietf.org;btconnect.com; dmarc=fail action=oreject
 header.from=google.com;

and below that is one I received without hassle in March 2017 which said

Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass
(2048-bit key)
 header.d=google.com

so is it as simple as the IETF updating their software to provide more
comprehensive Authentication-Results:  which now causes my ESP to junk
the e-mail?

As I said, the change is abrupt and comprehensive and happened some time
in the past week or so.  I noticed it on Friday although had become
aware of the disjointed nature of the IPv6 threads some time before
that.

Tom Petch

> R's,
> John
=================================================
 Received: from DB5PR07MB1560.eurprd07.prod.outlook.com
 (2a01:111:e400:c577::47) by DB5PR07MB1560.eurprd07.prod.outlook.com
with
 HTTPS via DB5PR09CA0121.EURPRD09.PROD.OUTLOOK.COM; Sat, 10 Jun 2017
17:26:32
 +0000
Received: from AM5PR0701CA0054.eurprd07.prod.outlook.com
(2603:10a6:203:2::16)
 by DB5PR07MB1560.eurprd07.prod.outlook.com (2a01:111:e400:5bc7::10)
with
 Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1178.5; Sat,
10
 Jun 2017 17:26:31 +0000
Received: from VE1EUR02FT039.eop-EUR02.prod.protection.outlook.com
 (2a01:111:f400:7e06::207) by AM5PR0701CA0054.outlook.office365.com
 (2603:10a6:203:2::16) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1178.5 via
 Frontend Transport; Sat, 10 Jun 2017 17:26:31 +0000
Authentication-Results: spf=pass (sender IP is 4.31.198.44)
 smtp.mailfrom=ietf.org; btconnect.com; dkim=pass (signature was
verified)
 header.d=ietf.org;btconnect.com; dmarc=fail action=oreject
 header.from=google.com;
Received-SPF: Pass (protection.outlook.com: domain of ietf.org
designates
 4.31.198.44 as permitted sender) receiver=protection.outlook.com;
 client-ip=4.31.198.44; helo=mail.ietf.org;
Received: from mail.ietf.org (4.31.198.44) by
 VE1EUR02FT039.mail.protection.outlook.com (10.152.13.138) with
Microsoft SMTP
 Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id
 15.1.1143.11 via Frontend Transport; Sat, 10 Jun 2017 17:26:30 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id F1830128BC8;
 Sat, 10 Jun 2017 10:26:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org;
s=ietf1;
 t=1497115576; bh=/Ho/FUrKODC/id0i8RCq7vODJ4+lKB3Zce3OoSd8qV0=;
 h=Subject:From:In-Reply-To:Date:References:To:List-Id:
  List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
  Cc;
 b=lYEsZnwDDAOtb86vlJcnUJI+55tDicUPys8Y5JlS0FUVGIueqMWn/AVi798n5rp7D
  dPtMky8jNfaDdIilvAVXH3NLAhCleiEEA7jlPcby2SmOKyKPHxf4/3ix3G65JlRLR1
  JhjcyXz9vy9qVOfaPLA7SqOLHxf2+5Qtgfm78bbQ=
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 77650127076
 for <ietf@ietfa.amsl.com>; Sat, 10 Jun 2017 10:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5
tests=[BAYES_00=-1.9,
 DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
 HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=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 nJoNT6UKZx7J for <ietf@ietfa.amsl.com>;
 Sat, 10 Jun 2017 10:26:10 -0700 (PDT)
Received: from mail-pg0-x235.google.com (mail-pg0-x235.google.com
 [IPv6:2607:f8b0:400e:c05::235])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 3CC67127ABE
 for <ietf@ietf.org>; Sat, 10 Jun 2017 10:26:07 -0700 (PDT)
Received: by mail-pg0-x235.google.com with SMTP id k71so34574644pgd.2
 for <ietf@ietf.org>; Sat, 10 Jun 2017 10:26:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com;
s=20161025;
 h=mime-version:subject:from:in-reply-to:date:cc
 :content-transfer-encoding:message-id:references:to;
 bh=ZtGTPVNvFOUzYfWK8go3UQ72lUnqON4f8m60bYv6k4I=;
 b=BJ11Os8/GrHAUniJQNH47dCojHjE5bSsQEXCXNMhHIvuuHmbtmyuDMPdAW6SbYEXE4
 VQveikwBtiMZRA3t459N5STf8sdLALORzhQvwqso5l4pTQgvduGCjiX/hdDpR+TIYYyy
 m9qWy/zxDcdadmcqxVe+0p1QeMqCe4B6wO5N3HfR0ZkGXuowxeKk9bvay1LswKO+H/hg
 eFa1chKPxNI3NtpHlvCaikWREe22eGmRCYQxrdkZfVH/PF4+xzAaKLymbFJZryZNtNho
 hPd4cKxX1cymUqV4as4cvyS0a5+GdQwMZjuSwzBl8obpn3eJPi+JtelcotByaaNvYjAw
 XfYg==
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=ZtGTPVNvFOUzYfWK8go3UQ72lUnqON4f8m60bYv6k4I=;
 b=K3oZxjl0oqinHek/g/pQC1D5XnxR/fEmlBGuMnBs3CZsYrmLJNSuU020al7XxSqzht
 TIarYc7kklmSnScDYy68QFF4Q3hvI5HtIRm3cXvNLGgeMzImtq5ZCrwhWWZJziwou0dv
 wlYdpCVQcESr5IuyKls0q95DV5pjdPFZcsuUBxL2ylQfSx4x3rlRt3kb8uwVPLMc84TQ
 zvTvDAr/jmaF4t22vLijvMG/UkvhsKSsLG82k/1CnRwhnxrN/kKq2jF5AL3m1LSg10Io
 rJv51TO6lSPhUseiN9VnadPye8yN4qvwY9gc7A16cXQgUKOeq70IeP5Sa1YpU4ZSIIfo
 TKBA==
X-Gm-Message-State:
AODbwcDyy8FVbEWoQYuWY5UK5oqBiSlc6Ss4cUwnExvbBnHYrSZEEjoh
 WvDzkP6ZZn1qwLa7A8QmRA==
X-Received: by 10.98.80.140 with SMTP id
g12mr17181420pfj.146.1497115566443;
 Sat, 10 Jun 2017 10:26:06 -0700 (PDT)
Received: from [10.0.1.76] (c-98-248-223-72.hsd1.ca.comcast.net.
 [98.248.223.72])
 by smtp.gmail.com with ESMTPSA id k15sm4542588pfb.1.2017.06.10.10.26.05
 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Sat, 10 Jun 2017 10:26:05 -0700 (PDT)
Content-Type: multipart/alternative;
 boundary="Apple-Mail-07F97384-E491-4FE1-AD34-2328613D6C54"
Subject: Re: Genart last call review of
draft-ietf-bmwg-dcbench-methodology-07
From: Lucien Avramov <lucienav@google.com>
X-Mailer: iPhone Mail (14E304)
In-Reply-To:
<CAFgnS4Vstv9zyg9rE4-K-q-6GH-P6noXCmoOLvdjTY+dU_uRHw@mail.gmail.com>
Date: Sat, 10 Jun 2017 10:26:04 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <AC86F980-D9C1-4DE1-8296-70DB2A6482F9@google.com>
References: <149692498024.25760.14056448148418579949@ietfa.amsl.com>
 <CALTEt=DUhEVgSvYN+2XYUR8Ddq5n8HJtZW2RNj3DV3rSgH0YKQ@mail.gmail.com>
 <CAFgnS4Vstv9zyg9rE4-K-q-6GH-P6noXCmoOLvdjTY+dU_uRHw@mail.gmail.com>
To: Dan Romascanu <dromasca@gmail.com>
Archived-At:
<https://mailarchive.ietf.org/arch/msg/ietf/yDU6sz9VOgBkee3KV7bRyDKQ5fI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>,
 <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>,
 <mailto:ietf-request@ietf.org?subject=subscribe>
Cc: draft-ietf-bmwg-dcbench-methodology.all@ietf.org,
 gen-art <gen-art@ietf.org>, ietf <ietf@ietf.org>, bmwg@ietf.org
Errors-To: ietf-bounces@ietf.org
Sender: ietf <ietf-bounces@ietf.org>
Return-Path: ietf-bounces@ietf.org
X-MS-Exchange-Organization-Network-Message-Id:
fc29b2e2-bf02-4387-b9f8-08d4b025d5a5
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: cf8853ed-96e5-465b-9185-806bfe185e30:0
X-MS-Exchange-Organization-MessageDirectionality: Incoming
X-Forefront-Antispam-Report:
CIP:4.31.198.44;IPV:NLI;CTRY:US;EFV:NLI;SFV:SPM;SFS:(8156002)(2990300002
)(438002)(45984002)(189002)(156002)(199003)(377424004)(377454003)(244540
02)(176002)(76786999)(76176999)(63696999)(57326003)(110136004)(236005)(6
246003)(47976999)(230783001)(107886003)(8666007)(54896002)(7846003)(5490
6002)(6392003)(93516999)(6306002)(606005)(106466001)(15003)(81446001)(76
36002)(55446002)(60616004)(7906003)(7596002)(5660300001)(37156001)(77096
006)(50986999)(76482006)(60626007)(63966002)(8676002)(78456001)(19810500
001)(42882006)(2950100002)(81442002)(6862004)(345774005)(33656002)(35600
3)(50226002)(61266001)(4326008)(229853002)(9036002)(230700001)(146002)(1
411001)(16670700002)(189998001)(76806002)(84326002)(53546009)(82746002)(
1096003)(83716003)(956001)(36756003)(117466003)(98765029);DIR:INB;SFP:;S
CL:9;SRVR:DB5PR07MB1560;H:mail.ietf.org;FPR:;SPF:Pass;MLV:ovrnspm;MX:1;A
:1;PTR:mail.ietf.org;CAT:HSPM;LANG:en;
X-Microsoft-Exchange-Diagnostics:
1;VE1EUR02FT039;1:KGT2l3EVvs69KYftOEDpf0o8Ul8F+niXCER6msI0kCt442LwEPXt2q
ap++gpH4/icuhlROyhxv6Rvq4EHJlguhGwlBNRKREEQ9mfXJn3qdBKwwweMHadmI303SR5+C
5DfEsKoeRzMtivgFvEqCehSScPqIxWFz5UHXOSoNljNucSD/ZWNrhXv4BRqPC8+3DAPCWkZQ
xw62V0jMRFTyUqETQC7a+EPmP8sIFyJucmN3A3BDtEoRG1KM4Z/N2FnOlb7sXrDH9jGg91Cd
3vsgG1SJJK3VEZeFXc9iqg88iiUJ78qP4jVsTIQwFQQ7wzPhk2JbZWuC2wGpTHRxPwvnjI9f
IFevOU/HSW9Kpc7I9s1k8rK7ceVp4AiNS/w6Xd3xhO1RUZnDUCLI3iqvMKelkGecR0yZJi3H
0gtAdLEunN36NDvFYoIsXLZIqRTqXFloyoGtyNQ7nBoIMZidjuqPjmjXr3tevW7lyOv0iojD
lMVdJrkUfppigGFIEBzLlcJSSwr/o9+jcVFKI8BD7dr2CtnVOyWdRGLk0vWPhJTyRwY6cab5
dEAzj6etE7PtboAsI3EY8tq9CiDNpp8XlDjuD/5/y7+UtNyQ+5NIfPV2JOBeI=
X-MS-Exchange-Organization-AuthSource:
VE1EUR02FT039.eop-EUR02.prod.protection.outlook.com
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id:
fc29b2e2-bf02-4387-b9f8-08d4b025d5a5
X-DkimResult-Test: Passed
X-Microsoft-Antispam:
UriScan:;BCL:0;PCL:0;RULEID:(22001)(23075)(421252002)(3001016)(3008005)(
3009006)(3010002)(12181505038)(71702078);SRVR:DB5PR07MB1560;
X-Microsoft-Exchange-Diagnostics:
1;DB5PR07MB1560;3:OIn7J7KDriK9MiCyTm4FTkXoblUnLw/StOqgTZXBV1imWg7abWA/ht
IHUbJ13VpYSOqpD5xqnZLplTg7IwpdWit1cieXTWExu/UU0fZLc+SE4A+BlxJ6RESXopKcC/
o6Tzwf/XruQaAQs/OMy/i/k3gPHG9Y6uK+ysVVdDym+CIuQDDEWWvrq4NRf//rwiI0guB1It
V83FLq88DwhYsujbBKXkzESY4E8sGk1BJb+Sjsn/K2xb3VroUjRmeil2OLVvwr+gHEUoq67K
kke0G7u8YftejJKbhm5YXXa25lWSdJ8u3KHrcFeGM5Wrdiot3aVLwA4Nhz+RUlqc86v3yDJa
JBuarO+EWFPFDMb+PVmMqNqNyxBZbJTbpkfHa4H4BnOxGSMrMrsN0te6K8mpTit8CUYTMi6b
9oR/2iqhDiRr8zStUlro5ilGGm/PCus2CtHS/bhVDwddOqIX+3upSZZPXLn6x0mp8PzgA65E
uJLNLI5rlqjIn0a+74tTEvWk/NicHo5A/hTKbLgtIaMDd3ZQ==
X-MS-TrafficTypeDiagnostic: DB5PR07MB1560:
X-Microsoft-Exchange-Diagnostics:
1;DB5PR07MB1560;25:NLAsy94I6Gp1HyaGJKVa0i0GRSbS5iMB/yhVAfWmO9h8jpWTM+z2v
0KMG/dhwArkrFYCP2I9KUHIgtnMU0JQYLkBPkuOPpCjaVWpH/gT7SO1QOsGzHxPGmxCHc/X6
RuPS8/YNJjGhb0gZmPYx9kVcDSLBV55CK09Kze0va1dnjft1sBNByJqCdewG6SqzC86EsOWP
Rlf77uTTIglKLBupdQWZgMBKYSXYuNh8TVIzURC4NbBpVWAYanFiXNmKt3NB50Cqat+yfhH6
7Ozi7GkbBS9pPmlM+TefFGpInbjh5NaLA6dVn2U7LGN9SYhgT7Z3BrBxVW5fuR8kLIPB/yfW
bgnM/LQh0cJ6lotO9UxcjaxB4uIGTZS60mrcZMzUb0cEyuYxHbV2l8vPl5LoMrRAt89qGijs
6EWaWtWXtT/f810F+iT8SJn68roMqZmzde4LpOo/w0PaZmRrGg/wCRb9LGuL3eMTWSzt17g9
u8Y6JA=;31:Cio4PfQRFcMemJm3qrs60ZzipPWerNcdt6BlOMa5zevqtc4oITdLeblQb4BGX
S/UEO1qB48g4BySbPQg7IgxbNq05gB9/2w5fR7JJAQytvhdyk7IYlRaTCmlvyrOzSivVog8L
39OpMM54bnb7+5FpWDaApNuVjL/Eom+xmUuwabzWqZIu/bp7aYopMCLw8EGRQ+PPJNQ3CaxC
EW/dsHv9EyNL8cP0SBUmQH9eev+Ao9jdtOJMd7yuwEp+txqavU+6psLO5R5slwa+8whtB8bP
e42/RmsvLaPB5aGFI7qYGT/4pGt+FdIck73CoW+vVPtBA+7Ye/Q+d8X+oH4WNS6Mw==
X-Microsoft-Exchange-Diagnostics:
1;DB5PR07MB1560;20:jH28SG+tZdi03KxQHOfSWoyCHk/IlJy+MX5ymcchePv7cBqqnKHO3
GPl5+bwD1LLM+jocJctPifxiscLo8mQOLEix4JX3/axBfqDiXQ70ykiHVgi29J/iFtX7KKTH
RUFOzdv1NkUXffRdSoTq+FP1XlDkgFLdoULAZai60RuS3w=
X-Exchange-Antispam-Report-Test: UriScan:(211936372134217);
X-Exchange-Antispam-Report-CFA-Test:
BCL:0;PCL:0;RULEID:(100000700101)(100105000095)(100000701101)(1001053000
95)(100000702101)(100105100095)(61425038)(601004)(2401047)(13016025)(130
18025)(8121501046)(9101536074)(10201501046)(100000703101)(100105400095)(
3002001)(93006095)(93005095)(61426038)(61427038)(100000704101)(100105200
095)(100000705101)(100105500095);SRVR:DB5PR07MB1560;BCL:0;PCL:0;RULEID:(
100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(10
0110100095)(100000803101)(100110400095)(100000804101)(100110200095)(1000
00805101)(100110500095);SRVR:DB5PR07MB1560;
X-Microsoft-Exchange-Diagnostics:
1;DB5PR07MB1560;4:No9gJT7hkTTMu3gbMzmwX9h/tZZe82S8Fsrryi5AlF2xwjWl1yC3CU
7+VPTub9a1e97W0n3nX/7gaZJyaiLWLKL8JXny1IHoq+CUs0BwA38nwS50ztmMLgA6qd/GV+
2gvOiS580Sf+ZXXqn7Yu88OS9IYLWFhl0qJE/mDleYxPWe2P3qEwqwdHWpCi9TGsaHhAxb2v
8Me+brk9WuSL70QB0eU9vLhepW04Zc6aeudz89ZEaw2wiYWobN9DBY95J1X7weBTcXxaEGvG
N8uUTV4xalwe8IH2BZxbs+g4llN0rAQGL44nZAOqh6GnsQG86M8VLX9tVIDBcP9x4waNXrk4
HRxrC4PGL6YSYQxVGNxFNeAvRYb30Y3dkcxojG9hztObxtxwZfFJFSyO9nU48nwsRj8VXKIi
NANmo7zrnjDCPoojXjz540zjwbO2KCZe0QnRULGAU4zQQzTN1DPoKkWLoUHVuReOAe+6tBAD
cPOHsPs9qm4DDHs45Y26TszXntK6w4kHlZ5DObIUfigepHnyo52+XCanf1vSEIt4PwI+KTfU
yZtACbkOg7gh2tDDbobMNaPySZUwZjGeSMZCcKI20kpQ6tFXl0ypqTdRS+d4SbGrVLbE0UFL
iu8DPgraPOslnBEZDGaA749fUi2nmhZx0VcqVK1GfW8smVz7VuzmWAGpW/Rwab0bl3WhuEfr
OJx2+joL/GdHl0oXFyX5HrtNV30/3csGuSpynsA3Zjp8l2xnXvt4odmiuefH3m8ic/wBKiHh
ITshwdVfOkWcQbXKXj8TQCVws/otv6YgLF3bwQB/TClkEk4cRa7dd4Wxq32Udq9JbpiaS7TC
+g3eu49/MGxvooFH8WN0M+3XmtXGQsZBpRyUUQC4vE6Ox/fOENoLFYfeNESJk7ym3DX03For
i0ES3AdVkaamEBXZanDm8=
X-MS-Exchange-Organization-SCL: 9
X-Microsoft-Exchange-Diagnostics:
=?us-ascii?Q?1;DB5PR07MB1560;23:Udv1pT6QLLMgeQ7HJIVeiq4HVcqUx8kwIeD8p0KJ
4?=

=?us-ascii?Q?AFU3ey7JcHknMgqVFRr0DIFg9J2ID1mg1CqDqlq/bYiVJAlq3MC3pCEPvY+
C?=

=?us-ascii?Q?77gx2c6pOYxrdZWSa20WI3hMxO/FMQ5yRLJJTL3HxQpw+xOKznJ8eksV2Ay
R?=

=?us-ascii?Q?uKPN7QbiL4cRq88HrKEq/o69buXfjMZ+llPMQoHjopPUSM50Su3yhPg1tu9
c?=

=?us-ascii?Q?6XArd1NyDXGZcyjlOI0bu7VGw0ijqU6Glg72z5ecJylOdmTYwBwkR2mcYpc
T?=

=?us-ascii?Q?iQI1ZKAhjLyS7lxAyPol4V92niSNZ0HA7xPQg9A1pFe1PsKdpquIfW/o6TC
G?=

=?us-ascii?Q?maQc+HziwUrdsL+UijPJkUuFwFg4gEH6SSrf9ovFEAcGvBtVic8qKue/Ubz
Q?=

=?us-ascii?Q?XsbD8VAOgh4Uhvp9t4HU2PfmOgrzFbBkY6JLMAn1svxjeIFswMRgPbTG4fS
0?=

=?us-ascii?Q?4tkjk53b2NZKVNsJmup7q/FmflHrwbXokIXAvVOkKDFDyapHPLgCBq4zs0e
2?=

=?us-ascii?Q?j9XV4ujIle462KN7bHIbr7xphbsd/XLp95cZbja7xa08q3Qlvcu9uLrliB7
W?=

=?us-ascii?Q?W/3dDZCjeFIjVM+WKAR6uQfu3I7Yf4yrChh/UK2eKmCrmuSJOO5vn2AWs9j
G?=

=?us-ascii?Q?yVtl4P07zeQncCDlopgRtaKYOspSlOqrDo9e+fIYSkJ7seGeeyE3JalxRip
k?=

=?us-ascii?Q?i2g4f9vx1+GlGXmI5aWmwZY/Ta1LpT2I/4y37Y3cLDvdyBB0S79AalusdOO
2?=

=?us-ascii?Q?Duuiobw/OIdUBH7HKp0zQnqfMGvh0lA/1TWzq+lFMJpReJXMGUap8Gt0Y10
7?=

=?us-ascii?Q?ScYornIinc1crdvgXeS2P1S9V8adgHsJRYPtwsMNBu6yeRxKhhQzvmpxh9B
S?=

=?us-ascii?Q?mPtw1j8X0059V1zqGtwKdVy8gDM71LA+Z1aOYIRwjNqrevqOGSrtV1a2TxQ
q?=

=?us-ascii?Q?mrTsGIUKjRe1zw+hXgUbs7xXaXCxJcyf/SHEJw5ouJLXej/LDZdCP0+fECw
3?=

=?us-ascii?Q?RF+2uyRY8udXjSOOy//kb4d6gXSoM72KJaXva2fstlmNPMeqpKXzGJTqSrC
n?=

=?us-ascii?Q?WsEClI7NFBd+rqptWBZE5iHcY2hY7YhihSKMOfgo4WhrQF51ODHG+iDfqzY
8?=

=?us-ascii?Q?hiN/tlHASxQzGsTc+rNmhkwzGBOZQ3JAcxCZ4PVR6/n87hvENKkz2oO7kIS
A?=

=?us-ascii?Q?Dvu4EC8ls2smKP2JlirjV16SwkmYhwrqwPe7wHHHv4v4lRuFr1fv4a24T6k
J?=

=?us-ascii?Q?qYDsOEUti48xfX6GvNW1zWidMcEIGqL8KibavlQgydu80p4m+OKt0fCojiL
a?=

=?us-ascii?Q?pAIp7+EKJ0RFwYVmMSkgNlN+vSH7+iHO6hUZ9xdzgM0rCz2ZNNG8mpHWuk7
5?=

=?us-ascii?Q?8JGUkjZ65/ACjmQfDKiwsQNpkkbC+CpyPI7MAySOutjopg7/ySQQIzKUVU4
7?=

=?us-ascii?Q?5pTjk6t0CqrPq2am56HQLQNNHg0pvsmZll8W/q45HXKIc3umo38GtKkozN2
M?=

=?us-ascii?Q?jfQ7jnbo/pz4EbFl8MeLn4NNoct/yafPfgfRXDXeWKnVr5hHbSqSJe8kR6g
U?=

=?us-ascii?Q?NE0Oz2z/GMfVnLDwF4Y7PRQlruIqwvnna8LuZWzv/uTjCNLHiTHuar2L8eA
C?=

=?us-ascii?Q?F10Nrborv5bTw4f37ONWXgMjt40Rggla6Mue1wFbVZcIb8LC/CSeYs1Yvud
C?=
 =?us-ascii?Q?gfJyTUFb6njT0D515Aopq/0x2nO8yiXYTE2kwiigoAy5dQ=3D?=
X-Microsoft-Exchange-Diagnostics:
1;DB5PR07MB1560;6:eBnq2HFjXM+RHJVaqXPkD+/IK5VnO8RdM7AdaxJwrWAp88oYCNwjoh
+l4IbOMKRQwlp4U1r93usc1Qp2+4jygn41Zra42Nv5u+QO+LAzi/pOf8JhRNcHKydWHeRqNG
+MwDdROyVzu5f+96QI0Ruon9JSVEEoElQ5dBqq/AMLMnEx/Ar1dAJXfbsMQ71TR4dS6YtNmf
BajyX42RBjyX86wS8qgftmt4Br5kqF769aKygQ8Y8iArVfglBZQUTxvH9PwqIMR0FA5vHjjv
oSpKUbDgdfL4W2NywkIS1EbxAMYc7Pi1mnFZNoILiVwvRw3YRoxlmmTPbkb+T/kvevQ3P4k8
q3oc2qJ2rP1LHYhySbxFJbRmk1LAWreUZpeWDnOkXTZbNlMwXZDv7x8M1nN2S6SzOIig8DMk
Iupz9C2nM5zFwfvGvG1vFZHWTVjE+2hjYKFbfhJ4eHERghXnAmifDOAD4JoNSeGPdYkkMgJz
DwHlbQag4DrQr2Y33FCeJ5bVKpdv0hJOH05RaevpMkbK3SQNVgsb/xJTgxKYIyE+4Ec/A=
X-Microsoft-Exchange-Diagnostics:
1;DB5PR07MB1560;5:Y11844Gv53Tiw0usFkau8rQ5eFQkMD0wjBCzyLuDXllvBtluxEzGsC
3VIcXutZd/Xm2cpH5u3azCWbLMxwjpeMdrj6taYntcVjNiGGwSbBAtKCnL2QU56h3l0kcdUW
FJTfMwvzaXexVThIV/Dz/tLgksYG3IsoWPtmxY1+obzRIieYi6RskDMmEqs/QgT3JBYhhv6y
+1rN1qMjmN1qejEeeL52XOoe7ZSACnYrqrawV/NSuAOdd6k/ZjqQ/RFoJeQogZJneWiWFCfO
RvcCUs1VJYmVR4+o9bc3L9ZnXotT+pAJ8OaZDwpFyCdg7lB3gPstAMP8rQFkhBGB8ZjZ35qa
bfNoMjagy819Yv0hGEV92zKs6GYJFSBbN3OyKTINCVcUQgFReiuyR6I41o9cHRL4ixnzcHcX
r6d3XCjMcakfmTn5ftoI6MANv2duZdeTOOsmN16P1yR698P4yXTyN5re88rSjByaOzC/NIAS
4zFfvH+y2JeCHYo8t89SyG6Gz7;24:WAOp82+dekH0kfnNwyL7nxZGlu5kgXygWKApjIxsEu
KHicDHOzqYLv5zobCke/+d2y6R+yjVPRsvOzFGx/Ffbg==
SpamDiagnosticOutput: 1:22
SpamDiagnosticMetadata: Default
X-Microsoft-Exchange-Diagnostics:
1;DB5PR07MB1560;7:HPHm29uhIFhE/jx7/5C3GjTbi7kFV3w04KQhIq9iVDMjE+Gq27+x6r
wovoN0jH07DkLHFRbieVpbEYXNrCQtD/hU+a+IY1K68O9TRmlD8/Jndwx+0YqfjESsZTrKXL
V2p5ilFd1U/QiWvlSjPaX7Oy2VpRkhnh9xkCSeNrZOxMzfJdF2ebO42AttvKMl+qCtGZTIul
0A7EAu5G6kHwpmlA16r4lB1qtxvbhCHN6FFYQAyFIRexPBbCblQJErPImlsrwQkrbEEkI3Aq
mYYI2PuqRx5eGrru1Leb0XUMkFewZCYta+2He9na2t/0oWS7FSNC0Ff7R+D1DbVTh0xHcGKR
Vmb+GGrjqka03LBmJwdiF5V1S058xaZayKEl2jKjXMBoBMslgmbWMOQXHGyHg/DqtZzGIFYn
Lm5IpGkPwIc9OKXQ2xzW5eVrFVGYUpoZg8WuACpl6bJOj+IHSj6U9Ysj6eeRsu2ykVphwf98
cXh5GBWYs/KsvfJ5ydP7i2RX3k
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 Jun 2017 17:26:30.2643
 (UTC)
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB5PR07MB1560
X-MS-Exchange-Transport-EndToEndLatency: 00:00:02.4795905
X-Microsoft-Exchange-Diagnostics:

1;DB5PR07MB1560;27:0IEKDSRD8rt7WZ/lSTKiYkKtn0y+KT2CPDpwOjg/F7i6Tg1+KH0Fs
pR5bqrdag77rJGU23IHxtGa9gcLEtTXjfNSx+7+K6P/qx6Q8MbNRfgLaz+X0UON9lRYAofv3
VPLmHVeu+GJFz30k6oCzFeBEA==
MIME-Version: 1.0

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

Received: from AM5PR0701MB2996.eurprd07.prod.outlook.com
(10.168.156.146) by
 HE1PR0701MB3002.eurprd07.prod.outlook.com (10.168.93.136) with
Microsoft SMTP
 Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id
 15.1.977.5 via Mailbox Transport; Tue, 14 Mar 2017 04:07:23 +0000
Received: from AM3PR07CA0034.eurprd07.prod.outlook.com (10.141.45.162)
by
 AM5PR0701MB2996.eurprd07.prod.outlook.com (10.168.156.146) with
Microsoft
 SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.961.8; Tue,
14 Mar
 2017 04:07:23 +0000
Received: from HE1EUR02FT043.eop-EUR02.prod.protection.outlook.com
 (2a01:111:f400:7e05::208) by AM3PR07CA0034.outlook.office365.com
 (2a01:111:e400:882c::34) with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.977.5 via
Frontend
 Transport; Tue, 14 Mar 2017 04:07:23 +0000
Authentication-Results: spf=pass (sender IP is 4.31.198.44)
 smtp.mailfrom=ietf.org; btconnect.com; dkim=pass (signature was
verified)
 header.d=ietf.org;btconnect.com; dmarc=pass action=none
 header.from=google.com;
Received-SPF: Pass (protection.outlook.com: domain of ietf.org
designates
 4.31.198.44 as permitted sender) receiver=protection.outlook.com;
 client-ip=4.31.198.44; helo=mail.ietf.org;
Received: from mail.ietf.org (4.31.198.44) by
 HE1EUR02FT043.mail.protection.outlook.com (10.152.11.140) with
Microsoft SMTP
 Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id
 15.1.961.10 via Frontend Transport; Tue, 14 Mar 2017 04:07:22 +0000
Received: from ietfa.amsl.com (localhost [IPv6:::1])
 by ietfa.amsl.com (Postfix) with ESMTP id 85B73129C51;
 Mon, 13 Mar 2017 21:07:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org;
s=ietf1;
 t=1489464435; bh=OsWhB2gqoYehkwv3+6OPccAu1iQK1vNZQkuB9XXh16k=;
 h=In-Reply-To:References:From:Date:Subject:To:Cc:List-Id:
  List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe;
 b=gRfTRVTDWSyE2xyZUfIe9lXUAXzzIwghJbCEutTiukj3jLSE7xvjkQIdJOOH63Zkg
  oi9hhQGZLC+uh92zJQgswcKPVWYcb4qNmPgF2SW9AUXq8JXhC8MYiYZ7w2PX78sYmv
  Ziao05vpKFP5UuZUpwRJyteK283HuqB753PH1H1M=
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 44362129C46
 for <ipv6@ietfa.amsl.com>; Mon, 13 Mar 2017 21:07:13 -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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass
(2048-bit key)
 header.d=google.com
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 3iV5GZldIi1I for <ipv6@ietfa.amsl.com>;
 Mon, 13 Mar 2017 21:07:11 -0700 (PDT)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com
 [IPv6:2607:f8b0:400c:c08::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 BCABC129C43
 for <ipv6@ietf.org>; Mon, 13 Mar 2017 21:07:11 -0700 (PDT)
Received: by mail-ua0-x233.google.com with SMTP id q7so147531098uaf.2
 for <ipv6@ietf.org>; Mon, 13 Mar 2017 21:07:11 -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=pMYHbHtAZ8pVnmfgSioTLUnLmBMi6wQcHKSlabkpxaw=;
 b=JNGnKJAi/9egd1x+4U6X6A8JH85svdoY85d9B7jFbR+iMtCFvR1PVQInT0fZk4qHvl
 /7a2BkMknehH4n6r+Q33OPVi3sXSvqERbgoZJUMjxle7Q+uFJ3MrXK9ClJ5k8LtpCbtE
 SPgT9rHrmoycGMiz2+sjGufTwnUL/T08YSXrCWo3eIikcgYt8QR1jtoJynxRCEDe5dYX
 ITXHV5LTjipNnQ6dFkPqWvAEn8qrdLwnaU79NQZ+A3iH/1wlGiThmgdePS8uynqlIc96
 3/IAAimNqSAM/LNQS1IS8ajG7c1QukKWq/aM1cNjC6oZtHTz64mhIsf8sq0uzTE5VWOE
 yIYw==
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=pMYHbHtAZ8pVnmfgSioTLUnLmBMi6wQcHKSlabkpxaw=;
 b=ZuTPQ5VZhUkmPL1/q10NHWV5qPPu28zDfM8xo99dpPCotoiUJ/THdAqu0oIXJRsDj2
 UFmnd2/WOJzIEyhkyFjHjLNH5bmuJCXJZhmPPd986wixEWnVb10Zw9mDAclHcx10ADyH
 LVI2wND2lmtkGG6nYJFHHkm24EXAJ2DEVGrAO/cL12iKsy9k6gVwKf0R9qxDAfhggAAO
 DTVeYSviUuQOpAxvZSMC5obQ0OZAjyOKe+NBK1iCHu9chYOomOdhGKWtSTaMNLx6CfaJ
 xHgQWVKTHAl+Y/dqWasy5A+4TNXlo9+yJXSIBQ9AgB8oAkn6Z5BfCG03/ci0Kfne+jsl
 d6bQ==
X-Gm-Message-State:
AMke39lwOImitNqmN8jr8pFvq8BTFCKei7LD+s5jZ+Ecqx/AHwKbfLqcXO3oEhD5MOGZqmp0
ocoILOoy2p90Dbh3
X-Received: by 10.159.36.10 with SMTP id
10mr18430925uaq.124.1489464430559;
 Mon, 13 Mar 2017 21:07:10 -0700 (PDT)
Received: by 10.31.171.2 with HTTP; Mon, 13 Mar 2017 21:06:50 -0700
(PDT)
In-Reply-To:
<CAJE_bqdd9OXOi+SZ8_OfGWXxEoKSfoR6=Lp3-_=vEaWbjx4udw@mail.gmail.com>
References:
<CAJE_bqdd9OXOi+SZ8_OfGWXxEoKSfoR6=Lp3-_=vEaWbjx4udw@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Tue, 14 Mar 2017 13:06:50 +0900
Message-ID:
<CAKD1Yr3ncJkNwZgpWpr049K497iLAQ3dCzJ6dCHM1VsrC8UHog@mail.gmail.com>
Subject: Re: a draft about on-link and submit prefixes
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
Archived-At:
<https://mailarchive.ietf.org/arch/msg/ipv6/QVWSzTogtBKFZm2G1wkL_USAAzc>
Cc: IPv6 IPv6 List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>,
 <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>,
 <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed;
 boundary="===============0744342647399689566=="
Errors-To: ipv6-bounces@ietf.org
Sender: ipv6 <ipv6-bounces@ietf.org>
Return-Path: ipv6-bounces@ietf.org
X-MS-Exchange-Organization-Network-Message-Id:
115c00ff-6646-44cf-c3fc-08d46a8f9ddd
X-EOPAttributedMessage: 0
X-EOPTenantAttributedMessage: cf8853ed-96e5-465b-9185-806bfe185e30:0
X-MS-Exchange-Organization-MessageDirectionality: Incoming
X-Forefront-Antispam-Report:
CIP:4.31.198.44;IPV:NLI;CTRY:US;EFV:NLI;SFV:NSPM;SFS:(8046002)(299030000
2)(438002)(377454003)(176002)(156002)(24454002)(6246003)(16670700002)(54
206008)(6862004)(81446001)(189998001)(4326008)(956001)(9896002)(10788600
3)(110136004)(2476003)(229853002)(50986999)(7596002)(146002)(55446002)(4
98394004)(78456001)(6392003)(606005)(7846003)(8676002)(57326003)(8938600
3)(1096003)(19810500001)(2950100002)(42882006)(270700001)(260700001)(866
6007)(76482005)(47976999)(54356999)(76176999)(42186005)(76786999)(14003)
(93516999)(37156001)(63696999)(9036002)(236005)(6306002)(305945005)(7906
003)(7636002)(9686003)(512954002)(76806002)(84326002)(512874002)(5354600
7)(356003)(81442002)(61266001)(106466001)(24616003);DIR:INB;SFP:;SCL:1;S
RVR:AM5PR0701MB2996;H:mail.ietf.org;FPR:;SPF:Pass;MLV:sfv;LANG:en;
X-Microsoft-Exchange-Diagnostics:
1;HE1EUR02FT043;1:LsPogyfM75G+VyRq8SY2eF8S/tJVvY7GaxUSDhRtk0qfVoYVbXLVsR
XhmyXKsnsHEqu3C9Wroj7oeaGkOoL5DzDi/t1s7xocoVkxr4N79HIQ0B8dg1MpCI1tWlakGS
ckbcVKew6N/9xB79EZBN2gkuu1gIjxGuat0PAnoDc3+lL1AKZM8fMqEzOMNDdVJNJQ12NjGK
/rgf592EMO3is/UrPMk1AnNbSk0tpdUeO3upZAJYNdt3VnxrSvk+X0hbX/cr+hEHAG9304BY
7a38Cii2HiSCeONH2lRSFQv+Nu4I8hDPcaiD90/OdbsGkhGYhhy2mskdU25AF+Lp76OwsN2L
Gj/2qs0b+k/4N+nOnQtKmQ36Fx5hjkSi1fWXLpt/SV6pI/17GahMwKCZUVwEbgnqVSXJYP5y
L5hlJYmabFt3hGgQ5yAlSvWdztdFFfDANVxuDvXU8adKJ3y5dCi/1HSwaBZWyfl2MP/Hz87h
8PZ0NWNq/oqJm6D0d6FiP+XPboGsLzNMIFgo1WkAsDsBsl0FNg+g/5bnZjgdzOHZEBQSnveK
K/++ahdtBtBXBNNIjft0rSt+9UGBFen6vl9Q1yrA==
X-MS-Office365-Filtering-Correlation-Id:
115c00ff-6646-44cf-c3fc-08d46a8f9ddd
X-DkimResult-Test: Passed
X-Microsoft-Antispam:
UriScan:;BCL:0;PCL:0;RULEID:(22001)(421252002)(81800161)(8251501002)(300
1016)(12181505038)(3010002)(71702078);SRVR:AM5PR0701MB2996;
X-Microsoft-Exchange-Diagnostics:
1;AM5PR0701MB2996;3:Cca4jHTjn2slGwg6J1QBLVhzHN8zzUuedsV6qsXJKZhj4eFu2//+
IN/WmJWpije9WmB/E3o3Dq1iNobxPCr8KNPvgP0tLRXjAbUnglhGUZe+KJKdMDxCZXJhXSOS
bgLy6U07BPYEAfzYcSTLTCGiA2SuIaH2B0qqaoYLm6glwafYzq97nyScdubr0OXCvmz2uJTz
b7PK9jjQ2fP+6b5KDJydZiVZI8QwZX2I8TXUV6T9Domi65xt4qveasBMYykio2GR/FWyv6/t
xbkBewwLix0vigxhNFdzlvA4xoOPQteDKbu7sxwV8uhQ4EDu7cr36rbF51f1EE2+L/a1s5xD
PEzL51wsH37aGwKs1D6tNaMBCJDBTcyoLL2AFkx7mZ3g6Sn88lnxqOH2odmEVGwuegIjk369
WVaC243/tdLCSDPheHxqb4cLcXxVJPiyD2Lknv5QETBxeW+7qPtTl5y61b7bG2Ss887lRKcO
/58rcH9PUOg4VezJZ/4BFL7F0AYbiQXmLRguNmrkFP6otJyiSQ==
X-Microsoft-Exchange-Diagnostics:
1;AM5PR0701MB2996;25:jytImewa+9+senliw5tKFKqPzsE/qIkbDvxKLb9YJxScDWtOz95
mAlFpCmU5GjVC8rSMk+UNjvNwVccuKOnKuRXyT/ecMjG6cDmqmSGAjeui9Uo5nAZT8wNhl7w
7uposkGWCZtMQ04HvdLS9SoFhQQuMIa7coMMDjbNYcvmyX9xAkeaOMay8BAa1x1SWKVrzPEm
PIUw8NDpvpXd0Kcjs89/Mdejm6TypbBcLsfwIS4ETMzcK6pJZRA4Do3vAfiHqk3F165Ks3b0
nnphkO8ksQZZCF+A+Y0ae3ReAR9scjn0kEG+UCvT7PSNjTxkuPT6JDHv6jsPFOu7Umv/LRCA
0AsYAKN7w+umZKIjKH6ROcPBx665Hh9GG4qSIr65EW8crTznCCETA8w34CZLFL/71xc97ZMS
3T97/s59u+Y6yIMTut7v6Kdk5rOWe6U7kp1eH1skI7m9hNKdzwTV6yz+py7Hy/XfPlwicC99
dxRoAx3hihIwEj0qN8IqRgfs2RTQO;31:adBamT8Ted8JubFGRMwboo3SkDpKn559B5lek9S
oVp1EE0oE6cKb6z12+3O+7aZ+Lm3E4Kjwa3WHDoIU5ss+P9gK2MzfTggtXpygs0h5SPOAkfu
nPaW2GtEck9TFeoCWKfkNIysC+2F/nqi/PWsbGKhwzqGYhdtUe+HzeFPfSyxeIHTCiPiAluQ
J7PLQEAU3FdmuLwZZTycQBZfwganVzMqnZJCixzsrWRq9fWdbDCDzj/wakKnn0e69zI1BLRb
ZyO+msS8JeXLYlR3VWHg2P4+q5XItyJDqJ9/ykv1L7EIGFgiGV0F42yAhEDGWEXMnpAmep1d
8klGu9supmrUMuA==
X-MS-Exchange-Organization-AVStamp-Service: 1.0
X-Exchange-Antispam-Report-Test: UriScan:(120809045254105);
X-Exchange-Antispam-Report-CFA-Test:
BCL:0;PCL:0;RULEID:(102415395)(61425038)(601004)(2401047)(8121501046)(13
016025)(13018025)(9101536074)(3002001)(10201501046)(61426038)(61427038);
SRVR:AM5PR0701MB2996;BCL:0;PCL:0;RULEID:;SRVR:AM5PR0701MB2996;
X-Microsoft-Exchange-Diagnostics:
1;AM5PR0701MB2996;4:U2vh5xGwfs+BdUPiGGk8B0fqFfjMnuqCtz2FuqIXbONdUfI1Z9W1
py1wZilIqAh/qGTNES/VjMagzpS7gvf5XCjXtSdRXYhzX+jv7I5hXMFGCWIxPk010DDLnull
AacURVuAqlaz8u5Zvd3sV14N8DTJiNaI81j5L1xMSyNV8zcpyFAL/ROxzgEl0GtyxBi69o9c
012VPz2YDWXJx3g6GS7RnFROx2B/2P2P1/7294IgAOrsag0hUoZpnX0FhPTwkeaJg4W+GhUZ
hQqkhjm0YTW61TgwJzDZ9wAeuLkHApzPHkYJeSEgnHsGulH9heJ/fa0J23aob95NkwaKsqDn
CUWk07wsVjgEn/BGEvSuB3xDS/0zEKao6iSO3zgpzjLOTrBQ1VdGHIJrPXm7a6pQzQC2RzW9
Jv8SqWmxAFgqHnhijxMX7IL1eRY8dtLJAjQNRzuBrX06FTP07UNTjkw/5xMq+JfH/ZDaBrqe
q574eoxGBv4H5jHu4BXM/jWLo/oDvlLI4YqwX2qDNKwnF9PMhK+/d25CBIrnnA1LRFVi82Xn
369//iF+pu9wnSIgzcq3
X-MS-Exchange-Organization-SCL: 1
X-Microsoft-Exchange-Diagnostics:
=?us-ascii?Q?1;AM5PR0701MB2996;23:fBVdmFC9kd+vJxJXRK4OUYH2IetbRJv3H5oGLf
O?=

=?us-ascii?Q?C1B7vrxAK+gTGND57Efe4gwboDCIAPQGpmJpVMeTn4GspgYDTmfL7L+ZBYa
A?=

=?us-ascii?Q?5XhQkZwEeL57RQczBiJ/GYQQsbViUAsBaRgauUGLxTjGbyGJ0NksTho7s2f
p?=

=?us-ascii?Q?MRPtW2HQlyNVwo15lhYgPzGqyrcOa6UVlBUEQD55yar7q6EwK+/4f4I78/g
t?=

=?us-ascii?Q?KCIGwevmZR38vxfR4n8H1OHY+QN+8OLjKScc0v3aDAxYhQBQgOSlov5Npz9
Q?=

=?us-ascii?Q?UOZW3y3WTartOw/qJIeYVaFrmB+uS44jPoPOh5NgSOBkbMacmVcNsOa20Wk
S?=

=?us-ascii?Q?LhTReLtoiHj6sRtKUgZLq0yKmKPJ7GvypE5wKz96GsgPCBeqwCo9/ztCb0g
3?=

=?us-ascii?Q?wJJfm48lGIPqQMPhqW71dQMe3WKE6aCedmdZX2cFdKukClhyv/9kMXvpfey
/?=

=?us-ascii?Q?kK2QI/kZQYSO5U91If2B5FuHwmJDo40v6J2wHkDLXKMEL1coiNJg+W9T22z
5?=

=?us-ascii?Q?9CzKr/GRZFIbKM3T8brQUranUfi2PdaVP+XU9igdRbpN2sZ3rWeiKZuu1xF
T?=

=?us-ascii?Q?l9shqhzVD0r4LWLL+IjEFdBREZiktiiVcXWsgByTDEKNzvJAmJiyk6djVBs
7?=

=?us-ascii?Q?W3dslr1xHaTKJ7nhKa0ymPlnjqssxI7tbqHB7Rcf+Ii3DmpkW/AQ/E1m9hL
f?=

=?us-ascii?Q?aQHYo2DRHOBpMXEYLah97kOoXVgFExAm3SvhQvg4PM+JYLG/zZ4Q1X9PmlA
k?=

=?us-ascii?Q?x60p1LSahneMjz28BamNpqhDw7puqjAxkhgZEVnHLTOFI0r3cIUHGpmtGMm
H?=

=?us-ascii?Q?n3fxyS++dFkIBOqTfgnrAMNVXznPT8mVXQOp6K4VWewa5Wh3Y+uEBiAdJnF
L?=

=?us-ascii?Q?o8Sk16sLiNynUcoxsprHlztBTWAiNrei92kf4iktPJ+qVgK9cJHj0DjYofF
o?=

=?us-ascii?Q?YTX/XZrEdsFXLW9mr7J9Ydna1vaMl/rFwIF5VsgPB3V5sWcpQM9HM/btr1p
Z?=

=?us-ascii?Q?SHvprzdBrR7HDOQBqWA7AiMG0SSusZT9A7GpQR1g+Bwdn9S657dNBZPykpC
b?=

=?us-ascii?Q?cnegK1TXLIfuJFOosynQfVo2XR9w5VrFUrHccbWXQQXGrs57iMXwST+3B9B
z?=

=?us-ascii?Q?YLyN0OlTtTgiGWIWYTUJluNANIKmbWTNAgohy9+wucM8lgPvjfHBAdSSqxj
3?=

=?us-ascii?Q?RX4dZCu/R7io/6rBp+9N4vsRzkG/kAelJi9mjeUTy2I7lp9fI2IFJeO7y6Q
D?=

=?us-ascii?Q?UyEe/51R7wJbb2xN6G1zHvyDzpcokFyjgNECn6IYBQCIKhycB6OsAh47BEV
F?=

=?us-ascii?Q?931WL72sgj/fYeWghti1D3uItEooDDOy1w/48Wjhkj+W1AdgNyNWy3QvKJq
E?=

=?us-ascii?Q?rKBOsx/yeodZv+nvLeOp8RnyrxA02fK3V3gWupqWvDwd9XNqMfVZd1aCdEv
H?=

=?us-ascii?Q?UmnVK9vKbaDguGDthRO+xTuMJLKgoBLocuvlmYxmc9QJF6zEvnCdXRKHGgn
m?=
 =?us-ascii?Q?f7RgtonH2lj9cHw=3D=3D?=
X-Microsoft-Exchange-Diagnostics:
1;AM5PR0701MB2996;6:GzBmjK90OJDOVC/ljQ7VjqKaMp1eXm7Imbj2kheBqId46sN7Nra5
uiCfiZeMPbgwuaCbuNU+i6z6afVbXF22N57sYapjolxBboXCcIp/6NZPa9e+WvnidUwFiCcm
4cLOiAx5SgtngnFemC5AeJ1/MXPhjmtb32DxpYohOGQ97BIHettiKQEPSHpxiNXVUbmu8yNi
L3ATxW89eDuFYCr7CCTp8PnvlNZp8TNJsdzOZELce1k55FUkJ5GKvHQj2WGl9lxUkgw/8WhY
PpErbQaDjSstvvna2yDhIpon0a4uZ1CixF1ZqNIE/aFbO7khstkljyyo7jG7WntsrqQOtStA
kzfb/2fBz8qcycSG7Bltl3I2HP+ULmU8JIQSDU15LUO6AURK+N+cxPeVAVriV3a9jq8nSCfr
HR8WEMLAmrzifYU=;5:KGerXoyjkpbh9/fTs6z0Gv727+AH4g+I2fxrGpiMpzob8HvlJS4ll
V99Hi0BEdMgh2Q/k0lNXOrDVHPj8dt915nzHpBQow0RTjQgkbf51EFQHE98mpTDk6UDcTZL5
w3beHewNYTAvGCqKjbDdp/LMg==;24:fNBZtZwEpiq4AnFmMvzQR05Iuei0QvHslYBcxNi+Y
3vSn0Qe0z2NuF8Fe4/vGfEkKQtYIMiZmMpN0Y/mmgNetXbI+Jq4cmttActxflSwVRE=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics:
1;AM5PR0701MB2996;7:iBLcL/g4cUj/DZy8RbkBTUh52R4EpX4xHgSdFOJURwiNnJiy+hqf
UHYKeMBe/LyNY/DhLP143AoLMaMoksxbozMT2amejva8sDGe+CMs2f1zhdMbGoGaUewTKagT
L2bfEtHA3Tnbm1LXXL7G/Bkww2uJrFc6UGQeK7fShWd3vfkNjYR9wWDWPGnZwJ1tBJhCR0pN
P1lfCDefaetd40mgL1/IJBrwA9HXgUUd8PcTg1ufd3Sl6fA1b5JeOv6pW3OGAlmEIZcJHziP
tmazTOhr+QO69qIxjnCrLCeZSEBJGCrJWF0WsPs1oOiaRMkYeq5aeko4EEihTsCAZKxDwKAk
3HheHU+Kj1OG8Gb2w94TvOmzLdjphf6bYkQjxLLbryoV
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Mar 2017 04:07:22.1256
 (UTC)
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-FromEntityHeader: Internet
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM5PR0701MB2996
X-MS-Exchange-Organization-AuthSource:
HE1EUR02FT043.eop-EUR02.prod.protection.outlook.com
X-MS-Exchange-Organization-AuthAs: Anonymous
X-MS-Exchange-Transport-EndToEndLatency: 00:00:01.9527402
X-Microsoft-Exchange-Diagnostics:

1;HE1PR0701MB3002;27:9GOyxlSf2JYTyPy+en9N5hcIOoC1XyGYUg3wHyiJrs/gA+bWxE6
Qu1R3rdPoRw785qUFYO8qXuv9AmuNlrbWEnfOOD7gDi4cQtVLq0QvzZ/QM6i9Tgy4g8Nebpf
W8AXfwU3HSKqJhbT8WqERruX1tA==
MIME-Version: 1.0
=================================================


From nobody Sun Jun 11 04:20:41 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 38FC61294CC; Sun, 11 Jun 2017 04:20:27 -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 fuIg5cD3EHXa; Sun, 11 Jun 2017 04:20:21 -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 366DE129503; Sun, 11 Jun 2017 04:20:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml709-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DIH36148; Sun, 11 Jun 2017 11:20:18 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml709-cah.china.huawei.com (10.201.108.32) with Microsoft SMTP Server (TLS) id 14.3.301.0; Sun, 11 Jun 2017 12:20:16 +0100
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by nkgeml412-hub.china.huawei.com (10.98.56.73) with Microsoft SMTP Server (TLS) id 14.3.235.1; Sun, 11 Jun 2017 19:20:14 +0800
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.49]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0301.000; Sun, 11 Jun 2017 19:20:13 +0800
From: Roni Even <roni.even@huawei.com>
To: Jonathan Lennox <jonathan@vidyo.com>
CC: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>, General Area Review Team <gen-art@ietf.org>, "avtext@ietf.org" <avtext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMAgAAtEkCAAQCzAIAFrKRw
Date: Sun, 11 Jun 2017 11:20:13 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7D0641@DGGEMM506-MBX.china.huawei.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com> <B9294064-4F4E-4FA1-A864-4F9790767B5C@vidyo.com>
In-Reply-To: <B9294064-4F4E-4FA1-A864-4F9790767B5C@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.55]
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.0A020201.593D2772.0117, 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: e2a6e4c8b8332e96d28b21904c02d2cb
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WrtgON4vlxBp4MxwjTmK84t_C-k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 11 Jun 2017 11:20:27 -0000

SGkgSm9uYXRoYW4sDQpJIGFzc3VtZSB0aGUgbmV3IHRleHQgeW91IHByb3Bvc2UgaXMgDQoNCiJX
aGVuIEMgaXMgMSwgVFRJRCBNVVNUIE5PVCBiZSBsZXNzIHRoYW4gQ1RJRCwgYW5kIFRMSUQgTVVT
VCBOT1QgYmUNCiAgIGxlc3MgdGhhbiBDTElEOyBhdCBsZWFzdCBvbmUgb2YgVFRJRCBvciBUTElE
IE1VU1QgYmUgZ3JlYXRlciB0aGFuDQogICBDVElEIG9yIENMSUQgcmVzcGVjdGl2ZWx5LiAgVGhh
dCBpcyB0byBzYXksIHRoZSB0YXJnZXQgbGF5ZXIgaW5kZXgNCiAgIDxUVElELCBUTElEPiBNVVNU
IGJlIGEgbGF5ZXIgdXBncmFkZSBmcm9tIHRoZSBjdXJyZW50IGxheWVyIGluZGV4DQogICA8Q1RJ
RCwgQ0xJRD4uICBBIHNlbmRlciBNQVkgcmVxdWVzdCBhbiB1cGdyYWRlIGluIGJvdGggdGVtcG9y
YWwgYW5kDQogICBzcGF0aWFsL3F1YWxpdHkgbGF5ZXJzIHNpbXVsdGFuZW91c2x5LiINCg0KSSB0
aGluayB0aGF0IHRoaXMgdGV4dCBzdGlsbCBvbmx5IGltcGxpZXMgdGhlIGJlaGF2aW9yLCBhbHNv
IHRoZSBjdXJyZW50IHRleHQgdGFsa3MgYWJvdXQgdXBncmFkZSBidXQgSSBhc3N1bWUgaXQgaXMg
YWxzbyBmb3IgYSByZWZyZXNoIG5vdCBvbmx5IHRvIHVwZ3JhZGUNCg0KTWF5YmUgIiBBIHNlbmRl
ciBNQVkgcmVxdWVzdCBhbiB1cGdyYWRlIG9yIHJlZnJlc2ggIGluIGJvdGggdGVtcG9yYWwgYW5k
DQogICBzcGF0aWFsL3F1YWxpdHkgbGF5ZXJzIHNpbXVsdGFuZW91c2x5IGJ5IGVpdGhlciBoYXZp
bmcgQyA9MSBvciBieSBoYXZpbmcgYm90aCBDTElEIGFuZCBDVElEIHdpdGggbG93ZXIgdmFsdWVz
IHRoZW4gVFRJRCBhbmQgVExJRC4gSWYgdGhlIHNlbmRlciB3YW50IHRvIHVwZ3JhZGUgb3IgcmVm
cmVzaCBvbmx5IG9uZSBsYXllciB0aGVuIEMgTVVTVCBiZSBlcXVhbCB0byAxIGFuZCBvbmx5IHRo
ZSBDVElEIG9yICB0aGUgQ0xJRCBvZiB0aGUgbGF5ZXIgdG8gYmUgdXBncmFkZWQgb3IgcmVmcmVz
aGVkIHNob3VsZCBiZSBsb3dlciB0aGFuIHRoZSBUVElEIG9yIFRMSUQgcmVzcGVjdGl2ZWx5ICIN
Cg0KDQpSb25pDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEpvbmF0aGFu
IExlbm5veCBbbWFpbHRvOmpvbmF0aGFuQHZpZHlvLmNvbV0NCj4gU2VudDog15nXldedwqDXkyAw
NyDXmdeV16DXmSAyMDE3IDE4OjMwDQo+IFRvOiBSb25pIEV2ZW4NCj4gQ2M6IFJvbmkgRXZlbjsg
ZHJhZnQtaWV0Zi1hdnRleHQtbHJyLmFsbEBpZXRmLm9yZzsgR2VuZXJhbCBBcmVhIFJldmlldyBU
ZWFtOw0KPiBhdnRleHRAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IEdl
bmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci0wNQ0KPiANCj4g
DQo+ID4gT24gSnVuIDcsIDIwMTcsIGF0IDE6MTUgQU0sIFJvbmkgRXZlbiA8cm9uaS5ldmVuQGh1
YXdlaS5jb20+IHdyb3RlOg0KPiA+DQo+ID4gSGkgSm9uYXRoYW4sDQo+ID4gSSBkaWQgbm90IHNl
ZSB0aGUgdGV4dCB5b3UgYWRkZWQgeWV0IGFzIGEgcmVzcG9uc2UgdG8gbXkgZmlyc3QNCj4gPiBx
dWVzdGlvbiBTbyB0byBiZXR0ZXIgY2xhcmlmeSBteSBxdWVzdGlvbiAuIElmIHRoZSBGQ0kgaGFz
IFRUSUQ9MCBhbmQgVExJRD0yIC4NCj4gZG9lcyBpdCBtZWFuIHRoYXQgaXQgaXMgYSByZXF1ZXN0
IHRvIHVwZGF0ZSBib3RoPw0KPiA+IFRoaXMgd2FzIGFsc28gdGhlIHJlYXNvbiBmb3IgdGhlIHF1
ZXN0aW9uIGFib3V0IGJvdGggVFRJRD0wIGFuZCBUTElEPTAsDQo+IHdoaWNoIGxheWVyIG5lZWQg
dXBkYXRlIG9yIGlzIGl0IGJvdGg/DQo+ID4gQ2FuIHlvdSBzYXkgdGhhdCB5b3Ugd2FudCBqdXN0
IHRvIHVwZGF0ZSB0ZW1wb3JhbCBvciBzcGF0aWFsPw0KPiANCj4gWWVzLCBpZiB0aGUgRkNJIGhh
cyBUVElEPTAgYW5kIFRMSUQ9MiwgaXTigJlzIGEgcmVxdWVzdCB0byB1cGRhdGUgYm90aCBsYXll
cnMg4oCUDQo+IG9yIG1vcmUgc3BlY2lmaWNhbGx5LCB0byBtYWtlIHN1cmUgdGhhdCB5b3UgY2Fu
IHN0YXJ0IGRlY29kaW5nIHRoZSBzdWJzdHJlYW0NCj4gd2l0aCBUVElEPTAgYW5kIFRMSUQ9Mi4g
KEZvciBtb3N0IHNjYWxhYmlsaXR5IHN0cnVjdHVyZXMgdGhpcyB3b3VsZCBtZWFuDQo+IHVwZGF0
aW5nIGJvdGgsIGJ1dCBleG90aWMgc3RydWN0dXJlcyBhcmUgcG9zc2libGUuKQ0KPiANCj4gSWYg
eW91IHdhbnQgdG8ganVzdCB1cGRhdGUgb25lIHBhcnQgb2YgdGhlIHN0cmVhbSwgdGhhdOKAmXMg
d2hhdCBDVElEIGFuZCBDTElEDQo+IGFyZSBmb3IuICBJZiB5b3Ugc2VudCBUVElEPTAgYW5kIFRM
SUQ9MiwgYWNjb21wYW5pZWQgYnkgQ1RJRD0wIGFuZCBDTElEPTAsDQo+IHRoYXQgbWVhbnMgdGhh
dCB5b3UgYWxyZWFkeSBoYXZlIFRJRCAwLCBhbmQgeW91IGp1c3Qgd2FudCB0byBpbmNyZWFzZSB0
aGUNCj4gTElELg0KPiANCj4gVGhlIGN1cnJlbnQgdGV4dCBpcyBhdCBodHRwczovL2dpdGh1Yi5j
b20vanViZXJ0aS9kcmF1Z2h0cy90cmVlL21hc3Rlci9scnIgLA0KPiBpZiB5b3Ugd2FudCB0byB0
YWtlIGEgbG9vayBhdCB0aGUgbGF0ZXN0IHJldmlzaW9ucywgb3Igc3VnZ2VzdCB0ZXh0IHRoYXQg
eW91DQo+IHRoaW5rIHdvdWxkIG1ha2UgaXQgY2xlYW5lci4NCj4gDQo+IA0KPiA+IFJvbmkNCj4g
Pg0KPiA+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+PiBGcm9tOiBHZW4tYXJ0IFtt
YWlsdG86Z2VuLWFydC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgSm9uYXRoYW4NCj4g
Pj4gTGVubm94DQo+ID4+IFNlbnQ6INeZ15XXnSDXkyAwNyDXmdeV16DXmSAyMDE3IDAwOjMwDQo+
ID4+IFRvOiBSb25pIEV2ZW4NCj4gPj4gQ2M6IGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci5hbGxAaWV0
Zi5vcmc7IEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbTsNCj4gPj4gYXZ0ZXh0QGlldGYub3JnOyBp
ZXRmQGlldGYub3JnDQo+ID4+IFN1YmplY3Q6IFJlOiBbR2VuLWFydF0gR2VuYXJ0IGxhc3QgY2Fs
bCByZXZpZXcgb2YNCj4gPj4gZHJhZnQtaWV0Zi1hdnRleHQtbHJyLTA1DQo+ID4+DQo+ID4+IEhp
LCBSb25pIOKAlCB0aGFua3MgZm9yIHlvdXIgcmV2aWV3LiAgUmVzcG9uc2VzIGlubGluZS4NCj4g
Pj4NCj4gPj4+IE9uIEp1biAxLCAyMDE3LCBhdCAyOjUzIEFNLCBSb25pIEV2ZW4gPHJvbi5ldmVu
LnRsdkBnbWFpbC5jb20+IHdyb3RlOg0KPiA+Pj4NCj4gPj4+IFJldmlld2VyOiBSb25pIEV2ZW4N
Cj4gPj4+IFJldmlldyByZXN1bHQ6IFJlYWR5IHdpdGggSXNzdWVzDQo+ID4+Pg0KPiA+Pj4gSSBh
bSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVy
YWwgQXJlYQ0KPiA+Pj4gUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9j
dW1lbnRzIGJlaW5nIHByb2Nlc3NlZCBieQ0KPiA+Pj4gdGhlIElFU0cgZm9yIHRoZSBJRVRGIENo
YWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZQ0KPiA+Pj4gYW55IG90
aGVyIGxhc3QgY2FsbCBjb21tZW50cy4NCj4gPj4+DQo+ID4+PiBGb3IgbW9yZSBpbmZvcm1hdGlv
biwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQo+ID4+Pg0KPiA+Pj4gPGh0dHBzOi8vdHJhYy5pZXRm
Lm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQo+ID4+Pg0KPiA+Pj4gRG9jdW1lbnQ6IGRy
YWZ0LWlldGYtYXZ0ZXh0LWxyci0/Pw0KPiA+Pj4gUmV2aWV3ZXI6IFJvbmkgRXZlbg0KPiA+Pj4g
UmV2aWV3IERhdGU6IDIwMTctMDUtMzENCj4gPj4+IElFVEYgTEMgRW5kIERhdGU6IDIwMTctMDYt
MDgNCj4gPj4+IElFU0cgVGVsZWNoYXQgZGF0ZTogTm90IHNjaGVkdWxlZCBmb3IgYSB0ZWxlY2hh
dA0KPiA+Pj4NCj4gPj4+IFN1bW1hcnk6DQo+ID4+PiBUaGUgZG9jdW1lbnQgaXMgcmVhZHkgd2l0
aCBpc3N1ZXMgZm9yIGEgc3RhbmRhcmQgdHJhY2sgUkZDIE1ham9yDQo+ID4+PiBpc3N1ZXM6DQo+
ID4+Pg0KPiA+Pj4gTWlub3IgaXNzdWVzOg0KPiA+Pj4NCj4gPj4+IDEuIENhbiB5b3Ugc3BlY2lm
eSBib3RoIFRUSUQgYW5kIFRMSUQgaW4gdGhlIHNhbWUgRkNJLg0KPiA+Pg0KPiA+PiBTeW50YWN0
aWNhbGx5LCB0aGV5IG11c3QgYm90aCBvY2N1ci4NCj4gPj4NCj4gPj4gSWYgeW91IG1lYW4gY2Fu
IHlvdSByZXF1ZXN0IGFuIHVwZ3JhZGUgaW4gYm90aCBhdCBvbmNlLCB5ZXM7IEnigJl2ZQ0KPiA+
PiBhZGRlZCB0ZXh0IHRvIGNsYXJpZnkgdGhpcy4NCj4gPj4NCj4gPj4+IDIuIFdoYXQgaXMgdGhl
IG1lYW5pbmcgb2YgdmFsdWUgMCBmb3IgVFRJRCBhbmQgVExJRCAtIFRJRCBvciBMSUQgPTANCj4g
Pj4+IGluIGZyYW1lIG1hcmtpbmcgZHJhZnQgbWVhbnMgYmFzZSBsYXllciBpZiB0aGVyZSBpcyBz
Y2FsYWJpbGl0eS4NCj4gPj4+ICAgIFRoaXMgcmVsYXRlcyB0byB0aGUgcHJldmlvdXMgcXVlc3Rp
b24uDQo+ID4+DQo+ID4+IEnigJltIG5vdCBzdXJlIEkgdW5kZXJzdGFuZCB0aGlzIHF1ZXN0aW9u
Lg0KPiA+Pg0KPiA+PiBJ4oCZdmUgYWRkZWQgdGV4dCB0aGF0IGlmIEM9MSwgYXQgbGVhc3Qgb25l
IG9mIDxUVElELCBUTElEPiBNVVNUIGJlDQo+ID4+IGdyZWF0ZXIgdGhhbiA8Q1RJRCwgQ0xJRD4s
IGFuZCBib3RoIE1VU1QgYmUgZ3JlYXRlciB0aGFuIG9yIGVxdWFsIHRvDQo+ID4+IHRoZWlyIGNv
dW50ZXJwYXJ0LCBzbyB0aGUgTFJSIGlzIGFjdHVhbGx5IHJlcXVlc3RpbmcgYSBsYXllciB1cGdy
YWRlLg0KPiA+PiBJcyB0aGF0IHdoYXQgeW91IHdlcmUgYXNraW5nIGFib3V0Pw0KPiA+Pg0KPiA+
Pj4gMy4gIFdoYXQgd291bGQgYW4gRkNJIHdpdGggYm90aCBUVElEIGFuZCBUTElEIGVxdWFsIDAg
bWVhbi4NCj4gPj4NCj4gPj4gSXQgbWVhbnMgeW91IHdhbnQgYSByZWZyZXNoIG9mIHRoZSBiYXNl
IHRlbXBvcmFsL3NwYXRpYWwgbGF5ZXIsIG9ubHkuDQo+ID4+DQo+ID4+PiBOaXRzL2VkaXRvcmlh
bCBjb21tZW50czoNCj4gPj4+DQo+ID4+PiAxLiBTZWN0aW9uIDMgImFuIFJlYWwtVGltZSBUcmFu
c3BvcnQgQ29udHJvbCBQcm90b2NvbCIgc2hvdWxkIGJlICJhDQo+ID4+PiBSZWFs4oCmIi4NCj4g
Pj4NCj4gPj4gQ29saW4gcG9pbnRlZCBvdXQgdGhhdCBpdCBzaG91bGQgc2F5IOKAnGFuIFJUUCBD
b250cm9sIFByb3RvY29s4oCdIGFueXdheS4NCj4gPj4NCj4gPj4+IDIuIEluIHNlY3Rpb24gMyAi
IFtSRkM1MTA0XShTZWN0aW9uIDMuNS4xKSIgdGhlcmUgaXMgYSBsaW5rIHRvDQo+ID4+PiBzZWN0
aW9uDQo+ID4+PiAzLjUuMSBidXQgaXQgZG9lcyBub3Qgd29yay4NCj4gPj4NCj4gPj4geG1sMnJm
YyBkb2VzbuKAmXQgaGF2ZSBhbnkgd2F5IHRvIGxpbmsgdG8gc2VjdGlvbnMgb2Ygb3RoZXIgZG9j
dW1lbnRzLA0KPiA+PiBzbyB0aGUg4oCcKFNlY3Rpb24gMy41LjEp4oCdIHBhcnQgaXMganVzdCBh
IGNvbW1lbnQuDQo+ID4+DQo+ID4+IEkgdGhpbmsgdGhlIGludGVybmV0LWRyYWZ0IHRvb2xpbmcg
bWF5IGhhdmUgdGhvdWdodCBJIHdhcyB0cnlpbmcgdG8NCj4gPj4gbGluayB0byBhIG5vbi1leGlz
dGVudCBzZWN0aW9uIDMuNS4xIG9mIHRoaXMgZG9jdW1lbnQsIGJ1dCB0aGF04oCZcyBvdXRzaWRl
DQo+IG15IGNvbnRyb2wuDQo+ID4+DQo+ID4+PiAzLiBJbiBzZWN0aW9uIDMuMiAiKHNlZSBzZWN0
aW9uIFNlY3Rpb24gMi4xKSIgc2VjdGlvbiBhcHBlYXJzIHR3aWNlLg0KPiA+Pg0KPiA+PiBGaXhl
ZC4NCj4gPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18N
Cj4gPj4gR2VuLWFydCBtYWlsaW5nIGxpc3QNCj4gPj4gR2VuLWFydEBpZXRmLm9yZw0KPiA+PiBo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dlbi1hcnQNCg0K


From nobody Mon Jun 12 06:29:23 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 1BC851273B1 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 06:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7AoQXTv5Qp3R for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 06:29:21 -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 E2F3F126D05 for <ietf@ietf.org>; Mon, 12 Jun 2017 06:29:20 -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 1dKPP6-0004cc-FI; Mon, 12 Jun 2017 13:29:12 +0000
Date: Mon, 12 Jun 2017 20:29:09 +0700
Message-ID: <m2k24hfi6y.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: "John Levine" <johnl@taugh.com>, ietf@ietf.org
Subject: Re: wireless geolocation
In-Reply-To: <27214.1497026980@dooku.sandelman.ca>
References: <20170609153114.9827.qmail@ary.lan> <27214.1497026980@dooku.sandelman.ca>
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/VpxHY1q-or8UbqVDEAU9GMSujYE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 13:29:22 -0000

>> Would it be useful to document the various ways the meeting network
>> gets geolocated so at least we have a reference for what's broken?
>
>> I'm thinking of an info RFC.
> 
> I think so.
>     "A survey of failure cases for IP and BSSID based geolocation"

thanks for volunteering, guys

randy


From nobody Mon Jun 12 06:52:14 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9832C1286B1; Mon, 12 Jun 2017 06:52:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 tcaiWkY04qyb; Mon, 12 Jun 2017 06:52:03 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4: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 BDF66126D05; Mon, 12 Jun 2017 06:52:02 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 00E9A280589; Mon, 12 Jun 2017 15:52:01 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id EF3CA280651; Mon, 12 Jun 2017 15:52:00 +0200 (CEST)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id E8655280589; Mon, 12 Jun 2017 15:52:00 +0200 (CEST)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id E516D6000082; Mon, 12 Jun 2017 15:52:00 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id D673140E20; Mon, 12 Jun 2017 15:52:00 +0200 (CEST)
Date: Mon, 12 Jun 2017 15:52:00 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: ietf@ietf.org
Cc: dnsop@ietf.org
Subject: Re: Last Call: <draft-ietf-dnsop-sutld-ps-05.txt> (Special-Use Domain Names Problem Statement) to Informational RFC
Message-ID: <20170612135200.ya3tivlhg2dhe3ry@nic.fr>
References: <149678027581.3850.9197039878287017082.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <149678027581.3850.9197039878287017082.idtracker@ietfa.amsl.com>
X-Operating-System: Debian GNU/Linux 9.0
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000001, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.6.12.134516
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DQ7YKGOBKM35Er-admJa_qhmVYE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 13:52:07 -0000

On Tue, Jun 06, 2017 at 01:17:55PM -0700,
 The IESG <iesg-secretary@ietf.org> wrote 
 a message of 42 lines which said:

> The IESG has received a request from the Domain Name System
> Operations WG (dnsop) to consider the following document: -
> 'Special-Use Domain Names Problem Statement'
> <draft-ietf-dnsop-sutld-ps-05.txt> as Informational RFC

For an issue which is quite contentious and sensitive, I think there
are some points in the document that deserve a change.

Biggest point: the IESG decided to freeze the RFC 6761 process
<https://www.ietf.org/blog/2015/09/onion/> I regret this decision (RFC
6761 is still in force, it has not been deprecated or updated) and,
unfortunately, registration of new Special-Use Domain Names is now
impossible (pending an action on RFC 6761 that will probably never
come). So, de facto, a regular process has been shut down, leaving the
IETF without a possibility to register these domain names.

Now, on the draft:

* Section 3 says "No formal coordination process exists between the
IETF and ICANN" This is not true, there is a formal liaison
<https://www.ietf.org/liaison/managers.html> and it is even mentioned
laster, in section 4.1.4. This issue was mentioned during the WGLC
<https://mailarchive.ietf.org/arch/msg/dnsop/OWt8DkBJ_JpIITF-R2YpwEhiwFs>

* Section 3 says "Use of the registry is inconsistent -- some
Special-Use Domain Name RFCs specify registry entries, some don't;
some specify delegation, some don't." There is no inconsistency
here. RFC 6761 says (in its section 5) that the reservation of a
Special-Use Domain Name is free to choose the rules regarding
resolution, as long as they are properly explained.

* Section 4.2.2 says "the fact of its unilateral use by The Tor
Project without following the RFC 6761 process" The onion TLD was in
use in Tor since 2004, nine years before the publication of RFC
6761. It is grossly unfair to reproach not following an unpublished
RFC. It was mentioned a long time ago
<https://mailarchive.ietf.org/arch/msg/dnsop/nr4ECaVw6PT09o2xdM3jrKllHBI>

* Section 4.2.3 says "But it shares the problem that such names cannot
be assumed either to be unique or to be functional in all contexts for
all Internet-connected hosts." Unfortunately, because of the wide use
of censorship through lying DNS resolvers, this problem is now part of
our daily life. It would be nice if a name had the same global
signification, but it is no longer true.




From nobody Mon Jun 12 07:06:14 2017
Return-Path: <brian@innovationslab.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 5111C12EB01 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 07:05: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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ys-90pV689LK for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 07:05:55 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B3CE12EAF7 for <ietf@ietf.org>; Mon, 12 Jun 2017 07:05:55 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id EF7A5880E4 for <ietf@ietf.org>; Mon, 12 Jun 2017 07:05:54 -0700 (PDT)
Received: from clemson.local (swifi-nat.jhuapl.edu [128.244.87.133]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id BA9953280AE4 for <ietf@ietf.org>; Mon, 12 Jun 2017 07:05:54 -0700 (PDT)
Subject: Re: IAD Retirement
To: ietf@ietf.org
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <4f05ad54-e1f6-c6d1-6d2d-2ed3e0ad2fab@innovationslab.net>
Date: Mon, 12 Jun 2017 10:05:53 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="ATtknpClPbM9C7pxfTR0NBGdwupjaFE7t"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7oZzpC9OZyO07F4AdEs5XIzp-kQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 14:05:56 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--ATtknpClPbM9C7pxfTR0NBGdwupjaFE7t
Content-Type: multipart/mixed; boundary="XxluMWAHvfIO5cJBXCvwcoofKmdcGsklL";
 protected-headers="v1"
From: Brian Haberman <brian@innovationslab.net>
To: ietf@ietf.org
Message-ID: <4f05ad54-e1f6-c6d1-6d2d-2ed3e0ad2fab@innovationslab.net>
Subject: Re: IAD Retirement
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
In-Reply-To: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>

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

Hi Ray,
     Will be sad to see you go! Is this a permanent retirement or are
you moving on to other things?

Brian

On 6/12/17 9:31 AM, IETF Administrative Director wrote:
> All,
>=20
> I will be retiring from the position of IETF Administrative Director
> on 31 October 2017.
>=20
> On 1 June I concluded 12 years as IAD, member of the IAOC and
> trustee of the IETF Trust.
>=20
> I accepted this position because I believed in the mission of the
> IETF and its importance to people worldwide. It has been an honor
> and a privilege to have supported the IETF in this capacity.
>=20
> Thanks for your patience, feedback, and support.
>=20
> Best
> Ray
>=20


--XxluMWAHvfIO5cJBXCvwcoofKmdcGsklL--

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

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

iQEcBAEBCAAGBQJZPp/BAAoJEBOZRqCi7goqFgcH/2G/DpnTnfOPeDfnZ0w+vgTz
u1PjCIF3/tfaMO/THQk+gfNM05cG3QfyGbwO5RYmCE24lQIYISejsOSYUVmG1rLs
ZrQh9t2LD9GF5eT14NAuZakH6gGM0223QpRNE4YJyXAci+0Siqgq1CpVv8YG7G6g
WLdZvnyWALg09qBY2zcpE88qOeVsuSGNumLHoQmGgKtQqZGs4+bNJk4tk+rY0gb+
zB13JG0/wOcm/Idwt1DVVKQBHLGpAsZqbmNrVX9sQ46UoVO2d74vRGEGuW38XxB8
E4AtGiZB/tioCokczAwIabebb8UVi9Ya8Z1XkZScicZFe8IWlgtXMI5WK5L1A3k=
=1GDp
-----END PGP SIGNATURE-----

--ATtknpClPbM9C7pxfTR0NBGdwupjaFE7t--


From nobody Mon Jun 12 07:42:37 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED05F129526 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 07:42:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YXL4YcqzvBbe for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 07:42:33 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 846C11289B5 for <ietf@ietf.org>; Mon, 12 Jun 2017 07:42:33 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id u12so128163445qth.0 for <ietf@ietf.org>; Mon, 12 Jun 2017 07:42:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=iI2EgHe2vxd3I6Q7t3vjWXpCdMS0MUG0+jUTZj9M3JQ=; b=aM0Zkzlz4L3ZuCRxJBqUNcttj8yts7WeUGAu+H76THImdJgxljyRXKHWpJheEaI765 irhNiDftvBJY8hLsrnQy2XhvGTVgVQvliJ0mOfL9eEL8lMDSHUBjkOucI6spm/max0ve 5NUoQzDayrGEgTd97kZuXhcBb3upfx5gXT4A65CXATkKqlfTaN8WyPcxMxW4h+dMREk9 lf+c6JLsFeGbtgm9vciCEAutf9rCYXLQtVY/g739yRMN0CzRgp3+TDFcwc7MydKoxTAr rLQY2ZKiYNW7ikPcXgKR2KSvKsJisf82ZJhr70K4ih3b4mVd5FWMooCREWCJGJ4Tmv8Y QJOQ==
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=iI2EgHe2vxd3I6Q7t3vjWXpCdMS0MUG0+jUTZj9M3JQ=; b=FcVqHSaUHh8Sx3qiczQVJ+QxPUXe3EMwgm71szt5Z+4qsx/VG4A0tnGBGm55PGI0we +Viq7cp8wG81D4H6oKb2pXAhDxyT6TpG6PxosMjr0Ky5iUCUO62UkqW7J1GMlgkSeKVg mjLW47RveTeBL4n5gXoejIJs8tD8NlqeF0OaUgsQsWdGCrrpPybLDc/4ZlsMGD2IQIu0 bVWYA7TSE7oMOHOWi8A/90X5HqEb+GZ0kwwNoP72J/XbEcEk8scPKmgZlONj7G+IxD7P rh3mchwhHsKkC96//VwMHJcJktBwbYxUqxInh7bhawOGbAY896xMKNr3lmDS1ur19fMb ufqA==
X-Gm-Message-State: AODbwcCctq6WhDpfMOym4FwL+mBqLIsNGx6Pz1TAffPXZWmqSeT0jDOs 6Fb5fMr0pWBZekSH
X-Received: by 10.237.47.39 with SMTP id l36mr52736358qtd.44.1497278552543; Mon, 12 Jun 2017 07:42:32 -0700 (PDT)
Received: from [10.0.30.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id x78sm6731154qkb.44.2017.06.12.07.42.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Jun 2017 07:42:31 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-sutld-ps-05.txt> (Special-Use Domain Names Problem Statement) to Informational RFC
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <20170612135200.ya3tivlhg2dhe3ry@nic.fr>
Date: Mon, 12 Jun 2017 10:42:30 -0400
Cc: ietf <ietf@ietf.org>, dnsop@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9619F7EF-668D-4275-9AB9-E4565D04C085@fugue.com>
References: <149678027581.3850.9197039878287017082.idtracker@ietfa.amsl.com> <20170612135200.ya3tivlhg2dhe3ry@nic.fr>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VTxPJ3gT8ZBaIxsaLNkU7eYDsQU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 14:42:36 -0000

On Jun 12, 2017, at 9:52 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:
> Biggest point: the IESG decided to freeze the RFC 6761 process
> <https://www.ietf.org/blog/2015/09/onion/> I regret this decision (RFC
> 6761 is still in force, it has not been deprecated or updated) and,
> unfortunately, registration of new Special-Use Domain Names is now
> impossible (pending an action on RFC 6761 that will probably never
> come). So, de facto, a regular process has been shut down, leaving the
> IETF without a possibility to register these domain names.

The point of publishing this document is to get a step closer to fixing =
this problem.

> Now, on the draft:
>=20
> * Section 3 says "No formal coordination process exists between the
> IETF and ICANN" This is not true, there is a formal liaison
> <https://www.ietf.org/liaison/managers.html> and it is even mentioned
> laster, in section 4.1.4. This issue was mentioned during the WGLC
> =
<https://mailarchive.ietf.org/arch/msg/dnsop/OWt8DkBJ_JpIITF-R2YpwEhiwFs>

What is meant here is not that the IETF and ICANN don't communicate, but =
rather that the IETF doesn't have a formal process for saying to ICANN, =
specifically, "don't use this name."   It's all informal.   It is done =
through the liaison, it's true, but there's no set of instructions to =
follow which, having been followed, we can point to and say "we followed =
the process."

We could replace the first sentence as follows: "Although the IETF and =
ICANN do have a liaison relationship through which special-use =
allocations can be discussed, there exists no formal process for =
coordinating these allocations."

Would that work?

> * Section 3 says "Use of the registry is inconsistent -- some
> Special-Use Domain Name RFCs specify registry entries, some don't;
> some specify delegation, some don't." There is no inconsistency
> here. RFC 6761 says (in its section 5) that the reservation of a
> Special-Use Domain Name is free to choose the rules regarding
> resolution, as long as they are properly explained.

The point here is not that every name should be treated the same, but =
that every RFC that does a 6761 allocation should specify how/whether =
the name is delegated every 6761 allocation should be added to the =
special-use names registry.

How about the following change:

   o  Use of the registry is inconsistent -- some Special-Use Domain
      Name RFCs specifically add registry entries, some don't; some =
specify
      how and whether special-use name delegations should be done,=20
      some don't.

> * Section 4.2.2 says "the fact of its unilateral use by The Tor
> Project without following the RFC 6761 process" The onion TLD was in
> use in Tor since 2004, nine years before the publication of RFC
> 6761. It is grossly unfair to reproach not following an unpublished
> RFC. It was mentioned a long time ago
> =
<https://mailarchive.ietf.org/arch/msg/dnsop/nr4ECaVw6PT09o2xdM3jrKllHBI>

This was not intended as a reproach, but I see why you read it that way. =
  How about this:

      The situation was somewhat forced, both by the fact of its
      unilateral use by The Tor Project before the RFC 6761
      process became available,

> * Section 4.2.3 says "But it shares the problem that such names cannot
> be assumed either to be unique or to be functional in all contexts for
> all Internet-connected hosts." Unfortunately, because of the wide use
> of censorship through lying DNS resolvers, this problem is now part of
> our daily life. It would be nice if a name had the same global
> signification, but it is no longer true.

Andrew McConachie brought up the same issue.   Unfortunately I think =
this is out of scope for this document, but several people have =
expressed interest in formally documenting this issue=E2=80=94I think =
Andrew Sullivan expressed a similar sentiment at the mic in Chicago.   =
You might want to discuss this with them and see if there's work to do.


From nobody Mon Jun 12 08:00:42 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 7B41012EB2B for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.419
X-Spam-Level: 
X-Spam-Status: No, score=-1.419 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5] 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 CLMwNWdm9PSg for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:00:38 -0700 (PDT)
Received: from mail-lf0-f54.google.com (mail-lf0-f54.google.com [209.85.215.54]) (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 29645127078 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:00:37 -0700 (PDT)
Received: by mail-lf0-f54.google.com with SMTP id v20so52414948lfa.1 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:00:37 -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=pkeKeP/Pix+rN9UQd7pdxJidKhjWTuh1mc9XiI+F0qM=; b=ORz4QMhRUxA4MLz51OsNIkJiG1WfF8plUHzg6buALw3Vr6I3wRBAl7e9GquN9G5npC VRd2BDm6p4X+w+Z1r2L5eyR8t0ZcBMFpnvdvDSlqJNsogS91bmAmlZCXy6Dar/FXB074 PgFTB1wM4sPpaGbCQtwNcXnkhuIKdZR+qFxT/kh0j9txXlz8wiQeP87uKKqr/J45nYf7 KNcuBTwyY5MD0Ei3D4MxlIi3ceEv+zpuIdU7fGeYxHAIbAaEUaPnABvkXvZAiKusld1+ AEZNalM+/zSSUZJuZmBrHTMd43JXJCzFoaa0mu+yaJWdnNDPj4p8e+Zgf3kb3D9B0u3C NajA==
X-Gm-Message-State: AODbwcCaPWGEDTf0kJxT8lJKcJTzFb1I8lfzXir/xlzI8Lc88l9YWl3A jpzVH+Be/GyX0pLbNhi3MQ==
X-Received: by 10.80.144.40 with SMTP id b37mr32105838eda.36.1497279636118; Mon, 12 Jun 2017 08:00:36 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:b984:270f:516c:29c8]) by smtp.gmail.com with ESMTPSA id e31sm5260449eda.15.2017.06.12.08.00.35 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Jun 2017 08:00:35 -0700 (PDT)
Date: Mon, 12 Jun 2017 17:00:34 +0200
From: Job Snijders <job@ntt.net>
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
Cc: ietf@ietf.org, dnsop@ietf.org
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-sutld-ps-05.txt> (Special-Use Domain Names Problem Statement) to Informational RFC
Message-ID: <20170612150034.f4etrpuhbnvbzpzz@hanna.meerval.net>
References: <149678027581.3850.9197039878287017082.idtracker@ietfa.amsl.com> <20170612135200.ya3tivlhg2dhe3ry@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170612135200.ya3tivlhg2dhe3ry@nic.fr>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170428 (1.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Yqw3FBBeCStCL-8E5NzXMm6UVw4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 15:00:41 -0000

On Mon, Jun 12, 2017 at 03:52:00PM +0200, Stephane Bortzmeyer wrote:
> On Tue, Jun 06, 2017 at 01:17:55PM -0700,
>  The IESG <iesg-secretary@ietf.org> wrote 
>  a message of 42 lines which said:
> 
> > The IESG has received a request from the Domain Name System
> > Operations WG (dnsop) to consider the following document: -
> > 'Special-Use Domain Names Problem Statement'
> > <draft-ietf-dnsop-sutld-ps-05.txt> as Informational RFC
> 
> For an issue which is quite contentious and sensitive, I think there
> are some points in the document that deserve a change.
> 
> Biggest point: the IESG decided to freeze the RFC 6761 process
> <https://www.ietf.org/blog/2015/09/onion/> I regret this decision (RFC
> 6761 is still in force, it has not been deprecated or updated) and,
> unfortunately, registration of new Special-Use Domain Names is now
> impossible (pending an action on RFC 6761 that will probably never
> come). So, de facto, a regular process has been shut down, leaving the
> IETF without a possibility to register these domain names.
> 
> 
> * Section 4.2.2 says "the fact of its unilateral use by The Tor
> Project without following the RFC 6761 process" The onion TLD was in
> use in Tor since 2004, nine years before the publication of RFC
> 6761. It is grossly unfair to reproach not following an unpublished
> RFC. It was mentioned a long time ago
> <https://mailarchive.ietf.org/arch/msg/dnsop/nr4ECaVw6PT09o2xdM3jrKllHBI>

----

OLD:
   The situation was somewhat forced, both by the fact of its unilateral
   use by The Tor Project without following the RFC 6761 process, and
   because a deadline had been set by the CA/Browser Forum
   [SDO-CABF-INT] after which all .onion PKI certificates would expire
   and no new certificates would be issued, unless the .onion
   Special-Use Top-Level Domain Name were to be recognized by the IETF.

NEW:
   The situation was somewhat forced, both by the fact that use of the
   .onion domain name by the Tor Project predates the process described
   in RFC 6761 by 9 years, and because a deadline [CABF-DEADLINE] had
   been set by the CA/Browser Forum [CABF] after which all PKI
   certificates for internal names would expire and no new certificates
   would be issued. At the time .onion was considered an internal name.
   IETF recognition of the .onion as a Special-Use Top-Level Domain Name
   facilitated the development of a certificate issuance process
   specific to .onion domain names [CABF-BALLOT144]. 

[CABF-DEADLINE] should link to https://www.digicert.com/internal-names.htm
[CABF] should link to https://cabforum.org/
[CABF-BALLOT144] should link to https://cabforum.org/2015/02/18/ballot-144-validation-rules-dot-onion-names/

----

I wasn't there, but reading ballot-144, some cabforum mails, and 
https://blog.torproject.org/blog/landmark-hidden-services-onion-names-reserved-ietf
it appears to me that all parties involved were actively trying to fix a
long standing broken situation.

Kind regards,

Job


From nobody Mon Jun 12 08:02: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 78C43126FB3 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:02:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.9
X-Spam-Level: 
X-Spam-Status: No, score=-2.9 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, 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 nhoxVg08tj1l for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:02:08 -0700 (PDT)
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.172]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id D2A82126C83 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:02:07 -0700 (PDT)
From: IETF Chair <chair@ietf.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: New blog posts
Message-Id: <4CDA6D0D-AAF0-4E12-8C56-4387A739BDF5@ietf.org>
Date: Mon, 12 Jun 2017 11:02:05 -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/WGauAAdy9zZqUcPK_8ghMJ4LRrE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 15:02:09 -0000

There are two new posts up on the blog today that I wanted to draw your =
attention to:

New Work at Upcoming IETF 99 Meeting: =
https://www.ietf.org/blog/2017/06/new-work-at-upcoming-ietf-99-meeting/

Working Together with 3GPP on 5G: =
https://www.ietf.org/blog/2017/06/working-together-with-3gpp-on-5g/

Feedback is welcome as always.
Alissa=


From nobody Mon Jun 12 08:06:22 2017
Return-Path: <iad@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 713A91242EA; Mon, 12 Jun 2017 06:31:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Administrative Director <iad@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Subject: IAD Retirement
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
Date: Mon, 12 Jun 2017 06:31:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/jl48b8zqu93t_LkimAzMQATy3Nc>
X-Mailman-Approved-At: Mon, 12 Jun 2017 08:06:22 -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: Mon, 12 Jun 2017 13:31:16 -0000

All,

I will be retiring from the position of IETF Administrative Director
on 31 October 2017.

On 1 June I concluded 12 years as IAD, member of the IAOC and
trustee of the IETF Trust.

I accepted this position because I believed in the mission of the
IETF and its importance to people worldwide. It has been an honor
and a privilege to have supported the IETF in this capacity.

Thanks for your patience, feedback, and support.

Best
Ray


From nobody Mon Jun 12 08:06:47 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 2B97F129490; Sun, 11 Jun 2017 18:41:14 -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 Second Call for Volunteers
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149723167407.10222.17231325070344745586.idtracker@ietfa.amsl.com>
Date: Sun, 11 Jun 2017 18:41:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/00TVcyqSDPRTeaEx_grjFkJW2yU>
X-Mailman-Approved-At: Mon, 12 Jun 2017 08:06:45 -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: Mon, 12 Jun 2017 01:41:14 -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.

Some 201 people have already volunteered by ticking the box on the IETF 96 through 98 registration forms. I will contact all of these volunteers 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)
    Adam Roach (ART)
 

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 Mon Jun 12 08:08:28 2017
Return-Path: <volz@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 164ED12EB2D for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:08:27 -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 Ko1H1uS6GLuT for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:08:25 -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 8739D12EAE4 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:08:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1150; q=dns/txt; s=iport; t=1497280104; x=1498489704; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=SV1+mtcFT9KEGsAAogt9byhQEepG/t2TwV76CLeZmXg=; b=QyItQgzqby5cX3VsjQjFm2MIFuhhBCl0AnZzXxxj/vI9ZzFL4qvSYGHF W6U0/Dy6VRRRPqeqbVysykoYS+rtFuCjIFZA5jlZ3GoWDDqmpmYRiqwH4 sm65R7VF6blkq0LuLdsSr2OB382KndRAH2JoCNpM8L3psKwrGC/pU7Iu+ M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DTAAA8rj5Z/49dJa1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBg1iBbweDbYoYkW6WA4IRhiQCGoJWPxgBAgEBAQEBAQFrHQuFGAEBAQE?= =?us-ascii?q?DIxFRBAIBCBEEAQEDAiMDAgICMBQBCAgCBBMIiiSwDIImi2QBAQEBAQEBAQIBA?= =?us-ascii?q?QEBAQEBASCBC4c2gyCHfIJhBZ4/ApM+kg+UawEfOIEKdBVIhw52iFGBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.39,333,1493683200"; d="scan'208";a="254637730"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 12 Jun 2017 15:07:56 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v5CF7uwR010030 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Mon, 12 Jun 2017 15:07:56 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 12 Jun 2017 10:07:55 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Mon, 12 Jun 2017 10:07:55 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: IAD Retirement
Thread-Topic: IAD Retirement
Thread-Index: AQHS44AqpXzVlhNdIE+a8eIW96txZ6IhVACA
Date: Mon, 12 Jun 2017 15:07:55 +0000
Message-ID: <3a9dbc93332d4b799c44909c68e469ec@XCH-ALN-003.cisco.com>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
In-Reply-To: <149727427537.10333.7649103852167051395.idtracker@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.98.1.197]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/R2VhwV4T4FPIlmQBOgyrns4ReRs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 15:08:27 -0000

SGk6DQoNClRoYW5rcyBmb3IgeW91ciBlZmZvcnRzIGFuZCBiZWxpZWYgaW4gdGhlIElFVEYhIFdp
bGwgYmUgc2FkIHRvIHNlZSB5b3UgZ28hDQoNCkJlc3Qgb2YgbHVjayB3aXRoIHdoYXRldmVyIGlz
IG5leHQgZm9yIHlvdSENCg0KLSBCZXJuaWUNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0N
CkZyb206IFdHQ2hhaXJzIFttYWlsdG86d2djaGFpcnMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVo
YWxmIE9mIElFVEYgQWRtaW5pc3RyYXRpdmUgRGlyZWN0b3INClNlbnQ6IE1vbmRheSwgSnVuZSAx
MiwgMjAxNyA5OjMxIEFNDQpUbzogSUVURiBBbm5vdW5jZW1lbnQgTGlzdCA8aWV0Zi1hbm5vdW5j
ZUBpZXRmLm9yZz4NClN1YmplY3Q6IElBRCBSZXRpcmVtZW50DQoNCkFsbCwNCg0KSSB3aWxsIGJl
IHJldGlyaW5nIGZyb20gdGhlIHBvc2l0aW9uIG9mIElFVEYgQWRtaW5pc3RyYXRpdmUgRGlyZWN0
b3INCm9uIDMxIE9jdG9iZXIgMjAxNy4NCg0KT24gMSBKdW5lIEkgY29uY2x1ZGVkIDEyIHllYXJz
IGFzIElBRCwgbWVtYmVyIG9mIHRoZSBJQU9DIGFuZA0KdHJ1c3RlZSBvZiB0aGUgSUVURiBUcnVz
dC4NCg0KSSBhY2NlcHRlZCB0aGlzIHBvc2l0aW9uIGJlY2F1c2UgSSBiZWxpZXZlZCBpbiB0aGUg
bWlzc2lvbiBvZiB0aGUNCklFVEYgYW5kIGl0cyBpbXBvcnRhbmNlIHRvIHBlb3BsZSB3b3JsZHdp
ZGUuIEl0IGhhcyBiZWVuIGFuIGhvbm9yDQphbmQgYSBwcml2aWxlZ2UgdG8gaGF2ZSBzdXBwb3J0
ZWQgdGhlIElFVEYgaW4gdGhpcyBjYXBhY2l0eS4NCg0KVGhhbmtzIGZvciB5b3VyIHBhdGllbmNl
LCBmZWVkYmFjaywgYW5kIHN1cHBvcnQuDQoNCkJlc3QNClJheQ0KDQo=


From nobody Mon Jun 12 08:10:48 2017
Return-Path: <sarikaya2012@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 E173D127078 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:10:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1i0HSXaIvNdY for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:10:45 -0700 (PDT)
Received: from mail-wr0-x232.google.com (mail-wr0-x232.google.com [IPv6:2a00:1450:400c:c0c::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7CA00129411 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:10:45 -0700 (PDT)
Received: by mail-wr0-x232.google.com with SMTP id v104so99523205wrb.0 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:10:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to:cc; bh=NhDNMuC1H0eSoN/WajoiNNeKjoLyrOlD6bUc5/h96GA=; b=riHo9cEDS2evpMsusFAMEzmwbSYNO2WQpj8X3tv9w7MXO0TLiILk+xtecpcYjN3YfB RAT59DIuxV549dWAjg2u7IVr6mXkSTFeJndpq2kgve5wptVMMtAH50IfbNEc7v0+tdQQ w4j113joFt+RqCsDkPEAEHUN51jW4Pj8dGnxMXR+f0Vw4XrHljKrZ7IQvUKhe4+2OOWY 04GhH8crSewXDxhc8mbSNLr5C2UpYtA8NxhoPIMSbhjMJTtd7NgFBx/srY5FzLIMUvE9 jw7hSb31aw9SViPgbXNFPRwcX0uA3F/Bnl/152s5RMgtOqVhyLXJXgDrOiYqRnvzyTIb M72A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=NhDNMuC1H0eSoN/WajoiNNeKjoLyrOlD6bUc5/h96GA=; b=U5laFptrPu+hZba+V4Tx+/V8aFpk7Ggcc5XHOkDezwi90AaHQupUXBnDKRfnFqpJbW TIK7JuhtHolqJXPnohYtoo2Eq8YpXTfYAQZoBiRz4n6uVeNlsNjso973lM8Vj//hLVV5 5hwfWSkQEhIt8lq0FnXJwigChvFC378Vvti/H3SSU1tYx5MLDvcP0wJwrV4gWCInGECV KO7tbD0ZeaE5u4Pa/fkGKm7m1M2ZNxo1P2nk+iEPhD9crrpJN+lTzE1XV1EVOpaEoG8r 12Q/UeOUCP5PN/T+4Hw/hfOAFkMQqD8aEJZIoJ0jJEZzjKwKg51LdayIp5F4xDDTtZjc 5gxg==
X-Gm-Message-State: AKS2vOxeJgPqn9/1ysVoCL29pZ01v61wH2DoOciE/toXzD0qRD3aWSgY WiKCcUWA/NiBEVxeus88ekT4VONW7g==
X-Received: by 10.223.171.29 with SMTP id q29mr7319236wrc.12.1497280243896; Mon, 12 Jun 2017 08:10:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.138.210 with HTTP; Mon, 12 Jun 2017 08:10:43 -0700 (PDT)
Reply-To: sarikaya@ieee.org
In-Reply-To: <3a9dbc93332d4b799c44909c68e469ec@XCH-ALN-003.cisco.com>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com> <3a9dbc93332d4b799c44909c68e469ec@XCH-ALN-003.cisco.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
Date: Mon, 12 Jun 2017 10:10:43 -0500
Message-ID: <CAC8QAcep2PbCNBXZ29ZvBaDE2EHK=tajei7tgs0Nm_DY9kS0xA@mail.gmail.com>
Subject: Re: IAD Retirement
To: "Bernie Volz (volz)" <volz@cisco.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c1b4d9c11169a0551c4b911"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lMWbsVli0YszLIZqrEMgQ-H6dOU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 15:10:47 -0000

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

On Mon, Jun 12, 2017 at 10:07 AM, Bernie Volz (volz) <volz@cisco.com> wrote:

> Hi:
>
> Thanks for your efforts and belief in the IETF! Will be sad to see you go!
>
> Best of luck with whatever is next for you!
>
>
+1


Regards,

Behcet

> - Bernie
>
> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of IETF
> Administrative Director
> Sent: Monday, June 12, 2017 9:31 AM
> To: IETF Announcement List <ietf-announce@ietf.org>
> Subject: IAD Retirement
>
> All,
>
> I will be retiring from the position of IETF Administrative Director
> on 31 October 2017.
>
> On 1 June I concluded 12 years as IAD, member of the IAOC and
> trustee of the IETF Trust.
>
> I accepted this position because I believed in the mission of the
> IETF and its importance to people worldwide. It has been an honor
> and a privilege to have supported the IETF in this capacity.
>
> Thanks for your patience, feedback, and support.
>
> Best
> Ray
>
>

--94eb2c1b4d9c11169a0551c4b911
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 Mon, Jun 12, 2017 at 10:07 AM, Bernie Volz (volz) <span dir=3D"ltr">=
&lt;<a href=3D"mailto:volz@cisco.com" target=3D"_blank">volz@cisco.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-le=
ft-width:1px;border-left-style:solid">Hi:<br>
<br>
Thanks for your efforts and belief in the IETF! Will be sad to see you go!<=
br>
<br>
Best of luck with whatever is next for you!<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br></font></span></blockquo=
te><div><br></div><div>+1</div><div><br></div><div><br></div><div>Regards,<=
/div><div><br></div><div>Behcet=C2=A0</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(=
204,204,204);border-left-width:1px;border-left-style:solid"><span class=3D"=
HOEnZb"><font color=3D"#888888">
- Bernie<br>
</font></span><div class=3D"HOEnZb"><div class=3D"h5"><br>
-----Original Message-----<br>
From: WGChairs [mailto:<a href=3D"mailto:wgchairs-bounces@ietf.org">wgchair=
s-bounces@ietf.<wbr>org</a>] On Behalf Of IETF Administrative Director<br>
Sent: Monday, June 12, 2017 9:31 AM<br>
To: IETF Announcement List &lt;<a href=3D"mailto:ietf-announce@ietf.org">ie=
tf-announce@ietf.org</a>&gt;<br>
Subject: IAD Retirement<br>
<br>
All,<br>
<br>
I will be retiring from the position of IETF Administrative Director<br>
on 31 October 2017.<br>
<br>
On 1 June I concluded 12 years as IAD, member of the IAOC and<br>
trustee of the IETF Trust.<br>
<br>
I accepted this position because I believed in the mission of the<br>
IETF and its importance to people worldwide. It has been an honor<br>
and a privilege to have supported the IETF in this capacity.<br>
<br>
Thanks for your patience, feedback, and support.<br>
<br>
Best<br>
Ray<br>
<br>
</div></div></blockquote></div><br></div></div>

--94eb2c1b4d9c11169a0551c4b911--


From nobody Mon Jun 12 08:12:05 2017
Return-Path: <marc.blanchet@viagenie.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 D72F8129411 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:12: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, 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 roqNtfirpeGA for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:12:02 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4853B127078 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:12:02 -0700 (PDT)
Received: from [10.0.1.20] (h132.viagenie.ca [206.123.31.132]) by jazz.viagenie.ca (Postfix) with ESMTPSA id B2FB947A1D for <ietf@ietf.org>; Mon, 12 Jun 2017 11:12:01 -0400 (EDT)
From: "Marc Blanchet" <marc.blanchet@viagenie.ca>
To: ietf@ietf.org
Subject: Re: IAD Retirement
Date: Mon, 12 Jun 2017 11:12:02 -0400
Message-ID: <B5C21928-24F8-4F03-907E-76D86D859A5E@viagenie.ca>
In-Reply-To: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; markup=markdown
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iMKTs0HnPqAzQ2BH_k2gtZ0JvVs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 15:12:04 -0000

happy retirement Ray!

Marc.

On 12 Jun 2017, at 9:31, IETF Administrative Director wrote:

> All,
>
> I will be retiring from the position of IETF Administrative Director
> on 31 October 2017.
>
> On 1 June I concluded 12 years as IAD, member of the IAOC and
> trustee of the IETF Trust.
>
> I accepted this position because I believed in the mission of the
> IETF and its importance to people worldwide. It has been an honor
> and a privilege to have supported the IETF in this capacity.
>
> Thanks for your patience, feedback, and support.
>
> Best
> Ray


From nobody Mon Jun 12 08:13:12 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA985127078 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:13:05 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GzArsh8QAape for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:13: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 A8AB9120726 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:13:02 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id u19so129420732qta.3 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:13:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=N+QfH0lURpQc7OIk1u+AraG6AtzhNlWcdQbpjCC/ghY=; b=Yr+wibPKNGUmcyjltHN9T36hVT/UZg5ADlH4albBkUpCVHQksRg/oZEUbWlAQvtwGG gSDAWEiij6+VgWJ5e2KnAaDKhL6PJ/0YYQ24EV9g745N/K1fbKHLvb2pBNJVfED830r8 Qi6CL2I6XfUqBVcC9DP0QerpJ5g/yGKQ3hXWT5L0A16qQq829f9XEyIUoEx1CJ0ttrfo urV7yOvdPeR36IjBzEIijt6Kdf7v0ETN5InEccazzKZU+aXO+hwPWl0U2yw0HPe6zGkJ 7o76fbUfBeDFMwu/bzABeljwWhLZ8wmVrENqSEXDkf/NGIYleMwFjiRiEy3CL+itntzu EJdA==
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=N+QfH0lURpQc7OIk1u+AraG6AtzhNlWcdQbpjCC/ghY=; b=V6Z3w/p5bx68NG4yhsrVPFiSBHeLZOYVt6CWvtd9NSd4u5wnRV5itFqjv3dKp6DMPT XCcgWyhHZD53OdDRPGzyWWwlcoSiB1QtbN2T+P2Pc5r+J6yi7dJw1jHErRegjRhytPYf XXJAhKIkJn/ICow0r9CczQQgIb6i4v2QIrUr54wL5TuczxUtvRZcev/fCm0wu+/J5HWu iZyMDBNqGQIuo4G8yS4VWMX/FI/Ithep+kFxWc0/PtE5M25gBqvaM3SeSQl2XJoWnPBa I2Ugm+U/r5mbucwFJc7HJ8jpRVPD1/9F61UAsRWOUvTH8ThezgAvKpufwLvEJXWQcoAF q0iA==
X-Gm-Message-State: AODbwcC3QhpzZ5oHdPWweL7RZbGK3/jmyjXPzdlyTmyMs4L6cxe/7HHt r72YAW/so7S3jJJY
X-Received: by 10.237.61.231 with SMTP id j36mr68968568qtf.111.1497280381789;  Mon, 12 Jun 2017 08:13:01 -0700 (PDT)
Received: from [10.0.30.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id o41sm4935986qtc.26.2017.06.12.08.13.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Jun 2017 08:13:00 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: [DNSOP] Last Call: <draft-ietf-dnsop-sutld-ps-05.txt> (Special-Use Domain Names Problem Statement) to Informational RFC
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <20170612150034.f4etrpuhbnvbzpzz@hanna.meerval.net>
Date: Mon, 12 Jun 2017 11:12:59 -0400
Cc: Stephane Bortzmeyer <bortzmeyer@nic.fr>, "dnsop@ietf.org WG" <dnsop@ietf.org>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FA9EF11-83AF-4B1B-88D4-151108A47057@fugue.com>
References: <149678027581.3850.9197039878287017082.idtracker@ietfa.amsl.com> <20170612135200.ya3tivlhg2dhe3ry@nic.fr> <20170612150034.f4etrpuhbnvbzpzz@hanna.meerval.net>
To: Job Snijders <job@ntt.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/214n3FD6M5jSBfw3XAEWZ0zKZV0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 15:13:06 -0000

On Jun 12, 2017, at 11:00 AM, Job Snijders <job@ntt.net> wrote:
> NEW:
>   The situation was somewhat forced, both by the fact that use of the
>   .onion domain name by the Tor Project predates the process described
>   in RFC 6761 by 9 years, and because a deadline [CABF-DEADLINE] had
>   been set by the CA/Browser Forum [CABF] after which all PKI
>   certificates for internal names would expire and no new certificates
>   would be issued. At the time .onion was considered an internal name.
>   IETF recognition of the .onion as a Special-Use Top-Level Domain =
Name
>   facilitated the development of a certificate issuance process
>   specific to .onion domain names [CABF-BALLOT144].=20
>=20
> [CABF-DEADLINE] should link to =
https://www.digicert.com/internal-names.htm
> [CABF] should link to https://cabforum.org/
> [CABF-BALLOT144] should link to =
https://cabforum.org/2015/02/18/ballot-144-validation-rules-dot-onion-name=
s/

Thanks, I think this is better text.

> I wasn't there, but reading ballot-144, some cabforum mails, and=20
> =
https://blog.torproject.org/blog/landmark-hidden-services-onion-names-rese=
rved-ietf
> it appears to me that all parties involved were actively trying to fix =
a
> long standing broken situation.

Yes, that's what it looked like to me as well.


From nobody Mon Jun 12 08:15:19 2017
Return-Path: <bortzmeyer@nic.fr>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38A3F126FB3; Mon, 12 Jun 2017 08:15:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 siq9W18xccsb; Mon, 12 Jun 2017 08:15:11 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4: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 D6CB6120726; Mon, 12 Jun 2017 08:15:10 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 1A6B928067B; Mon, 12 Jun 2017 17:15:09 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id 13B872806B3; Mon, 12 Jun 2017 17:15:09 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id 0CEF628067B; Mon, 12 Jun 2017 17:15:09 +0200 (CEST)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id 06FB46079321; Mon, 12 Jun 2017 17:15:09 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id F3C3B40E20; Mon, 12 Jun 2017 17:15:08 +0200 (CEST)
Date: Mon, 12 Jun 2017 17:15:08 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Ted Lemon <mellon@fugue.com>
Cc: Job Snijders <job@ntt.net>, Stephane Bortzmeyer <bortzmeyer@nic.fr>, "dnsop@ietf.org WG" <dnsop@ietf.org>, ietf@ietf.org
Subject: Re: Last Call: <draft-ietf-dnsop-sutld-ps-05.txt>  (Special-Use Domain Names Problem Statement) to Informational RFC
Message-ID: <20170612151508.s7xf5aamnme5ridb@nic.fr>
References: <149678027581.3850.9197039878287017082.idtracker@ietfa.amsl.com> <20170612135200.ya3tivlhg2dhe3ry@nic.fr> <20170612150034.f4etrpuhbnvbzpzz@hanna.meerval.net> <7FA9EF11-83AF-4B1B-88D4-151108A47057@fugue.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7FA9EF11-83AF-4B1B-88D4-151108A47057@fugue.com>
X-Operating-System: Debian GNU/Linux 9.0
X-Kernel: Linux 4.9.0-3-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: NeoMutt/20170113 (1.7.2)
X-Bogosity: No, tests=bogofilter, spamicity=0.000564, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2017.6.12.150916
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QrXbyVL9VDq_aag0RuRV95pGjJc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 15:15:12 -0000

On Mon, Jun 12, 2017 at 11:12:59AM -0400,
 Ted Lemon <mellon@fugue.com> wrote 
 a message of 31 lines which said:

> Thanks, I think this is better text.

Me too (no longer talks of "unilateral" use)


From nobody Mon Jun 12 08:17:28 2017
Return-Path: <mellon@fugue.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E35C1129404 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:17:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GT4ra3V-4Y8o for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 08:17:25 -0700 (PDT)
Received: from mail-qt0-x235.google.com (mail-qt0-x235.google.com [IPv6:2607:f8b0:400d:c0d::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 24BF2126FB3 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:17:25 -0700 (PDT)
Received: by mail-qt0-x235.google.com with SMTP id c10so129486061qtd.1 for <ietf@ietf.org>; Mon, 12 Jun 2017 08:17:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=E55qGa17/5orOBadChvN+ZY7WU+4I8GVP/9iap3v0sw=; b=VLk1n7LjlGr/xl3CTMu7ycniuv33linwQGpcSxI0Qrsu+PuDYFfyXOiuhqt8J4Iq7O szY4Eo01waqv26LEbgVMUwy3Ce67O6yaE8GW1S3yNoEr/5BIFEVVL0lYDKvA58OwBsD/ B9bGR6sirKYRxq3Q9huCQx2NNDuyFKc3l/SdT7WgQSfcb9KmlJl2mCNgzQmJl53y0rk+ gQBBOF9twNB2LBUN7CsVjyCImGSn+kySb0Mn3rj/lw0fDoPS4f53lVpx//l2pXtyQNBP e0ZdG6NuT8+mxWOyzl7+5Scu5jRU6bp5Npn2+0y6D2wdFCAskoR7tyZrPurAyCZy0cfZ TlOw==
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=E55qGa17/5orOBadChvN+ZY7WU+4I8GVP/9iap3v0sw=; b=o77LtZ366DVAmKpLOxYTetl9L6O84jWG0GQX3DoJi4tPaLeU49zQizlEbq7ofGtD9K OvTefQ2BMm4sYX+v/flyzejP6ReUJAgfrq+1rdL2B37DwG8AkuAFxg414mRN04f0aAKC fEs9IWvOnfr5oGAGA71Pi1x/6WZ5gfmewFGxvJl/HzgIBkwdtG82NTgJ1W7O7LZmimIh XybjuwxChca8KleX2V+wUprDMcPQa0hvU8fIHlbjNolhJEkv0AohwNYAY54mvclLZLhT 4qq5+kkt28dJFo7IyTZidivE3/G9Ut4pNIxJc6a0n2ufDMhzBkToBX9+WwN0W3oPe184 yBLw==
X-Gm-Message-State: AKS2vOy4IzEVi4QJ379sxSc5rJPY2kx9CsaONKESjIOQTSNw24CWl6Zo ijR717KNDqJMT0UR1q4BKA==
X-Received: by 10.55.86.199 with SMTP id k190mr42146276qkb.70.1497280644353; Mon, 12 Jun 2017 08:17:24 -0700 (PDT)
Received: from [10.0.30.228] (c-73-167-64-188.hsd1.nh.comcast.net. [73.167.64.188]) by smtp.gmail.com with ESMTPSA id j6sm4923261qkd.0.2017.06.12.08.17.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Jun 2017 08:17:23 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <CE770688-DC27-4BB7-ABD9-B3B873532D47@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8665EF6E-0DE7-49C0-8263-7827973BC937"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Last Call: <draft-ietf-dnsop-sutld-ps-05.txt>  (Special-Use Domain Names Problem Statement) to Informational RFC
Date: Mon, 12 Jun 2017 11:17:22 -0400
In-Reply-To: <20170612151508.s7xf5aamnme5ridb@nic.fr>
Cc: Job Snijders <job@ntt.net>, "dnsop@ietf.org WG" <dnsop@ietf.org>, ietf@ietf.org
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>
References: <149678027581.3850.9197039878287017082.idtracker@ietfa.amsl.com> <20170612135200.ya3tivlhg2dhe3ry@nic.fr> <20170612150034.f4etrpuhbnvbzpzz@hanna.meerval.net> <7FA9EF11-83AF-4B1B-88D4-151108A47057@fugue.com> <20170612151508.s7xf5aamnme5ridb@nic.fr>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4n623lcJbjafmsnhuc7hn2ZOKtc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 15:17:27 -0000

--Apple-Mail=_8665EF6E-0DE7-49C0-8263-7827973BC937
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On Jun 12, 2017, at 11:15 AM, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:
> Me too (no longer talks of "unilateral" use)

"unilateral" isn't a criticism.   It's what happened.   There's a reason =
that it happened.   I don't think we should minimize that.   I disagree =
with the idea that was advanced by some folks in dnsop during the .onion =
discussion that the unilateral use of the name was bad.   It was common =
practice at the time.=

--Apple-Mail=_8665EF6E-0DE7-49C0-8263-7827973BC937
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D"">On Jun 12, 2017, at 11:15 AM, Stephane Bortzmeyer &lt;<a =
href=3D"mailto:bortzmeyer@nic.fr" class=3D"">bortzmeyer@nic.fr</a>&gt; =
wrote:<div><blockquote type=3D"cite" class=3D""><div class=3D""><span =
style=3D"font-family: Menlo-Regular; font-size: 18px; font-style: =
normal; font-variant-caps: normal; font-weight: normal; letter-spacing: =
normal; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
float: none; display: inline !important;" class=3D"">Me too (no longer =
talks of "unilateral" use)</span></div></blockquote></div><br =
class=3D""><div class=3D"">"unilateral" isn't a criticism. &nbsp; It's =
what happened. &nbsp; There's a reason that it happened. &nbsp; I don't =
think we should minimize that. &nbsp; I disagree with the idea that was =
advanced by some folks in dnsop during the .onion discussion that the =
unilateral use of the name was bad. &nbsp; It was common practice at the =
time.</div></body></html>=

--Apple-Mail=_8665EF6E-0DE7-49C0-8263-7827973BC937--


From nobody Mon Jun 12 09:30:35 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 60E431201F2 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 09:30:33 -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 KdAP4rYWI2ZD for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 09:30:32 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::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 DE326126BFD for <ietf@ietf.org>; Mon, 12 Jun 2017 09:30:31 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id l89so53315974pfi.2 for <ietf@ietf.org>; Mon, 12 Jun 2017 09:30:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to;  bh=RUkwc2vGAAjFqfy28nXSPSLYRTRy5G+csibnCPqYk5w=; b=ithWXCPVNy6VHxIe0nXap6poSUurvMkya8VyqdSBSfdehh045bV1BYxxjC20CJczbX /y3injsoVre9wLNxeAydCaIRvLqKp3J2nEdwq8lhqhRsn7mWIIDXdlt4a29BygClNve+ TlZ11VfQmHLh7IaFxvp6hEv0OrGIbG1SfL2aH4bAo7GvY0HhBSSwICcUJpQsHyFizmS5 qyGxSRrhO1UiUrE2bbz5htxzFLfFlEL/uJ9UrtKRBXA1nr3kGcylJCyik/SiW+5oXGC4 45yx4jLNll4ipvDQO14360o7uSgEkJWs442fbL/3Qx0hwl6/OOhRAi79mUr4wyKWWjFm wrqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=RUkwc2vGAAjFqfy28nXSPSLYRTRy5G+csibnCPqYk5w=; b=GF46MfB86KzXahNtEC1ARL8Gpa+HfCapALG2vO7tT9aNDtunZj/blMFuBE7SRjjQOY pEGCVwK3/pNbWjfEtfa1qrZAo4b7ee3VDXkgD3ufo3KvelgAQ+eLdUZX4wR6eYkhZ7K8 eSXA5bky9YphtAfHW7Gs+ma9JqTj4V4z/bNlQe451g6BrP0mXbqrv2Rt50TTm482HWz5 OuevF/yq2TypBMnMAV2HM/dVFQZNk7/AWpDH+nfHwnDma4Mirm9w5LN4CpV8IaAyXeJY P45n2BaglV5T0VYH3LB2GRILAFfwXr8rnfZI9NIEngrcPLbTzMgDDq0qGweGe/5FgKXU j9yw==
X-Gm-Message-State: AODbwcBajkUTA+F0xRYLeTYES1USg+vuei0lDLGZ7fS+haYUYC/vXEFS +dVBPso0w8dZMQKKvn/cmPK5KNhVcQ==
X-Received: by 10.98.86.132 with SMTP id h4mr44057136pfj.205.1497285031403; Mon, 12 Jun 2017 09:30:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.169.13 with HTTP; Mon, 12 Jun 2017 09:29:50 -0700 (PDT)
In-Reply-To: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Mon, 12 Jun 2017 12:29:50 -0400
Message-ID: <CAHbuEH6B8rWL7_aWbmuCoydFs8tb_LfO+s7NKQc-Y4V7xXCiHQ@mail.gmail.com>
Subject: Re: [IAB] IAD Retirement
To: IETF <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DUdo68o6REgzEWrMu5P99Xm8dDI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 16:30:33 -0000

Ray,

Thank you very much for serving in this role for such a long time!
It's not an easy job (at all) and we were very lucky to have you for
so long!  I hope you have fun plans for your next chapter!

Best,
Kathleen

On Mon, Jun 12, 2017 at 9:31 AM, IETF Administrative Director
<iad@ietf.org> wrote:
> All,
>
> I will be retiring from the position of IETF Administrative Director
> on 31 October 2017.
>
> On 1 June I concluded 12 years as IAD, member of the IAOC and
> trustee of the IETF Trust.
>
> I accepted this position because I believed in the mission of the
> IETF and its importance to people worldwide. It has been an honor
> and a privilege to have supported the IETF in this capacity.
>
> Thanks for your patience, feedback, and support.
>
> Best
> Ray
>



-- 

Best regards,
Kathleen


From nobody Mon Jun 12 09:42:02 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 E04701293F9 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 09:41:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 pGfzf0GxAZPQ for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 09:41:58 -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 031BE127866 for <ietf@ietf.org>; Mon, 12 Jun 2017 09:41:58 -0700 (PDT)
Received: by mail-wr0-x229.google.com with SMTP id q97so104425622wrb.2 for <ietf@ietf.org>; Mon, 12 Jun 2017 09:41: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=Yq80kTTbOsfF4XEUzxtMlerNI++YN5Cs/9ABSq1wQd0=; b=TQYdxCRCpqHnTjDIziy52zA89/ILQRC8W9YXxdi8n8r2TLjEDoXRgNev6b2i471XfF C+eCjeg5I2I8q1952PNQatzGqolK4ArzdjkGMIrR3xHP7xDHTXB8Y1DA7uSJNXfWEm/q QXjCRXDU0bSJHzTUncfMNjgYPL6VPe8SDCGw9S+kPfnpm2p8MVIJCDab4/s9zFaBB7NH woWq9Pho8BMobxtZYrOls65hn8YCpJwFNirBAlxpnsW0pwiSqtrIqs7N4ihsbC9nD1F6 vvaYhXwnCee9OUIIhJrBUZtweHVFYApCZafLslbuOsOu2CL8wSLf8xNjKGmVztc7dD4H SCsQ==
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=Yq80kTTbOsfF4XEUzxtMlerNI++YN5Cs/9ABSq1wQd0=; b=ViIxkobwBSm4LlYCsOHuxAmgGhTgEnDVhl2wA+4VWtV/RXcYJTk50rkwiy6SextK3O Wf7lyIR+VBVpDnzDHaBHyklhBLTLuDxXbyByM5W+xrqkfgzKtnDlCTK2ZELs9gBRBDpt zJYhgohGnsjnPTYXvnMj4jlnqOZMJK7a5kvCL+6qxvljjrtq/FkXz5ptz9Pttqo5scxt I625KFhsAsusqlT6iXjaJ7cP1gOlh9WvnsszkPLfo8tVGKy9n5iSzGrNUuenGBiPPb90 CqNdCggK6x6ccPnVAy7KJtKQKtYOaCbuKSSWZOMfyAQR4faKRT8O80i3nhL2Cf2HLzDr /yIQ==
X-Gm-Message-State: AKS2vOyYkxRNBKOYv6mJ2V+EMoMUQiWXeTs9wS1QX6sSe2ALvYT+Yfyv 63BYy7K2U/tJocopvAFd9XlxZSZ1JA==
X-Received: by 10.28.100.68 with SMTP id y65mr8521145wmb.40.1497285716406; Mon, 12 Jun 2017 09:41:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.131.66 with HTTP; Mon, 12 Jun 2017 09:41:55 -0700 (PDT)
In-Reply-To: <CAHbuEH6B8rWL7_aWbmuCoydFs8tb_LfO+s7NKQc-Y4V7xXCiHQ@mail.gmail.com>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com> <CAHbuEH6B8rWL7_aWbmuCoydFs8tb_LfO+s7NKQc-Y4V7xXCiHQ@mail.gmail.com>
From: Alia Atlas <akatlas@gmail.com>
Date: Mon, 12 Jun 2017 12:41:55 -0400
Message-ID: <CAG4d1rfbLZsEDZ+Uqdb=Z8pp7CM8q-Y2Cecb0TTazO0dDoPPjQ@mail.gmail.com>
Subject: Re: [IAB] IAD Retirement
To: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114b32be40fb810551c5ff6a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/I6jOoskm9LVeNoo0KvOBQZ0YXuc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 16:42:00 -0000

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

On Mon, Jun 12, 2017 at 12:29 PM, Kathleen Moriarty <
kathleen.moriarty.ietf@gmail.com> wrote:

> Ray,
>
> Thank you very much for serving in this role for such a long time!
> It's not an easy job (at all) and we were very lucky to have you for
> so long!  I hope you have fun plans for your next chapter!
>


+1

Thank you so much for all your work!

Regards,
Alia


> Best,
> Kathleen
>
> On Mon, Jun 12, 2017 at 9:31 AM, IETF Administrative Director
> <iad@ietf.org> wrote:
> > All,
> >
> > I will be retiring from the position of IETF Administrative Director
> > on 31 October 2017.
> >
> > On 1 June I concluded 12 years as IAD, member of the IAOC and
> > trustee of the IETF Trust.
> >
> > I accepted this position because I believed in the mission of the
> > IETF and its importance to people worldwide. It has been an honor
> > and a privilege to have supported the IETF in this capacity.
> >
> > Thanks for your patience, feedback, and support.
> >
> > Best
> > Ray
> >
>
>
>
> --
>
> Best regards,
> Kathleen
>
>

--001a114b32be40fb810551c5ff6a
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 M=
on, Jun 12, 2017 at 12:29 PM, Kathleen Moriarty <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:kathleen.moriarty.ietf@gmail.com" target=3D"_blank">kathleen.m=
oriarty.ietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">Ray,<br>
<br>
Thank you very much for serving in this role for such a long time!<br>
It&#39;s not an easy job (at all) and we were very lucky to have you for<br=
>
so long!=C2=A0 I hope you have fun plans for your next chapter!<br></blockq=
uote><div><br></div><div><br></div><div>+1</div><div><br></div><div>Thank y=
ou so much for all your work!</div><div><br></div><div>Regards,</div><div>A=
lia</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">
Best,<br>
Kathleen<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Mon, Jun 12, 2017 at 9:31 AM, IETF Administrative Director<br>
&lt;<a href=3D"mailto:iad@ietf.org">iad@ietf.org</a>&gt; wrote:<br>
&gt; All,<br>
&gt;<br>
&gt; I will be retiring from the position of IETF Administrative Director<b=
r>
&gt; on 31 October 2017.<br>
&gt;<br>
&gt; On 1 June I concluded 12 years as IAD, member of the IAOC and<br>
&gt; trustee of the IETF Trust.<br>
&gt;<br>
&gt; I accepted this position because I believed in the mission of the<br>
&gt; IETF and its importance to people worldwide. It has been an honor<br>
&gt; and a privilege to have supported the IETF in this capacity.<br>
&gt;<br>
&gt; Thanks for your patience, feedback, and support.<br>
&gt;<br>
&gt; Best<br>
&gt; Ray<br>
&gt;<br>
<br>
<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">--<br>
<br>
Best regards,<br>
Kathleen<br>
<br>
</font></span></blockquote></div><br></div></div>

--001a114b32be40fb810551c5ff6a--


From nobody Mon Jun 12 09:48:34 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 B83C4129408 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 09:48:32 -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=cooperw.in header.b=qSvGfD7F; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=l1otaFix
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TjDyNmfnAj-z for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 09:48:31 -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 0375D127866 for <ietf@ietf.org>; Mon, 12 Jun 2017 09:48:31 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 679DD20B4B for <ietf@ietf.org>; Mon, 12 Jun 2017 12:48:30 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Mon, 12 Jun 2017 12:48:30 -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=cHaIpI24EZcrsuZFeq wgZHpnXGCvDDb+iHx1Q4iG7zw=; b=qSvGfD7F2vOFaEmqmyQsi4LoCkRfdsI8hp bf7P7OUNo4u0pLMzKRRrfzbm96U/KxT49JRJOH1EV8Dv2GtjjCT5VbGGTeWIlfk2 +XSA1SeG2vHOxMIK34+Cxh7WnbIAv2L8TS5vVzzB8AJSfRBd0I7KFFPvz5Dk2oJT obz55wqBiUpWr0V8bJUDMgmjVh6lfgx5RNwYs2SsvMXgf32BcdmsCu1Th1TXPi/D foF1yXQV6spx8Tg3SbVape0R2iwlLVx5SScEr+lrd2RkT1Jh9Y2vcaSHdkCzVMbU ciyWqJ5rNEJBEvsp5zVTUaWpmJeqwfcYJEkLuF6Hxb4G16lX0DfQ==
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=cHaIpI24EZcrsuZFeqwgZHpnXGCvDDb+iHx1Q4iG7zw=; b=l1otaFix h3Np0eXf8p+ePekJIWDvrZphI2gdBDXZISjNiXvpqg/kCJ267lEH4FaQBLRKJnyq jR33zV4M1LE1E8TCauPy80O4qpR9zCjTHUoJiFP7774G1S1aRzGrhA+WLiycE0dd VoYsDUVlCAHlWdiSN/KLjEus7FQa1BzLtT0mgLzx/B7eQieRfim00PshpCiMeSEs FSFJc/79zg9YyPc3bqIzmXf217g8BjBA3AXSnWjZb8PuV2PXbZoSY+vtwq+NsWnK lenq5GMhOgI5vDZ3QmtXuDcfQ2j4RdHXiWkTTn8pyzH2MSJMcQiRGICFedUdFlBK p8zMgi7Di5Cy6Q==
X-ME-Sender: <xms:3sU-Wal6jm9YYa93Ut8mSBSc_7LCg-WvyQHKq2WE4F7zGV1DJwf8LA>
X-Sasl-enc: Sa7bMu3t/AfwjUZW6QvRRdNtGCIHs2rNV7E7qbQ8/p5n 1497286110
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.172]) by mail.messagingengine.com (Postfix) with ESMTPA id E3F897E7A3 for <ietf@ietf.org>; Mon, 12 Jun 2017 12:48:29 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [IAOC] IAD Retirement
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
Date: Mon, 12 Jun 2017 12:48:28 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <00CB2BBF-0FD6-441B-BDAB-51EF5EF1447A@cooperw.in>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EfEctusXeeTvXz6By3phmx4l5v4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 16:48:32 -0000

Ray,

I know there will be official thank-yous to come, but wanted to give my =
personal thanks for all your years of service to the IETF! And =
congratulations on this milestone.

Alissa

> On Jun 12, 2017, at 9:31 AM, IETF Administrative Director =
<iad@ietf.org> wrote:
>=20
> All,
>=20
> I will be retiring from the position of IETF Administrative Director
> on 31 October 2017.
>=20
> On 1 June I concluded 12 years as IAD, member of the IAOC and
> trustee of the IETF Trust.
>=20
> I accepted this position because I believed in the mission of the
> IETF and its importance to people worldwide. It has been an honor
> and a privilege to have supported the IETF in this capacity.
>=20
> Thanks for your patience, feedback, and support.
>=20
> Best
> Ray
>=20


From nobody Mon Jun 12 09:59:23 2017
Return-Path: <dmm@1-4-5.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 A83FC129417 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 09:59:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=1-4-5-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 OZla28NO3xsF for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 09:59:21 -0700 (PDT)
Received: from mail-ua0-x22f.google.com (mail-ua0-x22f.google.com [IPv6:2607:f8b0:400c:c08::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 060A81287A0 for <ietf@ietf.org>; Mon, 12 Jun 2017 09:59:20 -0700 (PDT)
Received: by mail-ua0-x22f.google.com with SMTP id q15so59926578uaa.2 for <ietf@ietf.org>; Mon, 12 Jun 2017 09:59:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1-4-5-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=MEOWYSkBB4dJDXhAPlNx8YEdLmz2PDumsQZWze0SK7I=; b=fhK/nYUDx4qyDPR3Qtt/68ZotRo/uICzwmCaQ3DImeWDlYTqVyHz1ndL3cw0Iwlo+g P9Dq/IQW53Cf4MJEjZQFGkHm1RHCI9IzBMfTYEizOxdQNqMxT4yIeGjRUiYiclMYRJpY nZ+mNd9R+IJCr8Wgee4zbl9zzFvVbqpztSm3Yr5GyeY2ykQ5AmOs+McixbWhCp1pE1Vk T26bPoFyXYOY6o/GqOurv1RkSOE/PaB3ei/f3mjH87OBslX/1tE+0oJerRFYdhafDMgC rb4hxweI9ui27/Y7pyf9l7fCYMbLkfargrjXrvjyIzkLbvR6xbEyeHVX9YE7Wzl4po8A 4nsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=MEOWYSkBB4dJDXhAPlNx8YEdLmz2PDumsQZWze0SK7I=; b=qZQeT2IMO7sVrpZ965Fs1iWidF9rHwt8j1MYOq+afr+6nfYHO5RBy6l8rD/MkN/t/W rU3Phkbr8yi2NObBEPUYI0LrDTOoHFmTw+Z3FU6Tufbh0hRMN5a0XY34PiESSOEYY9Y4 Bt0l5NwX6NJpbb7qWzrDhlTnRpek+auisY7Eu+KGeU2bHSqN0ka5BWTRTxBzKFzoi9jO KNE2HxhI5fcffPPTFij7LFUOuqNfVPl5oMI5yryiixBKdDFsL4beiiSg2oKlErFBBe80 BRkbGC/ANt3ZNr43ZEOdpZsgy64NHGFmad3hc1LxOITNljmla4X0ROg2wTulYJNdnPRr 1jyw==
X-Gm-Message-State: AODbwcAFeOFtH56EC29ia+xlfMloIsk5xf4N8ixDCePq+M6AgDrNwzXd ZEOwz4GRKDu8OR9zxGz71UKsfdq7APTC
X-Received: by 10.176.26.47 with SMTP id a47mr24365604uai.64.1497286759698; Mon, 12 Jun 2017 09:59:19 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.159.58.94 with HTTP; Mon, 12 Jun 2017 09:59:19 -0700 (PDT)
X-Originating-IP: [128.223.156.253]
In-Reply-To: <00CB2BBF-0FD6-441B-BDAB-51EF5EF1447A@cooperw.in>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com> <00CB2BBF-0FD6-441B-BDAB-51EF5EF1447A@cooperw.in>
From: David Meyer <dmm@1-4-5.net>
Date: Mon, 12 Jun 2017 09:59:19 -0700
Message-ID: <CAHiKxWjao60kHkZ5BsGyFwRL2y4OscQ2JuTR+NpoyKgAvJss-Q@mail.gmail.com>
Subject: Re: [IAOC] IAD Retirement
To: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403043651407089c90551c63d0d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZsiLEJvd6OUTpTep2qObXU30nR8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 16:59:22 -0000

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

>
> > On Jun 12, 2017, at 9:31 AM, IETF Administrative Director <iad@ietf.org>
> wrote:
> >
> > All,
> >
> > I will be retiring from the position of IETF Administrative Director
> > on 31 October 2017.
> >
> > On 1 June I concluded 12 years as IAD, member of the IAOC and
> > trustee of the IETF Trust.
> >
> > I accepted this position because I believed in the mission of the
> > IETF and its importance to people worldwide. It has been an honor
> > and a privilege to have supported the IETF in this capacity.
> >
> > Thanks for your patience, feedback, and support.
> >
> > Best
> > Ray
>
>
Ray, it seems like not that long ago that you came on board. Thank you for
all of your hard work and dedication, and best of luck in whatever the
future holds.

Dave

--f403043651407089c90551c63d0d
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"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5">&gt; On =
Jun 12, 2017, at 9:31 AM, IETF Administrative Director &lt;<a href=3D"mailt=
o:iad@ietf.org">iad@ietf.org</a>&gt; wrote:<br>
&gt;<br>
&gt; All,<br>
&gt;<br>
&gt; I will be retiring from the position of IETF Administrative Director<b=
r>
&gt; on 31 October 2017.<br>
&gt;<br>
&gt; On 1 June I concluded 12 years as IAD, member of the IAOC and<br>
&gt; trustee of the IETF Trust.<br>
&gt;<br>
&gt; I accepted this position because I believed in the mission of the<br>
&gt; IETF and its importance to people worldwide. It has been an honor<br>
&gt; and a privilege to have supported the IETF in this capacity.<br>
&gt;<br>
&gt; Thanks for your patience, feedback, and support.<br>
&gt;<br>
&gt; Best<br>
&gt; Ray<br><br></div></div></blockquote><div><br></div><div>Ray, it seems =
like not that long ago that you came on board. Thank you for all of your ha=
rd work and dedication, and best of luck in whatever the future holds.</div=
><div><br></div><div>Dave</div><div>=C2=A0</div></div><br></div></div>

--f403043651407089c90551c63d0d--


From nobody Mon Jun 12 10:06:16 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 1A31E127866; Mon, 12 Jun 2017 10:06:15 -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 H80MLKgiMgOR; Mon, 12 Jun 2017 10:06:13 -0700 (PDT)
Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::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 E8CDA12441E; Mon, 12 Jun 2017 10:06:12 -0700 (PDT)
Received: by mail-lf0-x22a.google.com with SMTP id o83so54288823lff.3; Mon, 12 Jun 2017 10:06:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=message-id:mime-version:to:from:subject:date:importance:in-reply-to :references; bh=ge5PqsKHc/9tlk1mB/bHAJdF96PNMZIvwOmMkDLAFqs=; b=d180cR5Y017HWIHn+dE1pWPJJ0/ie3sw3Uc7dyKr/CYmdmDsKmk5K+iY44K4mB6Ri6 rrNm+E5iDxTHPkCT0lv0bs99mclm79kl0gBHXeTua/TEoOf+a6jjhN1bFVVjYI/KTNtO rhXH2/JRH/vIMC0TXGAMnrMIYRQKBQQvUKkic46aS4agtnT2184YusXP5ceqomh7quk8 HnH0Aospe3t8yLZAayExxyGyuRRI7rgb6x1O2flZplc6bJuOx2uCH7DErao8YDNbr/7X 4FZfJGLXfHUWnDtPz7wAornXh1nLIEhLnX0BImc2Ud445dpOYhbsV2n/7dvYRAeUNhea WKdA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version:to:from:subject:date :importance:in-reply-to:references; bh=ge5PqsKHc/9tlk1mB/bHAJdF96PNMZIvwOmMkDLAFqs=; b=iNiKLU0v68CBtHL59EG75CjKVUelZ7kt9VkaVIbWpc+FgqmI0Crf36d1HmMRGwy9ND ZRwH1G4xrWjDyYrEKeZtvYznaeyeg0KwVsCOi/S57PMPzo/mROHm6Kz4HmQrJm8s+Lgv U4Jn0iQplQjF/irWLtF1Cuf5Wy828tWASAWzioogyawS6u/yIWszjB47r191GHshwZVp qDsx/Q+fImfkca+z/02dRHA/HpSj/nZwEk6vvVG5D4sxUH7P7XUnGNAZYIDvO9aC3Q5l hGjH8MmU6HafnM0A2vir0WQeE9nqWl/4ByxgIWJ226jPNG5oPeUqLAzXU3x7Mffeu6ZF URRw==
X-Gm-Message-State: AODbwcAN2Z7fmKKwCT4PMZmA6630YT7db9tGpnzi5xd8SoMqiKalHPQ+ 9sKVUolSlzJjp9H/1Qs=
X-Received: by 10.80.214.157 with SMTP id r29mr16212175edi.147.1497287171015;  Mon, 12 Jun 2017 10:06:11 -0700 (PDT)
Received: from ?IPv6:::ffff:10.160.10.181? ([109.253.128.5]) by smtp.gmail.com with ESMTPSA id i38sm6308594eda.18.2017.06.12.10.06.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Jun 2017 10:06:10 -0700 (PDT)
Message-ID: <593eca02.2992500a.f4719.086d@mx.google.com>
MIME-Version: 1.0
To: "ietf@ietf.org" <ietf@ietf.org>,  IETF Announcement List <ietf-announce@ietf.org>
From: Yoav Nir <ynir.ietf@gmail.com>
Subject: RE: IAD Retirement
Date: Mon, 12 Jun 2017 20:05:35 +0300
Importance: normal
X-Priority: 3
In-Reply-To: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="_6AD3D148-EB17-4838-9AD1-C7BD7FB042EE_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G8gebbf_bZg-9ty_i2ncmaN1Mwo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 17:06:15 -0000

--_6AD3D148-EB17-4838-9AD1-C7BD7FB042EE_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Thank you for your service. It is very much appreciated.

Yoav

Sent from my Windows 10 phone

From: IETF Administrative Director
Sent: Monday, June 12, 2017 18:02
To: IETF Announcement List
Subject: IAD Retirement

All,

I will be retiring from the position of IETF Administrative Director
on 31 October 2017.

On 1 June I concluded 12 years as IAD, member of the IAOC and
trustee of the IETF Trust.

I accepted this position because I believed in the mission of the
IETF and its importance to people worldwide. It has been an honor
and a privilege to have supported the IETF in this capacity.

Thanks for your patience, feedback, and support.

Best
Ray



--_6AD3D148-EB17-4838-9AD1-C7BD7FB042EE_
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="utf-8"

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta ht=
tp-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8"><meta name=
=3DGenerator content=3D"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DEN-US link=3Dblue vlink=3D"#954F72"><div cla=
ss=3DWordSection1><p class=3DMsoNormal>Thank you for your service. It is ve=
ry much appreciated.</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>Yoav</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DM=
soNormal>Sent from my Windows 10 phone</p><p class=3DMsoNormal><o:p>&nbsp;<=
/o:p></p><div style=3D'mso-element:para-border-div;border:none;border-top:s=
olid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D=
'border:none;padding:0in'><b>From: </b><a href=3D"mailto:iad@ietf.org">IETF=
 Administrative Director</a><br><b>Sent: </b>Monday, June 12, 2017 18:02<br=
><b>To: </b><a href=3D"mailto:ietf-announce@ietf.org">IETF Announcement Lis=
t</a><br><b>Subject: </b>IAD Retirement</p></div><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p><p class=3DMsoNormal>All,</p><p class=3DMsoNormal><o:p>&nbs=
p;</o:p></p><p class=3DMsoNormal>I will be retiring from the position of IE=
TF Administrative Director</p><p class=3DMsoNormal>on 31 October 2017.</p><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>On 1 June I c=
oncluded 12 years as IAD, member of the IAOC and</p><p class=3DMsoNormal>tr=
ustee of the IETF Trust.</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cl=
ass=3DMsoNormal>I accepted this position because I believed in the mission =
of the</p><p class=3DMsoNormal>IETF and its importance to people worldwide.=
 It has been an honor</p><p class=3DMsoNormal>and a privilege to have suppo=
rted the IETF in this capacity.</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p><p class=3DMsoNormal>Thanks for your patience, feedback, and support.</p>=
<p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Best</p><p c=
lass=3DMsoNormal>Ray</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal><o:p>&nbsp;</o:p></p></div></body></html>=

--_6AD3D148-EB17-4838-9AD1-C7BD7FB042EE_--


From nobody Mon Jun 12 10:30:59 2017
Return-Path: <tony@att.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 56763127136; Mon, 12 Jun 2017 10:30:58 -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 DK2O4OTJs0hZ; Mon, 12 Jun 2017 10:30:56 -0700 (PDT)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD3171241FC; Mon, 12 Jun 2017 10:30:56 -0700 (PDT)
Received: from pps.filterd (m0049462.ppops.net [127.0.0.1]) by m0049462.ppops.net-00191d01. (8.16.0.17/8.16.0.17) with SMTP id v5CHQreN002265; Mon, 12 Jun 2017 13:30:54 -0400
Received: from alpi155.enaf.aldc.att.com (sbcsmtp7.sbc.com [144.160.229.24]) by m0049462.ppops.net-00191d01. with ESMTP id 2b1trv8q5c-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 12 Jun 2017 13:30:53 -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 v5CHUprf015151; Mon, 12 Jun 2017 13:30:52 -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 v5CHUhss014658 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 12 Jun 2017 13:30:50 -0400
Received: from MISOUT7MSGHUBAH.ITServices.sbc.com (MISOUT7MSGHUBAH.itservices.sbc.com [130.9.129.152]) by mlpi408.sfdc.sbc.com (RSA Interceptor); Mon, 12 Jun 2017 17:30:24 GMT
Received: from MISOUT7MSGUSRCG.ITServices.sbc.com ([169.254.7.110]) by MISOUT7MSGHUBAH.ITServices.sbc.com ([130.9.129.152]) with mapi id 14.03.0319.002; Mon, 12 Jun 2017 13:30:24 -0400
From: "HANSEN, TONY L" <tony@att.com>
To: "ietf@ietf.org" <ietf@ietf.org>, IETF Announcement List <ietf-announce@ietf.org>
Subject: Re: IAD Retirement
Thread-Topic: IAD Retirement
Thread-Index: AQHS44Aztgz0utAunkCr8+i5vNjdT6IhfCSA
Date: Mon, 12 Jun 2017 17:30:23 +0000
Message-ID: <E5444AE8-1E81-4653-86F2-7CF92703FA53@att.com>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
In-Reply-To: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [135.210.8.155]
Content-Type: text/plain; charset="utf-8"
Content-ID: <6FEF1D2433010649B4AEF8D46DF9CA0C@LOCAL>
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-06-12_11:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706120303
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nlYXLrfhmA7RjZAoRmqVZvJQ5TI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 17:30:58 -0000

V293LiBSYXksIHlvdXIgcXVpZXQgY29tcGV0ZW5jZSB3aWxsIGJlIHNvcmVseSBtaXNzZWQuIFRo
YW5rIHlvdSBmb3IgbWFueSB5ZWFycyBvZiBkZWRpY2F0ZWQgc2VydmljZS4NCg0KCVRvbnkNCg0K
T24gNi8xMi8xNywgOTozMSBBTSwgIklFVEYtQW5ub3VuY2Ugb24gYmVoYWxmIG9mIElFVEYgQWRt
aW5pc3RyYXRpdmUgRGlyZWN0b3IiIDxpZXRmLWFubm91bmNlLWJvdW5jZXNAaWV0Zi5vcmcgb24g
YmVoYWxmIG9mIGlhZEBpZXRmLm9yZz4gd3JvdGU6DQoNCiAgICBBbGwsDQogICAgDQogICAgSSB3
aWxsIGJlIHJldGlyaW5nIGZyb20gdGhlIHBvc2l0aW9uIG9mIElFVEYgQWRtaW5pc3RyYXRpdmUg
RGlyZWN0b3INCiAgICBvbiAzMSBPY3RvYmVyIDIwMTcuDQogICAgDQogICAgT24gMSBKdW5lIEkg
Y29uY2x1ZGVkIDEyIHllYXJzIGFzIElBRCwgbWVtYmVyIG9mIHRoZSBJQU9DIGFuZA0KICAgIHRy
dXN0ZWUgb2YgdGhlIElFVEYgVHJ1c3QuDQogICAgDQogICAgSSBhY2NlcHRlZCB0aGlzIHBvc2l0
aW9uIGJlY2F1c2UgSSBiZWxpZXZlZCBpbiB0aGUgbWlzc2lvbiBvZiB0aGUNCiAgICBJRVRGIGFu
ZCBpdHMgaW1wb3J0YW5jZSB0byBwZW9wbGUgd29ybGR3aWRlLiBJdCBoYXMgYmVlbiBhbiBob25v
cg0KICAgIGFuZCBhIHByaXZpbGVnZSB0byBoYXZlIHN1cHBvcnRlZCB0aGUgSUVURiBpbiB0aGlz
IGNhcGFjaXR5Lg0KICAgIA0KICAgIFRoYW5rcyBmb3IgeW91ciBwYXRpZW5jZSwgZmVlZGJhY2ss
IGFuZCBzdXBwb3J0Lg0KICAgIA0KICAgIEJlc3QNCiAgICBSYXkNCiAgICANCiAgICANCg0K


From nobody Mon Jun 12 13:43:07 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 467E9129AA4 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 13:43:05 -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 ijLC7hTuzsz2 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 13:43:03 -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 CA19E129A9D for <ietf@ietf.org>; Mon, 12 Jun 2017 13:43:03 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id x63so56263893pff.3 for <ietf@ietf.org>; Mon, 12 Jun 2017 13:43:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=9wTbnn+fTbuRmDSVrn0fVEJRaTToGLru/CgXgtEy4tg=; b=AyFL1pGeuDG1Eoh4JkUB/8Sw0Ke0AZZqhJ9VcPmD3yu8EGzDBRi5Ip22/57RXnZswh 25rjzrGyeDkweyZpj8MvXt4tGOtybcnjAI3n6EBDcXGL5cmzyKv7aykhnbhdSA7KJldL 3fiqAnAxlIFOo0/qMY2frirmsgJ05fq9KTTH+URMfA4iBHNcdFr+lsyE7Jd1JlXChK75 jv+jmMFS+IQNFzc7ju0sK3SGXP7sgrzQrNOAL16tVLpR7pZGN2o9btLFGawkroFPCVTP VPGa5LQurbL4xwf3E2zMJX10AIZa4g948Rb4Bbs/fU0L5yaBqeL81LS4BbqUKSkrEgDX nCWw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=9wTbnn+fTbuRmDSVrn0fVEJRaTToGLru/CgXgtEy4tg=; b=gEdRi8+sCw/euSQ/ONy0z8Ho/VMIDJn1KCbSKJo+bRqK9qM02weFS/UqIbH5yCamhL 6QIXivTXzfwOw5GRPYOww788FqLWq5MhxBI1c4bL3NRQdUDnR6+bXDt+h1RI0hOL0bMh mKm1YqUR8qgDINwgbfhWoqtZAgmDuEhZmfA8GIWvxGROpueGSm4j4vTU04ETb8UW0ORm BzJ3HegDzyw2kGPGMbwjKHGQZBrx2rYCXQnUX+Z1A+4eAwYmJsa4VhODEs4/vXt3HzLC neJe91C4mlcc/VbRBGJ0uAYJkPxxpV7DPE8bw5GPKl9iZcN3D5/GOcEV8gdFWVXMkDiB o7QQ==
X-Gm-Message-State: AODbwcAV3tTc9yUoRqHAHJuBl9U9/E05mNZ0allL5wviXlyHgWzlJ2zw su4vIFmkpAgkjyUoXmc=
X-Received: by 10.84.224.6 with SMTP id r6mr57565888plj.132.1497300183276; Mon, 12 Jun 2017 13:43:03 -0700 (PDT)
Received: from ?IPv6:2406:e007:7b4b:1:28cc:dc4c:9703:6781? ([2406:e007:7b4b:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id t20sm21245828pgo.29.2017.06.12.13.43.01 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 12 Jun 2017 13:43:02 -0700 (PDT)
Subject: Re: IAD Retirement
To: ietf@ietf.org
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <77b44755-0da4-6058-3ef0-879923739c6e@gmail.com>
Date: Tue, 13 Jun 2017 08:43:00 +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: <149727427537.10333.7649103852167051395.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/-sXDnnpI9ua5W1jwVqdxgo_2-sQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 20:43:05 -0000

We tend to complain a lot in the IETF. So I'm going to complain:
The IETF won't be the same without Ray.

Thanks for everything, especially for acting as a very helpful,
cheerful and efficient complaints desk.

Very best wishes.
   Brian Carpenter

On 13/06/2017 01:31, IETF Administrative Director wrote:
> All,
> 
> I will be retiring from the position of IETF Administrative Director
> on 31 October 2017.
> 
> On 1 June I concluded 12 years as IAD, member of the IAOC and
> trustee of the IETF Trust.
> 
> I accepted this position because I believed in the mission of the
> IETF and its importance to people worldwide. It has been an honor
> and a privilege to have supported the IETF in this capacity.
> 
> Thanks for your patience, feedback, and support.
> 
> Best
> Ray
> 
> .
> 


From nobody Mon Jun 12 13:52:30 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 01F1E129AB0 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 13:52:29 -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 wfYBH4S2HKqS for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 13:52:27 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04CAB1250B8 for <ietf@ietf.org>; Mon, 12 Jun 2017 13:52:27 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id w1so142342826qtg.2 for <ietf@ietf.org>; Mon, 12 Jun 2017 13:52:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=3XKovl3Kp+S6EerIx5qUWyJnK7RvWUynStTKI+8YACc=; b=RcATtXvdBZaBKTW1sLK+4VFNF6qxQ3h+F0w/yKOJZc8Ms9bJdMJE1W5b1J1nbWhJIs cqNZTbRfVgOupL39xVKhaPLH0Q9K0eLO+Nz/xlkC9Wr7ow4ofvvNLmpjQ5Q0Dt0JYI9M yo7hnaZdg1rZl6TRJf+mO0PuM1z3fP9AwGz7sBhajuMd1lE5hHssPKsatlVuLCuw83nd NGjJ9OpToMGejQ01fzg6ZoegOAtZdhLHid1b6OPuynWkNXuucFKhWENo5xXwT59gtoS6 CSSgLYd5vhkwWkKIQLREh99klEvKQPupWJv6h120NssEfnXF9Y0GAOuJoxLtr60xc9yy iQUQ==
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=3XKovl3Kp+S6EerIx5qUWyJnK7RvWUynStTKI+8YACc=; b=V2Kbk/Fz8hDGc+Zk2PjFdNqTEYH1aQgK7wGoTsZHRunzvAn6AAKOsJFoBBBdDRmZ6D zuPfkOOc11TSpGtnYeCnb6HTVZFCN2JQD+I7sj+eFjQEsLsPFSVYYZuiaYmjFWXM5C6U IVkl1qLNIepVfU2nyfPUYkyi61WOZKI64IE4AQP2euT8xc7OofrKh2zsSsB8caa/RdaL BTyEBmFWpaMix5PyOV15eK1yHCLajG3Gc8qtSmK2YaeF12lZYbmUu+Z0rSDwKPtxwptp O9GPzOja9Sqq/rRlMT7i7bwtjt+Egiq+SdvviX78oM6KY30xWfIy7PZwrRDr4p/UgAch BIIQ==
X-Gm-Message-State: AKS2vOypdUAAOj/UBuoYKb5CVWHUbrn06s3qdrEg/wt+dPd8UCDfZDgL AbWV2nC8iNGoJv0+V+c/PRDf/w5B/mSb
X-Received: by 10.55.9.6 with SMTP id 6mr9847822qkj.163.1497300745813; Mon, 12 Jun 2017 13:52:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.34.9 with HTTP; Mon, 12 Jun 2017 13:51:55 -0700 (PDT)
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 12 Jun 2017 13:51:55 -0700
Message-ID: <CA+9kkMBEhHGYPHupJ4=hCQ3zTb91ArA45frNwGLHxsDYonMSww@mail.gmail.com>
Subject: Blog entry on RFC 4084 and thoughts on a bis
To: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1148bdfa13994b0551c97f5b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ixQ4IxM0tPgOLRyTQKXVzvIYUa8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 20:52:29 -0000

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

Howdy,

In response to a discussion that came up between the IESG and IAB, I put
together the following blog entry:

https://www.ietf.org/blog/2017/06/what-does-internet-access-mean/

It will also be published in the upcoming IETF journal in a largely similar
form.  Both end with an invitation to comment on contribute at
architecture-discuss@iab.org; please do!

regards,

Ted Hardie
IAB

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

<div dir=3D"ltr"><div>Howdy,<br><br></div>In response to a discussion that =
came up between the IESG and IAB, I put together the following blog entry:<=
br><div><div><br><a href=3D"https://www.ietf.org/blog/2017/06/what-does-int=
ernet-access-mean/">https://www.ietf.org/blog/2017/06/what-does-internet-ac=
cess-mean/</a><br><br></div><div>It will also be published in the upcoming =
IETF journal in a largely similar form.=C2=A0 Both end with an invitation t=
o comment on contribute at <a href=3D"mailto:architecture-discuss@iab.org">=
architecture-discuss@iab.org</a>; please do!<br><br></div><div>regards,<br>=
<br></div><div>Ted Hardie<br></div><div>IAB<br></div></div></div>

--001a1148bdfa13994b0551c97f5b--


From nobody Mon Jun 12 14:28:13 2017
Return-Path: <Xufeng_Liu@jabil.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AB35128B51; Mon, 12 Jun 2017 14:28:11 -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=jabil.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 1CoZ81KPCPf7; Mon, 12 Jun 2017 14:28:07 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0131.outbound.protection.outlook.com [104.47.34.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 C5702128990; Mon, 12 Jun 2017 14:28:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jabil.onmicrosoft.com;  s=selector1-jabil-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=qIm0XoFtiZvMR95Bc16QPGl9th6ReOG2ELOyXEm60Ys=; b=m8CVmB3cROjre9SyLv0TDIOsE3OPXCtshJWA+zDq7+SNQ++358Nu/OBYw6TWMFmQ+tnUg2aQlnffNutu+rABDWBSvqTng2tRp1B16fPVUGWfQWFCOloAVH9r/LUq5HYZfnchnlryVOyyFb5Nvcffsl7ki9RASM5aaGW33iurz3Q=
Received: from BN3PR0201MB0867.namprd02.prod.outlook.com (10.160.154.13) by BN3PR0201MB0868.namprd02.prod.outlook.com (10.160.154.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1157.12; Mon, 12 Jun 2017 21:28:01 +0000
Received: from BN3PR0201MB0867.namprd02.prod.outlook.com ([10.160.154.13]) by BN3PR0201MB0867.namprd02.prod.outlook.com ([10.160.154.13]) with mapi id 15.01.1157.017; Mon, 12 Jun 2017 21:28:01 +0000
From: Xufeng Liu <Xufeng_Liu@jabil.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "draft-ietf-teas-yang-te-topo.all@ietf.org" <draft-ietf-teas-yang-te-topo.all@ietf.org>
Subject: RE: Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Thread-Topic: Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Thread-Index: AQHS1KSedaTR9X/fGEeQz0ke1nZ/sKIh1Ejw
Date: Mon, 12 Jun 2017 21:28:01 +0000
Message-ID: <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com>
In-Reply-To: <149564066257.28529.12761629961042171907@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-dg-ref: PG1ldGE+PGF0IG5tPSJib2R5LnR4dCIgcD0iYzpcdXNlcnNceGxpdVxhcHBkYXRhXHJvYW1pbmdcMDlkODQ5YjYtMzJkMy00YTQwLTg1ZWUtNmI4NGJhMjllMzViXG1zZ3NcbXNnLTAwOWM3YWRkLTRmYjYtMTFlNy05YzE0LTE4NWUwZmUzYzQ1Y1xhbWUtdGVzdFwwMDljN2FkZS00ZmI2LTExZTctOWMxNC0xODVlMGZlM2M0NWNib2R5LnR4dCIgc3o9IjEzNzAzIiB0PSIxMzE0MTc3NjQ3ODg3OTk0MzAiIGg9ImhheE1tTUo2OTZuaUdjai9PN1c2eGNKYXN1UT0iIGlkPSIiIGJsPSIwIiBibz0iMSIvPjwvbWV0YT4=
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=jabil.com;
x-originating-ip: [98.191.72.170]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0201MB0868; 7:hIxx/39NgnVDq6LMrqFpHPvYyDpnUmYUfWNLqi4jIWWTjGeGZbj8Ehe2PZ7TQjhW/c0SY+afRItZI5NEoi0fWNhGBue+hjSQsbxYLkEJti9+cz4/zC7zqfxwFjJQ9dryXv1oqfQ1ZWzYDWR1OB7CJrKvKlEMiKTXVx896zAB1+j1MhlgbvPVqPhszwrWEmUwPBSgiODhRGng+RFbRUC6C4/CAp+jAkoO5ZG/nr3EGJrla/cmljtGKA2m5mG/k1uW33MdReyBjwzzC3spQCpFWxewVQ4LbeptZDoZ+hnvEB4+EN6DMeLwhyHifwucZWMyZG/BB+wTX4Fqg50BpiYMgA==
x-ms-traffictypediagnostic: BN3PR0201MB0868:
x-ms-office365-filtering-correlation-id: 0d486f36-093c-4a0b-5991-08d4b1d9e74f
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081)(201702281549075); SRVR:BN3PR0201MB0868; 
x-microsoft-antispam-prvs: <BN3PR0201MB0868071B3E8C1F6D4097E2D7F1CD0@BN3PR0201MB0868.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(100000703101)(100105400095)(6055026)(6041248)(20161123555025)(20161123558100)(20161123560025)(20161123562025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN3PR0201MB0868; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN3PR0201MB0868; 
x-forefront-prvs: 03361FCC43
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(6009001)(39450400003)(39840400002)(39860400002)(39850400002)(39400400002)(39410400002)(13464003)(377454003)(7736002)(2950100002)(38730400002)(53546009)(6246003)(2501003)(305945005)(77096006)(7696004)(2900100001)(33656002)(74316002)(66066001)(4326008)(14454004)(25786009)(122556002)(53936002)(81166006)(8676002)(72206003)(8936002)(9686003)(55016002)(3846002)(54906002)(6436002)(478600001)(229853002)(6306002)(189998001)(80792005)(99286003)(86362001)(6506006)(3280700002)(3660700001)(2906002)(230783001)(39060400002)(6116002)(102836003)(50986999)(5660300001)(76176999)(54356999)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0201MB0868; H:BN3PR0201MB0867.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: jabil.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Jun 2017 21:28:01.1589 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bc876b21-f134-4c12-a265-8ed26b7f0f3b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0201MB0868
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hRiL3BeNwxlzvARXUJsTjilmHlk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 21:28:11 -0000

SGkgTWFoZXNoLA0KDQpUaGFuayB5b3UgbXVjaCBmb3IgdGhlIHJldmlldy4gV2UgaGF2ZSBzdWJt
aXR0ZWQgYW4gdXBkYXRlZCBkcmFmdCAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LWlldGYtdGVhcy15YW5nLXRlLXRvcG8tMDkpIHRvIGFkZHJlc3MgdGhlc2UgaXNzdWVzLiBNb3Jl
IGRldGFpbGVkIGV4cGxhbmF0aW9ucyBhcmUgcHV0IGJlbG93IGlubGluZS4gDQoNCklmIHRoZSBy
ZXNwb25zZXMgYW5kIHVwZGF0ZXMgYXJlIHNhdGlzZmFjdG9yeSwgd2UgYXJlIHJlYWR5IGZvciB0
aGUgbGFzdCBjYWxsLg0KDQpCZXN0IHJlZ2FyZHMsDQotIFh1ZmVuZw0KDQo+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IE1haGVzaCBKZXRoYW5hbmRhbmkgW21haWx0bzptamV0
aGFuYW5kYW5pQGdtYWlsLmNvbV0NCj4gU2VudDogV2VkbmVzZGF5LCBNYXkgMjQsIDIwMTcgMTE6
NDQgQU0NCj4gVG86IHlhbmctZG9jdG9yc0BpZXRmLm9yZw0KPiBDYzogaWV0ZkBpZXRmLm9yZzsg
dGVhc0BpZXRmLm9yZzsgZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby5hbGxAaWV0Zi5vcmcN
Cj4gU3ViamVjdDogWWFuZ2RvY3RvcnMgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLXRl
YXMteWFuZy10ZS10b3BvLTA4DQo+IA0KPiBSZXZpZXdlcjogTWFoZXNoIEpldGhhbmFuZGFuaQ0K
PiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KPiANCj4gRG9jdW1lbnQgcmV2aWV3
ZWQ6IGRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8tMDgNCj4gDQo+IFN0YXR1czogUmVhZHkg
d2l0aCBJc3N1ZXMNCj4gDQo+IEkgYW0gbm90IGFuIGV4cGVydCBpbiBUcmFmZmljIEVuZ2luZWVy
aW5nLiBUaGlzIHJldmlldyBpcyBsb29raW5nIGF0IHRoZSBkcmFmdCBmcm9tDQo+IGEgWUFORyBw
ZXJzcGVjdGl2ZS4gV2l0aCB0aGF0IHNhaWQsIEkgaGF2ZSBtYXJrZWQgaXQgYXMg4oCcUmVhZHkg
d2l0aCBJc3N1ZXPigJ0NCj4gYmVjYXVzZSBvZiBzb21lIG9mIHRoZSBwb2ludHMgZGlzY3Vzc2Vk
IGJlbG93Lg0KPiANCj4gU3VtbWFyeToNCj4gDQo+IFRoaXMgZG9jdW1lbnQgZGVmaW5lcyBhIFlB
TkcgZGF0YSBtb2RlbCBmb3IgcmVwcmVzZW50aW5nLCByZXRyaWV2aW5nIGFuZA0KPiBtYW5pcHVs
YXRpbmcgVEUgVG9wb2xvZ2llcy4gVGhlIG1vZGVsIHNlcnZlcyBhcyBhIGJhc2UgbW9kZWwgdGhh
dCBvdGhlcg0KPiB0ZWNobm9sb2d5IHNwZWNpZmljIFRFIFRvcG9sb2d5IG1vZGVscyBjYW4gYXVn
bWVudC4NCj4gDQo+IENvbW1lbnRzOg0KPiANCj4gQWxtb3N0IGFsbCB0aGUgY29udGFpbmVycyBp
biB0aGUgbW9kZWwgYXJlIHByZXNlbmNlIGNvbnRhaW5lcnMuIElzIHRoZXJlIGEgcmVhc29uDQo+
IHdoeSB0aGV5IGhhdmUgdG8gYmUgcHJlc2VuY2UgY29udGFpbmVycz8gTm90ZSwgdGhhdCBwcmVz
ZW5jZSBjb250YWluZXJzIGFyZQ0KPiBjb250YWluZXJzIHdob3NlIGV4aXN0ZW5jZSBpdHNlbGYg
cmVwcmVzZW50cyBjb25maWd1cmF0aW9uIGRhdGEuIFdoYXQgcGFydGljdWxhcg0KPiBjb25maWd1
cmF0aW9uIGRhdGEgaXMgZWFjaCBjb250YWluZXIgcmVwcmVzZW50aW5nIGluIGl0c2VsZj8NCltY
dWZlbmddIENvbnRhaW5lcnMgdGhhdCB1c2Ug4oCccHJlc2VuY2XigJ0gYXJlOg0KCS0gQ29udGFp
bmVyIOKAnHVuZGVybGF54oCdDQoJICBvICBXZSBoYXZlIGNoYW5nZWQgMTMgb2NjdXJyZW5jZXMg
b2Ygc3VjaCBjb250YWluZXJzIHRvIGJlIG5vdCBwcmVzZW5jZSBjb250YWluZXIuIA0KCS0gQ29u
dGFpbmVyIOKAnHRl4oCdIHVuZGVyIGF1Z21lbnRhdGlvbg0KCSAgbyAgVG8gaW5kaWNhdGUgdGhh
dCDigJxUReKAnSBpcyBlbmFibGVkIChjb25maWd1cmF0aW9uIGRhdGEpDQoJICBvICBBbHNvIHVz
ZWQgdG8gZG8gYXVnbWVudGF0aW9uLiBUaGUg4oCccHJlc2VuY2XigJ0gc3RhdGVtZW50IGNhbiBw
cmV2ZW50IHRoZSBtYW5kYXRvcnkgY2hpbGQgZnJvbSBhZmZlY3RpbmcgYXVnbWVudGVkIGJhc2Ug
bW9kZWwuDQoJLSAvbnc6bmV0d29ya3Mvbnc6bmV0d29yay9udzpuZXR3b3JrLXR5cGVzL3RlLXRv
cG9sb2d5IQ0KCSAgbyAgQSBtZWNoYW5pc20gcmVxdWlyZWQgYnkgSTJSUyB0b3BvbG9neSBtb2Rl
bCB0byBzcGVjaWZ5IHRoZSB0b3BvbG9neSB0eXBlLg0KDQo+IA0KPiBJdCBpcyBkaWZmaWN1bHQg
dG8gY28tcmVsYXRlIHRoZSBkaWFncmFtIHdpdGggdGhlIG1vZGVsIGl0c2VsZiBiZWNhdXNlIG9m
IGRpZmZlcmVudA0KPiB0ZXJtcyBiZWluZyB1c2VkIHRvIGRlZmluZSBkaWZmZXJlbnQgcGFydHMg
b2YgdGhlIG1vZGVsLg0KPiBUaGVyZSBpcyDigJxURSBUb3BvbG9neSBNb2RlbOKAnSBhbmQgdGhl
biB0aGVyZSBpcyDigJxHZW5lcmljIFRFIFRvcG9sb2d5IE1vZGVs4oCdLg0KPiBBcmUgdGhlc2Ug
b25lIGFuZCB0aGUgc2FtZSBtb2RlbHM/IElmIHNvLCBhIGNvbW1vbiB0ZXJtIGZvciBib3RoIG9m
IHRoZW0NCj4gd291bGQgYmUgaGVscGZ1bC4NCltYdWZlbmddIFllcy4gVGhlc2UgdHdvIHRlcm1z
IGFyZSB0aGUgc2FtZS4gRmlndXJlIDEyLCBGaWd1cmUgMTMsIGFuZCByZWxldmFudCBkZXNjcmlw
dGlvbnMgaGF2ZSBiZWVuIHVwZGF0ZWQgdG8gbWFrZSB0aGUgZG9jdW1lbnQgY29uc2lzdGVudC4N
Cg0KPiANCj4gVGhlcmUgaXMgZXh0ZW5zaXZlIHVzZSBvZiBncm91cGluZ3MgaW4gdGhlIGRvY3Vt
ZW50LiBIb3dldmVyLCBub3QgYWxsIGluc3RhbmNlcw0KPiBvZiBncm91cGluZ3MgYXJlIHVzZWQg
bXVsdGlwbGUgbnVtYmVyIG9mIHRpbWVzLiBXaGVyZSB0aGV5IGFyZSBub3QgYmVpbmcNCj4gcmVw
ZWF0ZWQsIGl0IHdvdWxkIGJlIGJldHRlciB0byBtb3ZlIHRoZSBncm91cGluZyBkaXJlY3RseSB3
aGVyZSB0aGUgdXNlcw0KPiBzdGF0ZW1lbnQgcmVzaWRlcy4gQ2FzZSBpbiBwb2ludCB0aGUgZ3Jv
dXBpbmcgY29ubmVjdGl2aXR5LWxhYmVsLXJlc3RyaWN0aW9uLWxpc3QuDQpbWHVmZW5nXSBXZSBo
YXZlIHJlbW92ZWQgdGhlIGZvbGxvd2luZyBncm91cGluZ3MNCiAgICB0ZS1saW5rLWF1Z21lbnQN
CiAgICB0ZS1ub2RlLWF1Z21lbnQNCiAgICB0ZS10ZXJtaW5hdGlvbi1wb2ludC1hdWdtZW50DQog
ICAgdGUtdG9wb2xvZ2llcy1hdWdtZW50DQogICAgdGUtdG9wb2xvZ3ktYXVnbWVudA0KICAgIHRl
LWxpbmstc3RhdGUtdW5kZXJsYXktYXR0cmlidXRlcw0KICAgIHRlLW5vZGUtc3RhdGUtZGVyaXZl
ZC1ub3RpZmljYXRpb24NCiAgICB0ZS10b3BvbG9neS10eXBlDQoNClRoZSByZW1haW5pbmcgZ3Jv
dXBpbmdzIGhhdmUgYmVlbiBrZXB0IHNvIHRoYXQgd2UgY2FuOg0KCS0gU2hhcmUgdGhlIGdyb3Vw
aW5ncyBpbiB0aGlzIG1vZGVsDQoJLSBQcmVwYXJlIHRvIGJlIHNoYXJlZCBieSBhIG1vZGVsIGF1
Z21lbnRpbmcgdGhpcyBtb2RlbA0KCS0gUHJldmVudCBhIGdyb3VwaW5nIG9yIGNvbmZpZ3VyYXRp
b24gc2VjdGlvbiBmcm9tIGJlaW5nIHRvbyBsb25nDQoJLSBJbXByb3ZlIHJlYWRhYmlsaXR5DQoN
Cj4gDQo+IFRoZSBzcGxpdCBiZXR3ZWVuIGNvbmZpZyBhbmQgc3RhdGUgY29udGFpbmVycyBkb2Vz
IG5vdCBzZWVtIHRvIGZvbGxvdyBhbnkNCj4gcGFydGljdWxhciBwYXR0ZXJuLiANCltYdWZlbmdd
IFRoZSBwYXR0ZXJuIGlzIGNsZWFyOg0KRm9yIGVhY2ggbWFuYWdlYWJsZSBlbnRpdHkgKG9iamVj
dCksIHRoZXJlIGlzIGEgY29uZmlnIGNvbnRhaW5lciBhbmQgc3RhdGUgY29udGFpbmVyLiBUaGUg
Y29uZmlndXJhYmxlIHByb3BlcnRpZXMgZ28gaW50byB0aGUgY29uZmlnIGNvbnRhaW5lciBhbmQg
c3RhdGUgcHJvcGVydGllcyBnbyBpbnRvIHRoZSBzdGF0ZSBjb250YWluZXIuIFN1Y2ggb2JqZWN0
cyBhcmUgaWRlbnRpZmllZCBieSBhIGxpc3QgaXRlbSBvciBhIHByZXNlbmNlIGNvbnRhaW5lciBz
byB0aGF0IHRoZSDigJxjcmVhdGXigJ0sIOKAnGRlbGV0ZeKAnSwgYW5kIOKAnG1vZGlmeeKAnSBv
cGVyYXRpb25zIGNhbiBiZSBwZXJmb3JtZWQgb24gdGhlbS4gVGhlIG5vbi1wcmVzZW5jZSBjb250
YWluZXJzIGRvIG5vdCByZXByZXNlbnQgY29uZmlndXJhdGlvbiBkYXRhIHNvIHRoZXkgZG8gbm90
IGludHJvZHVjZSBzdWNoIG9iamVjdHMuDQoNCj4gSXQgaXMgbmVpdGhlciBhIHRvcCBsZXZlbCBz
cGxpdCwgYXMgaXMgdGhlIGNhc2Ugd2l0aCBleGlzdGluZyBJRVRGDQo+IG1vZGVscywgDQpbWHVm
ZW5nXSBXZSBjb3VsZCBub3QgZG8gdG9wIGxldmVsIHNwbGl0IGJlY2F1c2UgdGhlIGJhc2UgSTJS
UyBuZXR3b3JrIHRvcG9sb2d5IG1vZGVsIChodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJh
ZnQtaWV0Zi1pMnJzLXlhbmctbmV0d29yay10b3BvLTEyKSB0aGF0IHdlIGF1Z21lbnQgZG9lcyBu
b3QgaGF2ZSB0aGUgdG9wLWxldmVsIHNwbGl0IChmb3IgaXRzIG93biByZWFzb25zKS4NCg0KPiBu
b3IgZG8gdGhleSBmb2xsb3cgdGhlIE9wZW5Db25maWcgc3R5bGUgb2Ygc3BsaXR0aW5nIGNvbmZp
ZyBhbmQgc3RhdGUNCj4gdW5kZXIgZWFjaCByZWxldmFudCBsZWFmLCANCltYdWZlbmddIFRoZSBw
YXR0ZXJuIGlzIGNvbnNpc3RlbnQgd2l0aCB0aGlzIHN0eWxlIGluIHByaW5jaXBsZSwgd2l0aCBz
b21lIGFkanVzdG1lbnRzIHRvIGZpdCB0byBvdXIgbXVsdGlwbGUgbGV2ZWxzIG9mIGhpZXJhcmNo
eS4NCg0KPiBub3IgZG8gdGhleSBmb2xsb3cgdGhlIG5ldyBndWlkZWxpbmVzIGFzIHN1Z2dlc3Rl
ZCBieQ0KPiB0aGUgbmV3IGRhdGFzdG9yZSBtb2RlbCBkcmFmdCAoaHR0cHM6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWRzZHQtbm1kYS0NCj4gZ3VpZGVsaW5lcy0wMS5odG1sKS4NCj4gU2lu
Y2UgdGhlcmUgcmVjb21tZW5kYXRpb24gZm9yIGFsbCBuZXcgbW9kZWxzIGlzIHRvIGZvbGxvdyB0
aGUgbmV3IGRhdGFzdG9yZQ0KPiBndWlkZWxpbmVzLCB3b3VsZCBzdWdnZXN0IHRoYXQgdGhlIHN0
YXRlIGNvbnRhaW5lcnMgYmUgcmVtb3ZlZCBhbmQgYW55IG5vbi0NCj4gZHVwbGljYXRlIGxlYWZz
IHdpdGhpbiBzdGF0ZSBiZSBtb3ZlZCB1bmRlciBhIHNpbmdsZSBjb250YWluZXIuIEkgYW0gdG9s
ZCB0aGF0IHRoZQ0KPiBjaGFuZ2UgaW4gaWV0Zi10ZS10b3BvbG9neSBmcm9tIHRoZSBjdXJyZW50
IGRyYWZ0IHRvIE5NREEgc3R5bGUgaXMgYWJvdXQgMTc1DQo+IGxpbmVzIGFuZCBmb3IgdGUtdHlw
ZXMgaXQgaXMgMjQgbGluZSBkaWZmICh0aGFua3MgUm9iZXJ0KS4gQXMgc3VjaCwgdGhlIGNoYW5n
ZSBpcyBub3QNCj4gbWFqb3IgYW5kIGNhbiBiZSBkb25lIGVhc2lseS4gU2VlIHRoZSBkaWZmcyBh
dCB0aGUgZW5kIG9mIHRoaXMgcmV2aWV3Lg0KW1h1ZmVuZ10gVGhlIGNoYW5nZXMgYXJlIHNpbXBs
ZSwgYnV0IHRoZSBpbXBsaWNhdGlvbnMgYXJlIG5vdDoNCglvICBOZWVkIHRvIHJlLW9wZW4gdGhl
IGRpc2N1c3Npb25zIGZvciB0aGUgSTJSUyBuZXR3b3JrIHRvcG9sb2d5IG1vZGVsIChodHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1pMnJzLXlhbmctbmV0d29yay10b3BvLTEy
KSwgd2hpY2ggY3VycmVudGx5IGRvZXMgbm90IGhhdmUgdGhlIHN0YXRlIGJyYW5jaCwgYW5kIGlz
IHRoZSBiYXNlIG1vZGVsIHRoYXQgdGhpcyBtb2RlbCBhdWdtZW50cy4NCglvICBOZWVkIHRvIHJl
LWRpc2N1c3MgdGhlIGlzc3VlcyBvZiBjcm9zcyByZWZlcmVuY2luZyBiZXR3ZWVuIGNvbmZpZyBi
cmFuY2ggYW5kIHN0YXRlIGJyYW5jaCAod2hpY2ggd2FzIGJyb3VnaHQgdXAgYnkgSTJSUyBtb2Rl
bCBhbmQgaGFzIG5vIGdvb2Qgc29sdXRpb24gY3VycmVudGx5KS4NCglvICBOZWVkIHRvIG1vZGlm
eSBleGlzdGluZyBhbmQgb24tZ29pbmcgaW1wbGVtZW50YXRpb25zIHdpdGggbm8gZnVuY3Rpb25h
bCBiZW5lZml0cy4NCglvICBXaWxsIGRlbGF5IHB1Ymxpc2hpbmcgYm90aCB0aGUgSTJSUyBiYXNl
IG5ldHdvcmsgdG9wb2xvZ3kgbW9kZWwgYW5kIHRoaXMgZG9jdW1lbnQuDQoNClRoaXMgcHJvcG9z
ZWQgbW9kZWwgY3VycmVudGx5IGhhcyBtdWx0aXBsZSBvbi1nb2luZyBpbXBsZW1lbnRhdGlvbnMu
IEltcGxlbWVudGVycyB3aXNoIGZvciBhZHZhbmNpbmcgdGhpcyBkb2N1bWVudCB3aXRob3V0IHVu
bmVjZXNzYXJ5IGRlbGF5cywgYW5kIGJlZm9yZSB0aGUgZmluYWwgTkVUQ09ORi9SRVNUQ09OIHBy
b3RvY29sIHN1cHBvcnQgd2hpY2ggaXMgZXhwZWN0ZWQgdG8gYmUgYXZhaWxhYmxlIGluIGEgeWVh
ci4gDQoNClRoZSBhdXRob3JzIGFuZCBjb250cmlidXRlcyBoYXZlIGRpc2N1c3NlZCB0aGUgYWRv
cHRpb24gb2YgdGhlIE5NREEgc3R5bGUsIGFuZCBjdXJyZW50bHkgcHJlZmVyIHRoZSBmb2xsb3dp
bmcgc3RyYXRlZ3k6DQoJbyAgUHVibGlzaCB0aGUgZG9jdW1lbnQgd2l0aCB0aGUgY3VycmVudCBt
b2RlbCBzdHlsZSB3aXRob3V0IHN0cnVjdHVyZSBjaGFuZ2VzLCBhbGxvd2luZyB0aGUgb24tZ29p
bmcgaW1wbGVtZW50YXRpb25zIHRvIGNvbnRpbnVlLCBzdXBwb3J0aW5nIG5lY2Vzc2FyeSBvcGVy
YXRpb25hbCBzdGF0ZXMgYmVmb3JlIHRoZSBOTURBIHByb3RvY29sIHNwZWNpZmljYXRpb24gaXMg
dXBkYXRlZCBhbmQgc3VwcG9ydGluZyBpbXBsZW1lbnRhdGlvbnMgYXJlIGF2YWlsYWJsZS4gDQoJ
byAgRm9sbG93IHRoaXMgdXAgQVNBUCB3aXRoIGFuIE5NREEtY29tcGF0aWJsZSBtb2RlbCBkcmFm
dCAoV0cgY291bGQgYWRvcHQgdGhpcyByaWdodCBhd2F5KS4gVGhpcyB3YXMgc3VnZ2VzdGVkIGJ5
IEtlbnQsIGFuZCBpcyBjb25zaWRlcmVkIHRvIGZpdCBvdXIgc2l0dWF0aW9uIHRoZSBiZXN0LCBh
bGxvd2luZyB0aGUgaW1wbGVtZW50YXRpb25zIHRvIG1pZ3JhdGUgdG8gdGhlIGxvbmcgdGVybSBh
cHByb2FjaCB3aXRob3V0IGludGVycnVwdGlvbi4NCg0KPiANCj4gQSBweWFuZyBjb21waWxhdGlv
biBvZiB0aGUgbW9kZWwgd2l0aCDigJRpZXRmIGFuZCDigJRsaW50IG9wdGlvbiB3YXMgY2xlYW4u
DQo+IA0KPiBBIGlkbml0cyBydW4gb2YgdGhlIGRyYWZ0IHJldmVhbHMgc29tZSBpc3N1ZXMgd2l0
aCBzcGFjaW5nIGFuZCByZWZlcmVuY2VzLCBidXQNCj4gdGhleSBhcmUgcGFydHMgb2YgdGhlIGRp
YWdyYW0sIHdoaWNoIGNvbmZ1c2VzIGlkbml0cy4NCj4gDQo+IHRlLXR5cGVzLmRpZmYNCj4g4oCU
4oCU4oCU4oCU4oCUDQo+IDUwNyw1MDljNTA3LDUwOQ0KPiA8ICAgZ3JvdXBpbmcgZXhwbGljaXQt
cm91dGUtaG9wX2NvbmZpZyB7DQo+IDwgICAgIGRlc2NyaXB0aW9uDQo+IDwgICAgICAgIlRoZSBl
eHBsaWNpdCByb3V0ZSBzdWJvYmplY3QgZ3JvdXBpbmciOw0KPiAtLS0NCj4gPiAgIGdyb3VwaW5n
IGV4cGxpY2l0LXJvdXRlLWhvcCB7DQo+ID4gICAgIGRlc2NyaXB0aW9uICJFeHBsaWNpdCByb3V0
ZSBob3AgZ3JvdXBpbmciOw0KPiA+DQo+IDU5NSw2MDlkNTk0DQo+IDwgICAgIH0NCj4gPCAgIH0N
Cj4gPA0KPiA8ICAgZ3JvdXBpbmcgZXhwbGljaXQtcm91dGUtaG9wIHsNCj4gPCAgICAgZGVzY3Jp
cHRpb24gIkV4cGxpY2l0IHJvdXRlIGhvcCBncm91cGluZyI7DQo+IDwgICAgIGNvbnRhaW5lciBj
b25maWcgew0KPiA8ICAgICAgIGRlc2NyaXB0aW9uDQo+IDwgICAgICAgICAiQ29uZmlndXJhdGlv
biBwYXJhbWV0ZXJzIGZvciB0aGUgZXhwbGljaXQgcm91dGUgaG9wIjsNCj4gPCAgICAgICB1c2Vz
IGV4cGxpY2l0LXJvdXRlLWhvcF9jb25maWc7DQo+IDwgICAgIH0NCj4gPCAgICAgY29udGFpbmVy
IHN0YXRlIHsNCj4gPCAgICAgICBjb25maWcgZmFsc2U7DQo+IDwgICAgICAgZGVzY3JpcHRpb24N
Cj4gPCAgICAgICAgICJTdGF0ZSBwYXJhbWV0ZXJzIGZvciB0aGUgZXhwbGljaXQgcm91dGUgaG9w
IjsNCj4gPCAgICAgICB1c2VzIGV4cGxpY2l0LXJvdXRlLWhvcF9jb25maWc7DQo+IA0KPiB0ZS10
b3BvbG9neS5kaWZmDQo+IOKAlOKAlOKAlOKAlOKAlOKAlC0NCj4gMjY0YTI2NQ0KPiA+ICAgICAg
IGNvbmZpZyBmYWxzZTsNCj4gMzIzYTMyNQ0KPiA+ICAgICAgIGNvbmZpZyBmYWxzZTsNCj4gMzI3
YTMzMA0KPiA+ICAgICAgIGNvbmZpZyBmYWxzZTsNCj4gMzU3YTM2MQ0KPiA+ICAgICAgIGNvbmZp
ZyBmYWxzZTsNCj4gMzYxYTM2Ng0KPiA+ICAgICAgIGNvbmZpZyBmYWxzZTsNCj4gNzMzLDc0NGM3
MzgsNzM5DQo+IDwgICAgICAgY29udGFpbmVyIGNvbmZpZyB7DQo+IDwgICAgICAgICBkZXNjcmlw
dGlvbg0KPiA8ICAgICAgICAgICAiQ29uZmlndXJhdGlvbiBkYXRhLiI7DQo+IDwgICAgICAgICB1
c2VzIHRlLWxpbmstY29uZmlnOw0KPiA8ICAgICAgIH0gLy8gY29uZmlnDQo+IDwgICAgICAgY29u
dGFpbmVyIHN0YXRlIHsNCj4gPCAgICAgICAgIGNvbmZpZyBmYWxzZTsNCj4gPCAgICAgICAgIGRl
c2NyaXB0aW9uDQo+IDwgICAgICAgICAgICJPcGVyYXRpb25hbCBzdGF0ZSBkYXRhLiI7DQo+IDwg
ICAgICAgICB1c2VzIHRlLWxpbmstY29uZmlnOw0KPiA8ICAgICAgICAgdXNlcyB0ZS1saW5rLXN0
YXRlLWRlcml2ZWQ7DQo+IDwgICAgICAgfSAvLyBzdGF0ZQ0KPiAtLS0NCj4gPiAgICAgICB1c2Vz
IHRlLWxpbmstY29uZmlnOw0KPiA+ICAgICAgIHVzZXMgdGUtbGluay1zdGF0ZS1kZXJpdmVkOw0K
PiA3ODAsNzgxYzc3NSw3NzYNCj4gPCAgICAgICAgICAgICAgICAgcGF0aCAiLi4vLi4vLi4vLi4v
Li4vLi4vbnc6bm9kZVtudzpub2RlLWlkID0gIg0KPiA8ICAgICAgICAgICAgICAgICAgICsgImN1
cnJlbnQoKS8uLi8uLi8uLi8uLi8uLi9udDpzb3VyY2UvIg0KPiAtLS0NCj4gPiAgICAgICAgICAg
ICAgICAgcGF0aCAiLi4vLi4vLi4vLi4vLi4vbnc6bm9kZVtudzpub2RlLWlkID0gIg0KPiA+ICAg
ICAgICAgICAgICAgICAgICsgImN1cnJlbnQoKS8uLi8uLi8uLi8uLi9udDpzb3VyY2UvIg0KPiA3
OTIsNzkzYzc4Nyw3ODgNCj4gPCAgICAgICAgICAgICAgICAgcGF0aCAiLi4vLi4vLi4vLi4vLi4v
Li4vbnc6bm9kZVtudzpub2RlLWlkID0gIg0KPiA8ICAgICAgICAgICAgICAgICAgICsgImN1cnJl
bnQoKS8uLi8uLi8uLi8uLi8uLi9udDpkZXN0aW5hdGlvbi8iDQo+IC0tLQ0KPiA+ICAgICAgICAg
ICAgICAgICBwYXRoICIuLi8uLi8uLi8uLi8uLi9udzpub2RlW253Om5vZGUtaWQgPSAiDQo+ID4g
ICAgICAgICAgICAgICAgICAgKyAiY3VycmVudCgpLy4uLy4uLy4uLy4uL250OmRlc3RpbmF0aW9u
LyINCj4gODQxYzgzNg0KPiA8ICAgICAgICAgcGF0aCAiLi4vLi4vLi4vLi4vLi4vdGUvdGVtcGxh
dGVzL2xpbmstdGVtcGxhdGUvbmFtZSI7DQo+IC0tLQ0KPiA+ICAgICAgICAgcGF0aCAiLi4vLi4v
Li4vLi4vdGUvdGVtcGxhdGVzL2xpbmstdGVtcGxhdGUvbmFtZSI7DQo+IDEwODdhMTA4Mw0KPiA+
ICAgICAgIGNvbmZpZyBmYWxzZTsNCj4gMTA5MmExMDg5DQo+ID4gICAgICAgY29uZmlnIGZhbHNl
Ow0KPiAxMTA2YTExMDQNCj4gPiAgICAgICBjb25maWcgZmFsc2U7DQo+IDExMTNhMTExMg0KPiA+
ICAgICAgIGNvbmZpZyBmYWxzZTsNCj4gMTEyOGExMTI4DQo+ID4gICAgICAgY29uZmlnIGZhbHNl
Ow0KPiAxMjY3LDEyNzljMTI2NywxMjY4DQo+IDwgICAgICAgY29udGFpbmVyIGNvbmZpZyB7DQo+
IDwgICAgICAgICBkZXNjcmlwdGlvbg0KPiA8ICAgICAgICAgICAiQ29uZmlndXJhdGlvbiBkYXRh
LiI7DQo+IDwgICAgICAgICB1c2VzIHRlLW5vZGUtY29uZmlnOw0KPiA8ICAgICAgIH0gLy8gY29u
ZmlnDQo+IDwgICAgICAgY29udGFpbmVyIHN0YXRlIHsNCj4gPCAgICAgICAgIGNvbmZpZyBmYWxz
ZTsNCj4gPCAgICAgICAgIGRlc2NyaXB0aW9uDQo+IDwgICAgICAgICAgICJPcGVyYXRpb25hbCBz
dGF0ZSBkYXRhLiI7DQo+IDwNCj4gPCAgICAgICAgIHVzZXMgdGUtbm9kZS1jb25maWc7DQo+IDwg
ICAgICAgICB1c2VzIHRlLW5vZGUtc3RhdGUtZGVyaXZlZDsNCj4gPCAgICAgICB9IC8vIHN0YXRl
DQo+IC0tLQ0KPiA+ICAgICAgIHVzZXMgdGUtbm9kZS1jb25maWc7DQo+ID4gICAgICAgdXNlcyB0
ZS1ub2RlLXN0YXRlLWRlcml2ZWQ7DQo+IDEyOTcsMTMwOWMxMjg2LDEyODcNCj4gPCAgICAgICAg
IGNvbnRhaW5lciBjb25maWcgew0KPiA8ICAgICAgICAgICBkZXNjcmlwdGlvbg0KPiA8ICAgICAg
ICAgICAgICJDb25maWd1cmF0aW9uIGRhdGEuIjsNCj4gPCAgICAgICAgICAgdXNlcyB0ZS1ub2Rl
LXR1bm5lbC10ZXJtaW5hdGlvbi1hdHRyaWJ1dGVzOw0KPiA8ICAgICAgICAgfQ0KPiA8ICAgICAg
ICAgY29udGFpbmVyIHN0YXRlIHsNCj4gPCAgICAgICAgICAgY29uZmlnIGZhbHNlOw0KPiA8ICAg
ICAgICAgICBkZXNjcmlwdGlvbg0KPiA8ICAgICAgICAgICAgICJPcGVyYXRpb25hbCBzdGF0ZSBk
YXRhLiI7DQo+IDwNCj4gPCAgICAgICAgICAgdXNlcyB0ZS1ub2RlLXR1bm5lbC10ZXJtaW5hdGlv
bi1hdHRyaWJ1dGVzOw0KPiA8ICAgICAgICAgICB1c2VzIGdlb2xvY2F0aW9uLWNvbnRhaW5lcjsN
Cj4gPCAgICAgICAgIH0gLy8gc3RhdGUNCj4gLS0tDQo+ID4gICAgICAgICB1c2VzIHRlLW5vZGUt
dHVubmVsLXRlcm1pbmF0aW9uLWF0dHJpYnV0ZXM7DQo+ID4gICAgICAgICB1c2VzIGdlb2xvY2F0
aW9uLWNvbnRhaW5lcjsNCj4gMTQwNmMxMzg0DQo+IDwgICAgICAgICBwYXRoICIuLi8uLi8uLi8u
Li8uLi90ZS90ZW1wbGF0ZXMvbm9kZS10ZW1wbGF0ZS9uYW1lIjsNCj4gLS0tDQo+ID4gICAgICAg
ICBwYXRoICIuLi8uLi8uLi8uLi90ZS90ZW1wbGF0ZXMvbm9kZS10ZW1wbGF0ZS9uYW1lIjsNCj4g
MTQ3MywxNDc0YzE0NTENCj4gPCAgICAgICAgICAgICAgIHBhdGggIi4uLy4uLy4uLy4uLy4uLy4u
Ly4uL250OnRlcm1pbmF0aW9uLXBvaW50LyIrDQo+IDwgICAgICAgICAgICAgICAgICJudDp0cC1p
ZCI7DQo+IC0tLQ0KPiA+ICAgICAgICAgICAgICAgcGF0aA0KPiAiLi4vLi4vLi4vLi4vLi4vLi4v
bnQ6dGVybWluYXRpb24tcG9pbnQvbnQ6dHAtaWQiOw0KPiAxNDg1LDE0ODZjMTQ2Mg0KPiA8ICAg
ICAgICAgICAgICAgcGF0aCAiLi4vLi4vLi4vLi4vLi4vLi4vLi4vbnQ6dGVybWluYXRpb24tcG9p
bnQvIisNCj4gPCAgICAgICAgICAgICAgICAgIm50OnRwLWlkIjsNCj4gLS0tDQo+ID4gICAgICAg
ICAgICAgICBwYXRoDQo+ICIuLi8uLi8uLi8uLi8uLi8uLi9udDp0ZXJtaW5hdGlvbi1wb2ludC9u
dDp0cC1pZCI7DQo+IDE1NzdhMTU1NA0KPiA+ICAgICAgIGNvbmZpZyBmYWxzZTsNCj4gMTU4M2Ex
NTYxDQo+ID4gICAgICAgY29uZmlnIGZhbHNlOw0KPiAxNTk1YTE1NzQNCj4gPiAgICAgICBjb25m
aWcgZmFsc2U7DQo+IDE3MzhjMTcxNw0KPiA8ICAgICAgICAgICAgIHBhdGggIi4uLy4uLy4uLy4u
Ly4uLy4uL250OnRlcm1pbmF0aW9uLXBvaW50L250OnRwLWlkIjsNCj4gLS0tDQo+ID4gICAgICAg
ICAgICAgcGF0aCAiLi4vLi4vLi4vLi4vLi4vbnQ6dGVybWluYXRpb24tcG9pbnQvbnQ6dHAtaWQi
Ow0KPiAxNzUzYzE3MzINCj4gPCAgICAgdXNlcyB0ZS10eXBlczpleHBsaWNpdC1yb3V0ZS1ob3Bf
Y29uZmlnOw0KPiAtLS0NCj4gPiAgICAgdXNlcyB0ZS10eXBlczpleHBsaWNpdC1yb3V0ZS1ob3A7
DQo+IDE3NzMsMTc3OWMxNzUyLDE3NTQNCj4gPCAgICAgICBjb250YWluZXIgY29uZmlnIHsNCj4g
PCAgICAgICAgIGRlc2NyaXB0aW9uDQo+IDwgICAgICAgICAgICJDb25maWd1cmF0aW9uIGRhdGEu
IjsNCj4gPCAgICAgICAgIHVzZXMgdGUtdGVybWluYXRpb24tcG9pbnQtY29uZmlnOw0KPiA8ICAg
ICAgIH0gLy8gY29uZmlnDQo+IDwgICAgICAgY29udGFpbmVyIHN0YXRlIHsNCj4gPCAgICAgICAg
IGNvbmZpZyBmYWxzZTsNCj4gLS0tDQo+ID4gICAgICAgdXNlcyBpbnRlcmZhY2Utc3dpdGNoaW5n
LWNhcGFiaWxpdHktbGlzdDsNCj4gPiAgICAgICBsZWFmIGludGVyLWxheWVyLWxvY2staWQgew0K
PiA+ICAgICAgICAgdHlwZSB1aW50MzI7DQo+IDE3ODEsMTc4NGMxNzU2LDE3NjUNCj4gPCAgICAg
ICAgICAgIk9wZXJhdGlvbmFsIHN0YXRlIGRhdGEuIjsNCj4gPCAgICAgICAgIHVzZXMgdGUtdGVy
bWluYXRpb24tcG9pbnQtY29uZmlnOw0KPiA8ICAgICAgICAgdXNlcyBnZW9sb2NhdGlvbi1jb250
YWluZXI7DQo+IDwgICAgICAgfSAvLyBzdGF0ZQ0KPiAtLS0NCj4gPiAgICAgICAgICAgIkludGVy
IGxheWVyIGxvY2sgSUQsIHVzZWQgZm9yIHBhdGggY29tcHV0YXRpb24gaW4gYSBURQ0KPiA+ICAg
ICAgICAgICAgdG9wb2xvZ3kgY292ZXJpbmcgbXVsdGlwbGUgbGF5ZXJzIG9yIG11bHRpcGxlIHJl
Z2lvbnMuIjsNCj4gPiAgICAgICAgIHJlZmVyZW5jZQ0KPiA+ICAgICAgICAgICAiUkZDNTIxMjog
UmVxdWlyZW1lbnRzIGZvciBHTVBMUy1CYXNlZCBNdWx0aS1SZWdpb24gYW5kDQo+ID4gICAgICAg
ICAgICBNdWx0aS1MYXllciBOZXR3b3JrcyAoTVJOL01MTikuDQo+ID4gICAgICAgICAgICBSRkM2
MDAxOiBHZW5lcmFsaXplZCBNUExTIChHTVBMUykgUHJvdG9jb2wgRXh0ZW5zaW9ucw0KPiBmb3IN
Cj4gPiAgICAgICAgICAgIE11bHRpLUxheWVyIGFuZCBNdWx0aS1SZWdpb24gTmV0d29ya3MgKE1M
Ti9NUk4pLiI7DQo+ID4gICAgICAgfQ0KPiA+DQo+ID4gICAgICAgdXNlcyBnZW9sb2NhdGlvbi1j
b250YWluZXI7DQo+IDE3ODcsMTgwMmQxNzY3DQo+IDwgICBncm91cGluZyB0ZS10ZXJtaW5hdGlv
bi1wb2ludC1jb25maWcgew0KPiA8ICAgICBkZXNjcmlwdGlvbg0KPiA8ICAgICAgICJURSB0ZXJt
aW5hdGlvbiBwb2ludCBjb25maWd1cmF0aW9uIGdyb3VwaW5nLiI7DQo+IDwgICAgIHVzZXMgaW50
ZXJmYWNlLXN3aXRjaGluZy1jYXBhYmlsaXR5LWxpc3Q7DQo+IDwgICAgIGxlYWYgaW50ZXItbGF5
ZXItbG9jay1pZCB7DQo+IDwgICAgICAgdHlwZSB1aW50MzI7DQo+IDwgICAgICAgZGVzY3JpcHRp
b24NCj4gPCAgICAgICAgICJJbnRlciBsYXllciBsb2NrIElELCB1c2VkIGZvciBwYXRoIGNvbXB1
dGF0aW9uIGluIGEgVEUNCj4gPCAgICAgICAgICB0b3BvbG9neSBjb3ZlcmluZyBtdWx0aXBsZSBs
YXllcnMgb3IgbXVsdGlwbGUgcmVnaW9ucy4iOw0KPiA8ICAgICAgIHJlZmVyZW5jZQ0KPiA8ICAg
ICAgICAgIlJGQzUyMTI6IFJlcXVpcmVtZW50cyBmb3IgR01QTFMtQmFzZWQgTXVsdGktUmVnaW9u
IGFuZA0KPiA8ICAgICAgICAgIE11bHRpLUxheWVyIE5ldHdvcmtzIChNUk4vTUxOKS4NCj4gPCAg
ICAgICAgICBSRkM2MDAxOiBHZW5lcmFsaXplZCBNUExTIChHTVBMUykgUHJvdG9jb2wgRXh0ZW5z
aW9ucw0KPiA8ICAgICAgICAgIGZvciBNdWx0aS1MYXllciBhbmQgTXVsdGktUmVnaW9uIE5ldHdv
cmtzIChNTE4vTVJOKS4iOw0KPiA8ICAgICB9DQo+IDwgICB9IC8vIHRlLXRlcm1pbmF0aW9uLXBv
aW50LWNvbmZpZw0KPiAxODc5LDE4OTBjMTg0NCwxODQ1DQo+IDwgICAgICAgY29udGFpbmVyIGNv
bmZpZyB7DQo+IDwgICAgICAgICBkZXNjcmlwdGlvbg0KPiA8ICAgICAgICAgICAiQ29uZmlndXJh
dGlvbiBkYXRhLiI7DQo+IDwgICAgICAgICB1c2VzIHRlLXRvcG9sb2d5LWNvbmZpZzsNCj4gPCAg
ICAgICB9IC8vIGNvbmZpZw0KPiA8ICAgICAgIGNvbnRhaW5lciBzdGF0ZSB7DQo+IDwgICAgICAg
ICBjb25maWcgZmFsc2U7DQo+IDwgICAgICAgICBkZXNjcmlwdGlvbg0KPiA8ICAgICAgICAgICAi
T3BlcmF0aW9uYWwgc3RhdGUgZGF0YS4iOw0KPiA8ICAgICAgICAgdXNlcyB0ZS10b3BvbG9neS1j
b25maWc7DQo+IDwgICAgICAgICB1c2VzIGdlb2xvY2F0aW9uLWNvbnRhaW5lcjsNCj4gPCAgICAg
ICB9IC8vIHN0YXRlDQo+IC0tLQ0KPiA+ICAgICAgIHVzZXMgdGUtdG9wb2xvZ3ktY29uZmlnOw0K
PiA+ICAgICAgIHVzZXMgZ2VvbG9jYXRpb24tY29udGFpbmVyOw0KPiANCj4gDQo+IA0KDQo=


From nobody Mon Jun 12 14:35:55 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 6E79012EB56 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 14:35:54 -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 nkzp-LhCSaBm for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 14:35:52 -0700 (PDT)
Received: from mail-qt0-x229.google.com (mail-qt0-x229.google.com [IPv6:2607:f8b0:400d:c0d::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ED1D127A91 for <ietf@ietf.org>; Mon, 12 Jun 2017 14:35:52 -0700 (PDT)
Received: by mail-qt0-x229.google.com with SMTP id u12so144531280qth.0 for <ietf@ietf.org>; Mon, 12 Jun 2017 14:35: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;  bh=6cHVNulsfKrvBD5wd2oVaC3mPHXQGBk7Cb5vBKtbdfo=; b=I7LNdvBdoZBPBLSvfZOmRjlnzypeK0fWghT6Yp6spEn+dwSBGUbUsI5eB6Pf8ArUuh ynVTmn/vK5KOD2OMlzD6jmjTKj8MtPKj8xb66QNkhd6E3wStv71Q/T5Q+uNgpUYupCQX NSaDS8hmYVeXlG1QNQo9gg2ZwpVmQvI3e6fGnIuWKVyrl9im6qSdPnLWlDrGHV80zTS2 B1FMDlrBJuFlIaZI2yzIFz3LPdTLIaVD/VNXUneXCJvpGFTDnWgpzH7QYRBWiu2ym6t/ AVgVMvjqk31q76nQ2+VkAszVuPSNzJjvmoIEQyHite2K0QuSv665OzQe4t6xi7I8P5Lo yRfw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=6cHVNulsfKrvBD5wd2oVaC3mPHXQGBk7Cb5vBKtbdfo=; b=DKMc+oKLwGkPB1aIvhOH3zjfWwCdJEfbC4Psckh8nkN3YwV1anxhyfDXtnRcXObB3f PlUYskcC+9y0jy4Kmb3k7+fkPOoQ3Rf2OOsqAoUk3KsNiUWRRF0aXcnCJCODtEyjZ3UF NwfWn6EK8dV45rANo4M4xtCmblsrj65/qF6/SRxE/xFM2RWgexVk6m6Fxp6538hLUwkI dNZoL/fp131+JR6FBofwUmVEVgSXjiM4Ko807QohyGE5dLAwmbVrnKrdS3MLnckRLzPH PpYZNuMeZ1il7UmPM0b28VuxTriOYgW2NFHv/I74K0wGIlmjZmeRumaXJ27y8RmJ3buh 9+hg==
X-Gm-Message-State: AKS2vOxhWaC8HSrveoJyYpaaoYFJlRap4JaYHZl/JfyrotdCipqfLN1T 8YRjQXTrsJWANgi80QaQvkJJ4vnLXQ==
X-Received: by 10.55.38.69 with SMTP id y66mr18550856qkg.226.1497303347986; Mon, 12 Jun 2017 14:35:47 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.31.101 with HTTP; Mon, 12 Jun 2017 14:35:47 -0700 (PDT)
In-Reply-To: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Tue, 13 Jun 2017 00:35:47 +0300
Message-ID: <CAFgnS4XcVPARjjjsTbU8=U2f4Umxiqpfnr3gUvqhyMDMR3YkgA@mail.gmail.com>
Subject: Re: IAD Retirement
To: ietf <ietf@ietf.org>, Ray Pelletier <rpelletier@isoc.org>
Content-Type: multipart/alternative; boundary="001a114559d82dd3920551ca1a17"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/14rH8dZZKAV_1RrjA63yUpWR1ps>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 12 Jun 2017 21:35:54 -0000

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

Hi Ray,

It's been a privilege to know you and to work with you. Thank you for your
exemplary service. Enjoy your next steps and keep in touch.

Regards,

Dan


On Mon, Jun 12, 2017 at 4:31 PM, IETF Administrative Director <iad@ietf.org>
wrote:

> All,
>
> I will be retiring from the position of IETF Administrative Director
> on 31 October 2017.
>
> On 1 June I concluded 12 years as IAD, member of the IAOC and
> trustee of the IETF Trust.
>
> I accepted this position because I believed in the mission of the
> IETF and its importance to people worldwide. It has been an honor
> and a privilege to have supported the IETF in this capacity.
>
> Thanks for your patience, feedback, and support.
>
> Best
> Ray
>
>

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

<div dir=3D"ltr"><div><div><div>Hi Ray,<br><br></div>It&#39;s been a privil=
ege to know you and to work with you. Thank you for your exemplary service.=
 Enjoy your next steps and keep in touch. <br><br></div>Regards,<br><br></d=
iv>Dan<br><br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On Mon, Jun 12, 2017 at 4:31 PM, IETF Administrative Director <span dir=
=3D"ltr">&lt;<a href=3D"mailto:iad@ietf.org" target=3D"_blank">iad@ietf.org=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br>
<br>
I will be retiring from the position of IETF Administrative Director<br>
on 31 October 2017.<br>
<br>
On 1 June I concluded 12 years as IAD, member of the IAOC and<br>
trustee of the IETF Trust.<br>
<br>
I accepted this position because I believed in the mission of the<br>
IETF and its importance to people worldwide. It has been an honor<br>
and a privilege to have supported the IETF in this capacity.<br>
<br>
Thanks for your patience, feedback, and support.<br>
<br>
Best<br>
Ray<br>
<br>
</blockquote></div><br></div>

--001a114559d82dd3920551ca1a17--


From nobody Mon Jun 12 20:39:02 2017
Return-Path: <heas@shrubbery.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 876EE129B22 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 20:39:01 -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_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 1O_RY8yIm5ol for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 20:38:59 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCD8A129B18 for <ietf@ietf.org>; Mon, 12 Jun 2017 20:38:59 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 802108DB91; Tue, 13 Jun 2017 03:38:59 +0000 (UTC)
Date: Tue, 13 Jun 2017 03:38:59 +0000
From: heasley <heas@shrubbery.net>
To: ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Message-ID: <20170613033859.GA71771@shrubbery.net>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <149727416998.10345.14056211125888203672@ietfa.amsl.com>
User-Agent: Mutt/1.8.0 (2017-02-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_rSjHuanbPvLoYb1QXDYo5MMnQE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 03:39:01 -0000

Mon, Jun 12, 2017 at 06:29:30AM -0700, internet-drafts@ietf.org:
>         Title           : The Harmful Consequences of Postel's Maxim
> https://tools.ietf.org/html/draft-thomson-postel-was-wrong-01

Perhaps instead of requiring two implementations for a protocol draft to
proceed to rfc, it should first or also have a test suite that

        ... fails noisily in response to bad or undefined inputs.

Having a community-developed test suite for any protocol would be a great
asset.


From nobody Mon Jun 12 20:50:00 2017
Return-Path: <marwa_simohamed@yahoo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 01E52129B26 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 20:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.09
X-Spam-Level: 
X-Spam-Status: No, score=-0.09 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FORGED_MUA_MOZILLA=2.309, FREEMAIL_FROM=0.001, FREEMAIL_REPLYTO=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, 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=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OYNlLOK3ndwK for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 20:49:57 -0700 (PDT)
Received: from sonic309-28.consmr.mail.ir2.yahoo.com (sonic309-28.consmr.mail.ir2.yahoo.com [77.238.179.86]) (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 6D7B5129B25 for <ietf@ietf.org>; Mon, 12 Jun 2017 20:49:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1497325795; bh=636T0eK+v2fLMhth9Jf16DBAE4KTJVR4Neq2Xfc1BlA=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=m52490Kf/lM+YvWVwEGCQs8ifCfkkGHn/bTTlGIDkZqosxKwpsDHoDANosayd3Cd/tfZftlZg5REkBPp+xI2cMJzOLnSqmgZb6sNJVuL7R26kkqGn5SULiqAL9mgfsH36zeYlAWhVTQX4STOBK45fLWPc5TMR9xqivZntXG1BO//cIuNzVVoqFESZDD/GNkjmEOGoGF6XRHfctMoZyoNhfvejvkDuQs2uTjrPoVLMuFjFt0y8wrjjuzYsh01/Y+M0OxZo/PGgDcOKTR5P1iZRI7b46VV6I7iz8cUnLhr5bVyVNWhU01Yn1UrqzvMLvL/A39pMiMj2SS7oNNVC8MYdg==
X-YMail-OSG: uvgLPDIVM1mp.DHVfwOltDwAlbUZEesjPq3B2ghUA0UAtThtgxH.gHvEx20OB7a uFBTofBdmY7zTmJhmwsTM8Rp47nZfWJBGzZ.LzbAeZfk_wlwCWUsZz4P658ELdnpaxzI8AzKdOKB ED_dqVx5z8LXmPr.kuW3Zb662UgqukK7vSLCR2BsLi1eMTT3Sn1FnCrzayY8z5870TrbHK_Le9qQ cIbNZ_3jsteMaptPs_o2EBqeqWIFllbKJgGOFdtxHYpeb.ioRSbBdg56OHDGWIhbluzYARlkEYFy l2fQ.2iFdu758ZxE0WAMb7B8Ev8MGZhf9bnR_X4zEP91X3FeBJ.N6Tmdz8HajHtBmzkiwDFpSPXU Z4UkDGdXO_gevaGuu0zG9hSeh.kGo9QSZxPIY1nuRfrcbDF7aew.HpXxD3yNYO7R7QKH_6r3.ZQD j8HHqEM687H2v3EQPx5zU9hmg05AgW0NJ33G.g39u2lCujxX7ueELV3100eiuL97WVECh7GOwuIx YOn6nuqn4NpYaEptSa62lPVw3tzSjMJN6FAGDiFrT
Received: from sonic.gate.mail.ne1.yahoo.com by sonic309.consmr.mail.ir2.yahoo.com with HTTP; Tue, 13 Jun 2017 03:49:55 +0000
Date: Tue, 13 Jun 2017 03:49:55 +0000 (UTC)
From: =?UTF-8?Q?=E2=80=AAmarwa_simohamed=E2=80=AC_=E2=80=AA?= <marwa_simohamed@yahoo.com>
Reply-To: =?UTF-8?Q?=E2=80=AAmarwa_simohamed=E2=80=AC_=E2=80=AA?= <marwa_simohamed@yahoo.com>
To: IETF Discussion <ietf@ietf.org>
Message-ID: <511491269.14046105.1497325795307@mail.yahoo.com>
Subject: RE: IAD Retirement
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_14046104_1406327495.1497325795305"
References: <511491269.14046105.1497325795307.ref@mail.yahoo.com>
X-Mailer: WebService/1.1.9778 YahooMailNeo Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QL9lqnWPBUAzgalicQ3fUa3j9ls>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 03:49:59 -0000

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

Thank you so much for your service
Regards,Marwa
=C2=A0
--=C2=A0Si Mohammed Marwa=C2=A0Master=E2=80=99s Degree Student (M.Sc)=C2=A0=
Computer Science Department=C2=A0Networks,Systems,Information Security=C2=
=A0Djilali Liabes university of Sidi Belabes Algeria=C2=A0Cell:+21369771700=
9=C2=A0Email: marwa.simohamed@avanquest-dz.com=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0=C2=A0marwa.simohamed@hotmail.com
------=_Part_14046104_1406327495.1497325795305
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:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font=
-size:13px"><div id=3D"yui_3_16_0_1_1497323551122_9040">Thank you so much f=
or your service</div><div id=3D"yui_3_16_0_1_1497323551122_9040"><br></div>=
<div id=3D"yui_3_16_0_1_1497323551122_9040">Regards,</div><div id=3D"yui_3_=
16_0_1_1497323551122_9040">Marwa</div><div id=3D"yui_3_16_0_1_1497323551122=
_9040"><br></div><div></div><div id=3D"yui_3_16_0_1_1497323551122_9069">&nb=
sp;</div><div class=3D"signature" id=3D"yui_3_16_0_1_1497323551122_9038"><d=
iv id=3D"yui_3_16_0_1_1497323551122_9099"><br></div><div id=3D"yui_3_16_0_1=
_1497323551122_9039">--&nbsp;</div><div id=3D"yui_3_16_0_1_1497323551122_90=
37"><span style=3D"font-size:small;" id=3D"yui_3_16_0_1_1497323551122_9036"=
>Si Mohammed Marwa&nbsp;</span></div><div id=3D"yui_3_16_0_1_1497323551122_=
9135"><span style=3D"font-size:small;" id=3D"yui_3_16_0_1_1497323551122_913=
4">Master=E2=80=99s Degree Student (M.Sc)&nbsp;</span></div><div><span styl=
e=3D"font-size:small;">Computer Science Department&nbsp;</span></div><div><=
span style=3D"font-size:small;">Networks,Systems,Information Security&nbsp;=
</span></div><div id=3D"yui_3_16_0_1_1497323551122_9137"><span style=3D"fon=
t-size:small;" id=3D"yui_3_16_0_1_1497323551122_9136">Djilali Liabes univer=
sity of Sidi Belabes Algeria&nbsp;</span></div><div><span style=3D"font-siz=
e:small;">Cell:+213697717009&nbsp;</span></div><div id=3D"yui_3_16_0_1_1497=
323551122_9139"><span style=3D"font-size:small;" id=3D"yui_3_16_0_1_1497323=
551122_9138">Email: <a rel=3D"nofollow" href=3D"">marwa.simohamed@avanquest=
-dz.com</a></span></div><div id=3D"yui_3_16_0_1_1497323551122_9140">&nbsp; =
&nbsp; &nbsp; &nbsp; &nbsp;&nbsp;<a rel=3D"nofollow" style=3D"font-size:sma=
ll;" href=3D"">marwa.simohamed@hotmail.com</a></div></div></div></body></ht=
ml>
------=_Part_14046104_1406327495.1497325795305--


From nobody Mon Jun 12 22:25:50 2017
Return-Path: <paf@frobbit.se>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 915D6129B33 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 22:25:48 -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, 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 OD-EbmUkug8i for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 22:25:46 -0700 (PDT)
Received: from mail.frobbit.se (mail.frobbit.se [85.30.129.185]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F029126CD6 for <ietf@ietf.org>; Mon, 12 Jun 2017 22:25:46 -0700 (PDT)
Received: from [169.254.248.118] (unknown [IPv6:2a01:3f0:1:0:70f6:37e4:c68d:92c]) by mail.frobbit.se (Postfix) with ESMTPSA id 36E6A21415 for <ietf@ietf.org>; Tue, 13 Jun 2017 07:25:43 +0200 (CEST)
From: "Patrik =?utf-8?b?RsOkbHRzdHLDtm0=?=" <paf@frobbit.se>
To: ietf@ietf.org
Subject: Re: IAD Retirement
Date: Tue, 13 Jun 2017 07:25:44 +0200
Message-ID: <345192A9-8FFD-48B1-9A16-084CBC03331C@frobbit.se>
In-Reply-To: <77b44755-0da4-6058-3ef0-879923739c6e@gmail.com>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com> <77b44755-0da4-6058-3ef0-879923739c6e@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=_MailMate_B00CAD62-1ACB-4EA8-8930-CBB2ACA7DA5C_="; micalg=pgp-sha1; protocol="application/pgp-signature"
X-Mailer: MailMate (2.0BETAr6085)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zIHALkckNXpVR8QvD9qL9G0N16c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 05:25:48 -0000

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

--=_MailMate_B00CAD62-1ACB-4EA8-8930-CBB2ACA7DA5C_=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

On 12 Jun 2017, at 22:43, Brian E Carpenter wrote:

> We tend to complain a lot in the IETF. So I'm going to complain:
> The IETF won't be the same without Ray.
>
> Thanks for everything, especially for acting as a very helpful, cheerfu=
l and efficient complaints desk.

Can not explain it much better than Brian.

Thanks Ray, you will indeed be missed. You took the job when the IETF was=
 in a delicate situation in time. You shaped the IAD, did ensure the acti=
ons where based on rough consensus in the community while staying within =
whatever real world constraints (budget, staff and what not) that exists.=
 Contracts here, contracts there. Travel logistics. Trains and airplanes.=
 Hotels and restaurants. Local jurisdictions. IANA transitions and many o=
ther issues.

But in the core are humans. And you have an incredible ability to never e=
ver forget the humans.

Hold on to that!

Best,

   Patrik F=C3=A4ltstr=C3=B6m

--=_MailMate_B00CAD62-1ACB-4EA8-8930-CBB2ACA7DA5C_=
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename=signature.asc
Content-Type: application/pgp-signature; name=signature.asc

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

iEYEARECAAYFAlk/d1gACgkQrMabGguI182pTACfbTbJ+wrwcKzXy3GdiSbrHBKu
W70AoIHURyleIzmJQ9ZcBosyl1cAnxIr
=gg3R
-----END PGP SIGNATURE-----

--=_MailMate_B00CAD62-1ACB-4EA8-8930-CBB2ACA7DA5C_=--


From nobody Mon Jun 12 22:49:07 2017
Return-Path: <liman@netnod.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 38DFB127863 for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 22:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level: 
X-Spam-Status: No, score=-4.301 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=netnod.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 L3vmjndWw42A for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 22:49:01 -0700 (PDT)
Received: from mail.netnod.se (mail.netnod.se [192.71.80.100]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A0A41270B4 for <ietf@ietf.org>; Mon, 12 Jun 2017 22:49:01 -0700 (PDT)
Received: from hiptop.local (vpn-client-130.netnod.se [192.71.80.130]) (Authenticated sender: liman) by mail.netnod.se (Postfix) with ESMTPSA id 48A8C7C142 for <ietf@ietf.org>; Tue, 13 Jun 2017 07:48:59 +0200 (CEST)
Authentication-Results: mail.netnod.se; dmarc=none header.from=netnod.se
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=netnod.se; s=mail; t=1497332939; bh=hB/OahgNuJMgB/B3UTPNLPMEAkJFLzI31sFHiEj8ZvM=; h=From:To:Subject:References:Date:In-Reply-To:From; b=Fnj3BUYIfOo6LhArXMizvWsgMRsPS7p0ocmPu6xWyD9bmJrrPfCxXk5tUO3OT5C7I QoQxgOGE74VernNFfB354LDJt6raxgjN/WgBflfayW4HGpGWZ20iFHgLVAtSh0v/YL 2IMjzMbbKr2IsqaHCMMPgUGIOr1Wht9Ti6nrus0slnvqBHKp646zuHmJjRly3CtLsl z1iFL9Pca+ElKfMbL0FBIbgq6vw2RZsYmjMs2v/SXtiUeLI98j63Vmy3k+nWbs8OB2 zxZxISGk3lznf9eYu5xFiQypztEAKYqYXgxz6WimKWbOZHydWNXxmMWzwmKAEl1YrU lOlihokA6s8hg==
Received: from hiptop.local (localhost [IPv6:::1]) by hiptop.local (Postfix) with ESMTP id 13A6B1499AC2 for <ietf@ietf.org>; Tue, 13 Jun 2017 07:48:59 +0200 (CEST)
From: Lars-Johan Liman <liman@netnod.se>
To: ietf@ietf.org
Subject: Re: IAD retirement
References: <149731904993.7732.10262100091459990539.idtracker@ietfa.amsl.com>
Date: Tue, 13 Jun 2017 07:48:58 +0200
In-Reply-To: <149731904993.7732.10262100091459990539.idtracker@ietfa.amsl.com> (IAOC Chair's message of "Mon, 12 Jun 2017 18:57:29 -0700")
Message-ID: <22efuol9o5.fsf@netnod.se>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (darwin)
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/IA2l9phSaORgzcOq2FVDtqinfbA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 05:49:05 -0000

Ray,

Thank you very much for all the time and efforts you've spent on making
sure that we could continue to work without having to give a single
thought to how and why there was always the right resources provided at
the right moment. I've taken part in organizing medium sized conferences
once or twice, and that was enough to make me say "never again!", and
you (and your excellent staff!) have done it for full-sized meetings for
12(!) years. It is time for us to "release" you, and bow in respect. It's
been pure pleasure to be on the receiving end of your efforts.

All the best for your future, and a million thanks for what you've done
for us!

				Warm regards,
				  /Liman, IETF:er since 1993
#----------------------------------------------------------------------
# Lars-Johan Liman, M.Sc.               !  E-mail: liman@netnod.se
# Senior Systems Specialist             !  Tel: +46 8 - 562 860 12
# Netnod Internet Exchange, Stockholm   !  http://www.netnod.se/
#----------------------------------------------------------------------

iaoc-chair@ietf.org:
> All,

> By now, you will have seen Ray Pelletier=E2=80=99s announcement that he is
> retiring as our IETF Administrative Director, effective October 31,
> 2017.

> The IAOC would like to thank Ray for his 12+ years of dedicated
> service in the role of IAD, as we collectively built and fine tuned
> the IETF Administrative Support Activity established in 2005. We wish
> Ray all the best in his retirement!

> Though the IAOC is mindful that the IASA 2.0 discussion may impact the
> shape of the role going forward, we are also concerned with the smooth
> functioning of the IETF's administration now.  We are therefore
> working to bring in staff before Ray retires in order to support that
> immediate need.

> Leslie,=20
> for the IAOC.


From nobody Mon Jun 12 23:29: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 152C3129ADD for <ietf@ietfa.amsl.com>; Mon, 12 Jun 2017 23:29:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sElsTVHPCLYz; Mon, 12 Jun 2017 23:29:54 -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 D221F12957A; Mon, 12 Jun 2017 23:29:51 -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 1dKfKn-0001pK-Ek; Tue, 13 Jun 2017 06:29:49 +0000
Date: Tue, 13 Jun 2017 13:29:47 +0700
Message-ID: <m28tkwe6xw.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IAOC Chair <iaoc-chair@ietf.org>
Cc: IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: IAD retirement
In-Reply-To: <149731904993.7732.10262100091459990539.idtracker@ietfa.amsl.com>
References: <149731904993.7732.10262100091459990539.idtracker@ietfa.amsl.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/eoMyVF4A2rKWRWiWViL4Pet0_Kk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 06:29:56 -0000

hi leslie,

> We are therefore working to bring in staff before Ray retires in order
> to support that immediate need.

could you be more specific?  i.e. bring staff 'in' in the sense of the
current isoc/ietf iad relationship?

randy


From nobody Tue Jun 13 02:17:21 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 C4F741314BF for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 02:17:19 -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 Ghg5ha8mbbPs for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 02:17:15 -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 3735412EBBA for <ietf@ietf.org>; Tue, 13 Jun 2017 02:10:49 -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 1dKhqZ-000JkM-9L; Tue, 13 Jun 2017 05:10:47 -0400
Date: Tue, 13 Jun 2017 05:10:41 -0400
From: John C Klensin <john-ietf@jck.com>
To: heasley <heas@shrubbery.net>, ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Message-ID: <0658C4E3DBD74293BF3A2CBB@PSB>
In-Reply-To: <20170613033859.GA71771@shrubbery.net>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/u34JzEjFEHYO-fo_qN7f6I8AZQc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 09:17:20 -0000

--On Tuesday, June 13, 2017 03:38 +0000 heasley
<heas@shrubbery.net> wrote:

> Mon, Jun 12, 2017 at 06:29:30AM -0700,
> internet-drafts@ietf.org:
>>         Title           : The Harmful Consequences of
>>         Postel's Maxim
>> https://tools.ietf.org/html/draft-thomson-postel-was-wrong-01
> 
> Perhaps instead of requiring two implementations for a
> protocol draft to proceed to rfc, it should first or also have
> a test suite that
> 
>         ... fails noisily in response to bad or undefined
> inputs.
> 
> Having a community-developed test suite for any protocol would
> be a great asset.

Actually, a number of standards bodies have found, to their
chagrin, that test suites that are developed and.or certified by
the standards body are a terrible idea.  The problem is that
they become the real standard, substituting "passes the test
suite" for "conformance to the standard" or the IETF's long
tradition of "interoperates successfully in practice".

And we have never had a global requirement for "two
implementations to proceed to rfc".

    john




From nobody Tue Jun 13 06:18:45 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 09B7E13184E for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 06:18:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.798
X-Spam-Level: 
X-Spam-Status: No, score=-4.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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=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 A363DSmzN5Ub; Tue, 13 Jun 2017 06:18:39 -0700 (PDT)
Received: from homiemail-a96.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 927F6129516; Tue, 13 Jun 2017 06:18:39 -0700 (PDT)
Received: from homiemail-a96.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTP id 1A0A0C00292C; Tue, 13 Jun 2017 06:18:39 -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=N Pu68lBdu0I5iJYyMj5yQQKicXw=; b=btQoLuk/gX/PE/vH5CfvZGo+6iOo+e2cr 3Cwx71wrG8C4DhCqBGDv1OdegDy7uBBqpY4oz4fORoTAIOpcMvk4w8qnd2Do5sho df6y7CkYcRQy5e3NvO2sD/ysM6Xre2MDnQ1g6M3FVzj4vTofA6cKtlMEaz9lWp/M +4EBucCHwQ=
Received: from [172.20.10.5] (mobile-166-171-184-136.mycingular.net [166.171.184.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTPSA id 1C768C002933; Tue, 13 Jun 2017 06:18:36 -0700 (PDT)
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: "Randy Bush" <randy@psg.com>
Cc: "IAOC Chair" <iaoc-chair@ietf.org>, "IETF Rinse Repeat" <ietf@ietf.org>
Subject: Re: IAD retirement
Date: Tue, 13 Jun 2017 09:18:35 -0400
Message-ID: <33EB1557-0054-467D-B22F-3AF6BEC36640@thinkingcat.com>
In-Reply-To: <m28tkwe6xw.wl-randy@psg.com>
References: <149731904993.7732.10262100091459990539.idtracker@ietfa.amsl.com> <m28tkwe6xw.wl-randy@psg.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_30430C70-E527-490C-8171-FBD8D64598CB_="
X-Mailer: MailMate (1.9.6r5347)
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nww-ArQS_v5bgcVRAOeGk-gyfAs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 13:18:44 -0000

--=_MailMate_30430C70-E527-490C-8171-FBD8D64598CB_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable


Hi,

Sorry that bit was particularly opaque.

We will be hiring someone.  What=E2=80=99s not yet clear is whether it wi=
ll be=20
best to hire one person for everything, whether it will be an interim=20
position or permanent.  Given that there are IASA2.0 discussions=20
underway, it=E2=80=99s not absolutely clear that trying to replicate Ray =
(as=20
if that were possible!) would be the right choice.

Leslie.

--=20

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

On 13 Jun 2017, at 2:29, Randy Bush wrote:

> hi leslie,
>
>> We are therefore working to bring in staff before Ray retires in=20
>> order
>> to support that immediate need.
>
> could you be more specific?  i.e. bring staff 'in' in the sense of the
> current isoc/ietf iad relationship?
>
> randy

--=_MailMate_30430C70-E527-490C-8171-FBD8D64598CB_=
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">Hi,</p>

<p dir=3D"auto">Sorry that bit was particularly opaque.  </p>

<p dir=3D"auto">We will be hiring someone.  What=E2=80=99s not yet clear =
is whether it will be best to hire one person for everything, whether it =
will be an interim position or permanent.  Given that there are IASA2.0 d=
iscussions underway, it=E2=80=99s not absolutely clear that trying to rep=
licate Ray (as if that were possible!) would be the right choice.</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 13 Jun 2017, at 2:29, Randy Bush wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">hi leslie,</p>

<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<p dir=3D"auto">We are therefore working to bring in staff before Ray ret=
ires in order<br>
to support that immediate need.</p>
</blockquote>

<p dir=3D"auto">could you be more specific?  i.e. bring staff 'in' in the=
 sense of the<br>
current isoc/ietf iad relationship?</p>

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

--=_MailMate_30430C70-E527-490C-8171-FBD8D64598CB_=--


From nobody Tue Jun 13 07:29:44 2017
Return-Path: <heas@shrubbery.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 DA6E41293E4 for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 07:29:42 -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_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 NAtfQeG0qjJD for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 07:29:38 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6606712EBED for <ietf@ietf.org>; Tue, 13 Jun 2017 07:28:21 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 276F18DF92; Tue, 13 Jun 2017 14:28:21 +0000 (UTC)
Date: Tue, 13 Jun 2017 14:28:21 +0000
From: heasley <heas@shrubbery.net>
To: John C Klensin <john-ietf@jck.com>
Cc: heasley <heas@shrubbery.net>, ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Message-ID: <20170613142820.GA21291@shrubbery.net>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0658C4E3DBD74293BF3A2CBB@PSB>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.8.0 (2017-02-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uPU1zSzgQddAm1p42Npb_rmS_ww>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 14:29:43 -0000

Tue, Jun 13, 2017 at 05:10:41AM -0400, John C Klensin:
> --On Tuesday, June 13, 2017 03:38 +0000 heasley
> <heas@shrubbery.net> wrote:
> 
> > Mon, Jun 12, 2017 at 06:29:30AM -0700,
> > internet-drafts@ietf.org:
> >>         Title           : The Harmful Consequences of
> >>         Postel's Maxim
> >> https://tools.ietf.org/html/draft-thomson-postel-was-wrong-01
> > 
> > Perhaps instead of requiring two implementations for a
> > protocol draft to proceed to rfc, it should first or also have
> > a test suite that
> > 
> >         ... fails noisily in response to bad or undefined
> > inputs.
> > 
> > Having a community-developed test suite for any protocol would
> > be a great asset.
> 
> Actually, a number of standards bodies have found, to their
> chagrin, that test suites that are developed and.or certified by
> the standards body are a terrible idea.  The problem is that
> they become the real standard, substituting "passes the test
> suite" for "conformance to the standard" or the IETF's long

reference?

> tradition of "interoperates successfully in practice".

so, both - test suite and a pair of interoperable implementation.

> And we have never had a global requirement for "two
> implementations to proceed to rfc".

Is that only IDR?


From nobody Tue Jun 13 08:10:01 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 ED32213197B for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 08:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hfoaZ935BoNp; Tue, 13 Jun 2017 08:09:52 -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 8AD3C1200FC; Tue, 13 Jun 2017 07:55:01 -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 1dKnDf-0004ZD-RY; Tue, 13 Jun 2017 14:55:00 +0000
Date: Tue, 13 Jun 2017 21:54:56 +0700
Message-ID: <m27f0gc4zj.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Leslie Daigle" <ldaigle@thinkingcat.com>
Cc: "IAOC Chair" <iaoc-chair@ietf.org>, "IETF Rinse Repeat" <ietf@ietf.org>
Subject: Re: IAD retirement
In-Reply-To: <33EB1557-0054-467D-B22F-3AF6BEC36640@thinkingcat.com>
References: <149731904993.7732.10262100091459990539.idtracker@ietfa.amsl.com> <m28tkwe6xw.wl-randy@psg.com> <33EB1557-0054-467D-B22F-3AF6BEC36640@thinkingcat.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/AekD5LqSJ5FqKJaYlvdbjGT4ChM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 15:09:59 -0000

>> could you be more specific?  i.e. bring staff 'in' in the sense of
>> the current isoc/ietf iad relationship?
> We will be hiring someone.

who is the we?  isoc, the ietf, or some other body?

sorry to be opaque myself.  is the ietf leaving all the logistics,
administrivia, and the money on the other side of the river, or is it
going to form an administration which employs folk?

randy


From nobody Tue Jun 13 08:13:37 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 4396C131C04; Tue, 13 Jun 2017 08:13:36 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Matthew Miller <linuxwolf+ietf@outer-planes.net>
To: <secdir@ietf.org>
Cc: draft-ietf-precis-7564bis.all@ietf.org, ietf@ietf.org, precis@ietf.org
Subject: Secdir last call review of draft-ietf-precis-7564bis-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149736681626.7439.2555177998557552719@ietfa.amsl.com>
Date: Tue, 13 Jun 2017 08:13:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G20nO2j1oPRmylh3iHzzgoHm3OI>
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, 13 Jun 2017 15:13:36 -0000

Reviewer: Matthew Miller
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.

Document: draft-ietf-precis-7564bis-07
Reviewer: Matthew A. Miller
Review Date: 2017-06-13
IETF LC End Date: 2017-06-13
IESG Telechat date: 2017-07-06

Summary:

This document is ready to be published as a Standards Track document.

This document defines a framework application protocols use to
prepare, compare, and enforce conformance of internationalized strings.
It obsoletes RFC 7564.

This document is well written, and reinforces the security concerns
discussed in Section 12 with references in the most relevant sections
throughout the document.  While much of it essentially proclaims
"be aware herein be dragons", the arguments for not proscribing more
are well laid out.

Major Issues:  NONE

Minor Issues: NONE

Nits: NONE



From nobody Tue Jun 13 08:39:32 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 4542B1318DB for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 08:39:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.798
X-Spam-Level: 
X-Spam-Status: No, score=-4.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-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=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 zCWvBNCYP9g3; Tue, 13 Jun 2017 08:39:29 -0700 (PDT)
Received: from homiemail-a96.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 ADF62131D18; Tue, 13 Jun 2017 08:25:19 -0700 (PDT)
Received: from homiemail-a96.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTP id 3A2A0C00292C; Tue, 13 Jun 2017 08:25:19 -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; s=thinkingcat.com; bh=K8bCod6w+/tr83cqnC846QYYutw =; b=k86FmniPEDm2WKAIVjfCimTEMNIZrNbKwq6eU22k2L4aw0szjeEh5j+6zSz scKPkroHbYw2FL4cfzeL5rMi9HD1HKupfuqa4pX9Ut9E4/gjMdiBIZkm087ZHrI3 T2mvKQSa9P4ej7B3oykptFhuupTXdsG5nRm4yOiuvin630lU=
Received: from [172.20.10.5] (mobile-166-171-184-136.mycingular.net [166.171.184.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: leslie@oceanpurl.net) by homiemail-a96.g.dreamhost.com (Postfix) with ESMTPSA id E608CC002928; Tue, 13 Jun 2017 08:25:17 -0700 (PDT)
From: "Leslie Daigle" <ldaigle@thinkingcat.com>
To: "Randy Bush" <randy@psg.com>
Cc: "IAOC Chair" <iaoc-chair@ietf.org>, "IETF Rinse Repeat" <ietf@ietf.org>
Subject: Re: IAD retirement
Date: Tue, 13 Jun 2017 11:25:15 -0400
Message-ID: <69BF8040-E0EE-468C-B29E-9BA9B4EF37DA@thinkingcat.com>
In-Reply-To: <m27f0gc4zj.wl-randy@psg.com>
References: <149731904993.7732.10262100091459990539.idtracker@ietfa.amsl.com> <m28tkwe6xw.wl-randy@psg.com> <33EB1557-0054-467D-B22F-3AF6BEC36640@thinkingcat.com> <m27f0gc4zj.wl-randy@psg.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_ACB29B30-50DB-415D-904D-E95F94A1390F_="
X-Mailer: MailMate (1.9.6r5347)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/d_Ae0Hg8sLTdse4aCIocAxYTvGo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 15:39:30 -0000

--=_MailMate_ACB29B30-50DB-415D-904D-E95F94A1390F_=
Content-Type: text/plain; format=flowed; markup=markdown


Hi,

Unless IASA2.0 moves along much more quickly than most IETF things, by 
the time Ray retires, it will still be ISOC doing the employment.  It 
will still be the IAOC (subcommittee) doing the search and selection.

What things look like a year (or more) from now is up for IASA2.0 to 
sort out.


Leslie.

-- 

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

On 13 Jun 2017, at 10:54, Randy Bush wrote:

>>> could you be more specific?  i.e. bring staff 'in' in the sense of
>>> the current isoc/ietf iad relationship?
>> We will be hiring someone.
>
> who is the we?  isoc, the ietf, or some other body?
>
> sorry to be opaque myself.  is the ietf leaving all the logistics,
> administrivia, and the money on the other side of the river, or is it
> going to form an administration which employs folk?
>
> randy

--=_MailMate_ACB29B30-50DB-415D-904D-E95F94A1390F_=
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">Hi,</p>

<p dir=3D"auto">Unless IASA2.0 moves along much more quickly than most IE=
TF things, by the time Ray retires, it will still be ISOC doing the emplo=
yment.  It will still be the IAOC (subcommittee) doing the search and sel=
ection.</p>

<p dir=3D"auto">What things look like a year (or more) from now is up for=
 IASA2.0 to sort out.</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 13 Jun 2017, at 10:54, Randy Bush wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<blockquote style=3D"border-left:2px solid #777; color:#999; margin:0 0 5=
px; padding-left:5px; border-left-color:#999">
<blockquote style=3D"border-left:2px solid #777; color:#BBB; margin:0 0 5=
px; padding-left:5px; border-left-color:#BBB">
<p dir=3D"auto">could you be more specific?  i.e. bring staff 'in' in the=
 sense of<br>
the current isoc/ietf iad relationship?</p>
</blockquote>

<p dir=3D"auto">We will be hiring someone.</p>
</blockquote>

<p dir=3D"auto">who is the we?  isoc, the ietf, or some other body?</p>

<p dir=3D"auto">sorry to be opaque myself.  is the ietf leaving all the l=
ogistics,<br>
administrivia, and the money on the other side of the river, or is it<br>=

going to form an administration which employs folk?</p>

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

--=_MailMate_ACB29B30-50DB-415D-904D-E95F94A1390F_=--


From nobody Tue Jun 13 08:41:59 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 291C013187C for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 08:41:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XqZUuWFllEdC; Tue, 13 Jun 2017 08:41:54 -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 1BF2C131C0C; Tue, 13 Jun 2017 08:27:28 -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 1dKnj4-0004so-Bz; Tue, 13 Jun 2017 15:27:26 +0000
Date: Tue, 13 Jun 2017 22:27:24 +0700
Message-ID: <m2r2ync3hf.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: "Leslie Daigle" <ldaigle@thinkingcat.com>
Cc: "IAOC Chair" <iaoc-chair@ietf.org>, "IETF Rinse Repeat" <ietf@ietf.org>
Subject: Re: IAD retirement
In-Reply-To: <69BF8040-E0EE-468C-B29E-9BA9B4EF37DA@thinkingcat.com>
References: <149731904993.7732.10262100091459990539.idtracker@ietfa.amsl.com> <m28tkwe6xw.wl-randy@psg.com> <33EB1557-0054-467D-B22F-3AF6BEC36640@thinkingcat.com> <m27f0gc4zj.wl-randy@psg.com> <69BF8040-E0EE-468C-B29E-9BA9B4EF37DA@thinkingcat.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/ADL9f_y7LWH0yM0WoVS7rzmMpa4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 15:41:57 -0000

evenin' leslie,

> Unless IASA2.0 moves along much more quickly than most IETF things, by
> the time Ray retires, it will still be ISOC doing the employment.  It
> will still be the IAOC (subcommittee) doing the search and selection.

that answers my question spot on, and allay's my worries.  thanks.

randy


From nobody Tue Jun 13 09:13:39 2017
Return-Path: <prvs=23375b132e=jonathan@vidyo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5221C131B94; Tue, 13 Jun 2017 09:13:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gaQOh_09-nlT; Tue, 13 Jun 2017 09:13:16 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com [67.231.157.197]) (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 5D003131BEA; Tue, 13 Jun 2017 09:03:45 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net [127.0.0.1]) by mx0b-00198e01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v5DFwsXH010494; Tue, 13 Jun 2017 12:03:25 -0400
Received: from mail.vidyo.com (mail2.vidyo.com [162.209.16.214]) by mx0b-00198e01.pphosted.com with ESMTP id 2b0bh4j2cd-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Tue, 13 Jun 2017 12:03:25 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Tue, 13 Jun 2017 11:03:24 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Roni Even <roni.even@huawei.com>
CC: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>, General Area Review Team <gen-art@ietf.org>, "avtext@ietf.org" <avtext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMAgAAtEkCAAQCzAIAFrKRwgAPKzwA=
Date: Tue, 13 Jun 2017 16:03:24 +0000
Message-ID: <116D9947-414D-47EB-A0C7-8031999E5A89@vidyo.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com> <B9294064-4F4E-4FA1-A864-4F9790767B5C@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7D0641@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD7D0641@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <21981E940CDBFB41BA11CCAD1E27437E@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-13_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706130276
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/s_o991lzAnNMDfnNJ7RuLFWiFxY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 16:13:18 -0000

SGksIFJvbmkg4oCUDQoNCllvdSBzZWVtIHRvIGJlIGFzc3VtaW5nIHRoYXQgYSByZWZyZXNoIGFu
ZCBhbiB1cGdyYWRlIGFyZSB0d28gZGlmZmVyZW50IGFjdGlvbnMuICBUaGF04oCZcyBub3QgdGhl
IGludGVudGlvbiDigJQgYSByZWZyZXNoIGlzIGEgY2hhcmFjdGVyaXN0aWMgb2YgYSBzdHJlYW0g
dGhhdCBhbGxvd3MgYSBkZWNvZGVyIHRvIHVwZ3JhZGUuDQoNCknigJlsbCB0cnkgdG8gZHJhZnQg
c29tZSB0ZXh0IHRoYXQgbWFrZXMgaXQgY2xlYXIgdGhhdCBpdOKAmXMgcG9zc2libGUgZWl0aGVy
IHRvIGluZGVwZW5kZW50bHkgdXBncmFkZSB0ZW1wb3JhbCBvciBzcGF0aWFsLCBvciBlbHNlIHVw
Z3JhZGUgYm90aCBhdCBvbmNlLg0KDQo+IE9uIEp1biAxMSwgMjAxNywgYXQgNzoyMCBBTSwgUm9u
aSBFdmVuIDxyb25pLmV2ZW5AaHVhd2VpLmNvbT4gd3JvdGU6DQo+IA0KPiBIaSBKb25hdGhhbiwN
Cj4gSSBhc3N1bWUgdGhlIG5ldyB0ZXh0IHlvdSBwcm9wb3NlIGlzIA0KPiANCj4gIldoZW4gQyBp
cyAxLCBUVElEIE1VU1QgTk9UIGJlIGxlc3MgdGhhbiBDVElELCBhbmQgVExJRCBNVVNUIE5PVCBi
ZQ0KPiAgIGxlc3MgdGhhbiBDTElEOyBhdCBsZWFzdCBvbmUgb2YgVFRJRCBvciBUTElEIE1VU1Qg
YmUgZ3JlYXRlciB0aGFuDQo+ICAgQ1RJRCBvciBDTElEIHJlc3BlY3RpdmVseS4gIFRoYXQgaXMg
dG8gc2F5LCB0aGUgdGFyZ2V0IGxheWVyIGluZGV4DQo+ICAgPFRUSUQsIFRMSUQ+IE1VU1QgYmUg
YSBsYXllciB1cGdyYWRlIGZyb20gdGhlIGN1cnJlbnQgbGF5ZXIgaW5kZXgNCj4gICA8Q1RJRCwg
Q0xJRD4uICBBIHNlbmRlciBNQVkgcmVxdWVzdCBhbiB1cGdyYWRlIGluIGJvdGggdGVtcG9yYWwg
YW5kDQo+ICAgc3BhdGlhbC9xdWFsaXR5IGxheWVycyBzaW11bHRhbmVvdXNseS4iDQo+IA0KPiBJ
IHRoaW5rIHRoYXQgdGhpcyB0ZXh0IHN0aWxsIG9ubHkgaW1wbGllcyB0aGUgYmVoYXZpb3IsIGFs
c28gdGhlIGN1cnJlbnQgdGV4dCB0YWxrcyBhYm91dCB1cGdyYWRlIGJ1dCBJIGFzc3VtZSBpdCBp
cyBhbHNvIGZvciBhIHJlZnJlc2ggbm90IG9ubHkgdG8gdXBncmFkZQ0KPiANCj4gTWF5YmUgIiBB
IHNlbmRlciBNQVkgcmVxdWVzdCBhbiB1cGdyYWRlIG9yIHJlZnJlc2ggIGluIGJvdGggdGVtcG9y
YWwgYW5kDQo+ICAgc3BhdGlhbC9xdWFsaXR5IGxheWVycyBzaW11bHRhbmVvdXNseSBieSBlaXRo
ZXIgaGF2aW5nIEMgPTEgb3IgYnkgaGF2aW5nIGJvdGggQ0xJRCBhbmQgQ1RJRCB3aXRoIGxvd2Vy
IHZhbHVlcyB0aGVuIFRUSUQgYW5kIFRMSUQuIElmIHRoZSBzZW5kZXIgd2FudCB0byB1cGdyYWRl
IG9yIHJlZnJlc2ggb25seSBvbmUgbGF5ZXIgdGhlbiBDIE1VU1QgYmUgZXF1YWwgdG8gMSBhbmQg
b25seSB0aGUgQ1RJRCBvciAgdGhlIENMSUQgb2YgdGhlIGxheWVyIHRvIGJlIHVwZ3JhZGVkIG9y
IHJlZnJlc2hlZCBzaG91bGQgYmUgbG93ZXIgdGhhbiB0aGUgVFRJRCBvciBUTElEIHJlc3BlY3Rp
dmVseSAiDQo+IA0KPiANCj4gUm9uaQ0KPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+
IEZyb206IEpvbmF0aGFuIExlbm5veCBbbWFpbHRvOmpvbmF0aGFuQHZpZHlvLmNvbV0NCj4+IFNl
bnQ6INeZ15XXnSDXkyAwNyDXmdeV16DXmSAyMDE3IDE4OjMwDQo+PiBUbzogUm9uaSBFdmVuDQo+
PiBDYzogUm9uaSBFdmVuOyBkcmFmdC1pZXRmLWF2dGV4dC1scnIuYWxsQGlldGYub3JnOyBHZW5l
cmFsIEFyZWEgUmV2aWV3IFRlYW07DQo+PiBhdnRleHRAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcN
Cj4+IFN1YmplY3Q6IFJlOiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWF2
dGV4dC1scnItMDUNCj4+IA0KPj4gDQo+Pj4gT24gSnVuIDcsIDIwMTcsIGF0IDE6MTUgQU0sIFJv
bmkgRXZlbiA8cm9uaS5ldmVuQGh1YXdlaS5jb20+IHdyb3RlOg0KPj4+IA0KPj4+IEhpIEpvbmF0
aGFuLA0KPj4+IEkgZGlkIG5vdCBzZWUgdGhlIHRleHQgeW91IGFkZGVkIHlldCBhcyBhIHJlc3Bv
bnNlIHRvIG15IGZpcnN0DQo+Pj4gcXVlc3Rpb24gU28gdG8gYmV0dGVyIGNsYXJpZnkgbXkgcXVl
c3Rpb24gLiBJZiB0aGUgRkNJIGhhcyBUVElEPTAgYW5kIFRMSUQ9MiAuDQo+PiBkb2VzIGl0IG1l
YW4gdGhhdCBpdCBpcyBhIHJlcXVlc3QgdG8gdXBkYXRlIGJvdGg/DQo+Pj4gVGhpcyB3YXMgYWxz
byB0aGUgcmVhc29uIGZvciB0aGUgcXVlc3Rpb24gYWJvdXQgYm90aCBUVElEPTAgYW5kIFRMSUQ9
MCwNCj4+IHdoaWNoIGxheWVyIG5lZWQgdXBkYXRlIG9yIGlzIGl0IGJvdGg/DQo+Pj4gQ2FuIHlv
dSBzYXkgdGhhdCB5b3Ugd2FudCBqdXN0IHRvIHVwZGF0ZSB0ZW1wb3JhbCBvciBzcGF0aWFsPw0K
Pj4gDQo+PiBZZXMsIGlmIHRoZSBGQ0kgaGFzIFRUSUQ9MCBhbmQgVExJRD0yLCBpdOKAmXMgYSBy
ZXF1ZXN0IHRvIHVwZGF0ZSBib3RoIGxheWVycyDigJQNCj4+IG9yIG1vcmUgc3BlY2lmaWNhbGx5
LCB0byBtYWtlIHN1cmUgdGhhdCB5b3UgY2FuIHN0YXJ0IGRlY29kaW5nIHRoZSBzdWJzdHJlYW0N
Cj4+IHdpdGggVFRJRD0wIGFuZCBUTElEPTIuIChGb3IgbW9zdCBzY2FsYWJpbGl0eSBzdHJ1Y3R1
cmVzIHRoaXMgd291bGQgbWVhbg0KPj4gdXBkYXRpbmcgYm90aCwgYnV0IGV4b3RpYyBzdHJ1Y3R1
cmVzIGFyZSBwb3NzaWJsZS4pDQo+PiANCj4+IElmIHlvdSB3YW50IHRvIGp1c3QgdXBkYXRlIG9u
ZSBwYXJ0IG9mIHRoZSBzdHJlYW0sIHRoYXTigJlzIHdoYXQgQ1RJRCBhbmQgQ0xJRA0KPj4gYXJl
IGZvci4gIElmIHlvdSBzZW50IFRUSUQ9MCBhbmQgVExJRD0yLCBhY2NvbXBhbmllZCBieSBDVElE
PTAgYW5kIENMSUQ9MCwNCj4+IHRoYXQgbWVhbnMgdGhhdCB5b3UgYWxyZWFkeSBoYXZlIFRJRCAw
LCBhbmQgeW91IGp1c3Qgd2FudCB0byBpbmNyZWFzZSB0aGUNCj4+IExJRC4NCj4+IA0KPj4gVGhl
IGN1cnJlbnQgdGV4dCBpcyBhdCBodHRwczovL2dpdGh1Yi5jb20vanViZXJ0aS9kcmF1Z2h0cy90
cmVlL21hc3Rlci9scnIgLA0KPj4gaWYgeW91IHdhbnQgdG8gdGFrZSBhIGxvb2sgYXQgdGhlIGxh
dGVzdCByZXZpc2lvbnMsIG9yIHN1Z2dlc3QgdGV4dCB0aGF0IHlvdQ0KPj4gdGhpbmsgd291bGQg
bWFrZSBpdCBjbGVhbmVyLg0KPj4gDQo+PiANCj4+PiBSb25pDQo+Pj4gDQo+Pj4+IC0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4+IEZyb206IEdlbi1hcnQgW21haWx0bzpnZW4tYXJ0LWJv
dW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBKb25hdGhhbg0KPj4+PiBMZW5ub3gNCj4+Pj4g
U2VudDog15nXldedINeTIDA3INeZ15XXoNeZIDIwMTcgMDA6MzANCj4+Pj4gVG86IFJvbmkgRXZl
bg0KPj4+PiBDYzogZHJhZnQtaWV0Zi1hdnRleHQtbHJyLmFsbEBpZXRmLm9yZzsgR2VuZXJhbCBB
cmVhIFJldmlldyBUZWFtOw0KPj4+PiBhdnRleHRAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj4+
Pj4gU3ViamVjdDogUmU6IFtHZW4tYXJ0XSBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZg0KPj4+
PiBkcmFmdC1pZXRmLWF2dGV4dC1scnItMDUNCj4+Pj4gDQo+Pj4+IEhpLCBSb25pIOKAlCB0aGFu
a3MgZm9yIHlvdXIgcmV2aWV3LiAgUmVzcG9uc2VzIGlubGluZS4NCj4+Pj4gDQo+Pj4+PiBPbiBK
dW4gMSwgMjAxNywgYXQgMjo1MyBBTSwgUm9uaSBFdmVuIDxyb24uZXZlbi50bHZAZ21haWwuY29t
PiB3cm90ZToNCj4+Pj4+IA0KPj4+Pj4gUmV2aWV3ZXI6IFJvbmkgRXZlbg0KPj4+Pj4gUmV2aWV3
IHJlc3VsdDogUmVhZHkgd2l0aCBJc3N1ZXMNCj4+Pj4+IA0KPj4+Pj4gSSBhbSB0aGUgYXNzaWdu
ZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVyYWwgQXJlYQ0KPj4+
Pj4gUmV2aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5n
IHByb2Nlc3NlZCBieQ0KPj4+Pj4gdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNl
IHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZQ0KPj4+Pj4gYW55IG90aGVyIGxhc3QgY2Fs
bCBjb21tZW50cy4NCj4+Pj4+IA0KPj4+Pj4gRm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBz
ZWUgdGhlIEZBUSBhdA0KPj4+Pj4gDQo+Pj4+PiA8aHR0cHM6Ly90cmFjLmlldGYub3JnL3RyYWMv
Z2VuL3dpa2kvR2VuQXJ0ZmFxPi4NCj4+Pj4+IA0KPj4+Pj4gRG9jdW1lbnQ6IGRyYWZ0LWlldGYt
YXZ0ZXh0LWxyci0/Pw0KPj4+Pj4gUmV2aWV3ZXI6IFJvbmkgRXZlbg0KPj4+Pj4gUmV2aWV3IERh
dGU6IDIwMTctMDUtMzENCj4+Pj4+IElFVEYgTEMgRW5kIERhdGU6IDIwMTctMDYtMDgNCj4+Pj4+
IElFU0cgVGVsZWNoYXQgZGF0ZTogTm90IHNjaGVkdWxlZCBmb3IgYSB0ZWxlY2hhdA0KPj4+Pj4g
DQo+Pj4+PiBTdW1tYXJ5Og0KPj4+Pj4gVGhlIGRvY3VtZW50IGlzIHJlYWR5IHdpdGggaXNzdWVz
IGZvciBhIHN0YW5kYXJkIHRyYWNrIFJGQyBNYWpvcg0KPj4+Pj4gaXNzdWVzOg0KPj4+Pj4gDQo+
Pj4+PiBNaW5vciBpc3N1ZXM6DQo+Pj4+PiANCj4+Pj4+IDEuIENhbiB5b3Ugc3BlY2lmeSBib3Ro
IFRUSUQgYW5kIFRMSUQgaW4gdGhlIHNhbWUgRkNJLg0KPj4+PiANCj4+Pj4gU3ludGFjdGljYWxs
eSwgdGhleSBtdXN0IGJvdGggb2NjdXIuDQo+Pj4+IA0KPj4+PiBJZiB5b3UgbWVhbiBjYW4geW91
IHJlcXVlc3QgYW4gdXBncmFkZSBpbiBib3RoIGF0IG9uY2UsIHllczsgSeKAmXZlDQo+Pj4+IGFk
ZGVkIHRleHQgdG8gY2xhcmlmeSB0aGlzLg0KPj4+PiANCj4+Pj4+IDIuIFdoYXQgaXMgdGhlIG1l
YW5pbmcgb2YgdmFsdWUgMCBmb3IgVFRJRCBhbmQgVExJRCAtIFRJRCBvciBMSUQgPTANCj4+Pj4+
IGluIGZyYW1lIG1hcmtpbmcgZHJhZnQgbWVhbnMgYmFzZSBsYXllciBpZiB0aGVyZSBpcyBzY2Fs
YWJpbGl0eS4NCj4+Pj4+ICAgVGhpcyByZWxhdGVzIHRvIHRoZSBwcmV2aW91cyBxdWVzdGlvbi4N
Cj4+Pj4gDQo+Pj4+IEnigJltIG5vdCBzdXJlIEkgdW5kZXJzdGFuZCB0aGlzIHF1ZXN0aW9uLg0K
Pj4+PiANCj4+Pj4gSeKAmXZlIGFkZGVkIHRleHQgdGhhdCBpZiBDPTEsIGF0IGxlYXN0IG9uZSBv
ZiA8VFRJRCwgVExJRD4gTVVTVCBiZQ0KPj4+PiBncmVhdGVyIHRoYW4gPENUSUQsIENMSUQ+LCBh
bmQgYm90aCBNVVNUIGJlIGdyZWF0ZXIgdGhhbiBvciBlcXVhbCB0bw0KPj4+PiB0aGVpciBjb3Vu
dGVycGFydCwgc28gdGhlIExSUiBpcyBhY3R1YWxseSByZXF1ZXN0aW5nIGEgbGF5ZXIgdXBncmFk
ZS4NCj4+Pj4gSXMgdGhhdCB3aGF0IHlvdSB3ZXJlIGFza2luZyBhYm91dD8NCj4+Pj4gDQo+Pj4+
PiAzLiAgV2hhdCB3b3VsZCBhbiBGQ0kgd2l0aCBib3RoIFRUSUQgYW5kIFRMSUQgZXF1YWwgMCBt
ZWFuLg0KPj4+PiANCj4+Pj4gSXQgbWVhbnMgeW91IHdhbnQgYSByZWZyZXNoIG9mIHRoZSBiYXNl
IHRlbXBvcmFsL3NwYXRpYWwgbGF5ZXIsIG9ubHkuDQo+Pj4+IA0KPj4+Pj4gTml0cy9lZGl0b3Jp
YWwgY29tbWVudHM6DQo+Pj4+PiANCj4+Pj4+IDEuIFNlY3Rpb24gMyAiYW4gUmVhbC1UaW1lIFRy
YW5zcG9ydCBDb250cm9sIFByb3RvY29sIiBzaG91bGQgYmUgImENCj4+Pj4+IFJlYWzigKYiLg0K
Pj4+PiANCj4+Pj4gQ29saW4gcG9pbnRlZCBvdXQgdGhhdCBpdCBzaG91bGQgc2F5IOKAnGFuIFJU
UCBDb250cm9sIFByb3RvY29s4oCdIGFueXdheS4NCj4+Pj4gDQo+Pj4+PiAyLiBJbiBzZWN0aW9u
IDMgIiBbUkZDNTEwNF0oU2VjdGlvbiAzLjUuMSkiIHRoZXJlIGlzIGEgbGluayB0bw0KPj4+Pj4g
c2VjdGlvbg0KPj4+Pj4gMy41LjEgYnV0IGl0IGRvZXMgbm90IHdvcmsuDQo+Pj4+IA0KPj4+PiB4
bWwycmZjIGRvZXNu4oCZdCBoYXZlIGFueSB3YXkgdG8gbGluayB0byBzZWN0aW9ucyBvZiBvdGhl
ciBkb2N1bWVudHMsDQo+Pj4+IHNvIHRoZSDigJwoU2VjdGlvbiAzLjUuMSnigJ0gcGFydCBpcyBq
dXN0IGEgY29tbWVudC4NCj4+Pj4gDQo+Pj4+IEkgdGhpbmsgdGhlIGludGVybmV0LWRyYWZ0IHRv
b2xpbmcgbWF5IGhhdmUgdGhvdWdodCBJIHdhcyB0cnlpbmcgdG8NCj4+Pj4gbGluayB0byBhIG5v
bi1leGlzdGVudCBzZWN0aW9uIDMuNS4xIG9mIHRoaXMgZG9jdW1lbnQsIGJ1dCB0aGF04oCZcyBv
dXRzaWRlDQo+PiBteSBjb250cm9sLg0KPj4+PiANCj4+Pj4+IDMuIEluIHNlY3Rpb24gMy4yICIo
c2VlIHNlY3Rpb24gU2VjdGlvbiAyLjEpIiBzZWN0aW9uIGFwcGVhcnMgdHdpY2UuDQo+Pj4+IA0K
Pj4+PiBGaXhlZC4NCj4+Pj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX18NCj4+Pj4gR2VuLWFydCBtYWlsaW5nIGxpc3QNCj4+Pj4gR2VuLWFydEBpZXRmLm9y
Zw0KPj4+PiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dlbi1hcnQNCj4g
DQoNCg==


From nobody Tue Jun 13 09:30:19 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 DBE61128B88 for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 09:30:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 VbDqWvnGrmr1; Tue, 13 Jun 2017 09:30:16 -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 5114912EB1D; Tue, 13 Jun 2017 09:27:23 -0700 (PDT)
Received: by mail-wr0-x229.google.com with SMTP id q97so151108364wrb.2; Tue, 13 Jun 2017 09:27:23 -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=4HDmx810Nw1e6vk2d1nybTexsBPk2rByn1EdnWUxrco=; b=s5BgqLk8TUL/FfHpHYaRaJ3Uxq9K9jjMWHg2C1tjsU5si93ys6Gnx1SuEIzAvf1ep5 2QA6j/K01aUt7X4mcQ4qKunHYP2PltTUgco0U1b7EtqsCPrFPIWgWOK1rewC1B3iWCVG 5WWQZY0QIyJdMGS/n/QjuUFvELEgIrudMg03rOPaL9x71V+e59e71FM/8nLmz/5wbACy bl1tmSTR7yUntMTED+EfG+9snW7GlXmZOmLFAR32it2h+ukNID5HFDyudKrQQa/sB9JT +BhUHyUOspq1Cqh1Zsumi5ilumVBO9L5fyeukOWOgudrgN1jdGPP/g+kMNunLQJ73x3r EpTg==
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=4HDmx810Nw1e6vk2d1nybTexsBPk2rByn1EdnWUxrco=; b=sVQsBijanPcsfl1oaUoHQsR+PicQnktNk9LH9gF5jilbzTRkhvuQAuNRDweN1dBXSB 6Uo09EPmue2UV0KDpr7Bdfl6yrtc2yD++Crd0mgKOAPojo7MeP8YjPCrO74bV14ax92H 4wKbLPlto9m87WDTWKhTotNU98gHnB+htdashB6HQMtRr+ZWuZVzr3UxHG+gKulaqi0U eyrybRnqMwxNsPqU3/NnwqVNXH6jYA/KyH9oDHM7sUpT4ZOqoUnnaaMGd329gP20ilWJ KTTbw9e2ny1UdRcQ0ilNJSAtuTXU24R258LWrszEPanvYh6XvkUyOzkWv5Tndju9mbwi wxOg==
X-Gm-Message-State: AKS2vOy8rM8NYlpSbFiSYYbPgHui9/CJZ8HtUuwZaOwbTHAGh8XV7Acu xgwxo+NdxAKDDA==
X-Received: by 10.223.129.230 with SMTP id 93mr3903666wra.57.1497371241853; Tue, 13 Jun 2017 09:27:21 -0700 (PDT)
Received: from ?IPv6:2601:647:4d01:db10:1d58:9ab5:9f1d:4035? ([2601:647:4d01:db10:1d58:9ab5:9f1d:4035]) by smtp.gmail.com with ESMTPSA id w52sm11901295wrc.33.2017.06.13.09.27.19 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Jun 2017 09:27:20 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <41F56A3A-1536-4546-9AEA-CC7674DC9546@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_026E2E82-A4EA-4CD0-9F8D-269D7F8057E9"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: IAD retirement
Date: Tue, 13 Jun 2017 09:27:05 -0700
In-Reply-To: <m2r2ync3hf.wl-randy@psg.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, Leslie Daigle <ldaigle@thinkingcat.com>, IETF <ietf@ietf.org>, IAOC Chair <iaoc-chair@ietf.org>
To: Randy Bush <randy@psg.com>
References: <149731904993.7732.10262100091459990539.idtracker@ietfa.amsl.com> <m28tkwe6xw.wl-randy@psg.com> <33EB1557-0054-467D-B22F-3AF6BEC36640@thinkingcat.com> <m27f0gc4zj.wl-randy@psg.com> <69BF8040-E0EE-468C-B29E-9BA9B4EF37DA@thinkingcat.com> <m2r2ync3hf.wl-randy@psg.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/fuYQTEAAfADN8QKrpZAAH1X3rDA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 16:30:18 -0000

--Apple-Mail=_026E2E82-A4EA-4CD0-9F8D-269D7F8057E9
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii


> On Jun 13, 2017, at 8:27 AM, Randy Bush <randy@psg.com> wrote:
> 
> evenin' leslie,
> 
>> Unless IASA2.0 moves along much more quickly than most IETF things, by
>> the time Ray retires, it will still be ISOC doing the employment.  It
>> will still be the IAOC (subcommittee) doing the search and selection.
> 
> that answers my question spot on, and allay's my worries.  thanks.

Same for me.

Bob



--Apple-Mail=_026E2E82-A4EA-4CD0-9F8D-269D7F8057E9
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

iQEcBAEBCgAGBQJZQBJZAAoJEK7rdBF357uo/vUH/0FNoDTkvJlZiZMJRyHzBnCG
Utgyqh04cKJ+XqPMNH6xajFbVpxt9T2yteTUyIPIN0GmYsWMIJH36eulvvZ2ChiA
/lJOGKnh0B6fU9D0fMd4ZxojOuH9HWYdCFFoXISb8uBVPUtMWqIxBElYWDCZC7NX
2biRdc22cfKOtzmQJ4ZqOJ6/zLu50kDt1hngb8fej8dD7zTv9qVaZ5Sy19UPIIWr
quatrTykU9USCo5bFFd5NNQX060pG5HyWl3pwjnUmFdFYUV8CVFMVGdMQHZpBttQ
S4jfcGEEWh/5gWaUAAv94kbnS73Da5J78EsccGILToHybdK6DRLIiQK2Nkp9BAA=
=Mxkk
-----END PGP SIGNATURE-----

--Apple-Mail=_026E2E82-A4EA-4CD0-9F8D-269D7F8057E9--


From nobody Tue Jun 13 10:14:15 2017
Return-Path: <ron.even.tlv@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 D155313194D; Tue, 13 Jun 2017 10:14:12 -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 XmbRrV0SaI3t; Tue, 13 Jun 2017 10:14:08 -0700 (PDT)
Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::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 683CD131929; Tue, 13 Jun 2017 10:14:08 -0700 (PDT)
Received: by mail-wr0-x22e.google.com with SMTP id 77so5440421wrb.1; Tue, 13 Jun 2017 10:14:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:content-language :thread-index; bh=WPKwBahHEhFhZc3y6c7xCvIlIxqbk7z4o8dO8fSRi/w=; b=sThW0w6x7F3kDLIt2sVqvMFcsVndhvLdPtN5mYNlL5eJVj2TEh/B5/Mwr9SB+Cokhm Ip92dGufih2q4Nh2X8u6Q0U/bzprokz3HimtWl/wbBTXtD9zpbww0WWWuZXs2kn8GQrb nYNMmiGk6CnLsM+6helVq03p/7rNzKWmbFPnONMzzFzHYDWfJpfAXT+I5zOalLwxHq6w 1RA/o6EBL1hTxCpdPE9Mtuv1haKXRdcNnwzmdAnAQcNqna7IfjZ+jGW5ph7DOG6UJqVG AUur2BvNk+382RcoX1qLILdGGD2xNsI8T96Ny15WfapbeYfjcdrzn/Zo+srL9ksLS6Sj B32A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:content-language :thread-index; bh=WPKwBahHEhFhZc3y6c7xCvIlIxqbk7z4o8dO8fSRi/w=; b=MBh5MjBWzX0Of6Aggtahz3DIaN819mmscZ4WX/Fyod4we0IjS3O5M7YdS5C+ClUeg0 aajDxYCaChXf20+dX/z1XBDfAnQF4CuHrUhFAU/COcJLZZ0QU1PNkJy9nGeSAD9aTidf oyiuxbcPm556aK+DIZb7liE3OWr8DG/ATP0J1GhjiMflNzQsS4Ur753OZ5foXBSmGtev 20sw19K8fc54Thqj1LgbV/ouIW50y5+NHMXg8jUd85yViddylZKRqSrK/M/bnOKQz6sb rzaVe6cuTiI4rd0V6dGu8kYpfTOviVHXRrtqKKu/wBXa711wsDuLxt3DvlCx50dj+YYP 7d8Q==
X-Gm-Message-State: AKS2vOzH0wC+3zfniVyYxNmlVvH/kf5RQpT+rFxZ19+xZTpon24JGFi1 8if/mjIRPpH1zzyt
X-Received: by 10.28.97.8 with SMTP id v8mr3662247wmb.72.1497374046598; Tue, 13 Jun 2017 10:14:06 -0700 (PDT)
Received: from RoniPC (bzq-109-64-51-177.red.bezeqint.net. [109.64.51.177]) by smtp.gmail.com with ESMTPSA id e24sm22763380wre.54.2017.06.13.10.14.04 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 13 Jun 2017 10:14:05 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Jonathan Lennox'" <jonathan@vidyo.com>, "'Roni Even'" <roni.even@huawei.com>
Cc: <draft-ietf-avtext-lrr.all@ietf.org>, "'General Area Review Team'" <gen-art@ietf.org>, <avtext@ietf.org>, <ietf@ietf.org>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com> <B9294064-4F4E-4FA1-A864-4F9790767B5C@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7D0641@DGGEMM506-MBX.china.huawei.com> <116D9947-414D-47EB-A0C7-8031999E5A89@vidyo.com>
In-Reply-To: <116D9947-414D-47EB-A0C7-8031999E5A89@vidyo.com>
Subject: RE: Genart last call review of draft-ietf-avtext-lrr-05
Date: Tue, 13 Jun 2017 20:13:37 +0300
Message-ID: <01fe01d2e468$662f18e0$328d4aa0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-Language: he
Thread-Index: AQEOBITKuJRO9nhiFivT7qoen86ZIALweQwbARran8oBJBqhhQNABGFpAZ6UghajXFYNEA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xfO5L8Wk7sKerbI9gzCFQRDmqLU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 17:14:13 -0000

Hi Jonathan,
This will be good but maybe explain the upgrade means also refresh. =
Because my poor understanding in English is that upgrade is adding a new =
layer that was not available to the media receiver while refresh is to =
restore existing layer (e.g. decoder synchronization loss).
Roni

> -----Original Message-----
> From: Jonathan Lennox [mailto:jonathan@vidyo.com]
> Sent: Tuesday, June 13, 2017 7:03 PM
> To: Roni Even
> Cc: Roni Even; draft-ietf-avtext-lrr.all@ietf.org; General Area Review =
Team;
> avtext@ietf.org; ietf@ietf.org
> Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
>=20
> Hi, Roni =E2=80=94
>=20
> You seem to be assuming that a refresh and an upgrade are two =
different
> actions.  That=E2=80=99s not the intention =E2=80=94 a refresh is a =
characteristic of a stream that
> allows a decoder to upgrade.
>=20
> I=E2=80=99ll try to draft some text that makes it clear that =
it=E2=80=99s possible either to
> independently upgrade temporal or spatial, or else upgrade both at =
once.
>=20
> > On Jun 11, 2017, at 7:20 AM, Roni Even <roni.even@huawei.com> wrote:
> >
> > Hi Jonathan,
> > I assume the new text you propose is
> >
> > "When C is 1, TTID MUST NOT be less than CTID, and TLID MUST NOT be
> >   less than CLID; at least one of TTID or TLID MUST be greater than
> >   CTID or CLID respectively.  That is to say, the target layer index
> >   <TTID, TLID> MUST be a layer upgrade from the current layer index
> >   <CTID, CLID>.  A sender MAY request an upgrade in both temporal =
and
> >   spatial/quality layers simultaneously."
> >
> > I think that this text still only implies the behavior, also the
> > current text talks about upgrade but I assume it is also for a =
refresh
> > not only to upgrade
> >
> > Maybe " A sender MAY request an upgrade or refresh  in both temporal =
and
> >   spatial/quality layers simultaneously by either having C =3D1 or =
by having both
> CLID and CTID with lower values then TTID and TLID. If the sender want =
to
> upgrade or refresh only one layer then C MUST be equal to 1 and only =
the CTID
> or  the CLID of the layer to be upgraded or refreshed should be lower =
than the
> TTID or TLID respectively "
> >
> >
> > Roni
> >> -----Original Message-----
> >> From: Jonathan Lennox [mailto:jonathan@vidyo.com]
> >> Sent: =D7=99=D7=95=D7=9D =D7=93 07 =D7=99=D7=95=D7=A0=D7=99 2017 =
18:30
> >> To: Roni Even
> >> Cc: Roni Even; draft-ietf-avtext-lrr.all@ietf.org; General Area
> >> Review Team; avtext@ietf.org; ietf@ietf.org
> >> Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
> >>
> >>
> >>> On Jun 7, 2017, at 1:15 AM, Roni Even <roni.even@huawei.com> =
wrote:
> >>>
> >>> Hi Jonathan,
> >>> I did not see the text you added yet as a response to my first
> >>> question So to better clarify my question . If the FCI has =
TTID=3D0 and TLID=3D2
> .
> >> does it mean that it is a request to update both?
> >>> This was also the reason for the question about both TTID=3D0 and
> >>> TLID=3D0,
> >> which layer need update or is it both?
> >>> Can you say that you want just to update temporal or spatial?
> >>
> >> Yes, if the FCI has TTID=3D0 and TLID=3D2, it=E2=80=99s a request =
to update both
> >> layers =E2=80=94 or more specifically, to make sure that you can =
start
> >> decoding the substream with TTID=3D0 and TLID=3D2. (For most =
scalability
> >> structures this would mean updating both, but exotic structures are
> >> possible.)
> >>
> >> If you want to just update one part of the stream, that=E2=80=99s =
what CTID
> >> and CLID are for.  If you sent TTID=3D0 and TLID=3D2, accompanied =
by
> >> CTID=3D0 and CLID=3D0, that means that you already have TID 0, and =
you
> >> just want to increase the LID.
> >>
> >> The current text is at
> >> https://github.com/juberti/draughts/tree/master/lrr , if you want =
to
> >> take a look at the latest revisions, or suggest text that you think =
would make
> it cleaner.
> >>
> >>
> >>> Roni
> >>>
> >>>> -----Original Message-----
> >>>> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of
> >>>> Jonathan Lennox
> >>>> Sent: =D7=99=D7=95=D7=9D =D7=93 07 =D7=99=D7=95=D7=A0=D7=99 2017 =
00:30
> >>>> To: Roni Even
> >>>> Cc: draft-ietf-avtext-lrr.all@ietf.org; General Area Review Team;
> >>>> avtext@ietf.org; ietf@ietf.org
> >>>> Subject: Re: [Gen-art] Genart last call review of
> >>>> draft-ietf-avtext-lrr-05
> >>>>
> >>>> Hi, Roni =E2=80=94 thanks for your review.  Responses inline.
> >>>>
> >>>>> On Jun 1, 2017, at 2:53 AM, Roni Even <ron.even.tlv@gmail.com>
> wrote:
> >>>>>
> >>>>> 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.
> >>>>
> >>>> Syntactically, they must both occur.
> >>>>
> >>>> If you mean can you request an upgrade in both at once, yes; =
I=E2=80=99ve
> >>>> added text to clarify this.
> >>>>
> >>>>> 2. What is the meaning of value 0 for TTID and TLID - TID or LID
> >>>>> =3D0 in frame marking draft means base layer if there is =
scalability.
> >>>>>   This relates to the previous question.
> >>>>
> >>>> I=E2=80=99m not sure I understand this question.
> >>>>
> >>>> I=E2=80=99ve added text that if C=3D1, at least one of <TTID, =
TLID> MUST be
> >>>> greater than <CTID, CLID>, and both MUST be greater than or equal
> >>>> to their counterpart, so the LRR is actually requesting a layer =
upgrade.
> >>>> Is that what you were asking about?
> >>>>
> >>>>> 3.  What would an FCI with both TTID and TLID equal 0 mean.
> >>>>
> >>>> It means you want a refresh of the base temporal/spatial layer, =
only.
> >>>>
> >>>>> Nits/editorial comments:
> >>>>>
> >>>>> 1. Section 3 "an Real-Time Transport Control Protocol" should be
> >>>>> "a Real=E2=80=A6".
> >>>>
> >>>> Colin pointed out that it should say =E2=80=9Can RTP Control =
Protocol=E2=80=9D anyway.
> >>>>
> >>>>> 2. In section 3 " [RFC5104](Section 3.5.1)" there is a link to
> >>>>> section
> >>>>> 3.5.1 but it does not work.
> >>>>
> >>>> xml2rfc doesn=E2=80=99t have any way to link to sections of other
> >>>> documents, so the =E2=80=9C(Section 3.5.1)=E2=80=9D part is just =
a comment.
> >>>>
> >>>> I think the internet-draft tooling may have thought I was trying =
to
> >>>> link to a non-existent section 3.5.1 of this document, but =
that=E2=80=99s
> >>>> outside
> >> my control.
> >>>>
> >>>>> 3. In section 3.2 "(see section Section 2.1)" section appears =
twice.
> >>>>
> >>>> Fixed.
> >>>> _______________________________________________
> >>>> Gen-art mailing list
> >>>> Gen-art@ietf.org
> >>>> https://www.ietf.org/mailman/listinfo/gen-art
> >



From nobody Tue Jun 13 10:51:01 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 6EF3312940E for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 10:50:59 -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, 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 XIn-khL6VlvM for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 10:50:57 -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 6065B129457 for <ietf@ietf.org>; Tue, 13 Jun 2017 10:50:57 -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 1dKpxv-0001RF-HZ for ietf@ietf.org; Tue, 13 Jun 2017 19:50:56 +0200
Received: from [10.5.2.14] (helo=xmail04.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 1dKpxL-0006uw-I3 for ietf@ietf.org; Tue, 13 Jun 2017 13:50:54 -0400
Received: (qmail 21134 invoked from network); 13 Jun 2017 17:50:18 -0000
Received: from unknown (HELO [192.168.1.102]) (Authenticated-user:_huitema@huitema.net@[172.56.42.233]) (envelope-sender <huitema@huitema.net>) by xmail04.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 13 Jun 2017 17:50:17 -0000
To: ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net>
Date: Tue, 13 Jun 2017 10:50:15 -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: <20170613142820.GA21291@shrubbery.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
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: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.11)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJYWea6pBBugJdVQWCV6zgcsND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA23IdxAa/6wyZqjl8q/NM7FC9SM4jd3ClxbkF2U h0iAyfIygF6zTQtZdySc8DvnR0L9YOEkjsX7F8KmpUaZQHV+SU9tg6wnJ2lrZSUCZrKFYsG2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpKrrXdhf8mmRqp8CWMEqUPf6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGyb/vZCXPdDTJVPxsRKQ1gwbeNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj236N2IVdgBdepwvDBBcDOz9LNdSMuNhZC3X/nGdDKYyg+1Fotn1TGspRGWfHjmaruO0b XpkevaElTi+sCWwmqxHi+BUHXGjp0J8FpT+J6AFTxh8XBHmF2hIeyKfJwZiM12egGl1aPxAtivmw 3hSDPS17fNbvgiPfI1SrJRLFdrj7Fy2wErj03uQL9OSP3oAqkbgmxYRXOZgzdAQCjuYKoBVKyLoA 6S28+bT6JBt5hIe9NsT+zJGLhBRfUiVo7tDfe92IvYPtoBVPF/cFj7Q8A7EvMLn6MURQGfriekzS 9Ga3AA==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/r8njHZ6ys9q0CrxxwuYw8g8e20w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 17:50:59 -0000

On 6/13/2017 7:28 AM, heasley wrote:
> Tue, Jun 13, 2017 at 05:10:41AM -0400, John C Klensin:
>> --On Tuesday, June 13, 2017 03:38 +0000 heasley
>> <heas@shrubbery.net> wrote:
>>
>>> Mon, Jun 12, 2017 at 06:29:30AM -0700,
>>> internet-drafts@ietf.org:
>>>>         Title           : The Harmful Consequences of
>>>>         Postel's Maxim
>>>> https://tools.ietf.org/html/draft-thomson-postel-was-wrong-01
>>> Perhaps instead of requiring two implementations for a
>>> protocol draft to proceed to rfc, it should first or also have
>>> a test suite that
>>>
>>>         ... fails noisily in response to bad or undefined
>>> inputs.
>>>
>>> Having a community-developed test suite for any protocol would
>>> be a great asset.

I am not a great fan of the test suite approach. I saw that used in OSI
protocols back in the days, and there are multiple issues -- including
for example special-casing the test suite in the implementation.

To come back to Martin's draft, I think two points are missing. One
about change, and one about grease. First, the part about change. The
Postel Principle was quite adequate in the 80's and 90's, when the
priority was to interconnect multiple systems and build the Internet.
Writing protocols can be hard, especially on machines with limited
resource. Many systems were gateways, interfacing for example Internet
mail with preexisting mainframe systems, and the protocol
implementations could not hide the quirkiness of the system that they
were interfacing. The principle was a trade-off. It made development and
interoperability easier, by tolerating some amount of non-conformance.
As the draft point out, it also tends to make evolution somewhat harder
-- although that probably cuts both ways, as overly rigid
implementations would also be ossified. Martin's draft advocates a
different trade-off. It would be nice to understand under which
circumstances the different trade-offs make sense.

Then there is grease, or greasing, which is a somewhat recent
development. The idea is to have some implementations forcefully
exercise the extension points in the protocol, which will trigger a
failure if the peer did not properly implement the negotiation of these
extensions, "grease the joints" in a way. That's kind of cool, but it
can only be implemented by important players. If an implementation has
0.5% of the market, it can try greasing all it wants, but the big
players might just as well ignore it, and the virtuous greasers will
find themselves cut off. On the other hand, if a big player does it, the
new implementations had better conform. Which means that greasing is
hard to distinguish from old fashioned "conformity with the big
implementations", which might have some unwanted consequences. Should it
be discussed?

-- Christian Huitema



From nobody Tue Jun 13 13:57:59 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 13CA21296C6; Tue, 13 Jun 2017 13:57:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 jCKjF9Ln2Ew3; Tue, 13 Jun 2017 13:57:50 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::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 7D954128DE5; Tue, 13 Jun 2017 13:57:50 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id x63so73375701pff.3; Tue, 13 Jun 2017 13:57:50 -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=+wqfUt/u6PBkPfqT1BdBj9TCgJRRgfnhLwXpjWTgfkE=; b=TXLB057JY/M1+QrSxGlUmYfDh3GJrDlo5HcZ3dS9uqCDqffMDZhTKWs+uqcj5sqsmZ QcHlHjXzYMtrYu20n2Syh+eKapSX6If5Iuu9BbiH3LV0fcwiAKcRix6xlsKjsqU8+b9i EwGmQJK/gZ04qsSsmsH9rVlF7jNfyYDn6h4QkZwurl4HaKr+W5FC4B7yM6C3Gn64doUz M4Qp1LavzYTiYyGi8kFELKapEWm7pY3QKtsIB4RcXSGFsyQxPNLABQUdp0EuZ8ndcUE3 YBzBDQ26HEve53TL1SJoXqHZXwNhiW6RTxndj9mL9Xr2Ymcfv36wcU/OiBovkpVqENzN X8NA==
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=+wqfUt/u6PBkPfqT1BdBj9TCgJRRgfnhLwXpjWTgfkE=; b=mW0qaiI9pLPP3aWuEupPSQ20wmw2Q9PkN8v7ISMx9SS4NxVGAhMK7N3VW0a65eoNtZ 5CeWTpmebA51fuwRDycWAw7ouF+h7gZici7/VfbCWFXO+SYIF3eU0Qjvtch1f1ClmCHf IRKmfuM76OnPcCkeTcsZrmi/ZLFSGAVB5oFw7lzS7NZrI26Dw1zBQ2VDVQFMHzEvQp1y TMRJnPZ9fQGVyuspADF7vv7hpR4b52uPFp95BwKmuCk0Oo2iM2M7E8BmW6kC5eIM3H0Z HT0erw9PzxGuT3lrQ71jfEqEstTMHZcSE/u7xdBLks4fHk55OusoIfvICuxJNC0hCQT6 XDww==
X-Gm-Message-State: AKS2vOwFzrPvSXGw5QEkksDk4n6phbF62mwZrtk0FTiONmwNiBykqEVx ZEiE4b+j3uvnwJPX945Uszdc1zNxqQ==
X-Received: by 10.84.209.199 with SMTP id y65mr1503304plh.205.1497387470191; Tue, 13 Jun 2017 13:57:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.169.13 with HTTP; Tue, 13 Jun 2017 13:57:09 -0700 (PDT)
In-Reply-To: <149616615640.19877.7389294095180042080@ietfa.amsl.com>
References: <149616615640.19877.7389294095180042080@ietfa.amsl.com>
From: Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>
Date: Tue, 13 Jun 2017 16:57:09 -0400
Message-ID: <CAHbuEH6L0JRUGXcjc-AocsqNDaUYO6rygdaZhHXBWmjnWt=8bw@mail.gmail.com>
Subject: Re: Secdir last call review of draft-ietf-sacm-requirements-15
To: Barry Leiba <barryleiba@computer.org>
Cc: "secdir@ietf.org" <secdir@ietf.org>, draft-ietf-sacm-requirements.all@ietf.org,  IETF <ietf@ietf.org>, "sacm@ietf.org" <sacm@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j7JwaBeyAvwHBbLPuM84FJP0vKI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 20:57:52 -0000

Hi Barry,

Thank you, for your review. It's much appreciated!  The SACM WG has
had this as a planned working group item and has wanted it published
from the start.  I checked again at the interim last week and it is
the WG's preference to publish this informational draft.  I did ask
about linking the draft to a wiki.

I'm supporting the WG's decision and feel that it is important for
their progress to move beyond this milestone.

Thanks for catching the nit, we'll make sure that gets corrected.

Best,
Kathleen

On Tue, May 30, 2017 at 1:42 PM, Barry Leiba <barryleiba@computer.org> wrote:
> 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".
>



-- 

Best regards,
Kathleen


From nobody Tue Jun 13 15:03:26 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 93ACB129AAD for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 15:03:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 KS77VxyXr7Ln for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 15:03:24 -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 14ED4131920 for <ietf@ietf.org>; Tue, 13 Jun 2017 15:03:24 -0700 (PDT)
Received: from [128.9.184.182] ([128.9.184.182]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v5DM36Ap002359 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 13 Jun 2017 15:03:07 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: Christian Huitema <huitema@huitema.net>, ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu>
Date: Tue, 13 Jun 2017 15:03:07 -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: <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net>
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/gaITMZBvruK13tCPpjTNk_2wUts>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 22:03:25 -0000

Hi, all,

...
>   Title           : The Harmful Consequences of
>         Postel's Maxim
> https://tools.ietf.org/html/draft-thomson-postel-was-wrong-01
I completely agree with John Klensin that a test suite defines the
protocol standard (warts and all).

However, I disagree with the characterization of the Postel Principle in
this doc, and strongly disagree with one of its key conclusions ("fail
noisily in response to...undefined inputs"). Failing in response to bad
inputs is fine, but "undefined" needs to be treated agnostically.

IMO, the Postel Principle is an admission of that sort of agnosticism -
if you don't know how the other end will react, act conservatively. If
you don't know what the other end intends, react conservatively. Both
are conservative actions - in one sense, you try not to trigger
unexpected behavior (when you send), and in another you try not to
create that unexpected behavior (when you receive).

That's the very definition of how unused bits need to be handled. Send
conservatively (use the known default value), but allow any value upon
receipt.

The principle does not setup the feedback cycle in Sec 2; a bug is a bug
and should be fixed, and accommodating alternate behaviors is the very
definition of "be generous in what you receive". "Being conservative in
what you send" doesn't mean "never send anything new" - it means do so
only deliberately.

-----
Failing noisily is, even when appropriate (e.g., on a known incorrect
input), an invitation for a DOS attack.

That behavior is nearly as bad as interpreting unexpected (but not
prohibited) behavior as an attack. Neither one serves a useful purpose
other than overreaction, which provides increased leverage for a real
DOS attack.

Joe


From nobody Tue Jun 13 15:19:30 2017
Return-Path: <dave@cridland.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4304E128B8F for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 15:19:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cridland.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6CWC4iiip2Id for <ietf@ietfa.amsl.com>; Tue, 13 Jun 2017 15:19:26 -0700 (PDT)
Received: from mail-yb0-x232.google.com (mail-yb0-x232.google.com [IPv6:2607:f8b0:4002: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 64C5912871F for <ietf@ietf.org>; Tue, 13 Jun 2017 15:19:26 -0700 (PDT)
Received: by mail-yb0-x232.google.com with SMTP id t7so11523842yba.3 for <ietf@ietf.org>; Tue, 13 Jun 2017 15:19:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cridland.net; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=oNaCZvtuOybRzqxeiQ/h+Cglc4Tk7o9CRgUoMoP5TAo=; b=ULzv9HxIZAfRcaUdgYJ52RVeNf2QRIPC5bqldk117Rv+F3NJ0nDq1AP9sbwW6I39k5 2hGt6RwejlyoDiYp8LpUo2DrQsS3LONA0gjbAsr43K8duDHk4nQcVRu9lbb/7U70CAC0 PzDsCL3YbmcRaCioOVHCe6hj3gx5SWZlXhv28=
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=oNaCZvtuOybRzqxeiQ/h+Cglc4Tk7o9CRgUoMoP5TAo=; b=IpfPPbnYvcsoc8aSPmr20T8g3xnux/MjQvDA4m3B/12O7kPK/IipuRARY58WVjQeID PtDIrqNDZRpdss82QcKLYY4b/zzUdC638qwUVmehSX+8sw66WXTCIls51C6ZiRolA6W3 Iesi5pdPavK4L2ELbPc8CA4pVNgUxNujrsS+VrDQZi2UK5npCEn69zDYNg2FDeSasNUt JB2T4JzY+etcZSsmne2tzjy/Tkaj+mzm0eWq+m6jXZvxKqQIX3WPMCazXDV1CTiDefu5 uU7YnyPniJLoByJYMwMAIaghN/9EvZSrfZznJfOGOEZ0AwmcOKQN/Alo4XCNE9egMrHH yf5Q==
X-Gm-Message-State: AKS2vOxV9MLJPT+LlynTfEO+yxKB1Z4S3r8hGcK/k6fqAhlf+wXJ6FuR t02+8qlfFcGfxJjHsCAlnR8WYUHEwvrhUgM=
X-Received: by 10.37.193.71 with SMTP id r68mr5138267ybf.51.1497392365537; Tue, 13 Jun 2017 15:19:25 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.25.195 with HTTP; Tue, 13 Jun 2017 15:19:25 -0700 (PDT)
In-Reply-To: <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net>
From: Dave Cridland <dave@cridland.net>
Date: Tue, 13 Jun 2017 23:19:25 +0100
Message-ID: <CAKHUCzy1gn4eu3cAHViAF=Xwa=uqcEkTi380Gobac7yZ6ruNzw@mail.gmail.com>
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: Christian Huitema <huitema@huitema.net>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9S3y2Pb9YPfYupf0g28KREt_fac>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 22:19:28 -0000

On 13 June 2017 at 18:50, Christian Huitema <huitema@huitema.net> wrote:
> Then there is grease, or greasing, which is a somewhat recent
> development. The idea is to have some implementations forcefully
> exercise the extension points in the protocol, which will trigger a
> failure if the peer did not properly implement the negotiation of these
> extensions, "grease the joints" in a way. That's kind of cool, but it
> can only be implemented by important players. If an implementation has
> 0.5% of the market, it can try greasing all it wants, but the big
> players might just as well ignore it, and the virtuous greasers will
> find themselves cut off. On the other hand, if a big player does it, the
> new implementations had better conform. Which means that greasing is
> hard to distinguish from old fashioned "conformity with the big
> implementations", which might have some unwanted consequences. Should it
> be discussed?

I think the pressure of large deployments on smaller ones works in
both good, and more often bad, ways. Within the XMPP community, we saw
this multiple times. Facebook and Google both deployed XMPP services
over the years, and both were larger than the rest of the community
put together. You've described this case as "important players", but
I'd prefer to simply describe them as large.

Facebook's involvement was restricted to client/server (C2S) links,
and in general worked reasonably well, though various custom
extensions were used that performed similar functions to standardized
ones.

Google's service did not support SRV lookups, and mandated the (at the
time) legacy immediate-mode TLS instead of XMPP's standard Start TLS,
for example. This was by design, apparently for security (though
likely for deployment considerations), but had the effect that client
developers often had to hardcode server discovery for the service.

Google did provide S2S peering, but - paradoxically given the above -
did not operate TLS at all, preventing any other service from
mandating TLS for several years. When Google withdrew support for the
service (about four years ago with the introduction of Hangouts), the
community almost universally switched to mandatory TLS within a few
months.

At the same time, Google's S2S peering made heavy use of multiplexing
(known as piggybacking within XMPP), which was unusual at the time,
and could easily cause problems with servers - these servers were
simply forced to update. One might consider this case "virtuous
greasing".

One can very easily look at DMARC as another example of larger players
versus small - DMARC obviously fails to work in the mailing list case
(amongst others), yet the large deployments simply don't care, since
it solves their problems, and to hell with everyone else.

Perhaps standards simply work best in a balanced community?


From nobody Tue Jun 13 15:48:53 2017
Return-Path: <prvs=23375b132e=jonathan@vidyo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF734131A57; Tue, 13 Jun 2017 15:48:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Nx8myBJ7PI6; Tue, 13 Jun 2017 15:48:48 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0b-00198e01.pphosted.com [67.231.157.197]) (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 988BA12EB58; Tue, 13 Jun 2017 15:48:48 -0700 (PDT)
Received: from pps.filterd (m0073110.ppops.net [127.0.0.1]) by mx0b-00198e01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v5DMhgj5022907; Tue, 13 Jun 2017 18:48:35 -0400
Received: from mail.vidyo.com (mail2.vidyo.com [162.209.16.214]) by mx0b-00198e01.pphosted.com with ESMTP id 2b0bh4jbdp-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Tue, 13 Jun 2017 18:48:35 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Tue, 13 Jun 2017 17:48:34 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Roni Even <ron.even.tlv@gmail.com>
CC: Roni Even <roni.even@huawei.com>, "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>, General Area Review Team <gen-art@ietf.org>, "avtext@ietf.org" <avtext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMAgAAtEkCAAQCzAIAFrKRwgAPKzwCAABOJgIAAXZUA
Date: Tue, 13 Jun 2017 22:48:34 +0000
Message-ID: <D99B14A9-C6A4-456B-AEFA-8819B9EF6760@vidyo.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com> <B9294064-4F4E-4FA1-A864-4F9790767B5C@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7D0641@DGGEMM506-MBX.china.huawei.com> <116D9947-414D-47EB-A0C7-8031999E5A89@vidyo.com> <01fe01d2e468$662f18e0$328d4aa0$@gmail.com>
In-Reply-To: <01fe01d2e468$662f18e0$328d4aa0$@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <C73136AE653C3841BC4A5610769C2DF3@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-13_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706130390
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zbt4M_cm563tO2bJQt1Ed1h6ze0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 13 Jun 2017 22:48:50 -0000

DQo+IE9uIEp1biAxMywgMjAxNywgYXQgMToxMyBQTSwgUm9uaSBFdmVuIDxyb24uZXZlbi50bHZA
Z21haWwuY29tPiB3cm90ZToNCj4gDQo+IEhpIEpvbmF0aGFuLA0KPiBUaGlzIHdpbGwgYmUgZ29v
ZCBidXQgbWF5YmUgZXhwbGFpbiB0aGUgdXBncmFkZSBtZWFucyBhbHNvIHJlZnJlc2guIEJlY2F1
c2UgbXkgcG9vciB1bmRlcnN0YW5kaW5nIGluIEVuZ2xpc2ggaXMgdGhhdCB1cGdyYWRlIGlzIGFk
ZGluZyBhIG5ldyBsYXllciB0aGF0IHdhcyBub3QgYXZhaWxhYmxlIHRvIHRoZSBtZWRpYSByZWNl
aXZlciB3aGlsZSByZWZyZXNoIGlzIHRvIHJlc3RvcmUgZXhpc3RpbmcgbGF5ZXIgKGUuZy4gZGVj
b2RlciBzeW5jaHJvbml6YXRpb24gbG9zcykuDQo+IFJvbmkNCg0KQWgsIEkgc2VlLg0KDQpUaGUg
ZGVzaWduIGdvYWwgb2YgTFJSIHdhcyBmb3IgaXQgdG8gYmUgdXNlZCBmb3IgdXBncmFkZSwgbm90
IGZvciBzeW5jaHJvbml6YXRpb24gbG9zcywgdGhvdWdoIG9mIGNvdXJzZSBub3cgdGhhdCB5b3Ug
bWVudGlvbiBpdCwgaXQgY291bGQgY2VydGFpbmx5IGJlIHVzZWQgZm9yIHRoZSBsYXR0ZXIgYXMg
d2VsbC4gKEkuZS4gaXQgd2FzIGRlc2lnbmVkIHRvIGJlIGFuYWxvZ291cyB0byBGSVIsIG5vdCB0
byBQTEkuKQ0KDQpBcyB3aXRoIHRoZSBkaWZmZXJlbmNlIGJldHdlZW4gRklSIGFuZCBQTEksIHRo
ZSBjb25nZXN0aW9uIGNvbnNpZGVyYXRpb25zIGFyZSBzb21ld2hhdCBkaWZmZXJlbnQgYmV0d2Vl
biB1cGdyYWRlIGFuZCBzeW5jaHJvbml6YXRpb24gbG9zcy4gIERvIHlvdSB0aGluayBpdCdzIHdv
cnRoIGFkZHJlc3NpbmcgdGhlIHN5bmNocm9uaXphdGlvbiBsb3NzIGNhc2VzIGV4cGxpY2l0bHk/
DQoNCj4gDQo+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4gRnJvbTogSm9uYXRoYW4g
TGVubm94IFttYWlsdG86am9uYXRoYW5AdmlkeW8uY29tXQ0KPj4gU2VudDogVHVlc2RheSwgSnVu
ZSAxMywgMjAxNyA3OjAzIFBNDQo+PiBUbzogUm9uaSBFdmVuDQo+PiBDYzogUm9uaSBFdmVuOyBk
cmFmdC1pZXRmLWF2dGV4dC1scnIuYWxsQGlldGYub3JnOyBHZW5lcmFsIEFyZWEgUmV2aWV3IFRl
YW07DQo+PiBhdnRleHRAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj4+IFN1YmplY3Q6IFJlOiBH
ZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWF2dGV4dC1scnItMDUNCj4+IA0K
Pj4gSGksIFJvbmkg4oCUDQo+PiANCj4+IFlvdSBzZWVtIHRvIGJlIGFzc3VtaW5nIHRoYXQgYSBy
ZWZyZXNoIGFuZCBhbiB1cGdyYWRlIGFyZSB0d28gZGlmZmVyZW50DQo+PiBhY3Rpb25zLiAgVGhh
dOKAmXMgbm90IHRoZSBpbnRlbnRpb24g4oCUIGEgcmVmcmVzaCBpcyBhIGNoYXJhY3RlcmlzdGlj
IG9mIGEgc3RyZWFtIHRoYXQNCj4+IGFsbG93cyBhIGRlY29kZXIgdG8gdXBncmFkZS4NCj4+IA0K
Pj4gSeKAmWxsIHRyeSB0byBkcmFmdCBzb21lIHRleHQgdGhhdCBtYWtlcyBpdCBjbGVhciB0aGF0
IGl04oCZcyBwb3NzaWJsZSBlaXRoZXIgdG8NCj4+IGluZGVwZW5kZW50bHkgdXBncmFkZSB0ZW1w
b3JhbCBvciBzcGF0aWFsLCBvciBlbHNlIHVwZ3JhZGUgYm90aCBhdCBvbmNlLg0KPj4gDQo+Pj4g
T24gSnVuIDExLCAyMDE3LCBhdCA3OjIwIEFNLCBSb25pIEV2ZW4gPHJvbmkuZXZlbkBodWF3ZWku
Y29tPiB3cm90ZToNCj4+PiANCj4+PiBIaSBKb25hdGhhbiwNCj4+PiBJIGFzc3VtZSB0aGUgbmV3
IHRleHQgeW91IHByb3Bvc2UgaXMNCj4+PiANCj4+PiAiV2hlbiBDIGlzIDEsIFRUSUQgTVVTVCBO
T1QgYmUgbGVzcyB0aGFuIENUSUQsIGFuZCBUTElEIE1VU1QgTk9UIGJlDQo+Pj4gIGxlc3MgdGhh
biBDTElEOyBhdCBsZWFzdCBvbmUgb2YgVFRJRCBvciBUTElEIE1VU1QgYmUgZ3JlYXRlciB0aGFu
DQo+Pj4gIENUSUQgb3IgQ0xJRCByZXNwZWN0aXZlbHkuICBUaGF0IGlzIHRvIHNheSwgdGhlIHRh
cmdldCBsYXllciBpbmRleA0KPj4+ICA8VFRJRCwgVExJRD4gTVVTVCBiZSBhIGxheWVyIHVwZ3Jh
ZGUgZnJvbSB0aGUgY3VycmVudCBsYXllciBpbmRleA0KPj4+ICA8Q1RJRCwgQ0xJRD4uICBBIHNl
bmRlciBNQVkgcmVxdWVzdCBhbiB1cGdyYWRlIGluIGJvdGggdGVtcG9yYWwgYW5kDQo+Pj4gIHNw
YXRpYWwvcXVhbGl0eSBsYXllcnMgc2ltdWx0YW5lb3VzbHkuIg0KPj4+IA0KPj4+IEkgdGhpbmsg
dGhhdCB0aGlzIHRleHQgc3RpbGwgb25seSBpbXBsaWVzIHRoZSBiZWhhdmlvciwgYWxzbyB0aGUN
Cj4+PiBjdXJyZW50IHRleHQgdGFsa3MgYWJvdXQgdXBncmFkZSBidXQgSSBhc3N1bWUgaXQgaXMg
YWxzbyBmb3IgYSByZWZyZXNoDQo+Pj4gbm90IG9ubHkgdG8gdXBncmFkZQ0KPj4+IA0KPj4+IE1h
eWJlICIgQSBzZW5kZXIgTUFZIHJlcXVlc3QgYW4gdXBncmFkZSBvciByZWZyZXNoICBpbiBib3Ro
IHRlbXBvcmFsIGFuZA0KPj4+ICBzcGF0aWFsL3F1YWxpdHkgbGF5ZXJzIHNpbXVsdGFuZW91c2x5
IGJ5IGVpdGhlciBoYXZpbmcgQyA9MSBvciBieSBoYXZpbmcgYm90aA0KPj4gQ0xJRCBhbmQgQ1RJ
RCB3aXRoIGxvd2VyIHZhbHVlcyB0aGVuIFRUSUQgYW5kIFRMSUQuIElmIHRoZSBzZW5kZXIgd2Fu
dCB0bw0KPj4gdXBncmFkZSBvciByZWZyZXNoIG9ubHkgb25lIGxheWVyIHRoZW4gQyBNVVNUIGJl
IGVxdWFsIHRvIDEgYW5kIG9ubHkgdGhlIENUSUQNCj4+IG9yICB0aGUgQ0xJRCBvZiB0aGUgbGF5
ZXIgdG8gYmUgdXBncmFkZWQgb3IgcmVmcmVzaGVkIHNob3VsZCBiZSBsb3dlciB0aGFuIHRoZQ0K
Pj4gVFRJRCBvciBUTElEIHJlc3BlY3RpdmVseSAiDQo+Pj4gDQo+Pj4gDQo+Pj4gUm9uaQ0KPj4+
PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPj4+PiBGcm9tOiBKb25hdGhhbiBMZW5ub3gg
W21haWx0bzpqb25hdGhhbkB2aWR5by5jb21dDQo+Pj4+IFNlbnQ6INeZ15XXnSDXkyAwNyDXmdeV
16DXmSAyMDE3IDE4OjMwDQo+Pj4+IFRvOiBSb25pIEV2ZW4NCj4+Pj4gQ2M6IFJvbmkgRXZlbjsg
ZHJhZnQtaWV0Zi1hdnRleHQtbHJyLmFsbEBpZXRmLm9yZzsgR2VuZXJhbCBBcmVhDQo+Pj4+IFJl
dmlldyBUZWFtOyBhdnRleHRAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj4+Pj4gU3ViamVjdDog
UmU6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci0wNQ0K
Pj4+PiANCj4+Pj4gDQo+Pj4+PiBPbiBKdW4gNywgMjAxNywgYXQgMToxNSBBTSwgUm9uaSBFdmVu
IDxyb25pLmV2ZW5AaHVhd2VpLmNvbT4gd3JvdGU6DQo+Pj4+PiANCj4+Pj4+IEhpIEpvbmF0aGFu
LA0KPj4+Pj4gSSBkaWQgbm90IHNlZSB0aGUgdGV4dCB5b3UgYWRkZWQgeWV0IGFzIGEgcmVzcG9u
c2UgdG8gbXkgZmlyc3QNCj4+Pj4+IHF1ZXN0aW9uIFNvIHRvIGJldHRlciBjbGFyaWZ5IG15IHF1
ZXN0aW9uIC4gSWYgdGhlIEZDSSBoYXMgVFRJRD0wIGFuZCBUTElEPTINCj4+IC4NCj4+Pj4gZG9l
cyBpdCBtZWFuIHRoYXQgaXQgaXMgYSByZXF1ZXN0IHRvIHVwZGF0ZSBib3RoPw0KPj4+Pj4gVGhp
cyB3YXMgYWxzbyB0aGUgcmVhc29uIGZvciB0aGUgcXVlc3Rpb24gYWJvdXQgYm90aCBUVElEPTAg
YW5kDQo+Pj4+PiBUTElEPTAsDQo+Pj4+IHdoaWNoIGxheWVyIG5lZWQgdXBkYXRlIG9yIGlzIGl0
IGJvdGg/DQo+Pj4+PiBDYW4geW91IHNheSB0aGF0IHlvdSB3YW50IGp1c3QgdG8gdXBkYXRlIHRl
bXBvcmFsIG9yIHNwYXRpYWw/DQo+Pj4+IA0KPj4+PiBZZXMsIGlmIHRoZSBGQ0kgaGFzIFRUSUQ9
MCBhbmQgVExJRD0yLCBpdOKAmXMgYSByZXF1ZXN0IHRvIHVwZGF0ZSBib3RoDQo+Pj4+IGxheWVy
cyDigJQgb3IgbW9yZSBzcGVjaWZpY2FsbHksIHRvIG1ha2Ugc3VyZSB0aGF0IHlvdSBjYW4gc3Rh
cnQNCj4+Pj4gZGVjb2RpbmcgdGhlIHN1YnN0cmVhbSB3aXRoIFRUSUQ9MCBhbmQgVExJRD0yLiAo
Rm9yIG1vc3Qgc2NhbGFiaWxpdHkNCj4+Pj4gc3RydWN0dXJlcyB0aGlzIHdvdWxkIG1lYW4gdXBk
YXRpbmcgYm90aCwgYnV0IGV4b3RpYyBzdHJ1Y3R1cmVzIGFyZQ0KPj4+PiBwb3NzaWJsZS4pDQo+
Pj4+IA0KPj4+PiBJZiB5b3Ugd2FudCB0byBqdXN0IHVwZGF0ZSBvbmUgcGFydCBvZiB0aGUgc3Ry
ZWFtLCB0aGF04oCZcyB3aGF0IENUSUQNCj4+Pj4gYW5kIENMSUQgYXJlIGZvci4gIElmIHlvdSBz
ZW50IFRUSUQ9MCBhbmQgVExJRD0yLCBhY2NvbXBhbmllZCBieQ0KPj4+PiBDVElEPTAgYW5kIENM
SUQ9MCwgdGhhdCBtZWFucyB0aGF0IHlvdSBhbHJlYWR5IGhhdmUgVElEIDAsIGFuZCB5b3UNCj4+
Pj4ganVzdCB3YW50IHRvIGluY3JlYXNlIHRoZSBMSUQuDQo+Pj4+IA0KPj4+PiBUaGUgY3VycmVu
dCB0ZXh0IGlzIGF0DQo+Pj4+IGh0dHBzOi8vZ2l0aHViLmNvbS9qdWJlcnRpL2RyYXVnaHRzL3Ry
ZWUvbWFzdGVyL2xyciAsIGlmIHlvdSB3YW50IHRvDQo+Pj4+IHRha2UgYSBsb29rIGF0IHRoZSBs
YXRlc3QgcmV2aXNpb25zLCBvciBzdWdnZXN0IHRleHQgdGhhdCB5b3UgdGhpbmsgd291bGQgbWFr
ZQ0KPj4gaXQgY2xlYW5lci4NCj4+Pj4gDQo+Pj4+IA0KPj4+Pj4gUm9uaQ0KPj4+Pj4gDQo+Pj4+
Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+Pj4+PiBGcm9tOiBHZW4tYXJ0IFttYWls
dG86Z2VuLWFydC1ib3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YNCj4+Pj4+PiBKb25hdGhh
biBMZW5ub3gNCj4+Pj4+PiBTZW50OiDXmdeV150g15MgMDcg15nXldeg15kgMjAxNyAwMDozMA0K
Pj4+Pj4+IFRvOiBSb25pIEV2ZW4NCj4+Pj4+PiBDYzogZHJhZnQtaWV0Zi1hdnRleHQtbHJyLmFs
bEBpZXRmLm9yZzsgR2VuZXJhbCBBcmVhIFJldmlldyBUZWFtOw0KPj4+Pj4+IGF2dGV4dEBpZXRm
Lm9yZzsgaWV0ZkBpZXRmLm9yZw0KPj4+Pj4+IFN1YmplY3Q6IFJlOiBbR2VuLWFydF0gR2VuYXJ0
IGxhc3QgY2FsbCByZXZpZXcgb2YNCj4+Pj4+PiBkcmFmdC1pZXRmLWF2dGV4dC1scnItMDUNCj4+
Pj4+PiANCj4+Pj4+PiBIaSwgUm9uaSDigJQgdGhhbmtzIGZvciB5b3VyIHJldmlldy4gIFJlc3Bv
bnNlcyBpbmxpbmUuDQo+Pj4+Pj4gDQo+Pj4+Pj4+IE9uIEp1biAxLCAyMDE3LCBhdCAyOjUzIEFN
LCBSb25pIEV2ZW4gPHJvbi5ldmVuLnRsdkBnbWFpbC5jb20+DQo+PiB3cm90ZToNCj4+Pj4+Pj4g
DQo+Pj4+Pj4+IFJldmlld2VyOiBSb25pIEV2ZW4NCj4+Pj4+Pj4gUmV2aWV3IHJlc3VsdDogUmVh
ZHkgd2l0aCBJc3N1ZXMNCj4+Pj4+Pj4gDQo+Pj4+Pj4+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1B
UlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsDQo+Pj4+Pj4+IEFyZWEgUmV2
aWV3IFRlYW0gKEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nDQo+Pj4+
Pj4+IHByb2Nlc3NlZCBieSB0aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJl
YXQgdGhlc2UNCj4+Pj4+Pj4gY29tbWVudHMganVzdCBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwg
Y29tbWVudHMuDQo+Pj4+Pj4+IA0KPj4+Pj4+PiBGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNl
IHNlZSB0aGUgRkFRIGF0DQo+Pj4+Pj4+IA0KPj4+Pj4+PiA8aHR0cHM6Ly90cmFjLmlldGYub3Jn
L3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPi4NCj4+Pj4+Pj4gDQo+Pj4+Pj4+IERvY3VtZW50OiBk
cmFmdC1pZXRmLWF2dGV4dC1scnItPz8NCj4+Pj4+Pj4gUmV2aWV3ZXI6IFJvbmkgRXZlbg0KPj4+
Pj4+PiBSZXZpZXcgRGF0ZTogMjAxNy0wNS0zMQ0KPj4+Pj4+PiBJRVRGIExDIEVuZCBEYXRlOiAy
MDE3LTA2LTA4DQo+Pj4+Pj4+IElFU0cgVGVsZWNoYXQgZGF0ZTogTm90IHNjaGVkdWxlZCBmb3Ig
YSB0ZWxlY2hhdA0KPj4+Pj4+PiANCj4+Pj4+Pj4gU3VtbWFyeToNCj4+Pj4+Pj4gVGhlIGRvY3Vt
ZW50IGlzIHJlYWR5IHdpdGggaXNzdWVzIGZvciBhIHN0YW5kYXJkIHRyYWNrIFJGQyBNYWpvcg0K
Pj4+Pj4+PiBpc3N1ZXM6DQo+Pj4+Pj4+IA0KPj4+Pj4+PiBNaW5vciBpc3N1ZXM6DQo+Pj4+Pj4+
IA0KPj4+Pj4+PiAxLiBDYW4geW91IHNwZWNpZnkgYm90aCBUVElEIGFuZCBUTElEIGluIHRoZSBz
YW1lIEZDSS4NCj4+Pj4+PiANCj4+Pj4+PiBTeW50YWN0aWNhbGx5LCB0aGV5IG11c3QgYm90aCBv
Y2N1ci4NCj4+Pj4+PiANCj4+Pj4+PiBJZiB5b3UgbWVhbiBjYW4geW91IHJlcXVlc3QgYW4gdXBn
cmFkZSBpbiBib3RoIGF0IG9uY2UsIHllczsgSeKAmXZlDQo+Pj4+Pj4gYWRkZWQgdGV4dCB0byBj
bGFyaWZ5IHRoaXMuDQo+Pj4+Pj4gDQo+Pj4+Pj4+IDIuIFdoYXQgaXMgdGhlIG1lYW5pbmcgb2Yg
dmFsdWUgMCBmb3IgVFRJRCBhbmQgVExJRCAtIFRJRCBvciBMSUQNCj4+Pj4+Pj4gPTAgaW4gZnJh
bWUgbWFya2luZyBkcmFmdCBtZWFucyBiYXNlIGxheWVyIGlmIHRoZXJlIGlzIHNjYWxhYmlsaXR5
Lg0KPj4+Pj4+PiAgVGhpcyByZWxhdGVzIHRvIHRoZSBwcmV2aW91cyBxdWVzdGlvbi4NCj4+Pj4+
PiANCj4+Pj4+PiBJ4oCZbSBub3Qgc3VyZSBJIHVuZGVyc3RhbmQgdGhpcyBxdWVzdGlvbi4NCj4+
Pj4+PiANCj4+Pj4+PiBJ4oCZdmUgYWRkZWQgdGV4dCB0aGF0IGlmIEM9MSwgYXQgbGVhc3Qgb25l
IG9mIDxUVElELCBUTElEPiBNVVNUIGJlDQo+Pj4+Pj4gZ3JlYXRlciB0aGFuIDxDVElELCBDTElE
PiwgYW5kIGJvdGggTVVTVCBiZSBncmVhdGVyIHRoYW4gb3IgZXF1YWwNCj4+Pj4+PiB0byB0aGVp
ciBjb3VudGVycGFydCwgc28gdGhlIExSUiBpcyBhY3R1YWxseSByZXF1ZXN0aW5nIGEgbGF5ZXIg
dXBncmFkZS4NCj4+Pj4+PiBJcyB0aGF0IHdoYXQgeW91IHdlcmUgYXNraW5nIGFib3V0Pw0KPj4+
Pj4+IA0KPj4+Pj4+PiAzLiAgV2hhdCB3b3VsZCBhbiBGQ0kgd2l0aCBib3RoIFRUSUQgYW5kIFRM
SUQgZXF1YWwgMCBtZWFuLg0KPj4+Pj4+IA0KPj4+Pj4+IEl0IG1lYW5zIHlvdSB3YW50IGEgcmVm
cmVzaCBvZiB0aGUgYmFzZSB0ZW1wb3JhbC9zcGF0aWFsIGxheWVyLCBvbmx5Lg0KPj4+Pj4+IA0K
Pj4+Pj4+PiBOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4+Pj4+Pj4gDQo+Pj4+Pj4+IDEuIFNl
Y3Rpb24gMyAiYW4gUmVhbC1UaW1lIFRyYW5zcG9ydCBDb250cm9sIFByb3RvY29sIiBzaG91bGQg
YmUNCj4+Pj4+Pj4gImEgUmVhbOKApiIuDQo+Pj4+Pj4gDQo+Pj4+Pj4gQ29saW4gcG9pbnRlZCBv
dXQgdGhhdCBpdCBzaG91bGQgc2F5IOKAnGFuIFJUUCBDb250cm9sIFByb3RvY29s4oCdIGFueXdh
eS4NCj4+Pj4+PiANCj4+Pj4+Pj4gMi4gSW4gc2VjdGlvbiAzICIgW1JGQzUxMDRdKFNlY3Rpb24g
My41LjEpIiB0aGVyZSBpcyBhIGxpbmsgdG8NCj4+Pj4+Pj4gc2VjdGlvbg0KPj4+Pj4+PiAzLjUu
MSBidXQgaXQgZG9lcyBub3Qgd29yay4NCj4+Pj4+PiANCj4+Pj4+PiB4bWwycmZjIGRvZXNu4oCZ
dCBoYXZlIGFueSB3YXkgdG8gbGluayB0byBzZWN0aW9ucyBvZiBvdGhlcg0KPj4+Pj4+IGRvY3Vt
ZW50cywgc28gdGhlIOKAnChTZWN0aW9uIDMuNS4xKeKAnSBwYXJ0IGlzIGp1c3QgYSBjb21tZW50
Lg0KPj4+Pj4+IA0KPj4+Pj4+IEkgdGhpbmsgdGhlIGludGVybmV0LWRyYWZ0IHRvb2xpbmcgbWF5
IGhhdmUgdGhvdWdodCBJIHdhcyB0cnlpbmcgdG8NCj4+Pj4+PiBsaW5rIHRvIGEgbm9uLWV4aXN0
ZW50IHNlY3Rpb24gMy41LjEgb2YgdGhpcyBkb2N1bWVudCwgYnV0IHRoYXTigJlzDQo+Pj4+Pj4g
b3V0c2lkZQ0KPj4+PiBteSBjb250cm9sLg0KPj4+Pj4+IA0KPj4+Pj4+PiAzLiBJbiBzZWN0aW9u
IDMuMiAiKHNlZSBzZWN0aW9uIFNlY3Rpb24gMi4xKSIgc2VjdGlvbiBhcHBlYXJzIHR3aWNlLg0K
Pj4+Pj4+IA0KPj4+Pj4+IEZpeGVkLg0KPj4+Pj4+IF9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fDQo+Pj4+Pj4gR2VuLWFydCBtYWlsaW5nIGxpc3QNCj4+Pj4+
PiBHZW4tYXJ0QGlldGYub3JnDQo+Pj4+Pj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9nZW4tYXJ0DQo+Pj4gDQo+IA0KPiANCg0K


From nobody Tue Jun 13 16:02:40 2017
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9084C1293FF; Tue, 13 Jun 2017 16:02:32 -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=stpeter.im header.b=i6v+q1k6; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=LRiZ4i3H
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D0y0x0B6-TiA; Tue, 13 Jun 2017 16:02:30 -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 655E1126D85; Tue, 13 Jun 2017 16:02:30 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id D4DE020779; Tue, 13 Jun 2017 19:02:29 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute2.internal (MEProxy); Tue, 13 Jun 2017 19:02:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; 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=hYpJEJxhfVVoKbe4O9 FJfQCUGyOkOZtXIGVtx8SZlK4=; b=i6v+q1k6/3RkDdyRWdbVjaKk52EJbu9vBG S1ZCp9vy8bvDPu4MjFGYEU26QLhcBr+D88COd7cbIhLEGy8eOCbgvvDpsg1Zrv12 BvwwpPEJ0dTzMzCCBEbKBAvEFPgxg6XjEhcIGE6TKiS6miSiOLaVUxJ2R92vjybS 8N64tHDp9QZYYys6FzQ95yq7KL7g8m4BhAnaFoeTRXLaibxPAHiVHfhDdfBXdilY X3/igy/HJ/5hnF772sPxcfRkwB2fw0+smNnNI/JD4RaBbl52o2zVqIPH70/O+eCS Ul4X0BkVWkijuLoRnCmtr52dQz9NCYEwaK0FQaAWo1ZougjnJcwQ==
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=hYpJEJxhfVVoKbe4O9FJfQCUGyOkOZtXIGVtx8SZlK4=; b=LRiZ4i3H Y+t0L4SqQhDd5ky1syaUs/W1PWVGW74C+Ox/+xXemYFQxSyK2TXxsLDfy8YdvgBb 61HtmKw1RVV1cC25vkvpwGpg98D10LTA26xdS1VsVbLuhmCBIIZoz6PhTFo8CWnB QAN2i+Tv9K8EocfEQOplPwvtaoLKZwEXiupJvLeVt9lnq/prppaVan4O0vSoLw01 zaCvzCrTSjDSzjLF2ZA3n6Y4orSehQAkCaCWSBYhnOcQW0nRhUnOSu97w7LDFrtZ 4fmPaWjpE95PN0Vw+KoIajctdpRx12dyc55F8HDWedHobAFu3lDz6KenNyBRA427 rWLa3Ibjw641pA==
X-ME-Sender: <xms:BW9AWWidEV8z2QL9-UpbyCVO2T6QChCgygcM_lP7xDjNf86YEVV-1Q>
X-Sasl-enc: e0uQ2UhIxT09nbCV9NHeq4i1ouZ7RDKecz5XaNtGaO5W 1497394949
Received: from aither.local (unknown [76.25.4.24]) by mail.messagingengine.com (Postfix) with ESMTPA id 2ACD47E7A3; Tue, 13 Jun 2017 19:02:29 -0400 (EDT)
Subject: Re: [precis] Secdir last call review of draft-ietf-precis-7564bis-07
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>, secdir@ietf.org
References: <149736681626.7439.2555177998557552719@ietfa.amsl.com>
Cc: draft-ietf-precis-7564bis.all@ietf.org, ietf@ietf.org, precis@ietf.org
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <8ea90b99-3005-0afb-da93-63cd1abfc905@stpeter.im>
Date: Tue, 13 Jun 2017 17:02:28 -0600
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: <149736681626.7439.2555177998557552719@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4W5wZtg2Zi5j2DpOmU7HUa1nV-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: Tue, 13 Jun 2017 23:02:33 -0000

Hi Matt, thanks for the review - it's much appreciated.

Just so you know: through discussion of Daniel Migualt's secdir review
of 7700bis (we're progressing them all together this time!), I realized
that it might be help to add another example of visually confusing
characters to 7564bis, so I plan to mention CYRILLIC SMALL LETTER A
U+0430 vs. LATIN SMALL LETTER A U+0061 (which will be more familiar to
readers than the Cherokee characters already in the document).

Peter

On 6/13/17 9:13 AM, Matthew Miller wrote:
> Reviewer: Matthew Miller
> 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.
> 
> Document: draft-ietf-precis-7564bis-07
> Reviewer: Matthew A. Miller
> Review Date: 2017-06-13
> IETF LC End Date: 2017-06-13
> IESG Telechat date: 2017-07-06
> 
> Summary:
> 
> This document is ready to be published as a Standards Track document.
> 
> This document defines a framework application protocols use to
> prepare, compare, and enforce conformance of internationalized strings.
> It obsoletes RFC 7564.
> 
> This document is well written, and reinforces the security concerns
> discussed in Section 12 with references in the most relevant sections
> throughout the document.  While much of it essentially proclaims
> "be aware herein be dragons", the arguments for not proscribing more
> are well laid out.
> 
> Major Issues:  NONE
> 
> Minor Issues: NONE
> 
> Nits: NONE
> 
> 
> _______________________________________________
> precis mailing list
> precis@ietf.org
> https://www.ietf.org/mailman/listinfo/precis
> 


From nobody Tue Jun 13 18:02:40 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 49977129423; Tue, 13 Jun 2017 18:02: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] 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 RSYQUWUkPIAz; Tue, 13 Jun 2017 18:02:30 -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 19B061252BA; Tue, 13 Jun 2017 18:02:30 -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 1dKwhX-000MWa-2U; Tue, 13 Jun 2017 21:02:27 -0400
Date: Tue, 13 Jun 2017 21:02:22 -0400
From: John C Klensin <john-ietf@jck.com>
To: Peter Saint-Andre <stpeter@stpeter.im>, Matthew Miller <linuxwolf+ietf@outer-planes.net>, secdir@ietf.org
cc: draft-ietf-precis-7564bis.all@ietf.org, ietf@ietf.org, precis@ietf.org
Subject: Re: [precis] Secdir last call review of draft-ietf-precis-7564bis-07
Message-ID: <FEF9D2847A170FC48DE8EC5E@PSB>
In-Reply-To: <8ea90b99-3005-0afb-da93-63cd1abfc905@stpeter.im>
References: <149736681626.7439.2555177998557552719@ietfa.amsl.com> <8ea90b99-3005-0afb-da93-63cd1abfc905@stpeter.im>
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/P9lJW0bTPktXlnVnxYQgz9cDDiQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 01:02:32 -0000

--On Tuesday, June 13, 2017 17:02 -0600 Peter Saint-Andre
<stpeter@stpeter.im> wrote:

> Hi Matt, thanks for the review - it's much appreciated.
> 
> Just so you know: through discussion of Daniel Migualt's
> secdir review of 7700bis (we're progressing them all together
> this time!), I realized that it might be help to add another
> example of visually confusing characters to 7564bis, so I plan
> to mention CYRILLIC SMALL LETTER A U+0430 vs. LATIN SMALL
> LETTER A U+0061 (which will be more familiar to readers than
> the Cherokee characters already in the document).

Peter,

I don't want to throw the proverbial spanner in the works, but,
just as things changes just as the original PRECIS documents
were being published, I wonder if some other things that appear
to be in process now could do it to us again.  

For example, consider draft-freytag-troublesome-characters.
Despite having contributed to it and expecting to continue to do
so, I've got some misgivings about the document and proposed
registry as IETF work but, if it were to be adopted, it seems to
me that it would be useful for the PRECIS documents to
normatively reference it, especially for Identifier Class.   To
some extent, that draft is a remedy for some of the issues
raised in the long-stalled draft-klensin-idna-5892upd-unicode70,
but it doesn't make those issues, and the lack of
comprehensiveness of normalization, go away.

Probably less important, but it might be advantageous to
incorporate some of the "whatever decisions you make, people
will probably hold you accountable if there are problems" tone
of draft-klensin-idna-rfc5891bis into the PRECIS documents.  It
might even be that RFC 7940, possibly supplemented by
draft-freytag-lager-variant-rules, would be a better, or at
least useful alternative, way to present some or all of the
PEECIS rule sets than the current approach. 

On a somewhat different topic, the Greek, Latin,  and Cyrillic
scripts are so closely related that finding examples of pairs of
similar-looking characters is in the low-lying fruit category
because the similarities are not coincidences but the result of
derivation and extensive borrowing (something of the same thing
can be said for the Latin-Cherokee relationship, at least in
printed, rather than cureive, forms).   The examples that may be
more scary, just because there is no evolutionary theory to
predict were to look, would be things like the resemblances
among the Latin U+006F, the Lao U+0ED0, the Ethiopic U+12D0, the
New Tai Lue U+19D0, and of course the ASCII/European digit
U+0030 and probably many more, with the group perhaps best
described as "open circle graphemes" or something like that.

best,
    john


 


From nobody Tue Jun 13 21:00:13 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 5292B127337; Tue, 13 Jun 2017 21:00:05 -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: <gen-art@ietf.org>
Cc: ietf@ietf.org, bmwg@ietf.org, draft-ietf-bmwg-dcbench-terminology.all@ietf.org
Subject: Genart last call review of draft-ietf-bmwg-dcbench-terminology-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149741280522.7481.5692213354540706614@ietfa.amsl.com>
Date: Tue, 13 Jun 2017 21:00:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H8DllEopBsk4wVk0yzbx5rDgvyI>
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, 14 Jun 2017 04:00:05 -0000

Reviewer: Matthew Miller
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-dcbench-terminology-10
Reviewer: Matthew A. Miller
Review Date: 2017-06-13
IETF LC End Date: 2017-06-13
IESG Telechat date: N/A

Summary:

This document is almost ready; this document is on the path to its
goals set out in the abstract and introduction, but the execution
needs more work.

I think the authors would benefit from another round of proofreading
and submit a new revision.  Below are the most obvious or egregious
issues I have.

Major issues:

* In section 6.2 "Incast", it is unclear what is being measured,
and what the units (if any) for that measurement are.  Is it the
percentage of synchronization?  Is it the synchronous arrival time
(which presumably is measured as a delta over some magnitude of
seconds)? Is it the number of ingress and egress ports?  If it is
the number of ingress and egress ports, then it should define what
"egress" means for the purpose of this measurement

* In Section 8. "Security Considerations", what is the reason for
the "SHOULD" and "SHOULD NOT" in the last paragraph (discussing
special capabilities)?  At the least it seems safest for the
exceptions that rationalize the "SHOULD" and "SHOULD NOT" be
explicitly stated here, or changed to "MUST" and "MUST NOT" if
that rationale cannot be stated.

Minor issues:

* RFC 2119 should be a normative reference, as the reader MUST
understand what the terms as-written mean.

* RFC 5841 needs to be a listed reference; It is explicitly pointed
to in Sections 3.1. and 3.2. From the text is seems a Normative
reference is warranted but it at least needs to be documented in
References.

* RFC 2647 needs to be a listed reference. It is explicitly pointed
to in Section 7.1.; from the text it seems appropriate to be an
Informative reference.

* The definition in Section 1.2. of what the "Measurement Units"
subsections definitions format doesn't seem to be followed in
this document.  Specifically, the "Measurement Units" subsections
rarely ever mention a unit of measure; instead the unit of measure
is almost always specified as part of the "Definition" subsection.
It may be worth revisiting the name for the "Measurement Units"
subsections, or to move the unit of measure out of the
"Definitions" subsections and into the "Measurement Units"
subsections.

* In section 2.3., the use of MUST, MAY, and MUST NOT seems
a little contradictory.  The MUST for point 1 would seem to
already negate point 3, and prohibit point 2.  Would changing
that MUST to SHOULD be acceptable?

Nits/editorial comments:

* It would be helpful to include a reference to what "north-south"
and "east-west" mean, if possible.

* the acronyms DUT and SUT -- at the least -- need to be
expanded on first use, or in Section 1.1. "Terminology".

* In a number of subsections (notably under Section 4. and Section
6.), square brackets ("[" and "]") are used instead of parentheses
("(" and ")"), without any clear reason for the difference.  They
should be switched to parentheses.

* In Section 2.2., the word "for" or "at" should be removed in the
sentence "The change of behavior happens for at specific larger
packet sizes."

* Section 2.3., the phrase "the application commonly need to" should
be changed to "the application commonly needs to".

* In Section 5.2., there is a comma missing between "crystals" and
"or" in "The crystals or clock modules, usually have a specific".

* Also in Section 5.2., the term "devices under test" is used
instead of DUTs the rest of the document seems to use.

* Throughout Section 6.1., the acronyms "cos" and "dcsp" should be
expanded on first use.

* In Section 6.1.1, the definition of "Buffer Size" calls out using
some magnitude of bytes (B, KB, MB, GB), then the example denotes
"Mb" -- which commonly is used for megabits.  From the rest of the
definition, it seems this should be MB, but I have not calculated
if the numerical value preceding the unit needs to be revisited.

* In Section 6.2.1, the Stateful and Stateless terms both use the
phrase "such as for example", which is redundant.  Either "such as"
or "for example" is sufficient, and the other should be removed.

* The formatting in Section 10. "References" is very inconsistent.
There is odd indentation and inconsistent anchor usage.

* The affiliation and email address for Lucien Avramov is Google,
but the street address is mostly that for Cisco Systems, Inc.



From nobody Tue Jun 13 22:38:26 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 B5C571270A7; Tue, 13 Jun 2017 22:38:06 -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 3XY2CWP8nXaZ; Tue, 13 Jun 2017 22:38:03 -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 86CD51200F1; Tue, 13 Jun 2017 22:38:02 -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 DIL87550; Wed, 14 Jun 2017 05:38:00 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.301.0; Wed, 14 Jun 2017 06:37:59 +0100
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by NKGEML413-HUB.china.huawei.com (10.98.56.74) with Microsoft SMTP Server (TLS) id 14.3.235.1; Wed, 14 Jun 2017 13:37:56 +0800
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.49]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0301.000; Wed, 14 Jun 2017 13:37:53 +0800
From: Roni Even <roni.even@huawei.com>
To: Jonathan Lennox <jonathan@vidyo.com>, Roni Even <ron.even.tlv@gmail.com>
CC: "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>,  General Area Review Team <gen-art@ietf.org>, "avtext@ietf.org" <avtext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMAgAAtEkCAAQCzAIAFrKRwgAPKzwD//zmbgIAAXZUAgADu7NA=
Date: Wed, 14 Jun 2017 05:37:52 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7D0DE0@DGGEMM506-MBX.china.huawei.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com> <B9294064-4F4E-4FA1-A864-4F9790767B5C@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7D0641@DGGEMM506-MBX.china.huawei.com> <116D9947-414D-47EB-A0C7-8031999E5A89@vidyo.com> <01fe01d2e468$662f18e0$328d4aa0$@gmail.com> <D99B14A9-C6A4-456B-AEFA-8819B9EF6760@vidyo.com>
In-Reply-To: <D99B14A9-C6A4-456B-AEFA-8819B9EF6760@vidyo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.55]
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.0A020206.5940CBB9.004F, 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: e2a6e4c8b8332e96d28b21904c02d2cb
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CszwuZS5LegROF0N0cnVsHwO1EQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 05:38:07 -0000

SGkgSm9uYXRoYW4sDQpQcm9iYWJseSAgcGFydCBvZiBteSBjb21tZW50IHdhcyBiYXNlZCBvbiB0
aGUgZHJhZnQgbmFtZSAsIHRoZSBtZXNzYWdlIG5hbWUgYW5kIHRoZSBhYnN0cmFjdCAoYWxsIGFi
b3V0IHJlZnJlc2gpLiBJIGRpZCBub3Qgc2VlIGFueSB0ZXh0IGFib3V0IHRoZSBzYW1lIHVzYWdl
IGxpbWl0YXRpb24gb24gRklSIGZyb20gUkZDNTEwNA0KIlVzaW5nIHRoZSBGSVIgY29tbWFuZCB0
byByZWNvdmVyIGZyb20gZXJyb3JzIGlzIGV4cGxpY2l0bHkgIGRpc2FsbG93ZWQsIGFuZCBpbnN0
ZWFkIHRoZSBQTEkgbWVzc2FnZSBkZWZpbmVkIGluIEFWUEYgW1JGQzQ1ODVdICBzaG91bGQgYmUg
dXNlZC4gIFRoZSBQTEkgbWVzc2FnZSByZXBvcnRzIGxvc3QgcGljdHVyZXMgYW5kIGhhcyBiZWVu
ICBpbmNsdWRlZCBpbiBBVlBGIGZvciBwcmVjaXNlbHkgdGhhdCBwdXJwb3NlLiINCg0KSSBhbSBP
SyB3aXRoIHNpbWlsYXIgYXBwcm9hY2ggYXMgeW91IHN1Z2dlc3RlZCwgc28gZG8geW91IG1lYW4g
dGhhdCBQTEkgc2hvdWxkIGJlIHVzZWQgYWxzbyBpbiB0aGlzIGNhc2UgdG8gcmVjb3ZlciBmcm9t
IGVycm9ycy4gDQoNClByYWN0aWNhbGx5IGl0IHdpbGwgaW50ZXJlc3RpbmcgIHRvIHNlZSBpZiBh
cHBsaWNhdGlvbnMgYXJlIHVzaW5nIFBMSSBhbmQgbm90IEZJUiBmb3IgcGFja2V0IGxvc3MgY2Fz
ZXMgYW5kIHdoYXQgZW5jb2RlcnMgZG8gd2hlbiByZWNlaXZpbmcgUExJLiAoLToNCg0KQlRXOiBl
cnJvcnMgaXMgYSBnZW5lcmFsIHRlcm0sIEkgYXNzdW1lIHRoYXQgZm9yIEZJUiBpdCBtZWFudCBl
cnJvcnMgZHVlIHRvIHBhY2tldCBsb3NzIChjb25nZXN0aW9uKQ0KUm9uaQ0KDQo+IC0tLS0tT3Jp
Z2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEpvbmF0aGFuIExlbm5veCBbbWFpbHRvOmpvbmF0
aGFuQHZpZHlvLmNvbV0NCj4gU2VudDog15nXldedwqDXkyAxNCDXmdeV16DXmSAyMDE3IDAxOjQ5
DQo+IFRvOiBSb25pIEV2ZW4NCj4gQ2M6IFJvbmkgRXZlbjsgZHJhZnQtaWV0Zi1hdnRleHQtbHJy
LmFsbEBpZXRmLm9yZzsgR2VuZXJhbCBBcmVhIFJldmlldyBUZWFtOw0KPiBhdnRleHRAaWV0Zi5v
cmc7IGlldGZAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3
IG9mIGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci0wNQ0KPiANCj4gDQo+ID4gT24gSnVuIDEzLCAyMDE3
LCBhdCAxOjEzIFBNLCBSb25pIEV2ZW4gPHJvbi5ldmVuLnRsdkBnbWFpbC5jb20+IHdyb3RlOg0K
PiA+DQo+ID4gSGkgSm9uYXRoYW4sDQo+ID4gVGhpcyB3aWxsIGJlIGdvb2QgYnV0IG1heWJlIGV4
cGxhaW4gdGhlIHVwZ3JhZGUgbWVhbnMgYWxzbyByZWZyZXNoLg0KPiBCZWNhdXNlIG15IHBvb3Ig
dW5kZXJzdGFuZGluZyBpbiBFbmdsaXNoIGlzIHRoYXQgdXBncmFkZSBpcyBhZGRpbmcgYSBuZXcN
Cj4gbGF5ZXIgdGhhdCB3YXMgbm90IGF2YWlsYWJsZSB0byB0aGUgbWVkaWEgcmVjZWl2ZXIgd2hp
bGUgcmVmcmVzaCBpcyB0byByZXN0b3JlDQo+IGV4aXN0aW5nIGxheWVyIChlLmcuIGRlY29kZXIg
c3luY2hyb25pemF0aW9uIGxvc3MpLg0KPiA+IFJvbmkNCj4gDQo+IEFoLCBJIHNlZS4NCj4gDQo+
IFRoZSBkZXNpZ24gZ29hbCBvZiBMUlIgd2FzIGZvciBpdCB0byBiZSB1c2VkIGZvciB1cGdyYWRl
LCBub3QgZm9yDQo+IHN5bmNocm9uaXphdGlvbiBsb3NzLCB0aG91Z2ggb2YgY291cnNlIG5vdyB0
aGF0IHlvdSBtZW50aW9uIGl0LCBpdCBjb3VsZA0KPiBjZXJ0YWlubHkgYmUgdXNlZCBmb3IgdGhl
IGxhdHRlciBhcyB3ZWxsLiAoSS5lLiBpdCB3YXMgZGVzaWduZWQgdG8gYmUgYW5hbG9nb3VzDQo+
IHRvIEZJUiwgbm90IHRvIFBMSS4pDQo+IA0KPiBBcyB3aXRoIHRoZSBkaWZmZXJlbmNlIGJldHdl
ZW4gRklSIGFuZCBQTEksIHRoZSBjb25nZXN0aW9uIGNvbnNpZGVyYXRpb25zDQo+IGFyZSBzb21l
d2hhdCBkaWZmZXJlbnQgYmV0d2VlbiB1cGdyYWRlIGFuZCBzeW5jaHJvbml6YXRpb24gbG9zcy4g
IERvIHlvdQ0KPiB0aGluayBpdCdzIHdvcnRoIGFkZHJlc3NpbmcgdGhlIHN5bmNocm9uaXphdGlv
biBsb3NzIGNhc2VzIGV4cGxpY2l0bHk/DQo+IA0KPiA+DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVz
c2FnZS0tLS0tDQo+ID4+IEZyb206IEpvbmF0aGFuIExlbm5veCBbbWFpbHRvOmpvbmF0aGFuQHZp
ZHlvLmNvbV0NCj4gPj4gU2VudDogVHVlc2RheSwgSnVuZSAxMywgMjAxNyA3OjAzIFBNDQo+ID4+
IFRvOiBSb25pIEV2ZW4NCj4gPj4gQ2M6IFJvbmkgRXZlbjsgZHJhZnQtaWV0Zi1hdnRleHQtbHJy
LmFsbEBpZXRmLm9yZzsgR2VuZXJhbCBBcmVhDQo+ID4+IFJldmlldyBUZWFtOyBhdnRleHRAaWV0
Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj4gPj4gU3ViamVjdDogUmU6IEdlbmFydCBsYXN0IGNhbGwg
cmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci0wNQ0KPiA+Pg0KPiA+PiBIaSwgUm9uaSDi
gJQNCj4gPj4NCj4gPj4gWW91IHNlZW0gdG8gYmUgYXNzdW1pbmcgdGhhdCBhIHJlZnJlc2ggYW5k
IGFuIHVwZ3JhZGUgYXJlIHR3bw0KPiA+PiBkaWZmZXJlbnQgYWN0aW9ucy4gIFRoYXTigJlzIG5v
dCB0aGUgaW50ZW50aW9uIOKAlCBhIHJlZnJlc2ggaXMgYQ0KPiA+PiBjaGFyYWN0ZXJpc3RpYyBv
ZiBhIHN0cmVhbSB0aGF0IGFsbG93cyBhIGRlY29kZXIgdG8gdXBncmFkZS4NCj4gPj4NCj4gPj4g
SeKAmWxsIHRyeSB0byBkcmFmdCBzb21lIHRleHQgdGhhdCBtYWtlcyBpdCBjbGVhciB0aGF0IGl0
4oCZcyBwb3NzaWJsZQ0KPiA+PiBlaXRoZXIgdG8gaW5kZXBlbmRlbnRseSB1cGdyYWRlIHRlbXBv
cmFsIG9yIHNwYXRpYWwsIG9yIGVsc2UgdXBncmFkZSBib3RoDQo+IGF0IG9uY2UuDQo+ID4+DQo+
ID4+PiBPbiBKdW4gMTEsIDIwMTcsIGF0IDc6MjAgQU0sIFJvbmkgRXZlbiA8cm9uaS5ldmVuQGh1
YXdlaS5jb20+IHdyb3RlOg0KPiA+Pj4NCj4gPj4+IEhpIEpvbmF0aGFuLA0KPiA+Pj4gSSBhc3N1
bWUgdGhlIG5ldyB0ZXh0IHlvdSBwcm9wb3NlIGlzDQo+ID4+Pg0KPiA+Pj4gIldoZW4gQyBpcyAx
LCBUVElEIE1VU1QgTk9UIGJlIGxlc3MgdGhhbiBDVElELCBhbmQgVExJRCBNVVNUIE5PVCBiZQ0K
PiA+Pj4gbGVzcyB0aGFuIENMSUQ7IGF0IGxlYXN0IG9uZSBvZiBUVElEIG9yIFRMSUQgTVVTVCBi
ZSBncmVhdGVyIHRoYW4NCj4gPj4+IENUSUQgb3IgQ0xJRCByZXNwZWN0aXZlbHkuICBUaGF0IGlz
IHRvIHNheSwgdGhlIHRhcmdldCBsYXllciBpbmRleA0KPiA+Pj4gPFRUSUQsIFRMSUQ+IE1VU1Qg
YmUgYSBsYXllciB1cGdyYWRlIGZyb20gdGhlIGN1cnJlbnQgbGF5ZXIgaW5kZXgNCj4gPj4+IDxD
VElELCBDTElEPi4gIEEgc2VuZGVyIE1BWSByZXF1ZXN0IGFuIHVwZ3JhZGUgaW4gYm90aCB0ZW1w
b3JhbCBhbmQNCj4gPj4+IHNwYXRpYWwvcXVhbGl0eSBsYXllcnMgc2ltdWx0YW5lb3VzbHkuIg0K
PiA+Pj4NCj4gPj4+IEkgdGhpbmsgdGhhdCB0aGlzIHRleHQgc3RpbGwgb25seSBpbXBsaWVzIHRo
ZSBiZWhhdmlvciwgYWxzbyB0aGUNCj4gPj4+IGN1cnJlbnQgdGV4dCB0YWxrcyBhYm91dCB1cGdy
YWRlIGJ1dCBJIGFzc3VtZSBpdCBpcyBhbHNvIGZvciBhDQo+ID4+PiByZWZyZXNoIG5vdCBvbmx5
IHRvIHVwZ3JhZGUNCj4gPj4+DQo+ID4+PiBNYXliZSAiIEEgc2VuZGVyIE1BWSByZXF1ZXN0IGFu
IHVwZ3JhZGUgb3IgcmVmcmVzaCAgaW4gYm90aCB0ZW1wb3JhbA0KPiA+Pj4gYW5kICBzcGF0aWFs
L3F1YWxpdHkgbGF5ZXJzIHNpbXVsdGFuZW91c2x5IGJ5IGVpdGhlciBoYXZpbmcgQyA9MSBvcg0K
PiA+Pj4gYnkgaGF2aW5nIGJvdGgNCj4gPj4gQ0xJRCBhbmQgQ1RJRCB3aXRoIGxvd2VyIHZhbHVl
cyB0aGVuIFRUSUQgYW5kIFRMSUQuIElmIHRoZSBzZW5kZXINCj4gPj4gd2FudCB0byB1cGdyYWRl
IG9yIHJlZnJlc2ggb25seSBvbmUgbGF5ZXIgdGhlbiBDIE1VU1QgYmUgZXF1YWwgdG8gMQ0KPiA+
PiBhbmQgb25seSB0aGUgQ1RJRCBvciAgdGhlIENMSUQgb2YgdGhlIGxheWVyIHRvIGJlIHVwZ3Jh
ZGVkIG9yDQo+ID4+IHJlZnJlc2hlZCBzaG91bGQgYmUgbG93ZXIgdGhhbiB0aGUgVFRJRCBvciBU
TElEIHJlc3BlY3RpdmVseSAiDQo+ID4+Pg0KPiA+Pj4NCj4gPj4+IFJvbmkNCj4gPj4+PiAtLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+Pj4+IEZyb206IEpvbmF0aGFuIExlbm5veCBbbWFp
bHRvOmpvbmF0aGFuQHZpZHlvLmNvbV0NCj4gPj4+PiBTZW50OiDXmdeV150g15MgMDcg15nXldeg
15kgMjAxNyAxODozMA0KPiA+Pj4+IFRvOiBSb25pIEV2ZW4NCj4gPj4+PiBDYzogUm9uaSBFdmVu
OyBkcmFmdC1pZXRmLWF2dGV4dC1scnIuYWxsQGlldGYub3JnOyBHZW5lcmFsIEFyZWENCj4gPj4+
PiBSZXZpZXcgVGVhbTsgYXZ0ZXh0QGlldGYub3JnOyBpZXRmQGlldGYub3JnDQo+ID4+Pj4gU3Vi
amVjdDogUmU6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0ZXh0LWxy
ci0wNQ0KPiA+Pj4+DQo+ID4+Pj4NCj4gPj4+Pj4gT24gSnVuIDcsIDIwMTcsIGF0IDE6MTUgQU0s
IFJvbmkgRXZlbiA8cm9uaS5ldmVuQGh1YXdlaS5jb20+DQo+IHdyb3RlOg0KPiA+Pj4+Pg0KPiA+
Pj4+PiBIaSBKb25hdGhhbiwNCj4gPj4+Pj4gSSBkaWQgbm90IHNlZSB0aGUgdGV4dCB5b3UgYWRk
ZWQgeWV0IGFzIGEgcmVzcG9uc2UgdG8gbXkgZmlyc3QNCj4gPj4+Pj4gcXVlc3Rpb24gU28gdG8g
YmV0dGVyIGNsYXJpZnkgbXkgcXVlc3Rpb24gLiBJZiB0aGUgRkNJIGhhcyBUVElEPTANCj4gPj4+
Pj4gYW5kIFRMSUQ9Mg0KPiA+PiAuDQo+ID4+Pj4gZG9lcyBpdCBtZWFuIHRoYXQgaXQgaXMgYSBy
ZXF1ZXN0IHRvIHVwZGF0ZSBib3RoPw0KPiA+Pj4+PiBUaGlzIHdhcyBhbHNvIHRoZSByZWFzb24g
Zm9yIHRoZSBxdWVzdGlvbiBhYm91dCBib3RoIFRUSUQ9MCBhbmQNCj4gPj4+Pj4gVExJRD0wLA0K
PiA+Pj4+IHdoaWNoIGxheWVyIG5lZWQgdXBkYXRlIG9yIGlzIGl0IGJvdGg/DQo+ID4+Pj4+IENh
biB5b3Ugc2F5IHRoYXQgeW91IHdhbnQganVzdCB0byB1cGRhdGUgdGVtcG9yYWwgb3Igc3BhdGlh
bD8NCj4gPj4+Pg0KPiA+Pj4+IFllcywgaWYgdGhlIEZDSSBoYXMgVFRJRD0wIGFuZCBUTElEPTIs
IGl04oCZcyBhIHJlcXVlc3QgdG8gdXBkYXRlDQo+ID4+Pj4gYm90aCBsYXllcnMg4oCUIG9yIG1v
cmUgc3BlY2lmaWNhbGx5LCB0byBtYWtlIHN1cmUgdGhhdCB5b3UgY2FuIHN0YXJ0DQo+ID4+Pj4g
ZGVjb2RpbmcgdGhlIHN1YnN0cmVhbSB3aXRoIFRUSUQ9MCBhbmQgVExJRD0yLiAoRm9yIG1vc3QN
Cj4gPj4+PiBzY2FsYWJpbGl0eSBzdHJ1Y3R1cmVzIHRoaXMgd291bGQgbWVhbiB1cGRhdGluZyBi
b3RoLCBidXQgZXhvdGljDQo+ID4+Pj4gc3RydWN0dXJlcyBhcmUNCj4gPj4+PiBwb3NzaWJsZS4p
DQo+ID4+Pj4NCj4gPj4+PiBJZiB5b3Ugd2FudCB0byBqdXN0IHVwZGF0ZSBvbmUgcGFydCBvZiB0
aGUgc3RyZWFtLCB0aGF04oCZcyB3aGF0IENUSUQNCj4gPj4+PiBhbmQgQ0xJRCBhcmUgZm9yLiAg
SWYgeW91IHNlbnQgVFRJRD0wIGFuZCBUTElEPTIsIGFjY29tcGFuaWVkIGJ5DQo+ID4+Pj4gQ1RJ
RD0wIGFuZCBDTElEPTAsIHRoYXQgbWVhbnMgdGhhdCB5b3UgYWxyZWFkeSBoYXZlIFRJRCAwLCBh
bmQgeW91DQo+ID4+Pj4ganVzdCB3YW50IHRvIGluY3JlYXNlIHRoZSBMSUQuDQo+ID4+Pj4NCj4g
Pj4+PiBUaGUgY3VycmVudCB0ZXh0IGlzIGF0DQo+ID4+Pj4gaHR0cHM6Ly9naXRodWIuY29tL2p1
YmVydGkvZHJhdWdodHMvdHJlZS9tYXN0ZXIvbHJyICwgaWYgeW91IHdhbnQNCj4gPj4+PiB0byB0
YWtlIGEgbG9vayBhdCB0aGUgbGF0ZXN0IHJldmlzaW9ucywgb3Igc3VnZ2VzdCB0ZXh0IHRoYXQg
eW91DQo+ID4+Pj4gdGhpbmsgd291bGQgbWFrZQ0KPiA+PiBpdCBjbGVhbmVyLg0KPiA+Pj4+DQo+
ID4+Pj4NCj4gPj4+Pj4gUm9uaQ0KPiA+Pj4+Pg0KPiA+Pj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gPj4+Pj4+IEZyb206IEdlbi1hcnQgW21haWx0bzpnZW4tYXJ0LWJvdW5jZXNA
aWV0Zi5vcmddIE9uIEJlaGFsZiBPZg0KPiA+Pj4+Pj4gSm9uYXRoYW4gTGVubm94DQo+ID4+Pj4+
PiBTZW50OiDXmdeV150g15MgMDcg15nXldeg15kgMjAxNyAwMDozMA0KPiA+Pj4+Pj4gVG86IFJv
bmkgRXZlbg0KPiA+Pj4+Pj4gQ2M6IGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci5hbGxAaWV0Zi5vcmc7
IEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbTsNCj4gPj4+Pj4+IGF2dGV4dEBpZXRmLm9yZzsgaWV0
ZkBpZXRmLm9yZw0KPiA+Pj4+Pj4gU3ViamVjdDogUmU6IFtHZW4tYXJ0XSBHZW5hcnQgbGFzdCBj
YWxsIHJldmlldyBvZg0KPiA+Pj4+Pj4gZHJhZnQtaWV0Zi1hdnRleHQtbHJyLTA1DQo+ID4+Pj4+
Pg0KPiA+Pj4+Pj4gSGksIFJvbmkg4oCUIHRoYW5rcyBmb3IgeW91ciByZXZpZXcuICBSZXNwb25z
ZXMgaW5saW5lLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+PiBPbiBKdW4gMSwgMjAxNywgYXQgMjo1MyBB
TSwgUm9uaSBFdmVuIDxyb24uZXZlbi50bHZAZ21haWwuY29tPg0KPiA+PiB3cm90ZToNCj4gPj4+
Pj4+Pg0KPiA+Pj4+Pj4+IFJldmlld2VyOiBSb25pIEV2ZW4NCj4gPj4+Pj4+PiBSZXZpZXcgcmVz
dWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4gSSBhbSB0aGUgYXNz
aWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVyYWwNCj4gPj4+
Pj4+PiBBcmVhIFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50
cyBiZWluZw0KPiA+Pj4+Pj4+IHByb2Nlc3NlZCBieSB0aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hh
aXIuICBQbGVhc2UgdHJlYXQgdGhlc2UNCj4gPj4+Pj4+PiBjb21tZW50cyBqdXN0IGxpa2UgYW55
IG90aGVyIGxhc3QgY2FsbCBjb21tZW50cy4NCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IEZvciBtb3Jl
IGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+
IDxodHRwczovL3RyYWMuaWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KPiA+Pj4+
Pj4+DQo+ID4+Pj4+Pj4gRG9jdW1lbnQ6IGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci0/Pw0KPiA+Pj4+
Pj4+IFJldmlld2VyOiBSb25pIEV2ZW4NCj4gPj4+Pj4+PiBSZXZpZXcgRGF0ZTogMjAxNy0wNS0z
MQ0KPiA+Pj4+Pj4+IElFVEYgTEMgRW5kIERhdGU6IDIwMTctMDYtMDgNCj4gPj4+Pj4+PiBJRVNH
IFRlbGVjaGF0IGRhdGU6IE5vdCBzY2hlZHVsZWQgZm9yIGEgdGVsZWNoYXQNCj4gPj4+Pj4+Pg0K
PiA+Pj4+Pj4+IFN1bW1hcnk6DQo+ID4+Pj4+Pj4gVGhlIGRvY3VtZW50IGlzIHJlYWR5IHdpdGgg
aXNzdWVzIGZvciBhIHN0YW5kYXJkIHRyYWNrIFJGQyBNYWpvcg0KPiA+Pj4+Pj4+IGlzc3VlczoN
Cj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+IE1pbm9yIGlzc3VlczoNCj4gPj4+Pj4+Pg0KPiA+Pj4+Pj4+
IDEuIENhbiB5b3Ugc3BlY2lmeSBib3RoIFRUSUQgYW5kIFRMSUQgaW4gdGhlIHNhbWUgRkNJLg0K
PiA+Pj4+Pj4NCj4gPj4+Pj4+IFN5bnRhY3RpY2FsbHksIHRoZXkgbXVzdCBib3RoIG9jY3VyLg0K
PiA+Pj4+Pj4NCj4gPj4+Pj4+IElmIHlvdSBtZWFuIGNhbiB5b3UgcmVxdWVzdCBhbiB1cGdyYWRl
IGluIGJvdGggYXQgb25jZSwgeWVzOyBJ4oCZdmUNCj4gPj4+Pj4+IGFkZGVkIHRleHQgdG8gY2xh
cmlmeSB0aGlzLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+PiAyLiBXaGF0IGlzIHRoZSBtZWFuaW5nIG9m
IHZhbHVlIDAgZm9yIFRUSUQgYW5kIFRMSUQgLSBUSUQgb3IgTElEDQo+ID4+Pj4+Pj4gPTAgaW4g
ZnJhbWUgbWFya2luZyBkcmFmdCBtZWFucyBiYXNlIGxheWVyIGlmIHRoZXJlIGlzIHNjYWxhYmls
aXR5Lg0KPiA+Pj4+Pj4+ICBUaGlzIHJlbGF0ZXMgdG8gdGhlIHByZXZpb3VzIHF1ZXN0aW9uLg0K
PiA+Pj4+Pj4NCj4gPj4+Pj4+IEnigJltIG5vdCBzdXJlIEkgdW5kZXJzdGFuZCB0aGlzIHF1ZXN0
aW9uLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IEnigJl2ZSBhZGRlZCB0ZXh0IHRoYXQgaWYgQz0xLCBh
dCBsZWFzdCBvbmUgb2YgPFRUSUQsIFRMSUQ+IE1VU1QgYmUNCj4gPj4+Pj4+IGdyZWF0ZXIgdGhh
biA8Q1RJRCwgQ0xJRD4sIGFuZCBib3RoIE1VU1QgYmUgZ3JlYXRlciB0aGFuIG9yIGVxdWFsDQo+
ID4+Pj4+PiB0byB0aGVpciBjb3VudGVycGFydCwgc28gdGhlIExSUiBpcyBhY3R1YWxseSByZXF1
ZXN0aW5nIGEgbGF5ZXINCj4gdXBncmFkZS4NCj4gPj4+Pj4+IElzIHRoYXQgd2hhdCB5b3Ugd2Vy
ZSBhc2tpbmcgYWJvdXQ/DQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4+IDMuICBXaGF0IHdvdWxkIGFuIEZD
SSB3aXRoIGJvdGggVFRJRCBhbmQgVExJRCBlcXVhbCAwIG1lYW4uDQo+ID4+Pj4+Pg0KPiA+Pj4+
Pj4gSXQgbWVhbnMgeW91IHdhbnQgYSByZWZyZXNoIG9mIHRoZSBiYXNlIHRlbXBvcmFsL3NwYXRp
YWwgbGF5ZXIsIG9ubHkuDQo+ID4+Pj4+Pg0KPiA+Pj4+Pj4+IE5pdHMvZWRpdG9yaWFsIGNvbW1l
bnRzOg0KPiA+Pj4+Pj4+DQo+ID4+Pj4+Pj4gMS4gU2VjdGlvbiAzICJhbiBSZWFsLVRpbWUgVHJh
bnNwb3J0IENvbnRyb2wgUHJvdG9jb2wiIHNob3VsZCBiZQ0KPiA+Pj4+Pj4+ICJhIFJlYWzigKYi
Lg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IENvbGluIHBvaW50ZWQgb3V0IHRoYXQgaXQgc2hvdWxkIHNh
eSDigJxhbiBSVFAgQ29udHJvbCBQcm90b2NvbOKAnQ0KPiBhbnl3YXkuDQo+ID4+Pj4+Pg0KPiA+
Pj4+Pj4+IDIuIEluIHNlY3Rpb24gMyAiIFtSRkM1MTA0XShTZWN0aW9uIDMuNS4xKSIgdGhlcmUg
aXMgYSBsaW5rIHRvDQo+ID4+Pj4+Pj4gc2VjdGlvbg0KPiA+Pj4+Pj4+IDMuNS4xIGJ1dCBpdCBk
b2VzIG5vdCB3b3JrLg0KPiA+Pj4+Pj4NCj4gPj4+Pj4+IHhtbDJyZmMgZG9lc27igJl0IGhhdmUg
YW55IHdheSB0byBsaW5rIHRvIHNlY3Rpb25zIG9mIG90aGVyDQo+ID4+Pj4+PiBkb2N1bWVudHMs
IHNvIHRoZSDigJwoU2VjdGlvbiAzLjUuMSnigJ0gcGFydCBpcyBqdXN0IGEgY29tbWVudC4NCj4g
Pj4+Pj4+DQo+ID4+Pj4+PiBJIHRoaW5rIHRoZSBpbnRlcm5ldC1kcmFmdCB0b29saW5nIG1heSBo
YXZlIHRob3VnaHQgSSB3YXMgdHJ5aW5nDQo+ID4+Pj4+PiB0byBsaW5rIHRvIGEgbm9uLWV4aXN0
ZW50IHNlY3Rpb24gMy41LjEgb2YgdGhpcyBkb2N1bWVudCwgYnV0DQo+ID4+Pj4+PiB0aGF04oCZ
cyBvdXRzaWRlDQo+ID4+Pj4gbXkgY29udHJvbC4NCj4gPj4+Pj4+DQo+ID4+Pj4+Pj4gMy4gSW4g
c2VjdGlvbiAzLjIgIihzZWUgc2VjdGlvbiBTZWN0aW9uIDIuMSkiIHNlY3Rpb24gYXBwZWFycyB0
d2ljZS4NCj4gPj4+Pj4+DQo+ID4+Pj4+PiBGaXhlZC4NCj4gPj4+Pj4+IF9fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+ID4+Pj4+PiBHZW4tYXJ0IG1haWxp
bmcgbGlzdA0KPiA+Pj4+Pj4gR2VuLWFydEBpZXRmLm9yZw0KPiA+Pj4+Pj4gaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9nZW4tYXJ0DQo+ID4+Pg0KPiA+DQo+ID4NCg0K


From nobody Wed Jun 14 08:41:56 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 EC7B812EC4C for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 08:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level: 
X-Spam-Status: No, score=-7.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_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 YWt-lwG_cAyg for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 08:41:52 -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 E1184129C55 for <ietf@ietf.org>; Wed, 14 Jun 2017 08:41:49 -0700 (PDT)
Received: from [192.168.3.127] (unknown [95.82.146.6]) by mail.nic.cz (Postfix) with ESMTPSA id 56A496012D for <ietf@ietf.org>; Wed, 14 Jun 2017 17:41:47 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1497454907; bh=Fw6bR+2BzGdOjqHg/JpkfxA5P7W1lmbhCR86hCq07PU=; h=To:From:Date; b=GNFfHerkiud6JAgNFzvqqd2cE4fE+aJ59u1LeZi3bX60yQvkjgLMiE1BEQvePDnr5 W5ooSUMQmJc4GHslgCWfzvNgCepDTtwg8Ocmr1k9+Bvim91jTig6deW98t4SzXJHcm CnKvS08UpHHOyXoToQnuKYRSXaAgxI0KDEh8QjNs=
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu>
From: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>
Organization: CZ.NIC
Message-ID: <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz>
Date: Wed, 14 Jun 2017 17:41:36 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu>
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/yynMIOw4w97V-xSsf8i0-OdlGEo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 15:41:55 -0000

On 14.6.2017 00:03, Joe Touch wrote:
> Hi, all,
> 
> ...
>>   Title           : The Harmful Consequences of
>>         Postel's Maxim
>> https://tools.ietf.org/html/draft-thomson-postel-was-wrong-01

Before I dive into details, let me state I support this documents in its
current form.


> I completely agree with John Klensin that a test suite defines the
> protocol standard (warts and all).
> 
> However, I disagree with the characterization of the Postel Principle in
> this doc, and strongly disagree with one of its key conclusions ("fail
> noisily in response to...undefined inputs"). Failing in response to bad
> inputs is fine, but "undefined" needs to be treated agnostically.
> 
> IMO, the Postel Principle is an admission of that sort of agnosticism -
> if you don't know how the other end will react, act conservatively. If
> you don't know what the other end intends, react conservatively. Both
> are conservative actions - in one sense, you try not to trigger
> unexpected behavior (when you send), and in another you try not to
> create that unexpected behavior (when you receive).
> 
> That's the very definition of how unused bits need to be handled. Send
> conservatively (use the known default value), but allow any value upon
> receipt.

This very much depends on the the original specification.

If the spec says "send zeros, ignore on receipt" and marks this clearly
as an extension mechanism then it might be okay as long as the extension
mechanism is well defined.


On the other hand, accepting values/features/requests which are not
specified is asking for trouble, especially in long-term. Look at DNS
protocol, it is a mess.

- CNAME at apex? Some resolvers will accept it, some will not.
- Differing TTLs inside RRset during zone transfer? Some servers will
accept it and some not.
...


To sum it up, decision what is acceptable and what is unacceptable
should be in protocol developer's hands. Implementations should reject
and non-specified messages/things unless protocol explicitly says
otherwise. No more "ignore this for interoperability"!


With my DNS-software-develoepr hat on, I very clearly see value of
The New Design Principle in section 4.

Set it to stone! :-)


> The principle does not setup the feedback cycle in Sec 2; a bug is a bug
> and should be fixed, and accommodating alternate behaviors is the very
> definition of "be generous in what you receive". "Being conservative in
> what you send" doesn't mean "never send anything new" - it means do so
> only deliberately.
> 
> -----
> Failing noisily is, even when appropriate (e.g., on a known incorrect
> input), an invitation for a DOS attack.
> 
> That behavior is nearly as bad as interpreting unexpected (but not
> prohibited) behavior as an attack. Neither one serves a useful purpose
> other than overreaction, which provides increased leverage for a real
> DOS attack.

Sorry but I cannot agree. This very much depens on properies of "hard
fail" messages.

If "error messages" are short enough they will not create significantly
more problems than mere flood of random packets (which can be used for
DoS no matter what we). In fact, short predictible error message is even
better because it gives you ability to filter it somewhere.

Also, passing underspecified messages further in the pipeline is causing
problems on its own. (Imagine cases when proxy passes
malformed/underspecified messages to the backend because it can.)


So again, I really like this document. Thank you!

-- 
Petr Špaček  @  CZ.NIC


From nobody Wed Jun 14 12:26:13 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 2660312943D; Wed, 14 Jun 2017 12:26:06 -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: ietf@ietf.org, dmm@ietf.org, draft-ietf-dmm-mag-multihoming.all@ietf.org
Subject: Genart last call review of draft-ietf-dmm-mag-multihoming-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149746836602.14035.16572809666065484300@ietfa.amsl.com>
Date: Wed, 14 Jun 2017 12:26:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3LbDauStC8FpTFc42alCD7rDxH0>
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, 14 Jun 2017 19:26:06 -0000

Reviewer: Robert Sparks
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-dmm-mag-multihoming-03
Reviewer: Robert Sparks
Review Date: 2017-06-14
IETF LC End Date: 2017-06-16
IESG Telechat date: Not scheduled for a telechat

Summary: Not Ready

This document has several issues that need to be addressed before publication
as a proposed standard.

1) The document defines some wire syntax, but does not define (or refine) the
protocol for using these bits of wire syntax. For instance, the document does
not discuss if/when the MAG Identifier Option is necessary. It does not
discuss when the new error code it defines should be sent, nor what a recipient
should do if it receives that error code (I would have expected discussion
similar to some of the paragraphs in sections 5.4.1.2 and 6.9.1.2 of RFC5213).

2) There are sentence fragments that indicate information was lost at some
point in editing. 

    - "In the continuation of c, a Proxy" : what should have been where the 'c'
      is?

    - "or at When operating" : This looks a clause (and the end of a sentence)
      was lost after 'or at'. 'When operating' is clearly starting a new
      sentence.


Nits: 

* How are Preference Settings either a goal or a benefit? It seems out of 
  place in the list.
  
* at "leverage on latest" do you mean "leverage the latest"?
  
* at "allowing to make appropriate traffic steering decision", _what_ are you
  allowing to make a decision (who is the actor)?
  
* 'For example, the operator may have policy which binds traffic for 
   Application "X" needs to interface with Label "Y".' does not make sense. 
   Is the word "needs" extraneous?
  
* The last sentence in the definition of the Binding-Identifier appears to be
  describing the Interface Label.
  
* Something is missing at "and either based on" in the security considerations
  section.
  
* Consider using RFC8174 instead of RFC2119



From nobody Wed Jun 14 12:56:19 2017
Return-Path: <heas@shrubbery.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 D7F3212EB2D for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 12:56:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 P5R7GUPM1lfu for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 12:56:14 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id B835912EB32 for <ietf@ietf.org>; Wed, 14 Jun 2017 12:56:04 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 8A20F8D147; Wed, 14 Jun 2017 19:56:04 +0000 (UTC)
Date: Wed, 14 Jun 2017 19:56:04 +0000
From: heasley <heas@shrubbery.net>
To: Joe Touch <touch@isi.edu>
Cc: ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Message-ID: <20170614195604.GN89424@shrubbery.net>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.8.0 (2017-02-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9web4p1H_axXn2bzS1pMEi9tZwc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 19:56:17 -0000

Tue, Jun 13, 2017 at 03:03:07PM -0700, Joe Touch:
> Hi, all,
> 
> ...
> >   Title           : The Harmful Consequences of
> >         Postel's Maxim
> > https://tools.ietf.org/html/draft-thomson-postel-was-wrong-01
> I completely agree with John Klensin that a test suite defines the
> protocol standard (warts and all).

This may be, even if a pair of implementations were required company,
but is that wholly negative?  The test suite is not stuck in time; it can
evolve to test things that its authors had not anticipated, its own bugs,
or evolution of the protocol itself.  It is also more likely to catch bugs
and protocol design flaws than interoperability testing alone.

At the very least, an open test suite allows everyone to test against a
know baseline, before they test interoperation with other implementations.
For example, a rigid test suite that fails when an reserved field is not
its prescribed value, would be an asset for future development that
allocates the field.

Certainly the mentioned JSON problems would have benefitted from a test
suite and interoperability testing.  Clearly, peer review and
interoperability testing are insufficient.


From nobody Wed Jun 14 13:20:55 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17D1D1295A0 for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 13:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.702
X-Spam-Level: 
X-Spam-Status: No, score=-2.702 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_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=joelhalpern.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hDQj7N5Mpmw5 for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 13:20:52 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 5B9DC12957C for <ietf@ietf.org>; Wed, 14 Jun 2017 13:20:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 0ED812405F0; Wed, 14 Jun 2017 13:20:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1497471652; bh=w88EuBzWMFM0+2IyXqs3QAuNppkALaCNx/ItXn/q6JA=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=fJuugTJR+76jUmsr6Tmipt1hKBeN0Gp2G4a1yYGgx1jlpkrtU/4BILpdnqVFri+i/ iMauCDoewTJbzF3/QqprYdipN4i/jn0FK9C61kHOPYaQfNJKp7MYVxTGxEt4ofB6vK LAV/xSj8p/t5gEhIJJZIKjfqDkgaWW/WrusJJcIQ=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id F3C7824051F; Wed, 14 Jun 2017 13:20:50 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: heasley <heas@shrubbery.net>, Joe Touch <touch@isi.edu>
Cc: ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com>
Date: Wed, 14 Jun 2017 16:20:50 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <20170614195604.GN89424@shrubbery.net>
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/H9k1hbZkdyJgsVbU-0ug8G1QFZA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 20:20:54 -0000

Test suites are often quite useful.
But I can not imagine holding up an I-D from publication while we work 
out a test suite.

Demonstrably, there are cases where we have had trouble because people 
took divergent paths based on liberality in interpretation.
Equally clearly, the liberal acceptance approach has served us well in 
many cases.

Unclear specifications (unclear RFCs) are a problem.  Even Jon's 
oroginal formulation was not, from what I saw, intended to permit sloppy 
writing.  Or sloppy implementation.

There are indeed contexts where an application calling attention to a 
problem is very useful.  Silently ignoring things that indicate trouble 
is usually a mistake (although not always.)

I would be very unhappy to see us take the lesson from cases where we 
were sloppy to be that we should tell everyone to have their 
implementations break at the slightest error.

Yours,
Joel

On 6/14/17 3:56 PM, heasley wrote:
> Tue, Jun 13, 2017 at 03:03:07PM -0700, Joe Touch:
>> Hi, all,
>>
>> ...
>>>    Title           : The Harmful Consequences of
>>>          Postel's Maxim
>>> https://tools.ietf.org/html/draft-thomson-postel-was-wrong-01
>> I completely agree with John Klensin that a test suite defines the
>> protocol standard (warts and all).
> 
> This may be, even if a pair of implementations were required company,
> but is that wholly negative?  The test suite is not stuck in time; it can
> evolve to test things that its authors had not anticipated, its own bugs,
> or evolution of the protocol itself.  It is also more likely to catch bugs
> and protocol design flaws than interoperability testing alone.
> 
> At the very least, an open test suite allows everyone to test against a
> know baseline, before they test interoperation with other implementations.
> For example, a rigid test suite that fails when an reserved field is not
> its prescribed value, would be an asset for future development that
> allocates the field.
> 
> Certainly the mentioned JSON problems would have benefitted from a test
> suite and interoperability testing.  Clearly, peer review and
> interoperability testing are insufficient.
> 
> 


From nobody Wed Jun 14 13:50:37 2017
Return-Path: <paul@nohats.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 76D781271FD for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 13:50:36 -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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qTS_Ef2_rlIQ for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 13:50:34 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 D9C80126CC4 for <ietf@ietf.org>; Wed, 14 Jun 2017 13:50:33 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3wnzKy4PYkzp6; Wed, 14 Jun 2017 22:50:30 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1497473430; bh=ZiX9rKlIaiX6edw83f+qaud1oAmkvVECB+cbicmXQuk=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=IOgcp4Da40F7DFTcVDsXS8d0Vq8hDJZ032nBAWtHpCGA2YWSYo5dd41OzrOxMXVfY SkfxHpmLGVmhNe8Fv0DYqV8zF0/TbHUZZNf+tk7yQYHK+yjIKD85Lhpa8yVtg9L4kE 2b/k/qwDb6ZQe128INoKmZXXDB3fO68VZP7kxE/I=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id LHeLuMsfY0Ds; Wed, 14 Jun 2017 22:50:29 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 14 Jun 2017 22:50:28 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id A8ADE30AF32; Wed, 14 Jun 2017 16:50:27 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca A8ADE30AF32
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 93B7C421252B; Wed, 14 Jun 2017 16:50:27 -0400 (EDT)
Date: Wed, 14 Jun 2017 16:50:27 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
cc: ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
In-Reply-To: <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com>
Message-ID: <alpine.LRH.2.20.999.1706141647480.23684@bofh.nohats.ca>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com>
User-Agent: Alpine 2.20.999 (LRH 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/Vo1sRwqOZtPBDfZW1GdIQ3Uvp6w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 20:50:36 -0000

On Wed, 14 Jun 2017, Joel M. Halpern wrote:

> There are indeed contexts where an application calling attention to a problem 
> is very useful.  Silently ignoring things that indicate trouble is usually a 
> mistake (although not always.)
>
> I would be very unhappy to see us take the lesson from cases where we were 
> sloppy to be that we should tell everyone to have their implementations break 
> at the slightest error.

I fully agree. Postel's advise was and is good guidance. It is not a
dogma, and the reverse should also not become a dogma.

Paul


From nobody Wed Jun 14 14:02:55 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 18F60129549 for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 14:02:47 -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] 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 C-9_swlHvAkm for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 14:02:36 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 088811275AB for <ietf@ietf.org>; Wed, 14 Jun 2017 14:02:36 -0700 (PDT)
Received: from [128.9.184.249] ([128.9.184.249]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v5EL2Leg019480 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 14 Jun 2017 14:02:21 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: heasley <heas@shrubbery.net>
Cc: ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <814c3467-9e91-700a-d830-57165d38175a@isi.edu>
Date: Wed, 14 Jun 2017 14:02:21 -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: <20170614195604.GN89424@shrubbery.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-MailScanner-ID: v5EL2Leg019480
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SAffh1Edhl9jZwkIjzMooTpZVrE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 21:02:47 -0000

On 6/14/2017 12:56 PM, heasley wrote:
> Tue, Jun 13, 2017 at 03:03:07PM -0700, Joe Touch:
>> Hi, all,
>>
>> ...
>>>   Title           : The Harmful Consequences of
>>>         Postel's Maxim
>>> https://tools.ietf.org/html/draft-thomson-postel-was-wrong-01
>> I completely agree with John Klensin that a test suite defines the
>> protocol standard (warts and all).
> This may be, even if a pair of implementations were required company,
> but is that wholly negative?
Not necessarily, but it does negate the need for a specification.

"A designer with one set of requirements always knows what to follow; a
designer with two is never sure" (a variant of "a person with one watch
always knows what time it is...")

If you have a test suite, that singularly defines the protocol to the
exclusion of the spec, otherwise you don't have a complete suite.

>   The test suite is not stuck in time; it can
> evolve to test things that its authors had not anticipated, its own bugs,
> or evolution of the protocol itself.  It is also more likely to catch bugs
> and protocol design flaws than interoperability testing alone.
Interoperability tests are just a variant of test suites - just that
they are all relative to each other, rather than to a single entity.

However, forcing testing to a single entity will necessarily catch less
issues than cross-testing can.

> At the very least, an open test suite allows everyone to test against a
> know baseline, before they test interoperation with other implementations.
> For example, a rigid test suite that fails when an reserved field is not
> its prescribed value, would be an asset for future development that
> allocates the field.

That then begs the question:
    - what happens if my version passes the test suite but fails
interoperability tests?

> Certainly the mentioned JSON problems would have benefitted from a test
> suite and interoperability testing. 

But what happens when they provide conflicting results? At that point,
you need to decide which one wins; if that wins, why do the other?

>  Clearly, peer review and
> interoperability testing are insufficient.
Nothing is ever sufficient unless it is complete, and complete protocol
tests are not feasible for anything other than toy examples. The state
space blows up.

Joe


From nobody Wed Jun 14 15:27:38 2017
Return-Path: <heas@shrubbery.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 E9A81127077 for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 15:27:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level: 
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 2HZI96GAUgm2 for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 15:27:35 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id CCDC4120724 for <ietf@ietf.org>; Wed, 14 Jun 2017 15:27:35 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id A05638D29C; Wed, 14 Jun 2017 22:27:35 +0000 (UTC)
Date: Wed, 14 Jun 2017 22:27:35 +0000
From: heasley <heas@shrubbery.net>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
Cc: heasley <heas@shrubbery.net>, Joe Touch <touch@isi.edu>, ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Message-ID: <20170614222735.GO89424@shrubbery.net>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.8.0 (2017-02-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TV6Jqm087XfYoHX2Sd4-K4BHuNA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 22:27:37 -0000

Wed, Jun 14, 2017 at 04:20:50PM -0400, Joel M. Halpern:
> There are indeed contexts where an application calling attention to a 
> problem is very useful.  Silently ignoring things that indicate trouble 
> is usually a mistake (although not always.)

I believe that it is always a mistake; it will either bite now or later,
or its not a real error and while ignoring it, real errors are missed.
It should be addressed, whether in your implementation, the test suite,
the spec or the other implementation.  And, to Joe's point of resolving
the conflicts between the those; that dispute is not for the individual
to resolve.  The standards body should determine what the correct behavior
is.  That loop improves the spec, the suite, and interoperability - for
everyone's benefit.

quality, speed, price; pick two.  if you dont pick quality, you will likely
be disappointed - whether beer, brakes or bgp.  testing is a large
contributor to quality.

> I would be very unhappy to see us take the lesson from cases where we 
> were sloppy to be that we should tell everyone to have their 
> implementations break at the slightest error.

That is the suggestion of the draft; i suggest only that a test suite
should follow this - be devilishly rude - about the slightest error.


From nobody Wed Jun 14 15:31:35 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 D4BEA127077 for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 15:31:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 snKAa7Dkn_Va for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 15:31:32 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 50401128B90 for <ietf@ietf.org>; Wed, 14 Jun 2017 15:31:32 -0700 (PDT)
Received: from [128.9.184.249] ([128.9.184.249]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v5EMVAhd001966 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 14 Jun 2017 15:31:11 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz>
From: Joe Touch <touch@isi.edu>
Message-ID: <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu>
Date: Wed, 14 Jun 2017 15:31:10 -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: <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-MailScanner-ID: v5EMVAhd001966
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7l5-_AvzWOCHSfH0Pih0wFl_Cpo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 22:31:34 -0000

On 6/14/2017 8:41 AM, Petr Špaček wrote:
> To sum it up, decision what is acceptable and what is unacceptable
> should be in protocol developer's hands.
That should be in the specification.

What the specification leaves open, implementations should respect and
honor as allowed.

Joe



From nobody Wed Jun 14 15:44:56 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 3B4D312940D for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 15:44:55 -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 jZ1Hub4RZ59k for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 15:44:53 -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 6C5371293E8 for <ietf@ietf.org>; Wed, 14 Jun 2017 15:44:53 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id x63so6972724pff.3 for <ietf@ietf.org>; Wed, 14 Jun 2017 15:44:53 -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=uD5uJOzXS/o7IDmSflqiGs9anDbpyIgDUIHlf7jQGu8=; b=An6ynU6Z3ctS5A0qmSgkYz4hP1kZAcYssmmcC6LO+8BH5EUARCc3T3IndbEWRL1CeQ qklF0kOheiP0m+v1Ju9M+jlzowT+JAGb6z95EHF9GugdY2/DyDcWtHoTpLG9WgdgCSI0 BnI0OpicoOgUmatDVIAUdKxA0QHamiKuGj8Awf8WOkKRmscPBdEV1qYxmYIFRfjkEu0e WU6W13JtRKTIejBuSr5pp0SRMqwrv3G+sk3IOyjDglQrw/89loCBqXhep6KsGyIyguq6 w0F4XnZbiq4yvl6c4TFCOALlSXX9Ds/tzV4hu5hKJDTIhbHHaLJugNqf1u5B+4dPKZik tmig==
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=uD5uJOzXS/o7IDmSflqiGs9anDbpyIgDUIHlf7jQGu8=; b=RerKdU/YdbZWQw5jdrdyT3Wtppc724UsujTYtNnIf+NyQ4tuwiS3iSUP5gbw+98dU+ TyCOCaFY5tVtbjg1BSADAp6g+P+Pg+lljMOiVjL27u0One8xm09OS1dlhF2kfD9zxt3J 7lFicgzFyNT890tavbpAeJwT2Ktsa4fS7AjYNEC1d1sv1ya+2Mi53+f8f0TY+AqssoaW 21nzXPYd2ajJucMKNg5f2UglkUKXSkeKgLzcyenRDhaTR8l8m5LsPalDbk4Ou/DVJJ+g bGD4T41Vtu9RvXDKppLBzwTd5qvxNVfEdnK885K87NiZOYXqBHr1hn4HwlYzMwPtj96V 20bQ==
X-Gm-Message-State: AKS2vOxDUSdpY++JEhVN2oXDgnPT8FTJcuObCujc8vMAj11YFjUXAK+f 88Ih/dCw5lQ4nZeU
X-Received: by 10.98.131.73 with SMTP id h70mr2202067pfe.18.1497480292899; Wed, 14 Jun 2017 15:44:52 -0700 (PDT)
Received: from [192.168.178.21] ([118.148.126.2]) by smtp.gmail.com with ESMTPSA id n15sm1659970pgs.61.2017.06.14.15.44.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Jun 2017 15:44:52 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: "Joel M. Halpern" <jmh@joelhalpern.com>, heasley <heas@shrubbery.net>, Joe Touch <touch@isi.edu>
Cc: ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com>
Date: Thu, 15 Jun 2017 10:44:55 +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: <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.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/oae0hIfcTuX4lG9qoTQ159lZ1Eo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 22:44:55 -0000

On 15/06/2017 08:20, Joel M. Halpern wrote:
...
> I would be very unhappy to see us take the lesson from cases where we 
> were sloppy to be that we should tell everyone to have their 
> implementations break at the slightest error.

Indeed. We need implementations to be as robust as possible. That
means careful thought, both in the specification and in every
implementation, about how to handle malformed incoming messages.
There's no single correct answer, as I am certain Jon would have
agreed. Some types of malformation should simply be ignored,
because the rest of the message is valid. Others should cause the
message to be discarded, or should cause an error response to be
sent back, or should cause the error to be logged or reported to
the user. There is no single correct solution.

Clearly the Postel principle was intended as general guidance.

Looking at the core of the draft:

      Protocol designs and implementations should fail noisily in
      response to bad or undefined inputs.

that seems a very reasonable principle for *prototype* and
*experimental* implementations, and a lousy one for production
code, where the response to malformed messages should be much
more nuanced; and the users will prefer the Postel principle
as a fallback.

   Brian


From nobody Wed Jun 14 16:36:01 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 D1B95127F0E for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 16:35:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, PP_MIME_FAKE_ASCII_TEXT=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pgHMFv5eWdq1 for <ietf@ietfa.amsl.com>; Wed, 14 Jun 2017 16:35:57 -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 6104812025C for <ietf@ietf.org>; Wed, 14 Jun 2017 16:35:57 -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 21C8424AE09; Wed, 14 Jun 2017 23:34:34 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id DC374160008; Wed, 14 Jun 2017 23:34:36 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id C9781160096; Wed, 14 Jun 2017 23:34:36 +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 aSztKKiY1vCw; Wed, 14 Jun 2017 23:34:36 +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 4DFD9160008; Wed, 14 Jun 2017 23:34:36 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id B484E7BB27E9; Thu, 15 Jun 2017 09:34:33 +1000 (AEST)
To: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>
Cc: ietf@ietf.org
From: Mark Andrews <marka@isc.org>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz>
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
In-reply-to: Your message of "Wed, 14 Jun 2017 17:41:36 +0200." <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz>
Date: Thu, 15 Jun 2017 09:34:33 +1000
Message-Id: <20170614233433.B484E7BB27E9@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/liZC40q5F2fChe1nRoI-GaF_a6M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 14 Jun 2017 23:36:00 -0000

In message <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz>, =?UTF-8?B?UGV0ciDFoHBhxI1law==?= writes:
> On 14.6.2017 00:03, Joe Touch wrote:
> > Hi, all,
> > 
> > ...
> >>   Title           : The Harmful Consequences of
> >>         Postel's Maxim
> >> https://tools.ietf.org/html/draft-thomson-postel-was-wrong-01
> 
> Before I dive into details, let me state I support this documents in its
> current form.
> 
> 
> > I completely agree with John Klensin that a test suite defines the
> > protocol standard (warts and all).
> > 
> > However, I disagree with the characterization of the Postel Principle in
> > this doc, and strongly disagree with one of its key conclusions ("fail
> > noisily in response to...undefined inputs"). Failing in response to bad
> > inputs is fine, but "undefined" needs to be treated agnostically.
> > 
> > IMO, the Postel Principle is an admission of that sort of agnosticism -
> > if you don't know how the other end will react, act conservatively. If
> > you don't know what the other end intends, react conservatively. Both
> > are conservative actions - in one sense, you try not to trigger
> > unexpected behavior (when you send), and in another you try not to
> > create that unexpected behavior (when you receive).
> > 
> > That's the very definition of how unused bits need to be handled. Send
> > conservatively (use the known default value), but allow any value upon
> > receipt.
> 
> This very much depends on the the original specification.
> 
> If the spec says "send zeros, ignore on receipt" and marks this clearly
> as an extension mechanism then it might be okay as long as the extension
> mechanism is well defined.
> 
> 
> On the other hand, accepting values/features/requests which are not
> specified is asking for trouble, especially in long-term. Look at DNS
> protocol, it is a mess.
> 
> - CNAME at apex? Some resolvers will accept it, some will not.

Well this is something that should be checked on the authoritative
server when the zone is loaded / updated.  A resolver can't check
this as DNS is loosely coherent.  Delegations can come or go.  Other
data comes and goes.

> - Differing TTLs inside RRset during zone transfer? Some servers will
> accept it and some not.

And we have rules to truncate to the minimum value.

Named fails hard for a number of zone content issues when running
as the master server for a zone which it deliberately ignores when
running in slave mode as the slave operator can't fix them.  That
said if there was IETF consensus that these should be fatal on slave
zones, so that we aren't left to pick up a bad reputation for failing
to serve the zone, it would be easy to change them.

We are already failing to resolve signed zones when validating where
the authoritative servers returns FORMERR or BADVERS or fail to
respond to queries with a DNS COOKIE EDNS option being present.  In
both cases we fallback to plain DNS queries which are incompatible
with DNSSEC.  There are a number of .GOV zone served by QWEST that
fall into this category.  Yes, we have attempted to inform QWEST
for the last 2+ years that their servers are broken.

See https://ednscomp.isc.org/compliance/gov-full-report.html#eo
for zones.  They are highlighted in orange.

If we ever need to set a EDNS flag or send EDNS version 1 queries
the number of zones that will fail on a validating resoler will
increase mostly because too many firewalls default to "these field
must be zero" and drop the request instead of listening to the EDNS
RFC which say to IGNORE unknown flags and to return BADVERS with
the highest version you do support if you don't support the version.

Firewalls are capable of generating TCP RST so they should be capable
of generating a BADVERS response if they don't want to pass version
!= 0 queries.

Note: It doesn't have to resolvers that detect DNS protocol errors.
You can test for these sorts of errors easily and refuse to delegate
to servers that don't follow the protocol.

Resolvers can't continue to workaround every stupid response
autoritative servers return.  They don't have enough time.

> To sum it up, decision what is acceptable and what is unacceptable
> should be in protocol developer's hands. Implementations should reject
> and non-specified messages/things unless protocol explicitly says
> otherwise. No more "ignore this for interoperability"!
> 
> 
> With my DNS-software-develoepr hat on, I very clearly see value of
> The New Design Principle in section 4.
> 
> Set it to stone! :-)
> 
> 
> > The principle does not setup the feedback cycle in Sec 2; a bug is a bug
> > and should be fixed, and accommodating alternate behaviors is the very
> > definition of "be generous in what you receive". "Being conservative in
> > what you send" doesn't mean "never send anything new" - it means do so
> > only deliberately.
> > 
> > -----
> > Failing noisily is, even when appropriate (e.g., on a known incorrect
> > input), an invitation for a DOS attack.
> > 
> > That behavior is nearly as bad as interpreting unexpected (but not
> > prohibited) behavior as an attack. Neither one serves a useful purpose
> > other than overreaction, which provides increased leverage for a real
> > DOS attack.
> 
> Sorry but I cannot agree. This very much depens on properies of "hard
> fail" messages.
> 
> If "error messages" are short enough they will not create significantly
> more problems than mere flood of random packets (which can be used for
> DoS no matter what we). In fact, short predictible error message is even
> better because it gives you ability to filter it somewhere.
> 
> Also, passing underspecified messages further in the pipeline is causing
> problems on its own. (Imagine cases when proxy passes
> malformed/underspecified messages to the backend because it can.)
> 
> 
> So again, I really like this document. Thank you!
> 
> -- 
> Petr Špaček  @  CZ.NIC
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Thu Jun 15 04:28: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 C135C129B7D for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 04:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dZze5cMyDJq8 for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 04:28:49 -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 E0A4C129353 for <ietf@ietf.org>; Thu, 15 Jun 2017 04:28:48 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id 63so4046483ywr.0 for <ietf@ietf.org>; Thu, 15 Jun 2017 04:28: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=EcFrEx++0oQ7jtzC/hem1uhJdpXuXoHJW/Xp2hCZEZk=; b=WH0mnZpNSBWgZp+LgfVANYe90EVuzYB3KjWw85PXsbQjEoo3Z6NsrEy6f1RtMcAoPF sCup11pTN8/DmiXGFjasyw+wJn6zajH3k/quAZiPoX0qacmg19YszskGVB1MhVt57oJJ 4w7i6zwmO+dPRi/6dC+ixbQ5iB1kg+lk3kRjatuI0AMfTVIk9q3vTeA9qCEBMn+9QPMZ OivzKYPXwyEOnqDLqN6ByMxldNyflJ086CF7yandvDv1kEIQsRxT6MF2jg1ybP4Wy42/ tTa3KPhpLL7ahoB5ecb//gW2yGsiah0UunVvVXFH2WfWVsJM4tGz2xlNwvmNftYoN6KZ YdAg==
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=EcFrEx++0oQ7jtzC/hem1uhJdpXuXoHJW/Xp2hCZEZk=; b=MERFwQP3q6wRbCYDJHlGqpejgVETkl9diuFhdvJdDeKq3B3SpRXbvECEEEvMXWg7HI t4vJ+eMZyI/Jc5Ko4zvTuV8ETMowNITmvGH2tYRQKEge7pjxGbkg3lDXMg7m3anxKhXQ eWOOr9a5B3I5i0sVqmzpGs/J/go0tBVxVphUA5OHnzWRgpqzbs9DPh0Ozav78RTIrbOr KLKOpgGNPkcMIY+ncLrevYtGag37PFZ0WDV93osjjGl1dgC6kvbs9zyTBn/dP2e980Q2 BTHRulmDEidLfYcyYBtC/yQDLlwAx6O/IOeyQb/TR+IvQ+wBlWdv7hMJKvc4Rm5xpHOp gqRA==
X-Gm-Message-State: AKS2vOy7wLcE+4yS5TC3eqj4lJ13ZlgiwhSDhdGl3tTEhlBS/T+bBSjv Mbf1FxCYmGghQ9ZDnBUXEk4ed6z4rw==
X-Received: by 10.13.228.69 with SMTP id n66mr3794484ywe.275.1497526128135; Thu, 15 Jun 2017 04:28:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.216.85 with HTTP; Thu, 15 Jun 2017 04:28:47 -0700 (PDT)
Received: by 10.37.216.85 with HTTP; Thu, 15 Jun 2017 04:28:47 -0700 (PDT)
In-Reply-To: <345192A9-8FFD-48B1-9A16-084CBC03331C@frobbit.se>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com> <77b44755-0da4-6058-3ef0-879923739c6e@gmail.com> <345192A9-8FFD-48B1-9A16-084CBC03331C@frobbit.se>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 15 Jun 2017 06:28:47 -0500
Message-ID: <CAKKJt-fHTMw5+SKr_iqSv6kKv_56pvo4VBAu_Qd9Dssa4Z+uMw@mail.gmail.com>
Subject: Re: IAD Retirement
To: =?UTF-8?B?UGF0cmlrIEbDpGx0c3Ryw7Zt?= <paf@frobbit.se>
Cc: ietf@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c034ce4e8d7970551fdf8e8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dGlPJm_c0_pZD6R92z1Xh-DIoig>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jun 2017 11:28:51 -0000

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

Hi, Ray,

On Jun 13, 2017 00:26, "Patrik F=C3=A4ltstr=C3=B6m" <paf@frobbit.se> wrote:

On 12 Jun 2017, at 22:43, Brian E Carpenter wrote:

> We tend to complain a lot in the IETF. So I'm going to complain:
> The IETF won't be the same without Ray.
>
> Thanks for everything, especially for acting as a very helpful, cheerful
and efficient complaints desk.

Can not explain it much better than Brian.

Thanks Ray, you will indeed be missed. You took the job when the IETF was
in a delicate situation in time. You shaped the IAD, did ensure the actions
where based on rough consensus in the community while staying within
whatever real world constraints (budget, staff and what not) that exists.
Contracts here, contracts there. Travel logistics. Trains and airplanes.
Hotels and restaurants. Local jurisdictions. IANA transitions and many
other issues.

But in the core are humans. And you have an incredible ability to never
ever forget the humans.

Hold on to that!


What Patrik said (better than I could have said it).

Thank you.

Spencer

Best,

   Patrik F=C3=A4ltstr=C3=B6m

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

<div dir=3D"auto"><div>Hi, Ray,<br><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Jun 13, 2017 00:26, &quot;Patrik F=C3=A4ltstr=C3=B6m&q=
uot; &lt;<a href=3D"mailto:paf@frobbit.se">paf@frobbit.se</a>&gt; wrote:<br=
 type=3D"attribution"><blockquote class=3D"quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"quoted-text">O=
n 12 Jun 2017, at 22:43, Brian E Carpenter wrote:<br>
<br>
&gt; We tend to complain a lot in the IETF. So I&#39;m going to complain:<b=
r>
&gt; The IETF won&#39;t be the same without Ray.<br>
&gt;<br>
&gt; Thanks for everything, especially for acting as a very helpful, cheerf=
ul and efficient complaints desk.<br>
<br>
</div>Can not explain it much better than Brian.<br>
<br>
Thanks Ray, you will indeed be missed. You took the job when the IETF was i=
n a delicate situation in time. You shaped the IAD, did ensure the actions =
where based on rough consensus in the community while staying within whatev=
er real world constraints (budget, staff and what not) that exists. Contrac=
ts here, contracts there. Travel logistics. Trains and airplanes. Hotels an=
d restaurants. Local jurisdictions. IANA transitions and many other issues.=
<br>
<br>
But in the core are humans. And you have an incredible ability to never eve=
r forget the humans.<br>
<br>
Hold on to that!<br></blockquote></div></div></div><div dir=3D"auto"><br></=
div><div dir=3D"auto">What Patrik said (better than I could have said it).<=
/div><div dir=3D"auto"><br></div><div dir=3D"auto">Thank you.</div><div dir=
=3D"auto"><br></div><div dir=3D"auto">Spencer</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 #cc=
c solid;padding-left:1ex">Best,<br>
<br>
=C2=A0 =C2=A0Patrik F=C3=A4ltstr=C3=B6m<br>
</blockquote></div><br></div></div></div>

--94eb2c034ce4e8d7970551fdf8e8--


From nobody Thu Jun 15 06:54:28 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 9E2DC12E057 for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 06:54:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 12zmg1gxf1kt for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 06:54:24 -0700 (PDT)
Received: from bsa2.jck.com (ns.jck.com [70.88.254.51]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81D7D129C1C for <ietf@ietf.org>; Thu, 15 Jun 2017 06:54:24 -0700 (PDT)
Received: from [198.252.137.10] (helo=PSB) by bsa2.jck.com with esmtp (Exim 4.82 (FreeBSD)) (envelope-from <john-ietf@jck.com>) id 1dLVDy-0005m1-IH; Thu, 15 Jun 2017 09:54:14 -0400
Date: Thu, 15 Jun 2017 09:54:08 -0400
From: John C Klensin <john-ietf@jck.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
cc: "Joel M. Halpern" <jmh@joelhalpern.com>, heasley <heas@shrubbery.net>, Joe Touch <touch@isi.edu>, ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Message-ID: <8DD97FABD6ADD0A0202246FE@PSB>
In-Reply-To: <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@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/8oRNercnDC5SFHEGT4b0z0esK-0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jun 2017 13:54:26 -0000

--On Thursday, June 15, 2017 10:44 +1200 Brian E Carpenter
<brian.e.carpenter@gmail.com> wrote:

> On 15/06/2017 08:20, Joel M. Halpern wrote:
> ...
>> I would be very unhappy to see us take the lesson from cases
>> where we  were sloppy to be that we should tell everyone to
>> have their  implementations break at the slightest error.
> 
> Indeed. We need implementations to be as robust as possible.
> That means careful thought, both in the specification and in
> every implementation, about how to handle malformed incoming
> messages. There's no single correct answer, as I am certain
> Jon would have agreed. Some types of malformation should
> simply be ignored, because the rest of the message is valid.
> Others should cause the message to be discarded, or should
> cause an error response to be sent back, or should cause the
> error to be logged or reported to the user. There is no single
> correct solution.
> 
> Clearly the Postel principle was intended as general guidance.
> 
> Looking at the core of the draft:
> 
>       Protocol designs and implementations should fail noisily
> in       response to bad or undefined inputs.
> 
> that seems a very reasonable principle for *prototype* and
> *experimental* implementations, and a lousy one for production
> code, where the response to malformed messages should be much
> more nuanced; and the users will prefer the Postel principle
> as a fallback.

+1 and exactly right.

It is also a good principle for independently-developed test
suites.  Indeed, I agree with 

--On Wednesday, June 14, 2017 22:27 +0000 heasley
<heas@shrubbery.net> wrote:

>> I would be very unhappy to see us take the lesson from cases
>> where we  were sloppy to be that we should tell everyone to
>> have their  implementations break at the slightest error.
> 
> That is the suggestion of the draft; i suggest only that a
> test suite should follow this - be devilishly rude - about the
> slightest error.

But I don't see that as a contradiction: test suites that are
developed by third parties reading standards, deciding what
should be tested, and being brutally narrow about requirements
may be very useful in developing good implementations.  The type
of reading of standards such developments that encourages can
also, if used as feedback, improve the standards.    The problem
arises when test suite (and/or certifications) are produced or
endorsed by the standards developer.  If they are endorsed in
that way, they become alternate statements of the standards
themselves and Joe's observation:

> Not necessarily, but it does negate the need for a
> specification.
> 
> "A designer with one set of requirements always knows what to
> follow; a designer with two is never sure" (a variant of "a
> person with one watch always knows what time it is...")
> 
> If you have a test suite, that singularly defines the protocol
> to the exclusion of the spec, otherwise you don't have a
> complete suite.

Applies.  If they are independently developed, they are just
like another implementation: two implementations either
interoperate or they do not; an implementation may conform to
the test suite or not but the standard is the standard and the
authority.  It is possible for the text suite to simply be in
error and for things to conform to the test suite but not the
standard.  It is the two sets of requirements that is the
problem.

The I-D notwithstanding, very little of that has anything to do
with the robustness principle, which, as Brian suggests, is
intended for production implementations and much less so for
experiments, demonstrations, prototypes, reference
implementations, etc.   Certainly the robustness principle has
been misused by sloppy or lazy implementers to claim that they
can produce and send any sort of garbage they like and that
recipients are responsible for figuring out what was intended,
but that was never the intent and (almost) everyone knows that,
including most of the sloppy/ lazy (or arrogant) implementers
who would probably behave that way whether Postel had ever
stated that principle [1]. I suggest that one of the reasons the
Internet has been successful is precisely because of sensible
application of the robustness principle.   Not only do things
mostly work, or at least produce sensible error messages or
warnings rather than blowing up, in the presence of small
deviations or errors, but (in recent years at least in theory)
it avoids out having to spend extra years in standards
development while we analyze every possible error and edge case
and specify what should happen.  Instead, when appropriate, we
get to say, when appropriate, "this is the conforming behavior,
if you don't conform, the standard has nothing to say to you,
but you should not depend on its working".  The robustness
principle is important guidance for those edge cases 

That assumes a higher level of thinking and responsibility on
the part of implementers than may be justified in the current
world, but I suggest that the fix is not to abandon the
robustness principle.  Personally, I'd like to see more
litigation or other sorts of negative reinforcement against
sloppy implementations and implementers that cause damage.
YMMD, but there is lots of evidence that standards that try to
cover and specify every case are not the solution (see below).

Finally, because I don't want to write a lot of separate,
slightly-connected, notes...

--On Tuesday, June 13, 2017 14:28 +0000 heasley
<heas@shrubbery.net> wrote:

>> Actually, a number of standards bodies have found, to their
>> chagrin, that test suites that are developed and.or certified
>> by the standards body are a terrible idea.  The problem is
>> that they become the real standard, substituting "passes the
>> test suite" for "conformance to the standard" or the IETF's
>> long
> 
> reference?

Sorry, but I don't have time to do the research to dig that
material out and some of what I found quickly has "members only"
availability.   I speak from a "been there, done that"
perspective, with a background that includes standards
development and oversight body leadership roles in ASNI SDOs,
ANSI, and ISO.  Most of my first-hand experience on that side of
things involved programming languages (including observing a
certain one named after a famous early woman programmer with a
three-letter first name that came, in practice, to be defined
entirely by the test/conformance suite) and, closer to IETF's
interests, some OSI-related protocols in which the effort to
specify ever case led to specifications and profiles that either
were never finished or that became so cumbersome as to be
unimplementable.  I won't claim that is what killed OSI and let
the Internet succeed instead (I think there is a rather long
list of contributors), but it was one element.

best,
    john

[1] I note that we have had some worked examples of software
vendors who have taken the position that they are so important,
or that their ideas have achieved sufficient perfection, that
their systems don't need to conform to standards and that
everyone else, including the standards bodies, just need to
conform to them and whatever they produce.  That behavior can't
be blamed on Postel either, nor can the consequences if the IETF
decides to go along and adjust the standards.

> 
>    Brian
> 





From nobody Thu Jun 15 07:50:18 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60256129BAC for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 07:50:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.41
X-Spam-Level: 
X-Spam-Status: No, score=0.41 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FORGED_MUA_MOZILLA=2.309, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k-HBmqxee9_1 for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 07:50:15 -0700 (PDT)
Received: from sonic302-29.consmr.mail.gq1.yahoo.com (sonic302-29.consmr.mail.gq1.yahoo.com [98.137.68.155]) (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 2E2B2128B93 for <ietf@ietf.org>; Thu, 15 Jun 2017 07:50:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1497538214; bh=jIplsw2/XV/gjnPMeR4mFiNFDQMUe9RrKz9IX1VriTs=; h=Date:From:Reply-To:To:Subject:References:From:Subject; b=dy2NV2TMG4TY9AK5Tyrbiw0CHYv3Z6yUuhs85ONWM7yQfdGX3PdZ5nx5Gky7W4QFtqUVkYvKt73Xi8wAbXjmHfUmg8LinSXG1yw94cI5xo4IvbL1nDN11xfrQbjbdfBWjykMhslNrzABPgznY2Mxvr24sMPSYfY6oOh98D6qrUz2QMSJllqLd6weO5FFcpwKiyZstdzKUDzmskmF1w22quMM4a5qh2+hn0LDTMYaHpq4gielLVrYAfTwvvxIi1oqPNQ55xDYQv3y9jZpBrYKtSTTEVb4ILPwMPqNJdD22lRQOVlVQCJ6vHaiV2mr2C4UPDdDoZzWVTB1YyrM4pQmlA==
X-YMail-OSG: HG3mLsQVM1l7lIerHjyf9YOIE0gKgM99rTvzORkjxkwaLA3uBaFmxnsvSQ5o7zM uUugq5Z8Y02G5lvAUva5RuO21C9tlxLhEFIupZBLgy0VgOaMCXz6JbUZLpmsVMU2aIq8psuS3FLc AN5egfXQD7AK0sBkw05Ev7D8zyCJU3TzzBmHBU7YQRnMJnnUhCgxLgvfT7HLtrSV7bq.IjRJHKVv RjWdgTk5rr4sXhF3Xsj18lGiAZUsqy9YehdcYx4JSB1oX_cLOid7pLd2lmKIyxQD.XePpBSNDb.4 Yy5sVQ6lA9awpdaFb71T8E.5805l6F40.VCqYUHJSHzx6HkWTyJW0ExAY1JQ20_2BX06aYKK7jFp zYpfsA7LVl5uBAnCXgUFvlnCtyKeUwFDAmQD5gBcsNCPJZQYehxDst_Pf8nKR5OTXwnhiRES2tOl GbBY2ooAj2BUG.StMHVQnsvswT6zhIzmQB_yki1ZSerNHkyLrx7KvCXVo0rR6y_p58wm_N0o8Dbw WNz_wo0I5N7aSXvO.wNsNjoZy9h8UzLxY2oMX0jE5wMJgILtZ.2cJ0V6aRSG0Q3uWjo6ReHfooTm J_IU-
Received: from sonic.gate.mail.ne1.yahoo.com by sonic302.consmr.mail.gq1.yahoo.com with HTTP; Thu, 15 Jun 2017 14:50:14 +0000
Date: Thu, 15 Jun 2017 14:50:14 +0000 (UTC)
From: <nalini.elkins@insidethestack.com>
Reply-To: <nalini.elkins@insidethestack.com>
To: <vmeet@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <1280323857.13113587.1497538214458@mail.yahoo.com>
Subject: Remote Participation Hubs
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
References: <1280323857.13113587.1497538214458.ref@mail.yahoo.com>
X-Mailer: WebService/1.1.9778 YahooMailBasic Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OGWPSOg9Aopq9Byxf4yXBDKJzZw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jun 2017 14:50:16 -0000

All,

We have submitted the first of three drafts discussing Remote Hubs.   Please provide comments on the VMEET list.

Three types of remote hubs are defined.  Each has its own characteristics.

  - Remote Participation Hubs
  - Remote Viewing Hubs
  - Enduring Local Meetups

The first document defines a Remote Participation Hub (RPH).  Other documents are coming to define the other types of hubs.  A common structure of sections will be
used as far as possible for all hub types.

 
URL:            https://www.ietf.org/internet-drafts/draft-elkins-ietf-remote-participation-hubs-00.txt
Status:        https://datatracker.ietf.org/doc/draft-elkins-ietf-remote-participation-hubs/
Htmlized:      https://tools.ietf.org/html/draft-elkins-ietf-remote-participation-hubs-00
Htmlized:      https://datatracker.ietf.org/doc/html/draft-elkins-ietf-remote-participation-hubs-00



Thanks,

Nalini Elkins
CEO and Founder
Inside Products, Inc.
www.insidethestack.com
(831) 659-8360


From nobody Thu Jun 15 07:52:17 2017
Return-Path: <bashandy@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 9A3B612EA7F; Thu, 15 Jun 2017 07:52:15 -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 w-e3yxxzD1bj; Thu, 15 Jun 2017 07:52:12 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9ACF712EA95; Thu, 15 Jun 2017 07:51:48 -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=1497538308; x=1498747908; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=CnegMkchwVxWlIMvfFKcTPdTWaehMbL2s/NPe3i6rZw=; b=Lwe1v3OLEFDMMDrfRLr7vCF95S3rSfz2jb16DNmGTYO/vLS0Ko+EY+2M X72ec8VtcZq7QWURPWwFfnff55B1egIvNaEJztRx+OvHKYeP6xidYYTiN RRJykI5mn4tf7hwPk4beSzYg9t6bdzoNxMQdJDEBQPfX0Wfrev5AsRmo3 k=;
X-IronPort-AV: E=Sophos;i="5.39,343,1493683200"; d="scan'208";a="256364433"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 15 Jun 2017 14:51:48 +0000
Received: from [10.24.36.248] ([10.24.36.248]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v5FEpjpL019773; Thu, 15 Jun 2017 14:51:46 GMT
Message-ID: <59429F00.5060503@cisco.com>
Date: Thu, 15 Jun 2017 07:51:44 -0700
From: "Ahmed Bashandy (bashandy)" <bashandy@cisco.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: Stewart Bryant <stewart@g3ysx.org.uk>, rtg-dir@ietf.org
CC: draft-bashandy-rtgwg-segment-routing-ti-lfa.all@ietf.org, ietf@ietf.org
Subject: Re: Rtgdir early review of draft-bashandy-rtgwg-segment-routing-ti-lfa-00
References: <149625574151.19908.2374594318145684422@ietfa.amsl.com>
In-Reply-To: <149625574151.19908.2374594318145684422@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/d9M5XvUrk1ldq5OK00_Xoqdt-Ho>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jun 2017 14:52:16 -0000

Thanks for the detailed review
See inline #Ahmed

Ahmed

On 5/31/2017 11:35 AM, Stewart Bryant wrote:
> 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.
#Ahmed
OK. We will take care of the 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.
#Ahmed:
The draft is specific to SR as it is clear from the title. But I can add 
a statement to mentioning that other traffic steering protocols and/or 
algorithms may be used but are outside the scope of this document
>
> 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.
#Ahmed
I agree. We are only protecting traffic that flows via the PLR.
>
> 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.
#Ahmed
This draft address only loop-free alternate due to local failure as it 
is very clear from its name. The concept of microloop avoidance is 
discussed in a separate draft as you may already know. I will add a 
reference to that other draft as you suggested.
>
> 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.
#Ahmed
Again the draft is specific to SR. There are other generic RFCs in the 
references. In this draft we are talking about SR-based techniques.
>
> 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.
#Ahmed
The draft mentions in multiple places that the protection is done for 
node and SRLG failures. But I can add a statement that says that we are 
protecting against a single link, single node, or single SRLG group 
failure to avoid any ambiguity
>
> 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.
#Ahmed
The traffic is steered over the shortest path(s). Traffic is steered 
over the post convergence path(s) by stitching path segments, where each 
path segment is either a shortest path on its own or a link. The 
resultant composite path(s) are loop free post-convergence shortest path(s)
There is no need to use any other concept other than the usual shortest 
path and/or links
>
> 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.
#Ahmed
The draft talks about shortest path only as calculated by the IGP on the 
PLR. Constrained shortest path is beyond the scope of this document. 
Although IMO it is clear, I will add a statement to clearly mention that 
we are protecting standard IGP shortest paths as calculated by routing 
protocols using SR methodology
>
>
> 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.
#Ahmed

What we are doing here is explicitly steering the traffic along the post 
convergence path without waiting for the the network to converge. This 
is the path that the user has selected to use when the primary path 
fails. Hence we are not really violating any constraint as long as 
SR-based traffic steering is used
We agree that constrained shortest path which utilize LFAs calculated by 
the techniques proposed in this draft may not conform to the original 
set of constrains. But as we mentioned above, protecting constrained 
shortest path is not a topic of this draft

>
> 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.
#Ahmed
As mentioned above, this draft is specific to protecting standard 
shortest path using SR
>
>
> 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.
#Ahmed
I do not understand the difference between the text in the draft and the 
text that you are proposing.
>
>     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?
#Ahmed
Agreed. I can reword it to say that it will protect against the failure 
of any one of the following: single Link, single node, or single local 
SRLG failure in any IGP network, using SR.
>
> 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.
#Ahmed
Agreed. I will add a reference there
>
> Also you are considering Adj segments, and presumably they were there
> for a reason, but you do not discuss that.
#Ahmed
Adj segments are used for steering. It is a basic SR concept that is not 
specific to ti-lfa. If you are asking whether technique proposed in this 
draft can be used to protect adj-SIDs, then the answer is yes. I will 
add description to that in the next versions
>
> 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.
#Ahmed
OK
>
> 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
#Ahmed
Agreed
>


From nobody Thu Jun 15 08:05:57 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 CE0DB12944A for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 08:05:55 -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 P_arSoeAddft for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 08:05:54 -0700 (PDT)
Received: from nitro.isi.edu (nitro.isi.edu [128.9.208.207]) (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 7707012EA95 for <ietf@ietf.org>; Thu, 15 Jun 2017 08:05:54 -0700 (PDT)
Received: from [192.168.1.158] (cpe-172-250-240-132.socal.res.rr.com [172.250.240.132]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v5FF5UdQ019462 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 15 Jun 2017 08:05:31 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
From: Joe Touch <touch@isi.edu>
X-Mailer: iPad Mail (14F89)
In-Reply-To: <8DD97FABD6ADD0A0202246FE@PSB>
Date: Thu, 15 Jun 2017 08:05:30 -0700
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, "Joel M. Halpern" <jmh@joelhalpern.com>, heasley <heas@shrubbery.net>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EED92F63-64AE-4CE3-B169-94C04998D051@isi.edu>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <8DD97FABD6ADD0A0202246FE@PSB>
To: John C Klensin <john-ietf@jck.com>
X-MailScanner-ID: v5FF5UdQ019462
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/RXNuuou3XUPZXtFf11v1vOlzaf4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jun 2017 15:05:56 -0000

> On Jun 15, 2017, at 6:54 AM, John C Klensin <john-ietf@jck.com> wrote:
>=20
> I suggest that one of the reasons the
> Internet has been successful is precisely because of sensible
> application of the robustness principle.   Not only do things
> mostly work, or at least produce sensible error messages or
> warnings rather than blowing up, in the presence of small
> deviations or errors, but (in recent years at least in theory)
> it avoids out having to spend extra years in standards
> development while we analyze every possible error and edge case
> and specify what should happen.  Instead, when appropriate, we
> get to say, when appropriate, "this is the conforming behavior,
> if you don't conform, the standard has nothing to say to you,
> but you should not depend on its working".  The robustness
> principle is important guidance for those edge cases.

+1

Further, testing for all those edge cases becomes itself a performance burde=
n on operational code, amplifying the leverage of a DOS attack based on all t=
hat excess validation.

The Postel principle helps make achieving the balance between usefulness and=
 correctness tractable.

Joe




From nobody Thu Jun 15 08:19:13 2017
Return-Path: <scott.brim@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 E847F127873; Thu, 15 Jun 2017 08:19:11 -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 qxWlA_iOs6Yn; Thu, 15 Jun 2017 08:19:10 -0700 (PDT)
Received: from mail-yw0-x230.google.com (mail-yw0-x230.google.com [IPv6:2607:f8b0:4002:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 012CF127201; Thu, 15 Jun 2017 08:19:09 -0700 (PDT)
Received: by mail-yw0-x230.google.com with SMTP id e142so7700606ywa.1; Thu, 15 Jun 2017 08:19:09 -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=3n3SWeN5vRUnEzKQU0WrhUrM95DuNWxxyzTRINU/msQ=; b=Vfee/Ql/iaSobucInr+tdK618L4LCWw9MeVfn1hm62Xo1I8oc94moC1xMvZE0+W0Af NDFAWfyc69STXaaccEYO/jYnSnJVBV77U8Qo6CD4fD3RFOIfkrcn5be5ayEtS8aE5smb x/xOjyvNuLfrjMT8vnJack3qbcC5v9qkCg1DJrkWNjhZ5H4T8SOv1CrNXW+ri6TSnNEK joaAqz3W3Zq1Sxq4YbJvtAlsfGi+FjNOQS6RjT56iTBvqE017yJ4lYV7amlgERs6iiDg Y6dyfTs33Ruc04Ta4BtYua2vPxuTA3X/2F70tnFmsWMhyWgBAfQOkNSoPfUm839R2/hR tidA==
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=3n3SWeN5vRUnEzKQU0WrhUrM95DuNWxxyzTRINU/msQ=; b=IM1tXUtkee93Tx0kpfTJy81f4Lul4dPi2A4FLcF9UyAHNryjmZgY9matYjH3Gc0cKI 4RAciNjgCdIwdLRgewWnLeV6qYNDGgFDIGBlhjt8EVw3B7g5+xOwGkEjRab8QXE53t+G gr4il8zrUm+Y0te0iLs0ZTdUhvIXN3IC+CfWd+uYP55gXyXfszsTffFYsqRB9zek1nwW x8xAW9BiOYR5ubVJdLmHV7TcounQ2X0pxr/LC8fKXSVxP3fAuLndH7C8MLTARYR+P6Qd LJV8tnDhEAtwQgYZe6KUUZLo723qVzhL4rPDN0pCVi3PyxXf4CWnQEqZsQ7KJD+TaIhj ONJA==
X-Gm-Message-State: AKS2vOwi+edV5cWFir3u1GdtuWhXNBDnGi5be+V9P9St/ctAW/WGL/Bb yQv43p8TJnWoOkNADKqYjNNMUZ6Fukae
X-Received: by 10.13.194.70 with SMTP id e67mr4693071ywd.304.1497539948884; Thu, 15 Jun 2017 08:19:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.45.194 with HTTP; Thu, 15 Jun 2017 08:18:48 -0700 (PDT)
In-Reply-To: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
References: <149727427537.10333.7649103852167051395.idtracker@ietfa.amsl.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Thu, 15 Jun 2017 11:18:48 -0400
Message-ID: <CAPv4CP9=6EghFNJSVLnjfBoqeJ3HhpmGYYfenZtzJOzz=vDxoQ@mail.gmail.com>
Subject: Re: IAD Retirement
To: IETF discussion list <ietf@ietf.org>
Cc: IETF Announcement List <ietf-announce@ietf.org>
Content-Type: multipart/alternative; boundary="001a114f5006b0bd0605520130b7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OcZnklHmgsTpDlmglMVKc4Cv4Pw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jun 2017 15:19:12 -0000

--001a114f5006b0bd0605520130b7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

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

<div dir=3D"ltr"><div class=3D"gmail_extra">=E2=9D=A4<br></div></div>

--001a114f5006b0bd0605520130b7--


From nobody Thu Jun 15 10:32:48 2017
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECA11293D8; Thu, 15 Jun 2017 10:32:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: <tsv-art@ietf.org>
Cc: trill@ietf.org, ietf@ietf.org, draft-ietf-trill-over-ip.all@ietf.org
Subject: Tsvart early review of draft-ietf-trill-over-ip-10
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149754795560.13109.17521244075940607817@ietfa.amsl.com>
Date: Thu, 15 Jun 2017 10:32:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SfGevKz3coSTezOChkONV8Lry10>
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, 15 Jun 2017 17:32:36 -0000

Reviewer: Magnus Westerlund
Review result: Not Ready

Early review of draft-ietf-trill-over-ip-10
Reviewer: Magnus Westerlund
Review result: Not Ready

TSV-ART review comments:

I have set this to not ready as there are several issues, some significant that
could affect the protocol realization significantly. Some may be me missing
things in TRILL, I was not that familiar with it before this review and I have
only tried looking up things, not reading the whole earlier specifications. So
don't hesitate to push back and provide pointers to things that can resolve
issues. The authors and the WG clearly have thought about a lot of issues and
dealt with much already.

Diffserv usage
--------------

Section 4.3:

   TRILL over IP implementations MUST support setting the DSCP value in
   the outer IP Header of TRILL packets they send by mapping the TRILL
   priority and DEI to the DSCP. They MAY support, for a TRILL Data
   packet where the native frame payload is an IP packet, mapping the
   DSCP in this inner IP packet to the outer IP Header with the default
   for that mapping being to copy the DSCP without change.

I think it is fine to require that implementations are capable  of setting
DSCP values on the outer IP header. However, I fail to see any discussion of
the potential issues with actually setting the DSCP values. It is one thing to
do this in an IP back bone use case where one can know and have control over
the PHB that the DSCP values maps to. But otherwise, over general internet the
behavior is not that predictable. One can easily be subject to policers or
remapping. Also as the actual DSCP code point usage is domain specific this is
difficult. Priority reversal is likely the least of the problems that this can
run into over general Internet.

Section 4.3:

   The default TRILL priority and DEI to DSCP mapping, which may be
   configured per TRILL over IP port, is an follows. Note that the DEI
   value does not affect the default mapping and, to provide a
   potentially lower priority service than the default priority 0,
   priority 1 is considered lower priority than 0. So the priority
   sequence from lower to higher priority is 1, 0, 2, 3, 4, 5, 6, 7.

      TRILL Priority  DEI  DSCP Field (Binary/decimal)
      --------------  ---  -----------------------------
                  0   0/1  001000 / 8
                  1   0/1  000000 / 0
                  2   0/1  010000 / 16
                  3   0/1  011000 / 24
                  4   0/1  100000 / 32
                  5   0/1  101000 / 40
                  6   0/1  110000 / 48
                  7   0/1  111000 / 56

This appear to be an problematic mapping. At least for prio 0 and 1. As
priority 1 appears to be intended to be higher than priority 0, it is
interesting that it is mapped to CS1, which to quote
https://datatracker.ietf.org/doc/rfc7657/:

CS1 ('001000') was subsequently designated as the recommended
      codepoint for the Lower Effort (LE) PHB [RFC3662].

So what is proposed can in a network using default mapping, result in that you
get priority 0 to be lower priority than 1. Plus that in some networks this can
also results in strange remapping that results in a different PHB for CS1 than.

MTU and Fragmentation
---------------------

I think there are two main issue here. The first one is MTUD discovery
of the actual IP path MTU between the ports. That will be needed to prevent
a lot of traffic going into MTU black holes. Especially as TRILL requries
1470 byte support which is likey above a lot of paths.

Section 8.4:

   Path MTU discovery [RFC4821] should be useful
   in determining the IP MTU between a pair of RBridge ports with IP
   connectivity.

The issue with RFC4821 is that it has requirements on the packetization layer.
Trill appears to have several components that are useful. However, it will
require a specification of the procedure to result in a useful tool.

Section 8.4:

   TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
   [RFC7177], can be used to obtain added assurance of the MTU of a
   link.

Yes, that can confirm working MTUs that are at 1470 or above, but appears
prevented from working below 1470?

Thus, it appears that there is a lack of mechanism here to actually get a valid
and functional MTU from TRILL in the cases where the Path MTU is below 1470. If
I am wrong good, but I think this is an important piece for how to handle the
next main issue.

UDP encapsulation and IP fragments.
I see it as a big issue that UDP encapsulation is the native one, and that
relies on IP fragmentation despite the need for reliable fragmentation. With
the setup of having to support 1470 MTU on TRILL level some packets will be
fragmented in many environments. That will lead to a lot of losses, and as
discussed below a very big problem with middleboxes. The main problem here is
that if one tries to rely on IP fragments one will have issues with packets
ending up in black holes. And different problems depending on IPv4 or IPv6.
IPv6 is lilkely the lesser problem assuming that one have working PMTUD.

There are several ways out of this.

1. Detect issues and use TCP encapsulation with correctly set MSS to not get IP
fragements 2. Determine MTU and implement an fragmentation mechanism on top of
UDP.

Zero Checksum:
--------------

Section 5.4:

UDP Checksum - as specified in [RFC0768]

Considering the fast path encapsulation desire, I am surprised to not see any
mentioning of use of zero checksum here. Raising the zero checksum and forward
reference would be good I think.

And then Section 8.5:

   The requirements for the usage of the zero UDP Checksum in a UDP
   tunnel protocol are detailed in [RFC6936]. These requirements apply
   to the UDP based TRILL over IP encapsulations specified herein
   (native and VXLAN), which are applications of UDP tunnel.

If you actually intended to allow zero checksum, then you actually should
document that Trill fulfills the requirements that the applicability statement
raises. I have not analyzed how well it meets these requirements.

Please review Section 6.2 of RFC 8086 for example how that can be done.

TCP Encapsulation issue
-----------------------

Section 5.6:

The TCP encapsulation appear to be missing an delimiter format allowing each
individual TRILL packet/payload to be read out of the TCP's byte stream. In
other words, a normal implementation has no way of ensuring that the TCP
payload starts with the start of a new TRILL payload. Multiple small TRILL
payloads may be included in the same TCP payload, and also only parts as TCP is
one way of dealing with TRILL packets that are larger than the IP+Encapsulation
MTU that actually will work.

This comment is based on that there appear to be no length fields included in
the TRILL header. The most straight forward delimiter is a 2-byte length field
for the TRILL payload to be encapsulated.

Section 5.6:

TCP endpoint requirements. I do wonder if an application like TRILL actual
would need to discuss performance impacting implementation choices or
limitations. For example use of NAGLE, the requirements on buffer sizes in
relation to Bandwidth delay products, as buffer memory in a RBridge will impact
performance.

Congestion Control
------------------
First thanks for the effort here.

8.1.2 In Other Environments

   Where UDP based encapsulation headers are used in TRILL over IP in
   environments other than those discussed in Section 8.1.1, specific
   congestion control mechanisms are commonly needed.  However, if the
   traffic being carried by the TRILL over IP link is already congestion
   controlled and the size and volatility of the TRILL IS-IS link state
   database is limited, then specific congestion control may not be
   needed. See [RFC8085] Section 3.1.11 for further guidance.

This is correct, however my question is if the RBridges have anyway of knowing
which traffic is actually congestion controlled, considering that TRILL provides
an layer 2 abstraction. I wonder if there should be any type of white list of
the types of layer 2 payloads that can be assumed to be congestion controlled,
and thus okay to forward over IP paths? I am worried that without any
recommendation to prevent traffic that is not controlled to be forwarded, can
lead to congestion issues.

The other issue I think may exist is the issue serial unicast emulation of
broadcast/multicast creates. As this amplifies the outgoing packet rate with
a factor of how many addresses are configured for serial unicast this can
be significant traffic expansion. Thus, I think additional considerations are
needed here, and maybe rate limiting of the amount of traffic to be multicasted.

Flow and ECMP
-------------

Section 8.3:

For example, for TRILL
   Data, this entropy field could be based on some hash of the
   Inner.MacDA, Inner.MacSA, and Inner.VLAN or Inner.FGL.

I would appreciate clearer references to what these fields are.

If I understand this correctly, the idea here is to look into the inner
layer 2 frames, and use the flow equivalents that exists on that level and
hash that into value that maps the flows onto the source port range.

I think this text should include a summary of the principle and ensure to
note the important requirement that what is considered flows in the inner
must not result in being striped over multiple source ports as this may lead to
reordering issues due to packets taking different paths.

NAT and TRILL over IP:
Section 8.5:

If one like to use TRILL over IP through a NAT, then there are some very
important considerations that are missing. First the need for static binding
configurations or the need for determining ones external address(es) and be
able to communicate that to the peer RBridges, and in addition ensure that one
has keep-alives to that the NAT binding never times out.

Next is the issue that there is almost zero chance of getting a IP/UDP
encapsulation TRILL payload through the NAT if it results in IP fragmentation,
as NATs don't do defragment and refragmented on the internal side, and an IP
fragment lacks UDP port and thus can't be matched to binding.

Also if you like to run IP/ESP through a NAT, then you most likely need the
IP/UDP/ESP encapsulation (https://tools.ietf.org/html/rfc3948). Note that this
will restrict the MTU even further and thus ensure that the 1470 requirement
cannot be fulfilled even without additional tunnels over an 1500 bytes MTU
Ethernet infrastructure.

I would note that also firewalls likely have issues with IP fragments for the
same reason, they require significant amount of state to be verified if they
should be let through.

In general I think you should create a configuration that has chance to work
through most middleboxes, but I think you should require static bindings. I
think that configuration is, and don't laugh now, but IP/UDP/ESP/TCP/TRILL,
otherwise you will not be able to have both security and reliable fragmentation
of TRILL packets.

Cheers

Magnus Westerlund



From nobody Thu Jun 15 11:28:14 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 C5B1212426E for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 11:28:13 -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 dhuy2T9j68Bl for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 11:28:11 -0700 (PDT)
Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B325B120721 for <ietf@ietf.org>; Thu, 15 Jun 2017 11:28:11 -0700 (PDT)
Received: by mail-it0-x22d.google.com with SMTP id m62so22860392itc.0 for <ietf@ietf.org>; Thu, 15 Jun 2017 11:28:11 -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=NbFYa0jSRl+ZbmR2SaZwB6mao3otcNwfmzQw1+SzVpA=; b=NVylPIZZGGP9sVKG6z3hRg5I73oTyTMcrG5Nm2JtUkQPxtgf41tq0XXt5jbAVrXtAn QK7kDm21oN4eQjbLIoTkEoHyN4N3ALPTLcKQseX4zOGwr3i195RsRk6NZAtugDq/icmE 3sJRhg43r0OFnEzT4F9QY8V1n6AfYy8iawQWtCUH9ABhQhibjlaH3HutrL5x705wjjff G9pPK5qkeupbE5bzKvekAiqSzxLq1/BpwgxoZ8CWOElByYgmuP5B/piUdl9yp+zxGIoI /ojJSUR5FF9B2jdkSDggKwOvWf6K9x5sjsUduxgflNA3kSFZ04cwkWbqgJpUu0bL2QXD W9jw==
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=NbFYa0jSRl+ZbmR2SaZwB6mao3otcNwfmzQw1+SzVpA=; b=ScITXCUPET3z5CPsdsIlTVUXRPtiOSwSHBHjGfBq+9pC0pV2VghF/zRAzMmjyRCCSG dJPd+yM9S32fTjBUMSH4GhFkWVJURTVNyiU71ZpgDLQ91tN0Gykxdx0hvDCVOPG9WbG7 SHkJ0Bo/rvMA0TaHz3flAELF3nafpkMUfbT1fAdIo3xcHYk23rUk8soHgsblOvAHYOFU Uf6DUjYVC0SZ0RVudocFmRz+jI1IZiMVUuGcz4/B5HewU2ppHgU+klSCPQv4b1Y6R3Z7 TvLSL10o/nlU5ULKEgxGqziPcyrHv3vmnDjd6GJsa4XjqEUNhXUoGAAxhjbxLvID22Xm 1nHQ==
X-Gm-Message-State: AKS2vOwOtNVR4L7ImEtX0xkUeSb+KCMWUphvIHqj20oyhve531PGCM5i yZNsU6YhXuvijQ==
X-Received: by 10.36.121.216 with SMTP id z207mr5758273itc.86.1497551290962; Thu, 15 Jun 2017 11:28:10 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by smtp.gmail.com with ESMTPSA id n103sm417016ioe.48.2017.06.15.11.28.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Jun 2017 11:28:09 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_512868B0-6536-446E-BCD3-38A987137E7C"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Date: Thu, 15 Jun 2017 11:28:08 -0700
In-Reply-To: <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: Brian Carpenter <brian.e.carpenter@gmail.com>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9rXfrLZ9N3_N5pw3gFVA0TtGDAE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jun 2017 18:28:14 -0000

--Apple-Mail=_512868B0-6536-446E-BCD3-38A987137E7C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Brian,

> On Jun 14, 2017, at 3:44 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 15/06/2017 08:20, Joel M. Halpern wrote:
> ...
>> I would be very unhappy to see us take the lesson from cases where we
>> were sloppy to be that we should tell everyone to have their
>> implementations break at the slightest error.
>=20
> Indeed. We need implementations to be as robust as possible. That
> means careful thought, both in the specification and in every
> implementation, about how to handle malformed incoming messages.
> There's no single correct answer, as I am certain Jon would have
> agreed. Some types of malformation should simply be ignored,
> because the rest of the message is valid. Others should cause the
> message to be discarded, or should cause an error response to be
> sent back, or should cause the error to be logged or reported to
> the user. There is no single correct solution.
>=20
> Clearly the Postel principle was intended as general guidance.
>=20
> Looking at the core of the draft:
>=20
>      Protocol designs and implementations should fail noisily in
>      response to bad or undefined inputs.
>=20
> that seems a very reasonable principle for *prototype* and
> *experimental* implementations, and a lousy one for production
> code, where the response to malformed messages should be much
> more nuanced; and the users will prefer the Postel principle
> as a fallback.

I agree.

It also seems to me that having implementations "fail noisily in =
response to bad or undefined inputs" is a great formula to making =
implementations very fragile and consequently very easy to attack.  =
Overall, I think the approach outlined in this draft would not have =
allowed us to build the current Internet.

Bob

p.s. The file name chosen for this draft appears to be a good example of =
stepping on the toes of those who came before, instead of standing on =
their shoulders.  See: http://wiki.c2.com/?ShouldersOfGiants



>=20
>   Brian
>=20


--Apple-Mail=_512868B0-6536-446E-BCD3-38A987137E7C
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

iQEcBAEBCgAGBQJZQtG5AAoJEK7rdBF357uoFNQH/17VWhDb0Spl2ejQY+anQITV
QurKyIr1Z1fPJ6bmJd8Igi5/Xd3DNxSgBFPOoz5b3E7ni8m0vMkheJq7ed/f3GNS
9YSRWfMLV2NsntRAM+gK2LZtW7x9zRFZpb9TxQMyddKTFCyFno7OhbThuTzwN/O2
qz//gtH95Axng7kWjnjg2eaLeIO/KQR1XikwxWaEVicRMDzIfhDYm4EzDp0DUkZQ
zmEcdkyEQeOwq9aeoYk2aMzBb28oiFk4oxQwlZvA8mXVVZcj0A6YpYlPay/v9wvX
CMhDWhkg/cQ519N8zhevhdPei9q4tWp/B1hP4iRV2hKfHHdXzYQkj8G3lHfaFv8=
=Sx3M
-----END PGP SIGNATURE-----

--Apple-Mail=_512868B0-6536-446E-BCD3-38A987137E7C--


From nobody Thu Jun 15 11:36:53 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 46E461286B1 for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 11:36:52 -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, 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 YX1zt800N9xm for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 11:36:50 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7058D1200FC for <ietf@ietf.org>; Thu, 15 Jun 2017 11:36:50 -0700 (PDT)
Received: from xsmtp02.mail2web.com ([168.144.250.215]) by mx43.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.86) (envelope-from <huitema@huitema.net>) id 1dLZdN-0006uB-DQ for ietf@ietf.org; Thu, 15 Jun 2017 20:36:48 +0200
Received: from [10.5.2.16] (helo=xmail06.myhosting.com) by xsmtp02.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1dLZcl-0004AH-RS for ietf@ietf.org; Thu, 15 Jun 2017 14:36:41 -0400
Received: (qmail 6610 invoked from network); 15 Jun 2017 18:36:06 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.228]) (envelope-sender <huitema@huitema.net>) by xmail06.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 15 Jun 2017 18:36:06 -0000
To: ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <be856ef3-7bef-244e-bf94-b0af1f1ba99b@huitema.net>
Date: Thu, 15 Jun 2017 11:35:47 -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: <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="6XJBOPWG4jq62S3mRuClMlErUFFHeChDO"
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
X-Originating-IP: 168.144.250.215
X-SpamExperts-Domain: xsmtpout.mail2web.com
X-SpamExperts-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.06)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJYWwktM+UPDyXniaU9ttNgkND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA2338jXfJKU/S9dpTf1LgVpCerb0NcNtDvNf3// WNJLl96R+SQq3snE9GARsJShr/gaYOEkjsX7F8KmpUaZQHV+SZbCEQkE+Ttak7yNVmHZUfi2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpPLwHqwRykc1ByOUA6hOga/6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGyeVlRkgtemRxeP0cdOYLTWLeNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj234Kahp30YSTh5OL3yMqjF0jNdSMuNhZC3X/nGdDKYyg+xII1yJ8udUSd8siDlV+9cBL pGLKbiMLMKI7KIsgfDrl6J1fhOzjF0b4LXcjJZ5log4vytsGSr6eWOoFoE19XxUmM9wtvvopM8mT NCUAE7SwgjVHZj0oO4qROkN2b5DxNc0yU2LI0GQUDn3k/srNlrrRG8CNIo3Sx0BJZHAPrCs7tyb7 Rrgi3wKcZ6DOEZP9h2AocVYAMa9P02RGLBmw4ypkL4BNYOol5ra+AFsZ/rzATRpUChnn7dZMk3sz 8NLrGw==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/m1XEEW93mZ4piaytTa8hON-_Qgw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jun 2017 18:36:52 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6XJBOPWG4jq62S3mRuClMlErUFFHeChDO
Content-Type: multipart/mixed; boundary="g1KDeSr7SA0Is4rrQ8x1prLr9GFrOq5rs";
 protected-headers="v1"
From: Christian Huitema <huitema@huitema.net>
To: ietf@ietf.org
Message-ID: <be856ef3-7bef-244e-bf94-b0af1f1ba99b@huitema.net>
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com>
 <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB>
 <20170613142820.GA21291@shrubbery.net>
 <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net>
 <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu>
 <20170614195604.GN89424@shrubbery.net>
 <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com>
 <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com>
 <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com>
In-Reply-To: <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com>

--g1KDeSr7SA0Is4rrQ8x1prLr9GFrOq5rs
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable



On 6/15/2017 11:28 AM, Bob Hinden wrote:
> p.s. The file name chosen for this draft appears to be a good example o=
f stepping on the toes of those who came before, instead of standing on t=
heir shoulders.  See: http://wiki.c2.com/?ShouldersOfGiants

On the other hand, there is something to be said for "being nice
considered harmful".

Martin describes a very real failure mode. Implementations deviate from
the standard, gain market share as the deviations are happily tolerated,
and then prevent standard evolution that would contradict their own
"extensions". Martin gives examples of that happening with JSON.

Or, implementations fail to properly implement the extension mechanism
specified in the standard, and then prevent deployments of perfectly
good options. The slow deployment of early congestion notification comes
to mind.

--=20
Christian Huitema



--g1KDeSr7SA0Is4rrQ8x1prLr9GFrOq5rs--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJZQtOSAAoJELba05IUOHVQVDgH/3QaE31DywhkKicebn6dP9n3
YVwcsNa0BGZzJvaQmd6W14yFzhpVq9AjNFSK7gqoh6rnnEhi6bbHe0/Puo9QuT+W
QM8EmxzUc21XGcaFoSATrV1zkl5ljTZ5WsljIZnUn5BOdIw1rWEfRSSfjP6lbNwV
YWbM5FSdbtQ98+KrdJ9RR+6fCWsZgxwBxuRAUWN/pJgRzFJfYo6SQZGAj9GbUxvv
wMTyphZRyxeUHAeXkb5DhnehFK1TvQoQnAeUwH4bb7BOxVYqKPb+RE3Sqg8RyakL
UwxCkfYVvsPF6WJKBPl1ZwZpiOwHmkSFuo53U6eqRh6oA2AMM0tQD+o34TyfoUI=
=hm/O
-----END PGP SIGNATURE-----

--6XJBOPWG4jq62S3mRuClMlErUFFHeChDO--


From nobody Thu Jun 15 13:28:22 2017
Return-Path: <prvs=2339fb6a44=jonathan@vidyo.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FFC11201F2; Thu, 15 Jun 2017 13:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.1
X-Spam-Level: 
X-Spam-Status: No, score=-1.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_WEB=1.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JxnBDmCPH2zn; Thu, 15 Jun 2017 13:28:19 -0700 (PDT)
Received: from mx0b-00198e01.pphosted.com (mx0a-00198e01.pphosted.com [67.231.149.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 186CF1287A0; Thu, 15 Jun 2017 13:28:19 -0700 (PDT)
Received: from pps.filterd (m0073109.ppops.net [127.0.0.1]) by mx0a-00198e01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v5FKOMqK032081; Thu, 15 Jun 2017 16:28:13 -0400
Received: from mail.vidyo.com (mail2.vidyo.com [162.209.16.214]) by mx0a-00198e01.pphosted.com with ESMTP id 2b09vkuxpf-1 (version=TLSv1 cipher=AES128-SHA bits=128 verify=NOT); Thu, 15 Jun 2017 16:28:12 -0400
Received: from 492132-EXCH1.vidyo.com ([fe80::50:56ff:fe85:4f77]) by 492133-EXCH2.vidyo.com ([fe80::50:56ff:fe85:6b62%13]) with mapi id 14.03.0195.001; Thu, 15 Jun 2017 15:28:11 -0500
From: Jonathan Lennox <jonathan@vidyo.com>
To: Roni Even <roni.even@huawei.com>
CC: Roni Even <ron.even.tlv@gmail.com>, "draft-ietf-avtext-lrr.all@ietf.org" <draft-ietf-avtext-lrr.all@ietf.org>, General Area Review Team <gen-art@ietf.org>, "avtext@ietf.org" <avtext@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Topic: Genart last call review of draft-ietf-avtext-lrr-05
Thread-Index: AQHS2qO4IAQ0EK1qvUeY+IF4GawhgaIYtpMAgAAtEkCAAQCzAIAFrKRwgAPKzwCAABOJgIAAXZUAgAByXACAAosVgA==
Date: Thu, 15 Jun 2017 20:28:11 +0000
Message-ID: <23DA0728-571B-4D1D-A567-6C4F3D245C03@vidyo.com>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com> <B9294064-4F4E-4FA1-A864-4F9790767B5C@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7D0641@DGGEMM506-MBX.china.huawei.com> <116D9947-414D-47EB-A0C7-8031999E5A89@vidyo.com> <01fe01d2e468$662f18e0$328d4aa0$@gmail.com> <D99B14A9-C6A4-456B-AEFA-8819B9EF6760@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7D0DE0@DGGEMM506-MBX.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD7D0DE0@DGGEMM506-MBX.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [160.79.219.114]
Content-Type: text/plain; charset="utf-8"
Content-ID: <D73F96935ED10244BFCDB18B0510D655@vidyo.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-15_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 impostorscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1703280000 definitions=main-1706150353
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j_AkvfWyXkPdoYRmdYOpAdvxpAQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 15 Jun 2017 20:28:21 -0000

DQo+IE9uIEp1biAxNCwgMjAxNywgYXQgMTozNyBBTSwgUm9uaSBFdmVuIDxyb25pLmV2ZW5AaHVh
d2VpLmNvbT4gd3JvdGU6DQo+IA0KPiBIaSBKb25hdGhhbiwNCj4gUHJvYmFibHkgIHBhcnQgb2Yg
bXkgY29tbWVudCB3YXMgYmFzZWQgb24gdGhlIGRyYWZ0IG5hbWUgLCB0aGUgbWVzc2FnZSBuYW1l
IGFuZCB0aGUgYWJzdHJhY3QgKGFsbCBhYm91dCByZWZyZXNoKS4gSSBkaWQgbm90IHNlZSBhbnkg
dGV4dCBhYm91dCB0aGUgc2FtZSB1c2FnZSBsaW1pdGF0aW9uIG9uIEZJUiBmcm9tIFJGQzUxMDQN
Cj4gIlVzaW5nIHRoZSBGSVIgY29tbWFuZCB0byByZWNvdmVyIGZyb20gZXJyb3JzIGlzIGV4cGxp
Y2l0bHkgIGRpc2FsbG93ZWQsIGFuZCBpbnN0ZWFkIHRoZSBQTEkgbWVzc2FnZSBkZWZpbmVkIGlu
IEFWUEYgW1JGQzQ1ODVdICBzaG91bGQgYmUgdXNlZC4gIFRoZSBQTEkgbWVzc2FnZSByZXBvcnRz
IGxvc3QgcGljdHVyZXMgYW5kIGhhcyBiZWVuICBpbmNsdWRlZCBpbiBBVlBGIGZvciBwcmVjaXNl
bHkgdGhhdCBwdXJwb3NlLiINCj4gDQo+IEkgYW0gT0sgd2l0aCBzaW1pbGFyIGFwcHJvYWNoIGFz
IHlvdSBzdWdnZXN0ZWQsIHNvIGRvIHlvdSBtZWFuIHRoYXQgUExJIHNob3VsZCBiZSB1c2VkIGFs
c28gaW4gdGhpcyBjYXNlIHRvIHJlY292ZXIgZnJvbSBlcnJvcnMuIA0KDQpZZXMsIGVpdGhlciBQ
TEkgaXRzZWxmIG9yIHNvbWUgZnV0dXJlIHRvLWJlLWRlZmluZWQgcGVyLWxheWVyIFBMSSBlcXVp
dmFsZW50LiAgSeKAmWxsIGFkZCBjb3JyZXNwb25kaW5nIHRleHQgZm9yIExSUi4gIFdvdWxkIHRo
YXQgc2F0aXNmeSB5b3VyIGNvbW1lbnRzPw0KDQo+IFByYWN0aWNhbGx5IGl0IHdpbGwgaW50ZXJl
c3RpbmcgIHRvIHNlZSBpZiBhcHBsaWNhdGlvbnMgYXJlIHVzaW5nIFBMSSBhbmQgbm90IEZJUiBm
b3IgcGFja2V0IGxvc3MgY2FzZXMgYW5kIHdoYXQgZW5jb2RlcnMgZG8gd2hlbiByZWNlaXZpbmcg
UExJLiAoLToNCg0KSSBzdXNwZWN0IFBMSSBhbmQgRklSIGFyZSBhY3R1YWxseSBoYW5kbGVkIGlk
ZW50aWNhbGx5IGJ5IG1vc3QgYXBwbGljYXRpb25zLCBidXQgaW4gbG93LWJpdHJhdGUgc2NlbmFy
aW9zIGl0IGxpa2VseSBtYWtlcyBzZW5zZSB0byB0cmVhdCB0aGVtIGRpZmZlcmVudGx5Lg0KDQo+
IEJUVzogZXJyb3JzIGlzIGEgZ2VuZXJhbCB0ZXJtLCBJIGFzc3VtZSB0aGF0IGZvciBGSVIgaXQg
bWVhbnQgZXJyb3JzIGR1ZSB0byBwYWNrZXQgbG9zcyAoY29uZ2VzdGlvbikNCg0KUGFja2V0IGxv
c3MgaXMgdGhlIG1vc3QgbGlrZWx5LCBidXQgcGFja2V0IGNvcnJ1cHRpb24gKGluIHRoZSBhYnNl
bmNlIG9mIFVEUCBjaGVja3N1bXMpLCBvciBlbmNvZGVyIG9yIGRlY29kZXIgYnVncywgYXJlIGFs
c28gcG9zc2libGUuDQoNCj4gUm9uaQ0KPiANCj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0t
DQo+PiBGcm9tOiBKb25hdGhhbiBMZW5ub3ggW21haWx0bzpqb25hdGhhbkB2aWR5by5jb21dDQo+
PiBTZW50OiDXmdeV150g15MgMTQg15nXldeg15kgMjAxNyAwMTo0OQ0KPj4gVG86IFJvbmkgRXZl
bg0KPj4gQ2M6IFJvbmkgRXZlbjsgZHJhZnQtaWV0Zi1hdnRleHQtbHJyLmFsbEBpZXRmLm9yZzsg
R2VuZXJhbCBBcmVhIFJldmlldyBUZWFtOw0KPj4gYXZ0ZXh0QGlldGYub3JnOyBpZXRmQGlldGYu
b3JnDQo+PiBTdWJqZWN0OiBSZTogR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0
Zi1hdnRleHQtbHJyLTA1DQo+PiANCj4+IA0KPj4+IE9uIEp1biAxMywgMjAxNywgYXQgMToxMyBQ
TSwgUm9uaSBFdmVuIDxyb24uZXZlbi50bHZAZ21haWwuY29tPiB3cm90ZToNCj4+PiANCj4+PiBI
aSBKb25hdGhhbiwNCj4+PiBUaGlzIHdpbGwgYmUgZ29vZCBidXQgbWF5YmUgZXhwbGFpbiB0aGUg
dXBncmFkZSBtZWFucyBhbHNvIHJlZnJlc2guDQo+PiBCZWNhdXNlIG15IHBvb3IgdW5kZXJzdGFu
ZGluZyBpbiBFbmdsaXNoIGlzIHRoYXQgdXBncmFkZSBpcyBhZGRpbmcgYSBuZXcNCj4+IGxheWVy
IHRoYXQgd2FzIG5vdCBhdmFpbGFibGUgdG8gdGhlIG1lZGlhIHJlY2VpdmVyIHdoaWxlIHJlZnJl
c2ggaXMgdG8gcmVzdG9yZQ0KPj4gZXhpc3RpbmcgbGF5ZXIgKGUuZy4gZGVjb2RlciBzeW5jaHJv
bml6YXRpb24gbG9zcykuDQo+Pj4gUm9uaQ0KPj4gDQo+PiBBaCwgSSBzZWUuDQo+PiANCj4+IFRo
ZSBkZXNpZ24gZ29hbCBvZiBMUlIgd2FzIGZvciBpdCB0byBiZSB1c2VkIGZvciB1cGdyYWRlLCBu
b3QgZm9yDQo+PiBzeW5jaHJvbml6YXRpb24gbG9zcywgdGhvdWdoIG9mIGNvdXJzZSBub3cgdGhh
dCB5b3UgbWVudGlvbiBpdCwgaXQgY291bGQNCj4+IGNlcnRhaW5seSBiZSB1c2VkIGZvciB0aGUg
bGF0dGVyIGFzIHdlbGwuIChJLmUuIGl0IHdhcyBkZXNpZ25lZCB0byBiZSBhbmFsb2dvdXMNCj4+
IHRvIEZJUiwgbm90IHRvIFBMSS4pDQo+PiANCj4+IEFzIHdpdGggdGhlIGRpZmZlcmVuY2UgYmV0
d2VlbiBGSVIgYW5kIFBMSSwgdGhlIGNvbmdlc3Rpb24gY29uc2lkZXJhdGlvbnMNCj4+IGFyZSBz
b21ld2hhdCBkaWZmZXJlbnQgYmV0d2VlbiB1cGdyYWRlIGFuZCBzeW5jaHJvbml6YXRpb24gbG9z
cy4gIERvIHlvdQ0KPj4gdGhpbmsgaXQncyB3b3J0aCBhZGRyZXNzaW5nIHRoZSBzeW5jaHJvbml6
YXRpb24gbG9zcyBjYXNlcyBleHBsaWNpdGx5Pw0KPj4gDQo+Pj4gDQo+Pj4+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+Pj4+IEZyb206IEpvbmF0aGFuIExlbm5veCBbbWFpbHRvOmpvbmF0
aGFuQHZpZHlvLmNvbV0NCj4+Pj4gU2VudDogVHVlc2RheSwgSnVuZSAxMywgMjAxNyA3OjAzIFBN
DQo+Pj4+IFRvOiBSb25pIEV2ZW4NCj4+Pj4gQ2M6IFJvbmkgRXZlbjsgZHJhZnQtaWV0Zi1hdnRl
eHQtbHJyLmFsbEBpZXRmLm9yZzsgR2VuZXJhbCBBcmVhDQo+Pj4+IFJldmlldyBUZWFtOyBhdnRl
eHRAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNCj4+Pj4gU3ViamVjdDogUmU6IEdlbmFydCBsYXN0
IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci0wNQ0KPj4+PiANCj4+Pj4gSGks
IFJvbmkg4oCUDQo+Pj4+IA0KPj4+PiBZb3Ugc2VlbSB0byBiZSBhc3N1bWluZyB0aGF0IGEgcmVm
cmVzaCBhbmQgYW4gdXBncmFkZSBhcmUgdHdvDQo+Pj4+IGRpZmZlcmVudCBhY3Rpb25zLiAgVGhh
dOKAmXMgbm90IHRoZSBpbnRlbnRpb24g4oCUIGEgcmVmcmVzaCBpcyBhDQo+Pj4+IGNoYXJhY3Rl
cmlzdGljIG9mIGEgc3RyZWFtIHRoYXQgYWxsb3dzIGEgZGVjb2RlciB0byB1cGdyYWRlLg0KPj4+
PiANCj4+Pj4gSeKAmWxsIHRyeSB0byBkcmFmdCBzb21lIHRleHQgdGhhdCBtYWtlcyBpdCBjbGVh
ciB0aGF0IGl04oCZcyBwb3NzaWJsZQ0KPj4+PiBlaXRoZXIgdG8gaW5kZXBlbmRlbnRseSB1cGdy
YWRlIHRlbXBvcmFsIG9yIHNwYXRpYWwsIG9yIGVsc2UgdXBncmFkZSBib3RoDQo+PiBhdCBvbmNl
Lg0KPj4+PiANCj4+Pj4+IE9uIEp1biAxMSwgMjAxNywgYXQgNzoyMCBBTSwgUm9uaSBFdmVuIDxy
b25pLmV2ZW5AaHVhd2VpLmNvbT4gd3JvdGU6DQo+Pj4+PiANCj4+Pj4+IEhpIEpvbmF0aGFuLA0K
Pj4+Pj4gSSBhc3N1bWUgdGhlIG5ldyB0ZXh0IHlvdSBwcm9wb3NlIGlzDQo+Pj4+PiANCj4+Pj4+
ICJXaGVuIEMgaXMgMSwgVFRJRCBNVVNUIE5PVCBiZSBsZXNzIHRoYW4gQ1RJRCwgYW5kIFRMSUQg
TVVTVCBOT1QgYmUNCj4+Pj4+IGxlc3MgdGhhbiBDTElEOyBhdCBsZWFzdCBvbmUgb2YgVFRJRCBv
ciBUTElEIE1VU1QgYmUgZ3JlYXRlciB0aGFuDQo+Pj4+PiBDVElEIG9yIENMSUQgcmVzcGVjdGl2
ZWx5LiAgVGhhdCBpcyB0byBzYXksIHRoZSB0YXJnZXQgbGF5ZXIgaW5kZXgNCj4+Pj4+IDxUVElE
LCBUTElEPiBNVVNUIGJlIGEgbGF5ZXIgdXBncmFkZSBmcm9tIHRoZSBjdXJyZW50IGxheWVyIGlu
ZGV4DQo+Pj4+PiA8Q1RJRCwgQ0xJRD4uICBBIHNlbmRlciBNQVkgcmVxdWVzdCBhbiB1cGdyYWRl
IGluIGJvdGggdGVtcG9yYWwgYW5kDQo+Pj4+PiBzcGF0aWFsL3F1YWxpdHkgbGF5ZXJzIHNpbXVs
dGFuZW91c2x5LiINCj4+Pj4+IA0KPj4+Pj4gSSB0aGluayB0aGF0IHRoaXMgdGV4dCBzdGlsbCBv
bmx5IGltcGxpZXMgdGhlIGJlaGF2aW9yLCBhbHNvIHRoZQ0KPj4+Pj4gY3VycmVudCB0ZXh0IHRh
bGtzIGFib3V0IHVwZ3JhZGUgYnV0IEkgYXNzdW1lIGl0IGlzIGFsc28gZm9yIGENCj4+Pj4+IHJl
ZnJlc2ggbm90IG9ubHkgdG8gdXBncmFkZQ0KPj4+Pj4gDQo+Pj4+PiBNYXliZSAiIEEgc2VuZGVy
IE1BWSByZXF1ZXN0IGFuIHVwZ3JhZGUgb3IgcmVmcmVzaCAgaW4gYm90aCB0ZW1wb3JhbA0KPj4+
Pj4gYW5kICBzcGF0aWFsL3F1YWxpdHkgbGF5ZXJzIHNpbXVsdGFuZW91c2x5IGJ5IGVpdGhlciBo
YXZpbmcgQyA9MSBvcg0KPj4+Pj4gYnkgaGF2aW5nIGJvdGgNCj4+Pj4gQ0xJRCBhbmQgQ1RJRCB3
aXRoIGxvd2VyIHZhbHVlcyB0aGVuIFRUSUQgYW5kIFRMSUQuIElmIHRoZSBzZW5kZXINCj4+Pj4g
d2FudCB0byB1cGdyYWRlIG9yIHJlZnJlc2ggb25seSBvbmUgbGF5ZXIgdGhlbiBDIE1VU1QgYmUg
ZXF1YWwgdG8gMQ0KPj4+PiBhbmQgb25seSB0aGUgQ1RJRCBvciAgdGhlIENMSUQgb2YgdGhlIGxh
eWVyIHRvIGJlIHVwZ3JhZGVkIG9yDQo+Pj4+IHJlZnJlc2hlZCBzaG91bGQgYmUgbG93ZXIgdGhh
biB0aGUgVFRJRCBvciBUTElEIHJlc3BlY3RpdmVseSAiDQo+Pj4+PiANCj4+Pj4+IA0KPj4+Pj4g
Um9uaQ0KPj4+Pj4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+Pj4+Pj4gRnJvbTogSm9u
YXRoYW4gTGVubm94IFttYWlsdG86am9uYXRoYW5AdmlkeW8uY29tXQ0KPj4+Pj4+IFNlbnQ6INeZ
15XXnSDXkyAwNyDXmdeV16DXmSAyMDE3IDE4OjMwDQo+Pj4+Pj4gVG86IFJvbmkgRXZlbg0KPj4+
Pj4+IENjOiBSb25pIEV2ZW47IGRyYWZ0LWlldGYtYXZ0ZXh0LWxyci5hbGxAaWV0Zi5vcmc7IEdl
bmVyYWwgQXJlYQ0KPj4+Pj4+IFJldmlldyBUZWFtOyBhdnRleHRAaWV0Zi5vcmc7IGlldGZAaWV0
Zi5vcmcNCj4+Pj4+PiBTdWJqZWN0OiBSZTogR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJh
ZnQtaWV0Zi1hdnRleHQtbHJyLTA1DQo+Pj4+Pj4gDQo+Pj4+Pj4gDQo+Pj4+Pj4+IE9uIEp1biA3
LCAyMDE3LCBhdCAxOjE1IEFNLCBSb25pIEV2ZW4gPHJvbmkuZXZlbkBodWF3ZWkuY29tPg0KPj4g
d3JvdGU6DQo+Pj4+Pj4+IA0KPj4+Pj4+PiBIaSBKb25hdGhhbiwNCj4+Pj4+Pj4gSSBkaWQgbm90
IHNlZSB0aGUgdGV4dCB5b3UgYWRkZWQgeWV0IGFzIGEgcmVzcG9uc2UgdG8gbXkgZmlyc3QNCj4+
Pj4+Pj4gcXVlc3Rpb24gU28gdG8gYmV0dGVyIGNsYXJpZnkgbXkgcXVlc3Rpb24gLiBJZiB0aGUg
RkNJIGhhcyBUVElEPTANCj4+Pj4+Pj4gYW5kIFRMSUQ9Mg0KPj4+PiAuDQo+Pj4+Pj4gZG9lcyBp
dCBtZWFuIHRoYXQgaXQgaXMgYSByZXF1ZXN0IHRvIHVwZGF0ZSBib3RoPw0KPj4+Pj4+PiBUaGlz
IHdhcyBhbHNvIHRoZSByZWFzb24gZm9yIHRoZSBxdWVzdGlvbiBhYm91dCBib3RoIFRUSUQ9MCBh
bmQNCj4+Pj4+Pj4gVExJRD0wLA0KPj4+Pj4+IHdoaWNoIGxheWVyIG5lZWQgdXBkYXRlIG9yIGlz
IGl0IGJvdGg/DQo+Pj4+Pj4+IENhbiB5b3Ugc2F5IHRoYXQgeW91IHdhbnQganVzdCB0byB1cGRh
dGUgdGVtcG9yYWwgb3Igc3BhdGlhbD8NCj4+Pj4+PiANCj4+Pj4+PiBZZXMsIGlmIHRoZSBGQ0kg
aGFzIFRUSUQ9MCBhbmQgVExJRD0yLCBpdOKAmXMgYSByZXF1ZXN0IHRvIHVwZGF0ZQ0KPj4+Pj4+
IGJvdGggbGF5ZXJzIOKAlCBvciBtb3JlIHNwZWNpZmljYWxseSwgdG8gbWFrZSBzdXJlIHRoYXQg
eW91IGNhbiBzdGFydA0KPj4+Pj4+IGRlY29kaW5nIHRoZSBzdWJzdHJlYW0gd2l0aCBUVElEPTAg
YW5kIFRMSUQ9Mi4gKEZvciBtb3N0DQo+Pj4+Pj4gc2NhbGFiaWxpdHkgc3RydWN0dXJlcyB0aGlz
IHdvdWxkIG1lYW4gdXBkYXRpbmcgYm90aCwgYnV0IGV4b3RpYw0KPj4+Pj4+IHN0cnVjdHVyZXMg
YXJlDQo+Pj4+Pj4gcG9zc2libGUuKQ0KPj4+Pj4+IA0KPj4+Pj4+IElmIHlvdSB3YW50IHRvIGp1
c3QgdXBkYXRlIG9uZSBwYXJ0IG9mIHRoZSBzdHJlYW0sIHRoYXTigJlzIHdoYXQgQ1RJRA0KPj4+
Pj4+IGFuZCBDTElEIGFyZSBmb3IuICBJZiB5b3Ugc2VudCBUVElEPTAgYW5kIFRMSUQ9MiwgYWNj
b21wYW5pZWQgYnkNCj4+Pj4+PiBDVElEPTAgYW5kIENMSUQ9MCwgdGhhdCBtZWFucyB0aGF0IHlv
dSBhbHJlYWR5IGhhdmUgVElEIDAsIGFuZCB5b3UNCj4+Pj4+PiBqdXN0IHdhbnQgdG8gaW5jcmVh
c2UgdGhlIExJRC4NCj4+Pj4+PiANCj4+Pj4+PiBUaGUgY3VycmVudCB0ZXh0IGlzIGF0DQo+Pj4+
Pj4gaHR0cHM6Ly9naXRodWIuY29tL2p1YmVydGkvZHJhdWdodHMvdHJlZS9tYXN0ZXIvbHJyICwg
aWYgeW91IHdhbnQNCj4+Pj4+PiB0byB0YWtlIGEgbG9vayBhdCB0aGUgbGF0ZXN0IHJldmlzaW9u
cywgb3Igc3VnZ2VzdCB0ZXh0IHRoYXQgeW91DQo+Pj4+Pj4gdGhpbmsgd291bGQgbWFrZQ0KPj4+
PiBpdCBjbGVhbmVyLg0KPj4+Pj4+IA0KPj4+Pj4+IA0KPj4+Pj4+PiBSb25pDQo+Pj4+Pj4+IA0K
Pj4+Pj4+Pj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4+Pj4+Pj4+IEZyb206IEdlbi1h
cnQgW21haWx0bzpnZW4tYXJ0LWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZg0KPj4+Pj4+
Pj4gSm9uYXRoYW4gTGVubm94DQo+Pj4+Pj4+PiBTZW50OiDXmdeV150g15MgMDcg15nXldeg15kg
MjAxNyAwMDozMA0KPj4+Pj4+Pj4gVG86IFJvbmkgRXZlbg0KPj4+Pj4+Pj4gQ2M6IGRyYWZ0LWll
dGYtYXZ0ZXh0LWxyci5hbGxAaWV0Zi5vcmc7IEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbTsNCj4+
Pj4+Pj4+IGF2dGV4dEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZw0KPj4+Pj4+Pj4gU3ViamVjdDog
UmU6IFtHZW4tYXJ0XSBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZg0KPj4+Pj4+Pj4gZHJhZnQt
aWV0Zi1hdnRleHQtbHJyLTA1DQo+Pj4+Pj4+PiANCj4+Pj4+Pj4+IEhpLCBSb25pIOKAlCB0aGFu
a3MgZm9yIHlvdXIgcmV2aWV3LiAgUmVzcG9uc2VzIGlubGluZS4NCj4+Pj4+Pj4+IA0KPj4+Pj4+
Pj4+IE9uIEp1biAxLCAyMDE3LCBhdCAyOjUzIEFNLCBSb25pIEV2ZW4gPHJvbi5ldmVuLnRsdkBn
bWFpbC5jb20+DQo+Pj4+IHdyb3RlOg0KPj4+Pj4+Pj4+IA0KPj4+Pj4+Pj4+IFJldmlld2VyOiBS
b25pIEV2ZW4NCj4+Pj4+Pj4+PiBSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KPj4+
Pj4+Pj4+IA0KPj4+Pj4+Pj4+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9y
IHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsDQo+Pj4+Pj4+Pj4gQXJlYSBSZXZpZXcgVGVhbSAoR2Vu
LUFSVCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcNCj4+Pj4+Pj4+PiBwcm9jZXNz
ZWQgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlDQo+
Pj4+Pj4+Pj4gY29tbWVudHMganVzdCBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMu
DQo+Pj4+Pj4+Pj4gDQo+Pj4+Pj4+Pj4gRm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBzZWUg
dGhlIEZBUSBhdA0KPj4+Pj4+Pj4+IA0KPj4+Pj4+Pj4+IDxodHRwczovL3RyYWMuaWV0Zi5vcmcv
dHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KPj4+Pj4+Pj4+IA0KPj4+Pj4+Pj4+IERvY3VtZW50
OiBkcmFmdC1pZXRmLWF2dGV4dC1scnItPz8NCj4+Pj4+Pj4+PiBSZXZpZXdlcjogUm9uaSBFdmVu
DQo+Pj4+Pj4+Pj4gUmV2aWV3IERhdGU6IDIwMTctMDUtMzENCj4+Pj4+Pj4+PiBJRVRGIExDIEVu
ZCBEYXRlOiAyMDE3LTA2LTA4DQo+Pj4+Pj4+Pj4gSUVTRyBUZWxlY2hhdCBkYXRlOiBOb3Qgc2No
ZWR1bGVkIGZvciBhIHRlbGVjaGF0DQo+Pj4+Pj4+Pj4gDQo+Pj4+Pj4+Pj4gU3VtbWFyeToNCj4+
Pj4+Pj4+PiBUaGUgZG9jdW1lbnQgaXMgcmVhZHkgd2l0aCBpc3N1ZXMgZm9yIGEgc3RhbmRhcmQg
dHJhY2sgUkZDIE1ham9yDQo+Pj4+Pj4+Pj4gaXNzdWVzOg0KPj4+Pj4+Pj4+IA0KPj4+Pj4+Pj4+
IE1pbm9yIGlzc3VlczoNCj4+Pj4+Pj4+PiANCj4+Pj4+Pj4+PiAxLiBDYW4geW91IHNwZWNpZnkg
Ym90aCBUVElEIGFuZCBUTElEIGluIHRoZSBzYW1lIEZDSS4NCj4+Pj4+Pj4+IA0KPj4+Pj4+Pj4g
U3ludGFjdGljYWxseSwgdGhleSBtdXN0IGJvdGggb2NjdXIuDQo+Pj4+Pj4+PiANCj4+Pj4+Pj4+
IElmIHlvdSBtZWFuIGNhbiB5b3UgcmVxdWVzdCBhbiB1cGdyYWRlIGluIGJvdGggYXQgb25jZSwg
eWVzOyBJ4oCZdmUNCj4+Pj4+Pj4+IGFkZGVkIHRleHQgdG8gY2xhcmlmeSB0aGlzLg0KPj4+Pj4+
Pj4gDQo+Pj4+Pj4+Pj4gMi4gV2hhdCBpcyB0aGUgbWVhbmluZyBvZiB2YWx1ZSAwIGZvciBUVElE
IGFuZCBUTElEIC0gVElEIG9yIExJRA0KPj4+Pj4+Pj4+ID0wIGluIGZyYW1lIG1hcmtpbmcgZHJh
ZnQgbWVhbnMgYmFzZSBsYXllciBpZiB0aGVyZSBpcyBzY2FsYWJpbGl0eS4NCj4+Pj4+Pj4+PiBU
aGlzIHJlbGF0ZXMgdG8gdGhlIHByZXZpb3VzIHF1ZXN0aW9uLg0KPj4+Pj4+Pj4gDQo+Pj4+Pj4+
PiBJ4oCZbSBub3Qgc3VyZSBJIHVuZGVyc3RhbmQgdGhpcyBxdWVzdGlvbi4NCj4+Pj4+Pj4+IA0K
Pj4+Pj4+Pj4gSeKAmXZlIGFkZGVkIHRleHQgdGhhdCBpZiBDPTEsIGF0IGxlYXN0IG9uZSBvZiA8
VFRJRCwgVExJRD4gTVVTVCBiZQ0KPj4+Pj4+Pj4gZ3JlYXRlciB0aGFuIDxDVElELCBDTElEPiwg
YW5kIGJvdGggTVVTVCBiZSBncmVhdGVyIHRoYW4gb3IgZXF1YWwNCj4+Pj4+Pj4+IHRvIHRoZWly
IGNvdW50ZXJwYXJ0LCBzbyB0aGUgTFJSIGlzIGFjdHVhbGx5IHJlcXVlc3RpbmcgYSBsYXllcg0K
Pj4gdXBncmFkZS4NCj4+Pj4+Pj4+IElzIHRoYXQgd2hhdCB5b3Ugd2VyZSBhc2tpbmcgYWJvdXQ/
DQo+Pj4+Pj4+PiANCj4+Pj4+Pj4+PiAzLiAgV2hhdCB3b3VsZCBhbiBGQ0kgd2l0aCBib3RoIFRU
SUQgYW5kIFRMSUQgZXF1YWwgMCBtZWFuLg0KPj4+Pj4+Pj4gDQo+Pj4+Pj4+PiBJdCBtZWFucyB5
b3Ugd2FudCBhIHJlZnJlc2ggb2YgdGhlIGJhc2UgdGVtcG9yYWwvc3BhdGlhbCBsYXllciwgb25s
eS4NCj4+Pj4+Pj4+IA0KPj4+Pj4+Pj4+IE5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KPj4+Pj4+
Pj4+IA0KPj4+Pj4+Pj4+IDEuIFNlY3Rpb24gMyAiYW4gUmVhbC1UaW1lIFRyYW5zcG9ydCBDb250
cm9sIFByb3RvY29sIiBzaG91bGQgYmUNCj4+Pj4+Pj4+PiAiYSBSZWFs4oCmIi4NCj4+Pj4+Pj4+
IA0KPj4+Pj4+Pj4gQ29saW4gcG9pbnRlZCBvdXQgdGhhdCBpdCBzaG91bGQgc2F5IOKAnGFuIFJU
UCBDb250cm9sIFByb3RvY29s4oCdDQo+PiBhbnl3YXkuDQo+Pj4+Pj4+PiANCj4+Pj4+Pj4+PiAy
LiBJbiBzZWN0aW9uIDMgIiBbUkZDNTEwNF0oU2VjdGlvbiAzLjUuMSkiIHRoZXJlIGlzIGEgbGlu
ayB0bw0KPj4+Pj4+Pj4+IHNlY3Rpb24NCj4+Pj4+Pj4+PiAzLjUuMSBidXQgaXQgZG9lcyBub3Qg
d29yay4NCj4+Pj4+Pj4+IA0KPj4+Pj4+Pj4geG1sMnJmYyBkb2VzbuKAmXQgaGF2ZSBhbnkgd2F5
IHRvIGxpbmsgdG8gc2VjdGlvbnMgb2Ygb3RoZXINCj4+Pj4+Pj4+IGRvY3VtZW50cywgc28gdGhl
IOKAnChTZWN0aW9uIDMuNS4xKeKAnSBwYXJ0IGlzIGp1c3QgYSBjb21tZW50Lg0KPj4+Pj4+Pj4g
DQo+Pj4+Pj4+PiBJIHRoaW5rIHRoZSBpbnRlcm5ldC1kcmFmdCB0b29saW5nIG1heSBoYXZlIHRo
b3VnaHQgSSB3YXMgdHJ5aW5nDQo+Pj4+Pj4+PiB0byBsaW5rIHRvIGEgbm9uLWV4aXN0ZW50IHNl
Y3Rpb24gMy41LjEgb2YgdGhpcyBkb2N1bWVudCwgYnV0DQo+Pj4+Pj4+PiB0aGF04oCZcyBvdXRz
aWRlDQo+Pj4+Pj4gbXkgY29udHJvbC4NCj4+Pj4+Pj4+IA0KPj4+Pj4+Pj4+IDMuIEluIHNlY3Rp
b24gMy4yICIoc2VlIHNlY3Rpb24gU2VjdGlvbiAyLjEpIiBzZWN0aW9uIGFwcGVhcnMgdHdpY2Uu
DQo+Pj4+Pj4+PiANCj4+Pj4+Pj4+IEZpeGVkLg0KPj4+Pj4+Pj4gX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4+Pj4+Pj4+IEdlbi1hcnQgbWFpbGluZyBs
aXN0DQo+Pj4+Pj4+PiBHZW4tYXJ0QGlldGYub3JnDQo+Pj4+Pj4+PiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dlbi1hcnQNCj4+Pj4+IA0KPj4+IA0KPj4+IA0KPiANCg0K


From nobody Thu Jun 15 18:07:17 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 8B9C312EB10 for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 18:07:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lBSpR7uOFAZ4 for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 18:07:13 -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 428ED1205F1 for <ietf@ietf.org>; Thu, 15 Jun 2017 18:07:13 -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 5436724AE14; Fri, 16 Jun 2017 01:07:04 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTPS id 1AD91160069; Fri, 16 Jun 2017 01:07:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 0758C16007A; Fri, 16 Jun 2017 01:07:07 +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 hxLXCiVUUT_c; Fri, 16 Jun 2017 01:07:06 +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 AE66E160069; Fri, 16 Jun 2017 01:07:06 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 8BECA7BC86B4; Fri, 16 Jun 2017 11:07:04 +1000 (AEST)
To: Christian Huitema <huitema@huitema.net>
Cc: ietf@ietf.org
From: Mark Andrews <marka@isc.org>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com> <be856ef3-7bef-244e-bf94-b0af1f1ba99b@huitema.net>
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
In-reply-to: Your message of "Thu, 15 Jun 2017 11:35:47 -0700." <be856ef3-7bef-244e-bf94-b0af1f1ba99b@huitema.net>
Date: Fri, 16 Jun 2017 11:07:04 +1000
Message-Id: <20170616010704.8BECA7BC86B4@rock.dv.isc.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CdS9BGFIvQ1lRrslc4vfaYrLnQs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jun 2017 01:07:16 -0000

In message <be856ef3-7bef-244e-bf94-b0af1f1ba99b@huitema.net>, Christian Huitema writes:
> This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
> On 6/15/2017 11:28 AM, Bob Hinden wrote:
> > p.s. The file name chosen for this draft appears to be a good example
> > of stepping on the toes of those who came before, instead of standing on
> > their shoulders.  See: http://wiki.c2.com/?ShouldersOfGiants
>
> On the other hand, there is something to be said for "being nice
> considered harmful".
>
> Martin describes a very real failure mode. Implementations deviate from
> the standard, gain market share as the deviations are happily tolerated,
> and then prevent standard evolution that would contradict their own
> "extensions". Martin gives examples of that happening with JSON.
>
> Or, implementations fail to properly implement the extension mechanism
> specified in the standard, and then prevent deployments of perfectly
> good options. The slow deployment of early congestion notification comes
> to mind.

DNS and EDNS fall into this category.  The AD bit in responses can't
be trusted as there are servers that just echo back (formally)
reserved bits.  STD 13 says these bits MUST be zero.

Then there are all the servers that fail to do EDNS version negotiation
correctly.  They talk EDNS but ignore the version field or return
FORMERR rather than the specified BADVERS error code. etc.  About
half the servers we have tested get EDNS version negotiation wrong
in one way or another.

When we tighted the unknown EDNS option behaviour (RFC 6891, RFC
2671 under specified the behaviour) updating the EDNS version field
would have been appropriate but we couldn't do this due to the level
of poor implementation of EDNS version negotiation and idiotic (yes,
name calling is appropriate) default firewall rules from multiple
vendors that dropped any EDNS request with a version field that
wasn't 0.

Mark
> --
> Christian Huitema

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


From nobody Thu Jun 15 18:45:14 2017
Return-Path: <shares@ndzh.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C87A8128B91; Thu, 15 Jun 2017 18:45:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.945
X-Spam-Level: 
X-Spam-Status: No, score=0.945 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NznLSlYVxRF3; Thu, 15 Jun 2017 18:44:58 -0700 (PDT)
Received: from hickoryhill-consulting.com (50-245-122-97-static.hfc.comcastbusiness.net [50.245.122.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E62831205D3; Thu, 15 Jun 2017 18:44:54 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=174.124.176.217; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Magnus Westerlund'" <magnus.westerlund@ericsson.com>, <tsv-art@ietf.org>
Cc: <trill@ietf.org>, <ietf@ietf.org>, <draft-ietf-trill-over-ip.all@ietf.org>, "'Alia Atlas'" <akatlas@gmail.com>, "'Jon Hudson'" <jon.hudson@gmail.com>
References: <149754795560.13109.17521244075940607817@ietfa.amsl.com>
In-Reply-To: <149754795560.13109.17521244075940607817@ietfa.amsl.com>
Subject: RE: Tsvart early review of draft-ietf-trill-over-ip-10
Date: Thu, 15 Jun 2017 21:39:10 -0400
Message-ID: <00a301d2e641$5a6cfb00$0f46f100$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHMe5Py4K7gCbNISswrkrRWdm5LSqIziw8g
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Er-xj91dtnWqRWOUyXFeoC_DMkI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jun 2017 01:45:01 -0000

Magnus:=20

Thank you for the very careful review.  Please let me chat with the =
authors regarding this document.  It make take some time, but each of =
your points will be responded to by the authors.=20

Sue Hares=20

-----Original Message-----
From: Magnus Westerlund [mailto:magnus.westerlund@ericsson.com]=20
Sent: Thursday, June 15, 2017 1:33 PM
To: tsv-art@ietf.org
Cc: trill@ietf.org; ietf@ietf.org; draft-ietf-trill-over-ip.all@ietf.org
Subject: Tsvart early review of draft-ietf-trill-over-ip-10

Reviewer: Magnus Westerlund
Review result: Not Ready

Early review of draft-ietf-trill-over-ip-10
Reviewer: Magnus Westerlund
Review result: Not Ready

TSV-ART review comments:

I have set this to not ready as there are several issues, some =
significant that could affect the protocol realization significantly. =
Some may be me missing things in TRILL, I was not that familiar with it =
before this review and I have only tried looking up things, not reading =
the whole earlier specifications. So don't hesitate to push back and =
provide pointers to things that can resolve issues. The authors and the =
WG clearly have thought about a lot of issues and dealt with much =
already.

Diffserv usage
--------------

Section 4.3:

   TRILL over IP implementations MUST support setting the DSCP value in
   the outer IP Header of TRILL packets they send by mapping the TRILL
   priority and DEI to the DSCP. They MAY support, for a TRILL Data
   packet where the native frame payload is an IP packet, mapping the
   DSCP in this inner IP packet to the outer IP Header with the default
   for that mapping being to copy the DSCP without change.

I think it is fine to require that implementations are capable  of =
setting DSCP values on the outer IP header. However, I fail to see any =
discussion of the potential issues with actually setting the DSCP =
values. It is one thing to do this in an IP back bone use case where one =
can know and have control over the PHB that the DSCP values maps to. But =
otherwise, over general internet the behavior is not that predictable. =
One can easily be subject to policers or remapping. Also as the actual =
DSCP code point usage is domain specific this is difficult. Priority =
reversal is likely the least of the problems that this can run into over =
general Internet.

Section 4.3:

   The default TRILL priority and DEI to DSCP mapping, which may be
   configured per TRILL over IP port, is an follows. Note that the DEI
   value does not affect the default mapping and, to provide a
   potentially lower priority service than the default priority 0,
   priority 1 is considered lower priority than 0. So the priority
   sequence from lower to higher priority is 1, 0, 2, 3, 4, 5, 6, 7.

      TRILL Priority  DEI  DSCP Field (Binary/decimal)
      --------------  ---  -----------------------------
                  0   0/1  001000 / 8
                  1   0/1  000000 / 0
                  2   0/1  010000 / 16
                  3   0/1  011000 / 24
                  4   0/1  100000 / 32
                  5   0/1  101000 / 40
                  6   0/1  110000 / 48
                  7   0/1  111000 / 56

This appear to be an problematic mapping. At least for prio 0 and 1. As =
priority 1 appears to be intended to be higher than priority 0, it is =
interesting that it is mapped to CS1, which to quote
https://datatracker.ietf.org/doc/rfc7657/:

CS1 ('001000') was subsequently designated as the recommended
      codepoint for the Lower Effort (LE) PHB [RFC3662].

So what is proposed can in a network using default mapping, result in =
that you get priority 0 to be lower priority than 1. Plus that in some =
networks this can also results in strange remapping that results in a =
different PHB for CS1 than.

MTU and Fragmentation
---------------------

I think there are two main issue here. The first one is MTUD discovery =
of the actual IP path MTU between the ports. That will be needed to =
prevent a lot of traffic going into MTU black holes. Especially as TRILL =
requries
1470 byte support which is likey above a lot of paths.

Section 8.4:

   Path MTU discovery [RFC4821] should be useful
   in determining the IP MTU between a pair of RBridge ports with IP
   connectivity.

The issue with RFC4821 is that it has requirements on the packetization =
layer.
Trill appears to have several components that are useful. However, it =
will require a specification of the procedure to result in a useful =
tool.

Section 8.4:

   TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
   [RFC7177], can be used to obtain added assurance of the MTU of a
   link.

Yes, that can confirm working MTUs that are at 1470 or above, but =
appears prevented from working below 1470?

Thus, it appears that there is a lack of mechanism here to actually get =
a valid and functional MTU from TRILL in the cases where the Path MTU is =
below 1470. If I am wrong good, but I think this is an important piece =
for how to handle the next main issue.

UDP encapsulation and IP fragments.
I see it as a big issue that UDP encapsulation is the native one, and =
that relies on IP fragmentation despite the need for reliable =
fragmentation. With the setup of having to support 1470 MTU on TRILL =
level some packets will be fragmented in many environments. That will =
lead to a lot of losses, and as discussed below a very big problem with =
middleboxes. The main problem here is that if one tries to rely on IP =
fragments one will have issues with packets ending up in black holes. =
And different problems depending on IPv4 or IPv6.
IPv6 is lilkely the lesser problem assuming that one have working PMTUD.

There are several ways out of this.

1. Detect issues and use TCP encapsulation with correctly set MSS to not =
get IP fragements 2. Determine MTU and implement an fragmentation =
mechanism on top of UDP.

Zero Checksum:
--------------

Section 5.4:

UDP Checksum - as specified in [RFC0768]

Considering the fast path encapsulation desire, I am surprised to not =
see any mentioning of use of zero checksum here. Raising the zero =
checksum and forward reference would be good I think.

And then Section 8.5:

   The requirements for the usage of the zero UDP Checksum in a UDP
   tunnel protocol are detailed in [RFC6936]. These requirements apply
   to the UDP based TRILL over IP encapsulations specified herein
   (native and VXLAN), which are applications of UDP tunnel.

If you actually intended to allow zero checksum, then you actually =
should document that Trill fulfills the requirements that the =
applicability statement raises. I have not analyzed how well it meets =
these requirements.

Please review Section 6.2 of RFC 8086 for example how that can be done.

TCP Encapsulation issue
-----------------------

Section 5.6:

The TCP encapsulation appear to be missing an delimiter format allowing =
each individual TRILL packet/payload to be read out of the TCP's byte =
stream. In other words, a normal implementation has no way of ensuring =
that the TCP payload starts with the start of a new TRILL payload. =
Multiple small TRILL payloads may be included in the same TCP payload, =
and also only parts as TCP is one way of dealing with TRILL packets that =
are larger than the IP+Encapsulation MTU that actually will work.

This comment is based on that there appear to be no length fields =
included in the TRILL header. The most straight forward delimiter is a =
2-byte length field for the TRILL payload to be encapsulated.

Section 5.6:

TCP endpoint requirements. I do wonder if an application like TRILL =
actual would need to discuss performance impacting implementation =
choices or limitations. For example use of NAGLE, the requirements on =
buffer sizes in relation to Bandwidth delay products, as buffer memory =
in a RBridge will impact performance.

Congestion Control
------------------
First thanks for the effort here.

8.1.2 In Other Environments

   Where UDP based encapsulation headers are used in TRILL over IP in
   environments other than those discussed in Section 8.1.1, specific
   congestion control mechanisms are commonly needed.  However, if the
   traffic being carried by the TRILL over IP link is already congestion
   controlled and the size and volatility of the TRILL IS-IS link state
   database is limited, then specific congestion control may not be
   needed. See [RFC8085] Section 3.1.11 for further guidance.

This is correct, however my question is if the RBridges have anyway of =
knowing which traffic is actually congestion controlled, considering =
that TRILL provides an layer 2 abstraction. I wonder if there should be =
any type of white list of the types of layer 2 payloads that can be =
assumed to be congestion controlled, and thus okay to forward over IP =
paths? I am worried that without any recommendation to prevent traffic =
that is not controlled to be forwarded, can lead to congestion issues.

The other issue I think may exist is the issue serial unicast emulation =
of broadcast/multicast creates. As this amplifies the outgoing packet =
rate with a factor of how many addresses are configured for serial =
unicast this can be significant traffic expansion. Thus, I think =
additional considerations are needed here, and maybe rate limiting of =
the amount of traffic to be multicasted.

Flow and ECMP
-------------

Section 8.3:

For example, for TRILL
   Data, this entropy field could be based on some hash of the
   Inner.MacDA, Inner.MacSA, and Inner.VLAN or Inner.FGL.

I would appreciate clearer references to what these fields are.

If I understand this correctly, the idea here is to look into the inner =
layer 2 frames, and use the flow equivalents that exists on that level =
and hash that into value that maps the flows onto the source port range.

I think this text should include a summary of the principle and ensure =
to note the important requirement that what is considered flows in the =
inner must not result in being striped over multiple source ports as =
this may lead to reordering issues due to packets taking different =
paths.

NAT and TRILL over IP:
Section 8.5:

If one like to use TRILL over IP through a NAT, then there are some very =
important considerations that are missing. First the need for static =
binding configurations or the need for determining ones external =
address(es) and be able to communicate that to the peer RBridges, and in =
addition ensure that one has keep-alives to that the NAT binding never =
times out.

Next is the issue that there is almost zero chance of getting a IP/UDP =
encapsulation TRILL payload through the NAT if it results in IP =
fragmentation, as NATs don't do defragment and refragmented on the =
internal side, and an IP fragment lacks UDP port and thus can't be =
matched to binding.

Also if you like to run IP/ESP through a NAT, then you most likely need =
the IP/UDP/ESP encapsulation (https://tools.ietf.org/html/rfc3948). Note =
that this will restrict the MTU even further and thus ensure that the =
1470 requirement cannot be fulfilled even without additional tunnels =
over an 1500 bytes MTU Ethernet infrastructure.

I would note that also firewalls likely have issues with IP fragments =
for the same reason, they require significant amount of state to be =
verified if they should be let through.

In general I think you should create a configuration that has chance to =
work through most middleboxes, but I think you should require static =
bindings. I think that configuration is, and don't laugh now, but =
IP/UDP/ESP/TCP/TRILL, otherwise you will not be able to have both =
security and reliable fragmentation of TRILL packets.

Cheers

Magnus Westerlund




From nobody Thu Jun 15 19:15:50 2017
Return-Path: <Michael.Jones@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 E5B42128DE7; Thu, 15 Jun 2017 19:15:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.791
X-Spam-Level: 
X-Spam-Status: No, score=-4.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] 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 2t1I5_-BBNSa; Thu, 15 Jun 2017 19:15:47 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0117.outbound.protection.outlook.com [104.47.34.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 E927A1205D3; Thu, 15 Jun 2017 19:15:43 -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=khQmYq0CmgQ2VNh2acNZl092L0ige9iO0ys4lBewH/w=; b=SoqEoUi+GgefSp/K8DoJvoEgVsvXUz5j4IW8lYaCqxgcXo92VngeyqfBQX1R1gswhcoJEMXNqic3aAPVKmHG3WMzZZPPDca1e7C+JtP2rY2iBKlktZtF0mA8hjGrFByQkWhHJZGlh2iosJ7f4SFACHXC1zmMPKYsEJgGNLJoKx4=
Received: from CY4PR21MB0504.namprd21.prod.outlook.com (10.172.122.14) by CY4PR21MB0119.namprd21.prod.outlook.com (10.173.189.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.3; Fri, 16 Jun 2017 02:15:42 +0000
Received: from CY4PR21MB0504.namprd21.prod.outlook.com ([10.172.122.14]) by CY4PR21MB0504.namprd21.prod.outlook.com ([10.172.122.14]) with mapi id 15.01.1199.007; Fri, 16 Jun 2017 02:15:42 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Roni Even <ron.even.tlv@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-jones-cose-rsa.all@ietf.org" <draft-jones-cose-rsa.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>
Subject: RE: Genart telechat review of draft-jones-cose-rsa-03
Thread-Topic: Genart telechat review of draft-jones-cose-rsa-03
Thread-Index: AQHS0rCZxlTm4kwp0UaJsSe/8SVNrqIm5glQ
Date: Fri, 16 Jun 2017 02:15:41 +0000
Message-ID: <CY4PR21MB05044A22C26C81815A0B6AA4F5C10@CY4PR21MB0504.namprd21.prod.outlook.com>
References: <149542590419.3467.434051460088011243@ietfa.amsl.com>
In-Reply-To: <149542590419.3467.434051460088011243@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Ref=https://api.informationprotection.azure.com/api/72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetBy=mbj@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2017-06-15T19:15:40.6553255-07:00; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:9::5ef]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY4PR21MB0119; 7:Tay25smmwUcEe92SHM/ucOtA5MFG6qGA6vhaNmE/f6Ud46lNZN7ix3f6AUsvuIPgCWoyAPpzTmOaG6LsS4jHNqZhqxk37tbBQh77mwpaOs6TWua8ZsWDWIg1mb8aEIFJ1hcjrNy9XADs4NweE+m3TttfpqWtwt/+D2twYU5UguvLH2VGaGNNwlYI3Mq0TNjWYjiNNOWJW0iHb6tnz5vV3g34xNZkOv1ytcZ19k+2SSKWV1s6YDntreXIvpGQx1WuG4AqBzkEP7VLBxEVXqTHOmWbZrH6hmXE6pZZPtOCAjOdmuRKujsVezh2J3AsvZmsiGELFjHbI5BtdA5FJG+OP1fZ4pYXyTsw8iqTEu/UakLzcj7ztPoh9ErdJ/G7zWx0FUXFc/iTMCkNensixIIEqx2Y9zBaX+6m6BviMh2I1Rtu1HVk7m9mcRr51xKsMaKTz4Chsa9wY4FzfQFtKNYbRMsygs5v/wIHHdOtiNVgNcUBPj6Ri8JuWTxdp1yiUGjMZseBLFc9pj76EVlNIr9CeyNJlXCJQ8jmFuKOunPrSTcsjyqgB+3BnwNMakyzvSc2mJgaQ8PyI8uXQq8y876HiN/ch5hI7+rJjamtnUedOI/nrg7+rbj9ru/ESqIPa6sYzRcLEJ/GZHT3Z8OmLsbyHeHnW+/OxdQa3w8Sosv7brcKoTdLooVbKSDegYS4dFuiFL59BOuDtRamLpvAk2wCesfheWEtS+sgjFVQgx8SC2J5b6WN2YKlRebw5YVmOBy8mEFCrsfCGRG0TlrgGccAuYmdkCaDGpXlQdWXumcXEYsd1XHEV+GTu3/K6suj9zUn
x-ms-office365-filtering-correlation-id: 18f456bb-237f-49f9-f574-08d4b45d96c0
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500039)(300135000095)(300000501039)(300135300095)(300000502039)(300135100095)(22001)(2017030254075)(48565401081)(300000503039)(300135400095)(201703131423075)(201703031133081)(201702281549075)(300000504039)(300135200095)(300000505039)(300135600095)(300000506035)(300135500095); SRVR:CY4PR21MB0119; 
x-ms-traffictypediagnostic: CY4PR21MB0119:
x-microsoft-antispam-prvs: <CY4PR21MB01193D3B62DB92A23FFAB629F5C10@CY4PR21MB0119.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(31418570063057)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(100000703101)(100105400095)(3002001)(6055026)(61426038)(61427038)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123555025)(20161123562025)(20161123560025)(20161123564025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CY4PR21MB0119; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CY4PR21MB0119; 
x-forefront-prvs: 0340850FCD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39850400002)(39400400002)(39410400002)(39840400002)(39860400002)(39450400003)(209900001)(13464003)(51914003)(377454003)(377424004)(790700001)(25786009)(606005)(189998001)(2501003)(6436002)(14454004)(53546009)(2906002)(10090500001)(86612001)(5005710100001)(86362001)(8990500004)(4326008)(3660700001)(3280700002)(33656002)(39060400002)(6116002)(8936002)(81166006)(122556002)(229853002)(6246003)(6306002)(54896002)(7696004)(53936002)(76176999)(8676002)(2900100001)(102836003)(50986999)(54356999)(230783001)(7906003)(54906002)(72206003)(99286003)(38730400002)(10290500003)(478600001)(966005)(55016002)(2950100002)(5660300001)(7736002)(236005)(77096006)(74316002)(9686003)(53376002)(6506006)(6606295002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR21MB0119; H:CY4PR21MB0504.namprd21.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY4PR21MB05044A22C26C81815A0B6AA4F5C10CY4PR21MB0504namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Jun 2017 02:15:41.9018 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR21MB0119
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BuR3CJ2wJg7DDqClxlwfk3IpkfE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jun 2017 02:15:50 -0000

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

aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWpvbmVzLWNvc2UtcnNhLTA0IGFkZHJl
c3NlcyB5b3VyIHJldmlldyBjb21tZW50cywgUm9uaS4gIFRoYW5rcyBmb3IgdGhlIHVzZWZ1bCBy
ZXZpZXchDQoNCg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgLS0gTWlrZQ0KDQoNCg0KUC5TLiAgSSBhbHNvIHRoYW5rZWQg
eW91IGluIHRoZSBwdWJsaWNhdGlvbiBhbm5vdW5jZW1lbnQgYXQgaHR0cDovL3NlbGYtaXNzdWVk
LmluZm8vP3A9MTY5NyBhbmQgYXMgQHNlbGZpc3N1ZWQ8aHR0cHM6Ly90d2l0dGVyLmNvbS9zZWxm
aXNzdWVkPi4NCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBSb25pIEV2
ZW4gW21haWx0bzpyb24uZXZlbi50bHZAZ21haWwuY29tXQ0KU2VudDogU3VuZGF5LCBNYXkgMjEs
IDIwMTcgOTowNSBQTQ0KVG86IGdlbi1hcnRAaWV0Zi5vcmcNCkNjOiBkcmFmdC1qb25lcy1jb3Nl
LXJzYS5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmcNClN1YmplY3Q6IEdlbmFydCB0ZWxlY2hh
dCByZXZpZXcgb2YgZHJhZnQtam9uZXMtY29zZS1yc2EtMDMNCg0KDQoNClJldmlld2VyOiBSb25p
IEV2ZW4NCg0KUmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBOaXRzDQoNCg0KDQpJIGFtIHRoZSBh
c3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVh
IFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBw
cm9jZXNzZWQgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiBQbGVhc2Ugd2FpdCBmb3Ig
ZGlyZWN0aW9uIGZyb20geW91ciBkb2N1bWVudCBzaGVwaGVyZCBvciBBRCBiZWZvcmUgcG9zdGlu
ZyBhIG5ldyB2ZXJzaW9uIG9mIHRoZSBkcmFmdC4NCg0KDQoNCkZvciBtb3JlIGluZm9ybWF0aW9u
LCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCg0KDQoNCjxodHRwczovL3RyYWMuaWV0Zi5vcmcvdHJh
Yy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KDQoNCg0KRG9jdW1lbnQ6IGRyYWZ0LWpvbmVzLWNvc2Ut
cnNhLT8/DQoNClJldmlld2VyOiBSb25pIEV2ZW4NCg0KUmV2aWV3IERhdGU6IDIwMTctMDUtMjEN
Cg0KSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wNi0xNQ0KDQpJRVNHIFRlbGVjaGF0IGRhdGU6IDIw
MTctMDYtMjINCg0KDQoNClN1bW1hcnk6IFRoZSBkb2N1bWVudCBpcyByZWFkeSBmb3IgcHVibGlj
YXRpb24gYXMgc3RhbmRhcmQgdHJhY2sgUkZDIHdpdGggbml0cw0KDQoNCg0KTWFqb3IgaXNzdWVz
Og0KDQoNCg0KTWlub3IgaXNzdWVzOg0KDQoNCg0KTml0cy9lZGl0b3JpYWwgY29tbWVudHM6DQoN
Cg0KDQoxLiBTZWN0aW9uIDMgZmlyc3QgcGFyYWdyYXBoICJjYW4gYmUgZmluZCIgc2hvdWxkIGJl
ICJjYW4gYmUgZm91bmQiDQoNCg0KDQoyLiBJQU5BIDUuMSAgdGFibGUgMSBhbmQgMiBtaXNzaW5n
IHJlY29tbWVuZGVkIGNvbHVtDQoNCg0KDQozLiBJQU5BIDUuMyB0YWJsZSA0IHRoZSB0aXRsZSBp
cyBub3QgInZhbHVlIiBidXQgImxhYmVsIg0KDQoNCg0KDQoNCg0KDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjojMDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjoj
OTU0RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5Nc29QbGFpblRleHQsIGxp
Lk1zb1BsYWluVGV4dCwgZGl2Lk1zb1BsYWluVGV4dA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQgQ2hhciI7DQoJbWFyZ2luOjBpbjsNCgltYXJn
aW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLlBsYWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6
IlBsYWluIFRleHQgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1s
aW5rOiJQbGFpbiBUZXh0IjsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQou
TXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVp
biAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2Vj
dGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28g
OV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+
DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5
b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9v
OnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4t
VVMiIGxpbms9IiMwNTYzQzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0
aW9uMSI+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48YSBocmVmPSJodHRwczovL3Rvb2xzLmll
dGYub3JnL2h0bWwvZHJhZnQtam9uZXMtY29zZS1yc2EtMDQiPmh0dHBzOi8vdG9vbHMuaWV0Zi5v
cmcvaHRtbC9kcmFmdC1qb25lcy1jb3NlLXJzYS0wNDwvYT4gYWRkcmVzc2VzIHlvdXIgcmV2aWV3
IGNvbW1lbnRzLCBSb25pLiZuYnNwOyBUaGFua3MgZm9yIHRoZSB1c2VmdWwgcmV2aWV3ITxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsgLS0gTWlrZTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5QLlMuJm5ic3A7IEkg
YWxzbyB0aGFua2VkIHlvdSBpbiB0aGUgcHVibGljYXRpb24gYW5ub3VuY2VtZW50IGF0DQo8YSBo
cmVmPSJodHRwOi8vc2VsZi1pc3N1ZWQuaW5mby8/cD0xNjk3Ij5odHRwOi8vc2VsZi1pc3N1ZWQu
aW5mby8/cD0xNjk3PC9hPiBhbmQgYXMNCjxhIGhyZWY9Imh0dHBzOi8vdHdpdHRlci5jb20vc2Vs
Zmlzc3VlZCI+QHNlbGZpc3N1ZWQ8L2E+LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4t
LS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IFJvbmkgRXZlbiBbbWFpbHRvOnJv
bi5ldmVuLnRsdkBnbWFpbC5jb21dIDxicj4NClNlbnQ6IFN1bmRheSwgTWF5IDIxLCAyMDE3IDk6
MDUgUE08YnI+DQpUbzogZ2VuLWFydEBpZXRmLm9yZzxicj4NCkNjOiBkcmFmdC1qb25lcy1jb3Nl
LXJzYS5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc8YnI+DQpTdWJqZWN0OiBHZW5hcnQgdGVs
ZWNoYXQgcmV2aWV3IG9mIGRyYWZ0LWpvbmVzLWNvc2UtcnNhLTAzPC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij5SZXZpZXdlcjogUm9uaSBFdmVuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij5SZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIE5pdHM8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFm
dC4gVGhlIEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVU
RiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFp
ci4gUGxlYXNlIHdhaXQgZm9yIGRpcmVjdGlvbiBmcm9tIHlvdXIgZG9jdW1lbnQgc2hlcGhlcmQg
b3IgQUQgYmVmb3JlIHBvc3RpbmcNCiBhIG5ldyB2ZXJzaW9uIG9mIHRoZSBkcmFmdC48bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Rm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBzZWUg
dGhlIEZBUSBhdDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbHQ7PGEgaHJlZj0iaHR0
cHM6Ly90cmFjLmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxIj48c3BhbiBzdHlsZT0i
Y29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRpb246bm9uZSI+aHR0cHM6Ly90cmFjLmlldGYu
b3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPC9zcGFuPjwvYT4mZ3Q7LjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij5Eb2N1bWVudDogZHJhZnQtam9uZXMtY29zZS1yc2EtPz88bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlJldmlld2VyOiBSb25pIEV2ZW48bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlJldmlldyBEYXRlOiAyMDE3LTA1
LTIxPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5JRVRGIExDIEVuZCBE
YXRlOiAyMDE3LTA2LTE1PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5J
RVNHIFRlbGVjaGF0IGRhdGU6IDIwMTctMDYtMjI8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+U3VtbWFyeTogVGhlIGRvY3VtZW50IGlzIHJlYWR5IGZvciBwdWJsaWNhdGlvbiBhcyBzdGFu
ZGFyZCB0cmFjayBSRkMgd2l0aCBuaXRzPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPk1h
am9yIGlzc3Vlczo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+TWlub3IgaXNzdWVzOjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5OaXRzL2VkaXRvcmlhbCBjb21tZW50czogPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjEuIFNlY3Rpb24gMyBmaXJzdCBwYXJhZ3JhcGgg
JnF1b3Q7Y2FuIGJlIGZpbmQmcXVvdDsgc2hvdWxkIGJlICZxdW90O2NhbiBiZSBmb3VuZCZxdW90
OzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4yLiBJQU5BIDUuMSZuYnNwOyB0YWJsZSAx
IGFuZCAyIG1pc3NpbmcgcmVjb21tZW5kZWQgY29sdW08bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+My4gSUFOQSA1LjMgdGFibGUgNCB0aGUgdGl0bGUgaXMgbm90ICZxdW90O3ZhbHVlJnF1
b3Q7IGJ1dCAmcXVvdDtsYWJlbCZxdW90OzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_CY4PR21MB05044A22C26C81815A0B6AA4F5C10CY4PR21MB0504namp_--


From nobody Thu Jun 15 20:47:21 2017
Return-Path: <frank.xialiang@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 C7A99128B91; Thu, 15 Jun 2017 20:47:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Liang Xia <frank.xialiang@huawei.com>
To: <secdir@ietf.org>
Cc: draft-ietf-avtcore-rfc5285-bis.all@ietf.org, ietf@ietf.org, avt@ietf.org
Subject: Secdir telechat review of draft-ietf-avtcore-rfc5285-bis-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.54.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149758483978.11296.2498869353473500417@ietfa.amsl.com>
Date: Thu, 15 Jun 2017 20:47:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/av9uPfwIAlLiY6Xzf-I0pdKQ198>
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, 16 Jun 2017 03:47:20 -0000

Reviewer: Liang Xia
Review result: Ready

This document is ready to be published as a Standards Track document.

This document provides a general mechanism to use the header extension feature
of RTP (the Real-Time Transport Protocol). It provides the option to use a
small number of small extensions in each RTP packet, where the universe of
possible extensions is large and registration is de-centralized.  The actual
extensions in use in a session are signaled in the setup information for that
session.  This document obsoletes RFC5285.

This document has addressed all the issues I raised in Secdir review of -09
version, and is a well written now. I don't have any more comments.


From nobody Thu Jun 15 21:53:24 2017
Return-Path: <ron.even.tlv@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 61E23126BF6; Thu, 15 Jun 2017 21:53:15 -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 OQuJ5gqL7BYI; Thu, 15 Jun 2017 21:53:12 -0700 (PDT)
Received: from mail-wr0-x230.google.com (mail-wr0-x230.google.com [IPv6:2a00:1450:400c:c0c::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 371571200F3; Thu, 15 Jun 2017 21:53:11 -0700 (PDT)
Received: by mail-wr0-x230.google.com with SMTP id 77so32020014wrb.1; Thu, 15 Jun 2017 21:53:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=y2oxbJ1B5NvJHXpaG77l9kjVCZpYhleZHCj0B5pDUkM=; b=vJqYYdf9XWXBOrRmh8iRlVuvgPv9B0E0SaCEp2wWZrmPFX4RdXCPpMBmP3XqdCYF4y DgNpQmLuiMiFs2wRAd2nfCJMvtW1IenZVi7DcBxRIDsakMTATfSz0m4JhEtR7359nIN+ uza6h3sZ01uiVt8LFmLvebhi2rDjld77Xv/GKlYtBp33Po46AhGOuGU4u3AvGHEbutUV aGSmsOIeyu341k+gSOE9k7bIf8LrQOFRku4zR10jNp4x49sC09Q3eeuCUVc//vcIz/th ijBdhYVWIuqfl5gQECaWfdxBjNVXBSP8AA/8mcRO6Bu5nbWIyVZ6abj1yk9HO2GRPnhb OH0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=y2oxbJ1B5NvJHXpaG77l9kjVCZpYhleZHCj0B5pDUkM=; b=NWN8mTI0k3yKNE4qb6u4nSLFX/EOAadQbI+0y+56X1BwJB8q8YMaMCIHpYXGGFysF3 3c2EizPoMFO0mCBvLzprwuRWfCkL+0+0oPFGHcGaDT/n2i1LVLxkyobBcyNlirU7DiaJ hjq9stBnUZabbW7KtcMG0Nm/xdB2niULlnCHphAEo0fz0D1G2YdpVb5q4TA7vgPinKEk oTxDia3GrmcuyshQKSHO7bi/HLZ6blxuJ4Uwj1PUTwb7vfeX/7EP+/MRxmdXpMqMNMns /GkYrX+L3fVKeISbWKKcbQ9GnmvxBNXDIKecrlBQmTSd4vCSgs1Jr3P6tl3bqeTyplHF aWgw==
X-Gm-Message-State: AKS2vOxp+w20GegSY4TQM/BDCJJuTuJmwZ5yzWeN2+TSnV7is4z+vO2K aA5lHEPFOkQNYncNoz0=
X-Received: by 10.223.161.220 with SMTP id v28mr5505308wrv.37.1497588790216; Thu, 15 Jun 2017 21:53:10 -0700 (PDT)
Received: from RoniPC (bzq-109-64-85-249.red.bezeqint.net. [109.64.85.249]) by smtp.gmail.com with ESMTPSA id 70sm2346488wmu.28.2017.06.15.21.53.07 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 15 Jun 2017 21:53:08 -0700 (PDT)
From: "Roni Even" <ron.even.tlv@gmail.com>
To: "'Jonathan Lennox'" <jonathan@vidyo.com>, "'Roni Even'" <roni.even@huawei.com>
Cc: <draft-ietf-avtext-lrr.all@ietf.org>, "'General Area Review Team'" <gen-art@ietf.org>, <avtext@ietf.org>, <ietf@ietf.org>
References: <149629998360.19813.14889515687249184753@ietfa.amsl.com> <BAFC5C7C-466C-4756-9AF1-A803196E7D25@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7CFF25@DGGEMM506-MBX.china.huawei.com> <B9294064-4F4E-4FA1-A864-4F9790767B5C@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7D0641@DGGEMM506-MBX.china.huawei.com> <116D9947-414D-47EB-A0C7-8031999E5A89@vidyo.com> <01fe01d2e468$662f18e0$328d4aa0$@gmail.com> <D99B14A9-C6A4-456B-AEFA-8819B9EF6760@vidyo.com> <6E58094ECC8D8344914996DAD28F1CCD7D0DE0@DGGEMM506-MBX.china.huawei.com> <23DA0728-571B-4D1D-A567-6C4F3D245C03@vidyo.com>
In-Reply-To: <23DA0728-571B-4D1D-A567-6C4F3D245C03@vidyo.com>
Subject: RE: Genart last call review of draft-ietf-avtext-lrr-05
Date: Fri, 16 Jun 2017 07:52:00 +0300
Message-ID: <001e01d2e65c$4b2a9fb0$e17fdf10$@gmail.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: AQEOBITKuJRO9nhiFivT7qoen86ZIALweQwbARran8oBJBqhhQNABGFpAZ6UghYByHOz5gHNftrUAX0ZIuQCRL/WiKMlgM2w
Content-Language: he
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/80poCln4EiEv3xX3U5i65V7W5rY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jun 2017 04:53:15 -0000

Hi Jonathan,
In line
Roni

> -----Original Message-----
> From: Jonathan Lennox [mailto:jonathan@vidyo.com]
> Sent: Thursday, June 15, 2017 11:28 PM
> To: Roni Even
> Cc: Roni Even; draft-ietf-avtext-lrr.all@ietf.org; General Area Review =
Team;
> avtext@ietf.org; ietf@ietf.org
> Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
>=20
>=20
> > On Jun 14, 2017, at 1:37 AM, Roni Even <roni.even@huawei.com> wrote:
> >
> > Hi Jonathan,
> > Probably  part of my comment was based on the draft name , the =
message
> > name and the abstract (all about refresh). I did not see any text =
about the
> same usage limitation on FIR from RFC5104 "Using the FIR command to =
recover
> from errors is explicitly  disallowed, and instead the PLI message =
defined in AVPF
> [RFC4585]  should be used.  The PLI message reports lost pictures and =
has been
> included in AVPF for precisely that purpose."
> >
> > I am OK with similar approach as you suggested, so do you mean that =
PLI
> should be used also in this case to recover from errors.
>=20
> Yes, either PLI itself or some future to-be-defined per-layer PLI =
equivalent.  I=E2=80=99ll
> add corresponding text for LRR.  Would that satisfy your comments?
[Roni Even] Yes this will be OK
>=20
> > Practically it will interesting  to see if applications are using =
PLI and not FIR for
> packet loss cases and what encoders do when receiving PLI. (-:
>=20
> I suspect PLI and FIR are actually handled identically by most =
applications, but in
> low-bitrate scenarios it likely makes sense to treat them differently.
>=20
> > BTW: errors is a general term, I assume that for FIR it meant errors
> > due to packet loss (congestion)
>=20
> Packet loss is the most likely, but packet corruption (in the absence =
of UDP
> checksums), or encoder or decoder bugs, are also possible.
>=20
> > Roni
> >
> >> -----Original Message-----
> >> From: Jonathan Lennox [mailto:jonathan@vidyo.com]
> >> Sent: =D7=99=D7=95=D7=9D =D7=93 14 =D7=99=D7=95=D7=A0=D7=99 2017 =
01:49
> >> To: Roni Even
> >> Cc: Roni Even; draft-ietf-avtext-lrr.all@ietf.org; General Area
> >> Review Team; avtext@ietf.org; ietf@ietf.org
> >> Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
> >>
> >>
> >>> On Jun 13, 2017, at 1:13 PM, Roni Even <ron.even.tlv@gmail.com> =
wrote:
> >>>
> >>> Hi Jonathan,
> >>> This will be good but maybe explain the upgrade means also =
refresh.
> >> Because my poor understanding in English is that upgrade is adding =
a
> >> new layer that was not available to the media receiver while =
refresh
> >> is to restore existing layer (e.g. decoder synchronization loss).
> >>> Roni
> >>
> >> Ah, I see.
> >>
> >> The design goal of LRR was for it to be used for upgrade, not for
> >> synchronization loss, though of course now that you mention it, it
> >> could certainly be used for the latter as well. (I.e. it was =
designed
> >> to be analogous to FIR, not to PLI.)
> >>
> >> As with the difference between FIR and PLI, the congestion
> >> considerations are somewhat different between upgrade and
> >> synchronization loss.  Do you think it's worth addressing the =
synchronization
> loss cases explicitly?
> >>
> >>>
> >>>> -----Original Message-----
> >>>> From: Jonathan Lennox [mailto:jonathan@vidyo.com]
> >>>> Sent: Tuesday, June 13, 2017 7:03 PM
> >>>> To: Roni Even
> >>>> Cc: Roni Even; draft-ietf-avtext-lrr.all@ietf.org; General Area
> >>>> Review Team; avtext@ietf.org; ietf@ietf.org
> >>>> Subject: Re: Genart last call review of draft-ietf-avtext-lrr-05
> >>>>
> >>>> Hi, Roni =E2=80=94
> >>>>
> >>>> You seem to be assuming that a refresh and an upgrade are two
> >>>> different actions.  That=E2=80=99s not the intention =E2=80=94 a =
refresh is a
> >>>> characteristic of a stream that allows a decoder to upgrade.
> >>>>
> >>>> I=E2=80=99ll try to draft some text that makes it clear that =
it=E2=80=99s possible
> >>>> either to independently upgrade temporal or spatial, or else
> >>>> upgrade both
> >> at once.
> >>>>
> >>>>> On Jun 11, 2017, at 7:20 AM, Roni Even <roni.even@huawei.com>
> wrote:
> >>>>>
> >>>>> Hi Jonathan,
> >>>>> I assume the new text you propose is
> >>>>>
> >>>>> "When C is 1, TTID MUST NOT be less than CTID, and TLID MUST NOT
> >>>>> be less than CLID; at least one of TTID or TLID MUST be greater
> >>>>> than CTID or CLID respectively.  That is to say, the target =
layer
> >>>>> index <TTID, TLID> MUST be a layer upgrade from the current =
layer
> >>>>> index <CTID, CLID>.  A sender MAY request an upgrade in both
> >>>>> temporal and spatial/quality layers simultaneously."
> >>>>>
> >>>>> I think that this text still only implies the behavior, also the
> >>>>> current text talks about upgrade but I assume it is also for a
> >>>>> refresh not only to upgrade
> >>>>>
> >>>>> Maybe " A sender MAY request an upgrade or refresh  in both
> >>>>> temporal and  spatial/quality layers simultaneously by either
> >>>>> having C =3D1 or by having both
> >>>> CLID and CTID with lower values then TTID and TLID. If the sender
> >>>> want to upgrade or refresh only one layer then C MUST be equal to =
1
> >>>> and only the CTID or  the CLID of the layer to be upgraded or
> >>>> refreshed should be lower than the TTID or TLID respectively "
> >>>>>
> >>>>>
> >>>>> Roni
> >>>>>> -----Original Message-----
> >>>>>> From: Jonathan Lennox [mailto:jonathan@vidyo.com]
> >>>>>> Sent: =D7=99=D7=95=D7=9D =D7=93 07 =D7=99=D7=95=D7=A0=D7=99 =
2017 18:30
> >>>>>> To: Roni Even
> >>>>>> Cc: Roni Even; draft-ietf-avtext-lrr.all@ietf.org; General Area
> >>>>>> Review Team; avtext@ietf.org; ietf@ietf.org
> >>>>>> Subject: Re: Genart last call review of =
draft-ietf-avtext-lrr-05
> >>>>>>
> >>>>>>
> >>>>>>> On Jun 7, 2017, at 1:15 AM, Roni Even <roni.even@huawei.com>
> >> wrote:
> >>>>>>>
> >>>>>>> Hi Jonathan,
> >>>>>>> I did not see the text you added yet as a response to my first
> >>>>>>> question So to better clarify my question . If the FCI has
> >>>>>>> TTID=3D0 and TLID=3D2
> >>>> .
> >>>>>> does it mean that it is a request to update both?
> >>>>>>> This was also the reason for the question about both TTID=3D0 =
and
> >>>>>>> TLID=3D0,
> >>>>>> which layer need update or is it both?
> >>>>>>> Can you say that you want just to update temporal or spatial?
> >>>>>>
> >>>>>> Yes, if the FCI has TTID=3D0 and TLID=3D2, it=E2=80=99s a =
request to update
> >>>>>> both layers =E2=80=94 or more specifically, to make sure that =
you can
> >>>>>> start decoding the substream with TTID=3D0 and TLID=3D2. (For =
most
> >>>>>> scalability structures this would mean updating both, but =
exotic
> >>>>>> structures are
> >>>>>> possible.)
> >>>>>>
> >>>>>> If you want to just update one part of the stream, =
that=E2=80=99s what
> >>>>>> CTID and CLID are for.  If you sent TTID=3D0 and TLID=3D2,
> >>>>>> accompanied by
> >>>>>> CTID=3D0 and CLID=3D0, that means that you already have TID 0, =
and
> >>>>>> you just want to increase the LID.
> >>>>>>
> >>>>>> The current text is at
> >>>>>> https://github.com/juberti/draughts/tree/master/lrr , if you =
want
> >>>>>> to take a look at the latest revisions, or suggest text that =
you
> >>>>>> think would make
> >>>> it cleaner.
> >>>>>>
> >>>>>>
> >>>>>>> Roni
> >>>>>>>
> >>>>>>>> -----Original Message-----
> >>>>>>>> From: Gen-art [mailto:gen-art-bounces@ietf.org] On Behalf Of
> >>>>>>>> Jonathan Lennox
> >>>>>>>> Sent: =D7=99=D7=95=D7=9D =D7=93 07 =D7=99=D7=95=D7=A0=D7=99 =
2017 00:30
> >>>>>>>> To: Roni Even
> >>>>>>>> Cc: draft-ietf-avtext-lrr.all@ietf.org; General Area Review
> >>>>>>>> Team; avtext@ietf.org; ietf@ietf.org
> >>>>>>>> Subject: Re: [Gen-art] Genart last call review of
> >>>>>>>> draft-ietf-avtext-lrr-05
> >>>>>>>>
> >>>>>>>> Hi, Roni =E2=80=94 thanks for your review.  Responses inline.
> >>>>>>>>
> >>>>>>>>> On Jun 1, 2017, at 2:53 AM, Roni Even =
<ron.even.tlv@gmail.com>
> >>>> wrote:
> >>>>>>>>>
> >>>>>>>>> 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.
> >>>>>>>>
> >>>>>>>> Syntactically, they must both occur.
> >>>>>>>>
> >>>>>>>> If you mean can you request an upgrade in both at once, yes;
> >>>>>>>> I=E2=80=99ve added text to clarify this.
> >>>>>>>>
> >>>>>>>>> 2. What is the meaning of value 0 for TTID and TLID - TID or
> >>>>>>>>> LID
> >>>>>>>>> =3D0 in frame marking draft means base layer if there is =
scalability.
> >>>>>>>>> This relates to the previous question.
> >>>>>>>>
> >>>>>>>> I=E2=80=99m not sure I understand this question.
> >>>>>>>>
> >>>>>>>> I=E2=80=99ve added text that if C=3D1, at least one of <TTID, =
TLID> MUST
> >>>>>>>> be greater than <CTID, CLID>, and both MUST be greater than =
or
> >>>>>>>> equal to their counterpart, so the LRR is actually requesting =
a
> >>>>>>>> layer
> >> upgrade.
> >>>>>>>> Is that what you were asking about?
> >>>>>>>>
> >>>>>>>>> 3.  What would an FCI with both TTID and TLID equal 0 mean.
> >>>>>>>>
> >>>>>>>> It means you want a refresh of the base temporal/spatial =
layer, only.
> >>>>>>>>
> >>>>>>>>> Nits/editorial comments:
> >>>>>>>>>
> >>>>>>>>> 1. Section 3 "an Real-Time Transport Control Protocol" =
should
> >>>>>>>>> be "a Real=E2=80=A6".
> >>>>>>>>
> >>>>>>>> Colin pointed out that it should say =E2=80=9Can RTP Control =
Protocol=E2=80=9D
> >> anyway.
> >>>>>>>>
> >>>>>>>>> 2. In section 3 " [RFC5104](Section 3.5.1)" there is a link =
to
> >>>>>>>>> section
> >>>>>>>>> 3.5.1 but it does not work.
> >>>>>>>>
> >>>>>>>> xml2rfc doesn=E2=80=99t have any way to link to sections of =
other
> >>>>>>>> documents, so the =E2=80=9C(Section 3.5.1)=E2=80=9D part is =
just a comment.
> >>>>>>>>
> >>>>>>>> I think the internet-draft tooling may have thought I was
> >>>>>>>> trying to link to a non-existent section 3.5.1 of this
> >>>>>>>> document, but that=E2=80=99s outside
> >>>>>> my control.
> >>>>>>>>
> >>>>>>>>> 3. In section 3.2 "(see section Section 2.1)" section =
appears twice.
> >>>>>>>>
> >>>>>>>> Fixed.
> >>>>>>>> _______________________________________________
> >>>>>>>> Gen-art mailing list
> >>>>>>>> Gen-art@ietf.org
> >>>>>>>> https://www.ietf.org/mailman/listinfo/gen-art
> >>>>>
> >>>
> >>>
> >



From nobody Thu Jun 15 22:10:08 2017
Return-Path: <lucienav@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 4E8461200F3 for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 22:10:06 -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=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LFkRHw139siV for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 22:10:03 -0700 (PDT)
Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::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 6D7AF128616 for <ietf@ietf.org>; Thu, 15 Jun 2017 22:10:03 -0700 (PDT)
Received: by mail-pf0-x22d.google.com with SMTP id 83so17607420pfr.0 for <ietf@ietf.org>; Thu, 15 Jun 2017 22:10:03 -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=1MzW+4GS38pV0WSPQQwPrZiGZ/cfaVXAB1ECkxrRhvI=; b=uIa/LF20NvivIY1u47gVH4D4es1v7HT3WIWhl59dg850RjswJk8XViGaOT0aJkBrLA 3Y4Za1tTEKQOczE6UTi7dAUKwROisJfDhBVH/aA3mjG0cSV5wMmxKdwWVmEl69CztoLy S+WQBsdS7KBKGV7x4dS1OgkhSQ6fdy8tnTWulH6zyTOneTLBmmMGXSZGXC1nunJXZvnE jleYqcegE2CWMMnHQb9O1AQ4CYILzG8xLKiUIo7B7j2ZLAydYjnqrgtp45Emq+M+vzMV 9ddry2xMZ4aEh2aJU5tbI1ZG8Pi0vbrJs7eHhSh48bz+uwx/U99j5U2ZlZL+q/b4sVv6 i8cg==
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=1MzW+4GS38pV0WSPQQwPrZiGZ/cfaVXAB1ECkxrRhvI=; b=jBLbhJB9jOMUgfK1BtyEofFgK5E9l8FbBUeATQSdRy5LMwJDtfDN9kp7O1VcYhPQYU kQ1JYwaXhmfqbGKw7/FJjY2p4DuOvYHusT8PecFtlEUzZkDWbeSilHQGsrD886+PwR5Y uxC0oxQpGajQi4H/156k4JCZF76ogxATEXoPHKluawKoym0/7L8XFxSzTJipY93hvcRd FJbhSO3+Vj/M80RGGcNTvXD1A20/0RBvULcYTE0mx03GoP4Ha1ySiZgOzA4Vw9rBNpXQ CWGL5pXsdSozm+YzxI2emPSvXSfsX7hn2FOI1VdFxcHa61OQFk2VT7ZY75A55ZcYke19 wqFw==
X-Gm-Message-State: AKS2vOyBvxoRy1XAzBOxOREU80q16GJai/JA0eU/KaTQvy7YmnBTSIDi UGuZr5VtJRKYlDs23gDLrJPK6Zfe9pgP
X-Received: by 10.99.105.4 with SMTP id e4mr9354729pgc.186.1497589802828; Thu, 15 Jun 2017 22:10:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.168.5 with HTTP; Thu, 15 Jun 2017 22:09:42 -0700 (PDT)
In-Reply-To: <149741280522.7481.5692213354540706614@ietfa.amsl.com>
References: <149741280522.7481.5692213354540706614@ietfa.amsl.com>
From: Lucien Avramov <lucienav@google.com>
Date: Thu, 15 Jun 2017 22:09:42 -0700
Message-ID: <CALTEt=DWK5n8xVJ_ZD3j5BZmBT=_id1ZERCHPY3SGEqYL6N8sg@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-bmwg-dcbench-terminology-10
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>
Cc: gen-art <gen-art@ietf.org>, ietf <ietf@ietf.org>, bmwg@ietf.org,  draft-ietf-bmwg-dcbench-terminology.all@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c140dce380ba605520cccb4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/TY_hNyKtIR7_GtTjeXe8Uj5Bx0s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jun 2017 05:10:06 -0000

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

Hi Matthew!

Thank you for the review!
We incorporated your feedback and now it's in -12: of the draft
<https://datatracker.ietf.org/doc/draft-ietf-bmwg-dcbench-terminology/>

Please see inline more details to each of your feedback.

Thank you for such a detailed write up.

Best,
Lucien




> *Subject:* *Genart last call review of
> draft-ietf-bmwg-dcbench-terminology-10*
>
> Reviewer: Matthew Miller
> 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-dcbench-terminology-10
> Reviewer: Matthew A. Miller
> Review Date: 2017-06-13
> IETF LC End Date: 2017-06-13
> IESG Telechat date: N/A
>
> Summary:
>
> This document is almost ready; this document is on the path to its
> goals set out in the abstract and introduction, but the execution
> needs more work.
>
> I think the authors would benefit from another round of proofreading
> and submit a new revision.  Below are the most obvious or egregious
> issues I have.
>
> Major issues:
>
> * In section 6.2 "Incast", it is unclear what is being measured,
> and what the units (if any) for that measurement are.  Is it the
> percentage of synchronization?  Is it the synchronous arrival time
> (which presumably is measured as a delta over some magnitude of
> seconds)? Is it the number of ingress and egress ports?  If it is
> the number of ingress and egress ports, then it should define what
> "egress" means for the purpose of this measurement
>
>
fixed!

>
>
> * In Section 8. "Security Considerations", what is the reason for
> the "SHOULD" and "SHOULD NOT" in the last paragraph (discussing
> special capabilities)?  At the least it seems safest for the
> exceptions that rationalize the "SHOULD" and "SHOULD NOT" be
> explicitly stated here, or changed to "MUST" and "MUST NOT" if
> that rationale cannot be stated.
>
>
These are the standard security considerations all BMWG uses for the
drafts. We want to stay with the considerations we chose.

>
>
> Minor issues:
>
> * RFC 2119 should be a normative reference, as the reader MUST
> understand what the terms as-written mean.
>
> done


>
>
> * RFC 5841 needs to be a listed reference; It is explicitly pointed
> to in Sections 3.1. and 3.2. From the text is seems a Normative
> reference is warranted but it at least needs to be documented in
> References.
>
> done

>
>
> * RFC 2647 needs to be a listed reference. It is explicitly pointed
> to in Section 7.1.; from the text it seems appropriate to be an
> Informative reference.
>
> done

>
>
> * The definition in Section 1.2. of what the "Measurement Units"
> subsections definitions format doesn't seem to be followed in
> this document.  Specifically, the "Measurement Units" subsections
> rarely ever mention a unit of measure; instead the unit of measure
> is almost always specified as part of the "Definition" subsection.
> It may be worth revisiting the name for the "Measurement Units"
> subsections, or to move the unit of measure out of the
> "Definitions" subsections and into the "Measurement Units"
> subsections.
>
> Section 1.2 has the purpose to explain how the document is formatted.
it has 3 subsections each time moving forward as described in 1.2. We use
that third subsection in this document to explain how to measure the topic
discussed.


   - Definition: The specific definition for the term.


   - Discussion: A brief discussion about the term, its application


   - Measurement Units


>
> * In section 2.3., the use of MUST, MAY, and MUST NOT seems
> a little contradictory.  The MUST for point 1 would seem to
> already negate point 3, and prohibit point 2.  Would changing
> that MUST to SHOULD be acceptable?
>
> We wanted to keep MUST , MAY and MUST NOT to explain that : 1) is the way
to go ALWAYS. 2) can be done but it very specific to particular corner use
case. 3) should never be done, although 1) negates 3), we want to call out
3, because people often time do 1) and don't follow 3. (they would do a
LIFO test although they must not do it).



These are the standard security considerations all BMWG uses for the
drafts. We want to stay with the considerations we chose.

>
>
> Nits/editorial comments:
>
> * It would be helpful to include a reference to what "north-south"
> and "east-west" mean, if possible.
>
> done!

>
>
> * the acronyms DUT and SUT -- at the least -- need to be
> expanded on first use, or in Section 1.1. "Terminology".
>
>
done!

>
>
> * In a number of subsections (notably under Section 4. and Section
> 6.), square brackets ("[" and "]") are used instead of parentheses
> ("(" and ")"), without any clear reason for the difference.  They
> should be switched to parentheses.
>
> done!

>
>
> * In Section 2.2., the word "for" or "at" should be removed in the
> sentence "The change of behavior happens for at specific larger
> packet sizes."
>
> done!

>
>
> * Section 2.3., the phrase "the application commonly need to" should
> be changed to "the application commonly needs to".
>
> done!

> * In Section 5.2., there is a comma missing between "crystals" and
> "or" in "The crystals or clock modules, usually have a specific".
>
> done!

>
>
> * Also in Section 5.2., the term "devices under test" is used
> instead of DUTs the rest of the document seems to use.
>
> done!

>
>
> * Throughout Section 6.1., the acronyms "cos" and "dcsp" should be
> expanded on first use.
>
> done!

>
>
> * In Section 6.1.1, the definition of "Buffer Size" calls out using
> some magnitude of bytes (B, KB, MB, GB), then the example denotes
> "Mb" -- which commonly is used for megabits.  From the rest of the
> definition, it seems this should be MB, but I have not calculated
> if the numerical value preceding the unit needs to be revisited.
>
> done!

>
>
> * In Section 6.2.1, the Stateful and Stateless terms both use the
> phrase "such as for example", which is redundant.  Either "such as"
> or "for example" is sufficient, and the other should be removed.
>
> * The formatting in Section 10. "References" is very inconsistent.
> There is odd indentation and inconsistent anchor usage.
>
>
fixed as much as i could, there is a problem with nits in submission tool
when

>
>
> * The affiliation and email address for Lucien Avramov is Google,
> but the street address is mostly that for Cisco Systems, Inc.
>
> done

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

<div dir=3D"ltr">Hi Matthew!<div><br></div><div>Thank you for the review!</=
div><div>We incorporated your feedback and now it&#39;s in -12: of the <a h=
ref=3D"https://datatracker.ietf.org/doc/draft-ietf-bmwg-dcbench-terminology=
/">draft</a></div><div><br></div><div>Please see inline more details to eac=
h of your feedback.</div><div><br></div><div>Thank you for such a detailed =
write up.</div><div><br></div><div>Best,</div><div>Lucien</div><div><br></d=
iv><div><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><div =
style=3D"min-height:100%"><div class=3D"gmail-nH" style=3D"width:1188px"><d=
iv class=3D"gmail-nH" style=3D""><div class=3D"gmail-nH gmail-bkL"><div cla=
ss=3D"gmail-no"><div class=3D"gmail-nH gmail-bkK gmail-nn" style=3D"width:9=
86px"><div class=3D"gmail-nH"><div class=3D"gmail-nH"><div class=3D"gmail-n=
H gmail-ar4 gmail-z"><div class=3D"gmail-aeI"><div class=3D"gmail-AO"><div =
id=3D"gmail-:4" class=3D"gmail-Tm gmail-aeJ" style=3D"height:551px"><div id=
=3D"gmail-:2" class=3D"gmail-aeF" style=3D"min-height:121px"><div class=3D"=
gmail-nH"><div class=3D"gmail-nH"><div class=3D"gmail-nH gmail-g"><table cl=
ass=3D"gmail-Bs gmail-nH gmail-iY" cellpadding=3D"0" style=3D"width:956px">=
<tbody><tr><td class=3D"gmail-Bu"><div class=3D"gmail-nH gmail-if"><div cla=
ss=3D"gmail-nH gmail-aHU"><div class=3D"gmail-nH gmail-hx"><div class=3D"gm=
ail-nH"><div class=3D"gmail-h7 gmail-hn gmail-ie gmail-nH gmail-oy8Mbf" tab=
index=3D"-1"><div class=3D"gmail-Bk" style=3D"width:705px"><div class=3D"gm=
ail-G3 gmail-G2 gmail-afm"><div id=3D"gmail-:1ph"><div class=3D"gmail-adn g=
mail-ads"><div class=3D"gmail-gs"><div id=3D"gmail-:1qg" class=3D"gmail-ii =
gmail-gt gmail-adO" style=3D"font-size:12.8px"><div id=3D"gmail-:1z2" class=
=3D"gmail-a3s gmail-aXjCH gmail-m15caf4bc03a5f652"><div dir=3D"ltr"><div cl=
ass=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"gmail-adM"><di=
v class=3D"gmail-im"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div class=3D"gmail-m_-5=
66981276781100764gmail-h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div=
 dir=3D"auto"><blockquote type=3D"cite" style=3D"font-size:12.8px"><br><b>S=
ubject:</b>=C2=A0<b>Genart last call review of draft-ietf-bmwg-dcbench-term=
in<wbr>ology-10</b><br><br></blockquote><div style=3D"font-size:12.8px"><di=
v class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><block=
quote type=3D"cite">Reviewer: Matthew Miller<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"=
 target=3D"_blank">https://trac.ietf.org/trac/ge<wbr>n/wiki/GenArtfaq</a>&g=
t;.<br><br>Document: draft-ietf-bmwg-dcbench-termin<wbr>ology-10<br>Reviewe=
r: Matthew A. Miller<br>Review Date: 2017-06-13<br>IETF LC End Date: 2017-0=
6-13<br>IESG Telechat date: N/A<br><br>Summary:<br><br>This document is alm=
ost ready; this document is on the path to its<br>goals set out in the abst=
ract and introduction, but the execution<br>needs more work.<br><br>I think=
 the authors would benefit from another round of proofreading<br>and submit=
 a new revision.=C2=A0 Below are the most obvious or egregious<br>issues I =
have.<br><br>Major issues:<br><br>* In section 6.2 &quot;Incast&quot;, it i=
s unclear what is being measured,<br>and what the units (if any) for that m=
easurement are.=C2=A0 Is it the<br>percentage of synchronization?=C2=A0 Is =
it the synchronous arrival time<br>(which presumably is measured as a delta=
 over some magnitude of<br>seconds)? Is it the number of ingress and egress=
 ports?=C2=A0 If it is<br>the number of ingress and egress ports, then it s=
hould define what<br>&quot;egress&quot; means for the purpose of this measu=
rement</blockquote></div></div></div></div></div></div></div></blockquote><=
div><br></div></div></div><div>fixed!=C2=A0</div><span class=3D"gmail-im"><=
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"><div class=3D"gmail-m_-566=
981276781100764gmail-HOEnZb"><div class=3D"gmail-m_-566981276781100764gmail=
-h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"auto"><div cla=
ss=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockquote=
 type=3D"cite"><br><br>* In Section 8. &quot;Security Considerations&quot;,=
 what is the reason for<br>the &quot;SHOULD&quot; and &quot;SHOULD NOT&quot=
; in the last paragraph (discussing<br>special capabilities)?=C2=A0 At the =
least it seems safest for the<br>exceptions that rationalize the &quot;SHOU=
LD&quot; and &quot;SHOULD NOT&quot; be<br>explicitly stated here, or change=
d to &quot;MUST&quot; and &quot;MUST NOT&quot; if<br>that rationale cannot =
be stated.</blockquote></div></div></div></div></div></div></blockquote><di=
v><br></div></span><div>These are the standard security considerations all =
BMWG uses for the drafts. We want to stay with the considerations we chose.=
 =C2=A0=C2=A0</div><span class=3D"gmail-im"><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"><div class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><=
div class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr"><div cla=
ss=3D"gmail_quote"><div dir=3D"auto"><div class=3D"gmail-m_-566981276781100=
764gmail-m_8608744719394608261h5"><blockquote type=3D"cite"><br><br>Minor i=
ssues:<br><br>* RFC 2119 should be a normative reference, as the reader MUS=
T<br>understand what the terms as-written mean.</blockquote></div></div></d=
iv></div></div></div></blockquote></span><div>done</div><span class=3D"gmai=
l-im"><div>=C2=A0</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"><d=
iv class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div class=3D"gmail-m_=
-566981276781100764gmail-h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><d=
iv dir=3D"auto"><div class=3D"gmail-m_-566981276781100764gmail-m_8608744719=
394608261h5"><blockquote type=3D"cite"><br><br>* RFC 5841 needs to be a lis=
ted reference; It is explicitly pointed<br>to in Sections 3.1. and 3.2. Fro=
m the text is seems a Normative<br>reference is warranted but it at least n=
eeds to be documented in<br>References.</blockquote></div></div></div></div=
></div></div></blockquote></span><div>done=C2=A0</div><span class=3D"gmail-=
im"><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"><div class=3D"gmail-m=
_-566981276781100764gmail-HOEnZb"><div class=3D"gmail-m_-566981276781100764=
gmail-h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"auto"><di=
v class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><block=
quote type=3D"cite"><br><br>* RFC 2647 needs to be a listed reference. It i=
s explicitly pointed<br>to in Section 7.1.; from the text it seems appropri=
ate to be an<br>Informative reference.</blockquote></div></div></div></div>=
</div></div></blockquote></span><div>done=C2=A0</div><span class=3D"gmail-i=
m"><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 class=3D"gmail-m_=
-566981276781100764gmail-HOEnZb"><div class=3D"gmail-m_-566981276781100764g=
mail-h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"auto"><div=
 class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite"><br><br>* The definition in Section 1.2. of what the &qu=
ot;Measurement Units&quot;<br>subsections definitions format doesn&#39;t se=
em to be followed in<br>this document.=C2=A0 Specifically, the &quot;Measur=
ement Units&quot; subsections<br>rarely ever mention a unit of measure; ins=
tead the unit of measure<br>is almost always specified as part of the &quot=
;Definition&quot; subsection.<br>It may be worth revisiting the name for th=
e &quot;Measurement Units&quot;<br>subsections, or to move the unit of meas=
ure out of the<br>&quot;Definitions&quot; subsections and into the &quot;Me=
asurement Units&quot;<br>subsections.</blockquote></div></div></div></div><=
/div></div></blockquote></span><div>Section 1.2 has the purpose to explain =
how the document is formatted.=C2=A0</div><div>it has 3 subsections each ti=
me moving forward as described in 1.2. We use that third subsection in this=
 document to explain how to measure the topic discussed.=C2=A0</div><div><b=
r></div><div><div><ul><li>Definition: The specific definition for the term.=
</li></ul></div><div><ul><li>Discussion: A brief discussion about the term,=
 its application</li></ul></div><div><ul><li>Measurement Units<br></li></ul=
></div></div><span class=3D"gmail-im"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div cl=
ass=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr"><div class=3D"=
gmail_quote"><div dir=3D"auto"><div class=3D"gmail-m_-566981276781100764gma=
il-m_8608744719394608261h5"><blockquote type=3D"cite"><br><br>* In section =
2.3., the use of MUST, MAY, and MUST NOT seems<br>a little contradictory.=
=C2=A0 The MUST for point 1 would seem to<br>already negate point 3, and pr=
ohibit point 2.=C2=A0 Would changing<br>that MUST to SHOULD be acceptable?<=
/blockquote></div></div></div></div></div></div></blockquote></span><div>We=
 wanted to keep MUST , MAY and MUST NOT to explain that : 1) is the way to =
go ALWAYS. 2) can be done but it very specific to particular corner use cas=
e. 3) should never be done, although 1) negates 3), we want to call out 3, =
because people often time do 1) and don&#39;t follow 3. (they would do a LI=
FO test although they must not do it).=C2=A0</div><div><br></div><div>=C2=
=A0</div><div><br></div><div>These are the standard security considerations=
 all BMWG uses for the drafts. We want to stay with the considerations we c=
hose. =C2=A0</div><span class=3D"gmail-im"><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex"><div class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><d=
iv class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr"><div clas=
s=3D"gmail_quote"><div dir=3D"auto"><div class=3D"gmail-m_-5669812767811007=
64gmail-m_8608744719394608261h5"><blockquote type=3D"cite"><br><br>Nits/edi=
torial comments:<br><br>* It would be helpful to include a reference to wha=
t &quot;north-south&quot;<br>and &quot;east-west&quot; mean, if possible.</=
blockquote></div></div></div></div></div></div></blockquote></span><div>don=
e!=C2=A0</div><span class=3D"gmail-im"><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div c=
lass=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr"><div class=3D=
"gmail_quote"><div dir=3D"auto"><div class=3D"gmail-m_-566981276781100764gm=
ail-m_8608744719394608261h5"><blockquote type=3D"cite"><br><br>* the acrony=
ms DUT and SUT -- at the least -- need to be<br>expanded on first use, or i=
n Section 1.1. &quot;Terminology&quot;.</blockquote></div></div></div></div=
></div></div></blockquote><div><br></div></span><div>done!=C2=A0</div><span=
 class=3D"gmail-im"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div class=3D"gmail-m_-56=
6981276781100764gmail-h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div =
dir=3D"auto"><div class=3D"gmail-m_-566981276781100764gmail-m_8608744719394=
608261h5"><blockquote type=3D"cite"><br><br>* In a number of subsections (n=
otably under Section 4. and Section<br>6.), square brackets (&quot;[&quot; =
and &quot;]&quot;) are used instead of parentheses<br>(&quot;(&quot; and &q=
uot;)&quot;), without any clear reason for the difference.=C2=A0 They<br>sh=
ould be switched to parentheses.</blockquote></div></div></div></div></div>=
</div></blockquote></span><div>done!=C2=A0</div><span class=3D"gmail-im"><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 class=3D"gmail-m_-5669=
81276781100764gmail-HOEnZb"><div class=3D"gmail-m_-566981276781100764gmail-=
h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"auto"><div clas=
s=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockquote =
type=3D"cite"><br><br>* In Section 2.2., the word &quot;for&quot; or &quot;=
at&quot; should be removed in the<br>sentence &quot;The change of behavior =
happens for at specific larger<br>packet sizes.&quot;</blockquote></div></d=
iv></div></div></div></div></blockquote></span><div>done!=C2=A0</div><span =
class=3D"gmail-im"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div c=
lass=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div class=3D"gmail-m_-566=
981276781100764gmail-h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div d=
ir=3D"auto"><div class=3D"gmail-m_-566981276781100764gmail-m_86087447193946=
08261h5"><blockquote type=3D"cite"><br><br>* Section 2.3., the phrase &quot=
;the application commonly need to&quot; should<br>be changed to &quot;the a=
pplication commonly needs to&quot;.<br><br></blockquote></div></div></div><=
/div></div></div></blockquote></span><div>done!=C2=A0</div><span class=3D"g=
mail-im"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"gm=
ail-m_-566981276781100764gmail-HOEnZb"><div class=3D"gmail-m_-5669812767811=
00764gmail-h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"auto=
"><div class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><=
blockquote type=3D"cite">* In Section 5.2., there is a comma missing betwee=
n &quot;crystals&quot; and<br>&quot;or&quot; in &quot;The crystals or clock=
 modules, usually have a specific&quot;.</blockquote></div></div></div></di=
v></div></div></blockquote></span><div>done!=C2=A0</div><span class=3D"gmai=
l-im"><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"><div class=3D"gmail=
-m_-566981276781100764gmail-HOEnZb"><div class=3D"gmail-m_-5669812767811007=
64gmail-h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"auto"><=
div class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blo=
ckquote type=3D"cite"><br><br>* Also in Section 5.2., the term &quot;device=
s under test&quot; is used<br>instead of DUTs the rest of the document seem=
s to use.</blockquote></div></div></div></div></div></div></blockquote></sp=
an><div>done!=C2=A0</div><span class=3D"gmail-im"><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div class=3D"gmail-m_-566981276781100764gmail-HOE=
nZb"><div class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr"><d=
iv class=3D"gmail_quote"><div dir=3D"auto"><div class=3D"gmail-m_-566981276=
781100764gmail-m_8608744719394608261h5"><blockquote type=3D"cite"><br><br>*=
 Throughout Section 6.1., the acronyms &quot;cos&quot; and &quot;dcsp&quot;=
 should be<br>expanded on first use.</blockquote></div></div></div></div></=
div></div></blockquote></span><div>done!=C2=A0</div><span class=3D"gmail-im=
"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"gmail-m_-=
566981276781100764gmail-HOEnZb"><div class=3D"gmail-m_-566981276781100764gm=
ail-h5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"auto"><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockqu=
ote type=3D"cite"><br><br>* In Section 6.1.1, the definition of &quot;Buffe=
r Size&quot; calls out using<br>some magnitude of bytes (B, KB, MB, GB), th=
en the example denotes<br>&quot;Mb&quot; -- which commonly is used for mega=
bits.=C2=A0 From the rest of the<br>definition, it seems this should be MB,=
 but I have not calculated<br>if the numerical value preceding the unit nee=
ds to be revisited.</blockquote></div></div></div></div></div></div></block=
quote></span><div>done!=C2=A0</div><span class=3D"gmail-im"><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 class=3D"gmail-m_-56698127678110076=
4gmail-HOEnZb"><div class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=
=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"auto"><div class=3D"gmail-m=
_-566981276781100764gmail-m_8608744719394608261h5"><blockquote type=3D"cite=
"><br><br>* In Section 6.2.1, the Stateful and Stateless terms both use the=
<br>phrase &quot;such as for example&quot;, which is redundant.=C2=A0 Eithe=
r &quot;such as&quot;<br>or &quot;for example&quot; is sufficient, and the =
other should be removed.<br><br>* The formatting in Section 10. &quot;Refer=
ences&quot; is very inconsistent.<br>There is odd indentation and inconsist=
ent anchor usage.</blockquote></div></div></div></div></div></div></blockqu=
ote><div><br></div></span><div>fixed as much as i could, there is a problem=
 with nits in submission tool when =C2=A0</div><span class=3D"gmail-im"><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex"><div class=3D"gmail-m_-56698=
1276781100764gmail-HOEnZb"><div class=3D"gmail-m_-566981276781100764gmail-h=
5"><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"auto"><div class=
=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockquote t=
ype=3D"cite"><br><br>* The affiliation and email address for Lucien Avramov=
 is Google,<br>but the street address is mostly that for Cisco Systems, Inc=
.</blockquote></div></div></div></div></div></div></blockquote></span><div>=
done=C2=A0</div></div></div></div></div></div></div></div></div></div></div=
></div></div></div></div></div></td></tr></tbody></table></div></div></div>=
</div></div></div></div></div></div></div></div></div></div></div></div></d=
iv></div></div></div></div>

--94eb2c140dce380ba605520cccb4--


From nobody Thu Jun 15 22:55: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 B74DD128AFE for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 22:55:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E1k1OsxWerkZ for <ietf@ietfa.amsl.com>; Thu, 15 Jun 2017 22:55:34 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 98998124D6C for <ietf@ietf.org>; Thu, 15 Jun 2017 22:55:33 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.75.184]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LrZOj-1dpDQ72zbJ-013QCW; Fri, 16 Jun 2017 07:55:30 +0200
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: Bob Hinden <bob.hinden@gmail.com>, Brian Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF <ietf@ietf.org>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <6f9a0398-7862-3c71-9b0f-0f8bd95ff277@gmx.de>
Date: Fri, 16 Jun 2017 07:55:28 +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: <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:AjrpfE/tAyWUv6DmshUOtAuGrWhQYPpNuuTmhggdaxXMza3feAu XLfDD8P04KyY65TqOwrfqvSOj3ox566EoDSXRIxX6SJwDUR7macPuA1FSvftH4YYz1Fyf2f Y2Yt5A4yRx9gbI5KTLaDuEt7sm/Xoetc8ggnQq4gN0+nJk18euK4bwHflRCC3+s/IiQb+YH drOblEYil1XOtTd9utSkQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:09jVcgow5bc=:Y2zyBvCwInrFVTaDBMMvzz +AVsdBMg49GcwEikL6fv0Ga8T3RAd00mOGcpyw4r5hyzJHcvo/4Mlk4Wx8zGylKNDwXxB//P6 rlinrYSxHInLWC6mu4qIDfM/G7CsuvweP6MshCx1EjZ7gOjs2uRORIoFLKqKXc+8INa0frcF4 86D4GkGA1V1nOw9f/CZLIUZNysAfm/BIjilRynNAMy71TCoAzekr+cZuuYP7fIJac/krHvTkv m4ta6AJ6KoWoj57MsV3RHHcpGmbFmeXtHfE0FOH70soo0R//GeJ+Op49JhiNzq3y6I9oNTHfi ZXis1OmzV0xFSsenKflA4p/Xm7K+ltfPTw55jTSEbKIJQXT+OkP6rZNl1Ouc+lPmqjDRZiUz9 So1MXywsM5EMLV9TrpdMEgEnBn6q9C6Y4J1g2m4QsKuefSzDMWY5gujbhochoBu0GiQ3G7+1q Ryih39PUqbPoAFNlJ2Cm5mRhtR1fyjp8hrzeWVnm3O+mdtfmBUw7NQwwR8pj/+wZiHfiD/piZ 17UzwW4kAszivfaKZ9TsdIZP6FW1/iy3+t3vYqxVqV1Kt6G2GVBWNWOf7p6m4TxkilvMRDq6f WWfPGUPrGEPfYFTE54XOGLiXkY/uzxo/YekaQmkxHGHJXcj98MvMHy43s2jPzrpqgLU6kfXmQ gs9FbM6C7rggFnLQBfX+UM8BRmIiejBKPmAVQ9LbRMMqv0jYoCl2XozcuoZqwj+vglZ8SFmW2 GET3YprpejeEqTo/7zHEX7cKd+i6eOM2J3UC1leR0yOkv+U9BTJ1hZKHLYYgehR5dD9ZUus52 wLf9dlw
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8YcaoaYTwxtoiUOJITeVsvRI3Gs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jun 2017 05:55:37 -0000

On 2017-06-15 20:28, Bob Hinden wrote:
> .. > I agree.
> 
> It also seems to me that having implementations "fail noisily in response to bad or undefined inputs" is a great formula to making implementations very fragile and consequently very easy to attack.  Overall, I think the approach outlined in this draft would not have allowed us to build the current Internet.
 > ...

There's a distinction between failing as in "catching fire and 
exploding" (bad) and "signalling an error and not processing a request" 
(what Martin is describing).

> Bob
> 
> p.s. The file name chosen for this draft appears to be a good example of stepping on the toes of those who came before, instead of standing on their shoulders.  See: http://wiki.c2.com/?ShouldersOfGiants

It was an excellent way to get attention. I think it's excellent that we 
are having this discussion.

Best regards, Julian


From nobody Fri Jun 16 00:50:49 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3B83131570 for <ietf@ietfa.amsl.com>; Fri, 16 Jun 2017 00:50:48 -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 Hje9WNUTLCfO for <ietf@ietfa.amsl.com>; Fri, 16 Jun 2017 00:50:46 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1447131586 for <ietf@ietf.org>; Fri, 16 Jun 2017 00:50:42 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id t87so25750022ioe.0 for <ietf@ietf.org>; Fri, 16 Jun 2017 00:50:42 -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=XrIrF0swI+QmK57U1Q8gRCODvrwU8GH86XmhmRghmSk=; b=altfJnti/yEazBbCSlFbLmS5+o0ZaOvJN5+NY4HmuOlmDbNYPZSuHSvWyAOYRNVp1w ktSOtMA2thsPyqmJCKfdq7r6BlbJtY9av27EoNNqMzxIlAFEFFC/YeenrP4KoGs7Boc5 4uI6yhvtlym0kXSn3sEx5fTjUVbAlgyu5qJi0s2MNbEo5Gnm06pggFL3CdQJ/Fn1yVOm ip7UaLjmZ9bs4Z5aF3/AcV7m3M9z8VGjYaQ6NTGSG8ZGblJpB8Ye7PAftXaM6b3MjHTG fg/X7DuOduNU2vEdoqnx7lLyJweCzpD3LXSCnkYjqSC6osi1BOAF1hnxLAQXnvevpi9w v4tw==
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=XrIrF0swI+QmK57U1Q8gRCODvrwU8GH86XmhmRghmSk=; b=bTE9wEBmlTjWDIBVPNVq55R29Fx0Y5su6pKAW3TEf584NhO3Igj4ftqP4XhHdeeS3d LHWzIg4+AGeqWhzqtj7xmhIDsK/7TG2jDJyNtsOTQ96QU0Q/5KmkRIOKu92/2qKfHL4C XxqNR/k4qUf6X0rli3utuv+h08TLAZzpTbfvWBVLpBxrxQ7A4IbZzajPkAlC0YtEFc3S kuUwHdsoE3MZH3J8BuGL9G+jYDMNkoLnkbQoIT+pcwiCFnNTARuGHITLGP/UcM1lUXVX I0iStEa9E7bVUNbILXv3Dlb1XvfT3wsFAO2ooxXwpkLZrmLbdBpgA9SEuujpFCHO+jTg xn2g==
X-Gm-Message-State: AKS2vOz6dR2iU1+srUEEWt3IvFJH1rKhnmoDleA6iu+e/L5wW37TEpRs Cn475IlFgM7hHbvy
X-Received: by 10.107.56.137 with SMTP id f131mr9103212ioa.86.1497599442024; Fri, 16 Jun 2017 00:50:42 -0700 (PDT)
Received: from ?IPv6:2406:e001:5078:1:28cc:dc4c:9703:6781? ([2406:e001:5078:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 137sm1435313itw.14.2017.06.16.00.50.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 16 Jun 2017 00:50:41 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: Julian Reschke <julian.reschke@gmx.de>, Bob Hinden <bob.hinden@gmail.com>
Cc: IETF <ietf@ietf.org>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com> <6f9a0398-7862-3c71-9b0f-0f8bd95ff277@gmx.de>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <3f20f07b-3e2b-4457-7578-39452a54eb3d@gmail.com>
Date: Fri, 16 Jun 2017 19:50:47 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <6f9a0398-7862-3c71-9b0f-0f8bd95ff277@gmx.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Bs2GsZ-5z9Gzb3OjynrIQFd7_Ps>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jun 2017 07:50:49 -0000

On 16/06/2017 17:55, Julian Reschke wrote:
> On 2017-06-15 20:28, Bob Hinden wrote:
>> .. > I agree.
>>
>> It also seems to me that having implementations "fail noisily in response to bad or undefined inputs" is a great formula to making implementations very fragile and consequently very easy to attack.  Overall, I think the approach outlined in this draft would not have allowed us to build the current Internet.
>  > ...
> 
> There's a distinction between failing as in "catching fire and 
> exploding" (bad) and "signalling an error and not processing a request" 
> (what Martin is describing).

That isn't obvious to the casual reader. But anyway, if you are under DDOS
attack, signalling an error rather than just releasing the mbuf may be all
the difference between system failure and survival*. I think it's very
dangerous to generalise.

    Brian

*That's why I often delete emails unread & unanswered :-)

> 
>> Bob
>>
>> p.s. The file name chosen for this draft appears to be a good example of stepping on the toes of those who came before, instead of standing on their shoulders.  See: http://wiki.c2.com/?ShouldersOfGiants
> 
> It was an excellent way to get attention. I think it's excellent that we 
> are having this discussion.
> 
> Best regards, Julian
> 


From nobody Fri Jun 16 03:04:28 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 EF4BA1317AE for <ietf@ietfa.amsl.com>; Fri, 16 Jun 2017 03:04:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 e8ukI7Cf35lf for <ietf@ietfa.amsl.com>; Fri, 16 Jun 2017 03:04:24 -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 E6E02129B43 for <ietf@ietf.org>; Fri, 16 Jun 2017 03:04:24 -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 boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v5GA3fml016699 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 16 Jun 2017 03:03:42 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: Christian Huitema <huitema@huitema.net>, ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com> <be856ef3-7bef-244e-bf94-b0af1f1ba99b@huitema.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <38132d0d-2e2a-e63e-f35d-7f4f3ad72990@isi.edu>
Date: Fri, 16 Jun 2017 03:03:41 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <be856ef3-7bef-244e-bf94-b0af1f1ba99b@huitema.net>
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/diYuEEgbJu4FSQCKpEzdnHRdJI8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jun 2017 10:04:26 -0000

On 6/15/2017 11:35 AM, Christian Huitema wrote:
> Martin describes a very real failure mode. Implementations deviate from
> the standard, gain market share as the deviations are happily tolerated,
> and then prevent standard evolution that would contradict their own
> "extensions". Martin gives examples of that happening with JSON.
Agreed.

It's very important to separate errors that diverge from specification
details from reasonable "wiggle room" created by specification gaps. The
Postel principle addresses the latter, but was never intended to
accommodate the former.

Joe


From nobody Fri Jun 16 03:07:25 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 7BCBD1317B7 for <ietf@ietfa.amsl.com>; Fri, 16 Jun 2017 03:07:23 -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, 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 53jsNZLRJ7mN for <ietf@ietfa.amsl.com>; Fri, 16 Jun 2017 03:07:21 -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 DD2911317B5 for <ietf@ietf.org>; Fri, 16 Jun 2017 03:07:21 -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 boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v5GA6uMf017019 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 16 Jun 2017 03:06:57 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: Julian Reschke <julian.reschke@gmx.de>, Bob Hinden <bob.hinden@gmail.com>,  Brian Carpenter <brian.e.carpenter@gmail.com>
Cc: IETF <ietf@ietf.org>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com> <6f9a0398-7862-3c71-9b0f-0f8bd95ff277@gmx.de>
From: Joe Touch <touch@isi.edu>
Message-ID: <568db7a9-7c34-36ed-1187-98b374be3164@isi.edu>
Date: Fri, 16 Jun 2017 03:06:56 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <6f9a0398-7862-3c71-9b0f-0f8bd95ff277@gmx.de>
Content-Type: multipart/alternative; boundary="------------B24F3F5F455F7B792D533F4B"
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/LLSxCRKKjRAFstd4Y8COYb8Agr0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jun 2017 10:07:23 -0000

This is a multi-part message in MIME format.
--------------B24F3F5F455F7B792D533F4B
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit



On 6/15/2017 10:55 PM, Julian Reschke wrote:
>> p.s. The file name chosen for this draft appears to be a good example
>> of stepping on the toes of those who came before, instead of standing
>> on their shoulders.  See: http://wiki.c2.com/?ShouldersOfGiants
>
> It was an excellent way to get attention.
Not necessarily the attention you seek, though.

> I think it's excellent that we are having this discussion. 
The utility of clarifying misconceptions in this doc is clear,
especially if they're shared by others.

Then again, some of us get paid to teach. ;-)

Joe

--------------B24F3F5F455F7B792D533F4B
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 6/15/2017 10:55 PM, Julian Reschke
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:6f9a0398-7862-3c71-9b0f-0f8bd95ff277@gmx.de">
      <blockquote type="cite" style="color: #000000;">p.s. The file name
        chosen for this draft appears to be a good example of stepping
        on the toes of those who came before, instead of standing on
        their shoulders.  See: <a class="moz-txt-link-freetext"
          href="http://wiki.c2.com/?ShouldersOfGiants"
          moz-do-not-send="true">http://wiki.c2.com/?ShouldersOfGiants</a>
        <br>
      </blockquote>
      <br>
      It was an excellent way to get attention.</blockquote>
    Not necessarily the attention you seek, though.<br>
    <br>
    <blockquote type="cite"
      cite="mid:6f9a0398-7862-3c71-9b0f-0f8bd95ff277@gmx.de"> I think
      it's excellent that we are having this discussion.
    </blockquote>
    The utility of clarifying misconceptions in this doc is clear,
    especially if they're shared by others.<br>
    <br>
    Then again, some of us get paid to teach. ;-)<br>
    <br>
    Joe<br>
  </body>
</html>

--------------B24F3F5F455F7B792D533F4B--


From nobody Fri Jun 16 11:10:13 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 D4AC5128E19; Fri, 16 Jun 2017 11:10:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 2ZfuxqUViMLL; Fri, 16 Jun 2017 11:10:02 -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 72558127137; Fri, 16 Jun 2017 11:10:02 -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 1dLvh3-0009YP-BP; Fri, 16 Jun 2017 14:10:01 -0400
Date: Fri, 16 Jun 2017 14:09:55 -0400
From: John C Klensin <john-ietf@jck.com>
To: nalini.elkins@insidethestack.com, vmeet@ietf.org, ietf@ietf.org
Subject: Re: [vmeet] Remote Participation Hubs
Message-ID: <51060E29D18DE784CEE290A0@PSB>
In-Reply-To: <1280323857.13113587.1497538214458@mail.yahoo.com>
References: <1280323857.13113587.1497538214458.ref@mail.yahoo.com> <1280323857.13113587.1497538214458@mail.yahoo.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/CvlxvhY9kA4ZHSb_NjhDeTL6MRc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 16 Jun 2017 18:10:05 -0000

--On Thursday, June 15, 2017 14:50 +0000
nalini.elkins@insidethestack.com wrote:

> All,
> 
> We have submitted the first of three drafts discussing Remote
> Hubs.   Please provide comments on the VMEET list.
> 
> Three types of remote hubs are defined.  Each has its own
> characteristics.
> 
>   - Remote Participation Hubs
>   - Remote Viewing Hubs
>   - Enduring Local Meetups
> 
> The first document defines a Remote Participation Hub (RPH).
> Other documents are coming to define the other types of hubs.
> A common structure of sections will be used as far as possible
> for all hub types.
>...

Nalini,

While I admire your energy and desire to more forward on all
fronts at once, I think the effort to get better and more
extensive remote participation would be best pursued by your
concentrating on Remote Viewing Hubs (and local discussions,
etc., as needed) and Local Meetings (no matter how enduring or
persistent) and letting Remote Participation Hubs go for a
while, perhaps returning to them after experience accumulates
and our knowledge and tools improve.

I have several reasons for that conclusion, some of which
overlap John Leslie's comments (which I will try to avoid
duplicating).   The note below hits just a few high points of
special concern to me before moving to the conclusion implied by
the previous paragraph.

>From one perspective, my problems start with an interesting
assertion in the Introduction to the I-D: 

	"A Remote Participation Hub is functionally equivalent
	to an IETF face-to-face meeting."

"Functionally equivalent" implies the ability to attend informal
sessions like the Newcomper's Meet and Greet and to have
spontaneous discussions in the halls, over lunch, and at events
like Bits-and-Bytes with subsets of the community that are less
homogeneous than Remote Hubs will tend to be; to get an
introduction (if needed) and have informal conversations
(restaurants, halls, informal meeting spaces, coffee shops,
bars) with WG Chairs, ADs, document authors or editors, or
others; to grab an author at the end of a WG session (or have
the author grab you) to continue a discussion; and so on.  Even
though some of the text later in the document can be seen as
qualifying that very broad equivalence statement, at least at
the current state of the technology and our procedures claiming
a remote hub is "functionally equivalent" to our unified f2f
meetings (or even could be) falls into the "you must be kidding"
category.

Moreover, while we've done much better in some WGs and at some
meetings than others, we still haven't got good and predictable
queue management for questions and comments by individual remote
participants.  Meetecho has decent (and improving) facilities
for that, but we have a long way to go to sort out the human
factors of balancing multiple in-room queues, remote interactive
queues, jabber input, the effects of various kinds of delays
between a comment and a question about it, and so on in a way
that is fair to everyone.  

If we have to combine the present situation and its challenges
with in-Hub-room queues, we have, AFAICT, two options ( think
the Meetecho team has reached much the same conclusion).  We can
put everyone in front of their own laptops, which forces the use
of headsets and complicates the bandwidth and other facility
issues (and makes some of your Section 4.6.3 inapplicable), or
we can set up in-room queues and a local queue manager or
moderator (perhaps the coordinator, perhaps not, but, if there
are parallel WGs being covered by the remote hub, we need at
least one each).   The latter raises more questions: how does a
WG Chair prioritize the third person in line in Hub#1 versus the
second person in line in Hub #2, versus in-room participants and
standalone remote participants?  Is the in-room queue manager
accountable to the WG Chair(s) or responsible ADs and how?   

If there is disruption in the remote hub, even someone becoming
aggressive in the microphone line or trying to control it, is a
remote hub coordinator or other leader authorized to control
that (or harassment, which the draft mentions) in the name of
the IETF?    Are their representatives of the ombudsteam present
and, if not, how is RFC 7776 interpreted and by whom?  What is
the accountability model there?  Are remote hub coordinators and
any necessary additional moderators covered by the same
insurance that, I believe, extends to WG Chairs even if the IESG
has no role in appointing them?

Is it reasonable and appropriate to put all of those decisions
under the control of whomever is participating in the remote
hob, or a sponsoring company, as your draft seems to suggest?
Does that provide adequate context and protection of the IETF
consensus process?

If a remote hub is open only to employee of the hosting
organization, do we continue to pretend that everyone
participating at the hub is participating as an individual?

And so on...

While I agree with John Leslie that the document is probably
overspecified in at least some places, none of the issues and
questions above are really addressed and there are probably many
more omissions.  Some imply a requirement for significant
training of WG Chairs and RPH coordinators (and perhaps
procedures (above and beyond "you don't get to do that again")
for how non-conforming behavior should be handled; others
involve at least a review and probably changes in important IETF
procedures.    While I believe we can sort them out, I note,
first, that we still don't have the much more simple case of
individual remote participants working smoothly and that remote
participation hubs raise a collection of new issues, and that
bandwidth spent on these kinds of issues (at least for the IETF
participant majority who don't have too much time on their
hands) intrudes on getting technical work done and/or on other
procedural (especially remote participation) refinements.

Is the community really ready to review (and possibly reopen or
amend) RFCs 2026, 2418, 7282, 7776, and perhaps other documents
to identify situations in which people meeting as a group
without the usual accountability structures are in place could
turn into issues?

If for no reason than to reduce the risk of disrupting work to
improve existing forms of remote participation, I suggest it is
in the community's best interests to adopt something of a "one
step at a time" attitude and put this aside 

Again, I'm strongly committed to remote participation.
Personally, I seem to be participating remotely more often than
I attend f2f meetings these days, which definitely motivates me.
But Remote Participation Hubs that are driven more by enthusiasm
than by careful understanding of issues and community consensus
about how to handle them just do not feel like a useful way
forward at this particular time.

 best,
    john


 



From nobody Fri Jun 16 16:32:58 2017
Return-Path: <agenda@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 55F09129427; Fri, 16 Jun 2017 16:32:49 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Agenda <agenda@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: 99all@ietf.org, ietf@ietf.org
Subject: IETF 99 Preliminary Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: IETF Agenda <agenda@ietf.org>
Message-ID: <149765596926.24039.3258268821492667190.idtracker@ietfa.amsl.com>
Date: Fri, 16 Jun 2017 16:32:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/YSRVFoElLKm2hYj4avadiTeQwLc>
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, 16 Jun 2017 23:32:49 -0000

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

The IETF 99 Preliminary Agenda has been posted. The final agenda will be published on Friday, June 23, 2017. 

https://datatracker.ietf.org/meeting/99/agenda.html 
https://datatracker.ietf.org/meeting/99/agenda.txt

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

Don’t forget to register for these exciting IETF 99 events!

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

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

Hackathon 
	Signup: https://www.ietf.org/registration/ietf99/hackathonregistration.py
	More information: http://ietf.org/hackathon/99-hackathon.html 
	Keep up to date by subscribing to: 
	https://www.ietf.org/mailman/listinfo/hackathon

Code Sprint
	Signup: https://trac.tools.ietf.org/tools/ietfdb/wiki/IETF99SprintSignUp
	More information: https://trac.tools.ietf.org/tools/ietfdb/wiki/IETF99Sprint


From nobody Sat Jun 17 05:24:39 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 36BA6129484; Sat, 17 Jun 2017 05:24:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.801
X-Spam-Level: 
X-Spam-Status: No, score=-4.801 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, 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 vcW6ks1O7jGw; Sat, 17 Jun 2017 05:24:29 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0130.outbound.protection.outlook.com [104.47.40.130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D41DF12947C; Sat, 17 Jun 2017 05:24:28 -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=oqRAXOMgnPDd57ozvyHwvVgJE28k8Cc96rzO0vcBXD8=; b=BAXbPYKHxCbukIdmHn6Rig7EtkewjZ+FM8JcjIWofNhGAUYFf8sM6iN7uJxYtzhYQmJbEFdzjSXlbFNOmDBIfpqhYsoREbonQTEjuA3LDjn10gOxjV8ZlB6WYU0ATGNmF9VL4OKk+AdlOpIBdiI7A0nxMj4eh61WlKOAnTTfUPU=
Received: from BN6PR03MB2612.namprd03.prod.outlook.com (10.173.143.135) by BN6PR03MB2610.namprd03.prod.outlook.com (10.173.143.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1178.14; Sat, 17 Jun 2017 12:24:20 +0000
Received: from BN6PR03MB2612.namprd03.prod.outlook.com ([10.173.143.135]) by BN6PR03MB2612.namprd03.prod.outlook.com ([10.173.143.135]) with mapi id 15.01.1143.018; Sat, 17 Jun 2017 12:24:20 +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-tcpm-dctcp.all@tools.ietf.org" <draft-ietf-tcpm-dctcp.all@tools.ietf.org>
Subject: Gen-ART Last Call review of draft-ietf-tcpm-dctcp-07
Thread-Topic: Gen-ART Last Call review of draft-ietf-tcpm-dctcp-07
Thread-Index: AdLnXhfXFS3sUvXFRwmmocCfhO+vxA==
Date: Sat, 17 Jun 2017 12:24:20 +0000
Message-ID: <BN6PR03MB2612D009D446DBCF899488DBADC60@BN6PR03MB2612.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: [77.126.4.95]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN6PR03MB2610; 7:fR/9kwD3AxsWvfAUtb5ZsPjc1CkzMStVZpzztCmgBwxfibRl6/kbkHGe9sVC0VGH5vGs5d92E/3CztzKb3rxbRwgBAZsAQbKvma+hm1bxFCp7mywIk/DnMcjXXkU38oVf/Y0cgdgyPBhsNvu48JfbDf4aLUd9LemHG4S441XC7OGziDUt5NEIm73YM+zOGOnQeB6lH0UWvAcj9hVdzZPNirnveOfbLSqTD2gcsswxPu+Q8CLOAxIZ6nbbyETH6W8nGUkt3UiCk/C/3JAs/ccxVNTbhemxazY4FEOCpLKmhJPC8A+RYT30qP1VbwJbHTs2MtvleaH7fL3YgahQyk5Upn8xoq6Uqx6gknbtWiepbRzOC27zoYujKTgptw3cH3Tl2xC6j86zyCfxrtCR0liyeLD0qTjDRo4iuzKyFx222qSkCwHrOgJi3xR+BGNs68U7wSjY/gpyBrAoLvZnJ0FFJdhhLlAvq1C7pMaycZMPL919vhYhCYt42mvbmjU+EZC2qgbLzDDipIHaCT52ZHIR34Wdpt2u7PIejKLCXED6vV3V5smqDPeWJURg6soXZVsMZPGadU6ZqH17A/c9DNfjpX/PQelOGqQE7lVUNEysLxILaDwNwJ2kLMfkxB+irnU8H40EOSt7pgcIYg0wMeCVJ8EAw7uMajUCCZ29hButZ0iSkDXmzr4WvBRQ7hFW8RpntAkY9Yn44yf5PFXtkcS20oTzQD6vAjJrtt4DOsjLuMrKEwVwJ7lK+vcAx5h3RNcIH+aC6AXDw3tmOGnl1EAIFHn13I4ZDGOmavoDFrQmwp57Q5exP6HRNWp6vYintV7
x-ms-office365-filtering-correlation-id: cdf24744-2677-4a6e-0e3e-08d4b57bc7e0
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:BN6PR03MB2610; 
x-ms-traffictypediagnostic: BN6PR03MB2610:
x-microsoft-antispam-prvs: <BN6PR03MB26105F3F4A4ABE80AC52AFB8ADC60@BN6PR03MB2610.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(3002001)(6055026)(61426038)(61427038)(6041248)(20161123564025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123560025)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN6PR03MB2610; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN6PR03MB2610; 
x-forefront-prvs: 034119E4F6
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39850400002)(39400400002)(39450400003)(39410400002)(39860400002)(39840400002)(377424004)(7736002)(2906002)(5640700003)(10290500003)(14454004)(2501003)(3846002)(6116002)(81166006)(102836003)(55016002)(478600001)(3660700001)(3280700002)(9686003)(74316002)(6306002)(53936002)(77096006)(189998001)(38730400002)(99286003)(110136004)(305945005)(66066001)(6916009)(122556002)(2351001)(5005710100001)(86612001)(8990500004)(230783001)(33656002)(5660300001)(6436002)(50986999)(54356999)(25786009)(86362001)(6506006)(54906002)(8936002)(4326008)(8676002)(7696004)(10090500001)(2900100001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR03MB2610; H:BN6PR03MB2612.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Jun 2017 12:24:20.3005 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR03MB2610
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/H3wE19FdplLNCuP6cder9l3Bamk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jun 2017 12:24:31 -0000

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-tcpm-dctcp-07
Reviewer: Orit Levin
Review Date: 2017-06-17
IETF LC End Date: 2017-06-15
IESG Telechat date: 2017-06-22

Summary: This draft is ready for publication with nits:

Section 3.2=20
"... an implementation may choose to send two ACKs, ..." Suggest changing "=
may" to either "can" or "MAY", as fitted.

Section 3.4=20
"... like ssthresh must be changed ..." Suggest changing "must" to either "=
need" or "MUST", as fitted.

Section 3.5=20
"... may result in..." Suggest changing "may" to "might".

Section 4.1=20
"An implementation should decide when to use DCTCP." Suggest replacing "sho=
uld decide" with "needs to know".

"... there is additional management and configuration overhead required..."=
 suggest replacing with "additional management and configuration functional=
ity is needed".

"Potential solutions ..." suggest replacing "Potential" with either "Possib=
le" or "Known".=20

Section 4.2
"... a scaled updated must ensure ..." Suggest replacing "must" with either=
 "MUST" or "needs to".

Section 7
"... the first versions..." Suggest replacing with "initial drafts".

Section 8
"Since most servers run virtualized in datacenters, in addition ..." Sugges=
t replacing with "Beyond the security considerations related to virtual ser=
vers, "

Thanks,
Orit.


From nobody Sat Jun 17 07:18:29 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 70BF7129ABE for <ietf@ietfa.amsl.com>; Sat, 17 Jun 2017 07:18:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level: 
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 SSTssclYMMHC for <ietf@ietfa.amsl.com>; Sat, 17 Jun 2017 07:18:25 -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 7B111129ABD for <ietf@ietf.org>; Sat, 17 Jun 2017 07:18:25 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:6:78cf:d9ff:fe94:ac02] (unknown [IPv6:2001:1488:fffe:6:78cf:d9ff:fe94:ac02]) by mail.nic.cz (Postfix) with ESMTPSA id E0FCF611AE for <ietf@ietf.org>; Sat, 17 Jun 2017 16:18:22 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1497709102; bh=uCEVK+Br4OjprrFt3xLMlxi0f5j3pAuseIcYwMqDduw=; h=To:From:Date; b=pXxmNpOLuV92Qxw1jU5hNN2wQMavBHkyIjyzBnG3p50mouNfM+WqVzhbTtj/QV/XL Z4n4dPD6+gGPdX5vrYn/KyY2VLaqF7xVZpbonH5PD9N1eNbBiSaSZcTk1oxMHg4wBK AkXQn1uY3aaBJVq/MM0yHXgWEjm5AkBA4EcFxjkU=
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu>
From: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>
Organization: CZ.NIC
Message-ID: <f69679ba-f69c-b063-943f-6994489c526d@nic.cz>
Date: Sat, 17 Jun 2017 16:18:22 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu>
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/iDKOypvIzx2zflt9rtDsXXwugXw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jun 2017 14:18:27 -0000

On 15.6.2017 00:31, Joe Touch wrote:
> On 6/14/2017 8:41 AM, Petr Špaček wrote:
>> To sum it up, decision what is acceptable and what is unacceptable
>> should be in protocol developer's hands.
> That should be in the specification.
> 
> What the specification leaves open, implementations should respect and
> honor as allowed.

This is exactly the point where our opinions differ.
My point of view is that specification should clearly define extension
points and implementations should:
a) Use Postel's principle within defined 'extension' points.
b) Treat any deviation from documented protocol (including non-defined
aspects of protocol outside of extension points) as an error.


Nice set of reasons for being strict when receiving messages is
described in the following article:

"A Patch for Postel's Robustness Principle",
Len Sassaman, Meredith L. Patterson, Sergey Bratus,
2012 IEEE S&P Journal,
http://langsec.org/papers/postel-patch.pdf

Also, the whole web http://langsec.org/ is an interesting read.

-- 
Petr Špaček  @  CZ.NIC


From nobody Sat Jun 17 07:26:52 2017
Return-Path: <paul@nohats.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 1960A1294F7 for <ietf@ietfa.amsl.com>; Sat, 17 Jun 2017 07:26:51 -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, 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=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O2ObbMvRUR5S for <ietf@ietfa.amsl.com>; Sat, 17 Jun 2017 07:26:48 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 2A85B120725 for <ietf@ietf.org>; Sat, 17 Jun 2017 07:26:48 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3wqfgn22QMz7q; Sat, 17 Jun 2017 16:26:45 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1497709605; bh=LOXR03RQ4lPLaQBX3X0VvfHCYjgwDRHdLwKI8yfCmg4=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=WxEhD2lsO4CTp0tgACcwm+b1KiHGxZIGGCW58TOGXK9mNwP/cDK7kl7kXDOWvFoqQ f+D0wXPLp8f2UGUBfgjqU9ztqCN6ghHhPOoodx0Ddq1u3MfV73DsPyLX+pzxuGVYOq nxoQ13nNJ7ASB5fL3Ks0oQrZHF+9vxbKHlzaBdWg=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id kAySH1o-8xnu; Sat, 17 Jun 2017 16:26:44 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Sat, 17 Jun 2017 16:26:44 +0200 (CEST)
Received: from [25.102.150.185] (unknown [24.114.55.247]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bofh.nohats.ca (Postfix) with ESMTPSA id 30443452D36; Sat, 17 Jun 2017 10:26:43 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 30443452D36
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
From: Paul Wouters <paul@nohats.ca>
X-Mailer: iPhone Mail (14F89)
In-Reply-To: <f69679ba-f69c-b063-943f-6994489c526d@nic.cz>
Date: Sat, 17 Jun 2017 10:26:41 -0400
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz>
To: =?utf-8?Q?Petr_=C5=A0pa=C4=8Dek?= <petr.spacek@nic.cz>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ejM3oxAYJEO9KV8fUEIMQXussRU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jun 2017 14:26:51 -0000

On Jun 17, 2017, at 10:18, Petr =C5=A0pa=C4=8Dek <petr.spacek@nic.cz> wrote:=

>=20
>=20
> This is exactly the point where our opinions differ.
> My point of view is that specification should clearly define extension
> points and implementations should:
> a) Use Postel's principle within defined 'extension' points.
> b) Treat any deviation from documented protocol (including non-defined
> aspects of protocol outside of extension points) as an error.

So abort all your HTML pages from loading?=20

b) is an error that should be handled in a Postel way and the RFC should
be updated to address the issue. Then maybe years down the line you can be m=
ore strict on the failure.

Also the consequences of being strict can be worse. Should a TLS connection f=
ail if the nonce size for the integrity algorithm is too weak? Will the resu=
lt be a retry using plaintext offers greater risks? What if the connection i=
s for a public webpage? What if it is for a nuclear control channel?

if things were an easy black and white, we wouldn't have this discussion eve=
ry couple of years.

Paul


From nobody Sat Jun 17 16:15:37 2017
Return-Path: <jtw@csail.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 6A7721243F6 for <ietf@ietfa.amsl.com>; Sat, 17 Jun 2017 16:15: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 lV4_y-0nbD1E for <ietf@ietfa.amsl.com>; Sat, 17 Jun 2017 16:15:35 -0700 (PDT)
Received: from ana-server.csail.mit.edu (ana-server.csail.mit.edu [18.26.1.3]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 014BF1242F7 for <ietf@ietf.org>; Sat, 17 Jun 2017 16:15:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ana-server.csail.mit.edu (Postfix) with ESMTP id A7BC9BCF36C; Sat, 17 Jun 2017 19:15:33 -0400 (EDT)
X-Virus-Scanned: amavisd-new at ana-server.csail.mit.edu
Received: from ana-server.csail.mit.edu ([127.0.0.1]) by localhost (ana-server.csail.mit.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8DnpbvdXhflC; Sat, 17 Jun 2017 19:15:31 -0400 (EDT)
Received: from callisto-vii.venice.schlepp.org (cpe-104-174-114-209.socal.res.rr.com [104.174.114.209]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ana-server.csail.mit.edu (Postfix) with ESMTPSA id 96A57BCF331; Sat, 17 Jun 2017 19:15:30 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
From: John Wroclawski <jtw@csail.mit.edu>
In-Reply-To: <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com>
Date: Sat, 17 Jun 2017 16:15:25 -0700
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, heasley <heas@shrubbery.net>, Joe Touch <touch@isi.edu>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A1D2966-0ED0-4BE9-9EFF-3870D227C4B8@csail.mit.edu>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X362yoEiS5ZX8DEqWjQbK6sWnKU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 17 Jun 2017 23:15:36 -0000

> On Jun 14, 2017, at 3:44 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:
>=20
> On 15/06/2017 08:20, Joel M. Halpern wrote:
> ...
>> I would be very unhappy to see us take the lesson from cases where we=20=

>> were sloppy to be that we should tell everyone to have their=20
>> implementations break at the slightest error.
>=20
> Indeed. We need implementations to be as robust as possible. [=E2=80=A6]=

>=20
> Looking at the core of the draft:
>=20
>      Protocol designs and implementations should fail noisily in
>      response to bad or undefined inputs.
>=20
> that seems a very reasonable principle for *prototype* and
> *experimental* implementations, and a lousy one for production
> code, where the response to malformed messages should be much
> more nuanced;=20

+1

Put another way -

the goal of a _specification_ is to coordinate the actions of multiple, =
independent implementors, across different circumstances, environments, =
depths of knowledge, etc. etc. etc.

The goal of an _implementation_ is to serve its users as best as it can =
when that coordination is not quite perfect.

These are decidedly not the same thing.

cheers, -john





From nobody Sat Jun 17 23:05:13 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 6415A127180 for <ietf@ietfa.amsl.com>; Sat, 17 Jun 2017 23:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mP20Tm6T4LvP for <ietf@ietfa.amsl.com>; Sat, 17 Jun 2017 23:05:10 -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 EFD60126DCA for <ietf@ietf.org>; Sat, 17 Jun 2017 23:05:09 -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 1dMTKZ-0006AU-Rd; Sun, 18 Jun 2017 06:05:04 +0000
Date: Sun, 18 Jun 2017 15:05:02 +0900
Message-ID: <m2a8553k6p.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: John Wroclawski <jtw@csail.mit.edu>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, heasley <heas@shrubbery.net>, ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
In-Reply-To: <2A1D2966-0ED0-4BE9-9EFF-3870D227C4B8@csail.mit.edu>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <2A1D2966-0ED0-4BE9-9EFF-3870D227C4B8@csail.mit.edu>
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/jJV6demikyKQ_LuciwQ-OdiujKk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jun 2017 06:05:11 -0000

>> that seems a very reasonable principle for *prototype* and
>> *experimental* implementations, and a lousy one for production
>> code, where the response to malformed messages should be much
>> more nuanced; 
> 
> +1
> 
> Put another way -
> 
> the goal of a _specification_ is to coordinate the actions of
> multiple, independent implementors, across different circumstances,
> environments, depths of knowledge, etc. etc. etc.
> 
> The goal of an _implementation_ is to serve its users as best as it
> can when that coordination is not quite perfect.
> 
> These are decidedly not the same thing.

the problem with do-gooder software is that

  when it tries and fails, you may or may not know it, but it is a real
  mess.  and usually the do-gooder receiver is blamed.

  when it succeeds, no one says thanks, and the incorrect sender goes on
  to find some other implementation to break.

at a minimum, the do-gooder receiver needs to notify the operator that
things are broken.

randy, with a respectful nod to erik naggum


From nobody Sun Jun 18 01:05:26 2017
Return-Path: <jaap@NLnetLabs.nl>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 114CB129426 for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 01:05:25 -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 GgCo-3gNu5bG for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 01:05:23 -0700 (PDT)
Received: from bela.nlnetlabs.nl (bela.nlnetlabs.nl [IPv6:2a04:b900::1:0:0: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 5C92712025C for <ietf@ietf.org>; Sun, 18 Jun 2017 01:05:23 -0700 (PDT)
Received: from bela.nlnetlabs.nl (localhost [127.0.0.1]) by bela.nlnetlabs.nl (8.15.2/8.15.2) with ESMTP id v5I859EL088610 for <ietf@ietf.org>; Sun, 18 Jun 2017 10:05:14 +0200 (CEST) (envelope-from jaap@NLnetLabs.nl)
Message-Id: <201706180805.v5I859EL088610@bela.nlnetlabs.nl>
To: ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
From: Jaap Akkerhuis <jaap@NLnetLabs.nl>
In-reply-to: <m2a8553k6p.wl-randy@psg.com>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <2A1D2966-0ED0-4BE9-9EFF-3870D227C4B8@csail.mit.edu> <m2a8553k6p.wl-randy@psg.com>
Comments: In-reply-to Randy Bush <randy@psg.com> message dated "Sun, 18 Jun 2017 15:05:02 +0900."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <88608.1497773109.1@bela.nlnetlabs.nl>
Date: Sun, 18 Jun 2017 10:05:09 +0200
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.2 (bela.nlnetlabs.nl [127.0.0.1]); Sun, 18 Jun 2017 10:05:14 +0200 (CEST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PQwjiwYMXD9oGqqkFnnBjymCHQ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jun 2017 08:05:25 -0000

 Randy Bush writes:

 > the problem with do-gooder software is that
 > 
 >   when it tries and fails, you may or may not know it, but it is a real
 >   mess.  and usually the do-gooder receiver is blamed.
 > 
 >   when it succeeds, no one says thanks, and the incorrect sender goes on
 >   to find some other implementation to break.

and thus completely ignoring the "be conservative what you send" part

	jaap


From nobody Sun Jun 18 01:25:54 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 E2A59129577 for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 01:25:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level: 
X-Spam-Status: No, score=-7.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_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 SjvGLYtz3mge for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 01:25:51 -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 EF07112025C for <ietf@ietf.org>; Sun, 18 Jun 2017 01:25:50 -0700 (PDT)
Received: from [192.168.1.26] (unknown [77.236.194.38]) by mail.nic.cz (Postfix) with ESMTPSA id 2495C62160 for <ietf@ietf.org>; Sun, 18 Jun 2017 10:25:49 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1497774349; bh=a+FFwsrGFGlaytsITwbgd3unOm85Jff3cGvImlKnMTQ=; h=From:To:Date; b=bikUukg3p1vCMJE00SuldeOc/3nhcXcJmVK7letWsaH4w7ii+qH35swGau3qOzR3v I4mZDGSeMBT8o0zhtuew8TwxQzHAYamAl+Hq1eezfXBIPJgPng81HiWtqerJDHXAEl vft09QlCLd+KWotFWm2TxpTFmtaG9sJNebl01UGM=
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca>
From: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>
Organization: CZ.NIC
To: ietf@ietf.org
Message-ID: <541d6631-c1f5-8916-8c00-73b9ff245aab@nic.cz>
Date: Sun, 18 Jun 2017 10:25:48 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca>
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/j1fxdSuQT2PLN3c1tF3lGiTlGKU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jun 2017 08:25:53 -0000

On 17.6.2017 16:26, Paul Wouters wrote:
> On Jun 17, 2017, at 10:18, Petr Špaček <petr.spacek@nic.cz> wrote:
>>
>>
>> This is exactly the point where our opinions differ.
>> My point of view is that specification should clearly define extension
>> points and implementations should:
>> a) Use Postel's principle within defined 'extension' points.
>> b) Treat any deviation from documented protocol (including non-defined
>> aspects of protocol outside of extension points) as an error.
> 
> So abort all your HTML pages from loading? 
> 
> b) is an error that should be handled in a Postel way and the RFC should
> be updated to address the issue. Then maybe years down the line you can be more strict on the failure.

Please let me clarify that can be reasonably applies only to new
protocols or new extensions of existing protocols. We do not have time
machine and I'm not proposing to break existing deployments...


> Also the consequences of being strict can be worse. Should a TLS connection fail if the nonce size for the integrity algorithm is too weak? Will the result be a retry using plaintext offers greater risks? What if the connection is for a public webpage? What if it is for a nuclear control channel?

To use your example, it might be better to refuse opening a "nuclear
control channel" if it is giving just false sense of security by using
nonce size 1 byte :-)

Now seriously:
If the protocol and strict approach to its implementation was specified
from the very begining (again, this is applicable to new development) we
could easily refuse to open connection because almost all
implementations would do the same, so incentive to fix it would be
significant.


> if things were an easy black and white, we wouldn't have this discussion every couple of years.
Sure. That is why I'm advocating for getting stricter and stricter from
now on.

I hope it clarifies the point. Also, please refer to langsec article
from the previous point, it has a lot to say about security reasons for
stricter approach.

-- 
Petr Špaček  @  CZ.NIC


From nobody Sun Jun 18 03:55:48 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 09DC3126CB6 for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 03:55:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 HT_5m-wUjLVb for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 03:55:45 -0700 (PDT)
Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::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 49E22120724 for <ietf@ietf.org>; Sun, 18 Jun 2017 03:55:45 -0700 (PDT)
Received: by mail-qt0-x22f.google.com with SMTP id c10so94732731qtd.1 for <ietf@ietf.org>; Sun, 18 Jun 2017 03:55:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=message-id:subject:from:to:cc:date:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=Llm49u1Twit1hfRyvGqPHPVUNmrxNVsnBE46eVy9jEc=; b=GBODE6h1w9dW9etw82ZtmSOr7BgzoI/VIW/r1zRLJSnUxcpHmkN0VK/ZRwHIsm9KD3 wN6pAsJCPnlJBsivXdxe0Lg7SFgGMO8Y0FqetrZCsxC39u8oEgUM0WNORYCAt5hPaAOF t5AHyjrxMrGXkrfXHXj3OFA/ezJPG3NmiyMvhBiumJkd+24IdLWSkOrSw30/ql2NHWM9 eewL7Wjw1JsgauO7HSczk5ToDX15TTZiarmzXvSTJjQrzSwe/cCs2Dgy7pCgT2JOCcKb QaNsfKrPihyjemems9x8+hbOUD+WkQeSRBmhbLZdie0vsZ16WlWK4aH7RW1En7/A2XNn FoKg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=Llm49u1Twit1hfRyvGqPHPVUNmrxNVsnBE46eVy9jEc=; b=EEH8Df0nNgfd7hpIJ5ombDzf2Z6KH9Jh0XHzwA1Kcy4AfI+rtiu4d1qGixKcUQAcBm bRoqiLdOmuytIo1w67WI78d/6jXhTVv4kqEEbOuTC5iFaxLxtcD4ZDgWYC863RtydQVZ NwHVEm5WlgEDkbDQL44bxIevIa3Xp9/x5xOEVZDFwIUybS0viUSt7Mgyia0r6WbEIclN kcY7Sh+2/Do7RFusmUivhF1Vw25E+L1BR6DGGIGSQXHxiWaIQ4e2uNX0b6m0/p8LAkbX Aii639CYca0Y0gKWHlm4PhjUt2JryLZuVH9KaOusbC3/52MYC2yceSM6RgZHeO3ss8VV +loQ==
X-Gm-Message-State: AKS2vOxEBG6JDqgAD3jqCR3hlCAXPiIEj21EGDhlEBeATeMmgzfptlgw 9waNZWHksdgzO3gV
X-Received: by 10.200.55.27 with SMTP id o27mr21976093qtb.120.1497783344401; Sun, 18 Jun 2017 03:55:44 -0700 (PDT)
Received: from sio_centos_lt ([147.178.6.131]) by smtp.googlemail.com with ESMTPSA id h54sm5226002qta.60.2017.06.18.03.55.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 18 Jun 2017 03:55:43 -0700 (PDT)
Message-ID: <1497783339.10304.9.camel@gmail.com>
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
From: Yoav Nir <ynir.ietf@gmail.com>
To: Petr =?UTF-8?Q?=C5=A0pa=C4=8Dek?= <petr.spacek@nic.cz>
Cc: ietf@ietf.org
Date: Sun, 18 Jun 2017 13:55:39 +0300
In-Reply-To: <541d6631-c1f5-8916-8c00-73b9ff245aab@nic.cz>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca> <541d6631-c1f5-8916-8c00-73b9ff245aab@nic.cz>
Organization: Dell-EMC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.12.11 (3.12.11-22.el7) 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nKtLbtwp0bs8dKPf_hibubDIcGI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jun 2017 10:55:47 -0000

On Sun, 2017-06-18 at 10:25 +0200, Petr Špaček wrote:
> 
> On 17.6.2017 16:26, Paul Wouters wrote:
> > On Jun 17, 2017, at 10:18, Petr Špaček <petr.spacek@nic.cz> wrote:
> >>
> >>
> >> This is exactly the point where our opinions differ.
> >> My point of view is that specification should clearly define extension
> >> points and implementations should:
> >> a) Use Postel's principle within defined 'extension' points.
> >> b) Treat any deviation from documented protocol (including non-defined
> >> aspects of protocol outside of extension points) as an error.
> > 
> > So abort all your HTML pages from loading? 
> > 
> > b) is an error that should be handled in a Postel way and the RFC should
> > be updated to address the issue. Then maybe years down the line you can be more strict on the failure.
> 
> Please let me clarify that can be reasonably applies only to new
> protocols or new extensions of existing protocols. We do not have time
> machine and I'm not proposing to break existing deployments...
> 

I don't think both Netscape and Microsoft wrote their browsers so that
they accepted very malformed HTML just because Postel said so. They
figured (probably correctly) that users would prefer a browser that
worked with all websites to a browser that worked with many websites. 

In fact being liberal in what you accept is a necessity for
implementations and any guidance we give to break the connection will be
ignored. 

Best we can do is to make both the sending and processing of protocol
messages clearly defined in our specs. So for example we should not say
"The Certificate Data field contains an X.509 certificate", but should
instead say "The Certificate Data field contains a DER-encoded X.509
certificate conforming to RFC 5280. The receiver MUST verify that the
content is valid DER and that all required fields are present."

This won't eliminate market forces, but at least it can reduce the cases
where different implementers interpreted the specification in a
different way.

Yoav


From nobody Sun Jun 18 04:48:12 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 2D75212704A for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 04:48:11 -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 eq3UeB7W9rnj for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 04:48:09 -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 A19EB1205D3 for <ietf@ietf.org>; Sun, 18 Jun 2017 04:48:08 -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 v5IBm4K5005276; Sun, 18 Jun 2017 13:48:05 +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 3wrC6D6CRfzDKBZ; Sun, 18 Jun 2017 13:48:04 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <1497783339.10304.9.camel@gmail.com>
Date: Sun, 18 Jun 2017 13:48:03 +0200
Cc: IETF <ietf@ietf.org>
X-Mao-Original-Outgoing-Id: 519479283.645984-59fac7ec1c23663861a7a6c0a9741c78
Content-Transfer-Encoding: quoted-printable
Message-Id: <BF7F578C-62B1-4302-AD79-01C6F0725C6C@tzi.org>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca> <541d6631-c1f5-8916-8c00-73b9ff245aab@nic.cz> <1497783339.10304.9.camel@gmail.com>
To: Yoav Nir <ynir.ietf@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_M_YE7WIN7KCbd01S9Jr8irPJ40>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jun 2017 11:48:11 -0000

On Jun 18, 2017, at 12:55, Yoav Nir <ynir.ietf@gmail.com> wrote:
>=20
> I don't think both Netscape and Microsoft wrote their browsers so that
> they accepted very malformed HTML just because Postel said so. They
> figured (probably correctly) that users would prefer a browser that
> worked with all websites to a browser that worked with many websites.=20=


Indeed, dumping the error messages on the human user would have been =
nonsensical.

Now assume for a second that HTTP had had a backchannel that would have =
allowed a browser to send error messages back to the server.  Of course, =
we don=E2=80=99t know whether browser implementer would have provided =
meaningful messages, and we don=E2=80=99t know whether server =
implementers would have collected them in a useful way.  And, of course, =
we also don=E2=80=99t know whether site authors would have had a look at =
these collected error messages.

Still, I think that this approach would have resulted in less soupifying =
of HTML than what actually happened.

What can we learn from this thought experiment?

When designing protocols, we can=E2=80=99t sustain the fiction that =
implementations will be compliant.
Instead, we have to think about what to do with the non-compliance that =
we=E2=80=99ll encounter.
And we have to think about ways that information about this can flow to =
a place where it can be acted upon.
(Or, preferably, where there actually are forces that make it likely =
that it *will* be acted upon.)

(Other points from the current discussion playing into this are:
=E2=80=94 be *definite* in what you accept =E2=80=94 I think we are =
getting better at that;
and
=E2=80=94 clearly identify (and envelope!) extension points =E2=80=94 =
still much work needed.
There was also a good discussion in the past that extension points need =
to be regularly exercised, or there will be problems at the time when =
they are actually needed.)

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


From nobody Sun Jun 18 11:01:48 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 63A92128CD5 for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 11:01:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 djUGg7KvSNkt for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 11:01:46 -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 03BE4127876 for <ietf@ietf.org>; Sun, 18 Jun 2017 11:01:45 -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 boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v5II1PSi005810 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 18 Jun 2017 11:01:26 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: Jaap Akkerhuis <jaap@NLnetLabs.nl>, ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <2A1D2966-0ED0-4BE9-9EFF-3870D227C4B8@csail.mit.edu> <m2a8553k6p.wl-randy@psg.com> <201706180805.v5I859EL088610@bela.nlnetlabs.nl>
From: Joe Touch <touch@isi.edu>
Message-ID: <3a0a263f-f3b4-1931-3c49-4fa1526658e5@isi.edu>
Date: Sun, 18 Jun 2017 11:01:24 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <201706180805.v5I859EL088610@bela.nlnetlabs.nl>
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/zmVYegH2BUVdjs9Rq2wTAyrBDW8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jun 2017 18:01:47 -0000

On 6/18/2017 1:05 AM, Jaap Akkerhuis wrote:
>  > the problem with do-gooder software is that
>  > 
>  >   when it tries and fails, you may or may not know it, but it is a real
>  >   mess.  and usually the do-gooder receiver is blamed.
>  > 
>  >   when it succeeds, no one says thanks, and the incorrect sender goes on
>  >   to find some other implementation to break.
>
> and thus completely ignoring the "be conservative what you send" part
No part of the Postel Principle says to ignore explicit errors.

The issue is how to treat something unexpected, and the implications
thereof.

If everything unexpected must be loudly rejected (as this doc claims), then:
a) specs will become unnecessarily detailed
b) implementations will be come unnecessarily detailed
c) receivers will be vulnerable to increased DOS attacks

The Postel Principle just tries to get the sender to avoid doing
something unexpected (because it could result in unexpected receiver
behavior), and to get the receiver to avoid over-reacting. It is, in a
sense, the dampener that enables practical protocol specification and
implementation.

IMO, it's somewhat an extension of Shannon's recognition that
communication is about symbol agreement, not semantics or intent.

Joe



From nobody Sun Jun 18 11:09:53 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 806EC128CD5 for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 11:09:52 -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, 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 5Bt_2MzQ7_-m for <ietf@ietfa.amsl.com>; Sun, 18 Jun 2017 11:09:45 -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 644FE127A90 for <ietf@ietf.org>; Sun, 18 Jun 2017 11:09:45 -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 boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v5II9VxJ007169 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Sun, 18 Jun 2017 11:09:33 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz>
From: Joe Touch <touch@isi.edu>
Message-ID: <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu>
Date: Sun, 18 Jun 2017 11:09:30 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <f69679ba-f69c-b063-943f-6994489c526d@nic.cz>
Content-Type: multipart/alternative; boundary="------------75B201712ECE0E74F2306F82"
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/XbliXAOd-ByIEjTHQzwVqWok4Kk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 18 Jun 2017 18:09:52 -0000

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

FWIW:

On 6/17/2017 7:18 AM, Petr Špaček wrote:
>> What the specification leaves open, implementations should respect and
>> honor as allowed.
> This is exactly the point where our opinions differ.
> My point of view is that specification should clearly define extension
> points and implementations should:
> a) Use Postel's principle within defined 'extension' points.
> b) Treat any deviation from documented protocol (including non-defined
> aspects of protocol outside of extension points) as an error.
You're asking for 10,000 page specifications and 10MB protocol
implementations that are vulnerable to attack.

> Nice set of reasons for being strict when receiving messages is
> described in the following article:
>
> "A Patch for Postel's Robustness Principle",
> Len Sassaman, Meredith L. Patterson, Sergey Bratus,
> 2012 IEEE S&P Journal,
> http://langsec.org/papers/postel-patch.pdf
I would encourage them to read Shannon/Weaver as well.

Joe



--------------75B201712ECE0E74F2306F82
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>FWIW:<br>
    </p>
    On 6/17/2017 7:18 AM, Petr Špaček wrote:<br>
    <blockquote type="cite"
      cite="mid:f69679ba-f69c-b063-943f-6994489c526d@nic.cz">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">What the specification leaves open, implementations should respect and
honor as allowed.
</pre>
      </blockquote>
      <pre wrap="">This is exactly the point where our opinions differ.
My point of view is that specification should clearly define extension
points and implementations should:
a) Use Postel's principle within defined 'extension' points.
b) Treat any deviation from documented protocol (including non-defined
aspects of protocol outside of extension points) as an error.</pre>
    </blockquote>
    You're asking for 10,000 page specifications and 10MB protocol
    implementations that are vulnerable to attack.<br>
    <br>
    <blockquote type="cite"
      cite="mid:f69679ba-f69c-b063-943f-6994489c526d@nic.cz">
      <pre wrap="">Nice set of reasons for being strict when receiving messages is
described in the following article:

"A Patch for Postel's Robustness Principle",
Len Sassaman, Meredith L. Patterson, Sergey Bratus,
2012 IEEE S&amp;P Journal,
<a class="moz-txt-link-freetext" href="http://langsec.org/papers/postel-patch.pdf" moz-do-not-send="true">http://langsec.org/papers/postel-patch.pdf</a></pre>
    </blockquote>
    I would encourage them to read Shannon/Weaver as well.<br>
    <br>
    Joe<br>
    <br>
    <br>
  </body>
</html>

--------------75B201712ECE0E74F2306F82--


From nobody Sun Jun 18 22:01:39 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 8F6471205F1; Sun, 18 Jun 2017 22:01:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 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, T_KAM_HTML_FONT_INVALID=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 XHTTtUlxiaYS; Sun, 18 Jun 2017 22:01:35 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B159127871; Sun, 18 Jun 2017 22:01:33 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML710-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DIT44053; Mon, 19 Jun 2017 05:01:31 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by LHREML710-CAH.china.huawei.com (10.201.108.33) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 19 Jun 2017 06:01:30 +0100
Received: from DGGEMM405-HUB.china.huawei.com (10.3.20.213) by NKGEML413-HUB.china.huawei.com (10.98.56.74) with Microsoft SMTP Server (TLS) id 14.3.235.1; Mon, 19 Jun 2017 13:01:26 +0800
Received: from DGGEMM506-MBX.china.huawei.com ([169.254.3.18]) by DGGEMM405-HUB.china.huawei.com ([10.3.20.213]) with mapi id 14.03.0301.000; Mon, 19 Jun 2017 13:01:25 +0800
From: Roni Even <roni.even@huawei.com>
To: Mike Jones <Michael.Jones@microsoft.com>, Roni Even <ron.even.tlv@gmail.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-jones-cose-rsa.all@ietf.org" <draft-jones-cose-rsa.all@ietf.org>, Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, Eric Rescorla <ekr@rtfm.com>
Subject: RE: Genart telechat review of draft-jones-cose-rsa-03
Thread-Topic: Genart telechat review of draft-jones-cose-rsa-03
Thread-Index: AQHS0rCZxlTm4kwp0UaJsSe/8SVNrqIm5glQgATmqfA=
Date: Mon, 19 Jun 2017 05:01:25 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD7D8DE3@DGGEMM506-MBX.china.huawei.com>
References: <149542590419.3467.434051460088011243@ietfa.amsl.com> <CY4PR21MB05044A22C26C81815A0B6AA4F5C10@CY4PR21MB0504.namprd21.prod.outlook.com>
In-Reply-To: <CY4PR21MB05044A22C26C81815A0B6AA4F5C10@CY4PR21MB0504.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.55]
Content-Type: multipart/alternative; boundary="_000_6E58094ECC8D8344914996DAD28F1CCD7D8DE3DGGEMM506MBXchina_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A090202.59475AAB.0087, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.18, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: f64d2297ee2bc0783decdc704aa6c19f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IoNWLIenvFBjbAno1-c4_0pnGaw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jun 2017 05:01:38 -0000

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

TWlrZSwNClRoYW5rcywgbG9vayBPSyB0byBtZSBub3cNClJvbmkNCg0KRnJvbTogR2VuLWFydCBb
bWFpbHRvOmdlbi1hcnQtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIE1pa2UgSm9uZXMN
ClNlbnQ6INeZ15XXnSDXlSAxNiDXmdeV16DXmSAyMDE3IDA1OjE2DQpUbzogUm9uaSBFdmVuOyBn
ZW4tYXJ0QGlldGYub3JnDQpDYzogZHJhZnQtam9uZXMtY29zZS1yc2EuYWxsQGlldGYub3JnOyBL
YXRobGVlbiBNb3JpYXJ0eTsgaWV0ZkBpZXRmLm9yZzsgRXJpYyBSZXNjb3JsYQ0KU3ViamVjdDog
UmU6IFtHZW4tYXJ0XSBHZW5hcnQgdGVsZWNoYXQgcmV2aWV3IG9mIGRyYWZ0LWpvbmVzLWNvc2Ut
cnNhLTAzDQoNCg0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWpvbmVzLWNvc2Ut
cnNhLTA0IGFkZHJlc3NlcyB5b3VyIHJldmlldyBjb21tZW50cywgUm9uaS4gIFRoYW5rcyBmb3Ig
dGhlIHVzZWZ1bCByZXZpZXchDQoNCg0KDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgLS0gTWlrZQ0KDQoNCg0KUC5TLiAgSSBh
bHNvIHRoYW5rZWQgeW91IGluIHRoZSBwdWJsaWNhdGlvbiBhbm5vdW5jZW1lbnQgYXQgaHR0cDov
L3NlbGYtaXNzdWVkLmluZm8vP3A9MTY5NyBhbmQgYXMgQHNlbGZpc3N1ZWQ8aHR0cHM6Ly90d2l0
dGVyLmNvbS9zZWxmaXNzdWVkPi4NCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpG
cm9tOiBSb25pIEV2ZW4gW21haWx0bzpyb24uZXZlbi50bHZAZ21haWwuY29tXQ0KU2VudDogU3Vu
ZGF5LCBNYXkgMjEsIDIwMTcgOTowNSBQTQ0KVG86IGdlbi1hcnRAaWV0Zi5vcmc8bWFpbHRvOmdl
bi1hcnRAaWV0Zi5vcmc+DQpDYzogZHJhZnQtam9uZXMtY29zZS1yc2EuYWxsQGlldGYub3JnPG1h
aWx0bzpkcmFmdC1qb25lcy1jb3NlLXJzYS5hbGxAaWV0Zi5vcmc+OyBpZXRmQGlldGYub3JnPG1h
aWx0bzppZXRmQGlldGYub3JnPg0KU3ViamVjdDogR2VuYXJ0IHRlbGVjaGF0IHJldmlldyBvZiBk
cmFmdC1qb25lcy1jb3NlLXJzYS0wMw0KDQoNCg0KUmV2aWV3ZXI6IFJvbmkgRXZlbg0KDQpSZXZp
ZXcgcmVzdWx0OiBSZWFkeSB3aXRoIE5pdHMNCg0KDQoNCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1B
UlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW0g
KEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZCBieSB0
aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuIFBsZWFzZSB3YWl0IGZvciBkaXJlY3Rpb24gZnJv
bSB5b3VyIGRvY3VtZW50IHNoZXBoZXJkIG9yIEFEIGJlZm9yZSBwb3N0aW5nIGEgbmV3IHZlcnNp
b24gb2YgdGhlIGRyYWZ0Lg0KDQoNCg0KRm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBzZWUg
dGhlIEZBUSBhdA0KDQoNCg0KPGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dl
bkFydGZhcT4uDQoNCg0KDQpEb2N1bWVudDogZHJhZnQtam9uZXMtY29zZS1yc2EtPz8NCg0KUmV2
aWV3ZXI6IFJvbmkgRXZlbg0KDQpSZXZpZXcgRGF0ZTogMjAxNy0wNS0yMQ0KDQpJRVRGIExDIEVu
ZCBEYXRlOiAyMDE3LTA2LTE1DQoNCklFU0cgVGVsZWNoYXQgZGF0ZTogMjAxNy0wNi0yMg0KDQoN
Cg0KU3VtbWFyeTogVGhlIGRvY3VtZW50IGlzIHJlYWR5IGZvciBwdWJsaWNhdGlvbiBhcyBzdGFu
ZGFyZCB0cmFjayBSRkMgd2l0aCBuaXRzDQoNCg0KDQpNYWpvciBpc3N1ZXM6DQoNCg0KDQpNaW5v
ciBpc3N1ZXM6DQoNCg0KDQpOaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCg0KDQoNCjEuIFNlY3Rp
b24gMyBmaXJzdCBwYXJhZ3JhcGggImNhbiBiZSBmaW5kIiBzaG91bGQgYmUgImNhbiBiZSBmb3Vu
ZCINCg0KDQoNCjIuIElBTkEgNS4xICB0YWJsZSAxIGFuZCAyIG1pc3NpbmcgcmVjb21tZW5kZWQg
Y29sdW0NCg0KDQoNCjMuIElBTkEgNS4zIHRhYmxlIDQgdGhlIHRpdGxlIGlzIG5vdCAidmFsdWUi
IGJ1dCAibGFiZWwiDQoNCg0KDQoNCg0KDQoNCg0K

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KYTpsaW5r
LCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1
NjNDMTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3
MjsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5Nc29Q
bGFpblRleHQsIGRpdi5Nc29QbGFpblRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1z
by1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJv
dHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LCJzYW5zLXNlcmlmIjt9DQpwLk1zb0FjZXRhdGUsIGxpLk1zb0FjZXRhdGUsIGRpdi5Nc29BY2V0
YXRlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBU
ZXh0IENoYXIiOw0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZTo4LjBwdDsNCglmb250LWZhbWlseToiVGFob21hIiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5Q
bGFpblRleHRDaGFyDQoJe21zby1zdHlsZS1uYW1lOiJQbGFpbiBUZXh0IENoYXIiOw0KCW1zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCI7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjt9DQpzcGFuLkJhbGxvb25UZXh0Q2hhcg0KCXtt
c28tc3R5bGUtbmFtZToiQmFsbG9vbiBUZXh0IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5
OTsNCgltc28tc3R5bGUtbGluazoiQmFsbG9vbiBUZXh0IjsNCglmb250LWZhbWlseToiVGFob21h
Iiwic2Fucy1zZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjENCgl7bXNvLXN0eWxlLXR5cGU6cGVy
c29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xv
cjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5
Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBw
dCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2Lldv
cmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3Rl
IG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAy
NiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hh
cGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+
DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5n
PSJFTi1VUyIgbGluaz0iIzA1NjNDMSIgdmxpbms9IiM5NTRGNzIiPg0KPGRpdiBjbGFzcz0iV29y
ZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJjb2xvcjojMUY0
OTdEIj5NaWtlLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5UaGFua3MsIGxvb2sgT0sgdG8gbWUgbm93PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImNvbG9y
OiMxRjQ5N0QiPlJvbmk8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iY29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtw
YWRkaW5nOjBjbSAwY20gMGNtIDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwY20gMGNtIDBj
bSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBw
dDtmb250LWZhbWlseTomcXVvdDtUYWhvbWEmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90OyI+
RnJvbTo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij4gR2VuLWFydCBbbWFp
bHRvOmdlbi1hcnQtYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+TWlrZSBK
b25lczxicj4NCjxiPlNlbnQ6PC9iPiA8c3BhbiBsYW5nPSJIRSIgZGlyPSJSVEwiPteZ15XXnSZu
YnNwO9eVIDE2INeZ15XXoNeZIDIwMTcgMDU6MTY8L3NwYW4+PGJyPg0KPGI+VG86PC9iPiBSb25p
IEV2ZW47IGdlbi1hcnRAaWV0Zi5vcmc8YnI+DQo8Yj5DYzo8L2I+IGRyYWZ0LWpvbmVzLWNvc2Ut
cnNhLmFsbEBpZXRmLm9yZzsgS2F0aGxlZW4gTW9yaWFydHk7IGlldGZAaWV0Zi5vcmc7IEVyaWMg
UmVzY29ybGE8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtHZW4tYXJ0XSBHZW5hcnQgdGVsZWNo
YXQgcmV2aWV3IG9mIGRyYWZ0LWpvbmVzLWNvc2UtcnNhLTAzPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRm
Lm9yZy9odG1sL2RyYWZ0LWpvbmVzLWNvc2UtcnNhLTA0Ij5odHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtam9uZXMtY29zZS1yc2EtMDQ8L2E+IGFkZHJlc3NlcyB5b3VyIHJldmlldyBj
b21tZW50cywgUm9uaS4mbmJzcDsgVGhhbmtzIGZvciB0aGUgdXNlZnVsIHJldmlldyE8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7IC0tIE1pa2U8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+UC5TLiZuYnNwOyBJIGFs
c28gdGhhbmtlZCB5b3UgaW4gdGhlIHB1YmxpY2F0aW9uIGFubm91bmNlbWVudCBhdA0KPGEgaHJl
Zj0iaHR0cDovL3NlbGYtaXNzdWVkLmluZm8vP3A9MTY5NyI+aHR0cDovL3NlbGYtaXNzdWVkLmlu
Zm8vP3A9MTY5NzwvYT4gYW5kIGFzDQo8YSBocmVmPSJodHRwczovL3R3aXR0ZXIuY29tL3NlbGZp
c3N1ZWQiPkBzZWxmaXNzdWVkPC9hPi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+LS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+DQpGcm9tOiBSb25pIEV2ZW4gWzxhIGhyZWY9Im1h
aWx0bzpyb24uZXZlbi50bHZAZ21haWwuY29tIj5tYWlsdG86cm9uLmV2ZW4udGx2QGdtYWlsLmNv
bTwvYT5dDQo8YnI+DQpTZW50OiBTdW5kYXksIE1heSAyMSwgMjAxNyA5OjA1IFBNPGJyPg0KVG86
IDxhIGhyZWY9Im1haWx0bzpnZW4tYXJ0QGlldGYub3JnIj5nZW4tYXJ0QGlldGYub3JnPC9hPjxi
cj4NCkNjOiA8YSBocmVmPSJtYWlsdG86ZHJhZnQtam9uZXMtY29zZS1yc2EuYWxsQGlldGYub3Jn
Ij5kcmFmdC1qb25lcy1jb3NlLXJzYS5hbGxAaWV0Zi5vcmc8L2E+Ow0KPGEgaHJlZj0ibWFpbHRv
OmlldGZAaWV0Zi5vcmciPmlldGZAaWV0Zi5vcmc8L2E+PGJyPg0KU3ViamVjdDogR2VuYXJ0IHRl
bGVjaGF0IHJldmlldyBvZiBkcmFmdC1qb25lcy1jb3NlLXJzYS0wMzxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij5SZXZpZXdlcjogUm9uaSBFdmVuPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij5SZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIE5pdHM8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBm
b3IgdGhpcyBkcmFmdC4gVGhlIEdlbmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2
aWV3cyBhbGwgSUVURiBkb2N1bWVudHMgYmVpbmcgcHJvY2Vzc2VkIGJ5IHRoZSBJRVNHIGZvciB0
aGUgSUVURiBDaGFpci4gUGxlYXNlIHdhaXQgZm9yIGRpcmVjdGlvbiBmcm9tIHlvdXIgZG9jdW1l
bnQgc2hlcGhlcmQgb3IgQUQgYmVmb3JlIHBvc3RpbmcNCiBhIG5ldyB2ZXJzaW9uIG9mIHRoZSBk
cmFmdC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Rm9yIG1vcmUgaW5mb3JtYXRpb24s
IHBsZWFzZSBzZWUgdGhlIEZBUSBhdDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbHQ7
PGEgaHJlZj0iaHR0cHM6Ly90cmFjLmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxIj48
c3BhbiBzdHlsZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRpb246bm9uZSI+aHR0cHM6
Ly90cmFjLmlldGYub3JnL3RyYWMvZ2VuL3dpa2kvR2VuQXJ0ZmFxPC9zcGFuPjwvYT4mZ3Q7Ljxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5Eb2N1bWVudDogZHJhZnQtam9uZXMtY29zZS1y
c2EtPz88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlJldmlld2VyOiBS
b25pIEV2ZW48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlJldmlldyBE
YXRlOiAyMDE3LTA1LTIxPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5J
RVRGIExDIEVuZCBEYXRlOiAyMDE3LTA2LTE1PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij5JRVNHIFRlbGVjaGF0IGRhdGU6IDIwMTctMDYtMjI8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+U3VtbWFyeTogVGhlIGRvY3VtZW50IGlzIHJlYWR5IGZvciBwdWJsaWNh
dGlvbiBhcyBzdGFuZGFyZCB0cmFjayBSRkMgd2l0aCBuaXRzPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPk1ham9yIGlzc3Vlczo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+TWlu
b3IgaXNzdWVzOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5OaXRzL2VkaXRvcmlhbCBj
b21tZW50czogPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjEuIFNlY3Rpb24gMyBmaXJz
dCBwYXJhZ3JhcGggJnF1b3Q7Y2FuIGJlIGZpbmQmcXVvdDsgc2hvdWxkIGJlICZxdW90O2NhbiBi
ZSBmb3VuZCZxdW90OzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4yLiBJQU5BIDUuMSZu
YnNwOyB0YWJsZSAxIGFuZCAyIG1pc3NpbmcgcmVjb21tZW5kZWQgY29sdW08bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+My4gSUFOQSA1LjMgdGFibGUgNCB0aGUgdGl0bGUgaXMgbm90ICZx
dW90O3ZhbHVlJnF1b3Q7IGJ1dCAmcXVvdDtsYWJlbCZxdW90OzxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_6E58094ECC8D8344914996DAD28F1CCD7D8DE3DGGEMM506MBXchina_--


From nobody Mon Jun 19 02:32:53 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 433F112943A; Mon, 19 Jun 2017 02:32:38 -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-dcbench-methodology.all@ietf.org, ietf@ietf.org, bmwg@ietf.org, dromasca@gmail.com
Subject: Genart telechat review of draft-ietf-bmwg-dcbench-methodology-12
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149786475813.10715.10157714153398648057@ietfa.amsl.com>
Date: Mon, 19 Jun 2017 02:32:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0rxRLILbBaAdo_fuotSlMo4MtsA>
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, 19 Jun 2017 09:32:38 -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-bmwg-dcbench-methodology-??
Reviewer: Dan Romascanu
Review Date: 2017-06-19
IETF LC End Date: 2017-06-13
IESG Telechat date: 2017-06-22

Summary:

This Informational I-D describes test and evaluation methodology and
measurement techniques for physical network equipment in the data center. It's
an useful and clearly written document and it is ready for publication. A few
minor issues and nits that were brought up in my LC review were addressed by
the authors - thanks!

Major issues:

Minor issues:

Nits/editorial comments:



From nobody Mon Jun 19 04:15:56 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 0D6CF129BE8 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 04:15:55 -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 obMyhPRvrOZv for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 04:15:52 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id D5ACC129BEE for <ietf@ietf.org>; Mon, 19 Jun 2017 04:14:58 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 196752D0A5; Mon, 19 Jun 2017 14:14:57 +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 7ht7Dwp3kVoN; Mon, 19 Jun 2017 14:14:56 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTP id 76CAB2D06B; Mon, 19 Jun 2017 14:14:56 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: 5G and Internet Technology
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_97C243F6-C41A-4151-8317-2DC3AF6416B9"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <4CDA6D0D-AAF0-4E12-8C56-4387A739BDF5@ietf.org>
Date: Mon, 19 Jun 2017 14:14:54 +0300
Message-Id: <47913646-ECF6-4DBB-841C-A67905BD6458@piuha.net>
References: <4CDA6D0D-AAF0-4E12-8C56-4387A739BDF5@ietf.org>
To: IETF Discussion <ietf@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/XEdnmvAR7KIe31FjYD3Swg_bH7s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jun 2017 11:15:55 -0000

--Apple-Mail=_97C243F6-C41A-4151-8317-2DC3AF6416B9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

Hi,

Alissa had earlier written about her visit to 3GPP, and about
working together on the topic of 5G in
https://www.ietf.org/blog/2017/06/working-together-with-3gpp-on-5g/

We also discussed this topic at the last month=92s IAB retreat. Jeff and =
I
wrote a blog post looking at the various aspects of where Internet and
5G technology interact. For instance, is there work that we should
be doing at the IETF that relates to 5G? What concrete network
changes does 5G imply?

Here=92s the article:

    https://www.ietf.org/blog/2017/06/5g-and-internet-technology/

Comments appreciated!

Jari


--Apple-Mail=_97C243F6-C41A-4151-8317-2DC3AF6416B9
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

iQIcBAEBCgAGBQJZR7IvAAoJEM80gCTQU46qEa0QAMV/A2T6LjY37Q+SHLcGv+0Z
d3/6V2rIH2rGusQtsftxPEXNC3kpQmrVfyAX6Ip96D152kMQ1Bku/7k4VzElRqjn
I4lTq9SgyWtC74C29YAJ/ya5/GtyHqGVCSKrUXjVMqnU8KbM8baO5RZFqnMYJp6b
kPygwp5DH90G8swzv09exr2D9hCDqvGF8P6UnP7beYlwSEjnlfs1bX6FUf9ZiKGM
Q3qpih6thB75GglzjSBi9WJEutpZgZggA/7jYRORc6GF4WQjRgTu/P656euHl1GO
9zrH+q0I5peWFh02i7m8j0pKgdISqLLGXMbPg4C1n6EY8Lnj1EhDvszc4FEd/oXP
n4KfDAW06saMVu3IjlXk0/P32NwVV68gJg9oHZP6NtxxyywnP5u8QssCLNEKwvE6
OF4c6JfXwobiBEr3I8zc2ojP4bijBi6UtbatRson4aryr2ENjHHGHIB7hiaqt7VH
jJ6NdxwV9Uzqjb8gX2DEZhfSpEazhubYQasrJc2BsGKfw3UgV3tK+okO9+J+NkFC
VcBeEhB0Jh8TrTJsQjfXQnP6Kgsz1vO4pgrFGDgrz8YwqazSN9l3+uw9NMXdmGmS
7CPtJJTWVRF9IG0MDj6yXoSbygLZfT045Am3kjJS54m7Gacoc39UeqQvVRKrOaCC
N04yI2pKWChL2cD0fGPx
=ndbX
-----END PGP SIGNATURE-----

--Apple-Mail=_97C243F6-C41A-4151-8317-2DC3AF6416B9--


From nobody Mon Jun 19 04:25:38 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 28DD9129B44 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 04:25:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.12
X-Spam-Level: 
X-Spam-Status: No, score=-1.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 pAs9TZI5EIxL for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 04:25:34 -0700 (PDT)
Received: from newdragon.webhostserver.biz (newdragon.webhostserver.biz [69.25.136.252]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90C8D129B1E for <ietf@ietf.org>; Mon, 19 Jun 2017 04:25:34 -0700 (PDT)
Received: from [::1] (port=38346) by newdragon.webhostserver.biz with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.86_1) (envelope-from <lberger@labn.net>) id 1dMuoH-0006Vg-Et; Mon, 19 Jun 2017 15:25:33 +0400
Subject: Re: 5G and Internet Technology
To: Jari Arkko <jari.arkko@piuha.net>, IETF Discussion <ietf@ietf.org>
References: <4CDA6D0D-AAF0-4E12-8C56-4387A739BDF5@ietf.org> <47913646-ECF6-4DBB-841C-A67905BD6458@piuha.net>
From: Lou Berger <lberger@labn.net>
Message-ID: <36977047-d8b8-5885-98e1-ce53f1ba2b86@labn.net>
Date: Mon, 19 Jun 2017 07:25:31 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <47913646-ECF6-4DBB-841C-A67905BD6458@piuha.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - newdragon.webhostserver.biz
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - labn.net
X-Get-Message-Sender-Via: newdragon.webhostserver.biz: authenticated_id: lberger@blabn.com
X-Authenticated-Sender: newdragon.webhostserver.biz: lberger@blabn.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5dJ4VHuqaI35UgszgHeUqNBDT3Q>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jun 2017 11:25:36 -0000

Hi Jari/Jeff,

    Thank you for the article, an interesting topic, certainly! 

In the DetNet WG, we've started considering the new resource
requirements of 5G networks and how these requirements could be
addressed within the constrained environments of an operator.  For those
who may be interested, take a look at [1].  We of course welcome
additional / new contributions to the WG!

Lou

DetNet WG co-chair

[1] https://tools.ietf.org/html/draft-ietf-detnet-use-cases-12#section-6.1

On 6/19/2017 7:14 AM, Jari Arkko wrote:
> Hi,
>
> Alissa had earlier written about her visit to 3GPP, and about
> working together on the topic of 5G in
> https://www.ietf.org/blog/2017/06/working-together-with-3gpp-on-5g/
>
> We also discussed this topic at the last month’s IAB retreat. Jeff and I
> wrote a blog post looking at the various aspects of where Internet and
> 5G technology interact. For instance, is there work that we should
> be doing at the IETF that relates to 5G? What concrete network
> changes does 5G imply?
>
> Here’s the article:
>
>     https://www.ietf.org/blog/2017/06/5g-and-internet-technology/
>
> Comments appreciated!
>
> Jari
>


From nobody Mon Jun 19 04:32:43 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 EBC0C12E050 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 04:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham 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 4Jbnc866qAKn for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 04:32:37 -0700 (PDT)
Received: from mail-yb0-x231.google.com (mail-yb0-x231.google.com [IPv6:2607:f8b0:4002: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 7023512E052 for <ietf@ietf.org>; Mon, 19 Jun 2017 04:32:21 -0700 (PDT)
Received: by mail-yb0-x231.google.com with SMTP id t7so26947860yba.3 for <ietf@ietf.org>; Mon, 19 Jun 2017 04:32:21 -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=9/nTYcrFe+z/0pDDYkWd3DQwO7BWd7xQkyFzgSBx6Ok=; b=i1sbCTpGASeNlgh8RYLup5jNwrWfqm+WNDxHMI3TmuS8OL4GTqu23SMcBGD7cO6ae6 RAXVWzu3xiX+P8IHZ160S4G8oJ7wjZz+Mru/rvLzFM/IXj5BLKyzYSUjq/7zhmcdR3Gq puY9hO+phSgjsgZMWHEUEUtMe+jw0nyhP+frl7k10KPCVNz8EehwO0mNjKSemqYtOp0M g9EcdEndvq44p1s5MERuX20ERa+wJ4ARhLF3tH/HEeh9Rab4XhxYlMxxqwlzrgS4ha11 ftTW6jZO5Ng52SxL38SSJG4+W2SXbIgyGemtUUKRaBGHnYoH3j3sy1HbzFJ6QPz+4IET KxvQ==
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=9/nTYcrFe+z/0pDDYkWd3DQwO7BWd7xQkyFzgSBx6Ok=; b=NzMQWHOKwi2e8nJ40Y5CaZUSIHrARd3OaWbR0xN3Wur6PikvQ9hUNj0fE/3BzgBkZ4 PTxdObKRMF2xmLGFjvvy5dSGaXxjfFekNhvYC0+RAW1EE8MnZkWeacCBldMukgRixQHU wH14yufq9e2KiQtSlGpm8nFvkgrcaZbOIRG/zpCF9C+twXCAJEDVJk+6E1nZaKJiGd69 w7k0bu+1kwrH1ifUZ1JOaoATJD7+OfSMTAnww/xFAGp6ggizfrwKBpp94m0pxkXRfIbk Hb0wdZewGXUvy/KlH7izYK/7gqaRq6qrct0wam/1sd7qstDXENG0lKiSgrF09Q+n6ZuY y6mg==
X-Gm-Message-State: AKS2vOxpGBd1EFBUC6413UWBSq2yhXdB+qK1DzqPpfpXtH+J49SR3ASk +khG7lW3X5bpW+oUYl039SMKhq4C+AkOueQ=
X-Received: by 10.37.52.214 with SMTP id b205mr15047981yba.89.1497871940671; Mon, 19 Jun 2017 04:32:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.215.144 with HTTP; Mon, 19 Jun 2017 04:31:40 -0700 (PDT)
In-Reply-To: <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 19 Jun 2017 04:31:40 -0700
Message-ID: <CABcZeBMC3Ya41Wa=DY7PyJBSHFaZcdyZrrBwfN+gJsOnd8L67g@mail.gmail.com>
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: Paul Wouters <paul@nohats.ca>
Cc: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>,  IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a1147c87cf172a305524e7ca6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oLoT15uc2yA9RI_81QsU_dNxaA0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jun 2017 11:32:41 -0000

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

On Sat, Jun 17, 2017 at 7:26 AM, Paul Wouters <paul@nohats.ca> wrote:

> On Jun 17, 2017, at 10:18, Petr =C5=A0pa=C4=8Dek <petr.spacek@nic.cz> wro=
te:
> >
> >
> > This is exactly the point where our opinions differ.
> > My point of view is that specification should clearly define extension
> > points and implementations should:
> > a) Use Postel's principle within defined 'extension' points.
> > b) Treat any deviation from documented protocol (including non-defined
> > aspects of protocol outside of extension points) as an error.
>
> So abort all your HTML pages from loading?
>
> b) is an error that should be handled in a Postel way and the RFC should
> be updated to address the issue. Then maybe years down the line you can b=
e
> more strict on the failure.
>
> Also the consequences of being strict can be worse. Should a TLS
> connection fail if the nonce size for the integrity algorithm is too weak=
?


Not to get too into the weeds, but this isn't a coherent question: In TLS
1.1 and TLS 1.2 [0]
the size of the nonce is associated with the cipher suite and it's encoded
onto the wire
without framing. If the sender uses the wrong nonce size, you just get
integrity failures.

To take an example that's more realistic: yes, browsers do indeed decide
that certain
algorithms (e.g., RC4 or DHE below a certain keylength) are insecure and
refuse to
connect.

-Ekr


[0] TLS 1.3 uses implicit nonces.

--001a1147c87cf172a305524e7ca6
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 Sat, Jun 17, 2017 at 7:26 AM, Paul Wouters <span dir=3D"ltr">&lt;<a =
href=3D"mailto:paul@nohats.ca" target=3D"_blank">paul@nohats.ca</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"><span class=3D"">On Jun 17, 20=
17, at 10:18, Petr =C5=A0pa=C4=8Dek &lt;<a href=3D"mailto:petr.spacek@nic.c=
z">petr.spacek@nic.cz</a>&gt; wrote:<br>
&gt;<br>
&gt;<br>
&gt; This is exactly the point where our opinions differ.<br>
&gt; My point of view is that specification should clearly define extension=
<br>
&gt; points and implementations should:<br>
&gt; a) Use Postel&#39;s principle within defined &#39;extension&#39; point=
s.<br>
&gt; b) Treat any deviation from documented protocol (including non-defined=
<br>
&gt; aspects of protocol outside of extension points) as an error.<br>
<br>
</span>So abort all your HTML pages from loading?<br>
<br>
b) is an error that should be handled in a Postel way and the RFC should<br=
>
be updated to address the issue. Then maybe years down the line you can be =
more strict on the failure.<br>
<br>
Also the consequences of being strict can be worse. Should a TLS connection=
 fail if the nonce size for the integrity algorithm is too weak? </blockquo=
te><div><br></div><div>Not to get too into the weeds, but this isn&#39;t a =
coherent question: In TLS 1.1 and TLS 1.2 [0]</div><div>the size of the non=
ce is associated with the cipher suite and it&#39;s encoded onto the wire</=
div><div>without framing. If the sender uses the wrong nonce size, you just=
 get integrity failures.</div><div><br></div><div>To take an example that&#=
39;s more realistic: yes, browsers do indeed decide that certain</div><div>=
algorithms (e.g., RC4 or DHE below a certain keylength) are insecure and re=
fuse to</div><div>connect.</div><div><br></div><div>-Ekr</div><div><br></di=
v><div><br></div><div>[0] TLS 1.3 uses implicit nonces.</div><div>=C2=A0</d=
iv></div></div></div>

--001a1147c87cf172a305524e7ca6--


From nobody Mon Jun 19 06:12:51 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 C5AD212F3D6 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 06:12:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 5uqFidniY-8v for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 06:12:40 -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 BB177126CB6 for <ietf@ietf.org>; Mon, 19 Jun 2017 06:12:40 -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 v5JDBmF6004234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 19 Jun 2017 06:11:58 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz>
From: Joe Touch <touch@isi.edu>
Message-ID: <8fb6bbab-42e5-1a11-ee62-03665a1d3c0e@isi.edu>
Date: Mon, 19 Jun 2017 06:11:47 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <f69679ba-f69c-b063-943f-6994489c526d@nic.cz>
Content-Type: multipart/alternative; boundary="------------0E269659DCD1541C9B1D7A9A"
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/hgKYdV3HEzRPbHl0G5rhNvwu4EI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jun 2017 13:12:44 -0000

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



On 6/17/2017 7:18 AM, Petr Špaček wrote:
> b) Treat any deviation from documented protocol (including non-defined
> aspects of protocol outside of extension points) as an error.
This, IMO, is where we differ.

Postel's Principle is more an application of Hanlon's Razor:
*Never attribute to malice that which is adequately explained by stupidity.
*http://quoteinvestigator.com/2016/12/30/not-malice/
(replace "stupidity" with "ignorance" or "accident" and the relationship
is more clear).

IMO, the Postel Principle advises two things:
    - don't over react to ignorance/accident
    - don't do things that make others question your motives

These principles apply both to protocol specification and
implementation. It's excessive to explicitly outlaw something that might
be useful and could occur benignly, UNLESS it creates a dangerous or
specifically incorrect result.

Joe


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

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 6/17/2017 7:18 AM, Petr Špaček
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:f69679ba-f69c-b063-943f-6994489c526d@nic.cz">
      <pre wrap="">b) Treat any deviation from documented protocol (including non-defined
aspects of protocol outside of extension points) as an error.</pre>
    </blockquote>
    This, IMO, is where we differ.<br>
    <br>
    Postel's Principle is more an application of Hanlon's Razor:<br>
    <strong>Never attribute to malice that which is adequately explained
      by stupidity. <br>
    </strong><a class="moz-txt-link-freetext" href="http://quoteinvestigator.com/2016/12/30/not-malice/">http://quoteinvestigator.com/2016/12/30/not-malice/</a><br>
    (replace "stupidity" with "ignorance" or "accident" and the
    relationship is more clear).<br>
    <br>
    IMO, the Postel Principle advises two things:<br>
        - don't over react to ignorance/accident<br>
        - don't do things that make others question your motives<br>
    <br>
    These principles apply both to protocol specification and
    implementation. It's excessive to explicitly outlaw something that
    might be useful and could occur benignly, UNLESS it creates a
    dangerous or specifically incorrect result. <br>
    <br>
    Joe<br>
    <br>
  </body>
</html>

--------------0E269659DCD1541C9B1D7A9A--


From nobody Mon Jun 19 08:01:32 2017
Return-Path: <paul@nohats.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 7525A131516 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 08:01:30 -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, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jtR4BgmegCkM for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 08:01:29 -0700 (PDT)
Received: from mx.nohats.ca (mx.nohats.ca [193.110.157.68]) (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 96E5013151E for <ietf@ietf.org>; Mon, 19 Jun 2017 08:01:19 -0700 (PDT)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3wrvLk2hXxz366; Mon, 19 Jun 2017 17:01:18 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1497884478; bh=6jdsUt4Yh9PHcr986V//rWnxw/KL75cPwzD01YdUb5I=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=Qwi+DmM8i20DWJ1l/rFYXUQ8+qxeDWSeX2Q29/bywRo5SJLOHQeqxCkDP6kZkoHxp 9tk8CtB4V2y4tZ7Ogl6H6Ea7ErhukevgxqAk7aWDXqdbSRcdsdDulA4q6VD2xK6lJv EDXlEwP1d/1sZqiUPa6V1HPCm9ajGoCL/IchdP34=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id izJtonyqeKWn; Mon, 19 Jun 2017 17:01:17 +0200 (CEST)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Mon, 19 Jun 2017 17:01:17 +0200 (CEST)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 2B685353479; Mon, 19 Jun 2017 11:01:16 -0400 (EDT)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca 2B685353479
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 222DA4212528; Mon, 19 Jun 2017 11:01:16 -0400 (EDT)
Date: Mon, 19 Jun 2017 11:01:15 -0400 (EDT)
From: Paul Wouters <paul@nohats.ca>
To: Eric Rescorla <ekr@rtfm.com>
cc: IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
In-Reply-To: <CABcZeBMC3Ya41Wa=DY7PyJBSHFaZcdyZrrBwfN+gJsOnd8L67g@mail.gmail.com>
Message-ID: <alpine.LRH.2.21.1706191059010.6340@bofh.nohats.ca>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca> <CABcZeBMC3Ya41Wa=DY7PyJBSHFaZcdyZrrBwfN+gJsOnd8L67g@mail.gmail.com>
User-Agent: Alpine 2.21 (LRH 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/ofYtmpU9xtQv7ZnmqpZL75ynCT8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jun 2017 15:01:30 -0000

On Mon, 19 Jun 2017, Eric Rescorla wrote:

>       Also the consequences of being strict can be worse. Should a TLS connection fail if the nonce size for the
>       integrity algorithm is too weak?
> 
> Not to get too into the weeds, but this isn't a coherent question: In TLS 1.1 and TLS 1.2 [0]
> the size of the nonce is associated with the cipher suite and it's encoded onto the wire
> without framing. If the sender uses the wrong nonce size, you just get integrity failures.

Ok you caught me on a last minute IKE -> TLS word-smithing change :)

We did run into this in our IKE implementation when going through FIPS
validation. And it seemed no one care that our values were too small
to do SHA2_512.

Paul


From nobody Mon Jun 19 09:06: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 4D5A2131553 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 09:06:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=ham 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 1cGTjcdXReR7 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 09:06:32 -0700 (PDT)
Received: from mail-yb0-x22f.google.com (mail-yb0-x22f.google.com [IPv6:2607:f8b0:4002:c09::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 995E912945C for <ietf@ietf.org>; Mon, 19 Jun 2017 09:06:23 -0700 (PDT)
Received: by mail-yb0-x22f.google.com with SMTP id f192so29429636yba.2 for <ietf@ietf.org>; Mon, 19 Jun 2017 09:06:23 -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=d+DTHIwjiDa5k2LXDKSE0E1JGaii5L8WPRgKn3nMVZ8=; b=t5uiDrvwENjBnD9Q4/xNFtiFKLSEV20VoI7Z9pXLQT7Ph3S8hQeW4SEdewAISzT6k3 +E1RLSdrpiR0sSYo8cDUOLPpRSnjPsnSixhr22rMGK6CsWYcRoxYaRWw6HvM66kECFI1 fNRVmMV/Vgmr/0X1KZS44sxOiz7GzHPFE0KJCGlA/Op1indjGcvP5hBlQeR28M/Q0ZG3 bGO8pG9Z5Igy2DD13oa+ahjBVHxuJCrqNUT7NzAYim3ymBtw3honZYvvUqGSOBwQ/obp +G7QfBKK+jIan3OZKNXdlvn2uIKkRGP9VWnI7nhpTtZrLbP6WJTz7kaAIyDV2tK+sLiW ca/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=d+DTHIwjiDa5k2LXDKSE0E1JGaii5L8WPRgKn3nMVZ8=; b=fvimkMTVKsqVtfHKbtoy9S7RbNtpMD9siI4f0fkmnjylv9mEUtJgMr2A6ccWh4c/8h 8o3K4Mwiwk9ZZ1WqKk9+AZtU17P0qeg9nqOg67pWFxIgVNYwxm1evhlCRCpzMRDoISCO LdcbfiyjnwauS9wTs2WkTHYqJmJ0n5uCg/Cvn/MBgmjc7vK66u783LHuIjCb+Sx7/Ybm AUQjwKhqGcUdTwhVFnxJmBsoaL1n0UgoHuIZykiTTa37AfYJLJdGOnYS30XjYVDXtpGc wEIyctRyTGNThLZIs/B8ZCbE/iG0plmSjpznjbEYICj9DUMFY9bBbm2bzpYJ17W3p5vV ke5g==
X-Gm-Message-State: AKS2vOy7d43f5s2rYmntzbdPpG4YbFA3+JxuKctIkkv9wMd/MeegU4KT 1FN5VGcuRp7GufzOym6J4chiXdETcnRz
X-Received: by 10.37.68.87 with SMTP id r84mr19859047yba.229.1497888382322; Mon, 19 Jun 2017 09:06:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.13.215.144 with HTTP; Mon, 19 Jun 2017 09:05:41 -0700 (PDT)
In-Reply-To: <alpine.LRH.2.21.1706191059010.6340@bofh.nohats.ca>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca> <CABcZeBMC3Ya41Wa=DY7PyJBSHFaZcdyZrrBwfN+gJsOnd8L67g@mail.gmail.com> <alpine.LRH.2.21.1706191059010.6340@bofh.nohats.ca>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 19 Jun 2017 09:05:41 -0700
Message-ID: <CABcZeBOdP5LEdhB+N+EiotD=oQUhf_t09pLxo0xnqTThFZMZOA@mail.gmail.com>
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: Paul Wouters <paul@nohats.ca>
Cc: IETF discussion list <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113f5f3ef12ace05525250fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pZ_D39J_7qB2yFd8QwgjoVdOnd8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jun 2017 16:06:34 -0000

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

On Mon, Jun 19, 2017 at 8:01 AM, Paul Wouters <paul@nohats.ca> wrote:

> On Mon, 19 Jun 2017, Eric Rescorla wrote:
>
>       Also the consequences of being strict can be worse. Should a TLS
>> connection fail if the nonce size for the
>>       integrity algorithm is too weak?
>>
>> Not to get too into the weeds, but this isn't a coherent question: In TLS
>> 1.1 and TLS 1.2 [0]
>> the size of the nonce is associated with the cipher suite and it's
>> encoded onto the wire
>> without framing. If the sender uses the wrong nonce size, you just get
>> integrity failures.
>>
>
> Ok you caught me on a last minute IKE -> TLS word-smithing change :)
>
> We did run into this in our IKE implementation when going through FIPS
> validation. And it seemed no one care that our values were too small
> to do SHA2_512.


Maybe we should take this offline, but I'm not really seeing a connection
between
the size of the hash function you are using as the basis for your MAC and
the
size of the nonces.

-Ekr


>
> Paul
>

--001a113f5f3ef12ace05525250fc
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 Mon, Jun 19, 2017 at 8:01 AM, Paul Wouters <span dir=3D"ltr">&lt;<a =
href=3D"mailto:paul@nohats.ca" target=3D"_blank">paul@nohats.ca</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"><span class=3D"">On Mon, 19 Ju=
n 2017, Eric Rescorla wrote:<br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
=C2=A0 =C2=A0 =C2=A0 Also the consequences of being strict can be worse. Sh=
ould a TLS connection fail if the nonce size for the<br>
=C2=A0 =C2=A0 =C2=A0 integrity algorithm is too weak?<br>
<br>
Not to get too into the weeds, but this isn&#39;t a coherent question: In T=
LS 1.1 and TLS 1.2 [0]<br>
the size of the nonce is associated with the cipher suite and it&#39;s enco=
ded onto the wire<br>
without framing. If the sender uses the wrong nonce size, you just get inte=
grity failures.<br>
</blockquote>
<br></span>
Ok you caught me on a last minute IKE -&gt; TLS word-smithing change :)<br>
<br>
We did run into this in our IKE implementation when going through FIPS<br>
validation. And it seemed no one care that our values were too small<br>
to do SHA2_512.</blockquote><div><br></div><div>Maybe we should take this o=
ffline, but I&#39;m not really seeing a connection between</div><div>the si=
ze of the hash function you are using as the basis for your MAC and the</di=
v><div>size of the nonces.</div><div><br></div><div>-Ekr</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"><span class=3D"HOEnZb"><font color=3D"#888=
888"><br>
<br>
Paul<br>
</font></span></blockquote></div><br></div></div>

--001a113f5f3ef12ace05525250fc--


From nobody Mon Jun 19 11:26:59 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 114211317E7 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 11:26:57 -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 uICJNBwJkuGN for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 11:26:55 -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 B009E1317E8 for <ietf@ietf.org>; Mon, 19 Jun 2017 11:26:53 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id x70so1084525wme.0 for <ietf@ietf.org>; Mon, 19 Jun 2017 11:26:53 -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=wwOPLQCeEvleOWpoOPs3kcN+YbaP+MAu+SkQUqq81Dk=; b=kwtzTCUBPFuPzSYedr1h2P0p3sAv6fUz8/otLxB48kbyfMTitYQi4tiNZTyqPhPcJj qHNSjTkl4pBLGeIk/a5yXAPhzBSbCI9QjTmD+DCD1JNg8DD+h/Kb+JkrkmxqVqA461GT qBT78dcat90q+dRSLMdUwBr02ABBUfCCohOTTywPbOUgpEBjc1DWvpIQ8xV7rkE+K6zL 65qj1QX5ch9sQU3l1xnLbwZbQC3gAELJJ14j2a3GFCr7ClXOFOo8LW/BV2yHidz3nxNv OUfxkjf6oy0cNQEvZIqagsm1YX6wQwwCtUb+Q4j7i0XA1g3NB0vx1yYL+9GoCBRWrXo2 k9xw==
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=wwOPLQCeEvleOWpoOPs3kcN+YbaP+MAu+SkQUqq81Dk=; b=bnywN+VnADrV2AWwNkQsvG8u2FpVW5td7CDHCnsWEe8D0WdlSDr6UEFK0zEHDthGEB WnVn/K2HQ3iPKIyJ2DIbY8Yl4YW1PljWRpaBFgvzwaLdNlu0rrX5h5xZGtGfQFqFFTgf VTmGrlLGUKvwWOd9WYdw1whH8WNYu+RwFt8kQHfgSMFF0JLIlo2T18rRP7E1httAg7Qt 2iHOc7KEBrNcw3pNWVlgg5TcAy6frn2zc+uhipLqyzrUTgTuJZxsECv65m2JsjpXabBS Tp9hfDz71wBiBseMrwMkgogFyeIs3Bx0n2CDNQPTxE+3mzuukJWL9TFZZqmBuY+snRt2 F2pA==
X-Gm-Message-State: AKS2vOx5VMKAFcnsL/ZhiogDt8QLnsoGCljqQaHEyD44S6pb5CJfty/R W2ON3yYUyWUrZ/ge4Hw=
X-Received: by 10.80.174.232 with SMTP id f37mr18232548edd.157.1497896812275;  Mon, 19 Jun 2017 11:26:52 -0700 (PDT)
Received: from [192.168.1.18] ([46.120.57.147]) by smtp.gmail.com with ESMTPSA id f48sm5224199ede.45.2017.06.19.11.26.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Jun 2017 11:26:51 -0700 (PDT)
From: Yoav Nir <ynir.ietf@gmail.com>
Message-Id: <6C7D26A4-62BD-45F9-A3A8-CFC2CBAB1E6E@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_5EF4B247-66D4-4945-9894-7222CF3C2DB0"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Date: Mon, 19 Jun 2017 21:26:48 +0300
In-Reply-To: <CABcZeBMC3Ya41Wa=DY7PyJBSHFaZcdyZrrBwfN+gJsOnd8L67g@mail.gmail.com>
Cc: Paul Wouters <paul@nohats.ca>, IETF discussion list <ietf@ietf.org>
To: Eric Rescorla <ekr@rtfm.com>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca> <CABcZeBMC3Ya41Wa=DY7PyJBSHFaZcdyZrrBwfN+gJsOnd8L67g@mail.gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_9a_UOGd1hEmV1xAhAHgS7h0GK0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jun 2017 18:26:57 -0000

--Apple-Mail=_5EF4B247-66D4-4945-9894-7222CF3C2DB0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I think a better example is what does a TLS client (or IKE =
initiator/responder) do when it receives a certificate chain (OK, it=E2=80=
=99s a certificate pile that the receiver is supposed to sort) with 17 =
certificates?

It=E2=80=99s fair to assume that most normal chains will have a root CA, =
one or two intermediaries and an EE certificate, so a chain of three =
because the root does not need to be transmitted. Setting an application =
limit of 5 or 7 or 10 seems reasonable, because reasonable senders =
don=E2=80=99t have longer chains. AFAICT the only limit set by RFC 5246 =
is 16 MB for the entire chain, enough for thousands of certificates. =
Thousands of certificates is either a bug or a DoS attack, but a shorter =
chain, like 17 certs is not.

By the Postel principle, the receiver should accept this chain. In =
practice I might limit it to a lower number, because I assume nobody =
does that. I think it=E2=80=99s best for the specification to say that =
=E2=80=9CMUST support a chain of at least 7 and MUST NOT send a chain =
longer than 7=E2=80=9D, and of course you=E2=80=99d have to say that =
profiles may further reduce this number (for IoT).

Yoav






--Apple-Mail=_5EF4B247-66D4-4945-9894-7222CF3C2DB0
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-----

iQEcBAEBCgAGBQJZSBdpAAoJELhJCxUKWMyZBUIH/0EDxSyz6uVkHxmLyc2DfBLI
4XmAD6npysmmBO6VcLkYwNNAWdqQDIqoShywGB90ZDNONPsjVC2VWWnLTYlE4H1q
SMGrnLJWHUpG02SUzVDPVBll3e9BZ+F9xf4dk4ZDqE6y1Ocb0IZu4w1PYBe9NUws
wQjZX6rnnTEi1ZE7aCkrprbY21YKGi5gBgXLH+atAmFexuTmBCCp2b6oyaU2r9o0
AzW6tpR5W1SDvTO2KSS2zRzu6RucrCRJu5sK3d2qhCj5kbxtVYenQIwqq66xbUn7
ahz/aLDfY4+dvCRUk6wdx7oNGYLjtbJRHvWWxEOqjFBNoX5TrMtHTRUk0wylY3Q=
=gupY
-----END PGP SIGNATURE-----

--Apple-Mail=_5EF4B247-66D4-4945-9894-7222CF3C2DB0--


From nobody Mon Jun 19 13:29:45 2017
Return-Path: <allison.mankin@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 47DF2126C22; Mon, 19 Jun 2017 13:29:44 -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 UXrh6soYCJzP; Mon, 19 Jun 2017 13:29:42 -0700 (PDT)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::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 60016131740; Mon, 19 Jun 2017 13:29:42 -0700 (PDT)
Received: by mail-pf0-x235.google.com with SMTP id s66so58859426pfs.1; Mon, 19 Jun 2017 13:29:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=m79K+bUMoSLFIvOXpFCH5DxAApVD2HMQ7amn9yRWShI=; b=M36nzItKRd7/q9MuCFxL33wfob0pOFGIwJP1Qw1xeU67L9CLn6SUFYR+Eez82KbCQn B8slk2dr6ptakTWhRvZr4yJWw3vGb5dg2AjDmmNQnJrOKgjNPW4xjdy/Hk7mit1HhmRU LkjHLy5R7IlvaF9sRkIoSKNs4FJHcozfEzYZK+Z9XjcXzhhSmnGCrSBe9s5QluNrD3ka w+O7m1UtVXJEihdLf32m2LXK+gC2b9KIASg5Z2j3ToplqOT60HeigP6q+YTn9+kUv93v 0WF/JN/7UoKMOPg2Dt496oL33wGu9CK3gSxJisbCQlKqnZ+4m/PbAWbT5lGnHpO1MQpY /piQ==
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=m79K+bUMoSLFIvOXpFCH5DxAApVD2HMQ7amn9yRWShI=; b=EDAs90r4aPqT6HS8cIofksratEcPTjky5gbQHVkiyzg+3A5D5Zd7FW8aKtIPukx81t Q0RA5wiqxIbic+OTPSdog0m8rP/FDoUdclzCL43ECOp+1X+rS9vZfwlbgPUwwYX5Pv2W W/0V/0b7uJ/mn3dy/5A2sXi1g2YScbWcms9gdO5vMi1D9YHvsyvtTu64+BTuCZsORryx g+E1ka7q3yaN1buW0WtKDoPYFGx4O1M/t6hpqpwpwDql60glyBW3feHMLJt2wb3nQoMv qaeKmicRyreIJknRZ7W/bbgbiWkyRc8SZMZIm7CpgHwBaPotTdfG2l9QlkAK8zRX9fHh 3Naw==
X-Gm-Message-State: AKS2vOwulrvCUuSNqH3pGC/K63MTx5GUrboL23P/Qec1DOQ9CyvGrq2w qvBJbcHZ6RW48Dlz2R6zUR810X1J1BIX
X-Received: by 10.84.213.129 with SMTP id g1mr31721407pli.202.1497904181740; Mon, 19 Jun 2017 13:29:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.178.110 with HTTP; Mon, 19 Jun 2017 13:29:41 -0700 (PDT)
From: Allison Mankin <allison.mankin@gmail.com>
Date: Mon, 19 Jun 2017 16:29:41 -0400
Message-ID: <CAP8yD=sc4pjX_6Jx=nACO76GOadw1sPvGY4-Ai6qFmW0mEiAWA@mail.gmail.com>
Subject: IETF 99 ANRP Awardees; also, Applied Networking Research Workshop
To: IETF Discussion <ietf@ietf.org>, 99attendees@ietf.org
Content-Type: multipart/alternative; boundary="f403045d2620a90969055255feb3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/UeYmKrCEcJOkvlc4sD0EsOdl4NU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jun 2017 20:29:44 -0000

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

The IRTF is pleased to announce the 2017 ANRP awardees for IETF 99:

Stephen Checkoway, University of Illinois Chicago, US
A Systematic Analysis of the Juniper Dual EC Incident

Philipp Richter, Technische Universit=C3=A4t Berlin, DE
A Multi-perspective Analysis of Carrier-Grade NAT Deployment


Congratulations to Stephen and Philipp!  They will join us in Prague to
present their award papers in the IRTFOPEN meeting, which has been given a
time on Thursday afternoon July 20 (as always, please check the final
agenda).

The Applied Networking Research Prizes are a program of the IRTF and ISOC.
We look forward to lively conversations in Prague.

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

In addition, a reminder that the IRTF/ACM/ISOC Applied Network Research
Workshop is taking place in Prague at the IETF meeting hotel, on Saturday,
July 15.  It looks like it will be an even better event than last year, so
please register and join us:  https://irtf.org/anrw/2017/

Allison

Allison Mankin
IRTF Chair

--f403045d2620a90969055255feb3
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"><div class=3D"gmail_default" style=3D"font-family:arial=
,helvetica,sans-serif">The IRTF is pleased to announce the 2017 ANRP awarde=
es for IETF 99:<br><br></div><div class=3D"gmail_default" style=3D"font-fam=
ily:arial,helvetica,sans-serif">Stephen Checkoway, University of Illinois C=
hicago, US<br>A Systematic Analysis of the Juniper Dual EC Incident<br><br>=
</div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,san=
s-serif">Philipp Richter, Technische Universit=C3=A4t Berlin, DE<br>A Multi=
-perspective Analysis of Carrier-Grade NAT Deployment<br><br></div><div cla=
ss=3D"gmail_default" style=3D"font-family:arial,helvetica,sans-serif"><br>C=
ongratulations
 to Stephen and Philipp!=C2=A0 They will join us in Prague to present their=
=20
award papers in the IRTFOPEN meeting, which has been given a time on=20
Thursday afternoon July 20 (as always, please check the final agenda).<br><=
br>The Applied Networking Research Prizes are a program of the IRTF and ISO=
C.=C2=A0 We look forward to lively conversations in Prague.<br><br>--------=
------------<br><br></div><div class=3D"gmail_default" style=3D"font-family=
:arial,helvetica,sans-serif">In
 addition, a reminder that the IRTF/ACM/ISOC Applied Network Research=20
Workshop is taking place in Prague at the IETF meeting hotel, on=20
Saturday, July 15.=C2=A0 It looks like it will be an even better event than=
=20
last year, so please register and join us:=C2=A0 <a href=3D"https://irtf.or=
g/anrw/2017/">https://irtf.org/anrw/2017/</a><br><br></div><div class=3D"gm=
ail_default" style=3D"font-family:arial,helvetica,sans-serif">Allison<br><b=
r></div><div class=3D"gmail_default" style=3D"font-family:arial,helvetica,s=
ans-serif">Allison Mankin<br></div>IRTF Chair</div></div>

--f403045d2620a90969055255feb3--


From nobody Mon Jun 19 16:31:36 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 08E0212948A for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 16:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 mxVTAVmlH0PJ for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 16:31:33 -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 3BD9E1289B5 for <ietf@ietf.org>; Mon, 19 Jun 2017 16:31:33 -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 1dN68n-000HbT-6H; Mon, 19 Jun 2017 19:31:29 -0400
Date: Mon, 19 Jun 2017 19:31:23 -0400
From: John C Klensin <john-ietf@jck.com>
To: Yoav Nir <ynir.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>
cc: Paul Wouters <paul@nohats.ca>, IETF discussion list <ietf@ietf.org>
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Message-ID: <9F77ECD346450AED6AEB9A7B@PSB>
In-Reply-To: <6C7D26A4-62BD-45F9-A3A8-CFC2CBAB1E6E@gmail.com>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca> <CABcZeBMC3Ya41Wa=DY7PyJBSHFaZcdyZrrBwfN+gJsOnd8L67g@mail.gmail.com> <6C7D26A4-62BD-45F9-A3A8-CFC2CBAB1E6E@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/WKLFGlAwh1FJwP6ikn3kqUz4vWA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 19 Jun 2017 23:31:35 -0000

--On Monday, June 19, 2017 21:26 +0300 Yoav Nir
<ynir.ietf@gmail.com> wrote:

>...
> By the Postel principle, the receiver should accept this
> chain. In practice I might limit it to a lower number, because
> I assume nobody does that. I think it's best for the
> specification to say that "MUST support a chain of at least
> 7 and MUST NOT send a chain longer than 7", and of course
> you'd have to say that profiles may further reduce this
> number (for IoT).

It seems to me that your example, and some others, suggest that
if the principle was being stated today, it would be "be
conservative about what you send and liberal about what you
accept, but nothing justifies violations of common sense or
taking actions that would create risks".  If the latter/new part
is really needed, we may be in worse trouble than with questions
about what the principle really means or even whether Jon was
right or wrong.

    john





From nobody Mon Jun 19 18:15:02 2017
Return-Path: <lucienav@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 6419E131869 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 18:14:48 -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 u8TiLVvipY69 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 18:14:46 -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 6A29B13186A for <ietf@ietf.org>; Mon, 19 Jun 2017 18:14:44 -0700 (PDT)
Received: by mail-pg0-x231.google.com with SMTP id u62so36353576pgb.3 for <ietf@ietf.org>; Mon, 19 Jun 2017 18:14:44 -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=vfqrLEDdElap3Mz/cSKhvEDVqOpBLJ4efL0Bp7XFRjU=; b=IXmzHZlE10xNRCF4Z7eSlcI+pR8cG16Vs74aevoIPsdQfxxTxU9SiiQ+jR5A/fgneU 6t8DBNTd2QsqGHdjv2ZXsPfJC9IVL7cSmoI7VHgDubuksgtPGClqWVT3eJgOgGJOq0JE PxTWtk1G91EMRMsxkuJrBGIQ0f0pawqamrkFVNEzbxGjaXv2p5JNxAopG3+O14+WGTMh NBxNXesQ6DcK23mtKFoI+6aXlw0gvdt5imZgJ46uESzaPcBNjjsAPzGD7oiyFVsjjiCE Jh+0ygdSsiE734RIXpP3f8Tzx6dUhkca1NX3ekFih1mr2Tds7WFGK/VhtkRz1CGGW8yx Pc/w==
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=vfqrLEDdElap3Mz/cSKhvEDVqOpBLJ4efL0Bp7XFRjU=; b=b8dI5ykCnNKvzzOt8tW/6HQ2baK4FuohxfuQJzDgQ3C9+vpA4zzXCDX24DxlCZtbLC 5pZfdj3tuhTuQ8cj/a0cAe3gh3jUGaNKTbfxv0NRdm2PjubkwHLqBtgdRM9G5J3RpHAJ F94mE6FZl6w0a3qfoGpdg4RAPZ4vqYoE/ghuFD55s4j7Co/5uKNb/0cpECB0LXHOnECP /LscioXTH3+TYTl6vtSQg6XxdoI5TCWHIYWIyjONW0q5s8NC5E+2PW9sRAhszCid8ein WjFxEDstEP7+YtLR+I+qmv2Bwxrqj8aqzQTLtvyI5LV84EsTRfNRhGkjuHIVzoP7c8yk TfyQ==
X-Gm-Message-State: AKS2vOyq26Ry7R7+ne1CUH8Yu4WeKt/MExGqXDKrjN8+BGtMFKlIMkl/ a2O9Kkym4eeqAUTjGXhxPaNC7e1o3hzK
X-Received: by 10.99.106.2 with SMTP id f2mr29594120pgc.46.1497921283799; Mon, 19 Jun 2017 18:14:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.168.5 with HTTP; Mon, 19 Jun 2017 18:14:23 -0700 (PDT)
In-Reply-To: <149786475813.10715.10157714153398648057@ietfa.amsl.com>
References: <149786475813.10715.10157714153398648057@ietfa.amsl.com>
From: Lucien Avramov <lucienav@google.com>
Date: Mon, 19 Jun 2017 18:14:23 -0700
Message-ID: <CALTEt=DJJmHMnOY4puDB+Qf9q2Rm_-Pj52VS2vwJq=sLqGVoew@mail.gmail.com>
Subject: Re: Genart telechat review of draft-ietf-bmwg-dcbench-methodology-12
To: Dan Romascanu <dromasca@gmail.com>
Cc: gen-art <gen-art@ietf.org>, draft-ietf-bmwg-dcbench-methodology.all@ietf.org,  ietf <ietf@ietf.org>, bmwg@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c13f244069026055259fa2b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6pqhgHtzWucNNzueo7pfIbS1yTw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jun 2017 01:14:48 -0000

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

Thank you Dan for your review and support!

On Mon, Jun 19, 2017 at 2:32 AM, Dan Romascanu <dromasca@gmail.com> wrote:

> 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-bmwg-dcbench-methodology-??
> Reviewer: Dan Romascanu
> Review Date: 2017-06-19
> IETF LC End Date: 2017-06-13
> IESG Telechat date: 2017-06-22
>
> Summary:
>
> This Informational I-D describes test and evaluation methodology and
> measurement techniques for physical network equipment in the data center.
> It's
> an useful and clearly written document and it is ready for publication. A
> few
> minor issues and nits that were brought up in my LC review were addressed
> by
> the authors - thanks!
>
> Major issues:
>
> Minor issues:
>
> Nits/editorial comments:
>
>
>

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

<div dir=3D"ltr">Thank you Dan for your review and support!</div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jun 19, 2017 at 2:3=
2 AM, Dan Romascanu <span dir=3D"ltr">&lt;<a href=3D"mailto:dromasca@gmail.=
com" target=3D"_blank">dromasca@gmail.com</a>&gt;</span> wrote:<br><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc s=
olid;padding-left:1ex">Reviewer: Dan Romascanu<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/<wbr>gen/wiki/GenArtfaq<=
/a>&gt;.<br>
<br>
Document: draft-ietf-bmwg-dcbench-<wbr>methodology-??<br>
Reviewer: Dan Romascanu<br>
Review Date: 2017-06-19<br>
IETF LC End Date: 2017-06-13<br>
IESG Telechat date: 2017-06-22<br>
<br>
Summary:<br>
<br>
This Informational I-D describes test and evaluation methodology and<br>
measurement techniques for physical network equipment in the data center. I=
t&#39;s<br>
an useful and clearly written document and it is ready for publication. A f=
ew<br>
minor issues and nits that were brought up in my LC review were addressed b=
y<br>
the authors - thanks!<br>
<br>
Major issues:<br>
<br>
Minor issues:<br>
<br>
Nits/editorial comments:<br>
<br>
<br>
</blockquote></div><br></div>

--94eb2c13f244069026055259fa2b--


From nobody Mon Jun 19 22:48:22 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 3076D124C27 for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 22:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level: 
X-Spam-Status: No, score=-7.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_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 nPYnLCDRtXTU for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 22:48:17 -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 5B79F1242F7 for <ietf@ietf.org>; Mon, 19 Jun 2017 22:48:16 -0700 (PDT)
Received: from [IPv6:2001:1488:fffe:6:38a6:5fff:fed8:6fe5] (unknown [IPv6:2001:1488:fffe:6:38a6:5fff:fed8:6fe5]) by mail.nic.cz (Postfix) with ESMTPSA id 30FA361E3D for <ietf@ietf.org>; Tue, 20 Jun 2017 07:48:14 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nic.cz; s=default; t=1497937694; bh=2TNwQ0HZxB5pPe4sswq+Xg/0xKTDpP/KPpmdP5SqzEc=; h=To:From:Date; b=kS00Rc9NUYM8Zxj7EydtrzGH3GOjcp22zPkZ8wZn5PXFlbrVA8NVZ91YKSCSVoK+f vj3LPWJiZjdwZAQzSDjopdSzv3s6dFgQlcGHYUHBG9b36TcwB8a7JTzUxGGQEZBJYQ 7SjMwRn/xF6WTeiPAjUi/2eQRHhtRlmxTp25hjaM=
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu>
From: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>
Organization: CZ.NIC
Message-ID: <8e8d4db9-93fd-5092-68de-6d8de44151c3@nic.cz>
Date: Tue, 20 Jun 2017 07:48:13 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0
MIME-Version: 1.0
In-Reply-To: <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu>
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/ej09LMqA6rfDUjm8Nbg54m8Juhg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jun 2017 05:48:21 -0000

On 18.6.2017 20:09, Joe Touch wrote:
> FWIW:
> 
> On 6/17/2017 7:18 AM, Petr Špaček wrote:
>>> What the specification leaves open, implementations should respect and
>>> honor as allowed.
>> This is exactly the point where our opinions differ.
>> My point of view is that specification should clearly define extension
>> points and implementations should:
>> a) Use Postel's principle within defined 'extension' points.
>> b) Treat any deviation from documented protocol (including non-defined
>> aspects of protocol outside of extension points) as an error.
> You're asking for 10,000 page specifications and 10MB protocol

We do not understand each other here. Let me explain what I meant in
different terms:

For purpose of this example, please imagine that protocol description
(and sometimes also implementation) is a finite state automata.


Right now, if a edge in the automata is not defined as result of
protocol under-specification, it is up to implementation to decide what
to do, i.e. implementation has to guess sender's intent.

This "guess" part is where I see problems because various
implementations naturally differ in their "guesses" and this is causing
problems later on.


I argue that default action triggered by "imagined missing edge" in our
hypothetical protocol automata should be "report protocol specific error
to sender".

This could be done by adding ~ two paragraphs to protocol specification.
One defining how error message looks like (this is already present in
e.g. DNS spec as FORMERR) and second explaining that non-defined inputs
should be treated as errors. Implementations always has to have some
code to handle erroneous inputs (ala switch { default: } ) as well.
I cannot see the 10 MB of code here.


> implementations that are vulnerable to attack.

Could you elaborate on that? I still do not see how early error
reporting invites DoS. In fact I believe that is is improving overall
situation because smaller set of accepted inputs makes it easier to
handle corner cases and to avoid crash bugs.


>> Nice set of reasons for being strict when receiving messages is
>> described in the following article:
>>
>> "A Patch for Postel's Robustness Principle",
>> Len Sassaman, Meredith L. Patterson, Sergey Bratus,
>> 2012 IEEE S&P Journal,
>> http://langsec.org/papers/postel-patch.pdf
> I would encourage them to read Shannon/Weaver as well.

(copied from Message-ID: <3a0a263f-f3b4-1931-3c49-4fa1526658e5@isi.edu>)
> IMO, it's somewhat an extension of Shannon's recognition that
> communication is about symbol agreement, not semantics or intent.

We have tried to be liberal in DNS protocol in last 25 years. It
resulted in humongous mess which in the end forces sender to do multiple
guesses until he finds meaning of particular "symbol" for that
particular "receiver". This necessitates means for caching
"receiver-symbol meaning" which brings its own problems. I'm sure that
Mark Andrews can tell you wild stories about EDNS version negotiation.

In other words, we had 25+ years to try this liberal approach in DNS and
now it is time to learn from that experience.


Thank you for your time, I really appreciate it.
Petr Špaček  @  CZ.NIC


From nobody Mon Jun 19 22:56:21 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 82D161286CA for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 22:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id btGQo4XNPPxV for <ietf@ietfa.amsl.com>; Mon, 19 Jun 2017 22:56:17 -0700 (PDT)
Received: from mail-qk0-x22d.google.com (mail-qk0-x22d.google.com [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DB47127863 for <ietf@ietf.org>; Mon, 19 Jun 2017 22:56:17 -0700 (PDT)
Received: by mail-qk0-x22d.google.com with SMTP id d14so49762449qkb.1 for <ietf@ietf.org>; Mon, 19 Jun 2017 22:56:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=message-id:subject:from:to:cc:date:in-reply-to:references :organization:mime-version:content-transfer-encoding; bh=UWSW62SHbFmFsSKEaO2c0jgTi6M6w7mIokbZst2QDRk=; b=j9DTj5Y6aYfTsArxsT/usZ6BJNqJ3ZtlEAy8ULJWCta32YFBc6H8lnuiD9hdEYdy4q eWsF+a0j7MccDG6olnXB0euyqJkiW8wHRRJ3hihE56u0gvnUbMyGg11UVEMqqq3GxDOu v0wzJRZ1NG+b2K1E5P4GFy/0Q7GOPoWMjvbEVJwuKeNleAXwXoJ01HKuejYxNNVtKkrK X4zAA86hzgDR/DZH7Pltz9Xe/X/5+a0IMW3GTKbtwSwONjFGWVKL2kEPf7NiIpZwSpRM MBJQnWCv5x1vk/3y1pG993JlzbL2EgIMODDTQQkTRTg4K/vedalOiI+OG87H9/1YMslD fYsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:cc:date:in-reply-to :references:organization:mime-version:content-transfer-encoding; bh=UWSW62SHbFmFsSKEaO2c0jgTi6M6w7mIokbZst2QDRk=; b=owLcwqfbwATE7+62aNsYu8cnfHCYKznqOS4HubaNj4Qpi9rC8Jni2hwiMyURt66/Q2 J5uIUMq3DSDOrFpWWKOQWB00l5sYRN/QTpw11xNnCNJt6RU4HsMjbi7iJOhm2iO70Z/v wCv9IKkxbsAtuD5enyuRUz54y2T56RjTp8ojV0SJmqUlIEuKjcAUeiyonW3UssuShTtq 2U5IXOm8L/Iu2raI5IXnpyXGY+59+TQXGF67ANCIvmQwsBFtzyepvRAAHS5idVbb8vxL lcV834YCmISIB5a24UPrJMba/AtuYwPLOrJeI9NsmgZe1EwRltQtfvV2b7om7Zr1T6Sg QEPQ==
X-Gm-Message-State: AKS2vOwK8iUwz1MASOqrXeVBN//eKRK201ZJTaoEN3Pk4j0UFJX5oRiL nmgPvUXacY/SU6FR
X-Received: by 10.55.101.206 with SMTP id z197mr8339876qkb.207.1497938176481;  Mon, 19 Jun 2017 22:56:16 -0700 (PDT)
Received: from sio_centos_lt ([147.178.6.131]) by smtp.googlemail.com with ESMTPSA id n194sm7678911qke.12.2017.06.19.22.56.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Jun 2017 22:56:16 -0700 (PDT)
Message-ID: <1497938171.4279.8.camel@gmail.com>
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
From: Yoav Nir <ynir.ietf@gmail.com>
To: John C Klensin <john-ietf@jck.com>
Cc: Eric Rescorla <ekr@rtfm.com>, Paul Wouters <paul@nohats.ca>, IETF discussion list <ietf@ietf.org>
Date: Tue, 20 Jun 2017 08:56:11 +0300
In-Reply-To: <9F77ECD346450AED6AEB9A7B@PSB>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <70531498-1D98-41D8-9265-1B620A8D09F1@nohats.ca> <CABcZeBMC3Ya41Wa=DY7PyJBSHFaZcdyZrrBwfN+gJsOnd8L67g@mail.gmail.com> <6C7D26A4-62BD-45F9-A3A8-CFC2CBAB1E6E@gmail.com> <9F77ECD346450AED6AEB9A7B@PSB>
Organization: Dell-EMC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.12.11 (3.12.11-22.el7) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/NwLDs_St2EfiDdCAw23G6CCImjw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jun 2017 05:56:19 -0000

On Mon, 2017-06-19 at 19:31 -0400, John C Klensin wrote:
> 
> --On Monday, June 19, 2017 21:26 +0300 Yoav Nir
> <ynir.ietf@gmail.com> wrote:
> 
> >...
> > By the Postel principle, the receiver should accept this
> > chain. In practice I might limit it to a lower number, because
> > I assume nobody does that. I think it's best for the
> > specification to say that "MUST support a chain of at least
> > 7 and MUST NOT send a chain longer than 7", and of course
> > you'd have to say that profiles may further reduce this
> > number (for IoT).
> 
> It seems to me that your example, and some others, suggest that
> if the principle was being stated today, it would be "be
> conservative about what you send and liberal about what you
> accept, but nothing justifies violations of common sense or
> taking actions that would create risks".  If the latter/new part
> is really needed, we may be in worse trouble than with questions
> about what the principle really means or even whether Jon was
> right or wrong.
> 

Yeah, as the joke goes, common sense isn't.  Even assuming it's
prevalent, if you run a survey at the next TLS meeting what is a
reasonable limit for the length of a chain, you'd get a bunch of
different answers. Mine would be 10 because I have seen a real 7-cert
chain in production, but before that I might have said 4 or 5.

Without specifying it any sender has to be really conservative, maybe
limiting themselves to 3 in case there is some receiver out there that
is making severe assumptions. Without this being specified we end up
with receivers planning for 10 and senders limiting themselves (and
their PKI) to 3. This is not optimal.

I am not sure what the take away is. On the one hand under-specifying
creates interop failures, security issues and much complexity to address
issues and fix interop with old and new implementations. On the other
hand, the most successful protocols had a lot of wiggle room, and I
don't think this is coincidence.

Yoav




From nobody Tue Jun 20 00:55:12 2017
Return-Path: <a@ackl.io>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD683127601 for <ietf@ietfa.amsl.com>; Tue, 20 Jun 2017 00:55:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k9W4cFLpJy6V for <ietf@ietfa.amsl.com>; Tue, 20 Jun 2017 00:55:07 -0700 (PDT)
Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [217.70.183.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39D161292C5 for <ietf@ietf.org>; Tue, 20 Jun 2017 00:55:07 -0700 (PDT)
Received: from [IPv6:2001:660:7301:3728:947a:292d:4be0:cd08] (unknown [IPv6:2001:660:7301:3728:947a:292d:4be0:cd08]) (Authenticated sender: alex@ackl.io) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id 4AAAAC5A95; Tue, 20 Jun 2017 09:55:03 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: 5G and Internet Technology
From: Alexander Pelov <a@ackl.io>
In-Reply-To: <36977047-d8b8-5885-98e1-ce53f1ba2b86@labn.net>
Date: Tue, 20 Jun 2017 09:55:03 +0200
Cc: Jari Arkko <jari.arkko@piuha.net>, IETF Discussion <ietf@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <10DDB89E-A299-4D78-9832-19A77CC88C9B@ackl.io>
References: <4CDA6D0D-AAF0-4E12-8C56-4387A739BDF5@ietf.org> <47913646-ECF6-4DBB-841C-A67905BD6458@piuha.net> <36977047-d8b8-5885-98e1-ce53f1ba2b86@labn.net>
To: Lou Berger <lberger@labn.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Y4bdfG37_9g79f9KiYoGiIgI9n0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jun 2017 07:55:10 -0000

Dear Jari and Jeff,

Thank you for the article! Indeed it covers a topic that will lead a lot =
of the future developments in the networking world.

As you point out, the 5G communication platform should also accommodate =
low-power IoT devices, and with this I would add - low-power networks. =
The convergence of the high-throughput networks with high-density, =
very-low throughput ones is also a thing which I think is part of the 5G =
paradigm. There are already works in this direction at the 3GPP - =
NB-IoT, LTE-M1, LTE-M0. There are other technologies as well - which I =
believe could also be a part of the future 5G world. I think that an =
important piece of this convergence that is worth mentioning is the work =
done at the LPWAN WG.

For the moment we have not explicitly considered 5G-specific =
requirements, but I think this is something we should look at. Thanks =
again, for starting the discussion!

Best,
Alexander

LPWAN WG Co-Chair


> Le 19 juin 2017 =C3=A0 13:25, Lou Berger <lberger@labn.net> a =C3=A9crit=
 :
>=20
> Hi Jari/Jeff,
>=20
>    Thank you for the article, an interesting topic, certainly!=20
>=20
> In the DetNet WG, we've started considering the new resource
> requirements of 5G networks and how these requirements could be
> addressed within the constrained environments of an operator.  For =
those
> who may be interested, take a look at [1].  We of course welcome
> additional / new contributions to the WG!
>=20
> Lou
>=20
> DetNet WG co-chair
>=20
> [1] =
https://tools.ietf.org/html/draft-ietf-detnet-use-cases-12#section-6.1
>=20
> On 6/19/2017 7:14 AM, Jari Arkko wrote:
>> Hi,
>>=20
>> Alissa had earlier written about her visit to 3GPP, and about
>> working together on the topic of 5G in
>> https://www.ietf.org/blog/2017/06/working-together-with-3gpp-on-5g/
>>=20
>> We also discussed this topic at the last month=E2=80=99s IAB retreat. =
Jeff and I
>> wrote a blog post looking at the various aspects of where Internet =
and
>> 5G technology interact. For instance, is there work that we should
>> be doing at the IETF that relates to 5G? What concrete network
>> changes does 5G imply?
>>=20
>> Here=E2=80=99s the article:
>>=20
>>    https://www.ietf.org/blog/2017/06/5g-and-internet-technology/
>>=20
>> Comments appreciated!
>>=20
>> Jari
>>=20
>=20


From nobody Tue Jun 20 11:32:07 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 8C3951294AB for <ietf@ietfa.amsl.com>; Tue, 20 Jun 2017 11:32:05 -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, MIME_QP_LONG_LINE=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 BHybTxM9F0JG for <ietf@ietfa.amsl.com>; Tue, 20 Jun 2017 11:32:03 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::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 695E3127444 for <ietf@ietf.org>; Tue, 20 Jun 2017 11:32:03 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id s66so73112517pfs.1 for <ietf@ietf.org>; Tue, 20 Jun 2017 11:32:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version:content-transfer-encoding; bh=Oy1/di98Avmi0xCoIU+h2NVrS+dCHP/6lD/Vu4WyRis=; b=MibDGdkArNjhyr1ZzeZCd3xWTDn1+pV+tUVof2MVrivoi5+xAhxNHPLgLk64+H51ze RwN382KX2J7NeoOlkHW6HZBZpu2IkQjaxpfAVzhQI9Sn+cm2Zz9Jl53/7ryM4n0BVQOH XRT1ISC2KpPUKygRhFx05sALBJTYFhQQ38z35jDqjF49arxhcRQCeF1sKseuoRzxWOZL /ic7RSMHf64tCNDMMYd8zcMQ17TyE2wVaiQAW+QfVyefhrL7EHcdqhvxxrRzGHdHPGQh znA7hh77tt+rfTATX8PZIq/ojqyRA752FeN6CXLn2pRzmnnP65BjMezdXc/oWWb2vfWb A4dw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:references:in-reply-to:mime-version :content-transfer-encoding; bh=Oy1/di98Avmi0xCoIU+h2NVrS+dCHP/6lD/Vu4WyRis=; b=mLbxaVMP8aJ3k3HmsH5MwCeWi5LNDHvqO3hNuiF+yM5AFVNo/6vQE03sO5TWju3mQZ 4Y0ukz5YYMxXimjU4P73CAQs/m1csda58KAt95tY6k+PiK72gHCgatnDuhykdR7YlHER Hxc+IgkDNhCyubE3zy4twqQc+mGfJORBJgQRiMXiR1KRiKS4Cez46Z4s/4h7XSxn8tO5 nWv0XaYbrWppAMvY+pJTCB7UfW53e/QskuEABcZ4U7Lju0xf4qUaYWA21JQdQ8qaFiLx /8fnHPF7/bYUBvk9hpFrj8tQiktjSL8GqeI1eHbaXidk5Ty7HA7yTTaxQOKaFRnNpO9B FtkA==
X-Gm-Message-State: AKS2vOzjsCP8ldRYt0S+coP2+UBy3HmfBLzEb3S6PhYlDpvybx7hvjDk hNBTI2i5d1Xko6Gh
X-Received: by 10.99.5.82 with SMTP id 79mr30915086pgf.134.1497983523033; Tue, 20 Jun 2017 11:32:03 -0700 (PDT)
Received: from [192.168.254.157] (107-1-141-74-ip-static.hfc.comcastbusiness.net. [107.1.141.74]) by smtp.gmail.com with ESMTPSA id i14sm28494787pgn.14.2017.06.20.11.32.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 20 Jun 2017 11:32:02 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Tue, 20 Jun 2017 11:32:03 -0700
Subject: Re: 5G and Internet Technology
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Lou Berger <lberger@labn.net>, Jari Arkko <jari.arkko@piuha.net>, IETF Discussion <ietf@ietf.org>
Message-ID: <3974494E-DADC-46AD-9A0F-60937BBFAB74@gmail.com>
Thread-Topic: 5G and Internet Technology
References: <4CDA6D0D-AAF0-4E12-8C56-4387A739BDF5@ietf.org> <47913646-ECF6-4DBB-841C-A67905BD6458@piuha.net> <36977047-d8b8-5885-98e1-ce53f1ba2b86@labn.net>
In-Reply-To: <36977047-d8b8-5885-98e1-ce53f1ba2b86@labn.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/k88mZVf2moFswHNvux6MSvmyHw4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jun 2017 18:32:05 -0000

Hi Lou,

Thank you for your comments!
Detnet is one of IETF  wg=E2=80=99s closely related to 5G relevant topics, this h=
as also been emphasized in number of 5G talks Jari and myself did.
=20
Cheers,
Jeff
=20

On 6/19/17, 04:25, "ietf on behalf of Lou Berger" <ietf-bounces@ietf.org on=
 behalf of lberger@labn.net> wrote:

    Hi Jari/Jeff,
   =20
        Thank you for the article, an interesting topic, certainly!=20
   =20
    In the DetNet WG, we've started considering the new resource
    requirements of 5G networks and how these requirements could be
    addressed within the constrained environments of an operator.  For thos=
e
    who may be interested, take a look at [1].  We of course welcome
    additional / new contributions to the WG!
   =20
    Lou
   =20
    DetNet WG co-chair
   =20
    [1] https://tools.ietf.org/html/draft-ietf-detnet-use-cases-12#section-=
6.1
   =20
    On 6/19/2017 7:14 AM, Jari Arkko wrote:
    > Hi,
    >
    > Alissa had earlier written about her visit to 3GPP, and about
    > working together on the topic of 5G in
    > https://www.ietf.org/blog/2017/06/working-together-with-3gpp-on-5g/
    >
    > We also discussed this topic at the last month=E2=80=99s IAB retreat. Jeff =
and I
    > wrote a blog post looking at the various aspects of where Internet an=
d
    > 5G technology interact. For instance, is there work that we should
    > be doing at the IETF that relates to 5G? What concrete network
    > changes does 5G imply?
    >
    > Here=E2=80=99s the article:
    >
    >     https://www.ietf.org/blog/2017/06/5g-and-internet-technology/
    >
    > Comments appreciated!
    >
    > Jari
    >
   =20
   =20



From nobody Tue Jun 20 13:07:39 2017
Return-Path: <eckelcu@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 269B41274D2 for <ietf@ietfa.amsl.com>; Tue, 20 Jun 2017 13:07:38 -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 IT2bYOEW28YE for <ietf@ietfa.amsl.com>; Tue, 20 Jun 2017 13:07:36 -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 7BE07131563 for <ietf@ietf.org>; Tue, 20 Jun 2017 13:07:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1570; q=dns/txt; s=iport; t=1497989256; x=1499198856; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=Z0svkmT/MRpudbOO04j/1dinFO5IHNh8gQwdejxM9SE=; b=EC8jwMjT+mSfZLMXiWaYwTpMggbx3cu0SOW25XWphADOj5SVTP0U+y4k ULqPDpcHchQ5VT6aR+e3yjRBVGwAKa+nbu6dNORQHj2k0uSE9xdvDpeGt 9WDfX61RFpDcgnQz/Kfac+JjkuPBHSPxubmwMuP4ZQMC5rdEHK51jIdg0 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DSAAAngElZ/4MNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1higQ0Hg2WKGZF/lXiCESELhS5KAhqCTT8YAQIBAQEBAQEBax0?= =?us-ascii?q?LhRgBAQEBAwEBIRFRBAIBCBEDAQIDAggeAgICJQsVBgEBBQMCBBOKLBCrcYImi?= =?us-ascii?q?10BAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYELh2yCeYd7MIIxBZ5hAopuiHKCCIV?= =?us-ascii?q?Iij6VDAEfOIEKdBVJEgGGfHaITIENAQEB?=
X-IronPort-AV: E=Sophos;i="5.39,366,1493683200"; d="scan'208";a="438318858"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Jun 2017 20:07:35 +0000
Received: from XCH-RCD-019.cisco.com (xch-rcd-019.cisco.com [173.37.102.29]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v5KK7Zaf024030 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Tue, 20 Jun 2017 20:07:35 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-RCD-019.cisco.com (173.37.102.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 20 Jun 2017 15:07:35 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Tue, 20 Jun 2017 15:07:34 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: FW: please complete your hackathon registration now to secure your t-shirt
Thread-Topic: please complete your hackathon registration now to secure your t-shirt
Thread-Index: AQHS6fSstivD8MxLO0G0ArXazAI+DaIuoxsA
Date: Tue, 20 Jun 2017 20:07:34 +0000
Message-ID: <7157917B-D28F-4D9A-8C76-5D8493E9A924@cisco.com>
References: <B8805E83-5EF3-4DC5-BAC5-EF3C4DE18ECF@cisco.com>
In-Reply-To: <B8805E83-5EF3-4DC5-BAC5-EF3C4DE18ECF@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.22.0.170515
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.164.246]
Content-Type: text/plain; charset="utf-8"
Content-ID: <94C6C58372495946B3A15D72E52565BE@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/OYLVKU9YF3EiEPf8N62e9oeEcro>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 20 Jun 2017 20:07:38 -0000

UGFyZG9uIHRoZSBub2lzZSwgYnV0IGZvcndhcmRpbmcgdG8gdGhlIElFVEYgbGlzdCB0byBjYXRj
aCB0aG9zZSB3aG8gaGF2ZSBub3Qgc3Vic2NyaWJlZCB0byB0aGUgaGFja2F0aG9uQGlldGYub3Jn
IGxpc3QuDQoNClRvIGNvbnRpbnVlIHRvIHJlY2VpdmUgaW5mb3JtYXRpb24gYWJvdXQgdGhpcyBh
bmQgZnV0dXJlIElFVEYgaGFja2F0aG9ucywgcGxlYXNlIHN1YnNjcmliZSBoZXJlOg0KaHR0cHM6
Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9oYWNrYXRob24NCg0KQ2hlZXJzLA0KQ2hh
cmxlcw0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogQ2hhcmxlcyBFY2tlbCA8
ZWNrZWxjdUBjaXNjby5jb20+DQpEYXRlOiBUdWVzZGF5LCBKdW5lIDIwLCAyMDE3IGF0IDExOjQw
IEFNDQpUbzogImhhY2thdGhvbkBpZXRmLm9yZyIgPGhhY2thdGhvbkBpZXRmLm9yZz4NClN1Ympl
Y3Q6IHBsZWFzZSBjb21wbGV0ZSB5b3VyIGhhY2thdGhvbiByZWdpc3RyYXRpb24gbm93IHRvIHNl
Y3VyZSB5b3VyIHQtc2hpcnQNCg0KICAgIEhleSBGb2xrcywgDQogICAgDQogICAgSUVURiA5OSBp
cyBhcHByb2FjaGluZyByYXBpZGx5LiBUaGVyZSBhcmUgbWFueSBuYW1lcyBvZiBwZW9wbGUgSSBl
eHBlY3QgdG8gYXR0ZW5kIHRoYXQgYXJlIHN0aWxsIG1pc3NpbmcgZnJvbSB0aGUgbGlzdCBvZiBy
ZWdpc3RlcmVkIGF0dGVuZGVlcyBmb3IgdGhlIGhhY2thdGhvbi4gSSB3aWxsIGJlIHBsYWNpbmcg
dGhlIHQtc2hpcnQgb3JkZXIgdGhpcyB3ZWVrLCBhbmQgZm9vZCBhbmQgYmV2ZXJhZ2Ugb3JkZXJz
IHdpbGwgYmUgcGxhY2VkIHNvb24gYXMgd2VsbC4gUGxlYXNlIGhlbHAgdXMgb3V0IGJ5IHJlZ2lz
dGVyaW5nIGFzYXAgaWYgeW91IHBsYW4gdG8gYXR0ZW5kLg0KICAgIA0KICAgIENoZWNrIG91dCB0
aGUgdXBkYXRlZCBsaXN0IG9mIHByb2plY3RzIGFuZCBmaW5kIGxpbmtzIGZvciByZWdpc3RyYXRp
b24gaGVyZToNCiAgICBodHRwczovL3d3dy5pZXRmLm9yZy9yZWdpc3RyYXRpb24vTWVldGluZ1dp
a2kvd2lraS85OWhhY2thdGhvbg0KICAgIA0KICAgIE5ldyBwcm9qZWN0cyBhcmUgc3RpbGwgd2Vs
Y29tZSBhcyB3ZWxsLg0KICAgIA0KICAgIFRoYW5rcywNCiAgICBDaGFybGVzDQogICAgDQogICAg
DQoNCg==


From nobody Tue Jun 20 13:29:19 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 23394129458; Mon, 19 Jun 2017 09:12:00 -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 Third and FINAL Call for Volunteers
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149788872004.10693.15641542068601991395.idtracker@ietfa.amsl.com>
Date: Mon, 19 Jun 2017 09:12:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IR5VmNbccS4QN0w4wybN_1e62xk>
X-Mailman-Approved-At: Tue, 20 Jun 2017 13:29:18 -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: Mon, 19 Jun 2017 16:12:00 -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.

Some 201 people have already volunteered by ticking the box on the IETF 96 through 98 registration forms. I will contact all of these volunteers 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)
    Adam Roach (ART)
 

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 short order.

Thank you!

Peter Yee
peter at akayla dot com
nomcom-chair-2017 at ietf dot org


From nobody Wed Jun 21 02:33:51 2017
Return-Path: <rwilton@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 8B4B3131C9B; Wed, 21 Jun 2017 02:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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, 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 kG0U8Hi3dI3O; Wed, 21 Jun 2017 02:33:46 -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 95DF4131C9F; Wed, 21 Jun 2017 02:33:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5295; q=dns/txt; s=iport; t=1498037622; x=1499247222; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=Uh8lzV2yIHZZfxnMoT74xKXwSgWvBg0dGBMqwCreJQQ=; b=Z8ZsqoXqfaaZX9q2HZv21GF/vvsUZwf83DMsu6lk6h9zUMsExr4z6g/a kvpu5T+LPeWlnqrDWt2qNUr8PscgcEKMkuc/ytHiAV6NERaQ89EVdyvjY GHoKfLNGOnYF/KCw/+Fs6FYUh9wmUHRoYlIkK3JQsxUo+waQ9Q2YUTCGk Q=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AqAQB3PEpZ/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgyuBD4ENg2yKGXOQbCKILI1MghEshXgCgy0YAQIBAQEBAQEBayi?= =?us-ascii?q?FGAEBAQEDIw8BBTMODAQLEQQBAQECAiMDAgIhJQkIBgEMBgIBAYoQAxUQqXGCJ?= =?us-ascii?q?oc5DYQWAQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWBC4VigWArC4FigQyCV4UlgkI?= =?us-ascii?q?fAQSeJzuHM4dIhGeLG4Zzi15siEcfOIEKMCEIGxVJhQ0cgWc/NolqAQEB?=
X-IronPort-AV: E=Sophos;i="5.39,368,1493683200"; d="scan'208";a="695301888"
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; 21 Jun 2017 09:33:37 +0000
Received: from [10.63.23.55] (dhcp-ensft1-uk-vla370-10-63-23-55.cisco.com [10.63.23.55]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v5L9XaGl021449; Wed, 21 Jun 2017 09:33:36 GMT
Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
To: Xufeng Liu <Xufeng_Liu@jabil.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "draft-ietf-teas-yang-te-topo.all@ietf.org" <draft-ietf-teas-yang-te-topo.all@ietf.org>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com>
Date: Wed, 21 Jun 2017 10:33:36 +0100
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: <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/bheDDQC7Em8gVnGQcVrfPMh4iAY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 09:33:50 -0000

Hi Xufeng,

On 12/06/2017 22:28, Xufeng Liu wrote:
> Hi Mahesh,
>
> Thank you much for the review. We have submitted an updated draft (https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09) to address these issues. More detailed explanations are put below inline.
>
> If the responses and updates are satisfactory, we are ready for the last call.
>
> Best regards,
> - Xufeng
>
>> -----Original Message-----
>> From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com]
>> Sent: Wednesday, May 24, 2017 11:44 AM
>> 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
>>
>> 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?
> [Xufeng] Containers that use “presence” are:
> 	- Container “underlay”
> 	  o  We have changed 13 occurrences of such containers to be not presence container.
> 	- Container “te” under augmentation
> 	  o  To indicate that “TE” is enabled (configuration data)
> 	  o  Also used to do augmentation. The “presence” statement can prevent the mandatory child from affecting augmented base model.
> 	- /nw:networks/nw:network/nw:network-types/te-topology!
> 	  o  A mechanism required by I2RS topology model to specify the topology type.
>
>> 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.
> [Xufeng] Yes. These two terms are the same. Figure 12, Figure 13, and relevant descriptions have been updated to make the document consistent.
>
>> 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.
> [Xufeng] We have removed the following groupings
>      te-link-augment
>      te-node-augment
>      te-termination-point-augment
>      te-topologies-augment
>      te-topology-augment
>      te-link-state-underlay-attributes
>      te-node-state-derived-notification
>      te-topology-type
>
> The remaining groupings have been kept so that we can:
> 	- Share the groupings in this model
> 	- Prepare to be shared by a model augmenting this model
> 	- Prevent a grouping or configuration section from being too long
> 	- Improve readability
>
>> The split between config and state containers does not seem to follow any
>> particular pattern.
> [Xufeng] The pattern is clear:
> For each manageable entity (object), there is a config container and state container. The configurable properties go into the config container and state properties go into the state container. Such objects are identified by a list item or a presence container so that the “create”, “delete”, and “modify” operations can be performed on them. The non-presence containers do not represent configuration data so they do not introduce such objects.
>
>> It is neither a top level split, as is the case with existing IETF
>> models,
> [Xufeng] We could not do top level split because the base I2RS network topology model (https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-12) that we augment does not have the top-level split (for its own reasons).
>
>> nor do they follow the OpenConfig style of splitting config and state
>> under each relevant leaf,
> [Xufeng] The pattern is consistent with this style in principle, with some adjustments to fit to our multiple levels of hierarchy.
This is effectively a new forth style of YANG models that is not 
consistent with any of the three existing styles, i.e.:
  - Current IETF config/state split model style
  - NMDA combined config/state tree
  - OpenConfig split config/state containers immediately above the 
config true leaves.

Tooling that it designed to work with OpenConfig models will need 
customization to work with these TE models because the config/state 
containers will not be where the tooling expects them to be.

Thanks,
Rob


From nobody Wed Jun 21 05:34:23 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 842B5129AB0 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 05:34:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=dYd3MPbA; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=IXfpHwiU
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RymEhybrgADr for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 05:34:20 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A74571294C9 for <ietf@ietf.org>; Wed, 21 Jun 2017 05:34:20 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 20443206B5 for <ietf@ietf.org>; Wed, 21 Jun 2017 08:34:20 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Wed, 21 Jun 2017 08:34:20 -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=gFxnmq KcJdimkEUEvg/IerY42XdC/GEiuqQOx3yCiNA=; b=dYd3MPbAxQP6T5y30RnFPc c33GqNtLwpbVjwQwOhwyEwsofd+08sdyV015Z/BZsqOAgrTsyXD12nxngwa1+JaO d01VuH3XPpNDhEVX0b0L56x7BT41S71qZLBhEIYGQ1IQ/4rEca2c05hngZjqwKps A+Jah9LnzZ2Wvz/1R2mP1ChfUHrfq4UqV+fYDVKY0T7Rp6TXeId6LnkJX3uAkfcT Z5EmV/JqMVdqIdNug2DOwfEubg5mSTSKLdbFMiPCIMkx3KhOuKV0xmalZfqybMtn oTtIGCswjL8ziwe826ZDUIO34gZd56L2zkW2ur1w+/S5O7qFhq8CVJqkaoai5+vw ==
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=gFxnmqKcJdimkEUEvg/IerY42XdC/GEiuqQOx3yCi NA=; b=IXfpHwiUZpG5e/D/WSPUywIvbdXpGzqKgvpsLvlQJUWyXI1Jc1XJZ2lxI IO7meIOkfdaXD6imA6VNw7xNd8ROo7y83E2PYdGLNTCprvPqWF8P/iSoFWQASPns f8aYZ+fYOmbS0IYHfCJtIMlwGEuSQWnwJnS3lCDzwDDyE4HyCB/vatFR8kGOeqEf 2TWiWrNh2LGdNJiaG2huIh1i7OoVa8Wl4tSCRU79/S41BLfCtCRI/mfK/pNeFxFZ QVdpN7hAnmQabJ7RVg8MPedIbFNTQRQ+weWMerhvwkvOlYGI1ddxYqvNhPjrsdcj BbROKpe5v5yjwUb4g7iklERxDcvxQ==
X-ME-Sender: <xms:zGdKWV_E7_0hfWinBkRpwf2pZXQstZHFDXbEH9z665KzcmGEpdEvMw>
X-Sasl-enc: 5bEhLTc9bLycSb2RmPTYp2fK9rTZZTMZ2j+ycxnOHXs3 1498048459
Received: from sjc-alcoop-8812.cisco.com (unknown [128.107.241.191]) by mail.messagingengine.com (Postfix) with ESMTPA id 902C32466C for <ietf@ietf.org>; Wed, 21 Jun 2017 08:34:19 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8F8B9428-0355-418C-8BD0-32394B371003"
Subject: Saturday as start day
Message-Id: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in>
Date: Wed, 21 Jun 2017 08:34:17 -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/GYTUFMWKyQ5B8m0Xzyf7fXMQ5v0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 12:34:22 -0000

--Apple-Mail=_8F8B9428-0355-418C-8BD0-32394B371003
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi all,

Based on a suggestion from Paul Hoffman, the IESG believes it would be =
beneficial to denote the official start of IETF meetings to be on =
Saturday rather than Sunday, starting with IETF 100. We believe this =
would be sensible given that events such as the hackathon and code =
sprint start on Saturday, and may make it easier for some participants =
to get travel approval to attend those events. This change would be =
reflected in the dates posted on the IETF web site and sent out in email =
announcements. We are not proposing any changes in terms of the =
scheduling of any meeting-related events, the full availability of the =
meeting network starting on Sunday, the opening of on-site registration, =
or the meeting fee.

If you have feedback about this change, please send it to ietf@ietf.org =
<mailto:ietf@ietf.org>, or exceptionally to iesg@ietf.org =
<mailto:iesg@ietf.org>, by July 5, 2017.

Thanks,
The IESG=

--Apple-Mail=_8F8B9428-0355-418C-8BD0-32394B371003
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"">Hi all,<div class=3D""><br class=3D""></div><div =
class=3D""><div class=3D"">Based on a suggestion from Paul Hoffman, the =
IESG believes it would be beneficial to denote the official start of =
IETF meetings to be on Saturday rather than Sunday, starting with IETF =
100. We believe this would be sensible given that events such as the =
hackathon and code sprint start on Saturday, and may make it easier for =
some participants to get travel approval to attend those events. This =
change would be reflected in the dates posted on the IETF web site and =
sent out in email announcements. We are not proposing any changes in =
terms of the scheduling of any meeting-related events, the full =
availability of the meeting network starting on Sunday, the opening of =
on-site registration, or the meeting fee.</div><div class=3D""><br =
class=3D""></div><div class=3D"">If you have feedback about this change, =
please send it 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>, by July 5, =
2017.<br class=3D""><br class=3D"">Thanks,<br class=3D"">The =
IESG</div></div></body></html>=

--Apple-Mail=_8F8B9428-0355-418C-8BD0-32394B371003--


From nobody Wed Jun 21 05:47:05 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 D60E012946F for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 05:47:03 -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 94lUgk4nrTQD for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 05:47:01 -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 8D13B129435 for <ietf@ietf.org>; Wed, 21 Jun 2017 05:47:01 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id 77so133664724wrb.1 for <ietf@ietf.org>; Wed, 21 Jun 2017 05:47:01 -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=va2rDI2ZnfBzYtKBa5wchnbY/zhHA32OZtrcVD/Mf/8=; b=USt5PqYH8wYAa/elUmtTzjjP9RqoJbWysiANsM3Bu5OzGJuwmzSHDZdv8ei0I9vJSa wy8rnVDE/MQJN1As6o2V4QhXJ5iJMfqmbx7W7KV99prelpJjzIhRFHHuDrrRU/rLPrGw UseFwOAM0mH+TFPrzBLfNZOQK/A+iP/v+KYP5N/uLNBkhlF1v8RUMgDg9KaajEPG3T1j xvvt8sM94Q4uUHxYUr3aSL7wp34A2835xhOfooNd/BPhCCqhWPnuVKOtiQ+vfETxdx+x eFQ1DmFXImBAgewgq63pCx4uUoQYHfjgMtxt+4KSc8OJJc2GZgu2GeChee/HyIYiJYE/ FutQ==
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=va2rDI2ZnfBzYtKBa5wchnbY/zhHA32OZtrcVD/Mf/8=; b=kajU6qfPiAdeft6fx9m3bGv58rgUC93gR+JUT8SvmQ/bW06v5vhBCvREWCfFk9x4RJ 6CchVcadONKRLIfsHh9U3C3OLjV5K92tOP21BR/nEksySeZ7DC+6cqwQAUTDrj3oZNeX sxWW3bySRg3/bF20VHAaw5oVUoQlgrFpNaJgn1HPLqRJIj0Zafx6kYoJLAdgNteX/jmk OovqABuZMaSaC6dwD5/feBwXrq7ZgUJGwhUjT3UGY3ecuG5UO61BUxSnk/ywuviJCfUq t0alL7AtZWN9dSOj/3ZzD+ukjJpuZloiolx3+VPipoWzrF9jJ+WOquC1+m5VZ0XstyOP Rapw==
X-Gm-Message-State: AKS2vOzw5+hYbQZ+5cujhNfTkUR3+q2vLE9CTUVbcdSwUarJoER/ERQ9 GVSyeGN+TTFI7w==
X-Received: by 10.223.152.20 with SMTP id v20mr26245925wrb.8.1498049220084; Wed, 21 Jun 2017 05:47:00 -0700 (PDT)
Received: from [172.24.228.74] (dyn32-131.checkpoint.com. [194.29.32.131]) by smtp.gmail.com with ESMTPSA id i5sm10474714wmc.0.2017.06.21.05.46.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Jun 2017 05:46:59 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Message-Id: <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_B238F067-7AC7-4D70-98D1-59A1F2D73340"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Saturday as start day
Date: Wed, 21 Jun 2017 15:46:57 +0300
In-Reply-To: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in>
Cc: Bob Hinden <bob.hinden@gmail.com>, IETF <ietf@ietf.org>
To: Alissa Cooper <alissa@cooperw.in>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/kwBV19d4g1xvg6MeH28riy8GS0s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 12:47:04 -0000

--Apple-Mail=_B238F067-7AC7-4D70-98D1-59A1F2D73340
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Alissa,

> On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>=20
> Hi all,
>=20
> Based on a suggestion from Paul Hoffman, the IESG believes it would be =
beneficial to denote the official start of IETF meetings to be on =
Saturday rather than Sunday, starting with IETF 100. We believe this =
would be sensible given that events such as the hackathon and code =
sprint start on Saturday, and may make it easier for some participants =
to get travel approval to attend those events. This change would be =
reflected in the dates posted on the IETF web site and sent out in email =
announcements. We are not proposing any changes in terms of the =
scheduling of any meeting-related events, the full availability of the =
meeting network starting on Sunday, the opening of on-site registration, =
or the meeting fee.
>=20

I think this is a fine idea, essentially formalizing what has happened =
informally.  I suspect once in effect it will push the network to be =
deployed earlier, but given current Saturday events, that was also =
probably going to happen at some point.

Thanks,
Bob



> If you have feedback about this change, please send it to =
ietf@ietf.org, or exceptionally to iesg@ietf.org, by July 5, 2017.
>=20


--Apple-Mail=_B238F067-7AC7-4D70-98D1-59A1F2D73340
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

iQEcBAEBCgAGBQJZSmrBAAoJEK7rdBF357uowLsIAL+r8sq61JOgpQYBDNkvUzz9
jCm6CJrznVym5wM0uQCRM4IIV6ZVkXcAt/OD5ygQ/3BoUo0PLaZn2Qtbr7qpaebp
X0oyAHrURlI8KgIdLkivCcwI9lRDQFwnu5LnlEJeZNt5F0jUdPyQSd1+hyrt7m0Y
dXcfg17cVlq3H5+dBEjIdfe2duZ6OCelRJA/cZm+ZsH84A+Q7cH3YZp389dwb2oh
ohEQacBB56kO3hnjLCC3c7v5Q1kUQ2qBKj0zOG7lJbbMvYhMpf5J2mzqLhW8PaV1
Dq8YrwD+Sa2yIImH1ELLj5pzDzj0kekaqN/sTZLrtl/I7D7ZC4D+CRYjmluIoR8=
=u/At
-----END PGP SIGNATURE-----

--Apple-Mail=_B238F067-7AC7-4D70-98D1-59A1F2D73340--


From nobody Wed Jun 21 06:51:57 2017
Return-Path: <agmalis@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BFCB129ACC for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 06:51:55 -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 c1vbZs4fIoNh for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 06:51:51 -0700 (PDT)
Received: from mail-ot0-x231.google.com (mail-ot0-x231.google.com [IPv6:2607:f8b0:4003:c0f::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 A91A7129B06 for <ietf@ietf.org>; Wed, 21 Jun 2017 06:51:51 -0700 (PDT)
Received: by mail-ot0-x231.google.com with SMTP id r67so112419171ota.1 for <ietf@ietf.org>; Wed, 21 Jun 2017 06:51:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NK7TAcRPdylqzeSDX0Owk8Dd2v/Nw2aeqhr+zBVotxo=; b=hyq2LtdlhwVziZcB2OQsxf/AASlLYUIykRBN0QkXtJc8pkoM5o/3axDacAzVRo6lc5 vUYmWztC8LmEQGiBm807VA8O4jDLrX8N4uevnD8uXpGFmgZTUlornsr33d70CD9bUd0B xJP1STEmH8CtDiR5QQd9lo2d/6wotpVNrlN/JLgAcpdnpkG1eof6aTDBq/6stPEjFLS6 00+CQk+2GeB55B+PEKPbE+rFjI75AHVfakenvP7O5KHnrCl2i0jsOkTzGINe0Ys4hCpL mM7F2F15mRy/8UNZNoO79jqSTS1R9HzX2NqLBhib6TRS96hGblNbiHJWnfJnHgL79h2V 3bAw==
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=NK7TAcRPdylqzeSDX0Owk8Dd2v/Nw2aeqhr+zBVotxo=; b=qOCAH7o1xpvewPpfugXE6/iU0V3bVB8Yx273XD+KqzoonTb/QP0SmrPNGwNffHlBeX CJGebMjjjKgPS0/CFSH26cXgon3dLEl7noRU7jTS1b2snT+TxG+Qym6L2+YoX1jI3HPT dSdG969dZB4DQ1RSAdKPLIgC9W+r/ka03T/mZOfDYT1eR591N7CTf8iI28I/43z/wAmt y/sNfdaB4yZ3QdAvOBkW1XAqb3pzqNNBc/TrMqDbJfykmLCWR1ohRYs3Wdh54fnEb1al xQXaSpglxQpn327JRtwGyG4UkOnY34cIsrzaAhby4OiY0JfN1Mmy5tyCHHbU3u4BrtYU 6UgA==
X-Gm-Message-State: AKS2vOxj1Xjawc3nN8kvGtyIQo3fAMhVXB9oyEEEo7Nd9h3m1FAXX9U2 NBhRw5FpK42Qd3ZzicbN8JISkz9fOA==
X-Received: by 10.157.42.4 with SMTP id t4mr14476596ota.146.1498053111082; Wed, 21 Jun 2017 06:51:51 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.46.165 with HTTP; Wed, 21 Jun 2017 06:51:30 -0700 (PDT)
In-Reply-To: <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 21 Jun 2017 09:51:30 -0400
Message-ID: <CAA=duU1YkjbUoc_MUyq8oVFPzr6HEKYWRoy+6VHXU9SoNJoXYA@mail.gmail.com>
Subject: Re: Saturday as start day
To: Bob Hinden <bob.hinden@gmail.com>
Cc: Alissa Cooper <alissa@cooperw.in>, IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113582ac8a757e055278aba4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/GLX0vXBzawQorwkFo_ukOZhnN6M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 13:51:55 -0000

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

I agree, this is an excellent idea.

Cheers,
Andy


On Wed, Jun 21, 2017 at 8:46 AM, Bob Hinden <bob.hinden@gmail.com> wrote:

> Alissa,
>
> > On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw.in> wrote:
> >
> > Hi all,
> >
> > Based on a suggestion from Paul Hoffman, the IESG believes it would be
> beneficial to denote the official start of IETF meetings to be on Saturday
> rather than Sunday, starting with IETF 100. We believe this would be
> sensible given that events such as the hackathon and code sprint start on
> Saturday, and may make it easier for some participants to get travel
> approval to attend those events. This change would be reflected in the
> dates posted on the IETF web site and sent out in email announcements. We
> are not proposing any changes in terms of the scheduling of any
> meeting-related events, the full availability of the meeting network
> starting on Sunday, the opening of on-site registration, or the meeting fee.
> >
>
> I think this is a fine idea, essentially formalizing what has happened
> informally.  I suspect once in effect it will push the network to be
> deployed earlier, but given current Saturday events, that was also probably
> going to happen at some point.
>
> Thanks,
> Bob
>
>
>
> > If you have feedback about this change, please send it to ietf@ietf.org,
> or exceptionally to iesg@ietf.org, by July 5, 2017.
> >
>
>

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

<div dir=3D"ltr">I agree, this is an excellent idea.<div><br></div><div>Che=
ers,</div><div>Andy</div><div><br></div></div><div class=3D"gmail_extra"><b=
r><div class=3D"gmail_quote">On Wed, Jun 21, 2017 at 8:46 AM, Bob Hinden <s=
pan dir=3D"ltr">&lt;<a href=3D"mailto:bob.hinden@gmail.com" target=3D"_blan=
k">bob.hinden@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">Alissa,<br>
<span class=3D""><br>
&gt; On Jun 21, 2017, at 3:34 PM, Alissa Cooper &lt;<a href=3D"mailto:aliss=
a@cooperw.in">alissa@cooperw.in</a>&gt; wrote:<br>
&gt;<br>
&gt; Hi all,<br>
&gt;<br>
&gt; Based on a suggestion from Paul Hoffman, the IESG believes it would be=
 beneficial to denote the official start of IETF meetings to be on Saturday=
 rather than Sunday, starting with IETF 100. We believe this would be sensi=
ble given that events such as the hackathon and code sprint start on Saturd=
ay, and may make it easier for some participants to get travel approval to =
attend those events. This change would be reflected in the dates posted on =
the IETF web site and sent out in email announcements. We are not proposing=
 any changes in terms of the scheduling of any meeting-related events, the =
full availability of the meeting network starting on Sunday, the opening of=
 on-site registration, or the meeting fee.<br>
&gt;<br>
<br>
</span>I think this is a fine idea, essentially formalizing what has happen=
ed informally.=C2=A0 I suspect once in effect it will push the network to b=
e deployed earlier, but given current Saturday events, that was also probab=
ly going to happen at some point.<br>
<br>
Thanks,<br>
Bob<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
<br>
&gt; If you have feedback about this change, please send it to <a href=3D"m=
ailto:ietf@ietf.org">ietf@ietf.org</a>, or exceptionally to <a href=3D"mail=
to:iesg@ietf.org">iesg@ietf.org</a>, by July 5, 2017.<br>
&gt;<br>
<br>
</div></div></blockquote></div><br></div>

--001a113582ac8a757e055278aba4--


From nobody Wed Jun 21 06:54: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 06324129B1E for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 06:53:58 -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, 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 KTocdTaqUQuH for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 06:53:55 -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 8C07A129ACC for <ietf@ietf.org>; Wed, 21 Jun 2017 06:53:55 -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 1dNg4u-0007m8-O9 for ietf@ietf.org; Wed, 21 Jun 2017 15:53:54 +0200
Received: from [10.5.2.35] (helo=xmail10.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 1dNg4p-000598-LX for ietf@ietf.org; Wed, 21 Jun 2017 09:53:51 -0400
Received: (qmail 26932 invoked from network); 21 Jun 2017 13:53:46 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.56.42.228]) (envelope-sender <huitema@huitema.net>) by xmail10.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ietf@ietf.org>; 21 Jun 2017 13:53:45 -0000
To: ietf@ietf.org
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com>
From: Christian Huitema <huitema@huitema.net>
Message-ID: <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net>
Date: Wed, 21 Jun 2017 06:53:27 -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: <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="stwNn7I4sjfMnVdvUVBlwNnlVhwfBsFrp"
Subject: Re: Saturday as start day
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: unsure
X-SpamExperts-Outgoing-Evidence: Combined (0.13)
X-Recommended-Action: accept
X-Filter-ID: PqwsvolAWURa0gwxuN3S5YEa3T7JuZT23fGO2rGt3ZgTCGhDnudOJ80D1c8rffxrus7BTv7Ss8cH d2IQQuvdbtM+m4WpRRDP6YzwkAPgQJYWea6pBBugJdVQWCV6zgcsND46yZLY9QyX+cRXmooQ3hum JwiT+2brWmQlzkLIcXivpIH4ag6BM/+u9ym+BA23lrz9HIyuebEKk8nLMSDcPeoI9GlgXFbGvhvB 71hlmrrn5ORwPKM/mmfRgPT0b8GOYOEkjsX7F8KmpUaZQHV+SU9tg6wnJ2lrZSUCZrKFYsG2G5Pj 7iQJEmtNUzH3idZ6uMF2OhyCCCV83x+RZrKIj0QqMGQOSwmEPwP4wBzM77N8GvkYGGDFjg9NrmGY yNnXsSjdYwfRhjHqxQXDsBKLpKrrXdhf8mmRqp8CWMEqUPf6lO4FGen962xgCFRckncKfg1XSK9P 1z/R6plfrFWGyRu0Fau6oNz853nNEumLnrTeNHk15VolAGHS5rCXQKDym+Gab6cuAPzLi/SdAxlO dgkraHgbbAuZgv0Q6mJ3vUcipz1IT62ZEk6+MmovaufbiR3bHfnMCIEU+nrglojKwMr3vOY18GvB wSXAfWcj236N2IVdgBdepwvDBBcDOz9LNdSMuNhZC3X/nGdDKYyg+1Fotn1TGspRGWfHjmaruO0b XpkevaElTi+sCWwmqxHi+BUHXGjp0J8FpT+J6AFTxh8XBHmF2hIeyKfJwZiM12egGl1aPxAtivmw 3hSDPS17I2lnAh5x+KE8NH/3oFbA7y2wErj03uQL9OSP3oAqkbgmxYRXOZgzdAQCjuYKoBVKyLoA 6S28+bT6JBt5hIe9NsT+zJGLhBRfUiVo7tDfe92IvYPtoBVPF/cFj7Q8A7EvMLn6MURQGfriekzS 9Ga3AA==
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IOzVcOOp9nMPIastVt8UrOsw8Qg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 13:53:58 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--stwNn7I4sjfMnVdvUVBlwNnlVhwfBsFrp
Content-Type: multipart/mixed; boundary="Qc9c4BhCNd73NoENA5HSKT9qtMXtsbvaP";
 protected-headers="v1"
From: Christian Huitema <huitema@huitema.net>
To: ietf@ietf.org
Message-ID: <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net>
Subject: Re: Saturday as start day
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in>
 <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com>
In-Reply-To: <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com>

--Qc9c4BhCNd73NoENA5HSKT9qtMXtsbvaP
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On 6/21/2017 5:46 AM, Bob Hinden wrote:

> Alissa,
>
>> On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>>
>> Hi all,
>>
>> Based on a suggestion from Paul Hoffman, the IESG believes it would be=
 beneficial to denote the official start of IETF meetings to be on Saturd=
ay rather than Sunday, starting with IETF 100. We believe this would be s=
ensible given that events such as the hackathon and code sprint start on =
Saturday, and may make it easier for some participants to get travel appr=
oval to attend those events. This change would be reflected in the dates =
posted on the IETF web site and sent out in email announcements. We are n=
ot proposing any changes in terms of the scheduling of any meeting-relate=
d events, the full availability of the meeting network starting on Sunday=
, the opening of on-site registration, or the meeting fee.
>>
> I think this is a fine idea, essentially formalizing what has happened =
informally.  I suspect once in effect it will push the network to be depl=
oyed earlier, but given current Saturday events, that was also probably g=
oing to happen at some point.
Matching reality is always a fine idea. But there might be a problem
with that reality...
>> If you have feedback about this change, please send it to ietf@ietf.or=
g, or exceptionally to iesg@ietf.org, by July 5, 2017.
The problem is that we now are expected to have work going non stop from
Saturday to Friday. 7 full days. Maybe I am just old, but that does not
look healthy.

-- Christian Huitema



--Qc9c4BhCNd73NoENA5HSKT9qtMXtsbvaP--

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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJZSnpoAAoJELba05IUOHVQZ98IAIIMNxAa7CWG2Lw8ypZT8Q0T
b49Nh0YpoDCJfuvGkb+Pq5QEKS078zFkwGqQPxNgJu4ifarn3F9YXDDC8GJ2+unF
cUGhoWmHxWSJw+Ybl8QxtZFl1ggT+vFcsNFAza3hhSPTR/1I/nCOjQt1SZM5AyO8
0WAL86jGt13dNlb5ThqIoQiUeWyWPK2mr1m8jdlnYAnKM1l7RgAkOKB3VWv8iqWJ
kXVWJjZRXWW26F8AmjoG8E2mif92wjgszjnKPH3QfvRibKXXn9CwjqX3pdNxbPUb
1hyFFhDVVw2530aNHjf1zSvk+/hZrBRc9lT988uAeNOLKXYBthlSr4Izi1/ZTbg=
=YKHS
-----END PGP SIGNATURE-----

--stwNn7I4sjfMnVdvUVBlwNnlVhwfBsFrp--


From nobody Wed Jun 21 06:57:00 2017
Return-Path: <tnadeau@lucidvision.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64226129B1E for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 06:56:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_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=lucidvision.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3ZeLsAfCjwot for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 06:56:56 -0700 (PDT)
Received: from lucidvision.com (lucidab1.miniserver.com [78.31.106.147]) (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 5CD29129A8D for <ietf@ietf.org>; Wed, 21 Jun 2017 06:56:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lucidvision.com; s=default; t=1498053356; bh=TB7Rw/YHpoytIt52+pJMWaQuCQrMXr19s5xG2S6wol0=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=GE01PvR6pCQy06d3z8fxF/pHKE/C4/WtkEGFKHqBjRtlgK/OVY3aODGg+Eaz1/fxi XiJMkLKxwvDmqTTgJp15ajpuqIg6VBqp+Fe+HKaKRHFXrTpX33rvvmW4NBGJS//EAY eSxGNOpDYD7tk+bokYUqzDMIshmRD3/RXUWQ5CxQ=
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=50.255.148.181; 
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Saturday as start day
From: Thomas Nadeau <tnadeau@lucidvision.com>
In-Reply-To: <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net>
Date: Wed, 21 Jun 2017 09:56:51 -0400
Cc: ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F62C85D-07BE-4F39-86AC-0BDD2F7C7825@lucidvision.com>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net>
To: Christian Huitema <huitema@huitema.net>
X-Mailer: Apple Mail (2.3273)
X-Authenticated-User: tnadeau@lucidvision.com 
X-Info: aspam skipped due to (g_smite_skip_relay)
X-Encryption: SSL encrypted
X-MyRbl: Color=Yellow Age=0 Spam=0 Notspam=4 Stars=0 Good=0 Friend=2 Surbl=0 Catch=0 r=0 ip=50.255.148.181
X-IP-stats: Notspam Incoming Last 0, First 768, in=5852, out=0, spam=0 Known=true ip=50.255.148.181
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/a5RrIMohyVIB4ZhABrTJz063HGo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 13:56:58 -0000

	It can also pose interesting issues pertaining to travel.

	=E2=80=94Tom

> On Jun 21, 2017:9:53 AM, at 9:53 AM, Christian Huitema =
<huitema@huitema.net> wrote:
>=20
> On 6/21/2017 5:46 AM, Bob Hinden wrote:
>=20
>> Alissa,
>>=20
>>> On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw.in> =
wrote:
>>>=20
>>> Hi all,
>>>=20
>>> Based on a suggestion from Paul Hoffman, the IESG believes it would =
be beneficial to denote the official start of IETF meetings to be on =
Saturday rather than Sunday, starting with IETF 100. We believe this =
would be sensible given that events such as the hackathon and code =
sprint start on Saturday, and may make it easier for some participants =
to get travel approval to attend those events. This change would be =
reflected in the dates posted on the IETF web site and sent out in email =
announcements. We are not proposing any changes in terms of the =
scheduling of any meeting-related events, the full availability of the =
meeting network starting on Sunday, the opening of on-site registration, =
or the meeting fee.
>>>=20
>> I think this is a fine idea, essentially formalizing what has =
happened informally.  I suspect once in effect it will push the network =
to be deployed earlier, but given current Saturday events, that was also =
probably going to happen at some point.
> Matching reality is always a fine idea. But there might be a problem
> with that reality...
>>> If you have feedback about this change, please send it to =
ietf@ietf.org, or exceptionally to iesg@ietf.org, by July 5, 2017.
> The problem is that we now are expected to have work going non stop =
from
> Saturday to Friday. 7 full days. Maybe I am just old, but that does =
not
> look healthy.
>=20
> -- Christian Huitema
>=20
>=20


From nobody Wed Jun 21 07:01:33 2017
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC91412702E for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 07:01:32 -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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ecs.soton.ac.uk
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o0FYsoH0CMqR for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 07:01:28 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EB72A1294CF for <ietf@ietf.org>; Wed, 21 Jun 2017 07:01:27 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v5LE1D1S003481; Wed, 21 Jun 2017 15:01:13 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk v5LE1D1S003481
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1498053674; bh=jVAKply6a5YdP3enuMKNwOmmcAg=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=FMWrql6hTzest6JtIrxPp0sEKkUOWi2QXroYVEQrPq/YK3vi7EXKijs+rrad8+yAP SFQzoJs3z62aNikBdKbBg/snLeuqVgejq0vxqRkjlX+A8KlHPYZZo5U03kxI/6d8UT zZSJNlwksgaDAGWaKBJNlTLeuM5STJbVp7t6Z+Cw=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id y5KF1D2961306636BK ret-id none; Wed, 21 Jun 2017 15:01:14 +0100
Received: from jntlt005491.atlas.ukerna.ac.uk (d7test.company.ja.net [193.62.83.225]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id v5LE18KN028309 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 21 Jun 2017 15:01:09 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Saturday as start day
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <2F62C85D-07BE-4F39-86AC-0BDD2F7C7825@lucidvision.com>
Date: Wed, 21 Jun 2017 15:01:08 +0100
Cc: Christian Huitema <huitema@huitema.net>, ietf@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|82a11207572e527158717bcf8b4445f0y5KF1D03tjc|ecs.soton.ac.uk|4A92ADFA-3605-4837-BF23-0D0F30C991F9@ecs.soton.ac.uk>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net> <2F62C85D-07BE-4F39-86AC-0BDD2F7C7825@lucidvision.com> <4A92ADFA-3605-4837-BF23-0D0F30C991F9@ecs.soton.ac.uk>
To: Thomas Nadeau <tnadeau@lucidvision.com>
X-Mailer: Apple Mail (2.3273)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=y5KF1D296130663600; tid=y5KF1D2961306636BK; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: v5LE1D1S003481
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vwSOgBrBd5XwxYazhUH7E2I-VIo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 14:01:32 -0000

> On 21 Jun 2017, at 14:56, Thomas Nadeau <tnadeau@lucidvision.com> =
wrote:
>=20
> 	It can also pose interesting issues pertaining to travel.

If it=E2=80=99s purely a change to help people get visas and travel =
approval to attend Saturday events, esp. the hackathon, great. =
No-one=E2=80=99s travel plans are changed, I think?

If WG meetings start creeping into the weekend, I=E2=80=99d agree!

Tim

>=20
> 	=E2=80=94Tom
>=20
>> On Jun 21, 2017:9:53 AM, at 9:53 AM, Christian Huitema =
<huitema@huitema.net> wrote:
>>=20
>> On 6/21/2017 5:46 AM, Bob Hinden wrote:
>>=20
>>> Alissa,
>>>=20
>>>> On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw.in> =
wrote:
>>>>=20
>>>> Hi all,
>>>>=20
>>>> Based on a suggestion from Paul Hoffman, the IESG believes it would =
be beneficial to denote the official start of IETF meetings to be on =
Saturday rather than Sunday, starting with IETF 100. We believe this =
would be sensible given that events such as the hackathon and code =
sprint start on Saturday, and may make it easier for some participants =
to get travel approval to attend those events. This change would be =
reflected in the dates posted on the IETF web site and sent out in email =
announcements. We are not proposing any changes in terms of the =
scheduling of any meeting-related events, the full availability of the =
meeting network starting on Sunday, the opening of on-site registration, =
or the meeting fee.
>>>>=20
>>> I think this is a fine idea, essentially formalizing what has =
happened informally.  I suspect once in effect it will push the network =
to be deployed earlier, but given current Saturday events, that was also =
probably going to happen at some point.
>> Matching reality is always a fine idea. But there might be a problem
>> with that reality...
>>>> If you have feedback about this change, please send it to =
ietf@ietf.org, or exceptionally to iesg@ietf.org, by July 5, 2017.
>> The problem is that we now are expected to have work going non stop =
from
>> Saturday to Friday. 7 full days. Maybe I am just old, but that does =
not
>> look healthy.
>>=20
>> -- Christian Huitema
>>=20
>>=20
>=20


From nobody Wed Jun 21 07:39:29 2017
Return-Path: <Jason_Livingood@comcast.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EE8C129B51 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 07:39:28 -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 stX18uLZfxyV for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 07:39:26 -0700 (PDT)
Received: from vaadcmhout02.cable.comcast.com (vaadcmhout02.cable.comcast.com [96.114.28.76]) (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 939FA129B9B for <ietf@ietf.org>; Wed, 21 Jun 2017 07:39:18 -0700 (PDT)
X-AuditID: 60721c4c-82dff7000000211d-5a-594a85146c2f
Received: from VAADCEX33.cable.comcast.com (vaadcmhoutvip.cable.comcast.com [96.115.73.56]) (using TLS with cipher AES256-SHA256 (256/256 bits)) (Client did not present a certificate) by vaadcmhout02.cable.comcast.com (SMTP Gateway) with SMTP id 7A.14.08477.4158A495; Wed, 21 Jun 2017 10:39:17 -0400 (EDT)
Received: from VAADCEX37.cable.comcast.com (147.191.103.214) by VAADCEX33.cable.comcast.com (147.191.103.210) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Wed, 21 Jun 2017 10:39:15 -0400
Received: from VAADCEX37.cable.comcast.com ([fe80::3aea:a7ff:fe12:38b0]) by VAADCEX37.cable.comcast.com ([fe80::3aea:a7ff:fe12:38b0%19]) with mapi id 15.00.1263.000; Wed, 21 Jun 2017 10:39:15 -0400
From: "Livingood, Jason" <Jason_Livingood@comcast.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Saturday as start day
Thread-Topic: Saturday as start day
Thread-Index: AQHS6oq9X1lKWjNlH0+7mAei5Hj+WaIvhueAgAASlYCAAADzgIAAATIA///HmYA=
Date: Wed, 21 Jun 2017 14:39:15 +0000
Message-ID: <A9C2B9FD-A28D-404B-AF17-D5FB6695DD0D@cable.comcast.com>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net> <2F62C85D-07BE-4F39-86AC-0BDD2F7C7825@lucidvision.com> <4A92ADFA-3605-4837-BF23-0D0F30C991F9@ecs.soton.ac.uk> <EMEW3|82a11207572e527158717bcf8b4445f0y5KF1D03tjc|ecs.soton.ac.uk|4A92ADFA-3605-4837-BF23-0D0F30C991F9@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|82a11207572e527158717bcf8b4445f0y5KF1D03tjc|ecs.soton.ac.uk|4A92ADFA-3605-4837-BF23-0D0F30C991F9@ecs.soton.ac.uk>
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: [96.115.73.254]
Content-Type: text/plain; charset="utf-8"
Content-ID: <A079C2430DEC6D4E8A234BAEBF52FD49@comcast.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Forward
X-Brightmail-Tracker: H4sIAAAAAAAAA11UfUwbZRzOe72WK/Sdx5W2725AxhE/g4CbzgaIUWNix9yy6IzWhMBRTlo5 WnIfQLdE57YmOmOcSszaMDuFzWxZMlmYbGR+rAOVssWPMDUz/IGyse0fUeb8iHHeex9w9a/7 3fPc73me3+99c5SD+cXNUrG4IkhxXuRcxWSbvDF4ry/VHK5fPH5n8MpIlnwYhIaH/yK2gueK mzoEMdYrSHUPtRVHBy4OOXsGHf3n/jwPdoJ9jr3ATSH6fpT+8cuivaCYYugxAuUXRknjJQfQ 0tx+/SuGngLop8Egrl30BjT73oyOl9HV6LP0D05ce2kOLc2/Aiw8/fKrLqPegmbPTOs4Sd+O pj9Pk7iG9GPo7NhN0/ktB5q8nCfwi5tOAXT15vt6N6D96I/8MQLXDjqALs1nCSM3jYbPfGXO 4EPXfv5XT+Gja9F3i0dIA69BF76fB0Zdj04e+sTEq9Df785o+pSmeTc6Pl5nyDegQ5feLDLq KjTw2lyREbQUTaXnzdYAOjdxyrkPsBlbosyKUsamlLEpZWxKB4HzKKjs5fmOSHc0oSr162oj fLso1EYS3RFeVvDzBMBnK5U/cQr89k4oB2gKcB64o685zDj5XjnZnQNdFMH5YN8mDVrVnuhI Rnk52iqpoiBzZfC0oMFwGW5XxS6Oha49GupdRuNCnywKinaZuEq4PvF4mAksc7Iq98QisYQq t6qSqF0GyqHJ3tiFZTv45HZBShhmObCGIrkApKONYYbu5BWhSxB6BMli+yiKQ3Bmt9ZYKgmd Qv/zMVGxaK2vYrvG0HZGD1sBH3wqFGb8dsKWtwo+cpfWx9rp/0cmKHcOdFIeLfcxBeeWe/hu OdZpWnvhngYN9ViobrsarsdJGQu0WVbAIbwiv0UV2uVBClC7FkdvEAwZT8QFNgA3YyUafx5V 48sjs37YsrAxzNxmI7A1Ww6/na0PMz4bvuLOroUq7lptYwsDWD+D6yCi3RUvzGN3j/arWJmY gRswWGKC+sAINuhHY2K2ecvhKJ7XZzKFbte1xRLaYq9OhPBiFV6xL5afDOHFmqi52GcxyFhg wWJ1ym9RhU7sTtAfbmk8v1T9drIpMNq+5kr2WnLH5g+z0wfEurnkC0+6Br7I/b7tcONHbZEX Jx/IVk94WkdSBxX35U//WfAeDd6qTNWsaznxRuDp/RM1214vbf516sKtTSUfj5xdKqsrf6bk m5dKhseOfFDVcjJIJqNDdwQGBie3qrtX5efWNjHjj57+evwiR8pR/r57HJLM/weXB3SnggUA AA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/F0rh8lSxVlX3uHMEAbX16lRQS5E>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 14:39:28 -0000

Pj4+IEkgdGhpbmsgdGhpcyBpcyBhIGZpbmUgaWRlYSwgZXNzZW50aWFsbHkgZm9ybWFsaXppbmcg
d2hhdCBoYXMgaGFwcGVuZWQgaW5mb3JtYWxseS4gIEkgc3VzcGVjdCBvbmNlIGluIGVmZmVjdCBp
dCB3aWxsIHB1c2ggdGhlIG5ldHdvcmsgdG8gYmUgZGVwbG95ZWQgZWFybGllciwgYnV0IGdpdmVu
IGN1cnJlbnQgU2F0dXJkYXkgZXZlbnRzLCB0aGF0IHdhcyBhbHNvIHByb2JhYmx5IGdvaW5nIHRv
IGhhcHBlbiBhdCBzb21lIHBvaW50Lg0KDQorMQ0KDQpUaGlzIGlzIGEgZ29vZCBtb3ZlIElNTy4N
Cg0KSmFzb24NCiANCg0K


From nobody Wed Jun 21 07:40:28 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 716CD129BC5 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 07:40:26 -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 ruQ_Jipiw2Lt for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 07:40:17 -0700 (PDT)
Received: from mail-ot0-x22e.google.com (mail-ot0-x22e.google.com [IPv6:2607:f8b0:4003:c0f::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 5E365129B9B for <ietf@ietf.org>; Wed, 21 Jun 2017 07:40:01 -0700 (PDT)
Received: by mail-ot0-x22e.google.com with SMTP id r67so113488203ota.1 for <ietf@ietf.org>; Wed, 21 Jun 2017 07:40:01 -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=4vQ5o0LQ0TQkrkQEB68ZApFcsmmQYGa/THGu+AUZ2uA=; b=CrpaDxEugVYuRgt2skmol2qnu3bDW/zTpb3xsfbTspNLsZEOfcrqJomycKUduTNpSs J3ZU+Dzmnr4i6RpfrTjnBr34ugVksaB+ccLLGXIldbyzwIpLEyVjbNkbZRCuTumxiq/N diw6Gog5iZKX57mP49aWBStsWnfkblpM8AwaAxQ6n88f6/sXX66eZyRiKtfoRzdnHBDu Biu1NZsrdprvV/p1RL0Pyf/3PLak/dBPO+1ojlRlHm+4o3hQfvgKrQHNzQUNcVhZFkB/ EWMjXkQpq4Z9XpJ4f0cFMiT8clV0i21vQ5gHJh5e8HYdJRRYh4Nt39jEpnUQa2/2LTD1 VlYw==
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=4vQ5o0LQ0TQkrkQEB68ZApFcsmmQYGa/THGu+AUZ2uA=; b=uNhV5VlZ4IeQ9KK4ET8kZ+JIadupHwhAsY/nSOnsDaLN/n46MqmI+jaKz78YyJZb0+ 9+tTM8iadQlwJF6XeVVcTz4uRFer3kuu0eeQoTrskH2jJzF4ZgnLVnTNI5DH5+wAK+EO d14/T6SgA3OZ8u/uLYwRubBWJZGqjOVqkBfWepTObWu1Dz4LW7ly7m1sDgkD/BHY51DE r5IhRfq7SWJQP6+fjj+qgwuocpIU0e92n6H2xBQDyUcwNgclQxPSqcSClq5Q0Lw4zIiy t4B7BHXZBG7vwM8yit14jKIoCRqX+6zhXI/58q+HDkv4RDESvM3sR3JUPw1WEmVHvxGT nHCg==
X-Gm-Message-State: AKS2vOw6QDFIrqT1DCabFdKAcvVk6UT2qk7n4+NgvAfOkpGWTMdEiqPj TGZhy070i+2gA7AQGsZdfB/1POJ8pC1Y
X-Received: by 10.157.42.4 with SMTP id t4mr14669466ota.146.1498056000708; Wed, 21 Jun 2017 07:40:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.182.46.165 with HTTP; Wed, 21 Jun 2017 07:39:40 -0700 (PDT)
In-Reply-To: <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 21 Jun 2017 10:39:40 -0400
Message-ID: <CAA=duU1tJDYm75Ons1sH-cFu8E0Nj+0H_J6oTc57BojhZdcSxw@mail.gmail.com>
Subject: Re: Saturday as start day
To: Christian Huitema <huitema@huitema.net>
Cc: IETF Discussion <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a113582acc6aaea0552795742"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LxipB_XGXzlNmeh12ewdymh4_6g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 14:40:26 -0000

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

Christian,

Alissa clearly said that there=E2=80=99s no change to the schedule, this is=
 solely
to help attendees get visas and travel approval when they want to
participate in the hackathon and code sprint.

Cheers,
Andy


On Wed, Jun 21, 2017 at 9:53 AM, Christian Huitema <huitema@huitema.net>
wrote:

> On 6/21/2017 5:46 AM, Bob Hinden wrote:
>
> > Alissa,
> >
> >> On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw.in> wrote:
> >>
> >> Hi all,
> >>
> >> Based on a suggestion from Paul Hoffman, the IESG believes it would be
> beneficial to denote the official start of IETF meetings to be on Saturda=
y
> rather than Sunday, starting with IETF 100. We believe this would be
> sensible given that events such as the hackathon and code sprint start on
> Saturday, and may make it easier for some participants to get travel
> approval to attend those events. This change would be reflected in the
> dates posted on the IETF web site and sent out in email announcements. We
> are not proposing any changes in terms of the scheduling of any
> meeting-related events, the full availability of the meeting network
> starting on Sunday, the opening of on-site registration, or the meeting f=
ee.
> >>
> > I think this is a fine idea, essentially formalizing what has happened
> informally.  I suspect once in effect it will push the network to be
> deployed earlier, but given current Saturday events, that was also probab=
ly
> going to happen at some point.
> Matching reality is always a fine idea. But there might be a problem
> with that reality...
> >> If you have feedback about this change, please send it to ietf@ietf.or=
g,
> or exceptionally to iesg@ietf.org, by July 5, 2017.
> The problem is that we now are expected to have work going non stop from
> Saturday to Friday. 7 full days. Maybe I am just old, but that does not
> look healthy.
>
> -- Christian Huitema
>
>
>

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

<div dir=3D"ltr">Christian,<div><br></div><div>Alissa clearly said that the=
re=E2=80=99s no change to the schedule, this is solely to help attendees ge=
t visas and travel approval when they want to participate in the hackathon =
and code sprint.<div><br></div><div>Cheers,</div><div>Andy</div></div><div>=
<br></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">O=
n Wed, Jun 21, 2017 at 9:53 AM, Christian Huitema <span dir=3D"ltr">&lt;<a =
href=3D"mailto:huitema@huitema.net" target=3D"_blank">huitema@huitema.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"><span class=3D"">On =
6/21/2017 5:46 AM, Bob Hinden wrote:<br>
<br>
&gt; Alissa,<br>
&gt;<br>
&gt;&gt; On Jun 21, 2017, at 3:34 PM, Alissa Cooper &lt;<a href=3D"mailto:a=
lissa@cooperw.in">alissa@cooperw.in</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; Hi all,<br>
&gt;&gt;<br>
&gt;&gt; Based on a suggestion from Paul Hoffman, the IESG believes it woul=
d be beneficial to denote the official start of IETF meetings to be on Satu=
rday rather than Sunday, starting with IETF 100. We believe this would be s=
ensible given that events such as the hackathon and code sprint start on Sa=
turday, and may make it easier for some participants to get travel approval=
 to attend those events. This change would be reflected in the dates posted=
 on the IETF web site and sent out in email announcements. We are not propo=
sing any changes in terms of the scheduling of any meeting-related events, =
the full availability of the meeting network starting on Sunday, the openin=
g of on-site registration, or the meeting fee.<br>
&gt;&gt;<br>
&gt; I think this is a fine idea, essentially formalizing what has happened=
 informally.=C2=A0 I suspect once in effect it will push the network to be =
deployed earlier, but given current Saturday events, that was also probably=
 going to happen at some point.<br>
</span>Matching reality is always a fine idea. But there might be a problem=
<br>
with that reality...<br>
<span class=3D"">&gt;&gt; If you have feedback about this change, please se=
nd it to <a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>, or exceptional=
ly to <a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>, by July 5, 2017.<=
br>
</span>The problem is that we now are expected to have work going non stop =
from<br>
Saturday to Friday. 7 full days. Maybe I am just old, but that does not<br>
look healthy.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
-- Christian Huitema<br>
<br>
<br>
</font></span></blockquote></div><br></div>

--001a113582acc6aaea0552795742--


From nobody Wed Jun 21 09:31:08 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 0678512EBCD for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 09:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 TZ3WZnXfl6sB for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 09:30:57 -0700 (PDT)
Received: from miucha.iecc.com (www.iecc.com [IPv6:2001:470:1f07:1126::4945:4343]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C150129B1A for <ietf@ietf.org>; Wed, 21 Jun 2017 09:30:56 -0700 (PDT)
Received: (qmail 30799 invoked from network); 21 Jun 2017 16:30:55 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 21 Jun 2017 16:30:55 -0000
Date: 21 Jun 2017 16:30:33 -0000
Message-ID: <20170621163033.22249.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: ietf@ietf.org
Cc: huitema@huitema.net
Subject: Re: Saturday as start day
In-Reply-To: <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net>
Organization: 
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rdHg38K7_sjL-mkDesCv6IMi2TY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 16:31:07 -0000

In article <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net> you write:
>Matching reality is always a fine idea. But there might be a problem
>with that reality...

My only concern is that if the announcement says it starts Saturday,
people will take that as permission to start scheduling stuff on the
preceding Friday, "the day before".

I'm thinking of weasel wording, e.g., pre-meeting activities on Saturday,
meeting Sunday-Friday.

R's,
John

PS: See any ICANN meeting calendar to see what I mean.


From nobody Wed Jun 21 09:47:36 2017
Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 738BC1286B2 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 09:47:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.411
X-Spam-Level: 
X-Spam-Status: No, score=0.411 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FORGED_MUA_MOZILLA=2.309, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tyScNm_zTPT0 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 09:47:32 -0700 (PDT)
Received: from sonic315-16.consmr.mail.gq1.yahoo.com (sonic315-16.consmr.mail.gq1.yahoo.com [98.137.65.40]) (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 3CAF6127286 for <ietf@ietf.org>; Wed, 21 Jun 2017 09:47:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1498063651; bh=+9sdyAscy+0vWC1b/S722fqw3E36r6ttUzlMKQB0iCw=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=gRi94B/e1oL3qOVHS1xsxVmMYPfsZDr1AAaSu79b1ZTtjT7JIs/2OArRVMBXMoMEFOa5VDbaJ4C/0LcI8tQaEMV06bmG4fT1tEiLBhemnSO5c2i8VqOLJlMGWtMC1AXX2bjRph4Tpgu5UbAvd9k7GVw6Bgq2DMTYzIht8FispINQIznYfmL/CO/5PCApY252iK4M4RhX8/SUOITO/EAEW0RUvRd/6A+HVcyvt0xYYZ4rH5vkjIUb6FqnEaU+RK69AilokSo6k2k9c7qmkc9QU0NDvzMwof1k/CsoZ6oJIDf7eQ9bv4croX40Eu6lxqg5F8jRbGKKdFfBkprKPDVOIA==
X-YMail-OSG: lnHLbeMVM1lJ5s_Uz2QslY_edbTYaYWDZRm3LvJSslskSha9owVUt3A4XGE4Wyk 1_8NyTFRUjN3xWyipvhNoflvcG9IxIN_.n2LkBxEzKNabftJs9Hpxooz_JjFBc8GxTMZcrmJpWIv z_6o.kQae6DQHTyjsafL0r3zEHxQZmKSAP2K4GIo5mbsaRYUjeB6cGtKpdnBy_wuVDbTczg9.F4. piyw44RxhjWBwv1AQUdnEnQ7aVyzuyOJyPmiWg51iKzxXY_zz7czIbql2NSETHs2KTxNCdjCQU4z daHms1noL_lJ9iJp6OMiDp4p.mI4NljK1MtH_xhRIBOluRhVsAJDLR2bciGgtROlBqYrjPdhVGJh V0ev7Ba7uBlGL.Wk2SJTG578gHmACO3O9y736vdoivCOgMtvsilwog7SluVwHus9NhZQLSS21wwb yzF4mqskf2Nt2UH27A9nFda_hZzy_V62f_I9Q6dyXEw5wpV5fU0quBm22pEFd9sA7hlBm_bWiYFa 8CdpRJGhoFDAmwY4YOZrtNwnZFuLaZC1Nj1xNc6LcErX1ODoqHGUiXGhS5o_hJ6MWJTvPcU80v9l KdOwdCA--
Received: from sonic.gate.mail.ne1.yahoo.com by sonic315.consmr.mail.gq1.yahoo.com with HTTP; Wed, 21 Jun 2017 16:47:31 +0000
Date: Wed, 21 Jun 2017 16:47:19 +0000 (UTC)
From: Nalini J Elkins <nalini.elkins@insidethestack.com>
Reply-To: Nalini J Elkins <nalini.elkins@insidethestack.com>
To: John C Klensin <john-ietf@jck.com>, "vmeet@ietf.org" <vmeet@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>
Message-ID: <344268538.4460995.1498063639755@mail.yahoo.com>
In-Reply-To: <51060E29D18DE784CEE290A0@PSB>
References: <1280323857.13113587.1497538214458.ref@mail.yahoo.com> <1280323857.13113587.1497538214458@mail.yahoo.com> <51060E29D18DE784CEE290A0@PSB>
Subject: Re: [vmeet] Remote Participation Hubs
MIME-Version: 1.0
Content-Type: multipart/alternative;  boundary="----=_Part_4460994_1188331952.1498063639752"
X-Mailer: WebService/1.1.9911 YahooMailNeo Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.86 Safari/537.36
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oH8yuMN0tp93WCO37mnv4CVJWnI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 16:47:34 -0000

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

John,

Thanks for your comments. =C2=A0Let me just say that we need to carefully c=
onsider and think out remote participation as a community. =C2=A0 Surprisin=
gly enough, I actually agree with many of your points. =C2=A0 I did this dr=
aft because this is a conversation that we need to have.
Today, I believe that we are ready for "Remote Viewing Hubs" (which is a dr=
aft that I will try to get posted by next week!)
IMO,=C2=A0ignoring the issues that come with "real" participation, many of =
whom you point out, we will do so at our peril. =C2=A0 We need to be thinki=
ng 3- 4 years out. =C2=A0And, planning for unforeseen disasters. =C2=A0Have=
 we so quickly forgotten the "travel ban" debacle? =C2=A0 Having said that,=
 I do not object at all to putting this work aside and concentrating on Rem=
ote Viewing Hubs. =C2=A0
But, on the back burner should not mean forgotten.
Is it so out of the question that in 2020, some region (say, India) may hav=
e 300 people who wish to participate in IETF WGs but cannot all do so in pe=
rson. =C2=A0 Why would we not have remote participation hubs in Bangalore, =
Kolkota, Mumbai? =C2=A0 =C2=A0We need to think and plan for that.
Nalini

--On Thursday, June 15, 2017 14:50 +0000
nalini.elkins@insidethestack.com wrote:


> All,
>=20
> We have submitted the first of three drafts discussing Remote
> Hubs.=C2=A0 Please provide comments on the VMEET list.
>=20
> Three types of remote hubs are defined.=C2=A0 Each has its own
> characteristics.
>=20
>=C2=A0 - Remote Participation Hubs
>=C2=A0 - Remote Viewing Hubs
>=C2=A0 - Enduring Local Meetups
>=20
> The first document defines a Remote Participation Hub (RPH).
> Other documents are coming to define the other types of hubs.
> A common structure of sections will be used as far as possible
> for all hub types.
>...

Nalini,

While I admire your energy and desire to more forward on all
fronts at once, I think the effort to get better and more
extensive remote participation would be best pursued by your
concentrating on Remote Viewing Hubs (and local discussions,
etc., as needed) and Local Meetings (no matter how enduring or
persistent) and letting Remote Participation Hubs go for a
while, perhaps returning to them after experience accumulates
and our knowledge and tools improve.

I have several reasons for that conclusion, some of which
overlap John Leslie's comments (which I will try to avoid
duplicating).=C2=A0 The note below hits just a few high points of
special concern to me before moving to the conclusion implied by
the previous paragraph.

>From one perspective, my problems start with an interesting
assertion in the Introduction to the I-D:=20

=C2=A0=C2=A0=C2=A0 "A Remote Participation Hub is functionally equivalent
=C2=A0=C2=A0=C2=A0 to an IETF face-to-face meeting."

"Functionally equivalent" implies the ability to attend informal
sessions like the Newcomper's Meet and Greet and to have
spontaneous discussions in the halls, over lunch, and at events
like Bits-and-Bytes with subsets of the community that are less
homogeneous than Remote Hubs will tend to be; to get an
introduction (if needed) and have informal conversations
(restaurants, halls, informal meeting spaces, coffee shops,
bars) with WG Chairs, ADs, document authors or editors, or
others; to grab an author at the end of a WG session (or have
the author grab you) to continue a discussion; and so on.=C2=A0 Even
though some of the text later in the document can be seen as
qualifying that very broad equivalence statement, at least at
the current state of the technology and our procedures claiming
a remote hub is "functionally equivalent" to our unified f2f
meetings (or even could be) falls into the "you must be kidding"
category.

Moreover, while we've done much better in some WGs and at some
meetings than others, we still haven't got good and predictable
queue management for questions and comments by individual remote
participants.=C2=A0 Meetecho has decent (and improving) facilities
for that, but we have a long way to go to sort out the human
factors of balancing multiple in-room queues, remote interactive
queues, jabber input, the effects of various kinds of delays
between a comment and a question about it, and so on in a way
that is fair to everyone.=C2=A0=20

If we have to combine the present situation and its challenges
with in-Hub-room queues, we have, AFAICT, two options ( think
the Meetecho team has reached much the same conclusion).=C2=A0 We can
put everyone in front of their own laptops, which forces the use
of headsets and complicates the bandwidth and other facility
issues (and makes some of your Section 4.6.3 inapplicable), or
we can set up in-room queues and a local queue manager or
moderator (perhaps the coordinator, perhaps not, but, if there
are parallel WGs being covered by the remote hub, we need at
least one each).=C2=A0 The latter raises more questions: how does a
WG Chair prioritize the third person in line in Hub#1 versus the
second person in line in Hub #2, versus in-room participants and
standalone remote participants?=C2=A0 Is the in-room queue manager
accountable to the WG Chair(s) or responsible ADs and how?=C2=A0=20

If there is disruption in the remote hub, even someone becoming
aggressive in the microphone line or trying to control it, is a
remote hub coordinator or other leader authorized to control
that (or harassment, which the draft mentions) in the name of
the IETF?=C2=A0 =C2=A0 Are their representatives of the ombudsteam present
and, if not, how is RFC 7776 interpreted and by whom?=C2=A0 What is
the accountability model there?=C2=A0 Are remote hub coordinators and
any necessary additional moderators covered by the same
insurance that, I believe, extends to WG Chairs even if the IESG
has no role in appointing them?

Is it reasonable and appropriate to put all of those decisions
under the control of whomever is participating in the remote
hob, or a sponsoring company, as your draft seems to suggest?
Does that provide adequate context and protection of the IETF
consensus process?

If a remote hub is open only to employee of the hosting
organization, do we continue to pretend that everyone
participating at the hub is participating as an individual?

And so on...

While I agree with John Leslie that the document is probably
overspecified in at least some places, none of the issues and
questions above are really addressed and there are probably many
more omissions.=C2=A0 Some imply a requirement for significant
training of WG Chairs and RPH coordinators (and perhaps
procedures (above and beyond "you don't get to do that again")
for how non-conforming behavior should be handled; others
involve at least a review and probably changes in important IETF
procedures.=C2=A0 =C2=A0 While I believe we can sort them out, I note,
first, that we still don't have the much more simple case of
individual remote participants working smoothly and that remote
participation hubs raise a collection of new issues, and that
bandwidth spent on these kinds of issues (at least for the IETF
participant majority who don't have too much time on their
hands) intrudes on getting technical work done and/or on other
procedural (especially remote participation) refinements.

Is the community really ready to review (and possibly reopen or
amend) RFCs 2026, 2418, 7282, 7776, and perhaps other documents
to identify situations in which people meeting as a group
without the usual accountability structures are in place could
turn into issues?

If for no reason than to reduce the risk of disrupting work to
improve existing forms of remote participation, I suggest it is
in the community's best interests to adopt something of a "one
step at a time" attitude and put this aside=20

Again, I'm strongly committed to remote participation.
Personally, I seem to be participating remotely more often than
I attend f2f meetings these days, which definitely motivates me.
But Remote Participation Hubs that are driven more by enthusiasm
than by careful understanding of issues and community consensus
about how to handle them just do not feel like a useful way
forward at this particular time.

best,
=C2=A0 =C2=A0 john
------=_Part_4460994_1188331952.1498063639752
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:Helvetica Neue, Helvetica, Arial, Lucida Grande, sans-serif;font=
-size:16px">John,<br><div id=3D"yui_3_16_0_ym19_1_1498062745627_8072"><br><=
/div><div id=3D"yui_3_16_0_ym19_1_1498062745627_6438">Thanks for your comme=
nts. &nbsp;Let me just say that we need to carefully consider and think out=
 remote participation as a community. &nbsp; Surprisingly enough, I actuall=
y agree with many of your points. &nbsp; I did this draft because this is a=
 conversation that we need to have.</div><div id=3D"yui_3_16_0_ym19_1_14980=
62745627_6438"><br></div><div id=3D"yui_3_16_0_ym19_1_1498062745627_6438">T=
oday, I believe that we are ready for "Remote Viewing Hubs" (which is a dra=
ft that I will try to get posted by next week!)</div><div id=3D"yui_3_16_0_=
ym19_1_1498062745627_6438"><br></div><div id=3D"yui_3_16_0_ym19_1_149806274=
5627_6438" dir=3D"ltr">IMO,&nbsp;<span style=3D"font-family: &quot;Helvetic=
a Neue&quot;, Helvetica, Arial, &quot;Lucida Grande&quot;, sans-serif; font=
-size: 16px;" id=3D"yui_3_16_0_ym19_1_1498062745627_12578">ignoring the iss=
ues that come with "real" participation, many of whom you point out, we wil=
l do so at our peril. &nbsp; We need to be thinking 3- 4 years out. &nbsp;A=
nd, planning for unforeseen disasters. &nbsp;Have we so quickly forgotten t=
he "travel ban" debacle? &nbsp; Having said that, I do not object at all to=
 putting this work aside and concentrating on Remote Viewing Hubs. &nbsp;</=
span></div><div id=3D"yui_3_16_0_ym19_1_1498062745627_6438" dir=3D"ltr"><sp=
an style=3D"font-family: &quot;Helvetica Neue&quot;, Helvetica, Arial, &quo=
t;Lucida Grande&quot;, sans-serif; font-size: 16px;"><br></span></div><div =
id=3D"yui_3_16_0_ym19_1_1498062745627_6438" dir=3D"ltr"><span style=3D"font=
-family: &quot;Helvetica Neue&quot;, Helvetica, Arial, &quot;Lucida Grande&=
quot;, sans-serif; font-size: 16px;">But, on the back burner should not mea=
n forgotten.</span></div><div id=3D"yui_3_16_0_ym19_1_1498062745627_6438"><=
span style=3D"font-family: &quot;Helvetica Neue&quot;, Helvetica, Arial, &q=
uot;Lucida Grande&quot;, sans-serif; font-size: 16px;"><br></span></div><di=
v id=3D"yui_3_16_0_ym19_1_1498062745627_6438" dir=3D"ltr"><span style=3D"fo=
nt-family: &quot;Helvetica Neue&quot;, Helvetica, Arial, &quot;Lucida Grand=
e&quot;, sans-serif; font-size: 16px;" id=3D"yui_3_16_0_ym19_1_149806274562=
7_12579">Is it so out of the question that in 2020, some region (say, India=
) may have 300 people who wish to participate in IETF WGs but cannot all do=
 so in person. &nbsp; Why would we not have remote participation hubs in Ba=
ngalore, Kolkota, Mumbai? &nbsp; &nbsp;We need to think and plan for that.<=
/span></div><div id=3D"yui_3_16_0_ym19_1_1498062745627_6438" dir=3D"ltr"><s=
pan style=3D"font-family: &quot;Helvetica Neue&quot;, Helvetica, Arial, &qu=
ot;Lucida Grande&quot;, sans-serif; font-size: 16px;"><br></span></div><div=
 id=3D"yui_3_16_0_ym19_1_1498062745627_6438" dir=3D"ltr"><span style=3D"fon=
t-family: &quot;Helvetica Neue&quot;, Helvetica, Arial, &quot;Lucida Grande=
&quot;, sans-serif; font-size: 16px;">Nalini</span></div><div id=3D"yui_3_1=
6_0_ym19_1_1498062745627_12614"><br></div><div id=3D"yui_3_16_0_ym19_1_1498=
062745627_12615"><br></div>--On Thursday, June 15, 2017 14:50 +0000<br>nali=
ni.elkins@insidethestack.com wrote:<br><br><br>&gt; All,<br>&gt; <br>&gt; W=
e have submitted the first of three drafts discussing Remote<br>&gt; Hubs.&=
nbsp;  Please provide comments on the VMEET list.<br>&gt; <br>&gt; Three ty=
pes of remote hubs are defined.&nbsp; Each has its own<br>&gt; characterist=
ics.<br>&gt; <br>&gt;&nbsp;  - Remote Participation Hubs<br>&gt;&nbsp;  - R=
emote Viewing Hubs<br>&gt;&nbsp;  - Enduring Local Meetups<br>&gt; <br>&gt;=
 The first document defines a Remote Participation Hub (RPH).<br>&gt; Other=
 documents are coming to define the other types of hubs.<br>&gt; A common s=
tructure of sections will be used as far as possible<br>&gt; for all hub ty=
pes.<br>&gt;...<br><br>Nalini,<br><br>While I admire your energy and desire=
 to more forward on all<br>fronts at once, I think the effort to get better=
 and more<br>extensive remote participation would be best pursued by your<b=
r>concentrating on Remote Viewing Hubs (and local discussions,<br>etc., as =
needed) and Local Meetings (no matter how enduring or<br>persistent) and le=
tting Remote Participation Hubs go for a<br>while, perhaps returning to the=
m after experience accumulates<br>and our knowledge and tools improve.<br><=
br>I have several reasons for that conclusion, some of which<br>overlap Joh=
n Leslie's comments (which I will try to avoid<br>duplicating).&nbsp;  The =
note below hits just a few high points of<br>special concern to me before m=
oving to the conclusion implied by<br>the previous paragraph.<br><br>&gt;Fr=
om one perspective, my problems start with an interesting<br>assertion in t=
he Introduction to the I-D: <br><br>&nbsp;&nbsp;&nbsp; "A Remote Participat=
ion Hub is functionally equivalent<br>&nbsp;&nbsp;&nbsp; to an IETF face-to=
-face meeting."<br><br>"Functionally equivalent" implies the ability to att=
end informal<br>sessions like the Newcomper's Meet and Greet and to have<br=
>spontaneous discussions in the halls, over lunch, and at events<br>like Bi=
ts-and-Bytes with subsets of the community that are less<br>homogeneous tha=
n Remote Hubs will tend to be; to get an<br>introduction (if needed) and ha=
ve informal conversations<br>(restaurants, halls, informal meeting spaces, =
coffee shops,<br>bars) with WG Chairs, ADs, document authors or editors, or=
<br>others; to grab an author at the end of a WG session (or have<br>the au=
thor grab you) to continue a discussion; and so on.&nbsp; Even<br>though so=
me of the text later in the document can be seen as<br>qualifying that very=
 broad equivalence statement, at least at<br>the current state of the techn=
ology and our procedures claiming<br>a remote hub is "functionally equivale=
nt" to our unified f2f<br>meetings (or even could be) falls into the "you m=
ust be kidding"<br>category.<br><br>Moreover, while we've done much better =
in some WGs and at some<br>meetings than others, we still haven't got good =
and predictable<br>queue management for questions and comments by individua=
l remote<br>participants.&nbsp; Meetecho has decent (and improving) facilit=
ies<br>for that, but we have a long way to go to sort out the human<br>fact=
ors of balancing multiple in-room queues, remote interactive<br>queues, jab=
ber input, the effects of various kinds of delays<br>between a comment and =
a question about it, and so on in a way<br>that is fair to everyone.&nbsp; =
<br><br>If we have to combine the present situation and its challenges<br>w=
ith in-Hub-room queues, we have, AFAICT, two options ( think<br>the Meetech=
o team has reached much the same conclusion).&nbsp; We can<br>put everyone =
in front of their own laptops, which forces the use<br>of headsets and comp=
licates the bandwidth and other facility<br>issues (and makes some of your =
Section 4.6.3 inapplicable), or<br>we can set up in-room queues and a local=
 queue manager or<br>moderator (perhaps the coordinator, perhaps not, but, =
if there<br>are parallel WGs being covered by the remote hub, we need at<br=
>least one each).&nbsp;  The latter raises more questions: how does a<br>WG=
 Chair prioritize the third person in line in Hub#1 versus the<br>second pe=
rson in line in Hub #2, versus in-room participants and<br>standalone remot=
e participants?&nbsp; Is the in-room queue manager<br>accountable to the WG=
 Chair(s) or responsible ADs and how?&nbsp; <br><br>If there is disruption =
in the remote hub, even someone becoming<br>aggressive in the microphone li=
ne or trying to control it, is a<br>remote hub coordinator or other leader =
authorized to control<br>that (or harassment, which the draft mentions) in =
the name of<br>the IETF?&nbsp; &nbsp; Are their representatives of the ombu=
dsteam present<br>and, if not, how is RFC 7776 interpreted and by whom?&nbs=
p; What is<br>the accountability model there?&nbsp; Are remote hub coordina=
tors and<br>any necessary additional moderators covered by the same<br>insu=
rance that, I believe, extends to WG Chairs even if the IESG<br>has no role=
 in appointing them?<br><br>Is it reasonable and appropriate to put all of =
those decisions<br>under the control of whomever is participating in the re=
mote<br>hob, or a sponsoring company, as your draft seems to suggest?<br>Do=
es that provide adequate context and protection of the IETF<br>consensus pr=
ocess?<br><br>If a remote hub is open only to employee of the hosting<br>or=
ganization, do we continue to pretend that everyone<br>participating at the=
 hub is participating as an individual?<br><br>And so on...<br><br>While I =
agree with John Leslie that the document is probably<br>overspecified in at=
 least some places, none of the issues and<br>questions above are really ad=
dressed and there are probably many<br>more omissions.&nbsp; Some imply a r=
equirement for significant<br>training of WG Chairs and RPH coordinators (a=
nd perhaps<br>procedures (above and beyond "you don't get to do that again"=
)<br>for how non-conforming behavior should be handled; others<br>involve a=
t least a review and probably changes in important IETF<br>procedures.&nbsp=
; &nbsp; While I believe we can sort them out, I note,<br>first, that we st=
ill don't have the much more simple case of<br>individual remote participan=
ts working smoothly and that remote<br>participation hubs raise a collectio=
n of new issues, and that<br>bandwidth spent on these kinds of issues (at l=
east for the IETF<br>participant majority who don't have too much time on t=
heir<br>hands) intrudes on getting technical work done and/or on other<br>p=
rocedural (especially remote participation) refinements.<br><br>Is the comm=
unity really ready to review (and possibly reopen or<br>amend) RFCs 2026, 2=
418, 7282, 7776, and perhaps other documents<br>to identify situations in w=
hich people meeting as a group<br>without the usual accountability structur=
es are in place could<br>turn into issues?<br><br>If for no reason than to =
reduce the risk of disrupting work to<br>improve existing forms of remote p=
articipation, I suggest it is<br>in the community's best interests to adopt=
 something of a "one<br>step at a time" attitude and put this aside <br><br=
>Again, I'm strongly committed to remote participation.<br>Personally, I se=
em to be participating remotely more often than<br>I attend f2f meetings th=
ese days, which definitely motivates me.<br>But Remote Participation Hubs t=
hat are driven more by enthusiasm<br>than by careful understanding of issue=
s and community consensus<br>about how to handle them just do not feel like=
 a useful way<br>forward at this particular time.<br><br>best,<br>&nbsp; &n=
bsp; john</div></body></html>
------=_Part_4460994_1188331952.1498063639752--


From nobody Wed Jun 21 09:48:55 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 85E2D12EC00; Wed, 21 Jun 2017 09:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=cooperw.in header.b=vTe2TaGn; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=OlJlA7Xd
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qwmMmJAREUJk; Wed, 21 Jun 2017 09:48:49 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DECC012EBCD; Wed, 21 Jun 2017 09:48:46 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 33FA820C95; Wed, 21 Jun 2017 12:48:46 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 21 Jun 2017 12:48:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :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=Z5Ou/fe3Xcme7EuzGObKmjbChPadzP84E+mvw9Z+Y 5o=; b=vTe2TaGnfshaOd8n0jq8chvCxRUrPjMsQuzEDvD1/MFja+0fXalM1/tgZ G8zLEmjziHNVSUl/pQzkX2shvcZBP6KyJRyeYqGe4iKy2ttWpgNyN1/a37JseVkb fWoyd1vunHc9V1uzeAL0iCjlJA9e17Dwdbxvxza/b8E7caZajLAmnHzT3Ft6ARRM ID3+GxFGO01jT7YFUrMCctvM2DFLZrXeXfAi4Je5HgAJP3CYWLf5iVsjfvGSlK7F A4mxZcBnfwosqvYdW2p6k0tewaqT4UVsSis+Wi1uIxqolKBn5CA+DY5EDqtfH1l5 u36eG+yJmCrvL8/yxXg8ktrHsFpow==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=Z5Ou/fe3Xcme7EuzGO bKmjbChPadzP84E+mvw9Z+Y5o=; b=OlJlA7Xd+hbUV/itGXx0pszdqPeR+OC3by lGw1kF2/LdBDRr2nmGl8/cQDZngMPokvRYaBmibsuE1pUxJnIRQwvSHSjsa7C2nf fAxTjcH42J3cszFSd9BAOFYWRaPvBEQp+9lKqzRqu1MFt1ixf7eapuum1agQCago WINnFQ1YiLhOIC162/CLQVjRexywD1O1eN9RE1By94EQtgXIMrLbtIve9GTmDkZS ef/7VL9bUa2jdw85MJsTc9Dgz8wfyIRlW230hP2VshtJ2c42VNb8dRBilQXhapJJ KDxuhZyP1PAk7CqO3tq3n/M2LQSCditfpTkjH1eA+rGZ7jTXXm9w==
X-ME-Sender: <xms:bqNKWRM62QLV1EEvrzTxd-wcgTz2b1AKzoiK4JUqvjaDxUwPCX_s9g>
X-Sasl-enc: g80yF0khpRd9o1W7AeoYjslAqKc4MPrMpxHaAHFQZb/T 1498063725
Received: from sjc-alcoop-8812.cisco.com (unknown [128.107.241.165]) by mail.messagingengine.com (Postfix) with ESMTPA id 5B6027E72B; Wed, 21 Jun 2017 12:48:44 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_AFC8A1E5-5097-4FF6-8B0E-5E79144E9572"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
Subject: Re: [Gen-art] Genart last call review of draft-ietf-bmwg-dcbench-terminology-10
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CALTEt=DWK5n8xVJ_ZD3j5BZmBT=_id1ZERCHPY3SGEqYL6N8sg@mail.gmail.com>
Date: Wed, 21 Jun 2017 12:48:42 -0400
Cc: Matthew Miller <linuxwolf+ietf@outer-planes.net>, gen-art <gen-art@ietf.org>, ietf <ietf@ietf.org>, bmwg@ietf.org, draft-ietf-bmwg-dcbench-terminology.all@ietf.org
Message-Id: <4776794B-BB06-451C-8B6D-A58051638306@cooperw.in>
References: <149741280522.7481.5692213354540706614@ietfa.amsl.com> <CALTEt=DWK5n8xVJ_ZD3j5BZmBT=_id1ZERCHPY3SGEqYL6N8sg@mail.gmail.com>
To: Lucien Avramov <lucienav@google.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_jrgZSRGNB3voOiZtdaueI70Gos>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 16:48:54 -0000

--Apple-Mail=_AFC8A1E5-5097-4FF6-8B0E-5E79144E9572
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Mtt, thanks for your review. Lucien, than you for your responses. I have =
entered a No Objection ballot position on this document.

Alissa


> On Jun 16, 2017, at 1:09 AM, Lucien Avramov <lucienav@google.com> =
wrote:
>=20
> Hi Matthew!
>=20
> Thank you for the review!
> We incorporated your feedback and now it's in -12: of the draft =
<https://datatracker.ietf.org/doc/draft-ietf-bmwg-dcbench-terminology/>
>=20
> Please see inline more details to each of your feedback.
>=20
> Thank you for such a detailed write up.
>=20
> Best,
> Lucien
>=20
>=20
>=20
>>=20
>> Subject: Genart last call review of =
draft-ietf-bmwg-dcbench-terminology-10
>>=20
>> Reviewer: Matthew Miller
>> Review result: Almost Ready
>>=20
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair.  Please treat these comments just
>> like any other last call comments.
>>=20
>> For more information, please see the FAQ at
>>=20
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq =
<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>>.
>>=20
>> Document: draft-ietf-bmwg-dcbench-terminology-10
>> Reviewer: Matthew A. Miller
>> Review Date: 2017-06-13
>> IETF LC End Date: 2017-06-13
>> IESG Telechat date: N/A
>>=20
>> Summary:
>>=20
>> This document is almost ready; this document is on the path to its
>> goals set out in the abstract and introduction, but the execution
>> needs more work.
>>=20
>> I think the authors would benefit from another round of proofreading
>> and submit a new revision.  Below are the most obvious or egregious
>> issues I have.
>>=20
>> Major issues:
>>=20
>> * In section 6.2 "Incast", it is unclear what is being measured,
>> and what the units (if any) for that measurement are.  Is it the
>> percentage of synchronization?  Is it the synchronous arrival time
>> (which presumably is measured as a delta over some magnitude of
>> seconds)? Is it the number of ingress and egress ports?  If it is
>> the number of ingress and egress ports, then it should define what
>> "egress" means for the purpose of this measurement
>=20
>=20
> fixed!=20
>>=20
>>=20
>> * In Section 8. "Security Considerations", what is the reason for
>> the "SHOULD" and "SHOULD NOT" in the last paragraph (discussing
>> special capabilities)?  At the least it seems safest for the
>> exceptions that rationalize the "SHOULD" and "SHOULD NOT" be
>> explicitly stated here, or changed to "MUST" and "MUST NOT" if
>> that rationale cannot be stated.
>=20
>=20
> These are the standard security considerations all BMWG uses for the =
drafts. We want to stay with the considerations we chose.  =20
>>=20
>>=20
>> Minor issues:
>>=20
>> * RFC 2119 should be a normative reference, as the reader MUST
>> understand what the terms as-written mean.
>=20
> done
> =20
>>=20
>>=20
>> * RFC 5841 needs to be a listed reference; It is explicitly pointed
>> to in Sections 3.1. and 3.2. =46rom the text is seems a Normative
>> reference is warranted but it at least needs to be documented in
>> References.
>=20
> done=20
>>=20
>>=20
>> * RFC 2647 needs to be a listed reference. It is explicitly pointed
>> to in Section 7.1.; from the text it seems appropriate to be an
>> Informative reference.
>=20
> done=20
>>=20
>>=20
>> * The definition in Section 1.2. of what the "Measurement Units"
>> subsections definitions format doesn't seem to be followed in
>> this document.  Specifically, the "Measurement Units" subsections
>> rarely ever mention a unit of measure; instead the unit of measure
>> is almost always specified as part of the "Definition" subsection.
>> It may be worth revisiting the name for the "Measurement Units"
>> subsections, or to move the unit of measure out of the
>> "Definitions" subsections and into the "Measurement Units"
>> subsections.
>=20
> Section 1.2 has the purpose to explain how the document is formatted.=20=

> it has 3 subsections each time moving forward as described in 1.2. We =
use that third subsection in this document to explain how to measure the =
topic discussed.=20
>=20
> Definition: The specific definition for the term.
> Discussion: A brief discussion about the term, its application
> Measurement Units
>>=20
>>=20
>> * In section 2.3., the use of MUST, MAY, and MUST NOT seems
>> a little contradictory.  The MUST for point 1 would seem to
>> already negate point 3, and prohibit point 2.  Would changing
>> that MUST to SHOULD be acceptable?
>=20
> We wanted to keep MUST , MAY and MUST NOT to explain that : 1) is the =
way to go ALWAYS. 2) can be done but it very specific to particular =
corner use case. 3) should never be done, although 1) negates 3), we =
want to call out 3, because people often time do 1) and don't follow 3. =
(they would do a LIFO test although they must not do it).=20
>=20
> =20
>=20
> These are the standard security considerations all BMWG uses for the =
drafts. We want to stay with the considerations we chose. =20
>>=20
>>=20
>> Nits/editorial comments:
>>=20
>> * It would be helpful to include a reference to what "north-south"
>> and "east-west" mean, if possible.
>=20
> done!=20
>>=20
>>=20
>> * the acronyms DUT and SUT -- at the least -- need to be
>> expanded on first use, or in Section 1.1. "Terminology".
>=20
>=20
> done!=20
>>=20
>>=20
>> * In a number of subsections (notably under Section 4. and Section
>> 6.), square brackets ("[" and "]") are used instead of parentheses
>> ("(" and ")"), without any clear reason for the difference.  They
>> should be switched to parentheses.
>=20
> done!=20
>>=20
>>=20
>> * In Section 2.2., the word "for" or "at" should be removed in the
>> sentence "The change of behavior happens for at specific larger
>> packet sizes."
>=20
> done!=20
>>=20
>>=20
>> * Section 2.3., the phrase "the application commonly need to" should
>> be changed to "the application commonly needs to".
>>=20
>=20
> done!=20
>> * In Section 5.2., there is a comma missing between "crystals" and
>> "or" in "The crystals or clock modules, usually have a specific".
>=20
> done!=20
>>=20
>>=20
>> * Also in Section 5.2., the term "devices under test" is used
>> instead of DUTs the rest of the document seems to use.
>=20
> done!=20
>>=20
>>=20
>> * Throughout Section 6.1., the acronyms "cos" and "dcsp" should be
>> expanded on first use.
>=20
> done!=20
>>=20
>>=20
>> * In Section 6.1.1, the definition of "Buffer Size" calls out using
>> some magnitude of bytes (B, KB, MB, GB), then the example denotes
>> "Mb" -- which commonly is used for megabits.  =46rom the rest of the
>> definition, it seems this should be MB, but I have not calculated
>> if the numerical value preceding the unit needs to be revisited.
>=20
> done!=20
>>=20
>>=20
>> * In Section 6.2.1, the Stateful and Stateless terms both use the
>> phrase "such as for example", which is redundant.  Either "such as"
>> or "for example" is sufficient, and the other should be removed.
>>=20
>> * The formatting in Section 10. "References" is very inconsistent.
>> There is odd indentation and inconsistent anchor usage.
>=20
>=20
> fixed as much as i could, there is a problem with nits in submission =
tool when =20
>>=20
>>=20
>> * The affiliation and email address for Lucien Avramov is Google,
>> but the street address is mostly that for Cisco Systems, Inc.
>=20
> done=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


--Apple-Mail=_AFC8A1E5-5097-4FF6-8B0E-5E79144E9572
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""><div class=3D"">Mtt, thanks for your review. Lucien, than you =
for your responses. I have entered a No Objection ballot position on =
this document.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Alissa</div><div class=3D""><br class=3D""></div><br =
class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On =
Jun 16, 2017, at 1:09 AM, Lucien Avramov &lt;<a =
href=3D"mailto:lucienav@google.com" class=3D"">lucienav@google.com</a>&gt;=
 wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
dir=3D"ltr" class=3D"">Hi Matthew!<div class=3D""><br =
class=3D""></div><div class=3D"">Thank you for the review!</div><div =
class=3D"">We incorporated your feedback and now it's in -12: of the <a =
href=3D"https://datatracker.ietf.org/doc/draft-ietf-bmwg-dcbench-terminolo=
gy/" class=3D"">draft</a></div><div class=3D""><br class=3D""></div><div =
class=3D"">Please see inline more details to each of your =
feedback.</div><div class=3D""><br class=3D""></div><div class=3D"">Thank =
you for such a detailed write up.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Best,</div><div =
class=3D"">Lucien</div><div class=3D""><br class=3D""></div><div =
class=3D""><br class=3D""><div class=3D"gmail_extra"><br class=3D""><div =
class=3D"gmail_quote"><div style=3D"min-height:100%" class=3D""><div =
class=3D"gmail-nH" style=3D"width:1188px"><div class=3D"gmail-nH" =
style=3D""><div class=3D"gmail-nH gmail-bkL"><div class=3D"gmail-no"><div =
class=3D"gmail-nH gmail-bkK gmail-nn" style=3D"width:986px"><div =
class=3D"gmail-nH"><div class=3D"gmail-nH"><div class=3D"gmail-nH =
gmail-ar4 gmail-z"><div class=3D"gmail-aeI"><div class=3D"gmail-AO"><div =
id=3D"gmail-:4" class=3D"gmail-Tm gmail-aeJ" style=3D"height:551px"><div =
id=3D"gmail-:2" class=3D"gmail-aeF" style=3D"min-height:121px"><div =
class=3D"gmail-nH"><div class=3D"gmail-nH"><div class=3D"gmail-nH =
gmail-g"><table class=3D"gmail-Bs gmail-nH gmail-iY" cellpadding=3D"0" =
style=3D"width:956px"><tbody class=3D""><tr class=3D""><td =
class=3D"gmail-Bu"><div class=3D"gmail-nH gmail-if"><div class=3D"gmail-nH=
 gmail-aHU"><div class=3D"gmail-nH gmail-hx"><div class=3D"gmail-nH"><div =
class=3D"gmail-hn gmail-ie gmail-nH gmail-oy8Mbf gmail-h7" =
tabindex=3D"-1"><div class=3D"gmail-Bk" style=3D"width:705px"><div =
class=3D"gmail-G3 gmail-G2 gmail-afm"><div id=3D"gmail-:1ph" =
class=3D""><div class=3D"gmail-adn gmail-ads"><div class=3D"gmail-gs"><div=
 id=3D"gmail-:1qg" class=3D"gmail-gt gmail-ii gmail-adO" =
style=3D"font-size:12.8px"><div id=3D"gmail-:1z2" class=3D"gmail-a3s =
gmail-aXjCH gmail-m15caf4bc03a5f652"><div dir=3D"ltr" class=3D""><div =
class=3D"gmail_extra"><div class=3D"gmail_quote"><div =
class=3D"gmail-adM"><div class=3D"gmail-im"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" =
class=3D""><blockquote type=3D"cite" style=3D"font-size:12.8px" =
class=3D""><br class=3D""><b class=3D"">Subject:</b>&nbsp;<b =
class=3D"">Genart last call review of draft-ietf-bmwg-dcbench-termin<wbr =
class=3D"">ology-10</b><br class=3D""><br class=3D""></blockquote><div =
style=3D"font-size:12.8px" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D"">Reviewer: Matthew Miller<br =
class=3D"">Review result: Almost Ready<br class=3D""><br class=3D"">I am =
the assigned Gen-ART reviewer for this draft. The General Area<br =
class=3D"">Review Team (Gen-ART) reviews all IETF documents being =
processed<br class=3D"">by the IESG for the IETF Chair.&nbsp; Please =
treat these comments just<br class=3D"">like any other last call =
comments.<br class=3D""><br class=3D"">For more information, please see =
the FAQ at<br class=3D""><br class=3D"">&lt;<a =
href=3D"https://trac.ietf.org/trac/gen/wiki/GenArtfaq" target=3D"_blank" =
class=3D"">https://trac.ietf.org/trac/ge<wbr =
class=3D"">n/wiki/GenArtfaq</a>&gt;.<br class=3D""><br =
class=3D"">Document: draft-ietf-bmwg-dcbench-termin<wbr =
class=3D"">ology-10<br class=3D"">Reviewer: Matthew A. Miller<br =
class=3D"">Review Date: 2017-06-13<br class=3D"">IETF LC End Date: =
2017-06-13<br class=3D"">IESG Telechat date: N/A<br class=3D""><br =
class=3D"">Summary:<br class=3D""><br class=3D"">This document is almost =
ready; this document is on the path to its<br class=3D"">goals set out =
in the abstract and introduction, but the execution<br class=3D"">needs =
more work.<br class=3D""><br class=3D"">I think the authors would =
benefit from another round of proofreading<br class=3D"">and submit a =
new revision.&nbsp; Below are the most obvious or egregious<br =
class=3D"">issues I have.<br class=3D""><br class=3D"">Major issues:<br =
class=3D""><br class=3D"">* In section 6.2 "Incast", it is unclear what =
is being measured,<br class=3D"">and what the units (if any) for that =
measurement are.&nbsp; Is it the<br class=3D"">percentage of =
synchronization?&nbsp; Is it the synchronous arrival time<br =
class=3D"">(which presumably is measured as a delta over some magnitude =
of<br class=3D"">seconds)? Is it the number of ingress and egress =
ports?&nbsp; If it is<br class=3D"">the number of ingress and egress =
ports, then it should define what<br class=3D"">"egress" means for the =
purpose of this =
measurement</blockquote></div></div></div></div></div></div></div></blockq=
uote><div class=3D""><br class=3D""></div></div></div><div =
class=3D"">fixed!&nbsp;</div><span class=3D"gmail-im"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* In Section =
8. "Security Considerations", what is the reason for<br class=3D"">the =
"SHOULD" and "SHOULD NOT" in the last paragraph (discussing<br =
class=3D"">special capabilities)?&nbsp; At the least it seems safest for =
the<br class=3D"">exceptions that rationalize the "SHOULD" and "SHOULD =
NOT" be<br class=3D"">explicitly stated here, or changed to "MUST" and =
"MUST NOT" if<br class=3D"">that rationale cannot be =
stated.</blockquote></div></div></div></div></div></div></blockquote><div =
class=3D""><br class=3D""></div></span><div class=3D"">These are the =
standard security considerations all BMWG uses for the drafts. We want =
to stay with the considerations we chose. &nbsp;&nbsp;</div><span =
class=3D"gmail-im"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">Minor =
issues:<br class=3D""><br class=3D"">* RFC 2119 should be a normative =
reference, as the reader MUST<br class=3D"">understand what the terms =
as-written =
mean.</blockquote></div></div></div></div></div></div></blockquote></span>=
<div class=3D"">done</div><span class=3D"gmail-im"><div =
class=3D"">&nbsp;</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* RFC 5841 =
needs to be a listed reference; It is explicitly pointed<br class=3D"">to =
in Sections 3.1. and 3.2. =46rom the text is seems a Normative<br =
class=3D"">reference is warranted but it at least needs to be documented =
in<br =
class=3D"">References.</blockquote></div></div></div></div></div></div></b=
lockquote></span><div class=3D"">done&nbsp;</div><span =
class=3D"gmail-im"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* RFC 2647 =
needs to be a listed reference. It is explicitly pointed<br class=3D"">to =
in Section 7.1.; from the text it seems appropriate to be an<br =
class=3D"">Informative =
reference.</blockquote></div></div></div></div></div></div></blockquote></=
span><div class=3D"">done&nbsp;</div><span class=3D"gmail-im"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* The =
definition in Section 1.2. of what the "Measurement Units"<br =
class=3D"">subsections definitions format doesn't seem to be followed =
in<br class=3D"">this document.&nbsp; Specifically, the "Measurement =
Units" subsections<br class=3D"">rarely ever mention a unit of measure; =
instead the unit of measure<br class=3D"">is almost always specified as =
part of the "Definition" subsection.<br class=3D"">It may be worth =
revisiting the name for the "Measurement Units"<br class=3D"">subsections,=
 or to move the unit of measure out of the<br class=3D"">"Definitions" =
subsections and into the "Measurement Units"<br =
class=3D"">subsections.</blockquote></div></div></div></div></div></div></=
blockquote></span><div class=3D"">Section 1.2 has the purpose to explain =
how the document is formatted.&nbsp;</div><div class=3D"">it has 3 =
subsections each time moving forward as described in 1.2. We use that =
third subsection in this document to explain how to measure the topic =
discussed.&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D""><div class=3D""><ul class=3D""><li class=3D"">Definition: The =
specific definition for the term.</li></ul></div><div class=3D""><ul =
class=3D""><li class=3D"">Discussion: A brief discussion about the term, =
its application</li></ul></div><div class=3D""><ul class=3D""><li =
class=3D"">Measurement Units<br class=3D""></li></ul></div></div><span =
class=3D"gmail-im"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* In section =
2.3., the use of MUST, MAY, and MUST NOT seems<br class=3D"">a little =
contradictory.&nbsp; The MUST for point 1 would seem to<br =
class=3D"">already negate point 3, and prohibit point 2.&nbsp; Would =
changing<br class=3D"">that MUST to SHOULD be =
acceptable?</blockquote></div></div></div></div></div></div></blockquote><=
/span><div class=3D"">We wanted to keep MUST , MAY and MUST NOT to =
explain that : 1) is the way to go ALWAYS. 2) can be done but it very =
specific to particular corner use case. 3) should never be done, =
although 1) negates 3), we want to call out 3, because people often time =
do 1) and don't follow 3. (they would do a LIFO test although they must =
not do it).&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">&nbsp;</div><div class=3D""><br class=3D""></div><div =
class=3D"">These are the standard security considerations all BMWG uses =
for the drafts. We want to stay with the considerations we chose. =
&nbsp;</div><span class=3D"gmail-im"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">Nits/editorial=
 comments:<br class=3D""><br class=3D"">* It would be helpful to include =
a reference to what "north-south"<br class=3D"">and "east-west" mean, if =
possible.</blockquote></div></div></div></div></div></div></blockquote></s=
pan><div class=3D"">done!&nbsp;</div><span class=3D"gmail-im"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* the =
acronyms DUT and SUT -- at the least -- need to be<br class=3D"">expanded =
on first use, or in Section 1.1. =
"Terminology".</blockquote></div></div></div></div></div></div></blockquot=
e><div class=3D""><br class=3D""></div></span><div =
class=3D"">done!&nbsp;</div><span class=3D"gmail-im"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* In a =
number of subsections (notably under Section 4. and Section<br =
class=3D"">6.), square brackets ("[" and "]") are used instead of =
parentheses<br class=3D"">("(" and ")"), without any clear reason for =
the difference.&nbsp; They<br class=3D"">should be switched to =
parentheses.</blockquote></div></div></div></div></div></div></blockquote>=
</span><div class=3D"">done!&nbsp;</div><span =
class=3D"gmail-im"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* In Section =
2.2., the word "for" or "at" should be removed in the<br =
class=3D"">sentence "The change of behavior happens for at specific =
larger<br class=3D"">packet =
sizes."</blockquote></div></div></div></div></div></div></blockquote></spa=
n><div class=3D"">done!&nbsp;</div><span class=3D"gmail-im"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* Section =
2.3., the phrase "the application commonly need to" should<br =
class=3D"">be changed to "the application commonly needs to".<br =
class=3D""><br =
class=3D""></blockquote></div></div></div></div></div></div></blockquote><=
/span><div class=3D"">done!&nbsp;</div><span =
class=3D"gmail-im"><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D"">* In Section 5.2., there is a comma =
missing between "crystals" and<br class=3D"">"or" in "The crystals or =
clock modules, usually have a =
specific".</blockquote></div></div></div></div></div></div></blockquote></=
span><div class=3D"">done!&nbsp;</div><span class=3D"gmail-im"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* Also in =
Section 5.2., the term "devices under test" is used<br class=3D"">instead =
of DUTs the rest of the document seems to =
use.</blockquote></div></div></div></div></div></div></blockquote></span><=
div class=3D"">done!&nbsp;</div><span class=3D"gmail-im"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* Throughout =
Section 6.1., the acronyms "cos" and "dcsp" should be<br =
class=3D"">expanded on first =
use.</blockquote></div></div></div></div></div></div></blockquote></span><=
div class=3D"">done!&nbsp;</div><span class=3D"gmail-im"><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* In Section =
6.1.1, the definition of "Buffer Size" calls out using<br class=3D"">some =
magnitude of bytes (B, KB, MB, GB), then the example denotes<br =
class=3D"">"Mb" -- which commonly is used for megabits.&nbsp; =46rom the =
rest of the<br class=3D"">definition, it seems this should be MB, but I =
have not calculated<br class=3D"">if the numerical value preceding the =
unit needs to be =
revisited.</blockquote></div></div></div></div></div></div></blockquote></=
span><div class=3D"">done!&nbsp;</div><span class=3D"gmail-im"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* In Section =
6.2.1, the Stateful and Stateless terms both use the<br class=3D"">phrase =
"such as for example", which is redundant.&nbsp; Either "such as"<br =
class=3D"">or "for example" is sufficient, and the other should be =
removed.<br class=3D""><br class=3D"">* The formatting in Section 10. =
"References" is very inconsistent.<br class=3D"">There is odd =
indentation and inconsistent anchor =
usage.</blockquote></div></div></div></div></div></div></blockquote><div =
class=3D""><br class=3D""></div></span><div class=3D"">fixed as much as =
i could, there is a problem with nits in submission tool when =
&nbsp;</div><span class=3D"gmail-im"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex"><div =
class=3D"gmail-m_-566981276781100764gmail-HOEnZb"><div =
class=3D"gmail-m_-566981276781100764gmail-h5"><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_quote"><div dir=3D"auto" class=3D""><div =
class=3D"gmail-m_-566981276781100764gmail-m_8608744719394608261h5"><blockq=
uote type=3D"cite" class=3D""><br class=3D""><br class=3D"">* The =
affiliation and email address for Lucien Avramov is Google,<br =
class=3D"">but the street address is mostly that for Cisco Systems, =
Inc.</blockquote></div></div></div></div></div></div></blockquote></span><=
div =
class=3D"">done&nbsp;</div></div></div></div></div></div></div></div></div=
></div></div></div></div></div></div></div></td></tr></tbody></table></div=
></div></div></div></div></div></div></div></div></div></div></div></div><=
/div></div></div></div></div></div></div>
_______________________________________________<br class=3D"">Gen-art =
mailing list<br class=3D""><a href=3D"mailto:Gen-art@ietf.org" =
class=3D"">Gen-art@ietf.org</a><br =
class=3D"">https://www.ietf.org/mailman/listinfo/gen-art<br =
class=3D""></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_AFC8A1E5-5097-4FF6-8B0E-5E79144E9572--


From nobody Wed Jun 21 10:18:02 2017
Return-Path: <lee@asgard.org>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2D481201FA for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 10:18:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_SORBS_SPAM=0.5, 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 UX_BXkGU6W-9 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 10:17:59 -0700 (PDT)
Received: from atl4mhob11.registeredsite.com (atl4mhob11.registeredsite.com [209.17.115.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 5F004128BBB for <ietf@ietf.org>; Wed, 21 Jun 2017 10:17:53 -0700 (PDT)
Received: from mailpod.hostingplatform.com ([10.30.71.204]) by atl4mhob11.registeredsite.com (8.14.4/8.14.4) with ESMTP id v5LHHpn0009315 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf@ietf.org>; Wed, 21 Jun 2017 13:17:51 -0400
Received: (qmail 6454 invoked by uid 0); 21 Jun 2017 17:17:51 -0000
X-TCPREMOTEIP: 68.100.68.25
X-Authenticated-UID: lee@asgard.org
Received: from unknown (HELO ?192.168.1.160?) (lee@asgard.org@68.100.68.25) by 0 with ESMTPA; 21 Jun 2017 17:17:50 -0000
User-Agent: Microsoft-MacOutlook/14.7.2.170228
Date: Wed, 21 Jun 2017 13:17:45 -0400
Subject: Re: Saturday as start day
From: Lee Howard <lee@asgard.org>
To: Christian Huitema <huitema@huitema.net>, <ietf@ietf.org>
Message-ID: <D57020DB.7D730%lee@asgard.org>
Thread-Topic: Saturday as start day
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net>
In-Reply-To: <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qPEuM-4bOM0jy89zhT8NRDeSvrs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 17:18:01 -0000

On 6/21/17, 9:53 AM, "ietf on behalf of Christian Huitema"
<ietf-bounces@ietf.org on behalf of huitema@huitema.net> wrote:

>On 6/21/2017 5:46 AM, Bob Hinden wrote:
>
>> Alissa,
>>
>>> On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>>>
>>> Hi all,
>>>
>>> Based on a suggestion from Paul Hoffman, the IESG believes it would be
>>>beneficial to denote the official start of IETF meetings to be on
>>>Saturday rather than Sunday, starting with IETF 100. We believe this
>>>would be sensible given that events such as the hackathon and code
>>>sprint start on Saturday, and may make it easier for some participants
>>>to get travel approval to attend those events. This change would be
>>>reflected in the dates posted on the IETF web site and sent out in
>>>email announcements. We are not proposing any changes in terms of the
>>>scheduling of any meeting-related events, the full availability of the
>>>meeting network starting on Sunday, the opening of on-site
>>>registration, or the meeting fee.
>>>
>The problem is that we now are expected to have work going non stop from
>Saturday to Friday. 7 full days. Maybe I am just old, but that does not
>look healthy.
>
>-- Christian Huitema

That=E2=80=99s already what many of us do, with 12-16 hour days, following our
regular work week the previous week, and slipping actual travel time in
between other work.

It=E2=80=99s not that anybody expects me to work that amount of time, it=E2=80=99s just
that that=E2=80=99s the amount of work I need to get done during IETF weeks. Many
times I=E2=80=99ve had people want to schedule hours-long meetings on Sunday
=E2=80=9Cbefore=E2=80=9D IETF, but I have IETF commitments that day. So this updating t=
he
description to match reality.

Having said that, I=E2=80=99ll argue my own point: are the Saturday-Sunday events
actually IETF activities? If =E2=80=9Cthe work of the IETF=E2=80=9D is just the set of
stuff contained in WGs and maybe BoFs, then the meeting is Monday-Friday.
If the Hackathon, Code Sprint, Tutorials, IEPG, and receptions are IETF
activities, then the meeting is Saturday-Friday, though many people may
elect not to arrive until later.

Lee



From nobody Wed Jun 21 10:59: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 0E3E512943C for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 10:59:36 -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 viM2FpDizPj9 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 10:59: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 56F2D126B7E for <ietf@ietf.org>; Wed, 21 Jun 2017 10:59:34 -0700 (PDT)
X-AuditID: 1209190d-9c5ff7000000429c-b5-594ab404bc60
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-2.mit.edu (Symantec Messaging Gateway) with SMTP id 8D.14.17052.404BA495; Wed, 21 Jun 2017 13:59:32 -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 v5LHxVEl025055; Wed, 21 Jun 2017 13:59: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 v5LHxRv1017770 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 21 Jun 2017 13:59:29 -0400
Date: Wed, 21 Jun 2017 12:59:27 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Lee Howard <lee@asgard.org>
Cc: Christian Huitema <huitema@huitema.net>, ietf@ietf.org
Subject: Re: Saturday as start day
Message-ID: <20170621175926.GM39245@kduck.kaduk.org>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net> <D57020DB.7D730%lee@asgard.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <D57020DB.7D730%lee@asgard.org>
User-Agent: Mutt/1.7.1 (2016-10-04)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuphleLIzCtJLcpLzFFi42IRYrdT12XZ4hVp0HlTzGJy42x2i2cb57NY /Nz3h9GB2eNXz3wmj1szTrF4LFnykymAOYrLJiU1J7MstUjfLoEr42DPPeaC5ZwVvw9uZ2lg 3MDexcjBISFgIvF9hVQXIxeHkMBiJokHvxYzQjgbGSVO3dzC3MXICeRcZZJouOAGYrMIqErM 7lsJFmcTUJFo6L4MZosIyEssnrkUzGYWsJJo+7iSHcQWFlCS+PykgxHE5gVaNuHITlaIBccZ JT68ncAMkRCUODnzCQtEs7rEn3mXmEGuYxaQllj+jwMiLC/RvHU2WDmngI7E5M/7wWxRAWWJ v4fvsUxgFJyFZNIsJJNmIUyahWTSAkaWVYyyKblVurmJmTnFqcm6xcmJeXmpRbpGermZJXqp KaWbGEGBzinJu4Px312vQ4wCHIxKPLwTGrwihVgTy4orcw8xSnIwKYnydiwDCvEl5adUZiQW Z8QXleakFh9ilOBgVhLhbd0ElONNSaysSi3Kh0lJc7AoifOKazRGCAmkJ5akZqemFqQWwWRl ODiUJHhXgTQKFqWmp1akZeaUIKSZODhBhvMADddZAzK8uCAxtzgzHSJ/ilFRSpz34UaghABI IqM0D64XlIgksvfXvGIUB3pFmPcAyAoeYBKD634FNJgJaPCLIx4gg0sSEVJSDYwLbBeGail+ 2q+65vm0Js4Vr5jZTnmoXRf8MLfVvEPXX/nYlSvmr7Yx/JHb1VKh6CG3b27MpVUXVyydbWX6 uv7C5ndKKZ+ufWdS3fy1TGv1roM695x2P8o9GXBtBWeTmWzgX+WZO6KVH1Yubl594v/HaO72 mfyN4QvOK36R95u36MRJEa0bq9bGK7EUZyQaajEXFScCADHOoaAfAwAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wTQ7SLEemloeGkA72DlAyoIgSEc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 17:59:36 -0000

On Wed, Jun 21, 2017 at 01:17:45PM -0400, Lee Howard wrote:
> 
> 
> On 6/21/17, 9:53 AM, "ietf on behalf of Christian Huitema"
> <ietf-bounces@ietf.org on behalf of huitema@huitema.net> wrote:
> 
> >>>
> >The problem is that we now are expected to have work going non stop from
> >Saturday to Friday. 7 full days. Maybe I am just old, but that does not
> >look healthy.
> >
> >-- Christian Huitema
> 
> That’s already what many of us do, with 12-16 hour days, following our
> regular work week the previous week, and slipping actual travel time in
> between other work.
> 
> It’s not that anybody expects me to work that amount of time, it’s just
> that that’s the amount of work I need to get done during IETF weeks. Many
> times I’ve had people want to schedule hours-long meetings on Sunday
> “before” IETF, but I have IETF commitments that day. So this updating the
> description to match reality.

I don't think anyone is disputing that this is updating the
description to match reality.  I believe Christian's question is
an attempt to prompt us to reassess that reality and its
sustainability, which seems a fair question to consider.

-Ben


From nobody Wed Jun 21 11:09:11 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 38E2B1270A0 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 11:09:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 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, MIME_QP_LONG_LINE=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 else2DJWeY9h for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 11:09:06 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::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 98B61126E3A for <ietf@ietf.org>; Wed, 21 Jun 2017 11:09:06 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id s66so88360319pfs.1 for <ietf@ietf.org>; Wed, 21 Jun 2017 11:09:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version; bh=iMmI1phkNpcfo6G1tD55Ztw+v9KqJfr/EUDxFN8dQms=; b=sTlcC4CG7ZOc77G552oF2sikDHu41wxNKcbfg8sm4jaFErKoTLjUaiYAYAP3UkfMNI I1PS5TIbUEB6SLlS73gRJWpnPFal+Y3/n0caGjLPgJww23JgREdd8sQbs2hk4nz7Wvx0 ncxj0jQU1zjAzIgVXKYNTrgkl18AY/nNJ4e/U5dxOei6bKh5sQZm3Efn7/f3xM62QHh/ iJEBGfh2Rt4nHsXG5Yl8Vsq0n4NnpAoakFz7zCi+GpBcKLfHa3iX0nvUCayZYEh5d4cK PxosWMI0Se9MMj6YViNUmImnjimBWmeCdDsTlSsqUlwq0pnNRFO+58G9etfK5H4s7M3w cG4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:references:in-reply-to:mime-version; bh=iMmI1phkNpcfo6G1tD55Ztw+v9KqJfr/EUDxFN8dQms=; b=oqe1HBBzSL7galWommaNmw13sClxZ/FpYvypA/KcB+BQ+yTAchb5cNc3YPm9L5buI1 e6MjklZr9eXcs7cb/VWvxs7l8xhfEjPkFcwXsNp4CZp4yOCqW+FCgbWxvp56CLxeVs0g k+08oNA7A4pOb8vCfDvyIJliABHzsK3w7eL9l/z5HcOzB+BnPkBgKuzzuIxS85n3vGjZ 9idmrwvzcF6D5IrmrkOWve4oZCTUwAJ5jwcdXEVpcmc3RpjNB60dP1dzsvyKlRmWdQLq apsd0cImBYfq1ixNei/PqgLAhq7d9A6LwFBnQqgbabXFFE5BRUHdM6fL6ShkBLMCDueY 7GAg==
X-Gm-Message-State: AKS2vOzHMA95zmszBagFwA9fC8vdLqALpljUwEAmB0293Ls951iHYn91 piKWmjPhqLoOO4M5S88=
X-Received: by 10.98.12.76 with SMTP id u73mr6513589pfi.62.1498068546240; Wed, 21 Jun 2017 11:09:06 -0700 (PDT)
Received: from [192.168.254.157] (107-1-141-74-ip-static.hfc.comcastbusiness.net. [107.1.141.74]) by smtp.gmail.com with ESMTPSA id d62sm778915pga.2.2017.06.21.11.09.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Jun 2017 11:09:05 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Wed, 21 Jun 2017 11:09:06 -0700
Subject: Re: Saturday as start day
From: Jeff Tantsura <jefftant.ietf@gmail.com>
To: Alissa Cooper <alissa@cooperw.in>, IETF Discussion <ietf@ietf.org>
Message-ID: <F00C077F-72B5-41CF-90A4-C1DFB4D6B3C3@gmail.com>
Thread-Topic: Saturday as start day
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in>
In-Reply-To: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3580888147_315881549"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xFpRJfOZjglucsUlvmi-aHPDGQc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 18:09:09 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3580888147_315881549
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: 7bit

Alissa,

 

I support the idea, for many of us this is just formalization of what we have been doing anyway.

It could help some folks who need to justify flight/hotel at earlier date to their management. 

 

Cheers,

Jeff

 

 

From: ietf <ietf-bounces@ietf.org> on behalf of Alissa Cooper <alissa@cooperw.in>
Date: Wednesday, June 21, 2017 at 05:34
To: IETF Discussion <ietf@ietf.org>
Subject: Saturday as start day

 

Hi all,

 

Based on a suggestion from Paul Hoffman, the IESG believes it would be beneficial to denote the official start of IETF meetings to be on Saturday rather than Sunday, starting with IETF 100. We believe this would be sensible given that events such as the hackathon and code sprint start on Saturday, and may make it easier for some participants to get travel approval to attend those events. This change would be reflected in the dates posted on the IETF web site and sent out in email announcements. We are not proposing any changes in terms of the scheduling of any meeting-related events, the full availability of the meeting network starting on Sunday, the opening of on-site registration, or the meeting fee.

 

If you have feedback about this change, please send it to ietf@ietf.org, or exceptionally to iesg@ietf.org, by July 5, 2017.

Thanks,
The IESG


--B_3580888147_315881549
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DTitle c=
ontent=3D""><meta name=3DKeywords content=3D""><meta http-equiv=3DContent-Type conte=
nt=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft Word 1=
5 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-reply;
	font-family:Calibri;
	color:windowtext;}
span.msoIns
	{mso-style-type:export-only;
	mso-style-name:"";
	text-decoration:underline;
	color:teal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body bgcolor=3Dwhite lang=3DEN-US link=3Dblue vlink=3Dpurple><di=
v class=3DWordSection1><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:Calibri'>Alissa,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
font-size:11.0pt;font-family:Calibri'><o:p>&nbsp;</o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:11.0pt;font-family:Calibri'>I support the id=
ea, for many of us this is just formalization of what we have been doing any=
way.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt;f=
ont-family:Calibri'>It could help some folks who need to justify flight/hote=
l at earlier date to their management. <o:p></o:p></span></p><div><p class=3DM=
soNormal><span style=3D'font-size:10.5pt;font-family:Calibri;color:black'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.5pt;fon=
t-family:Calibri;color:black'>Cheers,<o:p></o:p></span></p><p class=3DMsoNorma=
l><span style=3D'font-size:10.5pt;font-family:Calibri;color:black'>Jeff<o:p></=
o:p></span></p></div><p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-f=
amily:Calibri'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt;font-family:Calibri'><o:p>&nbsp;</o:p></span></p><div style=3D=
'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p cl=
ass=3DMsoNormal style=3D'margin-left:.5in'><b><span style=3D'font-family:Calibri;c=
olor:black'>From: </span></b><span style=3D'font-family:Calibri;color:black'>i=
etf &lt;ietf-bounces@ietf.org&gt; on behalf of Alissa Cooper &lt;alissa@coop=
erw.in&gt;<br><b>Date: </b>Wednesday, June 21, 2017 at 05:34<br><b>To: </b>I=
ETF Discussion &lt;ietf@ietf.org&gt;<br><b>Subject: </b>Saturday as start da=
y<o:p></o:p></span></p></div><div><p class=3DMsoNormal style=3D'margin-left:.5in=
'><o:p>&nbsp;</o:p></p></div><p class=3DMsoNormal style=3D'margin-left:.5in'>Hi =
all,<o:p></o:p></p><div><p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nb=
sp;</o:p></p></div><div><div><p class=3DMsoNormal style=3D'margin-left:.5in'>Bas=
ed on a suggestion from Paul Hoffman, the IESG believes it would be benefici=
al to denote the official start of IETF meetings to be on Saturday rather th=
an Sunday, starting with IETF 100. We believe this would be sensible given t=
hat events such as the hackathon and code sprint start on Saturday, and may =
make it easier for some participants to get travel approval to attend those =
events. This change would be reflected in the dates posted on the IETF web s=
ite and sent out in email announcements. We are not proposing any changes in=
 terms of the scheduling of any meeting-related events, the full availabilit=
y of the meeting network starting on Sunday, the opening of on-site registra=
tion, or the meeting fee.<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D=
'margin-left:.5in'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal style=3D=
'margin-left:.5in'>If you have feedback about this change, please send it to=
&nbsp;<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>, or exceptionally to&=
nbsp;<a href=3D"mailto:iesg@ietf.org">iesg@ietf.org</a>, by July 5, 2017.<br><=
br>Thanks,<br>The IESG<o:p></o:p></p></div></div></div></body></html>

--B_3580888147_315881549--



From nobody Wed Jun 21 12:32:45 2017
Return-Path: <heas@shrubbery.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 54CC5129480 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 12:32:43 -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_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 du4H5EgR5B9N for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 12:32:41 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADB20128CDB for <ietf@ietf.org>; Wed, 21 Jun 2017 12:32:41 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id 4485A851B6; Wed, 21 Jun 2017 19:32:41 +0000 (UTC)
Date: Wed, 21 Jun 2017 19:32:41 +0000
From: heasley <heas@shrubbery.net>
To: Christian Huitema <huitema@huitema.net>
Cc: ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Message-ID: <20170621193241.GN94345@shrubbery.net>
References: <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <20170614195604.GN89424@shrubbery.net> <8c75fbdc-8f9b-66ae-a005-260e70dfbe2b@joelhalpern.com> <fbdf6885-b6c2-faa3-53d8-8db135b077c4@gmail.com> <43A4111E-39B7-49FE-B63A-28658E859693@gmail.com> <be856ef3-7bef-244e-bf94-b0af1f1ba99b@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <be856ef3-7bef-244e-bf94-b0af1f1ba99b@huitema.net>
X-PGPkey: http://www.shrubbery.net/~heas/public-key.asc
X-note: live free, or die!
X-homer: i just want to have a beer while i am caring.
X-Claimation: an engineer needs a manager like a fish needs a bicycle
X-reality: only YOU can put an end to the embarrassment that is Tom Cruise
User-Agent: Mutt/1.8.0 (2017-02-23)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oVml4Cj7YEv4kLOB_aQMKq0sjuU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 19:32:43 -0000

Thu, Jun 15, 2017 at 11:35:47AM -0700, Christian Huitema:
>=20
>=20
> On 6/15/2017 11:28 AM, Bob Hinden wrote:
> > p.s. The file name chosen for this draft appears to be a good example o=
f stepping on the toes of those who came before, instead of standing on the=
ir shoulders.  See: http://wiki.c2.com/?ShouldersOfGiants
>=20
> On the other hand, there is something to be said for "being nice
> considered harmful".

Amen, the author is not being rude - be polite and leave your tender feelin=
gs
outside.


From nobody Wed Jun 21 12:58:21 2017
Return-Path: <eckelcu@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 10EC1128D19 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 12:58:19 -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 zUEfdY1OIMxy for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 12:58:17 -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 15535127866 for <ietf@ietf.org>; Wed, 21 Jun 2017 12:58:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11062; q=dns/txt; s=iport; t=1498075096; x=1499284696; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=wxN0RqvYojiLf0xHg25yzcB46Okly9WadjQ7hFo2kyE=; b=HbD9BB8jFH9TlHSh/zP4oIiaU9Ar+fVr8QJD+s3kj+yCIRsEaxIZ3iwk GOQWmuMgSo5HLly0DwFDAXQKAu7MZDkZ6WAottA+P9qSTnViHTLzdUiR6 HD5l+zQe054CGsaXg1cUSZRxa6KxIDb87nxPgaQg+lSQZ+PR/U9vjLlcY k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DgAQBszkpZ/40NJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm9pYoENB4NlihmROyKILIgihSqCEYYkAhqCXD8YAQIBAQEBAQE?= =?us-ascii?q?BayiFGAEBAQEDI1YQAgEIEQMBAigDAgICHxEUCQgCBA4FiUhMAxWqdIImKocJD?= =?us-ascii?q?YQeAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYhNKwuCboJXgWQSATwWglwwgjEFnic?= =?us-ascii?q?7Ao55hGeCCIVIij6LXokyAR84fwt0FVsBhnx2hzqBI4ENAQEB?=
X-IronPort-AV: E=Sophos; i="5.39,370,1493683200"; d="scan'208,217"; a="42876630"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 Jun 2017 19:58:16 +0000
Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id v5LJwGqL024567 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 21 Jun 2017 19:58:16 GMT
Received: from xch-aln-018.cisco.com (173.36.7.28) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 21 Jun 2017 14:58:15 -0500
Received: from xch-aln-018.cisco.com ([173.36.7.28]) by XCH-ALN-018.cisco.com ([173.36.7.28]) with mapi id 15.00.1210.000; Wed, 21 Jun 2017 14:58:15 -0500
From: "Charles Eckel (eckelcu)" <eckelcu@cisco.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Re: Saturday as start day
Thread-Topic: Saturday as start day
Thread-Index: AQHS6orAW3zVXZq7l0uVpJXyLJXhSaIv8a0A//+pJoA=
Date: Wed, 21 Jun 2017 19:58:15 +0000
Message-ID: <D9208D73-8048-4590-8C6D-2B93A350CB56@cisco.com>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <F00C077F-72B5-41CF-90A4-C1DFB4D6B3C3@gmail.com>
In-Reply-To: <F00C077F-72B5-41CF-90A4-C1DFB4D6B3C3@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.22.0.170515
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.20.182.35]
Content-Type: multipart/alternative; boundary="_000_D9208D73804845908C6D2B93A350CB56ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sSLDfFWPF0zCcTM08g9-kbqz-ek>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 19:58:19 -0000

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

SSBhbSB2ZXJ5IG11Y2ggaW4gZmF2b3IgaXQuIEl0IHdpbGwgaGVscCBhbGxldmlhdGUgY29uZnVz
aW9uIHBlb3BsZSBoYXZlIGhhZCBpbiB0aGUgcGFzdCByZWdhcmRpbmcgdGhlIGRhdGVzIG9mIHRo
ZSBoYWNrYXRob24sIGVzcGVjaWFsbHkgcGVvcGxlIHdobyBhcmUgbmV3IHRvIHRoZSBJRVRGLg0K
DQpDaGVlcnMsDQpDaGFybGVzDQoNCkZyb206IGlldGYgPGlldGYtYm91bmNlc0BpZXRmLm9yZz4g
b24gYmVoYWxmIG9mIEplZmYgVGFudHN1cmEgPGplZmZ0YW50LmlldGZAZ21haWwuY29tPg0KRGF0
ZTogV2VkbmVzZGF5LCBKdW5lIDIxLCAyMDE3IGF0IDExOjA5IEFNDQpUbzogQWxpc3NhIENvb3Bl
ciA8YWxpc3NhQGNvb3BlcncuaW4+LCAiaWV0ZkBpZXRmLm9yZyIgPGlldGZAaWV0Zi5vcmc+DQpT
dWJqZWN0OiBSZTogU2F0dXJkYXkgYXMgc3RhcnQgZGF5DQoNCkFsaXNzYSwNCg0KSSBzdXBwb3J0
IHRoZSBpZGVhLCBmb3IgbWFueSBvZiB1cyB0aGlzIGlzIGp1c3QgZm9ybWFsaXphdGlvbiBvZiB3
aGF0IHdlIGhhdmUgYmVlbiBkb2luZyBhbnl3YXkuDQpJdCBjb3VsZCBoZWxwIHNvbWUgZm9sa3Mg
d2hvIG5lZWQgdG8ganVzdGlmeSBmbGlnaHQvaG90ZWwgYXQgZWFybGllciBkYXRlIHRvIHRoZWly
IG1hbmFnZW1lbnQuDQoNCkNoZWVycywNCkplZmYNCg0KDQpGcm9tOiBpZXRmIDxpZXRmLWJvdW5j
ZXNAaWV0Zi5vcmc+IG9uIGJlaGFsZiBvZiBBbGlzc2EgQ29vcGVyIDxhbGlzc2FAY29vcGVydy5p
bj4NCkRhdGU6IFdlZG5lc2RheSwgSnVuZSAyMSwgMjAxNyBhdCAwNTozNA0KVG86IElFVEYgRGlz
Y3Vzc2lvbiA8aWV0ZkBpZXRmLm9yZz4NClN1YmplY3Q6IFNhdHVyZGF5IGFzIHN0YXJ0IGRheQ0K
DQpIaSBhbGwsDQoNCkJhc2VkIG9uIGEgc3VnZ2VzdGlvbiBmcm9tIFBhdWwgSG9mZm1hbiwgdGhl
IElFU0cgYmVsaWV2ZXMgaXQgd291bGQgYmUgYmVuZWZpY2lhbCB0byBkZW5vdGUgdGhlIG9mZmlj
aWFsIHN0YXJ0IG9mIElFVEYgbWVldGluZ3MgdG8gYmUgb24gU2F0dXJkYXkgcmF0aGVyIHRoYW4g
U3VuZGF5LCBzdGFydGluZyB3aXRoIElFVEYgMTAwLiBXZSBiZWxpZXZlIHRoaXMgd291bGQgYmUg
c2Vuc2libGUgZ2l2ZW4gdGhhdCBldmVudHMgc3VjaCBhcyB0aGUgaGFja2F0aG9uIGFuZCBjb2Rl
IHNwcmludCBzdGFydCBvbiBTYXR1cmRheSwgYW5kIG1heSBtYWtlIGl0IGVhc2llciBmb3Igc29t
ZSBwYXJ0aWNpcGFudHMgdG8gZ2V0IHRyYXZlbCBhcHByb3ZhbCB0byBhdHRlbmQgdGhvc2UgZXZl
bnRzLiBUaGlzIGNoYW5nZSB3b3VsZCBiZSByZWZsZWN0ZWQgaW4gdGhlIGRhdGVzIHBvc3RlZCBv
biB0aGUgSUVURiB3ZWIgc2l0ZSBhbmQgc2VudCBvdXQgaW4gZW1haWwgYW5ub3VuY2VtZW50cy4g
V2UgYXJlIG5vdCBwcm9wb3NpbmcgYW55IGNoYW5nZXMgaW4gdGVybXMgb2YgdGhlIHNjaGVkdWxp
bmcgb2YgYW55IG1lZXRpbmctcmVsYXRlZCBldmVudHMsIHRoZSBmdWxsIGF2YWlsYWJpbGl0eSBv
ZiB0aGUgbWVldGluZyBuZXR3b3JrIHN0YXJ0aW5nIG9uIFN1bmRheSwgdGhlIG9wZW5pbmcgb2Yg
b24tc2l0ZSByZWdpc3RyYXRpb24sIG9yIHRoZSBtZWV0aW5nIGZlZS4NCg0KSWYgeW91IGhhdmUg
ZmVlZGJhY2sgYWJvdXQgdGhpcyBjaGFuZ2UsIHBsZWFzZSBzZW5kIGl0IHRvIGlldGZAaWV0Zi5v
cmc8bWFpbHRvOmlldGZAaWV0Zi5vcmc+LCBvciBleGNlcHRpb25hbGx5IHRvIGllc2dAaWV0Zi5v
cmc8bWFpbHRvOmllc2dAaWV0Zi5vcmc+LCBieSBKdWx5IDUsIDIwMTcuDQoNClRoYW5rcywNClRo
ZSBJRVNHDQo=

--_000_D9208D73804845908C6D2B93A350CB56ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <244E1F77BB3E8249B303416C442FE1E6@emea.cisco.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8N
CnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWls
eToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1
bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNw
YW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQt
ZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bh
bi5tc29JbnMNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJbXNvLXN0eWxlLW5hbWU6
IiI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTsNCgljb2xvcjp0ZWFsO30NCi5Nc29DaHBE
ZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7
fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBp
biAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rp
b24xO30NCi0tPjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9keSBiZ2NvbG9yPSJ3aGl0ZSIgbGFuZz0i
RU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rp
b24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgYW0gdmVyeSBtdWNoIGluIGZhdm9yIGl0LiBJ
dCB3aWxsIGhlbHAgYWxsZXZpYXRlIGNvbmZ1c2lvbiBwZW9wbGUgaGF2ZSBoYWQgaW4gdGhlIHBh
c3QgcmVnYXJkaW5nIHRoZSBkYXRlcyBvZiB0aGUgaGFja2F0aG9uLCBlc3BlY2lhbGx5IHBlb3Bs
ZSB3aG8gYXJlIG5ldyB0byB0aGUgSUVURi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q2hlZXJz
LDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q2hhcmxlczxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0
eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzoz
LjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0i
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5G
cm9tOg0KPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5pZXRmICZsdDtpZXRmLWJvdW5jZXNAaWV0Zi5v
cmcmZ3Q7IG9uIGJlaGFsZiBvZiBKZWZmIFRhbnRzdXJhICZsdDtqZWZmdGFudC5pZXRmQGdtYWls
LmNvbSZndDs8YnI+DQo8Yj5EYXRlOiA8L2I+V2VkbmVzZGF5LCBKdW5lIDIxLCAyMDE3IGF0IDEx
OjA5IEFNPGJyPg0KPGI+VG86IDwvYj5BbGlzc2EgQ29vcGVyICZsdDthbGlzc2FAY29vcGVydy5p
biZndDssICZxdW90O2lldGZAaWV0Zi5vcmcmcXVvdDsgJmx0O2lldGZAaWV0Zi5vcmcmZ3Q7PGJy
Pg0KPGI+U3ViamVjdDogPC9iPlJlOiBTYXR1cmRheSBhcyBzdGFydCBkYXk8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlm
Ij5BbGlzc2EsPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OyxzYW5zLXNlcmlmIj4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkkgc3VwcG9ydCB0aGUgaWRlYSwgZm9yIG1hbnkgb2Yg
dXMgdGhpcyBpcyBqdXN0IGZvcm1hbGl6YXRpb24gb2Ygd2hhdCB3ZSBoYXZlIGJlZW4gZG9pbmcg
YW55d2F5Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZiI+SXQgY291bGQgaGVscCBzb21lIGZvbGtzIHdobyBuZWVkIHRvIGp1c3RpZnkg
ZmxpZ2h0L2hvdGVsIGF0IGVhcmxpZXIgZGF0ZSB0byB0aGVpciBtYW5hZ2VtZW50Lg0KPC9zcGFu
PjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1z
ZXJpZjtjb2xvcjpibGFjayI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5DaGVlcnMsPC9zcGFuPjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OmJsYWNrIj5KZWZmPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERG
IDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkZyb206DQo8L3NwYW4+PC9i
PjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6YmxhY2siPmlldGYgJmx0O2lldGYtYm91bmNlc0BpZXRmLm9yZyZndDsgb24gYmVoYWxm
IG9mIEFsaXNzYSBDb29wZXIgJmx0O2FsaXNzYUBjb29wZXJ3LmluJmd0Ozxicj4NCjxiPkRhdGU6
IDwvYj5XZWRuZXNkYXksIEp1bmUgMjEsIDIwMTcgYXQgMDU6MzQ8YnI+DQo8Yj5UbzogPC9iPklF
VEYgRGlzY3Vzc2lvbiAmbHQ7aWV0ZkBpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+
U2F0dXJkYXkgYXMgc3RhcnQgZGF5PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPiZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
LWxlZnQ6LjVpbiI+SGkgYWxsLDxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxl
ZnQ6LjVpbiI+QmFzZWQgb24gYSBzdWdnZXN0aW9uIGZyb20gUGF1bCBIb2ZmbWFuLCB0aGUgSUVT
RyBiZWxpZXZlcyBpdCB3b3VsZCBiZSBiZW5lZmljaWFsIHRvIGRlbm90ZSB0aGUgb2ZmaWNpYWwg
c3RhcnQgb2YgSUVURiBtZWV0aW5ncyB0byBiZSBvbiBTYXR1cmRheSByYXRoZXIgdGhhbiBTdW5k
YXksIHN0YXJ0aW5nIHdpdGggSUVURiAxMDAuIFdlIGJlbGlldmUgdGhpcyB3b3VsZA0KIGJlIHNl
bnNpYmxlIGdpdmVuIHRoYXQgZXZlbnRzIHN1Y2ggYXMgdGhlIGhhY2thdGhvbiBhbmQgY29kZSBz
cHJpbnQgc3RhcnQgb24gU2F0dXJkYXksIGFuZCBtYXkgbWFrZSBpdCBlYXNpZXIgZm9yIHNvbWUg
cGFydGljaXBhbnRzIHRvIGdldCB0cmF2ZWwgYXBwcm92YWwgdG8gYXR0ZW5kIHRob3NlIGV2ZW50
cy4gVGhpcyBjaGFuZ2Ugd291bGQgYmUgcmVmbGVjdGVkIGluIHRoZSBkYXRlcyBwb3N0ZWQgb24g
dGhlIElFVEYgd2ViIHNpdGUgYW5kIHNlbnQNCiBvdXQgaW4gZW1haWwgYW5ub3VuY2VtZW50cy4g
V2UgYXJlIG5vdCBwcm9wb3NpbmcgYW55IGNoYW5nZXMgaW4gdGVybXMgb2YgdGhlIHNjaGVkdWxp
bmcgb2YgYW55IG1lZXRpbmctcmVsYXRlZCBldmVudHMsIHRoZSBmdWxsIGF2YWlsYWJpbGl0eSBv
ZiB0aGUgbWVldGluZyBuZXR3b3JrIHN0YXJ0aW5nIG9uIFN1bmRheSwgdGhlIG9wZW5pbmcgb2Yg
b24tc2l0ZSByZWdpc3RyYXRpb24sIG9yIHRoZSBtZWV0aW5nIGZlZS48bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDou
NWluIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5JZiB5b3UgaGF2ZSBmZWVkYmFjayBhYm91
dCB0aGlzIGNoYW5nZSwgcGxlYXNlIHNlbmQgaXQgdG8mbmJzcDs8YSBocmVmPSJtYWlsdG86aWV0
ZkBpZXRmLm9yZyI+aWV0ZkBpZXRmLm9yZzwvYT4sIG9yIGV4Y2VwdGlvbmFsbHkgdG8mbmJzcDs8
YSBocmVmPSJtYWlsdG86aWVzZ0BpZXRmLm9yZyI+aWVzZ0BpZXRmLm9yZzwvYT4sIGJ5IEp1bHkg
NSwgMjAxNy48YnI+DQo8YnI+DQpUaGFua3MsPGJyPg0KVGhlIElFU0c8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_D9208D73804845908C6D2B93A350CB56ciscocom_--


From nobody Wed Jun 21 15:10:05 2017
Return-Path: <aaron.falk@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 7E0C6127369; Wed, 21 Jun 2017 15:10:02 -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 eluCVVIQgpta; Wed, 21 Jun 2017 15:10:00 -0700 (PDT)
Received: from mail-qk0-x242.google.com (mail-qk0-x242.google.com [IPv6:2607:f8b0:400d: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 6C71D124B0A; Wed, 21 Jun 2017 15:10:00 -0700 (PDT)
Received: by mail-qk0-x242.google.com with SMTP id r62so17655556qkf.3; Wed, 21 Jun 2017 15:10:00 -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; bh=Idj/peSl7su3vL97Z6PQgAoiwge7UNwUKyVpMH9MUPo=; b=PRZ2efERiHQL/i9y0SPZQvqua/8u48LTTpSgNJLPenH/2H/etBUvU42zIZH/dJvtT3 YNhIiBOD/SFVDmkzUkdcqKqurXqk8cGV247FPP0JXYtmhKrdwHCcOnotEMEeVRw6UdEY SIluCEtji6yIwVU1RywEVO3nZZNVeJTAPMkJceH7/Kirq3J5lC54kQe7GDtNCuHJ53c8 8UYBpboqQmAPxWJU8GXzkUJUYq5PKssYbGKjIgXfuZA+vhFFf4rxxKPtwX022p4grwcn 3VrwaDw832XQgEgab/39mAij9PJr1aCC/goRQ7EytdPfLrQ7PogrPgwzpquCc+bqUezo /naA==
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; bh=Idj/peSl7su3vL97Z6PQgAoiwge7UNwUKyVpMH9MUPo=; b=nx1pgVAd3ThSQrYbedHq6SvE9YRV6r2x+65Eai8HSbcSB5VLynuSZ+0wlVbpGFZMtk tqjh5hxO0lRlxcRhWOs9mhPeK5JjHw4ZtJHarU14SXf/G3ThzHS3SZmCjydCPxzcrGq9 z56hD8D0BTzRvQUaJlLJ+YB74PYX4joZQgTd5M/pds2r8X2ThR8rOdtazRL/uMcX+nwT E2oDN+RrJrLy6TYHsW/Ll9UDimJxZJhrj8ugwl4xGpVTJ7X91ekC/tmbUSCarXfNG/Hy K328lJ12PlzX4yqkZ8KFwjlRGddeXUH8VhEryi9FVYHZ0SXVyMq1QftA6CAyEnglb1FR 9UtQ==
X-Gm-Message-State: AKS2vOxw71er4MnTBZ6TztvNgkMyL9K46CH5Qef4HzsI7WtUyRXh8lfQ dxkiGKcrc78BT5xKQLY=
X-Received: by 10.55.149.130 with SMTP id x124mr43912020qkd.213.1498082999438;  Wed, 21 Jun 2017 15:09:59 -0700 (PDT)
Received: from [172.19.37.44] ([72.246.0.14]) by smtp.gmail.com with ESMTPSA id a62sm10975461qkd.14.2017.06.21.15.09.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Jun 2017 15:09:58 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, "99attendees@ietf.org" <99attendees@ietf.org>
Subject: PechaKucha presenters for Prague?
Date: Wed, 21 Jun 2017 18:09:56 -0400
Message-ID: <D53C2422-8C47-4E42-B5AF-9A263FB89730@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_6B0F69C3-F04B-40CE-94E7-85B89EAF4B4E_="
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O7byc23JsjgzcpAGw6d6aet-9MQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 21 Jun 2017 22:10:02 -0000

--=_MailMate_6B0F69C3-F04B-40CE-94E7-85B89EAF4B4E_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

This is a poll for folks who are interested in presenting at a =

PechaKucha in Prague.  The number of folks presenting has declined =

slightly and I=E2=80=99m contemplating whether holding a session at every=
 IETF =

meeting is too frequent.  If I don=E2=80=99t hear from enough folks we=E2=
=80=99ll =

wait until Singapore to do the next one.  In other words, if you want to =

give a talk, please send me a note ASAP.

Standard invitation and background info below.

Thanks!

=E2=80=94aaron

____

A Pecha Kucha is a lightning-talk presentation format, originating in =

Japan, where a speaker presents 20 image-only slides that are each on =

the screen for 20 seconds and advance automatically.  With each talk =

lasting for 6:40, it has the feature of forcing presentations -- good or =

bad -- to be focused and brief.  This is an unofficial event. Topics are =

encouraged to be a IETF-related and satirical or controversial in some =

way, although not mean-spirited.  Anyone can participate in this social =

event.  Video from the Berlin, Seoul, and Chicago PKs can be found =

[here](http://snaggletooth.akam.ai).

Format Details:

* Presentation slots are open to all, assigned first come, first served.
* To reserve a presentation slot, send a name and title to =

aaron.falk@gmail.com and receive confirmation.
* Presenters must agree to adhere to the Pecha Kucha format (20 slides, =

primarily image-only, automatically advancing every 20 seconds).
* There are lots of online tutorials and suggestions for how to make a =

good Pecha Kucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

[[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pecha=
=2Ehtml)], =

[[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].
--=_MailMate_6B0F69C3-F04B-40CE-94E7-85B89EAF4B4E_=
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">This is a poll for folks who are interested in presenting=
 at a PechaKucha in Prague.  The number of folks presenting has declined =
slightly and I=E2=80=99m contemplating whether holding a session at every=
 IETF meeting is too frequent.  If I don=E2=80=99t hear from enough folks=
 we=E2=80=99ll wait until Singapore to do the next one.  In other words, =
if you want to give a talk, please send me a note ASAP.   </p>

<p dir=3D"auto">Standard invitation and background info below.</p>

<p dir=3D"auto">Thanks!</p>

<p dir=3D"auto">=E2=80=94aaron</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">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin, Seoul, and Chicago PKs can be found <a =
href=3D"http://snaggletooth.akam.ai" style=3D"color:#3983C4">here</a>.</p=
>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#3983C4">aaron.falk@gmail.com<=
/a> and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#3983C4">1</a>], [<a href=3D"http://blog.indezine.com/20=
12/05/10-tips-to-create-and-present-pecha.html" style=3D"color:#3983C4">2=
</a>], [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha=
-kucha/" style=3D"color:#3983C4">3</a>].</li>
</ul>
</div>
</div>
</body>
</html>

--=_MailMate_6B0F69C3-F04B-40CE-94E7-85B89EAF4B4E_=--


From nobody Wed Jun 21 17:00: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 9C0C4126D74 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 17:00:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.902
X-Spam-Level: 
X-Spam-Status: No, score=-6.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A_BFr0-VRnNh for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 17:00:55 -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 30EB212426E for <ietf@ietf.org>; Wed, 21 Jun 2017 17:00:55 -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 1dNpYH-0003O3-0r; Thu, 22 Jun 2017 00:00:49 +0000
Date: Thu, 22 Jun 2017 09:00:47 +0900
Message-ID: <m2podwsxg0.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Benjamin Kaduk <kaduk@mit.edu>
Cc: Christian Huitema <huitema@huitema.net>, IETF Rinse Repeat <ietf@ietf.org>
Subject: Re: Saturday as start day
In-Reply-To: <20170621175926.GM39245@kduck.kaduk.org>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net> <D57020DB.7D730%lee@asgard.org> <20170621175926.GM39245@kduck.kaduk.org>
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/1xZQf2mMuAdDP-aNVk5gCFi_Bv4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 00:00:57 -0000

>>The problem is that we now are expected to have work going non stop
>>from Saturday to Friday. 7 full days. Maybe I am just old, but that
>>does not look healthy.
> I believe Christian's question is an attempt to prompt us to reassess
> that reality and its sustainability, which seems a fair question to
> consider.

and it would help if the *quality* of the week was higher.  time and
again, i have found the wg meeting to be a formalism, 25% process and
72% slideshow for those who need a preso slot to get travel approval.
for serious content, we retreat into side meetings, bar bofs, and
off-campus meals to have actual *discussion*.  and why endure extreme
travel if not to have discussion instead of process and powerpoint?

but ignore my whining.  i do not know any meeting of more than a hundred
which is mostly protein.  i.e. i have no model for 'success.'

randy


From nobody Wed Jun 21 18:41:16 2017
Return-Path: <ggm@algebras.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 9A66D129417 for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 18:41:15 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=algebras-org.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 H9BzP1eYfoaX for <ietf@ietfa.amsl.com>; Wed, 21 Jun 2017 18:41:12 -0700 (PDT)
Received: from mail-ua0-x233.google.com (mail-ua0-x233.google.com [IPv6:2607:f8b0:400c:c08::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 40B481293F4 for <ietf@ietf.org>; Wed, 21 Jun 2017 18:41:12 -0700 (PDT)
Received: by mail-ua0-x233.google.com with SMTP id z22so2462711uah.1 for <ietf@ietf.org>; Wed, 21 Jun 2017 18:41:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=algebras-org.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=KSkYt+z9CSVm8B1KNHptuR4KtMdUnW5zCUATFYmyssY=; b=dFffDg3TLBvqsAqSY51vgeWzt5gA2GPO/LGmsSLdIQDSQllema6U5DzqeI5/+pxstS OwYU6wcDBr/Tev1mXw5cErJOIKRa9lw0VcQTaJrZNORaxk4tlLJ3bGtqc7Zi6xHbaeC8 7ODHX65WZKqGDCBQQ5LCOrW6Qv+ElAVDjsm++T1qwN4g1qI7u5908pvzwlKS1YSgStf8 IsDr6YmckbHjisBw1MibhI1JojCKKfm8FammdfaU7yN/AA1ELuPPya+YrZI/CGTs7zjX lFF0PqKtVhocbSpzblyw0ccJzytugT1f7GoV5P8YoF0qZH8XaZ/y0TBgPvSyzPrKsFLa 7cMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=KSkYt+z9CSVm8B1KNHptuR4KtMdUnW5zCUATFYmyssY=; b=L4/rjUHBh++Q841SWAiuKwrnB6XZYX2OuIkJ9eC1IkDufSrDWtdMmCgEkHEItVWnYG zAxr4YUcGrRqvfJtklYHEyqMlu/LzTnE2mHiKG+pFdOoOXKNRIcz72IrPd11WpXqEnw5 We+Lk86xVUR6moLPvZYKnKLnYuLlh3rL6KoDi3QaPd2UpZZYx5G3d95nqtW07AvPLjPp LjAatXm5brq2be3izoB3jkT9d2UqBl1ZQsXQTIAwzjzKpnrlVhTdqWQphoP0rz8aCffx bt4hCXLnAdKWyVz2fnTnmerq/1rb/fjbKW19yVK1lAZNWYObcFGaCTavA3Mpi6PqwmDd g8oA==
X-Gm-Message-State: AKS2vOxVFbqOjhBTSdoY9oQBVGpsTVNfYcfEkgC5xxTD6XUdjT8erZ5Q JoaDVzkXHEKFH4VOTP21r4P0IlnZJrt0Etg=
X-Received: by 10.159.41.196 with SMTP id s62mr108891uas.136.1498095671127; Wed, 21 Jun 2017 18:41:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.103.90.18 with HTTP; Wed, 21 Jun 2017 18:41:10 -0700 (PDT)
X-Originating-IP: [2001:dc0:2001:210:7cca:eb27:9938:2080]
In-Reply-To: <m2podwsxg0.wl-randy@psg.com>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <a6ceaa2d-16fa-6145-bd2d-811dba6027ea@huitema.net> <D57020DB.7D730%lee@asgard.org> <20170621175926.GM39245@kduck.kaduk.org> <m2podwsxg0.wl-randy@psg.com>
From: George Michaelson <ggm@algebras.org>
Date: Thu, 22 Jun 2017 11:41:10 +1000
Message-ID: <CAKr6gn2rTb1Toufm9grz606Xx+eRRd+iTrrGWfV5bGk_GZWmag@mail.gmail.com>
Subject: Re: Saturday as start day
To: IETF Rinse Repeat <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eMXKlIRaChWTaPRpclmwl3fs_qw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 01:41:16 -0000

I would support this, if we remove Friday from the official calendar
of meetings. Because then,  I could expect to get back a weekend,
where currently 14+ hr flights in and out mean I lose two weekends per
IETF, I would lose only one.

So whilst I think 'desire/reality' has applied here and what you have
done formalizes what we know has happened, I would like the extension
act which you can't yet do: give us back one day please.

-george

PS the last time I raised this was probably 10 years ago. There is a
strong cultural push not to work specifically on Saturday, which I
understand, and I also understand there is a strong cultural push not
to work or travel on friday or saturday which I understand. I just
don't belong to those cultures, but I do understand this is a problem
for some people. I think my proposal is actually strictly neutral on
that, but arguably not.

On Thu, Jun 22, 2017 at 10:00 AM, Randy Bush <randy@psg.com> wrote:
>>>The problem is that we now are expected to have work going non stop
>>>from Saturday to Friday. 7 full days. Maybe I am just old, but that
>>>does not look healthy.
>> I believe Christian's question is an attempt to prompt us to reassess
>> that reality and its sustainability, which seems a fair question to
>> consider.
>
> and it would help if the *quality* of the week was higher.  time and
> again, i have found the wg meeting to be a formalism, 25% process and
> 72% slideshow for those who need a preso slot to get travel approval.
> for serious content, we retreat into side meetings, bar bofs, and
> off-campus meals to have actual *discussion*.  and why endure extreme
> travel if not to have discussion instead of process and powerpoint?
>
> but ignore my whining.  i do not know any meeting of more than a hundred
> which is mostly protein.  i.e. i have no model for 'success.'
>
> randy
>


From nobody Wed Jun 21 20:16:26 2017
Return-Path: <Xufeng_Liu@jabil.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96AD91293D6; Wed, 21 Jun 2017 20:16:24 -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=jabil.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 Y0uWAZxdI2-R; Wed, 21 Jun 2017 20:16:21 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0132.outbound.protection.outlook.com [104.47.32.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 117CE1292CE; Wed, 21 Jun 2017 20:16:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jabil.onmicrosoft.com;  s=selector1-jabil-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=0EE/DSPCFFS5UIrbNliM7O0qFUes2o8qk8RUzDX3X70=; b=4unVi7jwcVkbSeA+E2ZPApEoFPmpU45dVLqkrn1tv2wp2FGlEWP4MaM0zW23J6WanIw9bNHGUOrD8mMj6LrBBooD5x8I2DAnOHJyHJThTpbxC87F3TrRjU7Kg+UuCXW1wA8NJNT9WsJtoCu+ROxUtPP/a+OyZEXmrYzFHt4WtLM=
Received: from BN3PR0201MB0867.namprd02.prod.outlook.com (10.160.154.13) by BN3PR0201MB0865.namprd02.prod.outlook.com (10.160.154.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1178.14; Thu, 22 Jun 2017 03:16:18 +0000
Received: from BN3PR0201MB0867.namprd02.prod.outlook.com ([10.160.154.13]) by BN3PR0201MB0867.namprd02.prod.outlook.com ([10.160.154.13]) with mapi id 15.01.1178.023; Thu, 22 Jun 2017 03:16:18 +0000
From: Xufeng Liu <Xufeng_Liu@jabil.com>
To: Robert Wilton <rwilton@cisco.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "draft-ietf-teas-yang-te-topo.all@ietf.org" <draft-ietf-teas-yang-te-topo.all@ietf.org>
Subject: RE: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Thread-Topic: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Thread-Index: AQHS1KSedaTR9X/fGEeQz0ke1nZ/sKIh1EjwgA1lWACAASg0QA==
Date: Thu, 22 Jun 2017 03:16:18 +0000
Message-ID: <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com>
In-Reply-To: <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-dg-ref: PG1ldGE+PGF0IG5tPSJib2R5LnR4dCIgcD0iYzpcdXNlcnNceGxpdVxhcHBkYXRhXHJvYW1pbmdcMDlkODQ5YjYtMzJkMy00YTQwLTg1ZWUtNmI4NGJhMjllMzViXG1zZ3NcbXNnLTI2YWUwZGYyLTU2ZjktMTFlNy05YzE3LTE4NWUwZmUzYzQ1Y1xhbWUtdGVzdFwyNmFlMGRmNC01NmY5LTExZTctOWMxNy0xODVlMGZlM2M0NWNib2R5LnR4dCIgc3o9IjYzNDciIHQ9IjEzMTQyNTc0OTc2NzU5ODU4NSIgaD0iaE5UT2NTQ3VPMEZZUlpEVnJyQ1A1Q1pLNzRvPSIgaWQ9IiIgYmw9IjAiIGJvPSIxIi8+PC9tZXRhPg==
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=jabil.com;
x-originating-ip: [72.209.195.86]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0201MB0865; 7:sBCeBOmZu8nIcldVS1I00DtOW9HyDfju0hyUdaKwNi8sW00IQyWE5qI3DihAQSdb6UA/NiTmIezZoMUuAPgfXow6z5l+Yv+H166KCgjoBs5f5ZqmvoBKXw9W4wG7wO1eqyksPCIJtcNL3dS5ivyebhiBdJaBwL22YzYgf2Q1ec/0tcgQ9FCEvPQcsgLAu/2DhWOuESyr/GYzWtbVwBNVDrm31kZmZOTkrD0zoy6eWoxyrSfrxrsydVQ3FzQULg83i2UZ/zZws/BFpKfvUFSMbUQLgYeu96KI/+a3Sf9L6h7nU059GEMI0ZO/bJkgxFmbI9rVKAlB0mfU4uqKvzUTbj2WT1K0e1sOiX3+X2jMbzSF0E+AGWL+8MSzFh9pHL+kYuhjRD0uBUcJJBuXB0DeJz9XrEjYRTXVKPT4xKQVR92xu4akIZ9VVdsqEiiSPdkUSJeLV+3lw/vXNof/JZx30wrUEQnlVxh163D/PXjVAHN+x0StcfaTODLRD/L1kprE2ClRP0Vt87sm3I7YvKCa2XJZDOo3FnvHN+ZJEEgwj7FucI0wp2096FUDhGMm8sd25dh8xUIrRQFbCpyutDTWgOvUL0D7w2mYQUlanpnKf33cAv3wwbWK73hRX+Gnw9sPdzIUe/7Ed58YkMpLhkQFiUbr+wQJtZKAzurIEEcpdfwiqfS8UxgH46EYRM7JwkfJP4ueZOEhZduxIkCnmeN90WZ6cu6t5onualjlGJhtkgl+7KUO5rU+2KD/bV/V5LjvZs+4j/hoNFUS6sp8ArgXnDiZcPnF5i3KY07Xwfjnmvk=
x-ms-office365-filtering-correlation-id: ef4fcb30-7186-4622-bae1-08d4b91d0cee
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500055)(300135000095)(300000501055)(300135300095)(22001)(300000502055)(300135100095)(2017030254075)(48565401081)(300000503055)(300135400095)(201703131423075)(201703031133081)(201702281549075)(300000504055)(300135200095)(300000505055)(300135600095)(300000506048)(300135500095); SRVR:BN3PR0201MB0865; 
x-ms-traffictypediagnostic: BN3PR0201MB0865:
x-microsoft-antispam-prvs: <BN3PR0201MB0865DF75D71E01ABC6A21C3CF1DB0@BN3PR0201MB0865.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(95692535739014)(21534305686606);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(100000703101)(100105400095)(6055026)(6041248)(20161123562025)(20161123564025)(20161123555025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN3PR0201MB0865; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN3PR0201MB0865; 
x-forefront-prvs: 03468CBA43
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39400400002)(39410400002)(39450400003)(39850400002)(39840400002)(24454002)(13464003)(377454003)(76176999)(4326008)(54356999)(55016002)(8676002)(54906002)(50986999)(81166006)(53936002)(2906002)(6306002)(14454004)(102836003)(9686003)(478600001)(39060400002)(6116002)(3846002)(8936002)(305945005)(74316002)(122556002)(25786009)(72206003)(77096006)(99286003)(229853002)(230783001)(189998001)(6506006)(33656002)(66066001)(6436002)(7696004)(2950100002)(5660300001)(2501003)(3660700001)(2900100001)(80792005)(7736002)(3280700002)(38730400002)(6246003)(86362001)(53546010); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0201MB0865; H:BN3PR0201MB0867.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: jabil.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jun 2017 03:16:18.4963 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bc876b21-f134-4c12-a265-8ed26b7f0f3b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0201MB0865
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uGN8bOYvtuiuz2I9ocxuI0hxfuk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 03:16:25 -0000

SGkgUm9iLA0KDQpXaGlsZSB0aGUgdG9vbGluZyBpcyB2ZXJ5IG5pY2UgdG8gaGF2ZSwgZXNwZWNp
YWxseSBmb3Igd3JpdGluZyBuZXcgbW9kZWxzIG9yIGNvbnZlcnRpbmcgbW9kZWxzLCB3ZSBkbyBu
b3QgaGF2ZSB0byB1c2UgaXQgZm9yIGV2ZXJ5IG1vZGVsLiBJdCBzZWVtcyBub3QgbmVjZXNzYXJ5
IHRvIHVzZSB0aGUgdG9vbGluZyBvbiB0aGlzIG1vZGVsIGZvciBub3cuIFdlIGFscmVhZHkga25v
dyB0aGF0IHdlIGNhbiBtYW51YWxseSBjb252ZXJ0IGl0IHRvIE5NREEgc3R5bGUgaWYgbmVlZGVk
Lg0KDQpUaGFua3MsDQotIFh1ZmVuZw0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+
IEZyb206IFJvYmVydCBXaWx0b24gW21haWx0bzpyd2lsdG9uQGNpc2NvLmNvbV0NCj4gU2VudDog
V2VkbmVzZGF5LCBKdW5lIDIxLCAyMDE3IDU6MzQgQU0NCj4gVG86IFh1ZmVuZyBMaXUgPFh1ZmVu
Z19MaXVAamFiaWwuY29tPjsgTWFoZXNoIEpldGhhbmFuZGFuaQ0KPiA8bWpldGhhbmFuZGFuaUBn
bWFpbC5jb20+OyB5YW5nLWRvY3RvcnNAaWV0Zi5vcmcNCj4gQ2M6IGlldGZAaWV0Zi5vcmc7IHRl
YXNAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8uYWxsQGlldGYub3JnDQo+
IFN1YmplY3Q6IFJlOiBbVGVhc10gWWFuZ2RvY3RvcnMgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFm
dC1pZXRmLXRlYXMteWFuZy10ZS10b3BvLQ0KPiAwOA0KPiANCj4gSGkgWHVmZW5nLA0KPiANCj4g
T24gMTIvMDYvMjAxNyAyMjoyOCwgWHVmZW5nIExpdSB3cm90ZToNCj4gPiBIaSBNYWhlc2gsDQo+
ID4NCj4gPiBUaGFuayB5b3UgbXVjaCBmb3IgdGhlIHJldmlldy4gV2UgaGF2ZSBzdWJtaXR0ZWQg
YW4gdXBkYXRlZCBkcmFmdA0KPiAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWll
dGYtdGVhcy15YW5nLXRlLXRvcG8tMDkpIHRvIGFkZHJlc3MgdGhlc2UNCj4gaXNzdWVzLiBNb3Jl
IGRldGFpbGVkIGV4cGxhbmF0aW9ucyBhcmUgcHV0IGJlbG93IGlubGluZS4NCj4gPg0KPiA+IElm
IHRoZSByZXNwb25zZXMgYW5kIHVwZGF0ZXMgYXJlIHNhdGlzZmFjdG9yeSwgd2UgYXJlIHJlYWR5
IGZvciB0aGUgbGFzdCBjYWxsLg0KPiA+DQo+ID4gQmVzdCByZWdhcmRzLA0KPiA+IC0gWHVmZW5n
DQo+ID4NCj4gPj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPj4gRnJvbTogTWFoZXNo
IEpldGhhbmFuZGFuaSBbbWFpbHRvOm1qZXRoYW5hbmRhbmlAZ21haWwuY29tXQ0KPiA+PiBTZW50
OiBXZWRuZXNkYXksIE1heSAyNCwgMjAxNyAxMTo0NCBBTQ0KPiA+PiBUbzogeWFuZy1kb2N0b3Jz
QGlldGYub3JnDQo+ID4+IENjOiBpZXRmQGlldGYub3JnOyB0ZWFzQGlldGYub3JnOw0KPiA+PiBk
cmFmdC1pZXRmLXRlYXMteWFuZy10ZS10b3BvLmFsbEBpZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBZ
YW5nZG9jdG9ycyBsYXN0IGNhbGwgcmV2aWV3IG9mDQo+ID4+IGRyYWZ0LWlldGYtdGVhcy15YW5n
LXRlLXRvcG8tMDgNCj4gPj4NCj4gPj4gUmV2aWV3ZXI6IE1haGVzaCBKZXRoYW5hbmRhbmkNCj4g
Pj4gUmV2aWV3IHJlc3VsdDogUmVhZHkgd2l0aCBJc3N1ZXMNCj4gPj4NCj4gPj4gRG9jdW1lbnQg
cmV2aWV3ZWQ6IGRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8tMDgNCj4gPj4NCj4gPj4gU3Rh
dHVzOiBSZWFkeSB3aXRoIElzc3Vlcw0KPiA+Pg0KPiA+PiBJIGFtIG5vdCBhbiBleHBlcnQgaW4g
VHJhZmZpYyBFbmdpbmVlcmluZy4gVGhpcyByZXZpZXcgaXMgbG9va2luZyBhdA0KPiA+PiB0aGUg
ZHJhZnQgZnJvbSBhIFlBTkcgcGVyc3BlY3RpdmUuIFdpdGggdGhhdCBzYWlkLCBJIGhhdmUgbWFy
a2VkIGl0IGFzIOKAnFJlYWR5DQo+IHdpdGggSXNzdWVz4oCdDQo+ID4+IGJlY2F1c2Ugb2Ygc29t
ZSBvZiB0aGUgcG9pbnRzIGRpc2N1c3NlZCBiZWxvdy4NCj4gPj4NCj4gPj4gU3VtbWFyeToNCj4g
Pj4NCj4gPj4gVGhpcyBkb2N1bWVudCBkZWZpbmVzIGEgWUFORyBkYXRhIG1vZGVsIGZvciByZXBy
ZXNlbnRpbmcsIHJldHJpZXZpbmcNCj4gPj4gYW5kIG1hbmlwdWxhdGluZyBURSBUb3BvbG9naWVz
LiBUaGUgbW9kZWwgc2VydmVzIGFzIGEgYmFzZSBtb2RlbCB0aGF0DQo+ID4+IG90aGVyIHRlY2hu
b2xvZ3kgc3BlY2lmaWMgVEUgVG9wb2xvZ3kgbW9kZWxzIGNhbiBhdWdtZW50Lg0KPiA+Pg0KPiA+
PiBDb21tZW50czoNCj4gPj4NCj4gPj4gQWxtb3N0IGFsbCB0aGUgY29udGFpbmVycyBpbiB0aGUg
bW9kZWwgYXJlIHByZXNlbmNlIGNvbnRhaW5lcnMuIElzDQo+ID4+IHRoZXJlIGEgcmVhc29uIHdo
eSB0aGV5IGhhdmUgdG8gYmUgcHJlc2VuY2UgY29udGFpbmVycz8gTm90ZSwgdGhhdA0KPiA+PiBw
cmVzZW5jZSBjb250YWluZXJzIGFyZSBjb250YWluZXJzIHdob3NlIGV4aXN0ZW5jZSBpdHNlbGYg
cmVwcmVzZW50cw0KPiA+PiBjb25maWd1cmF0aW9uIGRhdGEuIFdoYXQgcGFydGljdWxhciBjb25m
aWd1cmF0aW9uIGRhdGEgaXMgZWFjaCBjb250YWluZXINCj4gcmVwcmVzZW50aW5nIGluIGl0c2Vs
Zj8NCj4gPiBbWHVmZW5nXSBDb250YWluZXJzIHRoYXQgdXNlIOKAnHByZXNlbmNl4oCdIGFyZToN
Cj4gPiAJLSBDb250YWluZXIg4oCcdW5kZXJsYXnigJ0NCj4gPiAJICBvICBXZSBoYXZlIGNoYW5n
ZWQgMTMgb2NjdXJyZW5jZXMgb2Ygc3VjaCBjb250YWluZXJzIHRvIGJlIG5vdA0KPiBwcmVzZW5j
ZSBjb250YWluZXIuDQo+ID4gCS0gQ29udGFpbmVyIOKAnHRl4oCdIHVuZGVyIGF1Z21lbnRhdGlv
bg0KPiA+IAkgIG8gIFRvIGluZGljYXRlIHRoYXQg4oCcVEXigJ0gaXMgZW5hYmxlZCAoY29uZmln
dXJhdGlvbiBkYXRhKQ0KPiA+IAkgIG8gIEFsc28gdXNlZCB0byBkbyBhdWdtZW50YXRpb24uIFRo
ZSDigJxwcmVzZW5jZeKAnSBzdGF0ZW1lbnQgY2FuDQo+IHByZXZlbnQgdGhlIG1hbmRhdG9yeSBj
aGlsZCBmcm9tIGFmZmVjdGluZyBhdWdtZW50ZWQgYmFzZSBtb2RlbC4NCj4gPiAJLSAvbnc6bmV0
d29ya3Mvbnc6bmV0d29yay9udzpuZXR3b3JrLXR5cGVzL3RlLXRvcG9sb2d5IQ0KPiA+IAkgIG8g
IEEgbWVjaGFuaXNtIHJlcXVpcmVkIGJ5IEkyUlMgdG9wb2xvZ3kgbW9kZWwgdG8gc3BlY2lmeSB0
aGUNCj4gdG9wb2xvZ3kgdHlwZS4NCj4gPg0KPiA+PiBJdCBpcyBkaWZmaWN1bHQgdG8gY28tcmVs
YXRlIHRoZSBkaWFncmFtIHdpdGggdGhlIG1vZGVsIGl0c2VsZg0KPiA+PiBiZWNhdXNlIG9mIGRp
ZmZlcmVudCB0ZXJtcyBiZWluZyB1c2VkIHRvIGRlZmluZSBkaWZmZXJlbnQgcGFydHMgb2YgdGhl
IG1vZGVsLg0KPiA+PiBUaGVyZSBpcyDigJxURSBUb3BvbG9neSBNb2RlbOKAnSBhbmQgdGhlbiB0
aGVyZSBpcyDigJxHZW5lcmljIFRFIFRvcG9sb2d5DQo+IE1vZGVs4oCdLg0KPiA+PiBBcmUgdGhl
c2Ugb25lIGFuZCB0aGUgc2FtZSBtb2RlbHM/IElmIHNvLCBhIGNvbW1vbiB0ZXJtIGZvciBib3Ro
IG9mDQo+ID4+IHRoZW0gd291bGQgYmUgaGVscGZ1bC4NCj4gPiBbWHVmZW5nXSBZZXMuIFRoZXNl
IHR3byB0ZXJtcyBhcmUgdGhlIHNhbWUuIEZpZ3VyZSAxMiwgRmlndXJlIDEzLCBhbmQgcmVsZXZh
bnQNCj4gZGVzY3JpcHRpb25zIGhhdmUgYmVlbiB1cGRhdGVkIHRvIG1ha2UgdGhlIGRvY3VtZW50
IGNvbnNpc3RlbnQuDQo+ID4NCj4gPj4gVGhlcmUgaXMgZXh0ZW5zaXZlIHVzZSBvZiBncm91cGlu
Z3MgaW4gdGhlIGRvY3VtZW50LiBIb3dldmVyLCBub3QgYWxsDQo+ID4+IGluc3RhbmNlcyBvZiBn
cm91cGluZ3MgYXJlIHVzZWQgbXVsdGlwbGUgbnVtYmVyIG9mIHRpbWVzLiBXaGVyZSB0aGV5DQo+
ID4+IGFyZSBub3QgYmVpbmcgcmVwZWF0ZWQsIGl0IHdvdWxkIGJlIGJldHRlciB0byBtb3ZlIHRo
ZSBncm91cGluZw0KPiA+PiBkaXJlY3RseSB3aGVyZSB0aGUgdXNlcyBzdGF0ZW1lbnQgcmVzaWRl
cy4gQ2FzZSBpbiBwb2ludCB0aGUgZ3JvdXBpbmcNCj4gY29ubmVjdGl2aXR5LWxhYmVsLXJlc3Ry
aWN0aW9uLWxpc3QuDQo+ID4gW1h1ZmVuZ10gV2UgaGF2ZSByZW1vdmVkIHRoZSBmb2xsb3dpbmcg
Z3JvdXBpbmdzDQo+ID4gICAgICB0ZS1saW5rLWF1Z21lbnQNCj4gPiAgICAgIHRlLW5vZGUtYXVn
bWVudA0KPiA+ICAgICAgdGUtdGVybWluYXRpb24tcG9pbnQtYXVnbWVudA0KPiA+ICAgICAgdGUt
dG9wb2xvZ2llcy1hdWdtZW50DQo+ID4gICAgICB0ZS10b3BvbG9neS1hdWdtZW50DQo+ID4gICAg
ICB0ZS1saW5rLXN0YXRlLXVuZGVybGF5LWF0dHJpYnV0ZXMNCj4gPiAgICAgIHRlLW5vZGUtc3Rh
dGUtZGVyaXZlZC1ub3RpZmljYXRpb24NCj4gPiAgICAgIHRlLXRvcG9sb2d5LXR5cGUNCj4gPg0K
PiA+IFRoZSByZW1haW5pbmcgZ3JvdXBpbmdzIGhhdmUgYmVlbiBrZXB0IHNvIHRoYXQgd2UgY2Fu
Og0KPiA+IAktIFNoYXJlIHRoZSBncm91cGluZ3MgaW4gdGhpcyBtb2RlbA0KPiA+IAktIFByZXBh
cmUgdG8gYmUgc2hhcmVkIGJ5IGEgbW9kZWwgYXVnbWVudGluZyB0aGlzIG1vZGVsDQo+ID4gCS0g
UHJldmVudCBhIGdyb3VwaW5nIG9yIGNvbmZpZ3VyYXRpb24gc2VjdGlvbiBmcm9tIGJlaW5nIHRv
byBsb25nDQo+ID4gCS0gSW1wcm92ZSByZWFkYWJpbGl0eQ0KPiA+DQo+ID4+IFRoZSBzcGxpdCBi
ZXR3ZWVuIGNvbmZpZyBhbmQgc3RhdGUgY29udGFpbmVycyBkb2VzIG5vdCBzZWVtIHRvIGZvbGxv
dw0KPiA+PiBhbnkgcGFydGljdWxhciBwYXR0ZXJuLg0KPiA+IFtYdWZlbmddIFRoZSBwYXR0ZXJu
IGlzIGNsZWFyOg0KPiA+IEZvciBlYWNoIG1hbmFnZWFibGUgZW50aXR5IChvYmplY3QpLCB0aGVy
ZSBpcyBhIGNvbmZpZyBjb250YWluZXIgYW5kIHN0YXRlDQo+IGNvbnRhaW5lci4gVGhlIGNvbmZp
Z3VyYWJsZSBwcm9wZXJ0aWVzIGdvIGludG8gdGhlIGNvbmZpZyBjb250YWluZXIgYW5kIHN0YXRl
DQo+IHByb3BlcnRpZXMgZ28gaW50byB0aGUgc3RhdGUgY29udGFpbmVyLiBTdWNoIG9iamVjdHMg
YXJlIGlkZW50aWZpZWQgYnkgYSBsaXN0IGl0ZW0NCj4gb3IgYSBwcmVzZW5jZSBjb250YWluZXIg
c28gdGhhdCB0aGUg4oCcY3JlYXRl4oCdLCDigJxkZWxldGXigJ0sIGFuZCDigJxtb2RpZnnigJ0g
b3BlcmF0aW9ucw0KPiBjYW4gYmUgcGVyZm9ybWVkIG9uIHRoZW0uIFRoZSBub24tcHJlc2VuY2Ug
Y29udGFpbmVycyBkbyBub3QgcmVwcmVzZW50DQo+IGNvbmZpZ3VyYXRpb24gZGF0YSBzbyB0aGV5
IGRvIG5vdCBpbnRyb2R1Y2Ugc3VjaCBvYmplY3RzLg0KPiA+DQo+ID4+IEl0IGlzIG5laXRoZXIg
YSB0b3AgbGV2ZWwgc3BsaXQsIGFzIGlzIHRoZSBjYXNlIHdpdGggZXhpc3RpbmcgSUVURg0KPiA+
PiBtb2RlbHMsDQo+ID4gW1h1ZmVuZ10gV2UgY291bGQgbm90IGRvIHRvcCBsZXZlbCBzcGxpdCBi
ZWNhdXNlIHRoZSBiYXNlIEkyUlMgbmV0d29yaw0KPiB0b3BvbG9neSBtb2RlbCAoaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtaTJycy15YW5nLW5ldHdvcmstdG9wby0NCj4g
MTIpIHRoYXQgd2UgYXVnbWVudCBkb2VzIG5vdCBoYXZlIHRoZSB0b3AtbGV2ZWwgc3BsaXQgKGZv
ciBpdHMgb3duIHJlYXNvbnMpLg0KPiA+DQo+ID4+IG5vciBkbyB0aGV5IGZvbGxvdyB0aGUgT3Bl
bkNvbmZpZyBzdHlsZSBvZiBzcGxpdHRpbmcgY29uZmlnIGFuZCBzdGF0ZQ0KPiA+PiB1bmRlciBl
YWNoIHJlbGV2YW50IGxlYWYsDQo+ID4gW1h1ZmVuZ10gVGhlIHBhdHRlcm4gaXMgY29uc2lzdGVu
dCB3aXRoIHRoaXMgc3R5bGUgaW4gcHJpbmNpcGxlLCB3aXRoIHNvbWUNCj4gYWRqdXN0bWVudHMg
dG8gZml0IHRvIG91ciBtdWx0aXBsZSBsZXZlbHMgb2YgaGllcmFyY2h5Lg0KPiBUaGlzIGlzIGVm
ZmVjdGl2ZWx5IGEgbmV3IGZvcnRoIHN0eWxlIG9mIFlBTkcgbW9kZWxzIHRoYXQgaXMgbm90IGNv
bnNpc3RlbnQgd2l0aA0KPiBhbnkgb2YgdGhlIHRocmVlIGV4aXN0aW5nIHN0eWxlcywgaS5lLjoN
Cj4gICAtIEN1cnJlbnQgSUVURiBjb25maWcvc3RhdGUgc3BsaXQgbW9kZWwgc3R5bGUNCj4gICAt
IE5NREEgY29tYmluZWQgY29uZmlnL3N0YXRlIHRyZWUNCj4gICAtIE9wZW5Db25maWcgc3BsaXQg
Y29uZmlnL3N0YXRlIGNvbnRhaW5lcnMgaW1tZWRpYXRlbHkgYWJvdmUgdGhlIGNvbmZpZyB0cnVl
DQo+IGxlYXZlcy4NCj4gDQo+IFRvb2xpbmcgdGhhdCBpdCBkZXNpZ25lZCB0byB3b3JrIHdpdGgg
T3BlbkNvbmZpZyBtb2RlbHMgd2lsbCBuZWVkDQo+IGN1c3RvbWl6YXRpb24gdG8gd29yayB3aXRo
IHRoZXNlIFRFIG1vZGVscyBiZWNhdXNlIHRoZSBjb25maWcvc3RhdGUNCj4gY29udGFpbmVycyB3
aWxsIG5vdCBiZSB3aGVyZSB0aGUgdG9vbGluZyBleHBlY3RzIHRoZW0gdG8gYmUuDQo+IA0KPiBU
aGFua3MsDQo+IFJvYg0KDQo=


From nobody Wed Jun 21 23:41:48 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 D0D7F126557; Wed, 21 Jun 2017 23:41:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uWoqj2Nx1xVf; Wed, 21 Jun 2017 23:41:45 -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 8A91F120227; Wed, 21 Jun 2017 23:41:45 -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 v5M6fg53010861; Thu, 22 Jun 2017 08:41:42 +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 3wtX6t2MQ9z3ZWV; Thu, 22 Jun 2017 08:41:42 +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-ietf-sacm-requirements-15.txt> (Security Automation and Continuous Monitoring (SACM) Requirements) to Informational RFC
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <149547765333.16443.10840963581238733682.idtracker@ietfa.amsl.com>
Date: Thu, 22 Jun 2017 08:41:41 +0200
Cc: draft-ietf-sacm-requirements@ietf.org
X-Mao-Original-Outgoing-Id: 519806501.633386-824e48038a841f46c1f3176a7c8ad8c4
Content-Transfer-Encoding: quoted-printable
Message-Id: <79A273B7-56C5-438D-BA99-976537813BC3@tzi.org>
References: <149547765333.16443.10840963581238733682.idtracker@ietfa.amsl.com>
To: IETF <ietf@ietf.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ec3L5Pgg0eosx0oEivWg7qVJVnQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 06:41:48 -0000

Quote:

   Multiple data models, protocols, and transports may be employed in a
   SACM environment.  A SACM transport protocol is one that runs on top
   of L3 protocols such as TCP/IP or L4 protocols such as HTTP, carries
   operations (requests / responses), and moves data.

Please expand abbreviations =E2=80=9CL3=E2=80=9D and =E2=80=9CL4=E2=80=9D =
on first (and apparently only) use.
Preferably do not use these abbreviations here at all as they are =
customarily understood to stand for =E2=80=9CInternet Layer=E2=80=9D and =
=E2=80=9CTransport Layer=E2=80=9D as defined in RFC1122 Section 1.1.3 =
(while using OSI layer numbers purely for convenience).  This common =
meaning doesn=E2=80=99t appear to be meant here.

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


From nobody Thu Jun 22 02:23:42 2017
Return-Path: <rwilton@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 D5BDB129405; Thu, 22 Jun 2017 02:23:33 -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 a7ZYlDSdzheP; Thu, 22 Jun 2017 02:23:31 -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 CEA4D128B51; Thu, 22 Jun 2017 02:23:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8061; q=dns/txt; s=iport; t=1498123402; x=1499333002; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=2qpl5Dg2c0m4dCo9rZm5VnuGbw+/L0pc001uqbpPd8U=; b=JDZkerYKTYE3MuQN8DSfzmoFtDFwZJdhU04vESX22S1w55HX97z+Ca3W zFMHtxiE2CAGnI5Uy/fTQABZtejO4aWIJmVyeY1hY+2Kv60Cp1mwgzb4H ci8eO75KR9tnT7DllHLrOO4SJJeCGUcT9nTaK5XxF+E5P4iXfSjjWXD/y Q=;
X-IronPort-AV: E=Sophos;i="5.39,372,1493683200"; d="scan'208";a="653782631"
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; 22 Jun 2017 09:23:20 +0000
Received: from [10.63.23.55] (dhcp-ensft1-uk-vla370-10-63-23-55.cisco.com [10.63.23.55]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v5M9NJ72018339; Thu, 22 Jun 2017 09:23:20 GMT
Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
To: Xufeng Liu <Xufeng_Liu@jabil.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "draft-ietf-teas-yang-te-topo.all@ietf.org" <draft-ietf-teas-yang-te-topo.all@ietf.org>, "Benoit Claise (bclaise)" <bclaise@cisco.com>
From: Robert Wilton <rwilton@cisco.com>
Message-ID: <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com>
Date: Thu, 22 Jun 2017 10:23:19 +0100
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: <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/N2gGBQRRML6EvVlRX3K0snl6q6I>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 09:23:34 -0000

Hi Xufeng,

OK, by tooling, I don't mean the pyang plugins that I have been working 
on to convert between different types of models.  As you aware, the TE 
YANG models can easily be converted to NMDA style since I have already 
done it (https://github.com/rgwilton/ietf-models-to-combined).

My comment actually relates to the fact the structure used by TE YANG 
modules don't match any other YANG modules - they are using their own 
unique style of structure.

Today, there are three common styles of modules:
(1) IETF style split config/state trees (e.g. ietf-interfaces).
(2) IETF NMDA style combined config/state trees (i.e. where all IETF 
modules are heading to).
(3) OpenConfig style modules with the config/state containers 
immediately above the config leaves.

Tooling is likely to be optimized to work with these model structures, 
but the TE modules do not fit into any of the three styles above.  They 
are a yet another OpenConfig-like style, but that is different enough 
that tooling that is designed to work with OpenConfig style YANG modules 
would likely not work with the TE YANG modules.

Specifically, for clients that expecting to work with an OpenConfig 
style YANG module, then if it knows the path to config leaf X, then they 
would expect the applied config value to be available at the path 
"../state/X".  But, this doesn't hold for the structure being used in 
the TE YANG models.

I believe strongly that the models being produced by organizations 
should be structures in a consistent way, hence why I think that the 
published standard version of the TE YANG modules should immediately 
align to the NMDA style.

Thanks,
Rob


On 22/06/2017 04:16, Xufeng Liu wrote:
> Hi Rob,
>
> While the tooling is very nice to have, especially for writing new models or converting models, we do not have to use it for every model. It seems not necessary to use the tooling on this model for now. We already know that we can manually convert it to NMDA style if needed.
>
> Thanks,
> - Xufeng
>
>> -----Original Message-----
>> From: Robert Wilton [mailto:rwilton@cisco.com]
>> Sent: Wednesday, June 21, 2017 5:34 AM
>> To: Xufeng Liu <Xufeng_Liu@jabil.com>; Mahesh Jethanandani
>> <mjethanandani@gmail.com>; yang-doctors@ietf.org
>> Cc: ietf@ietf.org; teas@ietf.org; draft-ietf-teas-yang-te-topo.all@ietf.org
>> Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-
>> 08
>>
>> Hi Xufeng,
>>
>> On 12/06/2017 22:28, Xufeng Liu wrote:
>>> Hi Mahesh,
>>>
>>> Thank you much for the review. We have submitted an updated draft
>> (https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09) to address these
>> issues. More detailed explanations are put below inline.
>>> If the responses and updates are satisfactory, we are ready for the last call.
>>>
>>> Best regards,
>>> - Xufeng
>>>
>>>> -----Original Message-----
>>>> From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com]
>>>> Sent: Wednesday, May 24, 2017 11:44 AM
>>>> 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
>>>>
>>>> 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?
>>> [Xufeng] Containers that use “presence” are:
>>> 	- Container “underlay”
>>> 	  o  We have changed 13 occurrences of such containers to be not
>> presence container.
>>> 	- Container “te” under augmentation
>>> 	  o  To indicate that “TE” is enabled (configuration data)
>>> 	  o  Also used to do augmentation. The “presence” statement can
>> prevent the mandatory child from affecting augmented base model.
>>> 	- /nw:networks/nw:network/nw:network-types/te-topology!
>>> 	  o  A mechanism required by I2RS topology model to specify the
>> topology type.
>>>> 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.
>>> [Xufeng] Yes. These two terms are the same. Figure 12, Figure 13, and relevant
>> descriptions have been updated to make the document consistent.
>>>> 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.
>>> [Xufeng] We have removed the following groupings
>>>       te-link-augment
>>>       te-node-augment
>>>       te-termination-point-augment
>>>       te-topologies-augment
>>>       te-topology-augment
>>>       te-link-state-underlay-attributes
>>>       te-node-state-derived-notification
>>>       te-topology-type
>>>
>>> The remaining groupings have been kept so that we can:
>>> 	- Share the groupings in this model
>>> 	- Prepare to be shared by a model augmenting this model
>>> 	- Prevent a grouping or configuration section from being too long
>>> 	- Improve readability
>>>
>>>> The split between config and state containers does not seem to follow
>>>> any particular pattern.
>>> [Xufeng] The pattern is clear:
>>> For each manageable entity (object), there is a config container and state
>> container. The configurable properties go into the config container and state
>> properties go into the state container. Such objects are identified by a list item
>> or a presence container so that the “create”, “delete”, and “modify” operations
>> can be performed on them. The non-presence containers do not represent
>> configuration data so they do not introduce such objects.
>>>> It is neither a top level split, as is the case with existing IETF
>>>> models,
>>> [Xufeng] We could not do top level split because the base I2RS network
>> topology model (https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-
>> 12) that we augment does not have the top-level split (for its own reasons).
>>>> nor do they follow the OpenConfig style of splitting config and state
>>>> under each relevant leaf,
>>> [Xufeng] The pattern is consistent with this style in principle, with some
>> adjustments to fit to our multiple levels of hierarchy.
>> This is effectively a new forth style of YANG models that is not consistent with
>> any of the three existing styles, i.e.:
>>    - Current IETF config/state split model style
>>    - NMDA combined config/state tree
>>    - OpenConfig split config/state containers immediately above the config true
>> leaves.
>>
>> Tooling that it designed to work with OpenConfig models will need
>> customization to work with these TE models because the config/state
>> containers will not be where the tooling expects them to be.
>>
>> Thanks,
>> Rob


From nobody Thu Jun 22 03:12:10 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 870D51293F2; Thu, 22 Jun 2017 03:11:52 -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 Ikab_ROoE8XI; Thu, 22 Jun 2017 03:11:50 -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 96C80128D64; Thu, 22 Jun 2017 03:11:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8754; q=dns/txt; s=iport; t=1498126310; x=1499335910; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=3a4A7y3aty+5liNIrUNcCShb8lEaC6J8xFZ7QfRbv8M=; b=Jj7PugFFJiClfjB7I1NKfh1w0iGj1/A+KVYyAeIbZKXx7PXACemn2Lm7 Qwr0wPagZ7uI1YdTLAoZTNhSUsP/WsUOjk0/JcMFgpfPE7LJ30lgGCSQI wAZj/dml94B2FmaB60w/XhDs/rGk11FFL3jli+Okch5lya5L9zORoWZtR 4=;
X-IronPort-AV: E=Sophos;i="5.39,372,1493683200"; d="scan'208";a="695327914"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Jun 2017 10:11:48 +0000
Received: from [10.55.221.38] (ams-bclaise-nitro5.cisco.com [10.55.221.38]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v5MABliK029933; Thu, 22 Jun 2017 10:11:47 GMT
Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
To: Robert Wilton <rwilton@cisco.com>, Xufeng Liu <Xufeng_Liu@jabil.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "draft-ietf-teas-yang-te-topo.all@ietf.org" <draft-ietf-teas-yang-te-topo.all@ietf.org>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com>
Date: Thu, 22 Jun 2017 12:11:43 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Tz4HhvH2xQAo5pLJypDyvdmOvAw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 10:11:53 -0000

Dear draft-ietf-teas-yang-te-topo authors,
> Hi Xufeng,
>
> OK, by tooling, I don't mean the pyang plugins that I have been 
> working on to convert between different types of models.  As you 
> aware, the TE YANG models can easily be converted to NMDA style since 
> I have already done it 
> (https://github.com/rgwilton/ietf-models-to-combined).
>
> My comment actually relates to the fact the structure used by TE YANG 
> modules don't match any other YANG modules - they are using their own 
> unique style of structure.
This is an important issue to resolve.
>
> Today, there are three common styles of modules:
> (1) IETF style split config/state trees (e.g. ietf-interfaces).
> (2) IETF NMDA style combined config/state trees (i.e. where all IETF 
> modules are heading to).
> (3) OpenConfig style modules with the config/state containers 
> immediately above the config leaves.
>
> Tooling is likely to be optimized to work with these model structures, 
> but the TE modules do not fit into any of the three styles above.  
> They are a yet another OpenConfig-like style, but that is different 
> enough that tooling that is designed to work with OpenConfig style 
> YANG modules would likely not work with the TE YANG modules.
>
> Specifically, for clients that expecting to work with an OpenConfig 
> style YANG module, then if it knows the path to config leaf X, then 
> they would expect the applied config value to be available at the path 
> "../state/X".  But, this doesn't hold for the structure being used in 
> the TE YANG models.
>
> I believe strongly that the models being produced by organizations 
> should be structures in a consistent way, hence why I think that the 
> published standard version of the TE YANG modules should immediately 
> align to the NMDA style.
Agreed.
Here is the OPS and RTG AD message: 
https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html

I understand that the I2RS topology YANG modules will be improved to the 
NMDA style.

Regards, Benoit
>
> Thanks,
> Rob
>
>
> On 22/06/2017 04:16, Xufeng Liu wrote:
>> Hi Rob,
>>
>> While the tooling is very nice to have, especially for writing new 
>> models or converting models, we do not have to use it for every 
>> model. It seems not necessary to use the tooling on this model for 
>> now. We already know that we can manually convert it to NMDA style if 
>> needed.
>>
>> Thanks,
>> - Xufeng
>>
>>> -----Original Message-----
>>> From: Robert Wilton [mailto:rwilton@cisco.com]
>>> Sent: Wednesday, June 21, 2017 5:34 AM
>>> To: Xufeng Liu <Xufeng_Liu@jabil.com>; Mahesh Jethanandani
>>> <mjethanandani@gmail.com>; yang-doctors@ietf.org
>>> Cc: ietf@ietf.org; teas@ietf.org; 
>>> draft-ietf-teas-yang-te-topo.all@ietf.org
>>> Subject: Re: [Teas] Yangdoctors last call review of 
>>> draft-ietf-teas-yang-te-topo-
>>> 08
>>>
>>> Hi Xufeng,
>>>
>>> On 12/06/2017 22:28, Xufeng Liu wrote:
>>>> Hi Mahesh,
>>>>
>>>> Thank you much for the review. We have submitted an updated draft
>>> (https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09) to 
>>> address these
>>> issues. More detailed explanations are put below inline.
>>>> If the responses and updates are satisfactory, we are ready for the 
>>>> last call.
>>>>
>>>> Best regards,
>>>> - Xufeng
>>>>
>>>>> -----Original Message-----
>>>>> From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com]
>>>>> Sent: Wednesday, May 24, 2017 11:44 AM
>>>>> 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
>>>>>
>>>>> 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?
>>>> [Xufeng] Containers that use “presence” are:
>>>>     - Container “underlay”
>>>>       o  We have changed 13 occurrences of such containers to be not
>>> presence container.
>>>>     - Container “te” under augmentation
>>>>       o  To indicate that “TE” is enabled (configuration data)
>>>>       o  Also used to do augmentation. The “presence” statement can
>>> prevent the mandatory child from affecting augmented base model.
>>>>     - /nw:networks/nw:network/nw:network-types/te-topology!
>>>>       o  A mechanism required by I2RS topology model to specify the
>>> topology type.
>>>>> 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.
>>>> [Xufeng] Yes. These two terms are the same. Figure 12, Figure 13, 
>>>> and relevant
>>> descriptions have been updated to make the document consistent.
>>>>> 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.
>>>> [Xufeng] We have removed the following groupings
>>>>       te-link-augment
>>>>       te-node-augment
>>>>       te-termination-point-augment
>>>>       te-topologies-augment
>>>>       te-topology-augment
>>>>       te-link-state-underlay-attributes
>>>>       te-node-state-derived-notification
>>>>       te-topology-type
>>>>
>>>> The remaining groupings have been kept so that we can:
>>>>     - Share the groupings in this model
>>>>     - Prepare to be shared by a model augmenting this model
>>>>     - Prevent a grouping or configuration section from being too long
>>>>     - Improve readability
>>>>
>>>>> The split between config and state containers does not seem to follow
>>>>> any particular pattern.
>>>> [Xufeng] The pattern is clear:
>>>> For each manageable entity (object), there is a config container 
>>>> and state
>>> container. The configurable properties go into the config container 
>>> and state
>>> properties go into the state container. Such objects are identified 
>>> by a list item
>>> or a presence container so that the “create”, “delete”, and “modify” 
>>> operations
>>> can be performed on them. The non-presence containers do not represent
>>> configuration data so they do not introduce such objects.
>>>>> It is neither a top level split, as is the case with existing IETF
>>>>> models,
>>>> [Xufeng] We could not do top level split because the base I2RS network
>>> topology model 
>>> (https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-
>>> 12) that we augment does not have the top-level split (for its own 
>>> reasons).
>>>>> nor do they follow the OpenConfig style of splitting config and state
>>>>> under each relevant leaf,
>>>> [Xufeng] The pattern is consistent with this style in principle, 
>>>> with some
>>> adjustments to fit to our multiple levels of hierarchy.
>>> This is effectively a new forth style of YANG models that is not 
>>> consistent with
>>> any of the three existing styles, i.e.:
>>>    - Current IETF config/state split model style
>>>    - NMDA combined config/state tree
>>>    - OpenConfig split config/state containers immediately above the 
>>> config true
>>> leaves.
>>>
>>> Tooling that it designed to work with OpenConfig models will need
>>> customization to work with these TE models because the config/state
>>> containers will not be where the tooling expects them to be.
>>>
>>> Thanks,
>>> Rob
>
> .
>


From nobody Thu Jun 22 05:44:55 2017
Return-Path: <mfidelman@meetinghouse.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97A8612943B for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 05:44:53 -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, 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 b5d0ANWWFw_p for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 05:44:45 -0700 (PDT)
Received: from server1.neighborhoods.net (server1.neighborhoods.net [207.154.13.48]) by ietfa.amsl.com (Postfix) with ESMTP id 867B4129404 for <ietf@ietf.org>; Thu, 22 Jun 2017 05:44:45 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by server1.neighborhoods.net (Postfix) with ESMTP id E115DCC418 for <ietf@ietf.org>; Thu, 22 Jun 2017 08:44:44 -0400 (EDT)
X-Virus-Scanned: by amavisd-new-2.6.2 (20081215) (Debian) at neighborhoods.net
Received: from server1.neighborhoods.net ([127.0.0.1]) by localhost (server1.neighborhoods.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 01ImZ83Ni4Cx for <ietf@ietf.org>; Thu, 22 Jun 2017 08:44:43 -0400 (EDT)
Received: from Miless-MBP.fios-router.home (pool-108-26-180-132.bstnma.fios.verizon.net [108.26.180.132]) by server1.neighborhoods.net (Postfix) with ESMTPSA id B8112CC3B7 for <ietf@ietf.org>; Thu, 22 Jun 2017 08:44:43 -0400 (EDT)
To: ietf@ietf.org
From: Miles Fidelman <mfidelman@meetinghouse.net>
Subject: is there a good email list / wiki for folks involved in protocol design?
Message-ID: <0d6283c7-3038-a9f2-6b17-916da8c4494e@meetinghouse.net>
Date: Thu, 22 Jun 2017 08:44:43 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
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/Op6BoCUBNmHV7yZoLwgmVbGjagg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 12:44:54 -0000

Hi Folks,

This would seem to be the right place to ask.

There's a wonderful blog/wiki/community-of-interest (Drupal site, 
actually) at lambda-the-ultimate.org that seems to have become a focal 
point for folks involved in the theory & practice of programming 
language design (billed as "The Programming Language Weblog").

I've been wondering if there's any kind of a similar site/community 
organized around protocol design.  Anybody know of one?

Context:  I've been thinking about writing a book on the history of 
protocol adoption - how & why some protocols have become ubiquitous - 
with a particular focus on how & why new functionality keeps showing up 
as APIs, SaaS, SOAs, and now micro-services. (Working title: Back to 
Walled Gardens).  There's lots of activity, email lists, etc. around API 
and micro-service development, but I can't seem to find much on the 
theory & practice of protocol development (is it that are spread around 
more focused on specific problems, say in specific IETF working groups - 
to the detriment of a more general community-of-interest?).

Thanks,

Miles Fidelman

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


From nobody Thu Jun 22 06:09:36 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 3680F1243F3 for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 06:09:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ND6BskV9ekmZ for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 06:09:32 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:1829::130]) by ietfa.amsl.com (Postfix) with ESMTP id 916C5128B8F for <ietf@ietf.org>; Thu, 22 Jun 2017 06:09:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id AB9672CFFA; Thu, 22 Jun 2017 16:09:31 +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 rMdwwugKeqgb; Thu, 22 Jun 2017 16:09:31 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:1829::130]) by p130.piuha.net (Postfix) with ESMTP id 3293B2CFB5; Thu, 22 Jun 2017 16:09:31 +0300 (EEST) (envelope-from jari.arkko@piuha.net)
Subject: Re: Saturday as start day
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: multipart/signed; boundary="Apple-Mail=_48D2AF18-0D7B-4C8A-A5B0-BEC613EBC10D"; protocol="application/pgp-signature"; micalg=pgp-sha512
X-Pgp-Agent: GPGMail
From: Jari Arkko <jari.arkko@piuha.net>
In-Reply-To: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in>
Date: Thu, 22 Jun 2017 16:09:29 +0300
Cc: IETF Discussion <ietf@ietf.org>
Message-Id: <92518741-DC0C-4180-A31F-1ACB617F75E2@piuha.net>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in>
To: Alissa Cooper <alissa@cooperw.in>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/S3mTTCl45ykC-yWvWTZHuZpjkH0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 13:09:35 -0000

--Apple-Mail=_48D2AF18-0D7B-4C8A-A5B0-BEC613EBC10D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

I think it is a good move, closest description of reality. Do it.

As for the other topics raised later in this thread, the 7 day
meeting has been tiresome at least for me. I don=92t think we
can effectively work for 7 long days. Take a day off when your
most important working group is not meeting. If you
find that you=92re scheduled to do something in every slot,
you are probably either doing something wrong or your
title is an area director :-)

Jari


--Apple-Mail=_48D2AF18-0D7B-4C8A-A5B0-BEC613EBC10D
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

iQIcBAEBCgAGBQJZS8GKAAoJEM80gCTQU46qByEP/3iHyFukteRXPFyoUp1mUPpc
Hc1eK/UPQXmrq81SV89yVdV9HbCPM8ZrJ7DT+HkG+V5j7iNhVUvflG6AAEmJcSIK
+eC0Y9RXWlU5AfY1ufVL/q9BAjZYvnBqkswrimdqDxtiHJZXg+ohZUUhwUHgLwNS
6Lj6q8MUh9ufX7v34PVZAWp1LEWw0LXhz3Knn+3bJPinmYvkjXy55rfmYF0RgMO1
Z7eGRKKB90GmapvvQ9GMJlc5WMMbZywxk6NEPafyYn7leDqLVxpymKp85BTmoO7m
X3tmr5vEC+BFkVfah990NN6i2B9PCmsDVzFwa5oL7SZhVk3ztDTNDAiTTKwslqcW
2Ji0TwRp7/veVKfwjBbLx90/SUXdPJOHuZOThUAaEGeW1CFDMONjbdfMAqInQxPo
1OyMw1xPlkej2Q/b4t7vfAQ3hg+mm00G16hsf8avpGfG7tlmCwYnkasZfEuDLsLR
bu1wKAD5LbezyBbLm66fxw9CGKDB03+Dp/7uIcz77dkSsq1lwXecbOsowakRYklE
oBBUo8A90R8OB+V9nKjzUUrbEHIFKM4XMYhdr/CE3mqQSyl28K25O+/bwzjkW1V4
vjtHd2WV5KDpCwUfdD3yYqH5zwvGUtHIVjUgM5ctHTLX2BTJugP0R5UgMciF9wkA
hISibBGDV9Yn4T2DVmL4
=oTAg
-----END PGP SIGNATURE-----

--Apple-Mail=_48D2AF18-0D7B-4C8A-A5B0-BEC613EBC10D--


From nobody Thu Jun 22 06:29:43 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 2AFC3129438; Thu, 22 Jun 2017 06:29:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <rtg-dir@ietf.org>
Cc: spring@ietf.org, ietf@ietf.org, draft-ietf-spring-oam-usecase.all@ietf.org
Subject: Rtgdir last call review of draft-ietf-spring-oam-usecase-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149813817013.30481.17524594111387704082@ietfa.amsl.com>
Date: Thu, 22 Jun 2017 06:29:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8RLdmGj2H5Xyhq9p_wug4w29Xw0>
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, 22 Jun 2017 13:29:30 -0000

Reviewer: Joel Halpern
Review result: Has Nits

This is a rtg-dir requested review.

Summary: Ready for publication as an Informational RFC with some minor items
that should be considered.

Major: N/A

Minor:
    The introduction treats having a single centralized monitoring system as an
    unalloyed positive.  To set context properly, it would seem more
    appropriate to note that many operators find such central systems useful,
    and the approach described here enables that when desired.

    The reference in the introduction to IGP topology discovery is very
    confusing. "Adding MPLS topology awareness to an IGP speaking device hence
    enables a simple and scalable data plane based monitoring mechanism."  As
    noted later in the document, link-state IGPs provide topology awareness. 
    So what is this part of the introduction trying to say?  (Side-note, not
    all IGPs are link state, although the applicability of Babel or RIP to MPLS
    Segment Routing is clearly outside the scope of this document.)

    In section 5.1 in discussing path trace the reference is to RFC 4379 which
    is a clear source for path trace.  However, the text refers to "tree
    trace".  While that may have become a common phrase for the usage, it is
    not used in RFC 4379.  The term should either be explain, include a
    suitable reference, or not be used.

   In section 5.3 on fault isolation, the text notes that the only difference
   between the test which succeeds and that which fails is the difference the
   the adjacency SID.  The text then goes on to say "Assuming the second probe
   has been routed correctly, the fault must have been occurring in R2 which
   didn't forward the packet to the interface identified by its Adjacency SID
   663."  That does not follow.  If the link as failed in an undetected fashion
   (either in one direction or both), R2 would be functioning fine and the
   symptom would be the same.  Remotely detecting the difference between R2
   failing to forward and the link not working seems a much harder task.

    The claim that the PMS can / should (intent is ambiguous) notify the router
    when it detects a path failure raises a number of issues.   It is not at
    all clear what the router would do with the notification.  (e.g. If it
    removed the link from service, then future monitoring would not be able to
    detect that the link was working.)  Either this needs to become a
    significantly larger section, or (more likely) the text needs to be removed.

Editorial:
    Chapter 7 is titled dealing with non-SR environments.  Which makes sense. 
    The text then switches to using "pre-SR" instead of "non-SR".  I would
    recommend that all uses of "pre-SR" be changed to "non-SR".


From nobody Thu Jun 22 06:44:18 2017
Return-Path: <Xufeng_Liu@jabil.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A41F41292AE; Thu, 22 Jun 2017 06:44:10 -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=jabil.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 7RlybPklPjpd; Thu, 22 Jun 2017 06:44:00 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0116.outbound.protection.outlook.com [104.47.37.116]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF421129426; Thu, 22 Jun 2017 06:43:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jabil.onmicrosoft.com;  s=selector1-jabil-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=AkNTDU+1sHSqnAQkTioVcwcCTa4RY5W2ZRPZwMeOClM=; b=xzaAJwHSS0ynUaLQ2bFpmWPne9uGZEDiuXUXXxXBXysdWNhwg8mgIxrey2T1yZlsaDzyfHWvzCvqiw9qWzuTgcHlsuidI1C/dJVj1jpA9xFmICO9a2GZ8CxwpHW0s/VOLy6tfp9lSQ3/s9Emg9jjG4pU3fznfmlba/j+YS6W250=
Received: from BN3PR0201MB0867.namprd02.prod.outlook.com (10.160.154.13) by BN3PR0201MB0867.namprd02.prod.outlook.com (10.160.154.13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1178.14; Thu, 22 Jun 2017 13:43:55 +0000
Received: from BN3PR0201MB0867.namprd02.prod.outlook.com ([10.160.154.13]) by BN3PR0201MB0867.namprd02.prod.outlook.com ([10.160.154.13]) with mapi id 15.01.1178.023; Thu, 22 Jun 2017 13:43:55 +0000
From: Xufeng Liu <Xufeng_Liu@jabil.com>
To: Benoit Claise <bclaise@cisco.com>, Robert Wilton <rwilton@cisco.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "draft-ietf-teas-yang-te-topo.all@ietf.org" <draft-ietf-teas-yang-te-topo.all@ietf.org>
Subject: RE: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Thread-Topic: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Thread-Index: AQHS1KSedaTR9X/fGEeQz0ke1nZ/sKIh1EjwgA1lWACAASg0QIAAZ0GAgAANhoCAADiPAA==
Date: Thu, 22 Jun 2017 13:43:55 +0000
Message-ID: <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com> <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com>
In-Reply-To: <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-dg-ref: PG1ldGE+PGF0IG5tPSJib2R5LnR4dCIgcD0iYzpcdXNlcnNceGxpdVxhcHBkYXRhXHJvYW1pbmdcMDlkODQ5YjYtMzJkMy00YTQwLTg1ZWUtNmI4NGJhMjllMzViXG1zZ3NcbXNnLWQzMzkyMDJhLTU3NTAtMTFlNy05YzE3LTE4NWUwZmUzYzQ1Y1xhbWUtdGVzdFxkMzM5MjAyYy01NzUwLTExZTctOWMxNy0xODVlMGZlM2M0NWNib2R5LnR4dCIgc3o9IjEwMTA2IiB0PSIxMzE0MjYxMjYzMzEwMTk4NDgiIGg9ImJQZ3M4TFVzZmJ6bVczbGt3dXM2VSswOFFLRT0iIGlkPSIiIGJsPSIwIiBibz0iMSIvPjwvbWV0YT4=
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=jabil.com;
x-originating-ip: [98.191.72.170]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BN3PR0201MB0867; 7:1ReIdtZJQVAO/eGVPcrrDmOOknf+1/oDS5J2TULjy9xLDj3mGdaM/eRwNsavJXghwdfc1dlYvVg4DoR15CJwK3Wp2PBl2dP3QrN0EjfXDcXWv1tQOcW0R2b/ngnBltTPXHUsRxnHcVKLO3WUU7VhiE5ljM49ynY9rE5MlTkh6UdYVAhv+1i4WluNZulwGRBpGAjmg+D8gl9io2b/WkVl2sVtmf6z2CKrqxLHT4+Jx0F6Sy/L4VSVA+40JVbklzrtZAnD+z0Tlb8hWgWLyKyYlSJ/aG0yUPu/x4xflomOHTiP3BUh+0jcSCD/Ju4w/wzY5dS4KrGAlosSN2DA8ZvrwormUD4DKRa07J6G6CZ3D43BF3p1iCpCwAY0MMwOZDx42NcXN9T9vU+ly3dx1P9T2LWQQd/mAEoulbaTKNjdU/8sBZYCEivwZgjChiU/meDFgEFw4bDbqq2Otf99ETU1HuXCjnti/33ewyJ/AKt2aF3s8f/glit1F1J5ObhPyeH20F+bGclGOGp0ujE5mun7ajPXjEP5eCOSzCjIfolQDH3ZFRl/Zlx05Q1TVoUMWClBDbj0WyhO1vbAC77wfegiP80o2A86OBOGaj3No3mE9X/fOujS3mjXMOMYMNeGAty5xx028ddrznawQ5k7qAoQw1kYi/CIpfCE9UZaQG1F5NGZbVY0E6rFpW7W8wcALeQ5LCyLcT6OC3kD/psEOYq7PdhSRhLD9uEbmI+ZtPaQb6/vrVK/BsDdJ6occVk78Q8VrtY90GYnrQ2EApyeHHyKcbOKPyYbXLlHLDdID/T/Siw=
x-ms-office365-filtering-correlation-id: ae919be1-a734-4684-15f3-08d4b974ba3c
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:BN3PR0201MB0867; 
x-ms-traffictypediagnostic: BN3PR0201MB0867:
x-microsoft-antispam-prvs: <BN3PR0201MB0867F7398C5D6FBF75C7C80EF1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820)(95692535739014)(21534305686606); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(100000703101)(100105400095)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(20161123564025)(20161123555025)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BN3PR0201MB0867; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BN3PR0201MB0867; 
x-forefront-prvs: 03468CBA43
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39850400002)(39450400003)(39400400002)(39410400002)(39860400002)(39840400002)(13464003)(377454003)(24454002)(51444003)(74316002)(3280700002)(2906002)(122556002)(2950100002)(229853002)(80792005)(305945005)(7736002)(2501003)(50986999)(54356999)(76176999)(25786009)(33656002)(4326008)(93886004)(53546010)(86362001)(3846002)(102836003)(39060400002)(6116002)(55016002)(6306002)(77096006)(72206003)(54906002)(5660300001)(7696004)(14454004)(6436002)(478600001)(3660700001)(6506006)(66066001)(6246003)(38730400002)(81156014)(81166006)(230783001)(189998001)(8936002)(53936002)(2900100001)(8676002)(9686003)(966005)(99286003); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0201MB0867; H:BN3PR0201MB0867.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: jabil.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jun 2017 13:43:55.6989 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bc876b21-f134-4c12-a265-8ed26b7f0f3b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0201MB0867
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/d8z7d8IYqhyPR-VW5moHK6jPmDg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 13:44:11 -0000

SGkgQmVub2l0LA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IEJlbm9p
dCBDbGFpc2UgW21haWx0bzpiY2xhaXNlQGNpc2NvLmNvbV0NCj4gU2VudDogVGh1cnNkYXksIEp1
bmUgMjIsIDIwMTcgNjoxMiBBTQ0KPiBUbzogUm9iZXJ0IFdpbHRvbiA8cndpbHRvbkBjaXNjby5j
b20+OyBYdWZlbmcgTGl1IDxYdWZlbmdfTGl1QGphYmlsLmNvbT47DQo+IE1haGVzaCBKZXRoYW5h
bmRhbmkgPG1qZXRoYW5hbmRhbmlAZ21haWwuY29tPjsgeWFuZy1kb2N0b3JzQGlldGYub3JnDQo+
IENjOiBpZXRmQGlldGYub3JnOyB0ZWFzQGlldGYub3JnOyBkcmFmdC1pZXRmLXRlYXMteWFuZy10
ZS10b3BvLmFsbEBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW1RlYXNdIFlhbmdkb2N0b3JzIGxh
c3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby0NCj4gMDgNCj4g
DQo+IERlYXIgZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wbyBhdXRob3JzLA0KPiA+IEhpIFh1
ZmVuZywNCj4gPg0KPiA+IE9LLCBieSB0b29saW5nLCBJIGRvbid0IG1lYW4gdGhlIHB5YW5nIHBs
dWdpbnMgdGhhdCBJIGhhdmUgYmVlbg0KPiA+IHdvcmtpbmcgb24gdG8gY29udmVydCBiZXR3ZWVu
IGRpZmZlcmVudCB0eXBlcyBvZiBtb2RlbHMuICBBcyB5b3UNCj4gPiBhd2FyZSwgdGhlIFRFIFlB
TkcgbW9kZWxzIGNhbiBlYXNpbHkgYmUgY29udmVydGVkIHRvIE5NREEgc3R5bGUgc2luY2UNCj4g
PiBJIGhhdmUgYWxyZWFkeSBkb25lIGl0DQo+ID4gKGh0dHBzOi8vZ2l0aHViLmNvbS9yZ3dpbHRv
bi9pZXRmLW1vZGVscy10by1jb21iaW5lZCkuDQo+ID4NCj4gPiBNeSBjb21tZW50IGFjdHVhbGx5
IHJlbGF0ZXMgdG8gdGhlIGZhY3QgdGhlIHN0cnVjdHVyZSB1c2VkIGJ5IFRFIFlBTkcNCj4gPiBt
b2R1bGVzIGRvbid0IG1hdGNoIGFueSBvdGhlciBZQU5HIG1vZHVsZXMgLSB0aGV5IGFyZSB1c2lu
ZyB0aGVpciBvd24NCj4gPiB1bmlxdWUgc3R5bGUgb2Ygc3RydWN0dXJlLg0KPiBUaGlzIGlzIGFu
IGltcG9ydGFudCBpc3N1ZSB0byByZXNvbHZlLg0KPiA+DQo+ID4gVG9kYXksIHRoZXJlIGFyZSB0
aHJlZSBjb21tb24gc3R5bGVzIG9mIG1vZHVsZXM6DQo+ID4gKDEpIElFVEYgc3R5bGUgc3BsaXQg
Y29uZmlnL3N0YXRlIHRyZWVzIChlLmcuIGlldGYtaW50ZXJmYWNlcykuDQo+ID4gKDIpIElFVEYg
Tk1EQSBzdHlsZSBjb21iaW5lZCBjb25maWcvc3RhdGUgdHJlZXMgKGkuZS4gd2hlcmUgYWxsIElF
VEYNCj4gPiBtb2R1bGVzIGFyZSBoZWFkaW5nIHRvKS4NCj4gPiAoMykgT3BlbkNvbmZpZyBzdHls
ZSBtb2R1bGVzIHdpdGggdGhlIGNvbmZpZy9zdGF0ZSBjb250YWluZXJzDQo+ID4gaW1tZWRpYXRl
bHkgYWJvdmUgdGhlIGNvbmZpZyBsZWF2ZXMuDQo+ID4NCj4gPiBUb29saW5nIGlzIGxpa2VseSB0
byBiZSBvcHRpbWl6ZWQgdG8gd29yayB3aXRoIHRoZXNlIG1vZGVsIHN0cnVjdHVyZXMsDQo+ID4g
YnV0IHRoZSBURSBtb2R1bGVzIGRvIG5vdCBmaXQgaW50byBhbnkgb2YgdGhlIHRocmVlIHN0eWxl
cyBhYm92ZS4NCj4gPiBUaGV5IGFyZSBhIHlldCBhbm90aGVyIE9wZW5Db25maWctbGlrZSBzdHls
ZSwgYnV0IHRoYXQgaXMgZGlmZmVyZW50DQo+ID4gZW5vdWdoIHRoYXQgdG9vbGluZyB0aGF0IGlz
IGRlc2lnbmVkIHRvIHdvcmsgd2l0aCBPcGVuQ29uZmlnIHN0eWxlDQo+ID4gWUFORyBtb2R1bGVz
IHdvdWxkIGxpa2VseSBub3Qgd29yayB3aXRoIHRoZSBURSBZQU5HIG1vZHVsZXMuDQo+ID4NCj4g
PiBTcGVjaWZpY2FsbHksIGZvciBjbGllbnRzIHRoYXQgZXhwZWN0aW5nIHRvIHdvcmsgd2l0aCBh
biBPcGVuQ29uZmlnDQo+ID4gc3R5bGUgWUFORyBtb2R1bGUsIHRoZW4gaWYgaXQga25vd3MgdGhl
IHBhdGggdG8gY29uZmlnIGxlYWYgWCwgdGhlbg0KPiA+IHRoZXkgd291bGQgZXhwZWN0IHRoZSBh
cHBsaWVkIGNvbmZpZyB2YWx1ZSB0byBiZSBhdmFpbGFibGUgYXQgdGhlIHBhdGgNCj4gPiAiLi4v
c3RhdGUvWCIuICBCdXQsIHRoaXMgZG9lc24ndCBob2xkIGZvciB0aGUgc3RydWN0dXJlIGJlaW5n
IHVzZWQgaW4NCj4gPiB0aGUgVEUgWUFORyBtb2RlbHMuDQo+ID4NCj4gPiBJIGJlbGlldmUgc3Ry
b25nbHkgdGhhdCB0aGUgbW9kZWxzIGJlaW5nIHByb2R1Y2VkIGJ5IG9yZ2FuaXphdGlvbnMNCj4g
PiBzaG91bGQgYmUgc3RydWN0dXJlcyBpbiBhIGNvbnNpc3RlbnQgd2F5LCBoZW5jZSB3aHkgSSB0
aGluayB0aGF0IHRoZQ0KPiA+IHB1Ymxpc2hlZCBzdGFuZGFyZCB2ZXJzaW9uIG9mIHRoZSBURSBZ
QU5HIG1vZHVsZXMgc2hvdWxkIGltbWVkaWF0ZWx5DQo+ID4gYWxpZ24gdG8gdGhlIE5NREEgc3R5
bGUuDQo+IEFncmVlZC4NCj4gSGVyZSBpcyB0aGUgT1BTIGFuZCBSVEcgQUQgbWVzc2FnZToNCj4g
aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9uZXRtb2QvY3VycmVudC9tc2cx
ODI1Mi5odG1sDQo+IA0KPiBJIHVuZGVyc3RhbmQgdGhhdCB0aGUgSTJSUyB0b3BvbG9neSBZQU5H
IG1vZHVsZXMgd2lsbCBiZSBpbXByb3ZlZCB0byB0aGUNCj4gTk1EQSBzdHlsZS4NCltYdWZlbmdd
IFRoZSBJMlJTIHRvcG9sb2d5IG1vZGVsIGlzIGFscmVhZHkgTk1EQSBzdHlsZSwgYnV0IHRoZSBO
TURBIG1vZGVscyBhcmUgbm90IGltbWVkaWF0ZWx5IGltcGxlbWVudGFibGUgd2l0aG91dCBORVRD
T05GL1JFU1RDT05GIHByb3RvY29sIHVwZGF0ZS4gV2Ugd2lsbCBuZWVkIHRoZSAiLXN0YXRlIiBt
b2R1bGUgZm9yIHRoZSBJMlJTIHRvcG9sb2d5IG1vZGVsIChhbmQgZm9yIGFsbCB0aGUgdG9wLWxl
dmVsIG1vZGVscykgZm9yIG5vdy4gV2hpbGUgdGhlIE5NREEgaXMgbmljZSwgdGhlIE5NREEgZGlz
Y3Vzc2lvbnMgaGF2ZSBhbHJlYWR5IHNpZ25pZmljYW50bHkgZGVsYXllZCBwdWJsaXNoaW5nIG5l
dyBtb2RlbHMsIGFuZCBkb2luZyBOTURBIHdpdGhvdXQgc3RhZ2luZyB3aWxsIGZ1cnRoZXIgZGVs
YXkgdGhlIHByb2Nlc3MuDQpUaGFua3MsICBYdWZlbmcNCj4gDQo+IFJlZ2FyZHMsIEJlbm9pdA0K
PiA+DQo+ID4gVGhhbmtzLA0KPiA+IFJvYg0KPiA+DQo+ID4NCj4gPiBPbiAyMi8wNi8yMDE3IDA0
OjE2LCBYdWZlbmcgTGl1IHdyb3RlOg0KPiA+PiBIaSBSb2IsDQo+ID4+DQo+ID4+IFdoaWxlIHRo
ZSB0b29saW5nIGlzIHZlcnkgbmljZSB0byBoYXZlLCBlc3BlY2lhbGx5IGZvciB3cml0aW5nIG5l
dw0KPiA+PiBtb2RlbHMgb3IgY29udmVydGluZyBtb2RlbHMsIHdlIGRvIG5vdCBoYXZlIHRvIHVz
ZSBpdCBmb3IgZXZlcnkNCj4gPj4gbW9kZWwuIEl0IHNlZW1zIG5vdCBuZWNlc3NhcnkgdG8gdXNl
IHRoZSB0b29saW5nIG9uIHRoaXMgbW9kZWwgZm9yDQo+ID4+IG5vdy4gV2UgYWxyZWFkeSBrbm93
IHRoYXQgd2UgY2FuIG1hbnVhbGx5IGNvbnZlcnQgaXQgdG8gTk1EQSBzdHlsZSBpZg0KPiA+PiBu
ZWVkZWQuDQo+ID4+DQo+ID4+IFRoYW5rcywNCj4gPj4gLSBYdWZlbmcNCj4gPj4NCj4gPj4+IC0t
LS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+PiBGcm9tOiBSb2JlcnQgV2lsdG9uIFttYWls
dG86cndpbHRvbkBjaXNjby5jb21dDQo+ID4+PiBTZW50OiBXZWRuZXNkYXksIEp1bmUgMjEsIDIw
MTcgNTozNCBBTQ0KPiA+Pj4gVG86IFh1ZmVuZyBMaXUgPFh1ZmVuZ19MaXVAamFiaWwuY29tPjsg
TWFoZXNoIEpldGhhbmFuZGFuaQ0KPiA+Pj4gPG1qZXRoYW5hbmRhbmlAZ21haWwuY29tPjsgeWFu
Zy1kb2N0b3JzQGlldGYub3JnDQo+ID4+PiBDYzogaWV0ZkBpZXRmLm9yZzsgdGVhc0BpZXRmLm9y
ZzsNCj4gPj4+IGRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8uYWxsQGlldGYub3JnDQo+ID4+
PiBTdWJqZWN0OiBSZTogW1RlYXNdIFlhbmdkb2N0b3JzIGxhc3QgY2FsbCByZXZpZXcgb2YNCj4g
Pj4+IGRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8tDQo+ID4+PiAwOA0KPiA+Pj4NCj4gPj4+
IEhpIFh1ZmVuZywNCj4gPj4+DQo+ID4+PiBPbiAxMi8wNi8yMDE3IDIyOjI4LCBYdWZlbmcgTGl1
IHdyb3RlOg0KPiA+Pj4+IEhpIE1haGVzaCwNCj4gPj4+Pg0KPiA+Pj4+IFRoYW5rIHlvdSBtdWNo
IGZvciB0aGUgcmV2aWV3LiBXZSBoYXZlIHN1Ym1pdHRlZCBhbiB1cGRhdGVkIGRyYWZ0DQo+ID4+
PiAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRv
cG8tMDkpIHRvDQo+ID4+PiBhZGRyZXNzIHRoZXNlIGlzc3Vlcy4gTW9yZSBkZXRhaWxlZCBleHBs
YW5hdGlvbnMgYXJlIHB1dCBiZWxvdw0KPiA+Pj4gaW5saW5lLg0KPiA+Pj4+IElmIHRoZSByZXNw
b25zZXMgYW5kIHVwZGF0ZXMgYXJlIHNhdGlzZmFjdG9yeSwgd2UgYXJlIHJlYWR5IGZvciB0aGUN
Cj4gPj4+PiBsYXN0IGNhbGwuDQo+ID4+Pj4NCj4gPj4+PiBCZXN0IHJlZ2FyZHMsDQo+ID4+Pj4g
LSBYdWZlbmcNCj4gPj4+Pg0KPiA+Pj4+PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiA+
Pj4+PiBGcm9tOiBNYWhlc2ggSmV0aGFuYW5kYW5pIFttYWlsdG86bWpldGhhbmFuZGFuaUBnbWFp
bC5jb21dDQo+ID4+Pj4+IFNlbnQ6IFdlZG5lc2RheSwgTWF5IDI0LCAyMDE3IDExOjQ0IEFNDQo+
ID4+Pj4+IFRvOiB5YW5nLWRvY3RvcnNAaWV0Zi5vcmcNCj4gPj4+Pj4gQ2M6IGlldGZAaWV0Zi5v
cmc7IHRlYXNAaWV0Zi5vcmc7DQo+ID4+Pj4+IGRyYWZ0LWlldGYtdGVhcy15YW5nLXRlLXRvcG8u
YWxsQGlldGYub3JnDQo+ID4+Pj4+IFN1YmplY3Q6IFlhbmdkb2N0b3JzIGxhc3QgY2FsbCByZXZp
ZXcgb2YNCj4gPj4+Pj4gZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby0wOA0KPiA+Pj4+Pg0K
PiA+Pj4+PiBSZXZpZXdlcjogTWFoZXNoIEpldGhhbmFuZGFuaQ0KPiA+Pj4+PiBSZXZpZXcgcmVz
dWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KPiA+Pj4+Pg0KPiA+Pj4+PiBEb2N1bWVudCByZXZpZXdl
ZDogZHJhZnQtaWV0Zi10ZWFzLXlhbmctdGUtdG9wby0wOA0KPiA+Pj4+Pg0KPiA+Pj4+PiBTdGF0
dXM6IFJlYWR5IHdpdGggSXNzdWVzDQo+ID4+Pj4+DQo+ID4+Pj4+IEkgYW0gbm90IGFuIGV4cGVy
dCBpbiBUcmFmZmljIEVuZ2luZWVyaW5nLiBUaGlzIHJldmlldyBpcyBsb29raW5nDQo+ID4+Pj4+
IGF0IHRoZSBkcmFmdCBmcm9tIGEgWUFORyBwZXJzcGVjdGl2ZS4gV2l0aCB0aGF0IHNhaWQsIEkg
aGF2ZQ0KPiA+Pj4+PiBtYXJrZWQgaXQgYXMg4oCcUmVhZHkNCj4gPj4+IHdpdGggSXNzdWVz4oCd
DQo+ID4+Pj4+IGJlY2F1c2Ugb2Ygc29tZSBvZiB0aGUgcG9pbnRzIGRpc2N1c3NlZCBiZWxvdy4N
Cj4gPj4+Pj4NCj4gPj4+Pj4gU3VtbWFyeToNCj4gPj4+Pj4NCj4gPj4+Pj4gVGhpcyBkb2N1bWVu
dCBkZWZpbmVzIGEgWUFORyBkYXRhIG1vZGVsIGZvciByZXByZXNlbnRpbmcsDQo+ID4+Pj4+IHJl
dHJpZXZpbmcgYW5kIG1hbmlwdWxhdGluZyBURSBUb3BvbG9naWVzLiBUaGUgbW9kZWwgc2VydmVz
IGFzIGENCj4gPj4+Pj4gYmFzZSBtb2RlbCB0aGF0IG90aGVyIHRlY2hub2xvZ3kgc3BlY2lmaWMg
VEUgVG9wb2xvZ3kgbW9kZWxzIGNhbg0KPiBhdWdtZW50Lg0KPiA+Pj4+Pg0KPiA+Pj4+PiBDb21t
ZW50czoNCj4gPj4+Pj4NCj4gPj4+Pj4gQWxtb3N0IGFsbCB0aGUgY29udGFpbmVycyBpbiB0aGUg
bW9kZWwgYXJlIHByZXNlbmNlIGNvbnRhaW5lcnMuIElzDQo+ID4+Pj4+IHRoZXJlIGEgcmVhc29u
IHdoeSB0aGV5IGhhdmUgdG8gYmUgcHJlc2VuY2UgY29udGFpbmVycz8gTm90ZSwgdGhhdA0KPiA+
Pj4+PiBwcmVzZW5jZSBjb250YWluZXJzIGFyZSBjb250YWluZXJzIHdob3NlIGV4aXN0ZW5jZSBp
dHNlbGYNCj4gPj4+Pj4gcmVwcmVzZW50cyBjb25maWd1cmF0aW9uIGRhdGEuIFdoYXQgcGFydGlj
dWxhciBjb25maWd1cmF0aW9uIGRhdGENCj4gPj4+Pj4gaXMgZWFjaCBjb250YWluZXINCj4gPj4+
IHJlcHJlc2VudGluZyBpbiBpdHNlbGY/DQo+ID4+Pj4gW1h1ZmVuZ10gQ29udGFpbmVycyB0aGF0
IHVzZSDigJxwcmVzZW5jZeKAnSBhcmU6DQo+ID4+Pj4gICAgIC0gQ29udGFpbmVyIOKAnHVuZGVy
bGF54oCdDQo+ID4+Pj4gICAgICAgbyAgV2UgaGF2ZSBjaGFuZ2VkIDEzIG9jY3VycmVuY2VzIG9m
IHN1Y2ggY29udGFpbmVycyB0byBiZQ0KPiA+Pj4+IG5vdA0KPiA+Pj4gcHJlc2VuY2UgY29udGFp
bmVyLg0KPiA+Pj4+ICAgICAtIENvbnRhaW5lciDigJx0ZeKAnSB1bmRlciBhdWdtZW50YXRpb24N
Cj4gPj4+PiAgICAgICBvICBUbyBpbmRpY2F0ZSB0aGF0IOKAnFRF4oCdIGlzIGVuYWJsZWQgKGNv
bmZpZ3VyYXRpb24gZGF0YSkNCj4gPj4+PiAgICAgICBvICBBbHNvIHVzZWQgdG8gZG8gYXVnbWVu
dGF0aW9uLiBUaGUg4oCccHJlc2VuY2XigJ0gc3RhdGVtZW50IGNhbg0KPiA+Pj4gcHJldmVudCB0
aGUgbWFuZGF0b3J5IGNoaWxkIGZyb20gYWZmZWN0aW5nIGF1Z21lbnRlZCBiYXNlIG1vZGVsLg0K
PiA+Pj4+ICAgICAtIC9udzpuZXR3b3Jrcy9udzpuZXR3b3JrL253Om5ldHdvcmstdHlwZXMvdGUt
dG9wb2xvZ3khDQo+ID4+Pj4gICAgICAgbyAgQSBtZWNoYW5pc20gcmVxdWlyZWQgYnkgSTJSUyB0
b3BvbG9neSBtb2RlbCB0byBzcGVjaWZ5IHRoZQ0KPiA+Pj4gdG9wb2xvZ3kgdHlwZS4NCj4gPj4+
Pj4gSXQgaXMgZGlmZmljdWx0IHRvIGNvLXJlbGF0ZSB0aGUgZGlhZ3JhbSB3aXRoIHRoZSBtb2Rl
bCBpdHNlbGYNCj4gPj4+Pj4gYmVjYXVzZSBvZiBkaWZmZXJlbnQgdGVybXMgYmVpbmcgdXNlZCB0
byBkZWZpbmUgZGlmZmVyZW50IHBhcnRzIG9mDQo+ID4+Pj4+IHRoZSBtb2RlbC4NCj4gPj4+Pj4g
VGhlcmUgaXMg4oCcVEUgVG9wb2xvZ3kgTW9kZWzigJ0gYW5kIHRoZW4gdGhlcmUgaXMg4oCcR2Vu
ZXJpYyBURQ0KPiA+Pj4+PiBUb3BvbG9neQ0KPiA+Pj4gTW9kZWzigJ0uDQo+ID4+Pj4+IEFyZSB0
aGVzZSBvbmUgYW5kIHRoZSBzYW1lIG1vZGVscz8gSWYgc28sIGEgY29tbW9uIHRlcm0gZm9yIGJv
dGgNCj4gPj4+Pj4gb2YgdGhlbSB3b3VsZCBiZSBoZWxwZnVsLg0KPiA+Pj4+IFtYdWZlbmddIFll
cy4gVGhlc2UgdHdvIHRlcm1zIGFyZSB0aGUgc2FtZS4gRmlndXJlIDEyLCBGaWd1cmUgMTMsDQo+
ID4+Pj4gYW5kIHJlbGV2YW50DQo+ID4+PiBkZXNjcmlwdGlvbnMgaGF2ZSBiZWVuIHVwZGF0ZWQg
dG8gbWFrZSB0aGUgZG9jdW1lbnQgY29uc2lzdGVudC4NCj4gPj4+Pj4gVGhlcmUgaXMgZXh0ZW5z
aXZlIHVzZSBvZiBncm91cGluZ3MgaW4gdGhlIGRvY3VtZW50LiBIb3dldmVyLCBub3QNCj4gPj4+
Pj4gYWxsIGluc3RhbmNlcyBvZiBncm91cGluZ3MgYXJlIHVzZWQgbXVsdGlwbGUgbnVtYmVyIG9m
IHRpbWVzLg0KPiA+Pj4+PiBXaGVyZSB0aGV5IGFyZSBub3QgYmVpbmcgcmVwZWF0ZWQsIGl0IHdv
dWxkIGJlIGJldHRlciB0byBtb3ZlIHRoZQ0KPiA+Pj4+PiBncm91cGluZyBkaXJlY3RseSB3aGVy
ZSB0aGUgdXNlcyBzdGF0ZW1lbnQgcmVzaWRlcy4gQ2FzZSBpbiBwb2ludA0KPiA+Pj4+PiB0aGUg
Z3JvdXBpbmcNCj4gPj4+IGNvbm5lY3Rpdml0eS1sYWJlbC1yZXN0cmljdGlvbi1saXN0Lg0KPiA+
Pj4+IFtYdWZlbmddIFdlIGhhdmUgcmVtb3ZlZCB0aGUgZm9sbG93aW5nIGdyb3VwaW5ncw0KPiA+
Pj4+ICAgICAgIHRlLWxpbmstYXVnbWVudA0KPiA+Pj4+ICAgICAgIHRlLW5vZGUtYXVnbWVudA0K
PiA+Pj4+ICAgICAgIHRlLXRlcm1pbmF0aW9uLXBvaW50LWF1Z21lbnQNCj4gPj4+PiAgICAgICB0
ZS10b3BvbG9naWVzLWF1Z21lbnQNCj4gPj4+PiAgICAgICB0ZS10b3BvbG9neS1hdWdtZW50DQo+
ID4+Pj4gICAgICAgdGUtbGluay1zdGF0ZS11bmRlcmxheS1hdHRyaWJ1dGVzDQo+ID4+Pj4gICAg
ICAgdGUtbm9kZS1zdGF0ZS1kZXJpdmVkLW5vdGlmaWNhdGlvbg0KPiA+Pj4+ICAgICAgIHRlLXRv
cG9sb2d5LXR5cGUNCj4gPj4+Pg0KPiA+Pj4+IFRoZSByZW1haW5pbmcgZ3JvdXBpbmdzIGhhdmUg
YmVlbiBrZXB0IHNvIHRoYXQgd2UgY2FuOg0KPiA+Pj4+ICAgICAtIFNoYXJlIHRoZSBncm91cGlu
Z3MgaW4gdGhpcyBtb2RlbA0KPiA+Pj4+ICAgICAtIFByZXBhcmUgdG8gYmUgc2hhcmVkIGJ5IGEg
bW9kZWwgYXVnbWVudGluZyB0aGlzIG1vZGVsDQo+ID4+Pj4gICAgIC0gUHJldmVudCBhIGdyb3Vw
aW5nIG9yIGNvbmZpZ3VyYXRpb24gc2VjdGlvbiBmcm9tIGJlaW5nIHRvbyBsb25nDQo+ID4+Pj4g
ICAgIC0gSW1wcm92ZSByZWFkYWJpbGl0eQ0KPiA+Pj4+DQo+ID4+Pj4+IFRoZSBzcGxpdCBiZXR3
ZWVuIGNvbmZpZyBhbmQgc3RhdGUgY29udGFpbmVycyBkb2VzIG5vdCBzZWVtIHRvDQo+ID4+Pj4+
IGZvbGxvdyBhbnkgcGFydGljdWxhciBwYXR0ZXJuLg0KPiA+Pj4+IFtYdWZlbmddIFRoZSBwYXR0
ZXJuIGlzIGNsZWFyOg0KPiA+Pj4+IEZvciBlYWNoIG1hbmFnZWFibGUgZW50aXR5IChvYmplY3Qp
LCB0aGVyZSBpcyBhIGNvbmZpZyBjb250YWluZXINCj4gPj4+PiBhbmQgc3RhdGUNCj4gPj4+IGNv
bnRhaW5lci4gVGhlIGNvbmZpZ3VyYWJsZSBwcm9wZXJ0aWVzIGdvIGludG8gdGhlIGNvbmZpZyBj
b250YWluZXINCj4gPj4+IGFuZCBzdGF0ZSBwcm9wZXJ0aWVzIGdvIGludG8gdGhlIHN0YXRlIGNv
bnRhaW5lci4gU3VjaCBvYmplY3RzIGFyZQ0KPiA+Pj4gaWRlbnRpZmllZCBieSBhIGxpc3QgaXRl
bSBvciBhIHByZXNlbmNlIGNvbnRhaW5lciBzbyB0aGF0IHRoZQ0KPiA+Pj4g4oCcY3JlYXRl4oCd
LCDigJxkZWxldGXigJ0sIGFuZCDigJxtb2RpZnnigJ0NCj4gPj4+IG9wZXJhdGlvbnMNCj4gPj4+
IGNhbiBiZSBwZXJmb3JtZWQgb24gdGhlbS4gVGhlIG5vbi1wcmVzZW5jZSBjb250YWluZXJzIGRv
IG5vdA0KPiA+Pj4gcmVwcmVzZW50IGNvbmZpZ3VyYXRpb24gZGF0YSBzbyB0aGV5IGRvIG5vdCBp
bnRyb2R1Y2Ugc3VjaCBvYmplY3RzLg0KPiA+Pj4+PiBJdCBpcyBuZWl0aGVyIGEgdG9wIGxldmVs
IHNwbGl0LCBhcyBpcyB0aGUgY2FzZSB3aXRoIGV4aXN0aW5nIElFVEYNCj4gPj4+Pj4gbW9kZWxz
LA0KPiA+Pj4+IFtYdWZlbmddIFdlIGNvdWxkIG5vdCBkbyB0b3AgbGV2ZWwgc3BsaXQgYmVjYXVz
ZSB0aGUgYmFzZSBJMlJTDQo+ID4+Pj4gbmV0d29yaw0KPiA+Pj4gdG9wb2xvZ3kgbW9kZWwNCj4g
Pj4+IChodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1pMnJzLXlhbmctbmV0
d29yay10b3BvLQ0KPiA+Pj4gMTIpIHRoYXQgd2UgYXVnbWVudCBkb2VzIG5vdCBoYXZlIHRoZSB0
b3AtbGV2ZWwgc3BsaXQgKGZvciBpdHMgb3duDQo+ID4+PiByZWFzb25zKS4NCj4gPj4+Pj4gbm9y
IGRvIHRoZXkgZm9sbG93IHRoZSBPcGVuQ29uZmlnIHN0eWxlIG9mIHNwbGl0dGluZyBjb25maWcg
YW5kDQo+ID4+Pj4+IHN0YXRlIHVuZGVyIGVhY2ggcmVsZXZhbnQgbGVhZiwNCj4gPj4+PiBbWHVm
ZW5nXSBUaGUgcGF0dGVybiBpcyBjb25zaXN0ZW50IHdpdGggdGhpcyBzdHlsZSBpbiBwcmluY2lw
bGUsDQo+ID4+Pj4gd2l0aCBzb21lDQo+ID4+PiBhZGp1c3RtZW50cyB0byBmaXQgdG8gb3VyIG11
bHRpcGxlIGxldmVscyBvZiBoaWVyYXJjaHkuDQo+ID4+PiBUaGlzIGlzIGVmZmVjdGl2ZWx5IGEg
bmV3IGZvcnRoIHN0eWxlIG9mIFlBTkcgbW9kZWxzIHRoYXQgaXMgbm90DQo+ID4+PiBjb25zaXN0
ZW50IHdpdGggYW55IG9mIHRoZSB0aHJlZSBleGlzdGluZyBzdHlsZXMsIGkuZS46DQo+ID4+PiAg
ICAtIEN1cnJlbnQgSUVURiBjb25maWcvc3RhdGUgc3BsaXQgbW9kZWwgc3R5bGUNCj4gPj4+ICAg
IC0gTk1EQSBjb21iaW5lZCBjb25maWcvc3RhdGUgdHJlZQ0KPiA+Pj4gICAgLSBPcGVuQ29uZmln
IHNwbGl0IGNvbmZpZy9zdGF0ZSBjb250YWluZXJzIGltbWVkaWF0ZWx5IGFib3ZlIHRoZQ0KPiA+
Pj4gY29uZmlnIHRydWUgbGVhdmVzLg0KPiA+Pj4NCj4gPj4+IFRvb2xpbmcgdGhhdCBpdCBkZXNp
Z25lZCB0byB3b3JrIHdpdGggT3BlbkNvbmZpZyBtb2RlbHMgd2lsbCBuZWVkDQo+ID4+PiBjdXN0
b21pemF0aW9uIHRvIHdvcmsgd2l0aCB0aGVzZSBURSBtb2RlbHMgYmVjYXVzZSB0aGUgY29uZmln
L3N0YXRlDQo+ID4+PiBjb250YWluZXJzIHdpbGwgbm90IGJlIHdoZXJlIHRoZSB0b29saW5nIGV4
cGVjdHMgdGhlbSB0byBiZS4NCj4gPj4+DQo+ID4+PiBUaGFua3MsDQo+ID4+PiBSb2INCj4gPg0K
PiA+IC4NCj4gPg0KDQo=


From nobody Thu Jun 22 07:28:44 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 0AEB312943B for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 07:28:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id X81hBllVdAZC for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 07:28:39 -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 ED64312954C for <ietf@ietf.org>; Thu, 22 Jun 2017 07:28:38 -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 v5MESZ1W021467; Thu, 22 Jun 2017 16:28:35 +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 3wtkTb1VSbz3Zn3; Thu, 22 Jun 2017 16:28:35 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: is there a good email list / wiki for folks involved in protocol design?
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <0d6283c7-3038-a9f2-6b17-916da8c4494e@meetinghouse.net>
Date: Thu, 22 Jun 2017 16:28:34 +0200
Cc: ietf@ietf.org
X-Mao-Original-Outgoing-Id: 519834514.606134-61d1e590eea50153cdbecf1f70501e80
Content-Transfer-Encoding: quoted-printable
Message-Id: <633C346E-B8B4-4382-8AC1-627E8BD9C729@tzi.org>
References: <0d6283c7-3038-a9f2-6b17-916da8c4494e@meetinghouse.net>
To: Miles Fidelman <mfidelman@meetinghouse.net>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1tXf-K62LSDLVX_agxM0sX-86mc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 14:28:42 -0000

Hi Miles,

I=E2=80=99m not aware of a lambda-the-ultimate kind of site, but the =
IETF has a number of very good RFCs on protocol design.

RFC 1958 comes to mind as an early example, and I think RFC 8170 is the =
most recent one (which also happens to be right on your subject).  RFC =
5218 is one of my favorites.  There are also more technical documents =
such as RFC 3819.

But it is true that much of what makes a good protocol design (or design =
process) remains the tacit knowledge of the experienced designers that =
we have collected here in the IETF, and that also remains one of the =
USPs of the IETF that would be really hard to duplicate.

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


> On Jun 22, 2017, at 14:44, Miles Fidelman <mfidelman@meetinghouse.net> =
wrote:
>=20
> Hi Folks,
>=20
> This would seem to be the right place to ask.
>=20
> There's a wonderful blog/wiki/community-of-interest (Drupal site, =
actually) at lambda-the-ultimate.org that seems to have become a focal =
point for folks involved in the theory & practice of programming =
language design (billed as "The Programming Language Weblog").
>=20
> I've been wondering if there's any kind of a similar site/community =
organized around protocol design.  Anybody know of one?
>=20
> Context:  I've been thinking about writing a book on the history of =
protocol adoption - how & why some protocols have become ubiquitous - =
with a particular focus on how & why new functionality keeps showing up =
as APIs, SaaS, SOAs, and now micro-services. (Working title: Back to =
Walled Gardens).  There's lots of activity, email lists, etc. around API =
and micro-service development, but I can't seem to find much on the =
theory & practice of protocol development (is it that are spread around =
more focused on specific problems, say in specific IETF working groups - =
to the detriment of a more general community-of-interest?).
>=20
> Thanks,
>=20
> Miles Fidelman
>=20
> --=20
> In theory, there is no difference between theory and practice.
> In practice, there is.  .... Yogi Berra
>=20
>=20


From nobody Thu Jun 22 13:08:25 2017
Return-Path: <brown@isoc.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 2F84F129492 for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 13:08:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level: 
X-Spam-Status: No, score=-4.8 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, LOTS_OF_MONEY=0.001, 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=isoc.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2hBS3PAkeZw1 for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 13:08:20 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0045.outbound.protection.outlook.com [104.47.41.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30EFB128C84 for <ietf@ietf.org>; Thu, 22 Jun 2017 13:08:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector1;  h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ojG0T9P7zNmmdR3+Q7qS2DsriWuZGHGC3DfV+qaNGjE=; b=JEQYCuKpcDrBHBzQb2Hgh9yWcqVnQgUyVeHHyc9Tnbq1vHvAMtaSeksD8IGp6+hIGJBcZ1d56Pj0Idv1CyPGDTfnfZVKJuYhx6T1FllbiO7redqt00SNdln08VmlllrpPobLiDkIE++O9Qwq06BhasYomD08vjj1Zibhm6qCLXA=
Received: from SN1PR06MB1824.namprd06.prod.outlook.com (10.162.133.11) by SN1PR06MB1823.namprd06.prod.outlook.com (10.162.133.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.15; Thu, 22 Jun 2017 20:08:18 +0000
Received: from SN1PR06MB1824.namprd06.prod.outlook.com ([10.162.133.11]) by SN1PR06MB1824.namprd06.prod.outlook.com ([10.162.133.11]) with mapi id 15.01.1199.016; Thu, 22 Jun 2017 20:08:17 +0000
From: Kathy Brown <brown@isoc.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: New Sponsorship Coordinator: Joe Abley
Thread-Topic: New Sponsorship Coordinator: Joe Abley
Thread-Index: AQHS65NJ3chitwz3LEeAGzmiI0NoiA==
Date: Thu, 22 Jun 2017 20:08:17 +0000
Message-ID: <D5719BE2.1D9991%brown@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.3.170325
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=isoc.org;
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [73.135.10.43]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR06MB1823; 7:XoOrLcyxizZ+SPtJJ5NqrEEZ8vOkhgtXPpGNRdeYPefV+funvPC8Mc9ZcHPSVjiNMidJLH0uEnMXcOuoY71mSsGbMK6HMazvJPnVp6Xlmwg0oNHLiT1YXq94LhFQXzr1F7m3dGI+kdSVufoMDnSfSjdTy4A/KfMd4Zhjhv+V/zu/UeNlRJo6MpyIERcIgsHR3aM42IsX8LUJZ+GbgwPJL65WF77L+UC0cLru0WSs86DHZdYiHVmIX6Jd596D8S77Bv29DJ0y6OZaheqHBLDD0a1i1sXyCzyuyvl/SaGcedE8+qqqn/MBdbyAzYXTgoFLq53HAqaxo84YMuDN++yHh3CUQu3queEsMguMLQOhArPv50ixzqA1YAe6saH12Oi6nv8t9NZsJEox/dQ7hEM9jjtZfK0oN9ddP4602hXfWpwsApyvrkN9/FYNlk0GQx1fKxY9Up9vYQQvqY+lsqTefXIdJWMo5kRCnpxCxqMqmjB2p2zru6LwJojTzZt5eURbcM6l/KPWkOUD7mmqlbOQXq0ApzMSYpWkdfstGU2ZuxqCtnBVe2QfvKruQxhybWhR1r1fH7HGuzC01gKWB9HzKwUzfzgKYuzyB7Jjdi4Xo8qJcoMfLFaXApf8n+InhkrMQmpW7xTlIi+1Ec4EQJ9V2YXvzZg/QxqMWRLNt4bdP1ApWh5nkiHTI2Wzgaas1JZ31WxZkqiVbh5Lq5LRk8XQBXhkFJ2LZV58SCcCuLL7R/YGUslBOYeTB+8SGiySGjFo89jQvBTexZL5ytuJEMf8nTch/RK/wSLmCO8gtaGCzIs=
x-ms-office365-filtering-correlation-id: b4214850-405e-4438-7707-08d4b9aa6c5b
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500055)(300135000095)(300000501055)(300135300095)(22001)(300000502055)(300135100095)(2017030254075)(300000503055)(300135400095)(201703131423075)(201703031133081)(300000504055)(300135200095)(300000505055)(300135600095)(300000506048)(300135500095); SRVR:SN1PR06MB1823; 
x-ms-traffictypediagnostic: SN1PR06MB1823:
x-microsoft-antispam-prvs: <SN1PR06MB1823BEB2E3C9CD757B84EC20DEDB0@SN1PR06MB1823.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(6041248)(20161123558100)(20161123555025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123564025)(20161123560025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:SN1PR06MB1823; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN1PR06MB1823; 
x-forefront-prvs: 03468CBA43
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39450400003)(39830400002)(39400400002)(39410400002)(66654002)(3660700001)(1730700003)(81166006)(2900100001)(8936002)(6916009)(189998001)(6506006)(66066001)(86362001)(6436002)(8676002)(7736002)(36756003)(4001350100001)(478600001)(2351001)(54356999)(50986999)(14454004)(2501003)(6486002)(77096006)(6512007)(25786009)(236005)(83506001)(3846002)(6116002)(102836003)(3280700002)(5640700003)(110136004)(38730400002)(5660300001)(53936002)(122556002)(99286003)(54896002)(2906002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN1PR06MB1823; H:SN1PR06MB1824.namprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_D5719BE21D9991brownisocorg_"
MIME-Version: 1.0
X-OriginatorOrg: isoc.org
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jun 2017 20:08:17.6938 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR06MB1823
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/HmCl-H7cTnBcYP_ajg4ZTFCuMHg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 20:08:23 -0000

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

Each year, the IETF is supported in part by over $2 million USD in sponsors=
hip contributions from a variety of organizations. BCP 101 tasks the Intern=
et Society with creating and maintaining appropriate structures and program=
s to coordinate donations intended to support the work of the IETF.

ISOC has recently secured the services of Joe Abley to work on raising spon=
sorship funding for the IETF. Many of you know Joe as a long-time participa=
nt in the IETF and broader internet community. For those who do not, his bi=
o is below. Please join us in welcoming Joe in this new role!

Howie Baggott has been working closely with Joe to transition the IETF spon=
sorship portfolio to him before shifting to other non-IETF-related responsi=
bilities within ISOC. Many thanks to Howie for his work on sponsorship fund=
raising over the last year.

If you are interested in discussing IETF sponsorship opportunities with Joe=
, feel free to contact him at jabley@ietf.org<mailto:jabley@ietf.org>.

Kathy Brown
ISOC CEO

Alissa Cooper
IETF Chair

---

Joe's bio:

Joe Abley has been working in some form or other in the general area of Int=
ernet architecture and operations since graduating from the University of C=
ambridge in the UK in the early 90s. Originally from New Zealand, he now li=
ves in Canada where he helps run Snake Hill Labs, a small consulting compan=
y that helps clients solve Internet infrastructure problems with particular=
 reference to the DNS. Joe has held engineering and technical management ro=
les at companies such as AboveNet, ISC, Afilias, TekSavvy, ICANN and Dyn.

Joe has served on various committees with regional Network Operator Groups =
over the years, was one of the original enthusiasts behind the Auckland Pee=
ring Exchange and has worked for many years with the Network Startup Resour=
ce Center (NSRC) on technical capacity building in developing economies. At=
 the IETF, Joe has volunteered as Executive Director for the IAB, co-author=
ed fifteen RFCs and was one-time co-chair of the OpSec working group.


--_000_D5719BE21D9991brownisocorg_
Content-Type: text/html; charset="us-ascii"
Content-ID: <E7ED657C00AEBD48AC99476AA7BCD4AC@namprd06.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<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-lin=
e-break: after-white-space; color: rgb(0, 0, 0); font-size: 18px; font-fami=
ly: Cambria, sans-serif;">
<div>
<div class=3D"" style=3D"font-family: Cambria;">Each year, the IETF is supp=
orted in part by over $2 million USD in sponsorship contributions from a va=
riety of organizations. BCP 101 tasks the Internet Society with creating an=
d maintaining appropriate structures
 and programs to coordinate donations intended to support the work of the I=
ETF.</div>
<div class=3D"" style=3D"font-family: Cambria;"><br class=3D"">
</div>
<div class=3D"" style=3D"font-family: Cambria;">ISOC has recently secured t=
he services of Joe Abley to work on raising sponsorship funding for the IET=
F. Many of you know Joe as a long-time participant in the IETF and broader =
internet community. For those who do
 not, his bio is below. Please join us in welcoming Joe in this new role!</=
div>
<div class=3D"" style=3D"font-family: Cambria;"><br class=3D"">
</div>
<div class=3D"" style=3D"font-family: Cambria;">Howie Baggott has been work=
ing closely with Joe to transition the IETF sponsorship portfolio to him be=
fore shifting to other non-IETF-related responsibilities within ISOC. Many =
thanks to Howie for his work on sponsorship
 fundraising over the last year.</div>
<div class=3D"" style=3D"font-family: Cambria;"><br class=3D"">
</div>
<div class=3D"" style=3D"font-family: Cambria;">If you are interested in di=
scussing IETF sponsorship opportunities with Joe, feel free to contact him =
at&nbsp;<a href=3D"mailto:jabley@ietf.org" class=3D"">jabley@ietf.org</a>.<=
/div>
<div class=3D"" style=3D"font-family: Cambria;"><br class=3D"">
</div>
<div class=3D"" style=3D"font-family: Cambria;">Kathy Brown</div>
<div class=3D"" style=3D"font-family: Cambria;">ISOC CEO</div>
<div class=3D"" style=3D"font-family: Cambria;"><br class=3D"">
</div>
<div class=3D"" style=3D"font-family: Cambria;">Alissa Cooper</div>
<div class=3D"" style=3D"font-family: Cambria;">IETF Chair</div>
<div class=3D"" style=3D"font-family: Cambria;"><br class=3D"">
</div>
<div class=3D"" style=3D"font-family: Cambria;">---</div>
<div class=3D"" style=3D"font-family: Cambria;"><br class=3D"">
</div>
<div class=3D"" style=3D"font-family: Cambria;">Joe's bio:</div>
<div class=3D"" style=3D"font-family: Cambria;"><br class=3D"">
</div>
<div class=3D"" style=3D"font-family: Cambria;">Joe Abley has been working =
in some form or other in the general area of Internet architecture and oper=
ations since graduating from the University of Cambridge in the UK in the e=
arly 90s. Originally from New Zealand,
 he now lives in Canada where he helps run Snake Hill Labs, a small consult=
ing company that helps clients solve Internet infrastructure problems with =
particular reference to the DNS. Joe has held engineering and technical man=
agement roles at companies such
 as AboveNet, ISC, Afilias, TekSavvy, ICANN and Dyn.</div>
<div class=3D"" style=3D"font-family: Cambria;"><br class=3D"">
</div>
<div class=3D"" style=3D"font-family: Cambria;">Joe has served on various c=
ommittees with regional Network Operator Groups over the years, was one of =
the original enthusiasts behind the Auckland Peering Exchange and has worke=
d for many years with the Network Startup
 Resource Center (NSRC) on technical capacity building in developing econom=
ies. At the IETF, Joe has volunteered as Executive Director for the IAB, co=
-authored fifteen RFCs and was one-time co-chair of the OpSec working group=
.</div>
</div>
<div><br>
</div>
</body>
</html>

--_000_D5719BE21D9991brownisocorg_--


From nobody Thu Jun 22 13:30:12 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 111B31293EE for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 13:30:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T_Aq4L3-3zlV for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 13:30:09 -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 1C2B912714F for <ietf@ietf.org>; Thu, 22 Jun 2017 13:30:09 -0700 (PDT)
Received: from [128.9.184.190] ([128.9.184.190]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v5MKTo5m010330 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 22 Jun 2017 13:29:51 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu> <8e8d4db9-93fd-5092-68de-6d8de44151c3@nic.cz>
From: Joe Touch <touch@isi.edu>
Message-ID: <c9202a09-af8b-faf6-b583-694378022dae@isi.edu>
Date: Thu, 22 Jun 2017 13:29:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <8e8d4db9-93fd-5092-68de-6d8de44151c3@nic.cz>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
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/CE13IEWFY69jCzmWydtK8ziyuvA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 20:30:11 -0000

On 6/19/2017 10:48 PM, Petr Špaček wrote:
>
> On 18.6.2017 20:09, Joe Touch wrote:
>> ...
>> You're asking for 10,000 page specifications and 10MB protocol
> We do not understand each other here. Let me explain what I meant in
> different terms:
>
> For purpose of this example, please imagine that protocol description
> (and sometimes also implementation) is a finite state automata.
>
> Right now, if a edge in the automata is not defined as result of
> protocol under-specification, it is up to implementation to decide what
> to do, 
I agree. A complete FSM specification, including specific actions for
all undefined combinations of state and input, is what I suggest might
be 10,000 pages and result in a 10MB implementation.
> i.e. implementation has to guess sender's intent.
The Postel Principle provides guidance here. The implementation isn't
supposed to guess the other side's intent - it's supposed to consider
(in some sense) any possible other side intent and act as safely as
possible. This is why I think it helps to refer to Shannon/Weaver, who
take intent out of the picture.

> This "guess" part is where I see problems because various
> implementations naturally differ in their "guesses" and this is causing
> problems later on.
The Postel Principle, IMO, is about agnosticism. If there is more than
one way to interpret a received message, then consider that before
reacting, and react safely (conservatively).

> I argue that default action triggered by "imagined missing edge" in our
> hypothetical protocol automata should be "report protocol specific error
> to sender".
A missing edge in a protocol spec isn't defined as an error unless the
spec says exactly that. So reporting that edge as an error otherwise
would be wrong.

> This could be done by adding ~ two paragraphs to protocol specification.
> One defining how error message looks like (this is already present in
> e.g. DNS spec as FORMERR) and second explaining that non-defined inputs
> should be treated as errors.
That would result in a very vulnerable protocol, and a good reason why
protocol specifications do not say this.

The most correct thing a protocol FSM could do when receiving an
undefined input is to DO NOTHING. Logging or user reporting might be
useful when debugging, but there is no part of the TCP API that
specifies that all errors are to be reported to the user.

>  Implementations always has to have some
> code to handle erroneous inputs (ala switch { default: } ) as well.
> I cannot see the 10 MB of code here.
You're correct that adding a "simple" default to report all undefined
inputs would be easy to code, but then you'd have to consider code to do
the reporting, to throttle the reporting when load gets high, etc.
Things get complicated quickly.


>
>> implementations that are vulnerable to attack.
> Could you elaborate on that? I still do not see how early error
> reporting invites DoS. In fact I believe that is is improving overall
> situation because smaller set of accepted inputs makes it easier to
> handle corner cases and to avoid crash bugs.

Turn on error full error logging in any kernel and watch performance
drop. Writing messages is a non-zero cost of cycles, storage, and memory
bandwidth. If you report every unexpected message, you're putting up a
very large attack surface - I just have to send you a series of
unexpected messages repeatedly and your system will grind to a halt.

>>> Nice set of reasons for being strict when receiving messages is
>>> described in the following article:
>>>
>>> "A Patch for Postel's Robustness Principle",
>>> Len Sassaman, Meredith L. Patterson, Sergey Bratus,
>>> 2012 IEEE S&P Journal,
>>> http://langsec.org/papers/postel-patch.pdf
>> I would encourage them to read Shannon/Weaver as well.
> (copied from Message-ID: <3a0a263f-f3b4-1931-3c49-4fa1526658e5@isi.edu>)
>> IMO, it's somewhat an extension of Shannon's recognition that
>> communication is about symbol agreement, not semantics or intent.
> We have tried to be liberal in DNS protocol in last 25 years. It
> resulted in humongous mess which in the end forces sender to do multiple
> guesses until he finds meaning of particular "symbol" for that
> particular "receiver". 

IMO, you're overdoing the "liberal in what you receive". Liberal means
that if it's possibly valid, you should accept it as such. It does not
mean that all ambiguous messages need to be handled in the best possible
light.

Let's say that DNS says "all domains are lowercase, dash, and dot", and
you get uppercase. Sure, maybe that means convert to lowercase. It also
means you should not crash if you get some other character that isn't
valid - but it also does not mean that you strip invalid characters and
provide a response anyway. Maybe a trailing CR, LF, NL, etc., but not
much else.

So if that's the point, I do agree - it's possible to overdo the Postel
Principle, but IMO that usually requires deliberate intent to make a
mockery of what is otherwise a generally useful principle.

Joe


From nobody Thu Jun 22 13:53:24 2017
Return-Path: <iab-chair@iab.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 A0BF312869B; Thu, 22 Jun 2017 13:53:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.899
X-Spam-Level: 
X-Spam-Status: No, score=-2.899 tagged_above=-999 required=5 tests=[ALL_TRUSTED=-1, BAYES_00=-1.9, HTML_MESSAGE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XfFyvwi7Jl46; Thu, 22 Jun 2017 13:53:20 -0700 (PDT)
Received: from thornhill.mtv.corp.google.com (unknown [IPv6:2620:0:1000:4200:9151:c8f9:67fc:ff95]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id A2C3512420B; Thu, 22 Jun 2017 13:53:20 -0700 (PDT)
To: iab@iab.org, ietf-announce@ietf.org, ietf@ietf.org
From: IAB Chair <iab-chair@iab.org>
Subject: Call for Participation, Workshop on Internet naming systems
Message-ID: <9afa1487-e1f7-8758-7ead-ab8114b822ed@iab.org>
Date: Thu, 22 Jun 2017 13:53:20 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------6467FA8D96CB5DD811613044"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4KcLr0LboQb6DGbUDCGJby2QyGI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 20:53:23 -0000

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

Call for Participation

IAB workshop on Explicit Internet Naming Systems

Internet namespaces relyon Internet connected systems sharing a common 
set of assumptions on the scope, method of resolution, and uniqueness of 
the names.    That set of assumption allowed the creation of URIs and 
other systems which presumed that you could authoritatively identify a 
service using an Internet name, a service port, and a set of 
locally-significant path elements.

There are now multiple challenges to maintaining that commonality of 
understanding.

  * Some naming systems wish to use URIs to identify both a service and
    the method of resolution used to map the name to a serving node.
      Because there is no common facility for varying the resolution
    method in the URI structure, those naming systems must either mint
    new URI schemes for each resolution service or infer the resolution
    method from a reserved name or pattern.  Both methods are currently
    difficult and costly, and the effort thus scales poorly.
  * Users’ intentions to refer to specific names are now often expressed
    in voice input, gestures, and other methods which must be
    interpreted before being put into practice.  The systems which carry
    on that interpretation often infer which intent a user is
    expressing, and thus what name is meant, by contextual elements.
      Those systems are linked to existing systems who have no access to
    that context and which may thus return results or create security
    expectations for an unintended name.

  * Unicode allows for both combining characters and composed characters
    when local language communities have different practices.  When
    these do not have a single normalization, context is required to
    determine which to produce or assume in resolution.  How can this
    context be maintained in Internet systems?

While any of these challenges could easily be the topic of a stand-alone 
effort, this workshop seeks to explore whether there is a common set of 
root problems in the explicitness of the resolution context, heuristic 
derivation of intent, or language matching. If so, it seeks to identify 
promising areas for the development of new, more explicit naming systems 
for the Internet.

We invite position papers on this topic to be submitted by July 28, 2017 
toename@iab.org <mailto:ename@iab.org>.    Decisions on accepted 
submissions will be made by August 11, 2017.

Proposed dates for the workshop are September 28th and 29th, 2017 and 
the proposed location is in the Pacific North West of North America. 
  Finalized logistics will be announced prior to the deadline for 
submissions.

Ted Hardie

for the IAB



--------------6467FA8D96CB5DD811613044
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 class="c1" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;">Call for
        Participation</span></p>
    <p class="c1" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span>IAB
        workshop on Explicit Internet Naming Systems</span></p>
    <p class="c1 c2" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      height: 11pt; font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;"></span></p>
    <p class="c1" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span>Internet
        namespaces rely<span> </span></span><span class="c0"
        style="color: rgb(0, 0, 0); font-weight: 400; text-decoration:
        none; vertical-align: baseline; font-size: 11pt; font-family:
        Arial; font-style: normal;">on Internet connected systems
        sharing a common set of assumptions on the scope, method of
        resolution, and uniqueness of the names.    That set of
        assumption allowed the creation of URIs and other systems which
        presumed that you could authoritatively identify a service using
        an Internet name, a service port, and a set of
        locally-significant path elements.  </span></p>
    <p class="c1 c2" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      height: 11pt; font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;"></span></p>
    <p class="c1" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;">There are now
        multiple challenges to maintaining that commonality of
        understanding.  </span></p>
    <p class="c1 c2" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      height: 11pt; font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;"></span></p>
    <ul class="c3 lst-kix_vlchuldijmo2-0 start" style="padding: 0px;
      margin: 0px; list-style-type: none; color: rgb(0, 0, 0);
      font-family: &quot;Times New Roman&quot;; font-size: medium;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; orphans: 2; text-align: start; text-indent: 0px;
      text-transform: none; white-space: normal; widows: 2;
      word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;">
      <li class="c4" style="color: rgb(0, 0, 0); font-size: 11pt;
        font-family: Arial; margin-left: 36pt; padding-top: 0pt;
        padding-left: 0pt; padding-bottom: 10pt; line-height: 1.15;
        orphans: 2; widows: 2; text-align: left;"><span class="c0"
          style="color: rgb(0, 0, 0); font-weight: 400; text-decoration:
          none; vertical-align: baseline; font-size: 11pt; font-family:
          Arial; font-style: normal;">Some naming systems wish to use
          URIs to identify both a service and the method of resolution
          used to map the name to a serving node.  Because there is no
          common facility for varying the resolution method in the URI
          structure, those naming systems must either mint new URI
          schemes for each resolution service or infer the resolution
          method from a reserved name or pattern.  Both methods are
          currently difficult and costly, and the effort thus scales
          poorly.</span></li>
      <li class="c4" style="color: rgb(0, 0, 0); font-size: 11pt;
        font-family: Arial; margin-left: 36pt; padding-top: 0pt;
        padding-left: 0pt; padding-bottom: 10pt; line-height: 1.15;
        orphans: 2; widows: 2; text-align: left;"><span class="c0"
          style="color: rgb(0, 0, 0); font-weight: 400; text-decoration:
          none; vertical-align: baseline; font-size: 11pt; font-family:
          Arial; font-style: normal;">Users’ intentions to refer to
          specific names are now often expressed in voice input,
          gestures, and other methods which must be interpreted before
          being put into practice.  The systems which carry on that
          interpretation often infer which intent a user is expressing,
          and thus what name is meant, by contextual elements.  Those
          systems are linked to existing systems who have no access to
          that context and which may thus return results or create
          security expectations for an unintended name.</span></li>
    </ul>
    <ul class="c3 lst-kix_ykgz29z81s2h-0 start" style="padding: 0px;
      margin: 0px; list-style-type: none; color: rgb(0, 0, 0);
      font-family: &quot;Times New Roman&quot;; font-size: medium;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; orphans: 2; text-align: start; text-indent: 0px;
      text-transform: none; white-space: normal; widows: 2;
      word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;">
      <li class="c4" style="color: rgb(0, 0, 0); font-size: 11pt;
        font-family: Arial; margin-left: 36pt; padding-top: 0pt;
        padding-left: 0pt; padding-bottom: 10pt; line-height: 1.15;
        orphans: 2; widows: 2; text-align: left;"><span class="c0"
          style="color: rgb(0, 0, 0); font-weight: 400; text-decoration:
          none; vertical-align: baseline; font-size: 11pt; font-family:
          Arial; font-style: normal;">Unicode allows for both combining
          characters and composed characters when local language
          communities have different practices.  When these do not have
          a single normalization, context is required to determine which
          to produce or assume in resolution.  How can this context be
          maintained in Internet systems?</span></li>
    </ul>
    <p class="c1 c2" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      height: 11pt; font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;"></span></p>
    <p class="c1" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;">While any of
        these challenges could easily be the topic of a stand-alone
        effort, this workshop seeks to explore whether there is a common
        set of root problems in the explicitness of the resolution
        context, heuristic derivation of intent, or language matching.  
        If so, it seeks to identify promising areas for the development
        of new, more explicit naming systems for the Internet.</span></p>
    <p class="c1 c2" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      height: 11pt; font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;"></span></p>
    <p class="c1" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span>We
        invite position papers on this topic to be submitted by July 28,
        2017 to<span> </span></span><span class="c8" style="color:
        rgb(17, 85, 204); text-decoration: underline;"><a class="c6"
          href="mailto:ename@iab.org" style="color: inherit;
          text-decoration: inherit;">ename@iab.org</a></span><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;">.    Decisions on
        accepted submissions will be made by August 11, 2017.</span></p>
    <p class="c1 c2" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      height: 11pt; font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;"></span></p>
    <p class="c1" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;">Proposed dates
        for the workshop are September 28th and 29th, 2017 and the
        proposed location is in the Pacific North West of North America.
         Finalized logistics will be announced prior to the deadline for
        submissions.</span></p>
    <p class="c1 c2" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      height: 11pt; font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;"></span></p>
    <p class="c1" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;">Ted Hardie</span></p>
    <p class="c1" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;">for the IAB</span></p>
    <p class="c1 c2" style="margin: 0px; color: rgb(0, 0, 0); font-size:
      11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt;
      line-height: 1.15; orphans: 2; widows: 2; text-align: left;
      height: 11pt; font-style: normal; font-variant-ligatures: normal;
      font-variant-caps: normal; font-weight: normal; letter-spacing:
      normal; text-indent: 0px; text-transform: none; white-space:
      normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      text-decoration-style: initial; text-decoration-color: initial;"><span
        class="c0" style="color: rgb(0, 0, 0); font-weight: 400;
        text-decoration: none; vertical-align: baseline; font-size:
        11pt; font-family: Arial; font-style: normal;"><br>
      </span></p>
  </body>
</html>

--------------6467FA8D96CB5DD811613044--


From nobody Thu Jun 22 14:14:41 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 53F4312945E; Thu, 22 Jun 2017 14:14:40 -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: webpush@ietf.org, ietf@ietf.org, draft-ietf-webpush-vapid.all@ietf.org
Subject: Genart last call review of draft-ietf-webpush-vapid-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149816608028.23068.7975099108704386725@ietfa.amsl.com>
Date: Thu, 22 Jun 2017 14:14:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/dZlLXnukswFpM1w6EXPkm5h-bEM>
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, 22 Jun 2017 21:14:40 -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-webpush-vapid-??
Reviewer: Joel Halpern
Review Date: 2017-06-22
IETF LC End Date: 2017-07-03
IESG Telechat date: Not scheduled for a telechat

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 Thu Jun 22 15:43:49 2017
Return-Path: <sesale@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 15C9C129496; Thu, 22 Jun 2017 15:43:30 -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_H4=-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 VH8RO4rlcQQn; Thu, 22 Jun 2017 15:43:27 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0098.outbound.protection.outlook.com [104.47.41.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DA49127868; Thu, 22 Jun 2017 15:43:24 -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=3oZKMAHgnUcNOd4hk+vsu5Wp1R4P6iaHYo3Y1DAM4f4=; b=G8Kd/iPi4QHeRmSD/GjNloQYEL4aH9sJBJc0WZNIZkcHfuq3NgKcRYmmN9aBhSBtJBckbKd1MBymPSCGGtmmQsgVVu0hJk5UAzKsiNDg1su9hN20UlAgZ5lxPCI/n4rqs9oWeoNTeIZPfUXON4CHCo4SVoZgErGyR9Cn5kkCOeE=
Received: from CO2PR05MB2774.namprd05.prod.outlook.com (10.166.200.26) by CO2PR05MB2712.namprd05.prod.outlook.com (10.166.200.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1178.10; Thu, 22 Jun 2017 22:43:22 +0000
Received: from CO2PR05MB2774.namprd05.prod.outlook.com ([10.166.200.26]) by CO2PR05MB2774.namprd05.prod.outlook.com ([10.166.200.26]) with mapi id 15.01.1178.023; Thu, 22 Jun 2017 22:43:22 +0000
From: Santosh Esale <sesale@juniper.net>
To: Yoav Nir <ynir.ietf@gmail.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "mpls@ietf.org" <mpls@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "BRUNGARD, DEBORAH A" <db3546@att.com>, "draft-ietf-mpls-app-aware-tldp.all@ietf.org" <draft-ietf-mpls-app-aware-tldp.all@ietf.org>
Subject: Re: Secdir last call review of draft-ietf-mpls-app-aware-tldp-08
Thread-Topic: Secdir last call review of draft-ietf-mpls-app-aware-tldp-08
Thread-Index: AQHS4KDQZGAu47rNb06vXUX2WNUYyKIxG0oA
Date: Thu, 22 Jun 2017 22:43:22 +0000
Message-ID: <D57167EA.F0905%sesale@juniper.net>
References: <149695844237.15142.17304755568511932911@ietfa.amsl.com>
In-Reply-To: <149695844237.15142.17304755568511932911@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/14.7.0.161029
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=juniper.net;
x-originating-ip: [66.129.241.14]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CO2PR05MB2712; 7:zPg/aRa9PQ6EjbAn1rptM8EEkl25dn7rbwOwy9eL87yBany9y5/0/3G2xl17WvmVbHrXi9D4+9nqUoggHfSdGXlUFZrYPSVlu7WWoloduz6JU1hCt0MVl4GHzJIaqDeqsI0cKrKs0jK8SEF+kojFwNc1b1yPGfpQ9LXN+DTfGFvJiHOKzuCwXpCAdRGdUqInHP1GstP1eTsU2W6Uzfuloeu6mLMzhSfMeigR6dEuSw7rUpGascXSuYHZtrJId+NgNJgqNQqpEhXugCQbrH4R1TC7Cl7rMzhMVP06eFbTTkoerB3P/Dm1KtRoz9CrIYQIOco87cbYabUJqZon+u5ymm0dQtNA22/D2fev4PtRm5WJj6l2p6fBocarR8xRyf9N3eYRKf4BkhGYH+BbS+UP81YT2fzTaMVB1WqavrONNCFc4HaKKYUPL01S36DDxhnWhfA7XukYSkv8eO8kR5TGNF61zTebPwhPcjvz9ORfreO/qO9zh5s60J42FrTEO/9768R6mtyWss/0WDi+Z3bs0l3INUTHMWmqD3UelyTQJ3iUPDjVDMHdilAWtckVsuttjtDrYmf4QpHrbQgXXDE6Ya2QGDt//DDSVRND57OP6Wm2tgvXPWpORjf6FHWOvnZ3DzxfAetcRnEg/5SFhwbu9LNtnzz+6aEqVTEz/CtnF0XtEtMoxfyU8ZCZVz6N73N8zqg/C+bnJn85+RAtyb+L12UNH20LlB4KGkTefK9J4VaW2sSD4ROC+V2HekmHJUhYUe1LGvaKn8f6zBcXXmxZC4gYxVpy8o0C10u8AIu8OCY=
x-ms-office365-filtering-correlation-id: f268fd6a-9ff5-415c-b7e2-08d4b9c0162c
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:CO2PR05MB2712; 
x-ms-traffictypediagnostic: CO2PR05MB2712:
x-microsoft-antispam-prvs: <CO2PR05MB2712FA4DCADB5EB4490B0ACBD9DB0@CO2PR05MB2712.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278428928389397)(192374486261705);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(100000703101)(100105400095)(93006095)(93001095)(6055026)(6041248)(20161123555025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(20161123564025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:CO2PR05MB2712; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:CO2PR05MB2712; 
x-forefront-prvs: 03468CBA43
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39400400002)(39410400002)(39840400002)(39850400002)(39450400003)(39860400002)(24454002)(377454003)(122556002)(54356999)(76176999)(50986999)(38730400002)(39060400002)(2900100001)(54906002)(189998001)(6246003)(6512007)(305945005)(345774005)(53546010)(53936002)(25786009)(229853002)(8936002)(2906002)(8676002)(81166006)(3846002)(83506001)(6506006)(5660300001)(478600001)(4001350100001)(14454004)(2950100002)(6116002)(36756003)(102836003)(3280700002)(6436002)(230783001)(66066001)(4326008)(99286003)(2501003)(77096006)(3660700001)(7736002)(86362001)(6486002); DIR:OUT; SFP:1102; SCL:1; SRVR:CO2PR05MB2712; H:CO2PR05MB2774.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <18E78FFDEF8011419B26FF1F80A43B53@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Jun 2017 22:43:22.2190 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR05MB2712
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tZZ3Vxvs3kW_SJjqX68d16R9MvU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 22 Jun 2017 22:43:30 -0000

SGkgWW9hdiwNCiAgICAgICBUaGFuayB5b3UgZm9yIHRoZSByZXZpZXcuIFBsZWFzZSBmaW5kIGNv
bW1lbnRzIGlubGluZS4NCg0KT24gNi84LzE3LCAyOjQ3IFBNLCAiWW9hdiBOaXIiIDx5bmlyLmll
dGZAZ21haWwuY29tPiB3cm90ZToNCg0KPlJldmlld2VyOiBZb2F2IE5pcg0KPlJldmlldyByZXN1
bHQ6IEhhcyBOaXRzDQo+DQo+SSBoYXZlIHJldmlld2VkIHRoaXMgZG9jdW1lbnQgYXMgcGFydCBv
ZiB0aGUgc2VjdXJpdHkgZGlyZWN0b3JhdGUncw0KPm9uZ29pbmcNCj5lZmZvcnQgdG8gcmV2aWV3
IGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cuIFRoZXNlDQo+
Y29tbWVudHMNCj53ZXJlIHdyaXR0ZW4gcHJpbWFyaWx5IGZvciB0aGUgYmVuZWZpdCBvZiB0aGUg
c2VjdXJpdHkgYXJlYSBkaXJlY3RvcnMuDQo+RG9jdW1lbnQNCj5lZGl0b3JzIGFuZCBXRyBjaGFp
cnMgc2hvdWxkIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZSBhbnkgb3RoZXINCj5sYXN0
IGNhbGwNCj5jb21tZW50cy4NCj4NCj5NeSBiaWdnZXN0IGlzc3VlIHdpdGggdGhpcyBkb2N1bWVu
dCBpcyB0aGF0IGl0IGlzIGhhcmQgdG8gcmVhZC4gIEZvcg0KPmV4YW1wbGUsDQo+dGhlIEludHJv
ZHVjdGlvbiBleHBhbmRzIHRMRFAgdG8gInRhcmdldGVkIExEUCIsIGFuZCB0aGUgSW50cm9kdWN0
aW9uDQo+YmVnaW5zDQo+d2l0aCAiTERQIHVzZXMgZXh0ZW5kZWQgZGlzY292ZXJ5Li4uIiwgYnV0
IExEUCBpdHNlbGYgaXMgb25seSBleHBhbmRlZCB0bw0KPiJsYWJlbCBkaXN0cmlidXRpb24gcHJv
dG9jb2wiIGluIHRoZSBJQU5BIGNvbnNpZGVyYXRpb25zIHNlY3Rpb24uDQoNClVwZGF0ZWQgdGV4
dCBhcyDigJxSZWNlbnQgdGFyZ2V0ZWQgTGFiZWwgRGlzdHJpYnV0aW9uIFByb3RvY29sICh0TERQ
KQ0KYXBwbGljYXRpb25zIC4uIg0KDQo+U2ltaWxhcmx5LA0KPnRoZSBtdWNoLW92ZXJsb2FkZWQg
dGVybSAiYXBwbGljYXRpb24iIGlzIG5ldmVyIGV4cGxhaW5lZCBleGNlcHQgdGhhdCBzb21lDQo+
YXBwbGljYXRpb25zIGFyZSAidGFyZ2V0ZWQiIGFuZCB0aGF0ICJGRUMgMTI4IHBzZXVkb3dpcmUi
IGlzIGFuIGV4YW1wbGUNCj5vZiBhbg0KPmFwcGxpY2F0aW9uLiAgSSBhbSBzdXJlIHRoaXMgbWFr
ZXMgc2Vuc2UgdG8gcGFydGljaXBhbnRzIG9mIHRoZSBNUExTDQo+d29ya2luZw0KPmdyb3VwLCBi
dXQgdG8gb3RoZXJzIHRoaXMgaXMgbXVjaCBoYXJkZXIuIFRoZXJlIG5lZWRzIHRvIGJlIGF0IGxl
YXN0IGENCj5yZWZlcmVuY2UgdG8gUkZDIDUwMzYgd2hlcmUgdGhlc2UgdGVybXMgYXJlIGJldHRl
ciBleHBsYWluZWQgKFJGQyA1MDM2IGlzDQo+cmVmZXJlbmNlZCBidXQgb25seSBhcyB0aGUgZG9j
dW1lbnQgd2hlcmUgdExEUCBhZGphY2VuY3kgaXMgZGVzY3JpYmVkKS4NCg0KUmVmZXJlbmNlZCBS
RkM1MDM2IGluIHRoZSBzZWNvbmQgcGFyYWdyYXBoIHRoYXQgaW50cm9kdWNlcyB0aGUgYXBwbGlj
YXRpb24NCmtleXdvcmQuDQoiQXBwbGljYXRpb25zIFtSRkM1MDM2XSBzdWNoIGFzIFJlbW90ZSBM
RkEgYW5kIEJHUCBhdXRvIGRpc2NvdmVyZWTigKYiDQo+DQo+Tml0czoNCj5UaGUgU2VjdXJpdHkg
Q29uc2lkZXJhdGlvbnMgc2VjdGlvbiBiZWdpbnMgd2l0aCAiVGhlIENhcGFiaWxpdHkgcHJvY2Vk
dXJlDQo+ZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1lbnQgd2lsbCBhcHBseSBhbmQgZG9lcyBub3Qg
aW50cm9kdWNlIGFueSBjaGFuZ2UNCj50byBMRFANCj5TZWN1cml0eSBDb25zaWRlcmF0aW9ucyIu
ICBUaGUgcHJvY2VkdXJlIHdpbGwgYXBwbHkgd2hhdD8gIE9yIHdpbGwgYXBwbHkNCj50bw0KPndo
YXQ/ICBJIHRoaW5rIHRoZSB3b3JkcyAid2lsbCBhcHBseSBhbmQiIGFyZSBzdXBlcmZsdW91cy4N
Cg0KQ29ycmVjdCA6KSBSZW1vdmVkLiBOb3cgaXQgcmVhZHMgYXMgIlRoZSBDYXBhYmlsaXR5IHBy
b2NlZHVyZSBkZXNjcmliZWQgaW4NCnRoaXMgDQpkb2N1bWVudCBkb2VzIG5vdCBpbnRyb2R1Y2Ug
YW55IGNoYW5nZSB0by4uIg0KPg0KPlRoZSBzZWNvbmQgcGFyYWdyYXBoIHNlZW1zIHRvIGJlIHJl
cGVhdGluZyBwYXJ0IG9mIHRoZSAocmF0aGVyIGV4dGVuc2l2ZSkNCj5zZWN1cml0eSBjb25zaWRl
cmF0aW9ucyBvZiBSRkMgNTAzNiwgYnV0IGl0IGRvZXMgbm90IHNheSB3aHkgKG9yIGV2ZW4NCj53
aGV0aGVyKQ0KPnRoYXQgcGFydGljdWxhciBhbnRpLURvUyBtZWFzdXJlIGFwcGxpZXMgaW4gcGFy
dGljdWxhciB0byB0aGUgbWVjaGFuaXNtDQo+ZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1lbnQuIElP
VyB3aHkgaXMgdGhpcyBtZWFzdXJlIHNpbmdsZWQgb3V0IGZyb20NCj5hbW9uZyB0aGUNCj50aHJl
ZSBwYWdlcyBvZiBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyBmcm9tIFJGQyA1MDM2Pw0KDQpUaGlz
IHBhcnQgb2Ygc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgaXMgcmVwZWF0ZWQgYXMgaXQgaXMgcmVs
YXRlZCB0bw0KZXh0ZW5kZWQgDQpoZWxsb3MgdGhhdCBhcmUgcmVxdWlyZWQgdG8gZXN0YWJsaXNo
IHRMRFAgc2Vzc2lvbi4gVGhlIG1lY2hhbmlzbQ0KZGVzY3JpYmVkIGluIA0KdGhpcyBkb2N1bWVu
dCB1cGRhdGVzIHRMRFAgc2Vzc2lvbiBlc3RhYmxpc2htZW50IHByb2NlZHVyZXMuIFRoZSB0ZXh0
IGlzDQp1cGRhdGVkDQp0byBjb3ZleSB0aGUgaW50ZW50aW9uLg0KDQo+VGhlIHRoaXJkIHBhcmFn
cmFwaCBpcyBub3QgY2xlYXIgdG8gbWUuIEl0IHRhbGtzIGFib3V0IHR3byBub2RlcyBub3QNCj5l
c3RhYmxpc2hpbmcgYSB0TERQIHNlc3Npb24gaWYgdGhleSBkb24ndCBzdXBwb3J0IHRoZSBzYW1l
IGFwcGxpY2F0aW9uLiBJDQo+ZG9uJ3QNCj5rbm93IHdoeSB0aGF0IGJlbG9uZ3MgaW4gdGhlIHNl
Y3VyaXR5IGNvbnNpZGVyYXRpb25zIHNlY3Rpb24uIFRoZSBTSE9VTEQNCj5OT1QNCj4oZXN0YWJs
aXNoIGEgc2Vzc2lvbikgbWFuZGF0ZSBkZWZpbml0ZWx5IGRvZXMgbm90IGJlbG9uZyB0aGVyZS4N
Cg0KUmVtb3ZlZCB0aGUgZW50aXJlIGxpbmUgdGhhdCBzdGF0ZWQgdGhlICdTSE9VTEQgTk9UIHBh
cnQnLiBBZ3JlZSwgdGhhdA0KdGV4dCANCmRvZXMgbm90IGJlbG9uZyBoZXJlLiBUaGUgdGhpcmQg
cGFyYWdyYXBoIGlzIGFkZGVkIHRvIGFkZHJlc3MgQnJ1bm/igJlzDQpjb21tZW50cyANCmR1cmlu
ZyByb3V0aW5nIGRpcmVjdG9yYXRlIHJldmlldy4gVGhlIGludGVudGlvbiBpcyB0byBzdGF0ZSBj
bGVhcmx5IC0gVGhlDQpJbml0aWF0aW5nIGFuZCByZWNlaXZpbmcgTFNSIE1VU1Qgb25seSBhZHZl
cnRpc2UgVEEtSWRzIHRoYXQgdGhleSBzdXBwb3J0Lg0KDQpUaGUgdXBkYXRlZCBzZWN1cml0eSBw
YXJhZ3JhcGggcmVhZHMgYXMgZm9sbG93cyAtDQoNCiAgVGhlIENhcGFiaWxpdHkgcHJvY2VkdXJl
IGRlc2NyaWJlZCBpbiB0aGlzIGRvY3VtZW50IGRvZXMgbm90DQogICBpbnRyb2R1Y2UgYW55IGNo
YW5nZSB0byBMRFAgU2VjdXJpdHkgQ29uc2lkZXJhdGlvbnMgc2VjdGlvbiBkZXNjcmliZWQNCmlu
IFtSRkM1MDM2XS4NCg0KICAgQXMgZGVzY3JpYmVkIGluIFtSRkM1MDM2XSwgRG9TIGF0dGFja3Mg
dmlhIEV4dGVuZGVkIEhlbGxvcywgd2hpY2ggYXJlDQogICByZXF1aXJlZCB0byBlc3RhYmxpc2gg
YSB0TERQIHNlc3Npb24sIGNhbiBiZSBhZGRyZXNzZWQgYnkgZmlsdGVyaW5nDQogICBFeHRlbmRl
ZCBIZWxsb3MgdXNpbmcgYWNjZXNzIGxpc3RzIHRoYXQgZGVmaW5lIGFkZHJlc3NlcyB3aXRoIHdo
aWNoDQogICBFeHRlbmRlZCBEaXNjb3ZlcnkgaXMgcGVybWl0dGVkLiAgRnVydGhlciwgYXMgZGVz
Y3JpYmVkIGluIHNlY3Rpb24NCiAgIDUuMiBvZiB0aGlzIGRvY3VtZW50LCBhIExTUiBjYW4gZW1w
bG95IGEgcG9saWN5IHRvIGFjY2VwdCBhbGwgYXV0by0NCiAgIGRpc2NvdmVyZWQgRXh0ZW5kZWQg
SGVsbG9zIGZyb20gdGhlIGNvbmZpZ3VyZWQgc291cmNlIGFkZHJlc3Nlcw0KICAgbGlzdC4NCg0K
ICAgQWxzbyBmb3IgdGhlIHR3byBMU1JzIHN1cHBvcnRpbmcgVEFDLCB0aGUgdExEUCBzZXNzaW9u
IGlzIG9ubHkNCiAgIGVzdGFibGlzaGVkIGFmdGVyIHN1Y2Nlc3NmdWwgbmVnb3RpYXRpb24gb2Yg
dGhlIFRBQy4gVGhlIGluaXRpYXRpbmcNCiAgIGFuZCByZWNlaXZpbmcgTFNSIE1VU1Qgb25seSBh
ZHZlcnRpc2UgVEEtSWRzIHRoYXQgdGhleSBzdXBwb3J0LiBJbg0KICAgb3RoZXIgd29yZHMsIHdo
YXQgdGhleSBhcmUgY29uZmlndXJlZCBmb3Igb3ZlciB0aGUgdExEUCBzZXNzaW9uLg0KDQoNClRo
YW5rcywNClNhbnRvc2ggKE9uIGJlaGFsZiBvZiBBdXRob3JzKQ0KPg0KPg0KDQo=


From nobody Thu Jun 22 16:02:40 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 1BBBA127873; Thu, 22 Jun 2017 16:02:39 -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-sipcore-content-id.all@ietf.org, sipcore@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-ietf-sipcore-content-id-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149817255908.17071.14195524382332366327@ietfa.amsl.com>
Date: Thu, 22 Jun 2017 16:02:39 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7tHyEFPVAzBPQx0IvSOoVRZfI2E>
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, 22 Jun 2017 23:02:39 -0000

Reviewer: Elwyn Davies
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please 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-sipcore-content-id-06
Reviewer: Elwyn Davies
Review Date: 2017-06-22
IETF LC End Date: 2017-06-27
IESG Telechat date: Not scheduled for a telechat

Summary:
Ready with nits.  There are a couple of minor issues related to the procedures
after inappropriate usage of the new header.

Major issues:
None

Minor issues:
s3.4.1, last para: In line with the last sentence of Section 3.2, the
Content-ID URL only needs to be unique within the SIP message where it occurs.
 I assume it does not make sense to have a Content-ID header combined with a
mutipart message-body (this isn't stated - maybe it should be); I am not
sufficiently knowledgeable in this area of SIP to know if there could be
content-id URLs in other headers if there is a Content-ID header in the
message.  Thus either the statement about global uniqueness is irrelevant (as
there is only one) and can be removed or it should be made consistent with s3.2
so that the Content URLs are unique within the message. Global uniqueness is
neither possible or required.

s3.4.1, para 1: Following on from the previous comment: Is a UA allowed to add
a Content-ID header to a message with a multipart message-body?

s3.4.1: What should a UA do if it receives a message with a Content-ID header
when the message is not allowed to contain one?  Is there some generic error
procedure that should be referenced?

s6.1: I started looking for specification that told me that items added to the
SIP header fields registry effectively extend the definition of the
message-header production in Section 25.1of RFC 3261.  Bit obvious perhaps, but
it would be nice if it had been said somewhere!  Time for an Erratum perhaps?

Nits/editorial comments:
Abstract:  I would suggest adding a sentence that clarifies what the update of
RFC 5621 is modifying: OLD: The document also updates RFC 5621, to enable a
Content-ID URL to reference a complete message-body and metadata provided by
some additional SIP header fields. NEW: The document also updates RFC 5621,
which only allows a Content-ID URL to reference a body-part that is part of a
multipart message-body.  This update enables a Content-ID URL to reference a
complete message-body and metadata provided by some additional SIP header
fields. END

s1.2, first bullet: s/for providing location/for providing location information/

s1.4.1: Need to expand UAC (User Agent Client) on first usage.

s1.4.1, para 1: s/can be e.g. of/can be, for example, of/

s3.4.1: Need to expand UA (User Agent) on first usage (in section title).

s4, NEW text: s/allow creating/allow the creation of/



From nobody Thu Jun 22 22:04:20 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 CB577129C12 for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 22:04:18 -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 wVRU9C7OylvD for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 22:04:16 -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 BDC31126C23 for <ietf@ietf.org>; Thu, 22 Jun 2017 22:04:16 -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 1dOGlL-0007He-RH; Fri, 23 Jun 2017 01:04:07 -0400
Date: Fri, 23 Jun 2017 01:04:00 -0400
From: John C Klensin <john-ietf@jck.com>
To: Joe Touch <touch@isi.edu>
cc: =?UTF-8?Q?Petr_=C5=A0pa=C4=8Dek?= <petr.spacek@nic.cz>, ietf@ietf.org
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
Message-ID: <56AAD497D44465073CA7B494@PSB>
In-Reply-To: <c9202a09-af8b-faf6-b583-694378022dae@isi.edu>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu> <8e8d4db9-93fd-5092-68de-6d8de44151c3@nic.cz> <c9202a09-af8b-faf6-b583-694378022dae@isi.edu>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Dketj0QJA8LeBWhY887Yq0WqZck>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 05:04:19 -0000

Joe,

I think we are in agreement -- we have been so far-- but let me
add a real world example that might help clarify some of  this.

--On Thursday, June 22, 2017 13:29 -0700 Joe Touch
<touch@isi.edu> wrote:

>...
>> We have tried to be liberal in DNS protocol in last 25 years.
>> It resulted in humongous mess which in the end forces sender
>> to do multiple guesses until he finds meaning of particular
>> "symbol" for that particular "receiver".=20

> IMO, you're overdoing the "liberal in what you receive".
> Liberal means that if it's possibly valid, you should accept
> it as such. It does not mean that all ambiguous messages need
> to be handled in the best possible light.

I would have been even more restrictive and said "possibly valid
and generally unambiguous".  Taking SMTP as an example, not just
because because it is one of the classic robustness principle
cases but because there is a long history of reasonable
applications of the principle and an equally long on of
unreasonable applications including situations in which senders
have claimed "be liberal about what you accept" allows them to
send complete nonsense and, if things then don't work, to claim
that is the receiver's fault (see my earlier comments about
common sense).

Prior to the introduction of the extension mechanism in RFC
1651, the spec said that the command that specifies recipients =
is
   RCPT TO:<forward-path>
Now, putting a space after the colon is a really common error.
The robustness principle is properly applied to just let that
go; there is no possible ambiguity about what was intended.  I
don't recall ever seeing "RCPTTO:", rather than "RCPT TO:", but
accepting it in the name of liberal acceptance would be
similarly reasonable although I'm not sure it would justify
redesigning a command parser just to allow it.

The question of whether the receiver should generate an error
reply if the brackets are omitted or should just assume them was
an argument that went back and forth for years.  It is an odd
case, because they are less easily overlooked in the specs than
someone not reading the BNF (821) or ABNF (2821 and 5321)
carefully enough.   But that is connected to another issue with
the robustness principle that I don't think has been discussed:

For some years, there were a few SMTP implementations around
that assumed that, since the syntax was as above, they could put
things into the command after the forward path and closing
bracket and have them treated as comments.  It got all the
predictable reactions: Some servers (receivers) just didn't
notice anything past the ">" and hence applied liberality in
acceptance accidentally.  Others applied it deliberately on the
assumption that ignoring noise was reasonable.   And still
others generated syntax replies, perhaps on the theory that
additional text might be an extra address or something else they
didn't know how to handle reliably.   Those choices needed to
come to an end with RFC 1651 because we needed to allow text
after the ">" for something specific.   That forced us to invent
a new session-starting verb rather than just dropping extra
syntax at the end, but that was (at least IMO) a relatively
small price to pay for giving receiver implementations (who
would be blamed, fairly or not, if messages didn't go through)
permission to use their judgment about how flexible to be.=20

=20
> Let's say that DNS says "all domains are lowercase, dash, and
> dot", and you get uppercase. Sure, maybe that means convert to
> lowercase. It also means you should not crash if you get some
> other character that isn't valid - but it also does not mean
> that you strip invalid characters and provide a response
> anyway. Maybe a trailing CR, LF, NL, etc., but not much else.

Somewhat in parallel with the SMTP case, it also doesn't mean
that, when "lowercase" doesn't automatically mean "lowercase
ASCII letters", that, in the general case, you don't get to
receive "=C3=A1" or "=C4=8D" and decide that the accent and =
caron are
superfluous so you can change them to, or interpret them as, "a"
and "c".    But, again, "be liberal" means to exercise
reasonable judgment about flexibility of interpretation.  It is
a requirement for thinking and understanding, not a requirement
that one be stupid or irresponsible.

> So if that's the point, I do agree - it's possible to overdo
> the Postel Principle, but IMO that usually requires deliberate
> intent to make a mockery of what is otherwise a generally
> useful principle.

Yep.

    john






From nobody Thu Jun 22 22:39:26 2017
Return-Path: <tobias.gondrom@gondrom.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 AD0BD126C0F for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 22:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, 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); domainkeys=pass (1024-bit key) header.from=tobias.gondrom@gondrom.org header.d=gondrom.org
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yQzCJFVYV_Lx for <ietf@ietfa.amsl.com>; Thu, 22 Jun 2017 22:39:23 -0700 (PDT)
Received: from gondrom.org (www.gondrom.org [5.35.241.16]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A9B6120721 for <ietf@ietf.org>; Thu, 22 Jun 2017 22:39:23 -0700 (PDT)
Received: from Galaxy-S6 (unknown [112.97.59.18]) by gondrom.org (Postfix) with ESMTPSA id 6CF3E64334; Fri, 23 Jun 2017 07:39:19 +0200 (CEST)
DomainKey-Signature: a=rsa-sha1;  q=dns; c=nofws; s=default; d=gondrom.org; b=N5MURKd+gIFT9Hx/wMngEkDxuN151g+3bJacusCG6d0WZcUEDYSv+G2iHCvQC6KM5ouHvNBB9iQzxApEgS67S2Wa0lRRZaq9NbtmY//Syf5k1E24mE3pfc3wh2LgxUiT3hZjBwIUWiugQlGcyCygmIlS/qezT4TdEOmrJGIsp60=; h=Date:User-Agent:In-Reply-To:References:MIME-Version:Content-Type:Content-Transfer-Encoding:Subject:To:CC:From:Message-ID;
Date: Fri, 23 Jun 2017 13:39:13 +0800
User-Agent: K-9 Mail for Android
In-Reply-To: <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----Q93WEDGHCS9O6XLNZ44DSBWMT454VT"
Content-Transfer-Encoding: 7bit
Subject: Re: Saturday as start day
To: ietf@ietf.org, Bob Hinden <bob.hinden@gmail.com>, Alissa Cooper <alissa@cooperw.in>
CC: IETF <ietf@ietf.org>
From: Tobias Gondrom <tobias.gondrom@gondrom.org>
Message-ID: <25CD3E0C-A03D-49A3-8375-AD4D834BF94B@gondrom.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_aIzJGKfA4lKO6IvGhZQKT9aOis>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 05:39:26 -0000

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

I also agree=2E This is good idea=2E
(with my individual hat on=2E=2E=2E ;-) )
Best regards, Tobias

On June 21, 2017 8:46:57 PM GMT+08:00, Bob Hinden <bob=2Ehinden@gmail=2Eco=
m> wrote:
>Alissa,
>
>> On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw=2Ein> wrote:
>>=20
>> Hi all,
>>=20
>> Based on a suggestion from Paul Hoffman, the IESG believes it would
>be beneficial to denote the official start of IETF meetings to be on
>Saturday rather than Sunday, starting with IETF 100=2E We believe this
>would be sensible given that events such as the hackathon and code
>sprint start on Saturday, and may make it easier for some participants
>to get travel approval to attend those events=2E This change would be
>reflected in the dates posted on the IETF web site and sent out in
>email announcements=2E We are not proposing any changes in terms of the
>scheduling of any meeting-related events, the full availability of the
>meeting network starting on Sunday, the opening of on-site
>registration, or the meeting fee=2E
>>=20
>
>I think this is a fine idea, essentially formalizing what has happened
>informally=2E  I suspect once in effect it will push the network to be
>deployed earlier, but given current Saturday events, that was also
>probably going to happen at some point=2E
>
>Thanks,
>Bob
>
>
>
>> If you have feedback about this change, please send it to
>ietf@ietf=2Eorg, or exceptionally to iesg@ietf=2Eorg, by July 5, 2017=2E
>>=20

--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E
------Q93WEDGHCS9O6XLNZ44DSBWMT454VT
Content-Type: text/html;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head></head><body>I also agree=2E This is good idea=2E<br>
(with my individual hat on=2E=2E=2E ;-) )<br>
Best regards, Tobias<br><br><div class=3D"gmail_quote">On June 21, 2017 8:=
46:57 PM GMT+08:00, Bob Hinden &lt;bob=2Ehinden@gmail=2Ecom&gt; wrote:<bloc=
kquote class=3D"gmail_quote" style=3D"margin: 0pt 0pt 0pt 0=2E8ex; border-l=
eft: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class=3D"k9mail">Alissa,<br /><br /><blockquote class=3D"gmail_quote"=
 style=3D"margin: 0pt 0pt 1ex 0=2E8ex; border-left: 1px solid #729fcf; padd=
ing-left: 1ex;"> On Jun 21, 2017, at 3:34 PM, Alissa Cooper &lt;alissa@coop=
erw=2Ein&gt; wrote:<br /> <br /> Hi all,<br /> <br /> Based on a suggestion=
 from Paul Hoffman, the IESG believes it would be beneficial to denote the =
official start of IETF meetings to be on Saturday rather than Sunday, start=
ing with IETF 100=2E We believe this would be sensible given that events su=
ch as the hackathon and code sprint start on Saturday, and may make it easi=
er for some participants to get travel approval to attend those events=2E T=
his change would be reflected in the dates posted on the IETF web site and =
sent out in email announcements=2E We are not proposing any changes in term=
s of the scheduling of any meeting-related events, the full availability of=
 the meeting network starting on Sunday, the opening of on-site registratio=
n, or the meeting fee=2E<br /> <br /></blockquote><br />I think this is a f=
ine idea, essentially formalizing what has happened informally=2E  I suspec=
t once in effect it will push the network to be deployed earlier, but given=
 current Saturday events, that was also probably going to happen at some po=
int=2E<br /><br />Thanks,<br />Bob<br /><br /><br /><br /><blockquote class=
=3D"gmail_quote" style=3D"margin: 0pt 0pt 1ex 0=2E8ex; border-left: 1px sol=
id #729fcf; padding-left: 1ex;"> If you have feedback about this change, pl=
ease send it to ietf@ietf=2Eorg, or exceptionally to iesg@ietf=2Eorg, by Ju=
ly 5, 2017=2E<br /> <br /></blockquote><br /></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E</=
body></html>
------Q93WEDGHCS9O6XLNZ44DSBWMT454VT--


From nobody Fri Jun 23 02:25:19 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 A63D112EABC for <ietf@ietfa.amsl.com>; Fri, 23 Jun 2017 02:25:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.127
X-Spam-Level: 
X-Spam-Status: No, score=-6.127 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] 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 ttLtNk-1BmBi for <ietf@ietfa.amsl.com>; Fri, 23 Jun 2017 02:25:16 -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 DA6E3129B3C for <ietf@ietf.org>; Fri, 23 Jun 2017 02:25:15 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.39,377,1493679600";  d="scan'208";a="7534618"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta2.baesystems.com with ESMTP; 23 Jun 2017 10:25:14 +0100
X-IronPort-AV: E=Sophos;i="5.39,377,1493679600";  d="scan'208";a="7218319"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasmds016.greenlnk.net with ESMTP; 23 Jun 2017 10:25:14 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.201]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.03.0248.002; Fri, 23 Jun 2017 10:25:14 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Joe Touch <touch@isi.edu>, =?utf-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: I-D Action: draft-thomson-postel-was-wrong-01.txt
Thread-Topic: I-D Action: draft-thomson-postel-was-wrong-01.txt
Thread-Index: AQHS4/ajWP45auakP0OI/9KB5mNdK6IicSuAgABYwYCAADhpgIAARqaAgAEnvQCAAHJvAIAELU4AgAHS6QCAAlWNgIAEGvuAgADk5LA=
Date: Fri, 23 Jun 2017 09:25:13 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636B715@GLKXM0003v.GREENLNK.net>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu> <8e8d4db9-93fd-5092-68de-6d8de44151c3@nic.cz> <c9202a09-af8b-faf6-b583-694378022dae@isi.edu>
In-Reply-To: <c9202a09-af8b-faf6-b583-694378022dae@isi.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SVVQXm9CzC6TNdxT7Hg5rf7-2XM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 09:25:18 -0000

Sm9lIFRvdWNoIHdyb3RlOg0KPiBMaWJlcmFsIG1lYW5zIHRoYXQgaWYgaXQncyBwb3NzaWJseSB2
YWxpZCwgeW91IHNob3VsZCBhY2NlcHQgaXQgYXMgc3VjaC4NCg0KVGhhdCBuZWNlc3NpdGF0ZXMg
dGhlIHByb3RvY29sIGRlc2lnbmVyIGV4cGxpY2l0bHkgZmxhZ2dpbmcgc29tZSB0aGluZ3MgYXMg
aW52YWxpZC4gT2J2aW91cyBleGFtcGxlIGlzIGEgc2hvdWxkIGJlIHNpZ25lZCBtZXNzYWdlIGxh
Y2tpbmcgYSBzaWduYXR1cmUuIElmIHRha2luZyB0aGUgbW9zdCBsaWJlcmFsIHZpZXcgKGFzIGFi
b3ZlKSB0aGUgcHJvdG9jb2wgbmVlZHMgdG8gc2F5IHNvbWV0aGluZyBsaWtlICJpZiB0aGUgc2ln
bmF0dXJlIGlzIG1pc3Npbmcgb3IgaW52YWxpZCwgdGhlbiB0aGUgbWVzc2FnZSBtdXN0IGJlIHJl
amVjdGVkIi4gSSBkb24ndCB0aGluayB0aGF0J3MgYW55dGhpbmcgbmV3LCBJJ3ZlIHNlZW4gaXQg
ZG9uZS4NCg0KSSBjYW4gc2VlIGF0IGxlYXN0IHRoZSBmb2xsb3dpbmcgY2FzZXMgd2hlcmUgbWFr
aW5nIGludGVudCBjbGVhciBpcywgaW4gbXkgb3BpbmlvbiBhdCBsZWFzdCwgYSBnb29kIGlkZWE6
DQotIFNlY3VyaXR5IGFuZCBvdGhlciBzZW5zaXRpdmUgY2FzZXMgb2YgZmFpbHVyZS4gTmVlZCB0
byBzYXkgZXhwbGljaXRseSByZWplY3QuDQotIE1lY2hhbmlzbXMgZGVzaWduZWQgZm9yIGV4dGVu
c2lvbnMuIFdoaWxlIHRoZSBQb3N0ZWwgcHJpbmNpcGxlIG1ha2VzIGl0IHVubmVjZXNzYXJ5IHRv
IHNheSBzbywgaXQgcmVhbGx5IGRvZXNuJ3QgaHVydCBzYXlpbmcgdGhhdCBhIG1lc3NhZ2Ugc2hv
dWxkbid0IGJlIHJlamVjdGVkIGp1c3QgZm9yIHRoaXMgcmVhc29uLg0KLSBXaGVyZSB3aGF0IHlv
dSByZWNlaXZlIGlzIGEgY29udGFpbmVyIG9mIG11bHRpcGxlIHRoaW5ncyAobWVzc2FnZXMgaW4g
YSBwYWNrZXQsIFRMVnMgaW4gYSBtZXNzYWdlKS4gTWFraW5nIHRoZSBhc3N1bWVkIGRlcGVuZGVu
Y2UvaW5kZXBlbmRlbmNlIGNsZWFyIGRvZXNuJ3QgaHVydCAoaWYgcmVqZWN0aW5nL2lnbm9yaW5n
IG9uZSwgZG9lcyB0aGlzIGltcGFjdCBvbiB0aGUgb3RoZXJzPykuDQoNClRoYXQncyBub3Qgc29t
ZXRoaW5nIHRoYXQgc3BpcmFscyBvdXQgb2YgY29udHJvbCBpbiBzaXplLCBhIGNvdXBsZSBvZiBz
ZW50ZW5jZXMgd291bGQgY292ZXIgbW9zdCBjYXNlcy4NCioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqClRoaXMgZW1haWwg
YW5kIGFueSBhdHRhY2htZW50cyBhcmUgY29uZmlkZW50aWFsIHRvIHRoZSBpbnRlbmRlZApyZWNp
cGllbnQgYW5kIG1heSBhbHNvIGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRl
bmRlZApyZWNpcGllbnQgcGxlYXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtIGFuZCBub3Rp
ZnkgdGhlIHNlbmRlci4KWW91IHNob3VsZCBub3QgY29weSBpdCBvciB1c2UgaXQgZm9yIGFueSBw
dXJwb3NlIG5vciBkaXNjbG9zZSBvcgpkaXN0cmlidXRlIGl0cyBjb250ZW50cyB0byBhbnkgb3Ro
ZXIgcGVyc29uLgoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKgo=


From nobody Fri Jun 23 03:01:55 2017
Return-Path: <liushucheng@huawei.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F0F731274D0; Fri, 23 Jun 2017 03:01:42 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Will LIU <liushucheng@huawei.com>
To: <ops-dir@ietf.org>
Cc: draft-ietf-trill-rbridge-multilevel.all@ietf.org, ietf@ietf.org, trill@ietf.org
Subject: Opsdir last call review of draft-ietf-trill-rbridge-multilevel-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149821210292.17338.9570586170242114506@ietfa.amsl.com>
Date: Fri, 23 Jun 2017 03:01:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/vkHMo9x37c3vmUausb9xmupMd0o>
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, 23 Jun 2017 10:01:43 -0000

Reviewer: Will LIU
Review result: Ready

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

"This informational document enumerates and examines alternatives based on a
number of factors including backward compatibility, simplicity, and scalability
and makes recommendations in some cases.""

The document was well written, and I didn't find any nit in it. The RFC editor
might modify and place the copyright part in the usual position.

My overall view of the document is 'Ready' for publication.



From nobody Fri Jun 23 04:39:02 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 546D3129B2F for <ietf@ietfa.amsl.com>; Fri, 23 Jun 2017 04:39:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.62
X-Spam-Level: 
X-Spam-Status: No, score=-2.62 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_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 ZH9vA4DRMoPK for <ietf@ietfa.amsl.com>; Fri, 23 Jun 2017 04:38:58 -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 C5C1F12EACA for <ietf@ietf.org>; Fri, 23 Jun 2017 04:38:58 -0700 (PDT)
Received: from pps.filterd (m0098409.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v5NBctGi069171 for <ietf@ietf.org>; Fri, 23 Jun 2017 07:38:55 -0400
Received: from e35.co.us.ibm.com (e35.co.us.ibm.com [32.97.110.153]) by mx0a-001b2d01.pphosted.com with ESMTP id 2b8yuhew36-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 23 Jun 2017 07:38:55 -0400
Received: from localhost by e35.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>; Fri, 23 Jun 2017 05:38:52 -0600
Received: from b03cxnp08025.gho.boulder.ibm.com (9.17.130.17) by e35.co.us.ibm.com (192.168.1.135) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 23 Jun 2017 05:38:50 -0600
Received: from b03ledav004.gho.boulder.ibm.com (b03ledav004.gho.boulder.ibm.com [9.17.130.235]) by b03cxnp08025.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v5NBcnUd1245568 for <ietf@ietf.org>; Fri, 23 Jun 2017 04:38:49 -0700
Received: from b03ledav004.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 9A13978043 for <ietf@ietf.org>; Fri, 23 Jun 2017 05:38:49 -0600 (MDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b03ledav004.gho.boulder.ibm.com (Postfix) with ESMTPS id 7D03178038 for <ietf@ietf.org>; Fri, 23 Jun 2017 05:38:49 -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 v5NBclTF005399 for <ietf@ietf.org>; Fri, 23 Jun 2017 07:38:47 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v5NBclnr005364 for ietf@ietf.org; Fri, 23 Jun 2017 07:38:47 -0400
From: narten@us.ibm.com
Date: Fri, 23 Jun 2017 07:38:46 -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: 17062311-0012-0000-0000-000014856689
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007277; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000214; SDB=6.00878725; UDB=6.00437881; IPR=6.00658876;  BA=6.00005438; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00015940; XFM=3.00000015; UTC=2017-06-23 11:38:51
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17062311-0013-0000-0000-00004E453DBD
Message-Id: <201706231138.v5NBclnr005364@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-23_07:, , 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-1706230199
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0oxUwwMvW5pDOJzjHMtyQ9OxRSk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 11:39:01 -0000

Total of 72 messages in the last 7 days.
 
script run at: Fri Jun 23 07:38:41 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  8.33% |    6 |  6.56% |    53599 | touch@isi.edu
  2.78% |    2 |  5.91% |    48306 | alissa@cooperw.in
  2.78% |    2 |  5.35% |    43734 | lucienav@google.com
  4.17% |    3 |  3.71% |    30358 | ynir.ietf@gmail.com
  2.78% |    2 |  4.76% |    38928 | xufeng_liu@jabil.com
  4.17% |    3 |  3.25% |    26526 | petr.spacek@nic.cz
  4.17% |    3 |  2.97% |    24281 | cabo@tzi.org
  2.78% |    2 |  3.42% |    27930 | eckelcu@cisco.com
  2.78% |    2 |  3.40% |    27795 | rwilton@cisco.com
  2.78% |    2 |  2.88% |    23505 | jefftant.ietf@gmail.com
  2.78% |    2 |  2.84% |    23251 | agmalis@gmail.com
  2.78% |    2 |  2.75% |    22462 | ekr@rtfm.com
  2.78% |    2 |  2.46% |    20136 | john-ietf@jck.com
  2.78% |    2 |  2.04% |    16713 | paul@nohats.ca
  2.78% |    2 |  1.95% |    15970 | jari.arkko@piuha.net
  1.39% |    1 |  3.32% |    27099 | iab-chair@iab.org
  1.39% |    1 |  3.30% |    26973 | nalini.elkins@insidethestack.com
  2.78% |    2 |  1.73% |    14176 | randy@psg.com
  2.78% |    2 |  1.58% |    12934 | jmh@joelhalpern.com
  1.39% |    1 |  2.51% |    20496 | roni.even@huawei.com
  1.39% |    1 |  2.34% |    19148 | ron.even.tlv@gmail.com
  1.39% |    1 |  1.99% |    16272 | brown@isoc.org
  1.39% |    1 |  1.93% |    15811 | bclaise@cisco.com
  1.39% |    1 |  1.81% |    14803 | sesale@juniper.net
  1.39% |    1 |  1.46% |    11929 | oritl@microsoft.com
  1.39% |    1 |  1.45% |    11882 | aaron.falk@gmail.com
  1.39% |    1 |  1.32% |    10822 | huitema@huitema.net
  1.39% |    1 |  1.25% |    10206 | allison.mankin@gmail.com
  1.39% |    1 |  1.20% |     9807 | bob.hinden@gmail.com
  1.39% |    1 |  1.19% |     9715 | tjc@ecs.soton.ac.uk
  1.39% |    1 |  1.17% |     9545 | brian.e.carpenter@gmail.com
  1.39% |    1 |  1.14% |     9354 | ggm@algebras.org
  1.39% |    1 |  1.11% |     9040 | nomcom-chair-2017@ietf.org
  1.39% |    1 |  1.09% |     8880 | jason_livingood@comcast.com
  1.39% |    1 |  1.08% |     8794 | kaduk@mit.edu
  1.39% |    1 |  1.04% |     8517 | lee@asgard.org
  1.39% |    1 |  1.03% |     8420 | tnadeau@lucidvision.com
  1.39% |    1 |  1.03% |     8406 | julian.reschke@gmx.de
  1.39% |    1 |  1.01% |     8292 | a@ackl.io
  1.39% |    1 |  0.98% |     7974 | jtw@csail.mit.edu
  1.39% |    1 |  0.95% |     7749 | elwynd@dial.pipex.com
  1.39% |    1 |  0.93% |     7582 | lberger@labn.net
  1.39% |    1 |  0.91% |     7427 | mfidelman@meetinghouse.net
  1.39% |    1 |  0.85% |     6987 | heas@shrubbery.net
  1.39% |    1 |  0.83% |     6824 | jaap@nlnetlabs.nl
  1.39% |    1 |  0.75% |     6122 | johnl@taugh.com
  1.39% |    1 |  0.74% |     6055 | agenda@ietf.org
  1.39% |    1 |  0.70% |     5741 | dromasca@gmail.com
--------+------+--------+----------+------------------------
100.00% |   72 |100.00% |   817276 | Total


From nobody Fri Jun 23 04:45:30 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 00B3712EAB1; Fri, 23 Jun 2017 04:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level: 
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7suYQIEJ8_zT; Fri, 23 Jun 2017 04:45:16 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 758AC129B2F; Fri, 23 Jun 2017 04:45:15 -0700 (PDT)
X-AuditID: c1b4fb3a-6e3519a000004a6a-83-594cff4960a2
Received: from ESESSHC020.ericsson.se (Unknown_Domain [153.88.183.78]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id F7.86.19050.94FFC495; Fri, 23 Jun 2017 13:45:13 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.25]) by ESESSHC020.ericsson.se ([153.88.183.78]) with mapi id 14.03.0339.000; Fri, 23 Jun 2017 13:45:11 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Elwyn Davies <elwynd@dial.pipex.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-sipcore-content-id.all@ietf.org" <draft-ietf-sipcore-content-id.all@ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Genart last call review of draft-ietf-sipcore-content-id-06
Thread-Topic: Genart last call review of draft-ietf-sipcore-content-id-06
Thread-Index: AQHS66unOzFnPwNS2kaBRZ3xc9koz6IySHwQ
Date: Fri, 23 Jun 2017 11:45:10 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4CC1C4B5@ESESSMB109.ericsson.se>
References: <149817255908.17071.14195524382332366327@ietfa.amsl.com>
In-Reply-To: <149817255908.17071.14195524382332366327@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.148]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpjkeLIzCtJLcpLzFFi42KZGbHdT9fzv0+kwder4hYzz+5isdh2XNDi 6qvPLBbPNs5nsfj6YxObA6vH8RU72T2WLPnJFMAUxWWTkpqTWZZapG+XwJXR9fUIc8EstYq1 DYsYGxjnqHYxcnBICJhI/Flp3MXIySEkcIRR4vlCwS5GLiB7MaPEqc2n2UFq2AQsJLr/aYPU iAgESsxcPYEVpIZZYCWjxJUpLSwgCWEBD4kjT5+xQBR5Shy/chbKNpJYtvoqG4jNIqAq0fV6 OjOIzSvgKzHtRwcbxGIXic2T54Lt4hRwlfh8sRwkzCggJvH91BomEJtZQFzi1pP5YLaEgIDE kj3nmSFsUYmXj/+xQthKEo1LnrCCjGEW0JRYv0sfolVRYkr3Q3aIrYISJ2c+YZnAKDoLydRZ CB2zkHTMQtKxgJFlFaNocWpxcW66kZFealFmcnFxfp5eXmrJJkZg7Bzc8ttqB+PB546HGAU4 GJV4eCt/+0QKsSaWFVfmHmKU4GBWEuGd8xUoxJuSWFmVWpQfX1Sak1p8iFGag0VJnNdh34UI IYH0xJLU7NTUgtQimCwTB6dUA+MG7rnsPuc3ZRc9OdijvWafruYMn1Mp93Y8u3dGrjFJ9Lik e/Hr7yrXtvg3hubF1+eE9AmeEw+obhB6fGn1ynNNHxcvNvp5V+G0FbeHo6os96T5h/xmRQrc DF3/9UHxp5i9v/7/jp1Ru3nOqZK0GXf7Ky6Y3Ofsr/m9RjbcnFPW4sfHzx+dcpSUWIozEg21 mIuKEwH8QMX9mQIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iCx2-7bwtSsxnRhsgLXolM0LkyA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 11:45:18 -0000

SGkgRWx3eW4sDQoNClRoYW5rIFlvdSBmb3IgdGhlIHJldmlldyEgUGxlYXNlIHNlZSBpbmxpbmUu
DQoNCj5TdW1tYXJ5Og0KPlJlYWR5IHdpdGggbml0cy4gIFRoZXJlIGFyZSBhIGNvdXBsZSBvZiBt
aW5vciBpc3N1ZXMgcmVsYXRlZCB0byB0aGUgcHJvY2VkdXJlcyBhZnRlciBpbmFwcHJvcHJpYXRl
IHVzYWdlIG9mIHRoZSBuZXcgaGVhZGVyLg0KPg0KPk1ham9yIGlzc3VlczoNCj5Ob25lDQo+DQo+
TWlub3IgaXNzdWVzOg0KPg0KPiBzMy40LjEsIGxhc3QgcGFyYTogSW4gbGluZSB3aXRoIHRoZSBs
YXN0IHNlbnRlbmNlIG9mIFNlY3Rpb24gMy4yLCB0aGUgQ29udGVudC1JRCBVUkwgb25seSBuZWVk
cyB0byBiZSB1bmlxdWUgd2l0aGluIHRoZSBTSVAgbWVzc2FnZSB3aGVyZSBpdCBvY2N1cnMuDQo+
wqBJIGFzc3VtZSBpdCBkb2VzIG5vdCBtYWtlIHNlbnNlIHRvIGhhdmUgYSBDb250ZW50LUlEIGhl
YWRlciBjb21iaW5lZCB3aXRoIGEgbXV0aXBhcnQgbWVzc2FnZS1ib2R5ICh0aGlzIGlzbid0IHN0
YXRlZCAtIG1heWJlIGl0IHNob3VsZCBiZSk7DQoNCkkgYW0gbm90IGF3YXJlIG9mIGFueSBjdXJy
ZW50IHVzZS1jYXNlLCBidXQgSSBzZWUgbm8gcmVhc29uIHRvIGZvcmJpZCBpdC4gUGVyaGFwcyBz
b21lb25lIHdpbGwgY29tZSB1cCB3aXRoIGEgdXNlLWNhc2UgaW4gZnV0dXJlLg0KDQo+IEkgYW0g
bm90IHN1ZmZpY2llbnRseSBrbm93bGVkZ2VhYmxlIGluIHRoaXMgYXJlYSBvZiBTSVAgdG8ga25v
dyBpZiB0aGVyZSBjb3VsZCBiZSBjb250ZW50LWlkIFVSTHMgaW4gb3RoZXIgaGVhZGVycyBpZiB0
aGVyZSBpcyBhIENvbnRlbnQtSUQgDQo+IGhlYWRlciBpbiB0aGUgbWVzc2FnZS4gwqBUaHVzIGVp
dGhlciB0aGUgc3RhdGVtZW50IGFib3V0IGdsb2JhbCB1bmlxdWVuZXNzIGlzIGlycmVsZXZhbnQg
KGFzIHRoZXJlIGlzIG9ubHkgb25lKSBhbmQgY2FuIGJlIHJlbW92ZWQgb3IgaXQgDQo+IHNob3Vs
ZCBiZSBtYWRlIGNvbnNpc3RlbnQgd2l0aCBzMy4yIHNvIHRoYXQgdGhlIENvbnRlbnQgVVJMcyBh
cmUgdW5pcXVlIHdpdGhpbiB0aGUgbWVzc2FnZS4gR2xvYmFsIHVuaXF1ZW5lc3MgaXMgbmVpdGhl
ciBwb3NzaWJsZSBvciByZXF1aXJlZC4NCg0KVGhlIHN0YXRlbWVudCBhYm91dCBnbG9iYWwgdW5p
cXVlbmVzcyBpcyBhIGJ1ZywgYW5kIHdpbGwgYmUgZml4ZWQuIFRoZSB2YWx1ZSBvbmx5IGhhcyB0
byBiZSB1bmlxdWUgd2l0aGluIHRoZSBtZXNzYWdlLg0KDQo+IHMzLjQuMSwgcGFyYSAxOiBGb2xs
b3dpbmcgb24gZnJvbSB0aGUgcHJldmlvdXMgY29tbWVudDogSXMgYSBVQSBhbGxvd2VkIHRvIGFk
ZCBhIENvbnRlbnQtSUQgaGVhZGVyIHRvIGEgbWVzc2FnZSB3aXRoIGEgbXVsdGlwYXJ0IG1lc3Nh
Z2UtYm9keT8NCg0KSSBzZWUgbm8gcmVhc29uIHRvIGZvcmJpZCBpdC4NCg0KPiBzMy40LjE6IFdo
YXQgc2hvdWxkIGEgVUEgZG8gaWYgaXQgcmVjZWl2ZXMgYSBtZXNzYWdlIHdpdGggYSBDb250ZW50
LUlEIGhlYWRlciB3aGVuIHRoZSBtZXNzYWdlIGlzIG5vdCBhbGxvd2VkIHRvIA0KPiBjb250YWlu
IG9uZT8gwqBJcyB0aGVyZSBzb21lIGdlbmVyaWMgZXJyb3IgcHJvY2VkdXJlIHRoYXQgc2hvdWxk
IGJlIHJlZmVyZW5jZWQ/DQoNCk5vcm1hbCBSRkMgMzI2MSBwcm9jZWR1cmVzIGFwcGx5LiBJIGRv
bid0IHRoaW5rIHdlIHdhbnQgdG8gY29weS9wYXN0ZSB0aGUgZ2VuZXJpYyBoZWFkZXIgcHJvY2Vz
c2luZyBydWxlcywNCg0KPiBzNi4xOiBJIHN0YXJ0ZWQgbG9va2luZyBmb3Igc3BlY2lmaWNhdGlv
biB0aGF0IHRvbGQgbWUgdGhhdCBpdGVtcyBhZGRlZCB0byB0aGUgU0lQIGhlYWRlciBmaWVsZHMg
cmVnaXN0cnkgZWZmZWN0aXZlbHkNCj4gZXh0ZW5kIHRoZSBkZWZpbml0aW9uIG9mIHRoZSBtZXNz
YWdlLWhlYWRlciBwcm9kdWN0aW9uIGluIFNlY3Rpb24gMjUuMW9mIFJGQyAzMjYxLiDCoEJpdCBv
YnZpb3VzIHBlcmhhcHMsIGJ1dCBpdCANCj4gd291bGQgYmUgbmljZSBpZiBpdCBoYWQgYmVlbiBz
YWlkIHNvbWV3aGVyZSEgwqBUaW1lIGZvciBhbiBFcnJhdHVtIHBlcmhhcHM/DQoNCkluIHRoZSBB
Qk5GIG9mIFJGQyAzMjYxLCAibWVzc2FnZS1oZWFkZXIiIGNvbnRhaW5zIHRoZSBoZWFkZXIgZmll
bGRzIGRlZmluZWQgaW4gdGhlIFJGQywgcGx1cyAiZXh0ZW5zaW9uLWhlYWRlciIsIHdoaWNoIGlz
IHVzZWQgZm9yIG5ldyBoZWFkZXJzLiBJIGFzc3VtZSBwZW9wbGUgdGhpbmsgdGhhdCBpcyBjbGVh
ciBlbm91Z2ggOikNCg0KSGF2aW5nIHNhaWQgdGhhdCwgd2hhdCB5b3Ugc3VnZ2VzdCBpcyBub3Qg
bmVjZXNzYXJpbHkgYSBiYWQgaWRlYSwgYnV0IGl0IGlzIG91dHNpZGUgdGhlIHNjb3BlIG9mIHRo
aXMgZHJhZnQuDQoNCj5OaXRzL2VkaXRvcmlhbCBjb21tZW50czoNCj4NCj5BYnN0cmFjdDogwqBJ
IHdvdWxkIHN1Z2dlc3QgYWRkaW5nIGEgc2VudGVuY2UgdGhhdCBjbGFyaWZpZXMgd2hhdCB0aGUg
dXBkYXRlIG9mIFJGQyA1NjIxIGlzIG1vZGlmeWluZzogDQo+DQo+T0xEOiBUaGUgZG9jdW1lbnQg
YWxzbyB1cGRhdGVzIFJGQyA1NjIxLCB0byBlbmFibGUgYSBDb250ZW50LUlEIFVSTCB0byByZWZl
cmVuY2UgYSBjb21wbGV0ZSANCj5tZXNzYWdlLWJvZHkgYW5kIG1ldGFkYXRhIHByb3ZpZGVkIGJ5
IHNvbWUgYWRkaXRpb25hbCBTSVAgaGVhZGVyIGZpZWxkcy4gDQo+DQo+TkVXOiBUaGUgZG9jdW1l
bnQgIGFsc28gdXBkYXRlcyBSRkMgNTYyMSwgd2hpY2ggb25seSBhbGxvd3MgYSBDb250ZW50LUlE
IFVSTCB0byByZWZlcmVuY2UgYSANCj5ib2R5LXBhcnQgdGhhdCBpcyBwYXJ0IG9mIGEgbXVsdGlw
YXJ0IG1lc3NhZ2UtYm9keS4gwqBUaGlzIHVwZGF0ZSBlbmFibGVzIGEgQ29udGVudC1JRCBVUkwg
dG8gDQo+cmVmZXJlbmNlIGEgY29tcGxldGUgbWVzc2FnZS1ib2R5IGFuZCBtZXRhZGF0YSBwcm92
aWRlZCBieSBzb21lIGFkZGl0aW9uYWwgU0lQIGhlYWRlciBmaWVsZHMuIEVORA0KDQpMb29rcyBv
ay4gSSB3aWxsIG1vZGlmeSBhcyBzdWdnZXN0ZWQuDQoNCj5zMS4yLCBmaXJzdCBidWxsZXQ6IHMv
Zm9yIHByb3ZpZGluZyBsb2NhdGlvbi9mb3IgcHJvdmlkaW5nIGxvY2F0aW9uIGluZm9ybWF0aW9u
Lw0KDQpXaWxsIGJlIGZpeGVkIGFzIHN1Z2dlc3RlZC4NCg0KPnMxLjQuMTogTmVlZCB0byBleHBh
bmQgVUFDIChVc2VyIEFnZW50IENsaWVudCkgb24gZmlyc3QgdXNhZ2UuDQoNCkkgcmVhbGl6ZWQg
dGhlIGZpcnN0IHVzYWdlIGlzIGluIHNlY3Rpb24gMS4zLCBzbyBJIHdpbGwgZXhwZW5kIGl0IHRo
ZXJlLg0KDQo+czEuNC4xLCBwYXJhIDE6IHMvY2FuIGJlIGUuZy4gb2YvY2FuIGJlLCBmb3IgZXhh
bXBsZSwgb2YvDQoNCldpbGwgYmUgZml4ZWQgYXMgc3VnZ2VzdGVkLg0KDQo+czMuNC4xOiBOZWVk
IHRvIGV4cGFuZCBVQSAoVXNlciBBZ2VudCkgb24gZmlyc3QgdXNhZ2UgKGluIHNlY3Rpb24gdGl0
bGUpLg0KDQpXaWxsIGJlIGZpeGVkIGFzIHN1Z2dlc3RlZC4NCg0KPnM0LCBORVcgdGV4dDogcy9h
bGxvdyBjcmVhdGluZy9hbGxvdyB0aGUgY3JlYXRpb24gb2YvDQoNCldpbGwgYmUgZml4ZWQgYXMg
c3VnZ2VzdGVkLg0KDQpSZWdhcmRzLA0KDQpDaHJpc3Rlcg0KDQo=


From nobody Fri Jun 23 07:39:45 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 F01DA12EB03 for <ietf@ietfa.amsl.com>; Fri, 23 Jun 2017 07:39:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dTqXgdKLv1Cv for <ietf@ietfa.amsl.com>; Fri, 23 Jun 2017 07:39:37 -0700 (PDT)
Received: from smtp86.ord1d.emailsrvr.com (smtp86.ord1d.emailsrvr.com [184.106.54.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 5551C12EB01 for <ietf@ietf.org>; Fri, 23 Jun 2017 07:39:35 -0700 (PDT)
Received: from smtp11.relay.ord1d.emailsrvr.com (localhost [127.0.0.1]) by smtp11.relay.ord1d.emailsrvr.com (SMTP Server) with ESMTP id 81AA060083; Fri, 23 Jun 2017 10:39:34 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp11.relay.ord1d.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 3FA756007C;  Fri, 23 Jun 2017 10:39:34 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.55] (d172-219-247-164.abhsia.telus.net [172.219.247.164]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:25 (trex/5.7.12); Fri, 23 Jun 2017 10:39:34 -0400
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: Last Call: <draft-bormann-hybi-ws-wk-00.txt> (Well-known URIs for the WebSocket Protocol) to Proposed Standard
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <149806584125.15843.7356875656957821273.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jun 2017 08:39:33 -0600
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, draft-bormann-hybi-ws-wk@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <40588AD9-BA27-46D7-86FD-D89301DD17A0@iii.ca>
References: <149806584125.15843.7356875656957821273.idtracker@ietfa.amsl.com>
To: ietf@ietf.org
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iXK7ei_Zj4SHa0WSXOOCOHb3XJ0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 14:39:39 -0000

This seems very reasonable to me. Glad to see it get cleared up.=20


> On Jun 21, 2017, at 11:24 AM, The IESG <iesg-secretary@ietf.org> =
wrote:
>=20
>=20
> The IESG has received a request from an individual submitter to =
consider the
> following document: - 'Well-known URIs for the WebSocket Protocol'
>  <draft-bormann-hybi-ws-wk-00.txt> as Proposed Standard
>=20
> The IESG plans to make a decision in the next few weeks, and solicits =
final
> comments on this action. Please send substantive comments to the
> ietf@ietf.org mailing lists by 2017-07-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.
>=20
> Abstract
>=20
>=20
>   RFC 5785 defines a path prefix, "/.well-known/", that can be used by
>   well-known URIs, specifically for the "http" and "https" URI =
schemes.
>   The present memo formally updates RFC 6455, which defines the URI
>   schemes defined for the WebSocket Protocol, to extend the use of
>   these well-known URIs to those URI schemes.
>=20
>=20
>=20
>=20
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-bormann-hybi-ws-wk/
>=20
> IESG discussion can be tracked via
> https://datatracker.ietf.org/doc/draft-bormann-hybi-ws-wk/ballot/
>=20
>=20
> No IPR declarations have been submitted directly on this I-D.
>=20
>=20
>=20
>=20


From nobody Fri Jun 23 08:29:32 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB60F12702E; Fri, 23 Jun 2017 08:29:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 NaYpQM3YpuB1; Fri, 23 Jun 2017 08:29:27 -0700 (PDT)
Received: from b-painless.mh.aa.net.uk (b-painless.mh.aa.net.uk [81.187.30.52]) (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 EA825126C3D; Fri, 23 Jun 2017 08:29:26 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[192.168.0.129]) by b-painless.mh.aa.net.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <elwynd@dial.pipex.com>) id 1dOPxJ-00075X-La; Fri, 23 Jun 2017 15:53:09 +0100
Date: Fri, 23 Jun 2017 15:53:00 +0100
Subject: RE: Genart last call review of draft-ietf-sipcore-content-id-06
Message-ID: <tsxfglkj5vlsi1s6clcaqv4t.1498226524767@email.android.com>
Importance: normal
From: Elwyn Davies <elwynd@dial.pipex.com>
To: Christer Holmberg <christer.holmberg@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "draft-ietf-sipcore-content-id.all@ietf.org" <draft-ietf-sipcore-content-id.all@ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_121260130334430"
X-Painless-Spam-Score: -0.9
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BmM_4E6GuKmYy2reSvqMfjF2Tt0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 15:29:31 -0000

----_com.samsung.android.email_121260130334430
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

SGksIENocmlzdGVyLgpUaGFua3MgZm9yIHRoZSBxdWljayByZXNwb25zZS4KTG9va3MgbGlrZSB3
ZSBhcmUgY2xlYXIgb24gYWxsIHRoaXMsIGV4Y2VwdCB0aGF0OjEuIMKgSSB3b3VsZCBzdWdnZXN0
IG1ha2luZyBpdCBleHBsaWNpdCB0aGF0IHlvdSBjYW4gYWRkIGEgQ29udGVudC1JRCBoZWFkZXIg
ZXZlbiB0byBhIG1lc3NhZ2Ugd2l0aCBhIG11bHRpcGFydCBtZXNzYWdlLWJvZHkgdG8gYXZvaWQg
YW55IGNvbmZ1c2lvbi4gwqBJIGFtIG5vdCBzdXJlIHRoYXQgaXQgbWFrZXMgYW55IHNlbnNlIGJ1
dCBJIGd1ZXNzIGl0IHdvdWxkbid0IGRvIGFueSBoYXJtLsKgMi4gwqBJZiBhIG1lc3NhZ2Ugb2Yg
YSBraW5kIHRoYXQgY2FuIGxlZ2l0aW1hdGVseSBoYXZlIGEgQ29udGVudC1JRCBhcnJpdmVzIHdp
dGggYSBDb250ZW50LUlEIChvciBpbmRlZWQgYW55IENvbnRlbnQtKikgaGVhZGVyIGJ1dCBubyBt
ZXNzYWdlLWJvZHksIHByZXN1bWFibHkgb25lIHdvdWxkIHNlbmQgYSA0MDAgZXJyb3Igd2l0aCBh
IHN1aXRhYmxlIHJlYXNvbiBwaHJhc2UuIMKgSSB0aGluayBpdCB3b3VsZCBiZSB3b3J0aCBiZWlu
ZyBleHBsaWNpdCBhYm91dCB0aGlzLgpDaGVlcnMsRWx3eW4KCgpTZW50IGZyb20gU2Ftc3VuZyB0
YWJsZXQuCi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0tLS1Gcm9tOiBDaHJpc3RlciBI
b2xtYmVyZyA8Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPiBEYXRlOiAyMy8wNi8yMDE3
ICAxMjo0NSAgKEdNVCswMDowMCkgVG86IEVsd3luIERhdmllcyA8ZWx3eW5kQGRpYWwucGlwZXgu
Y29tPiwgZ2VuLWFydEBpZXRmLm9yZyBDYzogZHJhZnQtaWV0Zi1zaXBjb3JlLWNvbnRlbnQtaWQu
YWxsQGlldGYub3JnLCBzaXBjb3JlQGlldGYub3JnLCBpZXRmQGlldGYub3JnIFN1YmplY3Q6IFJF
OiBHZW5hcnQgbGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLXNpcGNvcmUtY29udGVudC1p
ZC0wNiAKSGkgRWx3eW4sCgpUaGFuayBZb3UgZm9yIHRoZSByZXZpZXchIFBsZWFzZSBzZWUgaW5s
aW5lLgoKPlN1bW1hcnk6Cj5SZWFkeSB3aXRoIG5pdHMuwqAgVGhlcmUgYXJlIGEgY291cGxlIG9m
IG1pbm9yIGlzc3VlcyByZWxhdGVkIHRvIHRoZSBwcm9jZWR1cmVzIGFmdGVyIGluYXBwcm9wcmlh
dGUgdXNhZ2Ugb2YgdGhlIG5ldyBoZWFkZXIuCj4KPk1ham9yIGlzc3VlczoKPk5vbmUKPgo+TWlu
b3IgaXNzdWVzOgo+Cj4gczMuNC4xLCBsYXN0IHBhcmE6IEluIGxpbmUgd2l0aCB0aGUgbGFzdCBz
ZW50ZW5jZSBvZiBTZWN0aW9uIDMuMiwgdGhlIENvbnRlbnQtSUQgVVJMIG9ubHkgbmVlZHMgdG8g
YmUgdW5pcXVlIHdpdGhpbiB0aGUgU0lQIG1lc3NhZ2Ugd2hlcmUgaXQgb2NjdXJzLgo+wqBJIGFz
c3VtZSBpdCBkb2VzIG5vdCBtYWtlIHNlbnNlIHRvIGhhdmUgYSBDb250ZW50LUlEIGhlYWRlciBj
b21iaW5lZCB3aXRoIGEgbXV0aXBhcnQgbWVzc2FnZS1ib2R5ICh0aGlzIGlzbid0IHN0YXRlZCAt
IG1heWJlIGl0IHNob3VsZCBiZSk7CgpJIGFtIG5vdCBhd2FyZSBvZiBhbnkgY3VycmVudCB1c2Ut
Y2FzZSwgYnV0IEkgc2VlIG5vIHJlYXNvbiB0byBmb3JiaWQgaXQuIFBlcmhhcHMgc29tZW9uZSB3
aWxsIGNvbWUgdXAgd2l0aCBhIHVzZS1jYXNlIGluIGZ1dHVyZS4KCj4gSSBhbSBub3Qgc3VmZmlj
aWVudGx5IGtub3dsZWRnZWFibGUgaW4gdGhpcyBhcmVhIG9mIFNJUCB0byBrbm93IGlmIHRoZXJl
IGNvdWxkIGJlIGNvbnRlbnQtaWQgVVJMcyBpbiBvdGhlciBoZWFkZXJzIGlmIHRoZXJlIGlzIGEg
Q29udGVudC1JRCAKPiBoZWFkZXIgaW4gdGhlIG1lc3NhZ2UuIMKgVGh1cyBlaXRoZXIgdGhlIHN0
YXRlbWVudCBhYm91dCBnbG9iYWwgdW5pcXVlbmVzcyBpcyBpcnJlbGV2YW50IChhcyB0aGVyZSBp
cyBvbmx5IG9uZSkgYW5kIGNhbiBiZSByZW1vdmVkIG9yIGl0IAo+IHNob3VsZCBiZSBtYWRlIGNv
bnNpc3RlbnQgd2l0aCBzMy4yIHNvIHRoYXQgdGhlIENvbnRlbnQgVVJMcyBhcmUgdW5pcXVlIHdp
dGhpbiB0aGUgbWVzc2FnZS4gR2xvYmFsIHVuaXF1ZW5lc3MgaXMgbmVpdGhlciBwb3NzaWJsZSBv
ciByZXF1aXJlZC4KClRoZSBzdGF0ZW1lbnQgYWJvdXQgZ2xvYmFsIHVuaXF1ZW5lc3MgaXMgYSBi
dWcsIGFuZCB3aWxsIGJlIGZpeGVkLiBUaGUgdmFsdWUgb25seSBoYXMgdG8gYmUgdW5pcXVlIHdp
dGhpbiB0aGUgbWVzc2FnZS4KCj4gczMuNC4xLCBwYXJhIDE6IEZvbGxvd2luZyBvbiBmcm9tIHRo
ZSBwcmV2aW91cyBjb21tZW50OiBJcyBhIFVBIGFsbG93ZWQgdG8gYWRkIGEgQ29udGVudC1JRCBo
ZWFkZXIgdG8gYSBtZXNzYWdlIHdpdGggYSBtdWx0aXBhcnQgbWVzc2FnZS1ib2R5PwoKSSBzZWUg
bm8gcmVhc29uIHRvIGZvcmJpZCBpdC4KCj4gczMuNC4xOiBXaGF0IHNob3VsZCBhIFVBIGRvIGlm
IGl0IHJlY2VpdmVzIGEgbWVzc2FnZSB3aXRoIGEgQ29udGVudC1JRCBoZWFkZXIgd2hlbiB0aGUg
bWVzc2FnZSBpcyBub3QgYWxsb3dlZCB0byAKPiBjb250YWluIG9uZT8gwqBJcyB0aGVyZSBzb21l
IGdlbmVyaWMgZXJyb3IgcHJvY2VkdXJlIHRoYXQgc2hvdWxkIGJlIHJlZmVyZW5jZWQ/CgpOb3Jt
YWwgUkZDIDMyNjEgcHJvY2VkdXJlcyBhcHBseS4gSSBkb24ndCB0aGluayB3ZSB3YW50IHRvIGNv
cHkvcGFzdGUgdGhlIGdlbmVyaWMgaGVhZGVyIHByb2Nlc3NpbmcgcnVsZXMsCgo+IHM2LjE6IEkg
c3RhcnRlZCBsb29raW5nIGZvciBzcGVjaWZpY2F0aW9uIHRoYXQgdG9sZCBtZSB0aGF0IGl0ZW1z
IGFkZGVkIHRvIHRoZSBTSVAgaGVhZGVyIGZpZWxkcyByZWdpc3RyeSBlZmZlY3RpdmVseQo+IGV4
dGVuZCB0aGUgZGVmaW5pdGlvbiBvZiB0aGUgbWVzc2FnZS1oZWFkZXIgcHJvZHVjdGlvbiBpbiBT
ZWN0aW9uIDI1LjFvZiBSRkMgMzI2MS4gwqBCaXQgb2J2aW91cyBwZXJoYXBzLCBidXQgaXQgCj4g
d291bGQgYmUgbmljZSBpZiBpdCBoYWQgYmVlbiBzYWlkIHNvbWV3aGVyZSEgwqBUaW1lIGZvciBh
biBFcnJhdHVtIHBlcmhhcHM/CgpJbiB0aGUgQUJORiBvZiBSRkMgMzI2MSwgIm1lc3NhZ2UtaGVh
ZGVyIiBjb250YWlucyB0aGUgaGVhZGVyIGZpZWxkcyBkZWZpbmVkIGluIHRoZSBSRkMsIHBsdXMg
ImV4dGVuc2lvbi1oZWFkZXIiLCB3aGljaCBpcyB1c2VkIGZvciBuZXcgaGVhZGVycy4gSSBhc3N1
bWUgcGVvcGxlIHRoaW5rIHRoYXQgaXMgY2xlYXIgZW5vdWdoIDopCgpIYXZpbmcgc2FpZCB0aGF0
LCB3aGF0IHlvdSBzdWdnZXN0IGlzIG5vdCBuZWNlc3NhcmlseSBhIGJhZCBpZGVhLCBidXQgaXQg
aXMgb3V0c2lkZSB0aGUgc2NvcGUgb2YgdGhpcyBkcmFmdC4KCj5OaXRzL2VkaXRvcmlhbCBjb21t
ZW50czoKPgo+QWJzdHJhY3Q6IMKgSSB3b3VsZCBzdWdnZXN0IGFkZGluZyBhIHNlbnRlbmNlIHRo
YXQgY2xhcmlmaWVzIHdoYXQgdGhlIHVwZGF0ZSBvZiBSRkMgNTYyMSBpcyBtb2RpZnlpbmc6IAo+
Cj5PTEQ6IFRoZSBkb2N1bWVudCBhbHNvIHVwZGF0ZXMgUkZDIDU2MjEsIHRvIGVuYWJsZSBhIENv
bnRlbnQtSUQgVVJMIHRvIHJlZmVyZW5jZSBhIGNvbXBsZXRlIAo+bWVzc2FnZS1ib2R5IGFuZCBt
ZXRhZGF0YSBwcm92aWRlZCBieSBzb21lIGFkZGl0aW9uYWwgU0lQIGhlYWRlciBmaWVsZHMuIAo+
Cj5ORVc6IFRoZSBkb2N1bWVudMKgIGFsc28gdXBkYXRlcyBSRkMgNTYyMSwgd2hpY2ggb25seSBh
bGxvd3MgYSBDb250ZW50LUlEIFVSTCB0byByZWZlcmVuY2UgYSAKPmJvZHktcGFydCB0aGF0IGlz
IHBhcnQgb2YgYSBtdWx0aXBhcnQgbWVzc2FnZS1ib2R5LiDCoFRoaXMgdXBkYXRlIGVuYWJsZXMg
YSBDb250ZW50LUlEIFVSTCB0byAKPnJlZmVyZW5jZSBhIGNvbXBsZXRlIG1lc3NhZ2UtYm9keSBh
bmQgbWV0YWRhdGEgcHJvdmlkZWQgYnkgc29tZSBhZGRpdGlvbmFsIFNJUCBoZWFkZXIgZmllbGRz
LiBFTkQKCkxvb2tzIG9rLiBJIHdpbGwgbW9kaWZ5IGFzIHN1Z2dlc3RlZC4KCj5zMS4yLCBmaXJz
dCBidWxsZXQ6IHMvZm9yIHByb3ZpZGluZyBsb2NhdGlvbi9mb3IgcHJvdmlkaW5nIGxvY2F0aW9u
IGluZm9ybWF0aW9uLwoKV2lsbCBiZSBmaXhlZCBhcyBzdWdnZXN0ZWQuCgo+czEuNC4xOiBOZWVk
IHRvIGV4cGFuZCBVQUMgKFVzZXIgQWdlbnQgQ2xpZW50KSBvbiBmaXJzdCB1c2FnZS4KCkkgcmVh
bGl6ZWQgdGhlIGZpcnN0IHVzYWdlIGlzIGluIHNlY3Rpb24gMS4zLCBzbyBJIHdpbGwgZXhwZW5k
IGl0IHRoZXJlLgoKPnMxLjQuMSwgcGFyYSAxOiBzL2NhbiBiZSBlLmcuIG9mL2NhbiBiZSwgZm9y
IGV4YW1wbGUsIG9mLwoKV2lsbCBiZSBmaXhlZCBhcyBzdWdnZXN0ZWQuCgo+czMuNC4xOiBOZWVk
IHRvIGV4cGFuZCBVQSAoVXNlciBBZ2VudCkgb24gZmlyc3QgdXNhZ2UgKGluIHNlY3Rpb24gdGl0
bGUpLgoKV2lsbCBiZSBmaXhlZCBhcyBzdWdnZXN0ZWQuCgo+czQsIE5FVyB0ZXh0OiBzL2FsbG93
IGNyZWF0aW5nL2FsbG93IHRoZSBjcmVhdGlvbiBvZi8KCldpbGwgYmUgZml4ZWQgYXMgc3VnZ2Vz
dGVkLgoKUmVnYXJkcywKCkNocmlzdGVyCgo=

----_com.samsung.android.email_121260130334430
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2PkhpLCBDaHJpc3Rlci48L2Rp
dj48ZGl2Pjxicj48L2Rpdj48ZGl2PlRoYW5rcyBmb3IgdGhlIHF1aWNrIHJlc3BvbnNlLjwvZGl2
PjxkaXY+PGJyPjwvZGl2PjxkaXY+TG9va3MgbGlrZSB3ZSBhcmUgY2xlYXIgb24gYWxsIHRoaXMs
IGV4Y2VwdCB0aGF0OjwvZGl2PjxkaXY+MS4gJm5ic3A7SSB3b3VsZCBzdWdnZXN0IG1ha2luZyBp
dCBleHBsaWNpdCB0aGF0IHlvdSBjYW4gYWRkIGEgQ29udGVudC1JRCBoZWFkZXIgZXZlbiB0byBh
IG1lc3NhZ2Ugd2l0aCBhIG11bHRpcGFydCBtZXNzYWdlLWJvZHkgdG8gYXZvaWQgYW55IGNvbmZ1
c2lvbi4gJm5ic3A7SSBhbSBub3Qgc3VyZSB0aGF0IGl0IG1ha2VzIGFueSBzZW5zZSBidXQgSSBn
dWVzcyBpdCB3b3VsZG4ndCBkbyBhbnkgaGFybS4mbmJzcDs8L2Rpdj48ZGl2PjIuICZuYnNwO0lm
IGEgbWVzc2FnZSBvZiBhIGtpbmQgdGhhdCBjYW4gbGVnaXRpbWF0ZWx5IGhhdmUgYSBDb250ZW50
LUlEIGFycml2ZXMgd2l0aCBhIENvbnRlbnQtSUQgKG9yIGluZGVlZCBhbnkgQ29udGVudC0qKSBo
ZWFkZXIgYnV0IG5vIG1lc3NhZ2UtYm9keSwgcHJlc3VtYWJseSBvbmUgd291bGQgc2VuZCBhIDQw
MCBlcnJvciB3aXRoIGEgc3VpdGFibGUgcmVhc29uIHBocmFzZS4gJm5ic3A7SSB0aGluayBpdCB3
b3VsZCBiZSB3b3J0aCBiZWluZyBleHBsaWNpdCBhYm91dCB0aGlzLjwvZGl2PjxkaXY+PGJyPjwv
ZGl2PjxkaXY+Q2hlZXJzLDwvZGl2PjxkaXY+RWx3eW48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2
Pjxicj48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2IGlkPSJjb21wb3Nlcl9zaWduYXR1cmUiPjxk
aXYgc3R5bGU9ImZvbnQtc2l6ZTo4NSU7Y29sb3I6IzU3NTc1NyIgZGlyPSJhdXRvIj5TZW50IGZy
b20gU2Ftc3VuZyB0YWJsZXQuPC9kaXY+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdiBzdHlsZT0i
Zm9udC1zaXplOjEwMCU7Y29sb3I6IzAwMDAwMCI+PCEtLSBvcmlnaW5hbE1lc3NhZ2UgLS0+PGRp
dj4tLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tPC9kaXY+PGRpdj5Gcm9tOiBDaHJp
c3RlciBIb2xtYmVyZyAmbHQ7Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tJmd0OyA8L2Rp
dj48ZGl2PkRhdGU6IDIzLzA2LzIwMTcgIDEyOjQ1ICAoR01UKzAwOjAwKSA8L2Rpdj48ZGl2PlRv
OiBFbHd5biBEYXZpZXMgJmx0O2Vsd3luZEBkaWFsLnBpcGV4LmNvbSZndDssIGdlbi1hcnRAaWV0
Zi5vcmcgPC9kaXY+PGRpdj5DYzogZHJhZnQtaWV0Zi1zaXBjb3JlLWNvbnRlbnQtaWQuYWxsQGll
dGYub3JnLCBzaXBjb3JlQGlldGYub3JnLCBpZXRmQGlldGYub3JnIDwvZGl2PjxkaXY+U3ViamVj
dDogUkU6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtc2lwY29yZS1jb250
ZW50LWlkLTA2IDwvZGl2PjxkaXY+PGJyPjwvZGl2PjwvZGl2PkhpIEVsd3luLDxicj48YnI+VGhh
bmsgWW91IGZvciB0aGUgcmV2aWV3ISBQbGVhc2Ugc2VlIGlubGluZS48YnI+PGJyPiZndDtTdW1t
YXJ5Ojxicj4mZ3Q7UmVhZHkgd2l0aCBuaXRzLiZuYnNwOyBUaGVyZSBhcmUgYSBjb3VwbGUgb2Yg
bWlub3IgaXNzdWVzIHJlbGF0ZWQgdG8gdGhlIHByb2NlZHVyZXMgYWZ0ZXIgaW5hcHByb3ByaWF0
ZSB1c2FnZSBvZiB0aGUgbmV3IGhlYWRlci48YnI+Jmd0Ozxicj4mZ3Q7TWFqb3IgaXNzdWVzOjxi
cj4mZ3Q7Tm9uZTxicj4mZ3Q7PGJyPiZndDtNaW5vciBpc3N1ZXM6PGJyPiZndDs8YnI+Jmd0OyBz
My40LjEsIGxhc3QgcGFyYTogSW4gbGluZSB3aXRoIHRoZSBsYXN0IHNlbnRlbmNlIG9mIFNlY3Rp
b24gMy4yLCB0aGUgQ29udGVudC1JRCBVUkwgb25seSBuZWVkcyB0byBiZSB1bmlxdWUgd2l0aGlu
IHRoZSBTSVAgbWVzc2FnZSB3aGVyZSBpdCBvY2N1cnMuPGJyPiZndDsmbmJzcDtJIGFzc3VtZSBp
dCBkb2VzIG5vdCBtYWtlIHNlbnNlIHRvIGhhdmUgYSBDb250ZW50LUlEIGhlYWRlciBjb21iaW5l
ZCB3aXRoIGEgbXV0aXBhcnQgbWVzc2FnZS1ib2R5ICh0aGlzIGlzbid0IHN0YXRlZCAtIG1heWJl
IGl0IHNob3VsZCBiZSk7PGJyPjxicj5JIGFtIG5vdCBhd2FyZSBvZiBhbnkgY3VycmVudCB1c2Ut
Y2FzZSwgYnV0IEkgc2VlIG5vIHJlYXNvbiB0byBmb3JiaWQgaXQuIFBlcmhhcHMgc29tZW9uZSB3
aWxsIGNvbWUgdXAgd2l0aCBhIHVzZS1jYXNlIGluIGZ1dHVyZS48YnI+PGJyPiZndDsgSSBhbSBu
b3Qgc3VmZmljaWVudGx5IGtub3dsZWRnZWFibGUgaW4gdGhpcyBhcmVhIG9mIFNJUCB0byBrbm93
IGlmIHRoZXJlIGNvdWxkIGJlIGNvbnRlbnQtaWQgVVJMcyBpbiBvdGhlciBoZWFkZXJzIGlmIHRo
ZXJlIGlzIGEgQ29udGVudC1JRCA8YnI+Jmd0OyBoZWFkZXIgaW4gdGhlIG1lc3NhZ2UuICZuYnNw
O1RodXMgZWl0aGVyIHRoZSBzdGF0ZW1lbnQgYWJvdXQgZ2xvYmFsIHVuaXF1ZW5lc3MgaXMgaXJy
ZWxldmFudCAoYXMgdGhlcmUgaXMgb25seSBvbmUpIGFuZCBjYW4gYmUgcmVtb3ZlZCBvciBpdCA8
YnI+Jmd0OyBzaG91bGQgYmUgbWFkZSBjb25zaXN0ZW50IHdpdGggczMuMiBzbyB0aGF0IHRoZSBD
b250ZW50IFVSTHMgYXJlIHVuaXF1ZSB3aXRoaW4gdGhlIG1lc3NhZ2UuIEdsb2JhbCB1bmlxdWVu
ZXNzIGlzIG5laXRoZXIgcG9zc2libGUgb3IgcmVxdWlyZWQuPGJyPjxicj5UaGUgc3RhdGVtZW50
IGFib3V0IGdsb2JhbCB1bmlxdWVuZXNzIGlzIGEgYnVnLCBhbmQgd2lsbCBiZSBmaXhlZC4gVGhl
IHZhbHVlIG9ubHkgaGFzIHRvIGJlIHVuaXF1ZSB3aXRoaW4gdGhlIG1lc3NhZ2UuPGJyPjxicj4m
Z3Q7IHMzLjQuMSwgcGFyYSAxOiBGb2xsb3dpbmcgb24gZnJvbSB0aGUgcHJldmlvdXMgY29tbWVu
dDogSXMgYSBVQSBhbGxvd2VkIHRvIGFkZCBhIENvbnRlbnQtSUQgaGVhZGVyIHRvIGEgbWVzc2Fn
ZSB3aXRoIGEgbXVsdGlwYXJ0IG1lc3NhZ2UtYm9keT88YnI+PGJyPkkgc2VlIG5vIHJlYXNvbiB0
byBmb3JiaWQgaXQuPGJyPjxicj4mZ3Q7IHMzLjQuMTogV2hhdCBzaG91bGQgYSBVQSBkbyBpZiBp
dCByZWNlaXZlcyBhIG1lc3NhZ2Ugd2l0aCBhIENvbnRlbnQtSUQgaGVhZGVyIHdoZW4gdGhlIG1l
c3NhZ2UgaXMgbm90IGFsbG93ZWQgdG8gPGJyPiZndDsgY29udGFpbiBvbmU/ICZuYnNwO0lzIHRo
ZXJlIHNvbWUgZ2VuZXJpYyBlcnJvciBwcm9jZWR1cmUgdGhhdCBzaG91bGQgYmUgcmVmZXJlbmNl
ZD88YnI+PGJyPk5vcm1hbCBSRkMgMzI2MSBwcm9jZWR1cmVzIGFwcGx5LiBJIGRvbid0IHRoaW5r
IHdlIHdhbnQgdG8gY29weS9wYXN0ZSB0aGUgZ2VuZXJpYyBoZWFkZXIgcHJvY2Vzc2luZyBydWxl
cyw8YnI+PGJyPiZndDsgczYuMTogSSBzdGFydGVkIGxvb2tpbmcgZm9yIHNwZWNpZmljYXRpb24g
dGhhdCB0b2xkIG1lIHRoYXQgaXRlbXMgYWRkZWQgdG8gdGhlIFNJUCBoZWFkZXIgZmllbGRzIHJl
Z2lzdHJ5IGVmZmVjdGl2ZWx5PGJyPiZndDsgZXh0ZW5kIHRoZSBkZWZpbml0aW9uIG9mIHRoZSBt
ZXNzYWdlLWhlYWRlciBwcm9kdWN0aW9uIGluIFNlY3Rpb24gMjUuMW9mIFJGQyAzMjYxLiAmbmJz
cDtCaXQgb2J2aW91cyBwZXJoYXBzLCBidXQgaXQgPGJyPiZndDsgd291bGQgYmUgbmljZSBpZiBp
dCBoYWQgYmVlbiBzYWlkIHNvbWV3aGVyZSEgJm5ic3A7VGltZSBmb3IgYW4gRXJyYXR1bSBwZXJo
YXBzPzxicj48YnI+SW4gdGhlIEFCTkYgb2YgUkZDIDMyNjEsICJtZXNzYWdlLWhlYWRlciIgY29u
dGFpbnMgdGhlIGhlYWRlciBmaWVsZHMgZGVmaW5lZCBpbiB0aGUgUkZDLCBwbHVzICJleHRlbnNp
b24taGVhZGVyIiwgd2hpY2ggaXMgdXNlZCBmb3IgbmV3IGhlYWRlcnMuIEkgYXNzdW1lIHBlb3Bs
ZSB0aGluayB0aGF0IGlzIGNsZWFyIGVub3VnaCA6KTxicj48YnI+SGF2aW5nIHNhaWQgdGhhdCwg
d2hhdCB5b3Ugc3VnZ2VzdCBpcyBub3QgbmVjZXNzYXJpbHkgYSBiYWQgaWRlYSwgYnV0IGl0IGlz
IG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZHJhZnQuPGJyPjxicj4mZ3Q7Tml0cy9lZGl0b3Jp
YWwgY29tbWVudHM6PGJyPiZndDs8YnI+Jmd0O0Fic3RyYWN0OiAmbmJzcDtJIHdvdWxkIHN1Z2dl
c3QgYWRkaW5nIGEgc2VudGVuY2UgdGhhdCBjbGFyaWZpZXMgd2hhdCB0aGUgdXBkYXRlIG9mIFJG
QyA1NjIxIGlzIG1vZGlmeWluZzogPGJyPiZndDs8YnI+Jmd0O09MRDogVGhlIGRvY3VtZW50IGFs
c28gdXBkYXRlcyBSRkMgNTYyMSwgdG8gZW5hYmxlIGEgQ29udGVudC1JRCBVUkwgdG8gcmVmZXJl
bmNlIGEgY29tcGxldGUgPGJyPiZndDttZXNzYWdlLWJvZHkgYW5kIG1ldGFkYXRhIHByb3ZpZGVk
IGJ5IHNvbWUgYWRkaXRpb25hbCBTSVAgaGVhZGVyIGZpZWxkcy4gPGJyPiZndDs8YnI+Jmd0O05F
VzogVGhlIGRvY3VtZW50Jm5ic3A7IGFsc28gdXBkYXRlcyBSRkMgNTYyMSwgd2hpY2ggb25seSBh
bGxvd3MgYSBDb250ZW50LUlEIFVSTCB0byByZWZlcmVuY2UgYSA8YnI+Jmd0O2JvZHktcGFydCB0
aGF0IGlzIHBhcnQgb2YgYSBtdWx0aXBhcnQgbWVzc2FnZS1ib2R5LiAmbmJzcDtUaGlzIHVwZGF0
ZSBlbmFibGVzIGEgQ29udGVudC1JRCBVUkwgdG8gPGJyPiZndDtyZWZlcmVuY2UgYSBjb21wbGV0
ZSBtZXNzYWdlLWJvZHkgYW5kIG1ldGFkYXRhIHByb3ZpZGVkIGJ5IHNvbWUgYWRkaXRpb25hbCBT
SVAgaGVhZGVyIGZpZWxkcy4gRU5EPGJyPjxicj5Mb29rcyBvay4gSSB3aWxsIG1vZGlmeSBhcyBz
dWdnZXN0ZWQuPGJyPjxicj4mZ3Q7czEuMiwgZmlyc3QgYnVsbGV0OiBzL2ZvciBwcm92aWRpbmcg
bG9jYXRpb24vZm9yIHByb3ZpZGluZyBsb2NhdGlvbiBpbmZvcm1hdGlvbi88YnI+PGJyPldpbGwg
YmUgZml4ZWQgYXMgc3VnZ2VzdGVkLjxicj48YnI+Jmd0O3MxLjQuMTogTmVlZCB0byBleHBhbmQg
VUFDIChVc2VyIEFnZW50IENsaWVudCkgb24gZmlyc3QgdXNhZ2UuPGJyPjxicj5JIHJlYWxpemVk
IHRoZSBmaXJzdCB1c2FnZSBpcyBpbiBzZWN0aW9uIDEuMywgc28gSSB3aWxsIGV4cGVuZCBpdCB0
aGVyZS48YnI+PGJyPiZndDtzMS40LjEsIHBhcmEgMTogcy9jYW4gYmUgZS5nLiBvZi9jYW4gYmUs
IGZvciBleGFtcGxlLCBvZi88YnI+PGJyPldpbGwgYmUgZml4ZWQgYXMgc3VnZ2VzdGVkLjxicj48
YnI+Jmd0O3MzLjQuMTogTmVlZCB0byBleHBhbmQgVUEgKFVzZXIgQWdlbnQpIG9uIGZpcnN0IHVz
YWdlIChpbiBzZWN0aW9uIHRpdGxlKS48YnI+PGJyPldpbGwgYmUgZml4ZWQgYXMgc3VnZ2VzdGVk
Ljxicj48YnI+Jmd0O3M0LCBORVcgdGV4dDogcy9hbGxvdyBjcmVhdGluZy9hbGxvdyB0aGUgY3Jl
YXRpb24gb2YvPGJyPjxicj5XaWxsIGJlIGZpeGVkIGFzIHN1Z2dlc3RlZC48YnI+PGJyPlJlZ2Fy
ZHMsPGJyPjxicj5DaHJpc3Rlcjxicj48YnI+PC9ib2R5PjwvaHRtbD4=

----_com.samsung.android.email_121260130334430--


From nobody Fri Jun 23 08:40:27 2017
Return-Path: <d3e3e3@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 0FA8F12951F; Fri, 23 Jun 2017 08:40:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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 BfhQEQWJtIVb; Fri, 23 Jun 2017 08:40:24 -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 4679C1243FE; Fri, 23 Jun 2017 08:40:21 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id h64so4866651iod.0; Fri, 23 Jun 2017 08:40:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=B+e85MCCzZCOvt7x6/pIg5lk9YbxaFBz3ciI08Ivtrg=; b=pobUC3BL+Cvk0RmiFGLCC0TzIs4uaHDMINhh5RJv9DiId6MeKzVXkbVkn2hxTF3lYP o0Z3KMc/7098LICf/klpjvqR6XDWddIcN6f72S56i1JgXcwlef6ex2QaCTXSPX6i4bKt NQdV/1D3mPKMt8roMfcL81lmLKXTo/SqmbWZRCFaOlzwbwD96odfzEyPCUI6MhczWEbG AvEifricfeS+yuhod4uepJLfB/DedKEnvJHDoq36cemF5bOR59yBU/mrg3vG+i4A0a0S yVDAfagVP8XG1jnSt9KB+5OD6qtV9vl06g9xpaHnUiX4poXp7gbin8cCoYYvJJfl1QFQ vimw==
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=B+e85MCCzZCOvt7x6/pIg5lk9YbxaFBz3ciI08Ivtrg=; b=NxtWweE97j+boUu1KZ/Rk6z5wxw41lxDZRNVptHWbjKJjLkhfwVevlj4w4HnrRSIf1 /6eLFqPTqoNowfA75sJo5xjSdXqx1byFmSmWEgrVTYfe096V3A4xyTpEbtnzygz1fpA3 nMd5e04dPFe3qazKVjMNmoJpAfpbFfTseNcecUrDiHyT/+l63DCOD9VB4ry07jhD6gUj BapbKNJckKAjfWJRpFwBjMEahFm0Twp5FJU4ZAAr0teTT67QRGbcXj+mjkpNGs72p6YL Z1Y0hoiI2hkZ+BrOzAvawObpPD4987td1jy/ifUWn0roMF//LEX7ayzXtxCdJEMhX3/j hMjQ==
X-Gm-Message-State: AKS2vOwXd6wSjXSQUUM+wqAtg6cXHkj5sfenBNZ3hikXR7OO1PtwvhJB 7mW9ZX1k2ShyYNb+Bw9e8lsxS857cQ==
X-Received: by 10.107.4.19 with SMTP id 19mr7739764ioe.95.1498232420499; Fri, 23 Jun 2017 08:40:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.17.221 with HTTP; Fri, 23 Jun 2017 08:40:04 -0700 (PDT)
In-Reply-To: <149821210292.17338.9570586170242114506@ietfa.amsl.com>
References: <149821210292.17338.9570586170242114506@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 23 Jun 2017 11:40:04 -0400
Message-ID: <CAF4+nEEgHKHO=NUYVUPppfY=4mPJLJw=XY5n5aH17jdZX4FvSQ@mail.gmail.com>
Subject: Re: Opsdir last call review of draft-ietf-trill-rbridge-multilevel-06
To: Will LIU <liushucheng@huawei.com>
Cc: "ops-dir@ietf.org" <ops-dir@ietf.org>, draft-ietf-trill-rbridge-multilevel.all@ietf.org,  IETF Discussion <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cdgd8rZH1dg6m7-2h54y8VwFIIU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 15:40:26 -0000

Hi Will,

Thanks for your review.

Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com


On Fri, Jun 23, 2017 at 6:01 AM, Will LIU <liushucheng@huawei.com> wrote:
> Reviewer: Will LIU
> Review result: Ready
>
> I have reviewed draft-ietf-trill-rbridge-multilevel-06 as part of the
> Operational directorate's ongoing effort to review all IETF documents being
> processed by the IESG.  These comments were written with the intent of
> improving the operational aspects of the IETF drafts. Comments that are not
> addressed in last call may be included in AD reviews during the IESG review.
> Document editors and WG chairs should treat these comments just like any other
> last call comments.
>
> "This informational document enumerates and examines alternatives based on a
> number of factors including backward compatibility, simplicity, and scalability
> and makes recommendations in some cases.""
>
> The document was well written, and I didn't find any nit in it. The RFC editor
> might modify and place the copyright part in the usual position.
>
> My overall view of the document is 'Ready' for publication.
>
>


From nobody Fri Jun 23 10:34:32 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 68367128C84 for <ietf@ietfa.amsl.com>; Fri, 23 Jun 2017 10:34:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 IaR8eOy4dCKG for <ietf@ietfa.amsl.com>; Fri, 23 Jun 2017 10:34:29 -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 24F66129AA4 for <ietf@ietf.org>; Fri, 23 Jun 2017 10:34:26 -0700 (PDT)
Received: from [128.9.184.92] ([128.9.184.92]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v5NHXSO5013410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 23 Jun 2017 10:33:28 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: John C Klensin <john-ietf@jck.com>
Cc: =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, ietf@ietf.org
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu> <8e8d4db9-93fd-5092-68de-6d8de44151c3@nic.cz> <c9202a09-af8b-faf6-b583-694378022dae@isi.edu> <56AAD497D44465073CA7B494@PSB>
From: Joe Touch <touch@isi.edu>
Message-ID: <110794ce-1c83-6b51-e9e4-113865ad3c57@isi.edu>
Date: Fri, 23 Jun 2017 10:33:26 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <56AAD497D44465073CA7B494@PSB>
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/uMLSEIEq39atpHci1laShK4QxtE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 17:34:30 -0000

Hi, John,

On 6/22/2017 10:04 PM, John C Klensin wrote:
> Joe,
>
> I think we are in agreement -- we have been so far-- 
We are.
> but let me
> add a real world example that might help clarify some of  this.

Your example makes a good point - my interpretation of that is "don't
rely on half of the Postel Principle".

> ... there is a long history of reasonable
> applications of the principle and an equally long on of
> unreasonable applications including situations in which senders
> have claimed "be liberal about what you accept" allows them to
> send complete nonsense and, if things then don't work, to claim
> that is the receiver's fault (see my earlier comments about
> common sense).
They need to "be conservative in what you send".

The principle cuts both ways.

Joe


From nobody Fri Jun 23 10:36:16 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 0A83B129AA4 for <ietf@ietfa.amsl.com>; Fri, 23 Jun 2017 10:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 FZ53mdgE0xgz for <ietf@ietfa.amsl.com>; Fri, 23 Jun 2017 10:36:13 -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 A3587129601 for <ietf@ietf.org>; Fri, 23 Jun 2017 10:36:13 -0700 (PDT)
Received: from [128.9.184.92] ([128.9.184.92]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v5NHZbje013532 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 23 Jun 2017 10:35:38 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, "ietf@ietf.org" <ietf@ietf.org>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu> <8e8d4db9-93fd-5092-68de-6d8de44151c3@nic.cz> <c9202a09-af8b-faf6-b583-694378022dae@isi.edu> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636B715@GLKXM0003v.GREENLNK.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <d0c4ecc7-1fe9-fc0b-bbe5-8cffb956b6ed@isi.edu>
Date: Fri, 23 Jun 2017 10:35:36 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636B715@GLKXM0003v.GREENLNK.net>
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/GCxJSgkauwWLXm0NgGqOf4qGtgw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 17:36:15 -0000

On 6/23/2017 2:25 AM, Dearlove, Christopher (UK) wrote:
> Joe Touch wrote:
>> Liberal means that if it's possibly valid, you should accept it as such.
> That necessitates the protocol designer explicitly flagging some things as invalid. 
That's quite typical. Many protocols clearly indicate explicit invalid
cases.

> Obvious example is a should be signed message lacking a signature. If taking the most liberal view (as above) the protocol needs to say something like "if the signature is missing or invalid, then the message must be rejected". I don't think that's anything new, I've seen it done.
>
> I can see at least the following cases where making intent clear is, in my opinion at least, a good idea:
> - Security and other sensitive cases of failure. Need to say explicitly reject.
When not specified, "silently ignore" is another option.

> - Mechanisms designed for extensions. While the Postel principle makes it unnecessary to say so, it really doesn't hurt saying that a message shouldn't be rejected just for this reason.
Agreed.
> - Where what you receive is a container of multiple things (messages in a packet, TLVs in a message). Making the assumed dependence/independence clear doesn't hurt (if rejecting/ignoring one, does this impact on the others?).
>
> That's not something that spirals out of control in size, a couple of sentences would cover most cases.
Right - the Postel Principle isn't a license to be lazy in either a
protocol spec or implementation.

Joe


From nobody Fri Jun 23 10:36:40 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 33C30126DCA; Fri, 23 Jun 2017 10:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 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, 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 T2WA9l7tYzjo; Fri, 23 Jun 2017 10:36:24 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B776127286; Fri, 23 Jun 2017 10:36:23 -0700 (PDT)
X-AuditID: c1b4fb3a-81bff70000001b2f-31-594d5195ee2d
Received: from ESESSHC024.ericsson.se (Unknown_Domain [153.88.183.90]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id E0.55.06959.5915D495; Fri, 23 Jun 2017 19:36:21 +0200 (CEST)
Received: from ESESSMB109.ericsson.se ([169.254.9.25]) by ESESSHC024.ericsson.se ([153.88.183.90]) with mapi id 14.03.0339.000; Fri, 23 Jun 2017 19:36:20 +0200
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: Elwyn Davies <elwynd@dial.pipex.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-sipcore-content-id.all@ietf.org" <draft-ietf-sipcore-content-id.all@ietf.org>, "sipcore@ietf.org" <sipcore@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: Genart last call review of draft-ietf-sipcore-content-id-06
Thread-Topic: Genart last call review of draft-ietf-sipcore-content-id-06
Thread-Index: AQHS7DBoOzFnPwNS2kaBRZ3xc9koz6IysnyA
Date: Fri, 23 Jun 2017 17:36:19 +0000
Message-ID: <7594FB04B1934943A5C02806D1A2204B4CC1CD27@ESESSMB109.ericsson.se>
References: <tsxfglkj5vlsi1s6clcaqv4t.1498226524767@email.android.com>
In-Reply-To: <tsxfglkj5vlsi1s6clcaqv4t.1498226524767@email.android.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.154]
Content-Type: multipart/alternative; boundary="_000_7594FB04B1934943A5C02806D1A2204B4CC1CD27ESESSMB109erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrCIsWRmVeSWpSXmKPExsUyM2J7lO7UQN9Ig3k3RS1mnt3FYrHtuKDF 1VefWSyebZzPYvH1xyY2B1aP4yt2snssWfKTKYApissmJTUnsyy1SN8ugStj2qnnzAUd+xkr 5uxYxtLA2LCLsYuRk0NCwERi64PtLF2MXBxCAkcYJT5cOQnlLGaUmD3nFVMXIwcHm4CFRPc/ bZAGEYFAiZmrJ7CC1DALrGSUuDKlhQUkISzgIXHk6TMWiCJPieNXzkLZRhKzPvYyg9gsAqoS r9ecZwexeQV8JVZ072cFsYUE3CSat30Gu4hTwF1if/MeJhCbUUBM4vupNWA2s4C4xK0n85kg rhaQWLLnPDOELSrx8vE/VghbSWLR7c9Q9fkSnee+MELsEpQ4OfMJywRGkVlIRs1CUjYLSdks oJeZBTQl1u/ShyhRlJjS/ZAdwtaQaJ0zlx1ZfAEj+ypG0eLU4uLcdCMjvdSizOTi4vw8vbzU kk2MwLg7uOW31Q7Gg88dDzEKcDAq8fDW+/hGCrEmlhVX5h5ilOBgVhLhZfzvEynEm5JYWZVa lB9fVJqTWnyIUZqDRUmc12HfhQghgfTEktTs1NSC1CKYLBMHp1QDY/m7ymeML2V7WY99+Fa8 LkynadKeg+9uTFuc2f2/xHHuXGXOM/5yHhPtzWZv2bvsYnisfdetk8aysWIWPhIL88ys6/ka CiQE4vQjzyzRKP+TxfX6qINtfSzT6xXHK+dsdHyoJVdikvtyc0zVVEMLq1knmJ7L/7wck8wT +cdI/IndDIO7crM+KbEUZyQaajEXFScCAOKzGrq3AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/T4dgO_QEZwofTxQiPswKFIltT1M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 17:36:31 -0000

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

SGksDQoNCj5Mb29rcyBsaWtlIHdlIGFyZSBjbGVhciBvbiBhbGwgdGhpcywgZXhjZXB0IHRoYXQ6
DQo+MS4gIEkgd291bGQgc3VnZ2VzdCBtYWtpbmcgaXQgZXhwbGljaXQgdGhhdCB5b3UgY2FuIGFk
ZCBhIENvbnRlbnQtSUQgaGVhZGVyIGV2ZW4gdG8gYQ0KPiBtZXNzYWdlIHdpdGggYSBtdWx0aXBh
cnQgbWVzc2FnZS1ib2R5IHRvIGF2b2lkIGFueSBjb25mdXNpb24uICBJIGFtIG5vdCBzdXJlIHRo
YXQgaXQNCj4gbWFrZXMgYW55IHNlbnNlIGJ1dCBJIGd1ZXNzIGl0IHdvdWxkbid0IGRvIGFueSBo
YXJtLg0KDQpJIHN1Z2dlc3QgYWRkaW5nIHRoZSBmb2xsb3dpbmcgbm90ZSB0byB0aGUgZW5kIG9m
IHNlY3Rpb24gMy4zLg0KDQoNCuKAnE5PVEU6IFRoZSBtZXNzYWdlIGJvZHkgaWRlbnRpZmllZCBi
eSB0aGUgQ29udGVudC1JRCBoZWFkZXIgZmllbGQgY2FuIGJlIGENCg0Kbm9uLW11bHRpcGFydCBt
ZXNzYWdlLWJvZHkgb3IgYSBtdWx0aXBhcnQgbWVzc2FnZS1ib2R5LuKAnQ0KDQo+Mi4gIElmIGEg
bWVzc2FnZSBvZiBhIGtpbmQgdGhhdCBjYW4gbGVnaXRpbWF0ZWx5IGhhdmUgYSBDb250ZW50LUlE
IGFycml2ZXMgd2l0aCBhDQo+DQo+Q29udGVudC1JRCAob3IgaW5kZWVkIGFueSBDb250ZW50LSop
IGhlYWRlciBidXQgbm8gbWVzc2FnZS1ib2R5LCBwcmVzdW1hYmx5IG9uZSB3b3VsZA0KPiBzZW5k
IGEgNDAwIGVycm9yIHdpdGggYSBzdWl0YWJsZSByZWFzb24gcGhyYXNlLiAgSSB0aGluayBpdCB3
b3VsZCBiZSB3b3J0aCBiZWluZyBleHBsaWNpdCBhYm91dCB0aGlzLg0KDQpXZWxsLCB0aGVyZSBp
cyBhY3R1YWxseSBhIHVzZS1jYXNlIGZvciBhIENvbnRlbnQtVHlwZSB2YWx1ZSAoSSBkaWQgbm90
IGNoZWNrIHRoZSBvdGhlciBoZWFkZXIgZmllbGRzKSBidXQgbm8gbWVzc2FnZS1ib2R5Lg0KDQpT
ZWN0aW9uIDIwLjE1IG9mIFJGQyAzMjYxIHNheXM6DQoNCg0KICAgICAgICDigJxJZiB0aGUgYm9k
eSBpcyBlbXB0eSwgYW5kIGEgQ29udGVudC1UeXBlIGhlYWRlciBmaWVsZCBpcyBwcmVzZW50LCBp
dCBpbmRpY2F0ZXMgdGhhdCB0aGUgYm9keSBvZiB0aGUgc3BlY2lmaWMNCg0KICAgICAgICB0eXBl
IGhhcyB6ZXJvIGxlbmd0aCAoZm9yIGV4YW1wbGUsIGFuIGVtcHR5IGF1ZGlvIGZpbGUpLuKAnQ0K
DQpBbmQsIHRvIGVjaG8gUGF1bCwgSSBkb27igJl0IHNlZSBhIHJlYXNvbiB0byBzYXkgc29tZXRo
aW5nIHNwZWNpZmljIGZvciB0aGUgQ29udGVudC0qIGhlYWRlciBmaWVsZHMuIE5vcm1hbCBTSVAg
cHJvY2VkdXJlcyBzaG91bGQgYXBwbHkgcmVnYXJkaW5nIHJlY2VpdmluZyBoZWFkZXIgZmllbGRz
IHdpdGggbm8gbWVhbmluZyBmb3IgYSBwYXJ0aWN1bGFyIFNJUCBtZXNzYWdlLg0KDQpSZWdhcmRz
LA0KDQpDaHJpc3Rlcg0KDQoNCg0KLS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLQ0K
RnJvbTogQ2hyaXN0ZXIgSG9sbWJlcmcgPGNocmlzdGVyLmhvbG1iZXJnQGVyaWNzc29uLmNvbTxt
YWlsdG86Y2hyaXN0ZXIuaG9sbWJlcmdAZXJpY3Nzb24uY29tPj4NCkRhdGU6IDIzLzA2LzIwMTcg
MTI6NDUgKEdNVCswMDowMCkNClRvOiBFbHd5biBEYXZpZXMgPGVsd3luZEBkaWFsLnBpcGV4LmNv
bTxtYWlsdG86ZWx3eW5kQGRpYWwucGlwZXguY29tPj4sIGdlbi1hcnRAaWV0Zi5vcmc8bWFpbHRv
Omdlbi1hcnRAaWV0Zi5vcmc+DQpDYzogZHJhZnQtaWV0Zi1zaXBjb3JlLWNvbnRlbnQtaWQuYWxs
QGlldGYub3JnPG1haWx0bzpkcmFmdC1pZXRmLXNpcGNvcmUtY29udGVudC1pZC5hbGxAaWV0Zi5v
cmc+LCBzaXBjb3JlQGlldGYub3JnPG1haWx0bzpzaXBjb3JlQGlldGYub3JnPiwgaWV0ZkBpZXRm
Lm9yZzxtYWlsdG86aWV0ZkBpZXRmLm9yZz4NClN1YmplY3Q6IFJFOiBHZW5hcnQgbGFzdCBjYWxs
IHJldmlldyBvZiBkcmFmdC1pZXRmLXNpcGNvcmUtY29udGVudC1pZC0wNg0KDQpIaSBFbHd5biwN
Cg0KVGhhbmsgWW91IGZvciB0aGUgcmV2aWV3ISBQbGVhc2Ugc2VlIGlubGluZS4NCg0KPlN1bW1h
cnk6DQo+UmVhZHkgd2l0aCBuaXRzLiAgVGhlcmUgYXJlIGEgY291cGxlIG9mIG1pbm9yIGlzc3Vl
cyByZWxhdGVkIHRvIHRoZSBwcm9jZWR1cmVzIGFmdGVyIGluYXBwcm9wcmlhdGUgdXNhZ2Ugb2Yg
dGhlIG5ldyBoZWFkZXIuDQo+DQo+TWFqb3IgaXNzdWVzOg0KPk5vbmUNCj4NCj5NaW5vciBpc3N1
ZXM6DQo+DQo+IHMzLjQuMSwgbGFzdCBwYXJhOiBJbiBsaW5lIHdpdGggdGhlIGxhc3Qgc2VudGVu
Y2Ugb2YgU2VjdGlvbiAzLjIsIHRoZSBDb250ZW50LUlEIFVSTCBvbmx5IG5lZWRzIHRvIGJlIHVu
aXF1ZSB3aXRoaW4gdGhlIFNJUCBtZXNzYWdlIHdoZXJlIGl0IG9jY3Vycy4NCj4gSSBhc3N1bWUg
aXQgZG9lcyBub3QgbWFrZSBzZW5zZSB0byBoYXZlIGEgQ29udGVudC1JRCBoZWFkZXIgY29tYmlu
ZWQgd2l0aCBhIG11dGlwYXJ0IG1lc3NhZ2UtYm9keSAodGhpcyBpc24ndCBzdGF0ZWQgLSBtYXli
ZSBpdCBzaG91bGQgYmUpOw0KDQpJIGFtIG5vdCBhd2FyZSBvZiBhbnkgY3VycmVudCB1c2UtY2Fz
ZSwgYnV0IEkgc2VlIG5vIHJlYXNvbiB0byBmb3JiaWQgaXQuIFBlcmhhcHMgc29tZW9uZSB3aWxs
IGNvbWUgdXAgd2l0aCBhIHVzZS1jYXNlIGluIGZ1dHVyZS4NCg0KPiBJIGFtIG5vdCBzdWZmaWNp
ZW50bHkga25vd2xlZGdlYWJsZSBpbiB0aGlzIGFyZWEgb2YgU0lQIHRvIGtub3cgaWYgdGhlcmUg
Y291bGQgYmUgY29udGVudC1pZCBVUkxzIGluIG90aGVyIGhlYWRlcnMgaWYgdGhlcmUgaXMgYSBD
b250ZW50LUlEDQo+IGhlYWRlciBpbiB0aGUgbWVzc2FnZS4gIFRodXMgZWl0aGVyIHRoZSBzdGF0
ZW1lbnQgYWJvdXQgZ2xvYmFsIHVuaXF1ZW5lc3MgaXMgaXJyZWxldmFudCAoYXMgdGhlcmUgaXMg
b25seSBvbmUpIGFuZCBjYW4gYmUgcmVtb3ZlZCBvciBpdA0KPiBzaG91bGQgYmUgbWFkZSBjb25z
aXN0ZW50IHdpdGggczMuMiBzbyB0aGF0IHRoZSBDb250ZW50IFVSTHMgYXJlIHVuaXF1ZSB3aXRo
aW4gdGhlIG1lc3NhZ2UuIEdsb2JhbCB1bmlxdWVuZXNzIGlzIG5laXRoZXIgcG9zc2libGUgb3Ig
cmVxdWlyZWQuDQoNClRoZSBzdGF0ZW1lbnQgYWJvdXQgZ2xvYmFsIHVuaXF1ZW5lc3MgaXMgYSBi
dWcsIGFuZCB3aWxsIGJlIGZpeGVkLiBUaGUgdmFsdWUgb25seSBoYXMgdG8gYmUgdW5pcXVlIHdp
dGhpbiB0aGUgbWVzc2FnZS4NCg0KPiBzMy40LjEsIHBhcmEgMTogRm9sbG93aW5nIG9uIGZyb20g
dGhlIHByZXZpb3VzIGNvbW1lbnQ6IElzIGEgVUEgYWxsb3dlZCB0byBhZGQgYSBDb250ZW50LUlE
IGhlYWRlciB0byBhIG1lc3NhZ2Ugd2l0aCBhIG11bHRpcGFydCBtZXNzYWdlLWJvZHk/DQoNCkkg
c2VlIG5vIHJlYXNvbiB0byBmb3JiaWQgaXQuDQoNCj4gczMuNC4xOiBXaGF0IHNob3VsZCBhIFVB
IGRvIGlmIGl0IHJlY2VpdmVzIGEgbWVzc2FnZSB3aXRoIGEgQ29udGVudC1JRCBoZWFkZXIgd2hl
biB0aGUgbWVzc2FnZSBpcyBub3QgYWxsb3dlZCB0bw0KPiBjb250YWluIG9uZT8gIElzIHRoZXJl
IHNvbWUgZ2VuZXJpYyBlcnJvciBwcm9jZWR1cmUgdGhhdCBzaG91bGQgYmUgcmVmZXJlbmNlZD8N
Cg0KTm9ybWFsIFJGQyAzMjYxIHByb2NlZHVyZXMgYXBwbHkuIEkgZG9uJ3QgdGhpbmsgd2Ugd2Fu
dCB0byBjb3B5L3Bhc3RlIHRoZSBnZW5lcmljIGhlYWRlciBwcm9jZXNzaW5nIHJ1bGVzLA0KDQo+
IHM2LjE6IEkgc3RhcnRlZCBsb29raW5nIGZvciBzcGVjaWZpY2F0aW9uIHRoYXQgdG9sZCBtZSB0
aGF0IGl0ZW1zIGFkZGVkIHRvIHRoZSBTSVAgaGVhZGVyIGZpZWxkcyByZWdpc3RyeSBlZmZlY3Rp
dmVseQ0KPiBleHRlbmQgdGhlIGRlZmluaXRpb24gb2YgdGhlIG1lc3NhZ2UtaGVhZGVyIHByb2R1
Y3Rpb24gaW4gU2VjdGlvbiAyNS4xb2YgUkZDIDMyNjEuICBCaXQgb2J2aW91cyBwZXJoYXBzLCBi
dXQgaXQNCj4gd291bGQgYmUgbmljZSBpZiBpdCBoYWQgYmVlbiBzYWlkIHNvbWV3aGVyZSEgIFRp
bWUgZm9yIGFuIEVycmF0dW0gcGVyaGFwcz8NCg0KSW4gdGhlIEFCTkYgb2YgUkZDIDMyNjEsICJt
ZXNzYWdlLWhlYWRlciIgY29udGFpbnMgdGhlIGhlYWRlciBmaWVsZHMgZGVmaW5lZCBpbiB0aGUg
UkZDLCBwbHVzICJleHRlbnNpb24taGVhZGVyIiwgd2hpY2ggaXMgdXNlZCBmb3IgbmV3IGhlYWRl
cnMuIEkgYXNzdW1lIHBlb3BsZSB0aGluayB0aGF0IGlzIGNsZWFyIGVub3VnaCA6KQ0KDQpIYXZp
bmcgc2FpZCB0aGF0LCB3aGF0IHlvdSBzdWdnZXN0IGlzIG5vdCBuZWNlc3NhcmlseSBhIGJhZCBp
ZGVhLCBidXQgaXQgaXMgb3V0c2lkZSB0aGUgc2NvcGUgb2YgdGhpcyBkcmFmdC4NCg0KPk5pdHMv
ZWRpdG9yaWFsIGNvbW1lbnRzOg0KPg0KPkFic3RyYWN0OiAgSSB3b3VsZCBzdWdnZXN0IGFkZGlu
ZyBhIHNlbnRlbmNlIHRoYXQgY2xhcmlmaWVzIHdoYXQgdGhlIHVwZGF0ZSBvZiBSRkMgNTYyMSBp
cyBtb2RpZnlpbmc6DQo+DQo+T0xEOiBUaGUgZG9jdW1lbnQgYWxzbyB1cGRhdGVzIFJGQyA1NjIx
LCB0byBlbmFibGUgYSBDb250ZW50LUlEIFVSTCB0byByZWZlcmVuY2UgYSBjb21wbGV0ZQ0KPm1l
c3NhZ2UtYm9keSBhbmQgbWV0YWRhdGEgcHJvdmlkZWQgYnkgc29tZSBhZGRpdGlvbmFsIFNJUCBo
ZWFkZXIgZmllbGRzLg0KPg0KPk5FVzogVGhlIGRvY3VtZW50ICBhbHNvIHVwZGF0ZXMgUkZDIDU2
MjEsIHdoaWNoIG9ubHkgYWxsb3dzIGEgQ29udGVudC1JRCBVUkwgdG8gcmVmZXJlbmNlIGENCj5i
b2R5LXBhcnQgdGhhdCBpcyBwYXJ0IG9mIGEgbXVsdGlwYXJ0IG1lc3NhZ2UtYm9keS4gIFRoaXMg
dXBkYXRlIGVuYWJsZXMgYSBDb250ZW50LUlEIFVSTCB0bw0KPnJlZmVyZW5jZSBhIGNvbXBsZXRl
IG1lc3NhZ2UtYm9keSBhbmQgbWV0YWRhdGEgcHJvdmlkZWQgYnkgc29tZSBhZGRpdGlvbmFsIFNJ
UCBoZWFkZXIgZmllbGRzLiBFTkQNCg0KTG9va3Mgb2suIEkgd2lsbCBtb2RpZnkgYXMgc3VnZ2Vz
dGVkLg0KDQo+czEuMiwgZmlyc3QgYnVsbGV0OiBzL2ZvciBwcm92aWRpbmcgbG9jYXRpb24vZm9y
IHByb3ZpZGluZyBsb2NhdGlvbiBpbmZvcm1hdGlvbi8NCg0KV2lsbCBiZSBmaXhlZCBhcyBzdWdn
ZXN0ZWQuDQoNCj5zMS40LjE6IE5lZWQgdG8gZXhwYW5kIFVBQyAoVXNlciBBZ2VudCBDbGllbnQp
IG9uIGZpcnN0IHVzYWdlLg0KDQpJIHJlYWxpemVkIHRoZSBmaXJzdCB1c2FnZSBpcyBpbiBzZWN0
aW9uIDEuMywgc28gSSB3aWxsIGV4cGVuZCBpdCB0aGVyZS4NCg0KPnMxLjQuMSwgcGFyYSAxOiBz
L2NhbiBiZSBlLmcuIG9mL2NhbiBiZSwgZm9yIGV4YW1wbGUsIG9mLw0KDQpXaWxsIGJlIGZpeGVk
IGFzIHN1Z2dlc3RlZC4NCg0KPnMzLjQuMTogTmVlZCB0byBleHBhbmQgVUEgKFVzZXIgQWdlbnQp
IG9uIGZpcnN0IHVzYWdlIChpbiBzZWN0aW9uIHRpdGxlKS4NCg0KV2lsbCBiZSBmaXhlZCBhcyBz
dWdnZXN0ZWQuDQoNCj5zNCwgTkVXIHRleHQ6IHMvYWxsb3cgY3JlYXRpbmcvYWxsb3cgdGhlIGNy
ZWF0aW9uIG9mLw0KDQpXaWxsIGJlIGZpeGVkIGFzIHN1Z2dlc3RlZC4NCg0KUmVnYXJkcywNCg0K
Q2hyaXN0ZXINCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCglj
b2xvcjojMDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBz
cGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjojOTU0RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcHJlDQoJe21zby1zdHls
ZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQgQ2hhciI7
DQoJbWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEwLjBw
dDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlm
Ow0KCWNvbG9yOiMxRjQ5N0Q7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6
cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCglj
b2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uSFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxl
LW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsN
Cgltc28tc3R5bGUtbGluazoiSFRNTCBQcmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OiJDb3Vy
aWVyIE5ldyI7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7
DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0
IDc5Mi4wcHQ7DQoJbWFyZ2luOjcyLjBwdCA3Mi4wcHQgNzIuMHB0IDcyLjBwdDt9DQpkaXYuV29y
ZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUg
bXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2
IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4N
CjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9
IkVOLUdCIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+DQo8ZGl2IGNsYXNzPSJXb3Jk
U2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMx
RjQ5N0Q7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkhpLDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDtMb29rcyBsaWtlIHdlIGFyZSBj
bGVhciBvbiBhbGwgdGhpcywgZXhjZXB0IHRoYXQ6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7MS4gJm5ic3A7SSB3b3VsZCBzdWdnZXN0IG1h
a2luZyBpdCBleHBsaWNpdCB0aGF0IHlvdSBjYW4gYWRkIGEgQ29udGVudC1JRCBoZWFkZXIgZXZl
biB0byBhPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPiZndDsNCjwvc3Bhbj5tZXNzYWdlIHdpdGggYSBtdWx0aXBhcnQgbWVzc2FnZS1ib2R5IHRv
IGF2b2lkIGFueSBjb25mdXNpb24uICZuYnNwO0kgYW0gbm90IHN1cmUgdGhhdCBpdA0KPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPiZndDsNCjwv
c3Bhbj5tYWtlcyBhbnkgc2Vuc2UgYnV0IEkgZ3Vlc3MgaXQgd291bGRuJ3QgZG8gYW55IGhhcm0u
Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZiI+SSBzdWdnZXN0IGFkZGluZyB0aGUgZm9sbG93aW5nIG5vdGUgdG8gdGhl
IGVuZCBvZiBzZWN0aW9uIDMuMy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxw
cmU+PGk+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2Fs
aWJyaSZxdW90OyxzYW5zLXNlcmlmIj7igJxOT1RFOiBUaGUgbWVzc2FnZSBib2R5IGlkZW50aWZp
ZWQgYnkgdGhlIENvbnRlbnQtSUQgaGVhZGVyIGZpZWxkIGNhbiBiZSBhIDxvOnA+PC9vOnA+PC9z
cGFuPjwvaT48L3ByZT4NCjxwcmU+PGk+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5ub24tbXVsdGlwYXJ0IG1l
c3NhZ2UtYm9keSBvciBhIG11bHRpcGFydCBtZXNzYWdlLWJvZHku4oCdPG86cD48L286cD48L3Nw
YW4+PC9pPjwvcHJlPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj4mZ3Q7Mi4gJm5ic3A7SWYgYSBtZXNzYWdlIG9mIGEga2luZCB0aGF0IGNhbiBsZWdpdGlt
YXRlbHkgaGF2ZSBhIENvbnRlbnQtSUQgYXJyaXZlcyB3aXRoIGE8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDtDb250ZW50LUlEIChvciBpbmRl
ZWQgYW55IENvbnRlbnQtKikgaGVhZGVyIGJ1dCBubyBtZXNzYWdlLWJvZHksIHByZXN1bWFibHkg
b25lIHdvdWxkPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMt
c2VyaWYiPiZndDsNCjwvc3Bhbj5zZW5kIGEgNDAwIGVycm9yIHdpdGggYSBzdWl0YWJsZSByZWFz
b24gcGhyYXNlLiAmbmJzcDtJIHRoaW5rIGl0IHdvdWxkIGJlIHdvcnRoIGJlaW5nIGV4cGxpY2l0
IGFib3V0IHRoaXMuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+V2VsbCwgdGhlcmUgaXMgYWN0dWFsbHkgYSB1c2UtY2FzZSBm
b3IgYSBDb250ZW50LVR5cGUgdmFsdWUgKEkgZGlkIG5vdCBjaGVjayB0aGUgb3RoZXIgaGVhZGVy
IGZpZWxkcykgYnV0IG5vIG1lc3NhZ2UtYm9keS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+U2VjdGlvbiAyMC4x
NSBvZiBSRkMgMzI2MSBzYXlzOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHBy
ZT4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsg4oCcSWYgdGhlIGJv
ZHkgaXMgZW1wdHksIGFuZCBhIENvbnRlbnQtVHlwZSBoZWFkZXIgZmllbGQgaXMgcHJlc2VudCwg
aXQgaW5kaWNhdGVzIHRoYXQgdGhlIGJvZHkgb2YgdGhlIHNwZWNpZmljPG86cD48L286cD48L3By
ZT4NCjxwcmU+Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB0eXBlIGhhcyB6
ZXJvIGxlbmd0aCAoZm9yIGV4YW1wbGUsIGFuIGVtcHR5IGF1ZGlvIGZpbGUpLuKAnTxvOnA+PC9v
OnA+PC9wcmU+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJp
ZiI+QW5kLCB0byBlY2hvIFBhdWwsIEkgZG9u4oCZdCBzZWUgYSByZWFzb24gdG8gc2F5IHNvbWV0
aGluZyBzcGVjaWZpYyBmb3IgdGhlIENvbnRlbnQtKiBoZWFkZXIgZmllbGRzLiBOb3JtYWwgU0lQ
IHByb2NlZHVyZXMgc2hvdWxkIGFwcGx5IHJlZ2FyZGluZyByZWNlaXZpbmcgaGVhZGVyIGZpZWxk
cyB3aXRoDQogbm8gbWVhbmluZyBmb3IgYSBwYXJ0aWN1bGFyIFNJUCBtZXNzYWdlLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5z
LXNlcmlmIj5SZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGli
cmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5DaHJpc3RlcjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJjb2xvcjpibGFjayI+LS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLTxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJjb2xvcjpibGFjayI+RnJvbTogQ2hyaXN0ZXIgSG9sbWJlcmcgJmx0OzxhIGhyZWY9
Im1haWx0bzpjaHJpc3Rlci5ob2xtYmVyZ0Blcmljc3Nvbi5jb20iPmNocmlzdGVyLmhvbG1iZXJn
QGVyaWNzc29uLmNvbTwvYT4mZ3Q7DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPkRhdGU6
IDIzLzA2LzIwMTcgMTI6NDUgKEdNVCYjNDM7MDA6MDApDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6
YmxhY2siPlRvOiBFbHd5biBEYXZpZXMgJmx0OzxhIGhyZWY9Im1haWx0bzplbHd5bmRAZGlhbC5w
aXBleC5jb20iPmVsd3luZEBkaWFsLnBpcGV4LmNvbTwvYT4mZ3Q7LA0KPGEgaHJlZj0ibWFpbHRv
Omdlbi1hcnRAaWV0Zi5vcmciPmdlbi1hcnRAaWV0Zi5vcmc8L2E+IDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj
b2xvcjpibGFjayI+Q2M6IDxhIGhyZWY9Im1haWx0bzpkcmFmdC1pZXRmLXNpcGNvcmUtY29udGVu
dC1pZC5hbGxAaWV0Zi5vcmciPg0KZHJhZnQtaWV0Zi1zaXBjb3JlLWNvbnRlbnQtaWQuYWxsQGll
dGYub3JnPC9hPiwgPGEgaHJlZj0ibWFpbHRvOnNpcGNvcmVAaWV0Zi5vcmciPg0Kc2lwY29yZUBp
ZXRmLm9yZzwvYT4sIDxhIGhyZWY9Im1haWx0bzppZXRmQGlldGYub3JnIj5pZXRmQGlldGYub3Jn
PC9hPiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPlN1YmplY3Q6IFJFOiBHZW5hcnQgbGFz
dCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLXNpcGNvcmUtY29udGVudC1pZC0wNg0KPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIu
MHB0Ij5IaSBFbHd5biw8YnI+DQo8YnI+DQpUaGFuayBZb3UgZm9yIHRoZSByZXZpZXchIFBsZWFz
ZSBzZWUgaW5saW5lLjxicj4NCjxicj4NCiZndDtTdW1tYXJ5Ojxicj4NCiZndDtSZWFkeSB3aXRo
IG5pdHMuJm5ic3A7IFRoZXJlIGFyZSBhIGNvdXBsZSBvZiBtaW5vciBpc3N1ZXMgcmVsYXRlZCB0
byB0aGUgcHJvY2VkdXJlcyBhZnRlciBpbmFwcHJvcHJpYXRlIHVzYWdlIG9mIHRoZSBuZXcgaGVh
ZGVyLjxicj4NCiZndDs8YnI+DQomZ3Q7TWFqb3IgaXNzdWVzOjxicj4NCiZndDtOb25lPGJyPg0K
Jmd0Ozxicj4NCiZndDtNaW5vciBpc3N1ZXM6PGJyPg0KJmd0Ozxicj4NCiZndDsgczMuNC4xLCBs
YXN0IHBhcmE6IEluIGxpbmUgd2l0aCB0aGUgbGFzdCBzZW50ZW5jZSBvZiBTZWN0aW9uIDMuMiwg
dGhlIENvbnRlbnQtSUQgVVJMIG9ubHkgbmVlZHMgdG8gYmUgdW5pcXVlIHdpdGhpbiB0aGUgU0lQ
IG1lc3NhZ2Ugd2hlcmUgaXQgb2NjdXJzLjxicj4NCiZndDsmbmJzcDtJIGFzc3VtZSBpdCBkb2Vz
IG5vdCBtYWtlIHNlbnNlIHRvIGhhdmUgYSBDb250ZW50LUlEIGhlYWRlciBjb21iaW5lZCB3aXRo
IGEgbXV0aXBhcnQgbWVzc2FnZS1ib2R5ICh0aGlzIGlzbid0IHN0YXRlZCAtIG1heWJlIGl0IHNo
b3VsZCBiZSk7PGJyPg0KPGJyPg0KSSBhbSBub3QgYXdhcmUgb2YgYW55IGN1cnJlbnQgdXNlLWNh
c2UsIGJ1dCBJIHNlZSBubyByZWFzb24gdG8gZm9yYmlkIGl0LiBQZXJoYXBzIHNvbWVvbmUgd2ls
bCBjb21lIHVwIHdpdGggYSB1c2UtY2FzZSBpbiBmdXR1cmUuPGJyPg0KPGJyPg0KJmd0OyBJIGFt
IG5vdCBzdWZmaWNpZW50bHkga25vd2xlZGdlYWJsZSBpbiB0aGlzIGFyZWEgb2YgU0lQIHRvIGtu
b3cgaWYgdGhlcmUgY291bGQgYmUgY29udGVudC1pZCBVUkxzIGluIG90aGVyIGhlYWRlcnMgaWYg
dGhlcmUgaXMgYSBDb250ZW50LUlEDQo8YnI+DQomZ3Q7IGhlYWRlciBpbiB0aGUgbWVzc2FnZS4g
Jm5ic3A7VGh1cyBlaXRoZXIgdGhlIHN0YXRlbWVudCBhYm91dCBnbG9iYWwgdW5pcXVlbmVzcyBp
cyBpcnJlbGV2YW50IChhcyB0aGVyZSBpcyBvbmx5IG9uZSkgYW5kIGNhbiBiZSByZW1vdmVkIG9y
IGl0DQo8YnI+DQomZ3Q7IHNob3VsZCBiZSBtYWRlIGNvbnNpc3RlbnQgd2l0aCBzMy4yIHNvIHRo
YXQgdGhlIENvbnRlbnQgVVJMcyBhcmUgdW5pcXVlIHdpdGhpbiB0aGUgbWVzc2FnZS4gR2xvYmFs
IHVuaXF1ZW5lc3MgaXMgbmVpdGhlciBwb3NzaWJsZSBvciByZXF1aXJlZC48YnI+DQo8YnI+DQpU
aGUgc3RhdGVtZW50IGFib3V0IGdsb2JhbCB1bmlxdWVuZXNzIGlzIGEgYnVnLCBhbmQgd2lsbCBi
ZSBmaXhlZC4gVGhlIHZhbHVlIG9ubHkgaGFzIHRvIGJlIHVuaXF1ZSB3aXRoaW4gdGhlIG1lc3Nh
Z2UuPGJyPg0KPGJyPg0KJmd0OyBzMy40LjEsIHBhcmEgMTogRm9sbG93aW5nIG9uIGZyb20gdGhl
IHByZXZpb3VzIGNvbW1lbnQ6IElzIGEgVUEgYWxsb3dlZCB0byBhZGQgYSBDb250ZW50LUlEIGhl
YWRlciB0byBhIG1lc3NhZ2Ugd2l0aCBhIG11bHRpcGFydCBtZXNzYWdlLWJvZHk/PGJyPg0KPGJy
Pg0KSSBzZWUgbm8gcmVhc29uIHRvIGZvcmJpZCBpdC48YnI+DQo8YnI+DQomZ3Q7IHMzLjQuMTog
V2hhdCBzaG91bGQgYSBVQSBkbyBpZiBpdCByZWNlaXZlcyBhIG1lc3NhZ2Ugd2l0aCBhIENvbnRl
bnQtSUQgaGVhZGVyIHdoZW4gdGhlIG1lc3NhZ2UgaXMgbm90IGFsbG93ZWQgdG8NCjxicj4NCiZn
dDsgY29udGFpbiBvbmU/ICZuYnNwO0lzIHRoZXJlIHNvbWUgZ2VuZXJpYyBlcnJvciBwcm9jZWR1
cmUgdGhhdCBzaG91bGQgYmUgcmVmZXJlbmNlZD88YnI+DQo8YnI+DQpOb3JtYWwgUkZDIDMyNjEg
cHJvY2VkdXJlcyBhcHBseS4gSSBkb24ndCB0aGluayB3ZSB3YW50IHRvIGNvcHkvcGFzdGUgdGhl
IGdlbmVyaWMgaGVhZGVyIHByb2Nlc3NpbmcgcnVsZXMsPGJyPg0KPGJyPg0KJmd0OyBzNi4xOiBJ
IHN0YXJ0ZWQgbG9va2luZyBmb3Igc3BlY2lmaWNhdGlvbiB0aGF0IHRvbGQgbWUgdGhhdCBpdGVt
cyBhZGRlZCB0byB0aGUgU0lQIGhlYWRlciBmaWVsZHMgcmVnaXN0cnkgZWZmZWN0aXZlbHk8YnI+
DQomZ3Q7IGV4dGVuZCB0aGUgZGVmaW5pdGlvbiBvZiB0aGUgbWVzc2FnZS1oZWFkZXIgcHJvZHVj
dGlvbiBpbiBTZWN0aW9uIDI1LjFvZiBSRkMgMzI2MS4gJm5ic3A7Qml0IG9idmlvdXMgcGVyaGFw
cywgYnV0IGl0DQo8YnI+DQomZ3Q7IHdvdWxkIGJlIG5pY2UgaWYgaXQgaGFkIGJlZW4gc2FpZCBz
b21ld2hlcmUhICZuYnNwO1RpbWUgZm9yIGFuIEVycmF0dW0gcGVyaGFwcz88YnI+DQo8YnI+DQpJ
biB0aGUgQUJORiBvZiBSRkMgMzI2MSwgJnF1b3Q7bWVzc2FnZS1oZWFkZXImcXVvdDsgY29udGFp
bnMgdGhlIGhlYWRlciBmaWVsZHMgZGVmaW5lZCBpbiB0aGUgUkZDLCBwbHVzICZxdW90O2V4dGVu
c2lvbi1oZWFkZXImcXVvdDssIHdoaWNoIGlzIHVzZWQgZm9yIG5ldyBoZWFkZXJzLiBJIGFzc3Vt
ZSBwZW9wbGUgdGhpbmsgdGhhdCBpcyBjbGVhciBlbm91Z2ggOik8YnI+DQo8YnI+DQpIYXZpbmcg
c2FpZCB0aGF0LCB3aGF0IHlvdSBzdWdnZXN0IGlzIG5vdCBuZWNlc3NhcmlseSBhIGJhZCBpZGVh
LCBidXQgaXQgaXMgb3V0c2lkZSB0aGUgc2NvcGUgb2YgdGhpcyBkcmFmdC48YnI+DQo8YnI+DQom
Z3Q7Tml0cy9lZGl0b3JpYWwgY29tbWVudHM6PGJyPg0KJmd0Ozxicj4NCiZndDtBYnN0cmFjdDog
Jm5ic3A7SSB3b3VsZCBzdWdnZXN0IGFkZGluZyBhIHNlbnRlbmNlIHRoYXQgY2xhcmlmaWVzIHdo
YXQgdGhlIHVwZGF0ZSBvZiBSRkMgNTYyMSBpcyBtb2RpZnlpbmc6DQo8YnI+DQomZ3Q7PGJyPg0K
Jmd0O09MRDogVGhlIGRvY3VtZW50IGFsc28gdXBkYXRlcyBSRkMgNTYyMSwgdG8gZW5hYmxlIGEg
Q29udGVudC1JRCBVUkwgdG8gcmVmZXJlbmNlIGEgY29tcGxldGUNCjxicj4NCiZndDttZXNzYWdl
LWJvZHkgYW5kIG1ldGFkYXRhIHByb3ZpZGVkIGJ5IHNvbWUgYWRkaXRpb25hbCBTSVAgaGVhZGVy
IGZpZWxkcy4gPGJyPg0KJmd0Ozxicj4NCiZndDtORVc6IFRoZSBkb2N1bWVudCZuYnNwOyBhbHNv
IHVwZGF0ZXMgUkZDIDU2MjEsIHdoaWNoIG9ubHkgYWxsb3dzIGEgQ29udGVudC1JRCBVUkwgdG8g
cmVmZXJlbmNlIGENCjxicj4NCiZndDtib2R5LXBhcnQgdGhhdCBpcyBwYXJ0IG9mIGEgbXVsdGlw
YXJ0IG1lc3NhZ2UtYm9keS4gJm5ic3A7VGhpcyB1cGRhdGUgZW5hYmxlcyBhIENvbnRlbnQtSUQg
VVJMIHRvDQo8YnI+DQomZ3Q7cmVmZXJlbmNlIGEgY29tcGxldGUgbWVzc2FnZS1ib2R5IGFuZCBt
ZXRhZGF0YSBwcm92aWRlZCBieSBzb21lIGFkZGl0aW9uYWwgU0lQIGhlYWRlciBmaWVsZHMuIEVO
RDxicj4NCjxicj4NCkxvb2tzIG9rLiBJIHdpbGwgbW9kaWZ5IGFzIHN1Z2dlc3RlZC48YnI+DQo8
YnI+DQomZ3Q7czEuMiwgZmlyc3QgYnVsbGV0OiBzL2ZvciBwcm92aWRpbmcgbG9jYXRpb24vZm9y
IHByb3ZpZGluZyBsb2NhdGlvbiBpbmZvcm1hdGlvbi88YnI+DQo8YnI+DQpXaWxsIGJlIGZpeGVk
IGFzIHN1Z2dlc3RlZC48YnI+DQo8YnI+DQomZ3Q7czEuNC4xOiBOZWVkIHRvIGV4cGFuZCBVQUMg
KFVzZXIgQWdlbnQgQ2xpZW50KSBvbiBmaXJzdCB1c2FnZS48YnI+DQo8YnI+DQpJIHJlYWxpemVk
IHRoZSBmaXJzdCB1c2FnZSBpcyBpbiBzZWN0aW9uIDEuMywgc28gSSB3aWxsIGV4cGVuZCBpdCB0
aGVyZS48YnI+DQo8YnI+DQomZ3Q7czEuNC4xLCBwYXJhIDE6IHMvY2FuIGJlIGUuZy4gb2YvY2Fu
IGJlLCBmb3IgZXhhbXBsZSwgb2YvPGJyPg0KPGJyPg0KV2lsbCBiZSBmaXhlZCBhcyBzdWdnZXN0
ZWQuPGJyPg0KPGJyPg0KJmd0O3MzLjQuMTogTmVlZCB0byBleHBhbmQgVUEgKFVzZXIgQWdlbnQp
IG9uIGZpcnN0IHVzYWdlIChpbiBzZWN0aW9uIHRpdGxlKS48YnI+DQo8YnI+DQpXaWxsIGJlIGZp
eGVkIGFzIHN1Z2dlc3RlZC48YnI+DQo8YnI+DQomZ3Q7czQsIE5FVyB0ZXh0OiBzL2FsbG93IGNy
ZWF0aW5nL2FsbG93IHRoZSBjcmVhdGlvbiBvZi88YnI+DQo8YnI+DQpXaWxsIGJlIGZpeGVkIGFz
IHN1Z2dlc3RlZC48YnI+DQo8YnI+DQpSZWdhcmRzLDxicj4NCjxicj4NCkNocmlzdGVyPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_7594FB04B1934943A5C02806D1A2204B4CC1CD27ESESSMB109erics_--


From nobody Fri Jun 23 13:25:49 2017
Return-Path: <stpeter@stpeter.im>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B44111293D9; Fri, 23 Jun 2017 13:25:34 -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=stpeter.im header.b=XuMrT1Iu; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=nXsYfYp4
Received: 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-YA7y4yUOSt; Fri, 23 Jun 2017 13:25:32 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 988D112943C; Fri, 23 Jun 2017 13:25:32 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id D9F4C20D2C; Fri, 23 Jun 2017 16:25:31 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Fri, 23 Jun 2017 16:25:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stpeter.im; 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=m89Z2sg84W5HEJcRce fmSyCTT/Yym/7rkqtq+2c79JE=; b=XuMrT1IuuJjVAmI3g/XVqcK1dJ6G5JnsdI WaCz1Ya6Hj2InSYP6kankNOznKD/pzojBtwYPRWlggbJYuOzY1e+AonBsixGyqYZ oLQ5hkJ0Xugh0HPCn2S67SnT2T8mcLc7IwoJC3QzsJMOBZ+19+KAs34psMmzHA8R 0fu21ClK5oSpVekNyzqJUlYcqoYmZM44bdsEYghvXkHgbv7UvziVLPssrXha8lyp wyugjYye4xQc8/MQFyLnieWjAYUZRAzjdHQ0K8bGeLI634/a0ywxrELA87B8DNDa dCuNC0aHhLXSdCwvZPhRKNUgz5iDw65AVvabkk2TTHYx7sKJBpmg==
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=m89Z2sg84W5HEJcRcefmSyCTT/Yym/7rkqtq+2c79JE=; b=nXsYfYp4 9YsJWx8jYfdeU4l4tTzjZv/QfeCOUzWZkqAy+YJmzg72UgdNq4cwmq++7tCmz2FX EDeMO3b/BmLsddiguFVBSKLaE7ZdPNzgyaPfYdjyQJRQgYqaiFcmYIfYhj0bJ2XJ O7W10j6lLUdQIEe2MbRCpgrYh5tipARf8EABDQelZzeTbasBCsYdp0KJUNXwXKIF CIoZRX2l4c5GDc5ssmV5hDsyC4U19Pin/UZRTBZsjIvTEPuuz6niCt5hUF4g36mh NICE3zK70qzNHyftF/nxkkCtQe7iJj25iZpY+GOtQIKJSVAbMR5cNta3NTu4EPtI nkWOh93YvjDQdA==
X-ME-Sender: <xms:O3lNWfKpGPczoVPg41SYxYP9YLuACrH3uQNlxPFdtYA65pZjnnbtLQ>
X-Sasl-enc: AvkEJi7ALSA9VHw+2BZ4ozCZ+qc/arQAlXavjCIJO6Ap 1498249531
Received: from aither.local (unknown [76.25.4.24]) by mail.messagingengine.com (Postfix) with ESMTPA id 0C24E24009; Fri, 23 Jun 2017 16:25:30 -0400 (EDT)
Subject: Re: [precis] Secdir last call review of draft-ietf-precis-7564bis-07
To: John C Klensin <john-ietf@jck.com>, Matthew Miller <linuxwolf+ietf@outer-planes.net>, secdir@ietf.org
References: <149736681626.7439.2555177998557552719@ietfa.amsl.com> <8ea90b99-3005-0afb-da93-63cd1abfc905@stpeter.im> <FEF9D2847A170FC48DE8EC5E@PSB>
Cc: draft-ietf-precis-7564bis.all@ietf.org, ietf@ietf.org, precis@ietf.org
From: Peter Saint-Andre <stpeter@stpeter.im>
Message-ID: <74ad8473-6036-2965-6833-7d59b0f9b038@stpeter.im>
Date: Fri, 23 Jun 2017 14:25:29 -0600
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: <FEF9D2847A170FC48DE8EC5E@PSB>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Q714szRyY7OU4BNK-dCxrW2wVYc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 23 Jun 2017 20:25:35 -0000

Hi John,

Thanks for your note, and my apologies for the slow reply. Comments inline.

On 6/13/17 7:02 PM, John C Klensin wrote:
> 
> 
> --On Tuesday, June 13, 2017 17:02 -0600 Peter Saint-Andre
> <stpeter@stpeter.im> wrote:
> 
>> Hi Matt, thanks for the review - it's much appreciated.
>>
>> Just so you know: through discussion of Daniel Migualt's
>> secdir review of 7700bis (we're progressing them all together
>> this time!), I realized that it might be help to add another
>> example of visually confusing characters to 7564bis, so I plan
>> to mention CYRILLIC SMALL LETTER A U+0430 vs. LATIN SMALL
>> LETTER A U+0061 (which will be more familiar to readers than
>> the Cherokee characters already in the document).
> 
> Peter,
> 
> I don't want to throw the proverbial spanner in the works, but,
> just as things changes just as the original PRECIS documents
> were being published, I wonder if some other things that appear
> to be in process now could do it to us again.  
> 
> For example, consider draft-freytag-troublesome-characters.
> Despite having contributed to it and expecting to continue to do
> so, I've got some misgivings about the document and proposed
> registry as IETF work but, if it were to be adopted, it seems to
> me that it would be useful for the PRECIS documents to
> normatively reference it, especially for Identifier Class. 

Given that we're dealing with a seemingly tenuous hypothetical, the best
approach might be for that I-D (if eventually published as an RFC) to
update the relevant PRECIS and IDNA RFCs? We'll need to do that for the
IDNA RFCs anyway because they're not currently under revision, as the
PRECIS RFCs are.

>  To
> some extent, that draft is a remedy for some of the issues
> raised in the long-stalled draft-klensin-idna-5892upd-unicode70,
> but it doesn't make those issues, and the lack of
> comprehensiveness of normalization, go away.

I'm not sure that anything could make those issues go away.

> Probably less important, but it might be advantageous to
> incorporate some of the "whatever decisions you make, people
> will probably hold you accountable if there are problems" tone
> of draft-klensin-idna-rfc5891bis into the PRECIS documents.  It
> might even be that RFC 7940, possibly supplemented by
> draft-freytag-lager-variant-rules, would be a better, or at
> least useful alternative, way to present some or all of the
> PEECIS rule sets than the current approach. 

One question in my mind is whether an approach such as that of RFC 7940
is so much better that it's worth scrapping / rewriting the PRECIS bis
I-Ds along those lines. Right now it's not even clear what criteria we'd
use to judge "better" or "useful" here - presumably specification
clarity and precision, algorithmic completeness, and reduced error rates
in code implementations might factor into the decision. But I don't
sense that we have a good handle on making these decisions yet. Another
tradeoff here is making the relatively small fixes to the PRECIS RFCs in
a relatively short amount of time (measured in IETF years) vs. making a
larger overhaul in a longer amount of time (and whether there is
sufficient energy to do so). Given our track record in
internationalization, I'd prefer to get these PRECIS fixes done now and
then look at a larger effort.

> On a somewhat different topic, the Greek, Latin,  and Cyrillic
> scripts are so closely related that finding examples of pairs of
> similar-looking characters is in the low-lying fruit category
> because the similarities are not coincidences but the result of
> derivation and extensive borrowing (something of the same thing
> can be said for the Latin-Cherokee relationship, at least in
> printed, rather than cureive, forms). 

Indeed.

>  The examples that may be
> more scary, just because there is no evolutionary theory to
> predict were to look, would be things like the resemblances
> among the Latin U+006F, the Lao U+0ED0, the Ethiopic U+12D0, the
> New Tai Lue U+19D0, and of course the ASCII/European digit
> U+0030 and probably many more, with the group perhaps best
> described as "open circle graphemes" or something like that.

Well, circles are common enough, so it's reasonable that they'd show up
in many different contexts as both letters and numbers (which is why we
have confusion between the letter "O" and the number zero even in the
basic Latin repertoire) and even as punctuation marks and symbols. But I
like the examples you've mentioned and will add them to 7564bis to
further illustrate the problem, all the while understanding full well
that a complete list of examples or an explanation of why such examples
are problematic is outside the scope of this specification (which is why
we point to UTR36 and UTS39).

Peter



From nobody Fri Jun 23 17:19:00 2017
Return-Path: <agenda@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 E86FF129B69; Fri, 23 Jun 2017 17:13:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: IETF Agenda <agenda@ietf.org>
To: "IETF Announcement List" <ietf-announce@ietf.org>
Cc: 99all@ietf.org, ietf@ietf.org
Subject: IETF 99 Final Agenda
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: IETF Agenda <agenda@ietf.org>
Message-ID: <149826319187.7852.3700772837147031578.idtracker@ietfa.amsl.com>
Date: Fri, 23 Jun 2017 17:13:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5IcXAjVdwC1jxIXeHKzbOW3qa2Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Jun 2017 00:13:13 -0000

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

The final agenda is now available.

https://datatracker.ietf.org/meeting/99/agenda.html
https://datatracker.ietf.org/meeting/99/agenda.txt

While this is considered the final agenda for printing, changes may be made to the agenda up until and during the meeting. Updates will be reflected on the web versions of the agenda. 

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

Don’t forget to register for these exciting IETF 99 events!

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

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

Hackathon 
	Signup: https://www.ietf.org/registration/ietf99/hackathonregistration.py
	More information: http://ietf.org/hackathon/99-hackathon.html 
	Keep up to date by subscribing to: 
	https://www.ietf.org/mailman/listinfo/hackathon

Code Sprint
	Signup: https://trac.tools.ietf.org/tools/ietfdb/wiki/IETF99SprintSignUp
	More information: https://trac.tools.ietf.org/tools/ietfdb/wiki/IETF99Sprint


From nobody Sat Jun 24 14:04:11 2017
Return-Path: <eburger@standardstrack.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E30E71293F2 for <ietf@ietfa.amsl.com>; Sat, 24 Jun 2017 14:04:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.781
X-Spam-Level: 
X-Spam-Status: No, score=-1.781 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_HELO_PASS=-0.001, T_DKIM_INVALID=0.01, T_SPF_PERMERROR=0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=standardstrack.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BXlYQolJYob5 for <ietf@ietfa.amsl.com>; Sat, 24 Jun 2017 14:04:08 -0700 (PDT)
Received: from biz221.inmotionhosting.com (biz221.inmotionhosting.com [23.235.223.233]) (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 6A159128D44 for <ietf@ietf.org>; Sat, 24 Jun 2017 14:04:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=Message-Id:In-Reply-To:To:References:Date: Subject:Mime-Version:Content-Type:From:Sender:Reply-To:Cc: 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=n/fmTBZ/EkvKmdPLcKRpgL0HEDdHSlHfFFG0yNE7Clc=; b=RfI+OREOEofDUypy10fpEeWZr N6eKbL6QLJpQqSQkEO/Iq5huHIDzgyrHGRQjwgvchA+izZw06RkOzh5+im50PEBn0DJITaWJ4yoZ5 d79Qr3jLo5iQ1q0TfZRRYaYQBwYKR/DC2X4o5SSifmsthkqcZp5Quh7CBVwA7NM3ubRbY=;
Received: from ip68-100-197-40.dc.dc.cox.net ([68.100.197.40]:56809 helo=[192.168.10.25]) by biz221.inmotionhosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.87) (envelope-from <eburger@standardstrack.com>) id 1dOsDd-0003Sc-LE for ietf@ietf.org; Sat, 24 Jun 2017 14:04:08 -0700
From: Eric Burger <eburger@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_378B9B58-ABC7-496C-8318-1042FEE67EBA"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Saturday as start day
Date: Sat, 24 Jun 2017 17:03:48 -0400
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <25CD3E0C-A03D-49A3-8375-AD4D834BF94B@gondrom.org>
To: ietf@ietf.org
In-Reply-To: <25CD3E0C-A03D-49A3-8375-AD4D834BF94B@gondrom.org>
Message-Id: <E01EDC06-5AEE-4957-AA46-DA87AF9D46C1@standardstrack.com>
X-Mailer: Apple Mail (2.3273)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - biz221.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Get-Message-Sender-Via: biz221.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: biz221.inmotionhosting.com: eburger@standardstrack.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/sZEhO80SB3LuJipoH-E0ZOjrQzc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 24 Jun 2017 21:04:10 -0000

--Apple-Mail=_378B9B58-ABC7-496C-8318-1042FEE67EBA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On the one hand, I won=E2=80=99t be working on Saturday.

On the other hand, as someone on a limited budget (read university) =
paying for someone else (read student) to go to the IETF, that Saturday =
night stay has a big impact on airfare.

So long as we don=E2=80=99t have Saturday creep in as a =E2=80=98regular=E2=
=80=99 IETF working day, I=E2=80=99m for the change.

> On Jun 23, 2017, at 1:39 AM, Tobias Gondrom =
<tobias.gondrom@gondrom.org> wrote:
>=20
> I also agree. This is good idea.
> (with my individual hat on... ;-) )
> Best regards, Tobias
>=20
> On June 21, 2017 8:46:57 PM GMT+08:00, Bob Hinden =
<bob.hinden@gmail.com> wrote:
> Alissa,
>=20
>  On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>=20
>  Hi all,
>=20
>  Based on a suggestion from Paul Hoffman, the IESG believes it would =
be beneficial to denote the official start of IETF meetings to be on =
Saturday rather than Sunday, starting with IETF 100. We believe this =
would be sensible given that events such as the hackathon and code =
sprint start on Saturday, and may make it easier for some participants =
to get travel approval to attend those events. This change would be =
reflected in the dates posted on the IETF web site and sent out in email =
announcements. We are not proposing any changes in terms of the =
scheduling of any meeting-related events, the full availability of the =
meeting network starting on Sunday, the opening of on-site registration, =
or the meeting fee.
>=20
>=20
> I think this is a fine idea, essentially formalizing what has happened =
informally.  I suspect once in effect it will push the network to be =
deployed earlier, but given current Saturday events, that was also =
probably going to happen at some point.
>=20
> Thanks,
> Bob
>=20
>=20
>=20
>  If you have feedback about this change, please send it to =
ietf@ietf.org, or exceptionally to iesg@ietf.org, by July 5, 2017.
>=20
>=20
>=20
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.


--Apple-Mail=_378B9B58-ABC7-496C-8318-1042FEE67EBA
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 - http://gpgtools.org

iQIcBAEBCAAGBQJZTtO0AAoJEORoZaSQsc1Ik7oP/ipKI6ANvukkIdwY+YCLb8iC
d2iEO/31rafcYqkcEEys7W7n2qNP/lUJI9PSZt17JeveVMyzyuNyqJ4AEwxWDShk
ZHTmaEC3aBX9QFK39gPw0XaT+58i/AbWgcvXXuIOk3SA0+Xi+Cb9eqsjMgImBaxd
OEj/zUCnc8E2QPtVgUs9o+HRprsOieM2Eo2+sNJ4f+Uh6kzdV/mC8dJkB1yOMkYC
ptuuEyczweAvyXFqqA0g8nvd9HR/J7zkYSSyX9jCFDCjZS5UGu4Y36lCzCpLw0ci
wV2MdednnZ7cLIRdOdWimyhvhry617/kUWtFBmeU5UekUfgpmLNZcWxTNoMUJsYE
e1cttcn4as0L2P858OzPseiTPQgXEJ016aex9TQ0IXiijz0ScRLkQerosJfuBX00
5Zr2AMFhwn3WBYBT+5NH6LBJgrLGdvWa3zttoccgMYZlM1kXxToqS+/6q/qimkTC
t1gP5UB1BCR3kIuIzkeoK3qCqwZFSKUrHniZUCFuFiK6Jgrlx6MPjKcyJztnNhgK
CKkS2EJ1RZ7C+jCCsiGXoVJByu2S1PEkaEHVmaPekz8tLnhvEGZnPqBGyPl6i6gu
NRc+zT6rnI0H0OweiQMWAHdTZ1hRUjLdt2BHPa+tOLoYktbQPZ4hcUAqmget/zrH
71I5GQK3IqZlTUbmp7AK
=KsMN
-----END PGP SIGNATURE-----

--Apple-Mail=_378B9B58-ABC7-496C-8318-1042FEE67EBA--


From nobody Sun Jun 25 03:11:46 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 90A92129462; Sun, 25 Jun 2017 03:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.699
X-Spam-Level: 
X-Spam-Status: No, score=-4.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0uBS7ynBqZFg; Sun, 25 Jun 2017 03:11:41 -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 5A3321242F5; Sun, 25 Jun 2017 03:11:38 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.96.65]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MNIAz-1dR0SA0zwP-006ykk; Sun, 25 Jun 2017 12:11:31 +0200
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
To: ietf@ietf.org
Cc: httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>, draft-ietf-httpbis-early-hints@ietf.org, ietf-http-wg@w3.org, alexey.melnikov@isode.com
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de>
Date: Sun, 25 Jun 2017 12:11:29 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:TxAO1g1ckcQ1IgCGXt5jOqL2bnyoR6hoftTQkPw9Di0QaMxLl1m XzZ+AA3I0L0zmv6EA/DZbrTeGfUbvKRTrIm8h+BnHyZPU8PYEADuyAW9VjKasIdMlulBRzc 5/ZMXNNW0jd58V31qFuorYqGw7jXNrVhmby+ivXSvGxeRrq/5DY3mz/Dq7GmXiEDonMW33K HL3URfUidkkjtm6H5XE2g==
X-UI-Out-Filterresults: notjunk:1;V01:K0:uaD7ch7hzj8=:8xj7/07D+PHyV+EPlaZZUN 2bJNfgd0OQKECnbcUZ9ESTm743yGO4GFp9LDjLvvKTCSl3FMb0Wceul4OK8ad90C62bwLo5Ep wL4o7yfaD7F6jzXVxdTc17pNPoIbZN2QViAsOlzpSvwEqQKaYt9qjNdlwdvdYiMb3kEXxdhCs RfDKOxRD2cZicxzRb8m8ok2zDjmYTEHhAaucE4xYuUz8vgkrm7P1yLyf3LUR1fQxZNH+frRxY AoJpEiRNNXonJQDQYfbgWEjjC6CYnHd2Zifh8uLOslSCfVcyPmFs1L/eIcSBCqPLEoIGxQTyF w3K/vHnpyN74jym11wyNT6WEk7+EE7w4eEsokFCy88bzrM2JsbmsbM2kKfHjAM3epBL2VVaB/ qCOOhGAW7pZ3Q1PqKlp8sI+X/UpK0HkGyhiX03GCRYq5gM+vGUiJdF7NdaBARvyJoqRNEK0JQ u/9UwtLrN87TCZ4eL6w7S402qE+qA73Dq5IpGInc1ysVJe7+G4wZOVkIFkSvdvsZQokgEJtfN ouLTaE+9CuYOWkcXuoqFGkIeIE1sNQt4vwGhv6NMP3rEdm6ceW7lJ40d576AYsPT3ls2X4dVT /XHx83vdpa6qiGLyPAmI8Vdz0vKZo9u81h5DFGs6k355g/6fR6M/OtY5Tdhjj+yTQ3yCsjnwO 7TzsU2lwWFr4BAd8ybw8JbjqJ0l1W4f3eDEIs0S8eZvt58HgJFade2jlxNtwGsAInlwQmSDtP L3DbmAmm4nbndCqGwUdKI0FboM1yRt0iNsk7huSZuy8vvlQAOZ/kZsCUFGB7usP1clu3pacf2 6Gc1eZ+
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/rVwe407uNI7IWcUxLYeRoYEBL6k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jun 2017 10:11:44 -0000

On 2017-06-21 18:59, The IESG wrote:
> 
> The IESG has received a request from the Hypertext Transfer Protocol WG
> (httpbis) to consider the following document: - 'An HTTP Status Code for
> Indicating Hints'
>    <draft-ietf-httpbis-early-hints-03.txt> as Experimental RFC
> ...


Here's my feedback...:

2.  103 Early Hints

    ...

    A server MUST NOT include Content-Length, Transfer-Encoding, or any
    hop-by-hop header fields ([RFC7230], Section 6.1) in a 103 (Early
    Hints) response.

That's a bit weird here, because the requirements for C-L and T-E are 
generic to 1xx, and already are stated in RFC 7230. The text above makes 
it sound as if these are specific to 103, which they are not.

For hop-by-hop, I'm not convinced that the requirement is needed here.

    ...

    An intermediary MAY drop the informational response. (...)

That seems to contradict a MUST-level requirement in RFC 7231 
(https://www.greenbytes.de/tech/webdav/rfc7231.html#rfc.section.6.2.p.3)

    The following example illustrates a typical message exchange that
    involves a 103 (Early Hints) response.

    Client request:

      GET / HTTP/1.1
      Host: example.com

(maybe insert blank line do delimit the message)

    Server response:

      HTTP/1.1 103 Early Hints
      Link: </style.css>; rel=preload; as=style
      Link: </script.js>; rel=preload; as=script

      HTTP/1.1 200 OK
      Date: Fri, 26 May 2017 10:02:11 GMT
      Content-Length: 1234
      Content-Type: text/html; charset=utf-8
      Link: </style.css>; rel=preload; as=style
      Link: </script.js>; rel=preload; as=script

      <!doctype html>
      [... rest of the response body is ommitted from the example ...]

The example suggests that early hints are repeated in the final 
response. Do they have to, actually?


3.  Security Considerations

    Some clients might have issues handling 103 (Early Hints), since
    informational responses are rarely used in reply to requests not
    including an Expect header ([RFC7231], Section 5.1.1).

s/header/header field/

    In particular, an HTTP/1.1 client that mishandles an informational
    response as a final response is likely to consider all responses to
    the succeeding requests sent over the same connection to be part of
    the final response.  Such behavior may constitute a cross-origin

s/may/might/ or /can/ (or invoke https://tools.ietf.org/html/rfc8174)

    information disclosure vulnerability in case the client multiplexes
    requests to different origins onto a single persistent connection.

    ...

5.  Acknowledgements

Nit: This should be an appendix (the last one).

6.  Changes

Nit: This should be an appendix.


Best regards, Julian


From nobody Sun Jun 25 03:46:41 2017
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB10D126CD8; Sun, 25 Jun 2017 03:46:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 iaGqcBWThPmc; Sun, 25 Jun 2017 03:46:36 -0700 (PDT)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 4A6FB120227; Sun, 25 Jun 2017 03:46:35 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id v5PAkTTa029029; Sun, 25 Jun 2017 12:46:29 +0200
Date: Sun, 25 Jun 2017 12:46:29 +0200
From: Willy Tarreau <w@1wt.eu>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: ietf@ietf.org, httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>, draft-ietf-httpbis-early-hints@ietf.org, ietf-http-wg@w3.org, alexey.melnikov@isode.com
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
Message-ID: <20170625104629.GA29021@1wt.eu>
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/O3nbCxfxKAFje3oHBLumrxz8tl4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jun 2017 10:46:39 -0000

Hi Julian,

On Sun, Jun 25, 2017 at 12:11:29PM +0200, Julian Reschke wrote:
>    An intermediary MAY drop the informational response. (...)
> 
> That seems to contradict a MUST-level requirement in RFC 7231
> (https://www.greenbytes.de/tech/webdav/rfc7231.html#rfc.section.6.2.p.3)

Not completely. An intermediary not aware of 103 may map it to 100. If
the intermediary inserted an "Expect: 100 continue" header field, we
can reasonably imagine that such an intermediary might also drop the
returning 103. This wording in 7231 may even encourage some implementations
to do so : "A proxy MUST forward 1xx responses unless the proxy itself
requested the generation of the 1xx response". Speaking about 1xx here
may be read as "I asked for 100, I'm receiving 1xx so that matches".

>    Server response:
> 
>      HTTP/1.1 103 Early Hints
>      Link: </style.css>; rel=preload; as=style
>      Link: </script.js>; rel=preload; as=script
> 
>      HTTP/1.1 200 OK
>      Date: Fri, 26 May 2017 10:02:11 GMT
>      Content-Length: 1234
>      Content-Type: text/html; charset=utf-8
>      Link: </style.css>; rel=preload; as=style
>      Link: </script.js>; rel=preload; as=script
> 
>      <!doctype html>
>      [... rest of the response body is ommitted from the example ...]
> 
> The example suggests that early hints are repeated in the final response. Do
> they have to, actually?

If we imagine that clients ignore 103 or that intermediaries occasionally
drop it, I think it's desirable to send them. Said differently, the 103
response prepends a copy of the Link header fields that the final response
is supposed to present to help the client fetch them earlier.

Regards,
Willy


From nobody Sun Jun 25 03:51:03 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 B0F03126DFF; Sun, 25 Jun 2017 03:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.699
X-Spam-Level: 
X-Spam-Status: No, score=-4.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IukgNc0tlMdJ; Sun, 25 Jun 2017 03:51:00 -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 B840A120227; Sun, 25 Jun 2017 03:50:59 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.96.65]) by mail.gmx.com (mrgmx003 [212.227.17.190]) with ESMTPSA (Nemesis) id 0Lta9E-1doLEa2Auy-010rSI; Sun, 25 Jun 2017 12:50:32 +0200
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
To: Willy Tarreau <w@1wt.eu>
Cc: ietf@ietf.org, httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>, draft-ietf-httpbis-early-hints@ietf.org, ietf-http-wg@w3.org, alexey.melnikov@isode.com
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de> <20170625104629.GA29021@1wt.eu>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <602955e2-cfd0-e4c8-7afa-e8f3ea78ab3a@gmx.de>
Date: Sun, 25 Jun 2017 12:50:30 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <20170625104629.GA29021@1wt.eu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:31ijMgdYwwjg8fzeF/nP/v1yKATGlffrDC5ytyGrNVQLK+ht+uW p2TQ2fCROgxMeDcIy13i+RpAmpql8EiU5AdWVbJjEiNTSUSt0VFzmY6vg+4dCMtC1ya0hZ1 ycU+ubfo9DRbSuvOId7w/kqlMNBlM0rFfDyOeWjA/3Vtp1FUzElERP5VW5UpG9hb8VqJ0yS DYeIpNYLVeCl+CURekytg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:vbGrI08fw90=:GYG8/qV+8qsHl3yz7Qee9/ tjMvcJf/GOUemm9HXT98wTSwkCzoYBqNgCYZelGEcVqXYPvYACMTCMX3QKgFC57JtdIyqkOkG o64UADOZiG6jErbr4GtLrckBGRHcl2SS/gi91iZtpX1f6uTducTxywCTusd4+JzkkpVd42RQ+ Y3OkYS6qLdLALe4Agbo/VjTLGo9Kz6kngkhOvoTClwZOfaIGzImE8tN7RhOezfjBHkPiaBOhC Rit4ZIw6B46zyuT76n/zFpGVK49rDdn7gM6QJuvQP5Z8k6ScMixIqh2g2rshG5JFypl8o1xBL nEZh/3S5grWdMhwcKVttmJpq2JIaWUVfJzkD5FNim6g4VRFq/fTXEVJLl3daIIOsfHoGIDN3k VsWf0YfRkjQu3omtI9mIPpHKDCPRpS63RwYbT58JFPZNPAUknVH/W+W/sTWE1UO1i3Ze9D/wJ lafR3GMU8f1uUAJC0Wml7Q8vwUQpYxF1WScY6NK9aocAFv09nfTG+w8EVh75uXKcCrisH48IG NqqeCx0YmYg2YP+EuEYmDB5mVcGR1dzjCFCeCig2aIEYZ33jR09XMwKuYnPoAlAZbZruZ688k J6QYv+E9oNScGIUaXRVQX7ZTud1v6IT9sxF0VCTyD9sXG49R5DRqssMx/8XAl4rvZfIHfLIOz wvstUN46AX8ovIatzR98LhxJRHooVQwpU28tb987VUs8Jp/GonYPsJE3J/bwWGlhcy/1ngACK Aq6dCspmMidm8rKiHZFknQhLvAeAwmK2xupwzHEoo5S+VD4Rif1LEpWSR/6qPozPPCNjIutO1 /1tdcjg
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/38TWz8dM4nwQOHrg1lwaqtU-SjM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jun 2017 10:51:02 -0000

On 2017-06-25 12:46, Willy Tarreau wrote:
> Hi Julian,
> 
> On Sun, Jun 25, 2017 at 12:11:29PM +0200, Julian Reschke wrote:
>>     An intermediary MAY drop the informational response. (...)
>>
>> That seems to contradict a MUST-level requirement in RFC 7231
>> (https://www.greenbytes.de/tech/webdav/rfc7231.html#rfc.section.6.2.p.3)
> 
> Not completely. An intermediary not aware of 103 may map it to 100. If

It may do so, but it's not allowed to (IMHO).

> the intermediary inserted an "Expect: 100 continue" header field, we
> can reasonably imagine that such an intermediary might also drop the
> returning 103. This wording in 7231 may even encourage some implementations
> to do so : "A proxy MUST forward 1xx responses unless the proxy itself
> requested the generation of the 1xx response". Speaking about 1xx here
> may be read as "I asked for 100, I'm receiving 1xx so that matches".

But that sounds like a bug in the proxy to me. A 103 is not a 100.

>>     Server response:
>>
>>       HTTP/1.1 103 Early Hints
>>       Link: </style.css>; rel=preload; as=style
>>       Link: </script.js>; rel=preload; as=script
>>
>>       HTTP/1.1 200 OK
>>       Date: Fri, 26 May 2017 10:02:11 GMT
>>       Content-Length: 1234
>>       Content-Type: text/html; charset=utf-8
>>       Link: </style.css>; rel=preload; as=style
>>       Link: </script.js>; rel=preload; as=script
>>
>>       <!doctype html>
>>       [... rest of the response body is ommitted from the example ...]
>>
>> The example suggests that early hints are repeated in the final response. Do
>> they have to, actually?
> 
> If we imagine that clients ignore 103 or that intermediaries occasionally
> drop it, I think it's desirable to send them. Said differently, the 103
> response prepends a copy of the Link header fields that the final response
> is supposed to present to help the client fetch them earlier.
> ...

Understood. But is this a requirement or just a suggestion? Does a 
client need to forget the information from the 103 when it's not 
repeated in the final response?

Best regards, Julian


From nobody Sun Jun 25 03:54:09 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 E291C1296CF; Sun, 25 Jun 2017 03:54:07 -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: bier@ietf.org, ietf@ietf.org, draft-ietf-bier-architecture.all@ietf.org, dromasca@gmail.com
Subject: Genart last call review of draft-ietf-bier-architecture-07
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149838804788.3251.829139224134758886@ietfa.amsl.com>
Date: Sun, 25 Jun 2017 03:54:07 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0GE3-pw35mGuaJStV2OkioGKl3E>
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, 25 Jun 2017 10:54:08 -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-bier-architecture-??
Reviewer: Dan Romascanu
Review Date: 2017-06-25
IETF LC End Date: 2017-06-29
IESG Telechat date: 2017-07-06

Summary:

This document specifies a new architecture known as "Bit Index Explicit
Replication" (BIER) for the forwarding of multicast data packets through a
"multicast domain".  It does not require a protocol for explicitly building
multicast distribution trees, nor does it require intermediate nodes to
maintain any per-flow state. This architecture is .  While the Abstract and
Introduction of the document mentions Architecture as the principal scope, this
document goes well beyond the scope of a typical architectural document.
including detailed definitions of the procedures, terminology and normative
algorithms required for BIER.

The document is clear and detailed. Because of its structure, I am missing some
information that usually can be found in architecture documents. I included
these in the 'minor issues' list. Although none of these may be a show-stopper,
I believe that addressing these before document approval can improve the
quality of the document and of the overall BIER work.

Major issues:

Minor issues:

1. As the document is targeting 'Experimental' it would be useful to mention
what is the scope of the experiment. The charter actually says:

' The scope of the experiment will be
documented in the output of the Working Group.'

Would not the Architecture document be the right place for this? If not, is
there another document that deals or is planned to define the scope of the
experiment?

2. While the Abstract and Introduction of the document mentions Architecture as
the principal scope, this document is different from a typical architectural
document. While it defines well the procedures, terminology and normative
algorithms required for BIER Intra-domain forwarding, it goes well beyond the
level of detail that other similar documents go. Specifications of the
procedures and normative algorithm should be mentioned in Abstract and
Introduction, they occupy the same or more space than architecture.

3. On the other hand I am missing the relationship with other work items in the
BIER charter - there is no manageability section for example, there is no
reference to the performance impact in networks. Maybe these are dealt with in
a different document or documents or BIER, if so it would be good at least to
mention and reference these here.

4. I also would have expected the architecture document to refer the use cases
document and note which of the use cases are being addressed and how -
draft-ietf-bier-use-cases is not even included in the references.

5. Sections 3 to 6 mentioned repeatedly provisioning. As there is no Operations
and Manageability section as in many other Routing Area documents, it is not
clear how this is expected to happen. For example draft-ietf-bier-bier-yang is
not mentioned or referred. I suggest adding a note (and maybe references) for
clarity.

6. In section 8 I found:

'Every BFR must be provisioned to know which of its interfaces lead to
   a BIER domain and which do not.  If two interfaces lead to different
   BIER domains, the BFR must be provisioned to know that those two
   interfaces lead to different BIER domains. '

It seems that the two 'must' in these sentences would rather be capitalized.

Nits/editorial comments:



From nobody Sun Jun 25 04:28:49 2017
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA4221272E1; Sun, 25 Jun 2017 04:28:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_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 fVUGLuH12FyC; Sun, 25 Jun 2017 04:28:46 -0700 (PDT)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id AFE3D12009C; Sun, 25 Jun 2017 04:28:45 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id v5PBSghq029082; Sun, 25 Jun 2017 13:28:42 +0200
Date: Sun, 25 Jun 2017 13:28:42 +0200
From: Willy Tarreau <w@1wt.eu>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: ietf@ietf.org, httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>, draft-ietf-httpbis-early-hints@ietf.org, ietf-http-wg@w3.org, alexey.melnikov@isode.com
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
Message-ID: <20170625112842.GA29052@1wt.eu>
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de> <20170625104629.GA29021@1wt.eu> <602955e2-cfd0-e4c8-7afa-e8f3ea78ab3a@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <602955e2-cfd0-e4c8-7afa-e8f3ea78ab3a@gmx.de>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EBE_6Bp6uXedyFFdQoyFO2qQrRE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jun 2017 11:28:48 -0000

On Sun, Jun 25, 2017 at 12:50:30PM +0200, Julian Reschke wrote:
> On 2017-06-25 12:46, Willy Tarreau wrote:
> > Hi Julian,
> > 
> > On Sun, Jun 25, 2017 at 12:11:29PM +0200, Julian Reschke wrote:
> > >     An intermediary MAY drop the informational response. (...)
> > > 
> > > That seems to contradict a MUST-level requirement in RFC 7231
> > > (https://www.greenbytes.de/tech/webdav/rfc7231.html#rfc.section.6.2.p.3)
> > 
> > Not completely. An intermediary not aware of 103 may map it to 100. If
> 
> It may do so, but it's not allowed to (IMHO).

I agree with you but there's probably a difference with what is really
deployed in field. However I'm now seeing a wording issue here, because
saying "An intermediary MAY drop the informational response" suggests
to intermediary implementations that this is permitted. I think that
using just a warning for server implementations would be more appropriate,
like "A server should be prepared to see its 103 responses silently dropped
or altered by some non-compliant intermediaries".

> > the intermediary inserted an "Expect: 100 continue" header field, we
> > can reasonably imagine that such an intermediary might also drop the
> > returning 103. This wording in 7231 may even encourage some implementations
> > to do so : "A proxy MUST forward 1xx responses unless the proxy itself
> > requested the generation of the 1xx response". Speaking about 1xx here
> > may be read as "I asked for 100, I'm receiving 1xx so that matches".
> 
> But that sounds like a bug in the proxy to me. A 103 is not a 100.

Sure, but it's also suggested that when processing a code XYY that you
don't know, you can consider that it will act like X00. I'm not
justifying that some might be doing this, just that we need the spec to
be robust against such bogus behavious *if they exist*. Especially
interim responses, which have always been tricky to get right
everywhere :-/

> > > 
> > > The example suggests that early hints are repeated in the final response. Do
> > > they have to, actually?
> > 
> > If we imagine that clients ignore 103 or that intermediaries occasionally
> > drop it, I think it's desirable to send them. Said differently, the 103
> > response prepends a copy of the Link header fields that the final response
> > is supposed to present to help the client fetch them earlier.
> > ...
> 
> Understood. But is this a requirement or just a suggestion? Does a client
> need to forget the information from the 103 when it's not repeated in the
> final response?

Hmmm the text says :
  "This memo defines a status code for sending an informational response
   ([RFC7231], Section 6.2) that contains header fields that are likely
   to be included in the final response"

Thus I think that the final header fields are the real ones, and that
those sent early are more about hints to help the client get mostly
prepared. Can there be a conflict between two overlapping header field
values for the same link ? If so, some text needs to be appended to
mandate that the final response the the only authoritative one and that
the interim ones are only here to help fill silence periods on the link.

Willy


From nobody Sun Jun 25 04:37:35 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 EF53F129A9A; Sun, 25 Jun 2017 04:37:32 -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, FREEMAIL_FROM=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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uypFUF8ezOip; Sun, 25 Jun 2017 04:37:29 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15]) (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 17BCF1242F7; Sun, 25 Jun 2017 04:37:28 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.96.65]) by mail.gmx.com (mrgmx002 [212.227.17.190]) with ESMTPSA (Nemesis) id 0MMBun-1dPwv50PiH-007zce; Sun, 25 Jun 2017 13:37:02 +0200
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
To: Willy Tarreau <w@1wt.eu>
Cc: ietf@ietf.org, httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>, draft-ietf-httpbis-early-hints@ietf.org, ietf-http-wg@w3.org, alexey.melnikov@isode.com
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de> <20170625104629.GA29021@1wt.eu> <602955e2-cfd0-e4c8-7afa-e8f3ea78ab3a@gmx.de> <20170625112842.GA29052@1wt.eu>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <8e93bbfc-b609-0392-5c78-114103accaed@gmx.de>
Date: Sun, 25 Jun 2017 13:36:59 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <20170625112842.GA29052@1wt.eu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:QviBdaRJbeEq6b035JWByHkUwk0QtVO1b2HovGkA9csI5VYRV6J dEAKtePW6FATm5PXKpx5cbBqzXyxtGKMo3MeoSifRCwOoooH0ji7XpGVGfbnBgv61t0ezMP DlVeT8Ez5dKX5XjQ4xYylC6zzfgtsOFqTJu8lhOLJ8KW+nvS63nW0ZE/yNPUlPeLYzL96n2 AUv7Mtbpmq20gS4TIec2A==
X-UI-Out-Filterresults: notjunk:1;V01:K0:3ZupbSrS5B4=:T9h1XRKvcJsGBgoX20EyAT fbUOqNzVEOBN/PKxYa3IdhGSFijt4hyfF/Jd23gg8y18jK3NxUOtoyH2DHCGYlgGLLKgkTBgm 7tHzYkzhyNFUzBe7c+DIusLQ9xvm+VK6KO4aiT/dnpm0EGBNixyxSLnqF4WFPkQKytVMyEOY5 jXzuaamltNs8fHJSsNcRZ/HYr1AKagYT9NswgKHM/S3/X2FLTmaYNPWldIuzn7MhPTHAMQNj/ DX7DVjk0EOCzdg3/yG3+deBfzJEnWMQrCEsm+F+BDbV4X6eWSP7qF/jICQSQfoTlhAFtk+i19 b1QbaCpumWQ0x7BnOabeJDRs3zWcQDgVB77dg6zmQWicSN8iC5tOfkDQZTvFh2QS9g51d1DoO LgHw7Y8C2mjDL8sdv7o08W2Jx0FksUADbENFXbanvTyelJS6vhYqfCmHp75ozxHIxrwUwG4Wu CKwsxwM4eye05dJmnRZI/AFSBBw3GsihPJTc4YNz9M00h45GZDkIh+mQT+mvYHMlCCNVoUrBX VWm7A6dEiJTIJ5oE6oDlLzbsOFdFxfeQghBRUI+ndBHZ59AyAy0s863yFzZ2BazZERe4dBi/G uozsvsovnVXgXik7wX50SCP9BykWi5R1nprQyqsGjomSEKDQANRIT8SK9J6f2xeCrKA65QPWP CXWVOMtVxiMDXMp+dvi/EPqpptbfZdP0ffJDpnof41WBETtongGYRpBbmomJBPkK8ydAcxZLn laiU+i99tq21nKXzHb4kWyPYXDNRL126pcnywd2o1hae6fTzojavfJXYMOCQIjH/TSqmTzVdZ YqwHBwW
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JPzwo4envY36cpL7fEhoGDvVySo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jun 2017 11:37:33 -0000

On 2017-06-25 13:28, Willy Tarreau wrote:
> On Sun, Jun 25, 2017 at 12:50:30PM +0200, Julian Reschke wrote:
>> On 2017-06-25 12:46, Willy Tarreau wrote:
>>> Hi Julian,
>>>
>>> On Sun, Jun 25, 2017 at 12:11:29PM +0200, Julian Reschke wrote:
>>>>      An intermediary MAY drop the informational response. (...)
>>>>
>>>> That seems to contradict a MUST-level requirement in RFC 7231
>>>> (https://www.greenbytes.de/tech/webdav/rfc7231.html#rfc.section.6.2.p.3)
>>>
>>> Not completely. An intermediary not aware of 103 may map it to 100. If
>>
>> It may do so, but it's not allowed to (IMHO).
> 
> I agree with you but there's probably a difference with what is really
> deployed in field. However I'm now seeing a wording issue here, because
> saying "An intermediary MAY drop the informational response" suggests
> to intermediary implementations that this is permitted. I think that
> using just a warning for server implementations would be more appropriate,
> like "A server should be prepared to see its 103 responses silently dropped
> or altered by some non-compliant intermediaries".

Yup.

>>> the intermediary inserted an "Expect: 100 continue" header field, we
>>> can reasonably imagine that such an intermediary might also drop the
>>> returning 103. This wording in 7231 may even encourage some implementations
>>> to do so : "A proxy MUST forward 1xx responses unless the proxy itself
>>> requested the generation of the 1xx response". Speaking about 1xx here
>>> may be read as "I asked for 100, I'm receiving 1xx so that matches".
>>
>> But that sounds like a bug in the proxy to me. A 103 is not a 100.
> 
> Sure, but it's also suggested that when processing a code XYY that you
> don't know, you can consider that it will act like X00. I'm not

I wouldn't consider that a license to *change* the code though.

> justifying that some might be doing this, just that we need the spec to
> be robust against such bogus behavious *if they exist*. Especially
> interim responses, which have always been tricky to get right
> everywhere :-/
> ...

True, but we shouldn't confuse normative language (which simply can't be 
in conflict with the base spec without additional work) from implementor 
guidance.

> ... >> Understood. But is this a requirement or just a suggestion? Does a 
client
>> need to forget the information from the 103 when it's not repeated in the
>> final response?
> 
> Hmmm the text says :
>    "This memo defines a status code for sending an informational response
>     ([RFC7231], Section 6.2) that contains header fields that are likely
>     to be included in the final response"
> 
> Thus I think that the final header fields are the real ones, and that
> those sent early are more about hints to help the client get mostly
> prepared. Can there be a conflict between two overlapping header field
> values for the same link ? If so, some text needs to be appended to
> mandate that the final response the the only authoritative one and that
> the interim ones are only here to help fill silence periods on the link.

I'm interested in the case where the Link appears in the 103 but not in 
the final response...

Best regards, Julian


From nobody Sun Jun 25 04:53:22 2017
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E080B127B60; Sun, 25 Jun 2017 04:53:20 -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, 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 ajOgvB5roILN; Sun, 25 Jun 2017 04:53:19 -0700 (PDT)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id B3C8712783A; Sun, 25 Jun 2017 04:53:18 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id v5PBrF2k029104; Sun, 25 Jun 2017 13:53:15 +0200
Date: Sun, 25 Jun 2017 13:53:15 +0200
From: Willy Tarreau <w@1wt.eu>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: ietf@ietf.org, httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>, draft-ietf-httpbis-early-hints@ietf.org, ietf-http-wg@w3.org, alexey.melnikov@isode.com
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
Message-ID: <20170625115315.GA29097@1wt.eu>
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de> <20170625104629.GA29021@1wt.eu> <602955e2-cfd0-e4c8-7afa-e8f3ea78ab3a@gmx.de> <20170625112842.GA29052@1wt.eu> <8e93bbfc-b609-0392-5c78-114103accaed@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8e93bbfc-b609-0392-5c78-114103accaed@gmx.de>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/EisCZ1ggI7GBEYH719BfdNmrI28>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jun 2017 11:53:21 -0000

On Sun, Jun 25, 2017 at 01:36:59PM +0200, Julian Reschke wrote:
> > > Understood. But is this a requirement or just a suggestion? Does
> > > a client
> > > need to forget the information from the 103 when it's not repeated in the
> > > final response?
> > 
> > Hmmm the text says :
> >    "This memo defines a status code for sending an informational response
> >     ([RFC7231], Section 6.2) that contains header fields that are likely
> >     to be included in the final response"
> > 
> > Thus I think that the final header fields are the real ones, and that
> > those sent early are more about hints to help the client get mostly
> > prepared. Can there be a conflict between two overlapping header field
> > values for the same link ? If so, some text needs to be appended to
> > mandate that the final response the the only authoritative one and that
> > the interim ones are only here to help fill silence periods on the link.
> 
> I'm interested in the case where the Link appears in the 103 but not in the
> final response...

I think it will be very common, because I see a cool opportunity here for
edge gateways to send a few links regardless of what the origin server thinks
about this. I'm even considering implementing this capability into haproxy
because I think it can bring some value. So if this is going to have side
effects, it would be nice that they are properly estimated.

Willy


From nobody Sun Jun 25 05:33:23 2017
Return-Path: <email1@jevan.com.au>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CBE2127B60 for <ietf@ietfa.amsl.com>; Sun, 25 Jun 2017 05:33:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.737
X-Spam-Level: 
X-Spam-Status: No, score=-0.737 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.779, T_REMOTE_IMAGE=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 M6YbnV66wnrC for <ietf@ietfa.amsl.com>; Sun, 25 Jun 2017 05:33:20 -0700 (PDT)
Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (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 436E91200ED for <ietf@ietf.org>; Sun, 25 Jun 2017 05:33:20 -0700 (PDT)
Received: from [10.9.9.210] (helo=mailfront10.runbox.com) by mailtransmit03.runbox with esmtp (Exim 4.86_2) (envelope-from <email1@jevan.com.au>) id 1dP6j6-0003o3-Qb for ietf@ietf.org; Sun, 25 Jun 2017 14:33:16 +0200
Received: from [121.127.210.125] (helo=desktop-797rgpq) by mailfront10.runbox.com with esmtpsa (uid:796123 ) (TLS1.0:DHE_RSA_3DES_EDE_CBC_SHA1:192) (Exim 4.82) id 1dP6j2-0004lx-87 for ietf@ietf.org; Sun, 25 Jun 2017 14:33:13 +0200
To: ietf@ietf.org
From: Jevan Pipitone <email1@jevan.com.au>
Subject: Is the "as" needed in "early hints" response
Message-ID: <d6c85dec-b232-453a-5476-2079fe5a8784@jevan.com.au>
Date: Sun, 25 Jun 2017 22:33:05 +1000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------2B49AC654154499A84F58FB3"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pwYfUjDP4bnCfnuPovleCe9EfXE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jun 2017 12:33:22 -0000

This is a multi-part message in MIME format.

--------------2B49AC654154499A84F58FB3
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Is the "as" needed in "early hints" response

What about if we had:

Server response:
       HTTP/1.1 103 Preload
       Link: </style.css>
       Link: </script.js>
       Loading: </ball.jpg>

since it doesn't matter what the content to be preloaded is, that will be determined later when the html page is sent. For example the case for type="javascript" since we don't actually know what type of script it is anyway from the "early hints" you mentioned, but that doesn't matter either.

Also we could have a "loading" item to display while the page is being loaded. This could be a jpg, gif, even a small flash file.

Date: Sun, 25 Jun 2017 12:11:29 +0200
From: Julian Reschke<julian.reschke@gmx.de>
...
Server response:
       HTTP/1.1 103 Early Hints
       Link: </style.css>; rel=preload; as=style
       Link: </script.js>; rel=preload; as=script
...





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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <pre wrap="">Is the "as" needed in "early hints" response

What about if we had:

Server response:
      HTTP/1.1 103 Preload
      Link: &lt;/style.css&gt;
      Link: &lt;/script.js&gt;
      Loading: &lt;/ball.jpg&gt; 
</pre>
    <pre wrap="">since it doesn't matter what the content to be preloaded is, that will be determined later when the html page is sent. For example the case for type="javascript" since we don't actually know what type of script it is anyway from the "early hints" you mentioned, but that doesn't matter either.

Also we could have a "loading" item to display while the page is being loaded. This could be a jpg, gif, even a small flash file.

Date: Sun, 25 Jun 2017 12:11:29 +0200
From: Julian Reschke <a class="moz-txt-link-rfc2396E" href="mailto:julian.reschke@gmx.de">&lt;julian.reschke@gmx.de&gt;</a>
...
Server response:
      HTTP/1.1 103 Early Hints
      Link: &lt;/style.css&gt;; rel=preload; as=style
      Link: &lt;/script.js&gt;; rel=preload; as=script
...
</pre>
    <div class="moz-signature"><br>
      <br>
    </div>
  <img src="http://ts.msgtag.net/bflFbwtnnsgFhjzhBoet/yDc/Auckx/uswt.gif" alt=" " border="0" id="MSGTAGImage"/></body>
</html>


--------------2B49AC654154499A84F58FB3--


From nobody Sun Jun 25 15:52:28 2017
Return-Path: <ncamwing@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 925601205F0; Sun, 25 Jun 2017 15:52:26 -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 LqHhYGKiDvgM; Sun, 25 Jun 2017 15:52:24 -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 0CC391270A7; Sun, 25 Jun 2017 15:52:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1220; q=dns/txt; s=iport; t=1498431144; x=1499640744; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ZTPXdGEtQo5Tbugrx/yDhIaNhjRDGw36YAL97AfuB/k=; b=TucWaRLqrw8PdTeOLZBa/WfsMnuJMMpSsJGqoci+qJJfqQfHHZ/AWeDR XENN4Z0jNj/I8Eo8Xzhe6I0Ut/kG4XFsosklZC+VwXzS9fqvmKLTAOpKE kwstwtduLtFlxQT6Jbf1MliuBPwXlkuAqLLo9PaoCAGxa7Vpz/ckvIhai c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0C2AADvPVBZ/5pdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1higQ0Hg2WKGadZghGGJAIagm4/GAECAQEBAQEBAWsohRkGIxE?= =?us-ascii?q?zEhACAQYCDgwCHwcCAgIwFRACBAENBYosk3qdYoImi08BAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEdgQuCHIUtK4J5hGqDEzCCMQEEnmkCk2WCCYVIikGJKot2AR84gQp?= =?us-ascii?q?0FVsBhS+BTXaIJIENAQEB?=
X-IronPort-AV: E=Sophos;i="5.39,392,1493683200"; d="scan'208";a="440620179"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 Jun 2017 22:52:23 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com [64.101.220.152]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v5PMqMwO011665 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 25 Jun 2017 22:52:22 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-012.cisco.com (64.101.220.152) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 25 Jun 2017 18:52:22 -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; Sun, 25 Jun 2017 18:52:21 -0400
From: "Nancy Cam-Winget (ncamwing)" <ncamwing@cisco.com>
To: Carsten Bormann <cabo@tzi.org>, IETF <ietf@ietf.org>
CC: "draft-ietf-sacm-requirements@ietf.org" <draft-ietf-sacm-requirements@ietf.org>
Subject: Re: Last Call: <draft-ietf-sacm-requirements-15.txt> (Security Automation and Continuous Monitoring (SACM) Requirements) to Informational RFC
Thread-Topic: Last Call: <draft-ietf-sacm-requirements-15.txt> (Security Automation and Continuous Monitoring (SACM) Requirements) to Informational RFC
Thread-Index: AQHS6yKgeeUsKIXVRECt1adxstm+BqI2AtWA
Date: Sun, 25 Jun 2017 22:52:21 +0000
Message-ID: <01D1AF10-ECE0-42AC-AD3D-5E31056ACACD@cisco.com>
References: <149547765333.16443.10840963581238733682.idtracker@ietfa.amsl.com> <79A273B7-56C5-438D-BA99-976537813BC3@tzi.org>
In-Reply-To: <79A273B7-56C5-438D-BA99-976537813BC3@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1a.0.160910
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.86.253.68]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BBF2A84C55BA534BBFB5E380F8B749E9@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/VPvDf62r-fzYMHRQclGxIUVvAoQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 25 Jun 2017 22:52:27 -0000

SGkgQ2Fyc3RlbiwNCg0KRmFpciBwb2ludC4gIFdpbGwgdXBkYXRlIGluIHRoZSBuZXh0IHJldmlz
aW9uLg0KDQoJTmFuY3kNCg0KT24gNi8yMS8xNywgMTE6NDEgUE0sICJDYXJzdGVuIEJvcm1hbm4i
IDxjYWJvQHR6aS5vcmc+IHdyb3RlOg0KDQogICAgUXVvdGU6DQogICAgDQogICAgICAgTXVsdGlw
bGUgZGF0YSBtb2RlbHMsIHByb3RvY29scywgYW5kIHRyYW5zcG9ydHMgbWF5IGJlIGVtcGxveWVk
IGluIGENCiAgICAgICBTQUNNIGVudmlyb25tZW50LiAgQSBTQUNNIHRyYW5zcG9ydCBwcm90b2Nv
bCBpcyBvbmUgdGhhdCBydW5zIG9uIHRvcA0KICAgICAgIG9mIEwzIHByb3RvY29scyBzdWNoIGFz
IFRDUC9JUCBvciBMNCBwcm90b2NvbHMgc3VjaCBhcyBIVFRQLCBjYXJyaWVzDQogICAgICAgb3Bl
cmF0aW9ucyAocmVxdWVzdHMgLyByZXNwb25zZXMpLCBhbmQgbW92ZXMgZGF0YS4NCiAgICANCiAg
ICBQbGVhc2UgZXhwYW5kIGFiYnJldmlhdGlvbnMg4oCcTDPigJ0gYW5kIOKAnEw04oCdIG9uIGZp
cnN0IChhbmQgYXBwYXJlbnRseSBvbmx5KSB1c2UuDQogICAgUHJlZmVyYWJseSBkbyBub3QgdXNl
IHRoZXNlIGFiYnJldmlhdGlvbnMgaGVyZSBhdCBhbGwgYXMgdGhleSBhcmUgY3VzdG9tYXJpbHkg
dW5kZXJzdG9vZCB0byBzdGFuZCBmb3Ig4oCcSW50ZXJuZXQgTGF5ZXLigJ0gYW5kIOKAnFRyYW5z
cG9ydCBMYXllcuKAnSBhcyBkZWZpbmVkIGluIFJGQzExMjIgU2VjdGlvbiAxLjEuMyAod2hpbGUg
dXNpbmcgT1NJIGxheWVyIG51bWJlcnMgcHVyZWx5IGZvciBjb252ZW5pZW5jZSkuICBUaGlzIGNv
bW1vbiBtZWFuaW5nIGRvZXNu4oCZdCBhcHBlYXIgdG8gYmUgbWVhbnQgaGVyZS4NCiAgICANCiAg
ICBHcsO8w59lLCBDYXJzdGVuDQogICAgDQogICAgDQoNCg==


From nobody Sun Jun 25 17:07:35 2017
Return-Path: <d3e3e3@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 B5D25126CC4; Sun, 25 Jun 2017 17:07:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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 uxaoUzQECrL6; Sun, 25 Jun 2017 17:07:30 -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 90BE4124217; Sun, 25 Jun 2017 17:07:30 -0700 (PDT)
Received: by mail-it0-x229.google.com with SMTP id b205so31637831itg.1; Sun, 25 Jun 2017 17:07:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=VsF13UUI8Adxncjmvg7IEhE9NYx7hp7x9Of78C4O/wk=; b=YUDdjbDup6DWDq2H5HmDhW/A+bI7BEZ2rXQ4ACctQHKlRW2mP1VU2RCjYagQ84nJtX j0j3h/Mv/IuDj7DFzjneLeyZi1ew55NxiLM0Qm5Igsn8DS6/TSFwxOy3O1mC8/81Lz7R 3907/zwSqNrGb1JnAcZbA+On6DgPpqSFW8+pT2X4U8JLySY5rq39+ghFpJU7kh47mqI6 Pdgbi+HxrCRaIAk4Wv3uRyk1oSyqYH2GTFf4sCDFOmGriUsjU0rUiNgmC60PeDncDbFX TXYbB9Fg3KrtWL66vH+967mgUmRp4AkPVKOYZF8dXoxWsTElZ/lPSpv0guaBZbfsHp7C fdYA==
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=VsF13UUI8Adxncjmvg7IEhE9NYx7hp7x9Of78C4O/wk=; b=Ui010ZSJ5F/BF0T0w+7mEY4Ekti8TDfPWg9bMs/EKdAi8o0PyAUiQfH9HCpTn9YwCm 1A8qnanDxW48VXVbsSVl8YrXIWItJSJDiWSXZfyKkX5LJ8tJ5za/rqRAd2A7nkMXL5sj XDnNWNTYqBtB42tRLGvGuKLN+dwFoGKLq+n8aIwMatxp8OVz3QCWNNxlNSvhzRV/D9G+ KS/iMajnZ0XqUt86r2yUHceSEz2IdwvWU0WRTrmBu9zsDFBCIYT2iQDDUAcWUDwBCpTf ylKF22+xH/TYsKHuVySPLJxOYk7MKQ8mdAJce7q3C/6r2HqfNPcZQlExsDeyD2U1mYg7 4iQg==
X-Gm-Message-State: AKS2vOy6dcYcUcjZH59F/aNjUSe4YzXDzbS62Axzi8K/39/gaAaaJf3d 73n0WRs01PKhGVe1wTXBzgeLslkWzA==
X-Received: by 10.36.20.137 with SMTP id 131mr21713650itg.104.1498435649336; Sun, 25 Jun 2017 17:07:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.17.221 with HTTP; Sun, 25 Jun 2017 17:07:13 -0700 (PDT)
In-Reply-To: <149754795560.13109.17521244075940607817@ietfa.amsl.com>
References: <149754795560.13109.17521244075940607817@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Sun, 25 Jun 2017 20:07:13 -0400
Message-ID: <CAF4+nEG-28weDot9R9Z4-05PX1tzBoKZSOHu8BJY2GiRzOv0nA@mail.gmail.com>
Subject: Re: Tsvart early review of draft-ietf-trill-over-ip-10
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: tsv-art@ietf.org, "trill@ietf.org" <trill@ietf.org>, IETF Discussion <ietf@ietf.org>, draft-ietf-trill-over-ip.all@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BPXtdmwpT8czmq1y1lu7I2hSpfI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 00:07:34 -0000

Hi Magnus,

Thanks for the extensive review. See my responses below.

On Thu, Jun 15, 2017 at 1:32 PM, Magnus Westerlund
<magnus.westerlund@ericsson.com> wrote:
>
> Reviewer: Magnus Westerlund
> Review result: Not Ready
>
> Early review of draft-ietf-trill-over-ip-10
> Reviewer: Magnus Westerlund
> Review result: Not Ready
>
> TSV-ART review comments:
>
> I have set this to not ready as there are several issues, some significant that
> could affect the protocol realization significantly. Some may be me missing
> things in TRILL, I was not that familiar with it before this review and I have
> only tried looking up things, not reading the whole earlier specifications. So
> don't hesitate to push back and provide pointers to things that can resolve
> issues. The authors and the WG clearly have thought about a lot of issues and
> dealt with much already.

OK. Hopefully we can resolve these one way or the other.

> Diffserv usage
> --------------
>
> Section 4.3:
>
>    TRILL over IP implementations MUST support setting the DSCP value in
>    the outer IP Header of TRILL packets they send by mapping the TRILL
>    priority and DEI to the DSCP. They MAY support, for a TRILL Data
>    packet where the native frame payload is an IP packet, mapping the
>    DSCP in this inner IP packet to the outer IP Header with the default
>    for that mapping being to copy the DSCP without change.
>
> I think it is fine to require that implementations are capable  of setting
> DSCP values on the outer IP header. However, I fail to see any discussion of
> the potential issues with actually setting the DSCP values. It is one thing to
> do this in an IP back bone use case where one can know and have control over
> the PHB that the DSCP values maps to. But otherwise, over general internet the
> behavior is not that predictable. One can easily be subject to policers or
> remapping. Also as the actual DSCP code point usage is domain specific this is
> difficult. Priority reversal is likely the least of the problems that this can
> run into over general Internet.

It sounds like appropriate discussion and warnings about these issues
would resolve the above comment.

> Section 4.3:
>
>    The default TRILL priority and DEI to DSCP mapping, which may be
>    configured per TRILL over IP port, is an follows. Note that the DEI
>    value does not affect the default mapping and, to provide a
>    potentially lower priority service than the default priority 0,
>    priority 1 is considered lower priority than 0. So the priority
>    sequence from lower to higher priority is 1, 0, 2, 3, 4, 5, 6, 7.
>
>       TRILL Priority  DEI  DSCP Field (Binary/decimal)
>       --------------  ---  -----------------------------
>                   0   0/1  001000 / 8
>                   1   0/1  000000 / 0
>                   2   0/1  010000 / 16
>                   3   0/1  011000 / 24
>                   4   0/1  100000 / 32
>                   5   0/1  101000 / 40
>                   6   0/1  110000 / 48
>                   7   0/1  111000 / 56
>
> This appear to be an problematic mapping. At least for prio 0 and 1. As
> priority 1 appears to be intended to be higher than priority 0, it is
> interesting that it is mapped to CS1, which to quote
> https://datatracker.ietf.org/doc/rfc7657/:
>
> CS1 ('001000') was subsequently designated as the recommended
>       codepoint for the Lower Effort (LE) PHB [RFC3662].
>
> So what is proposed can in a network using default mapping, result in that you
> get priority 0 to be lower priority than 1. Plus that in some networks this can
> also results in strange remapping that results in a different PHB for CS1 than.

The intent in the draft is to reflect the default relative priority of
the different priority code points in IEEE Std 802.1Q where priority 1
is lower than priority 0. At a quick look, it appears to me that RFC
2474 requires that 0x001000 be handled as being of a priority not
lower than the priority with which 0x000000 is handled. Yet RFC 3662,
which you point to, seems to suggest using 0x001000 as a lower
priority code point than 0x000000. Given that 3662 not only does not
update 2474 but is only Informational while 2474 is Standards Track, I
would say that 2474 dominates and that this draft makes the best
assumptions it can about default behavior...

> MTU and Fragmentation
> ---------------------
>
> I think there are two main issue here. The first one is MTUD discovery
> of the actual IP path MTU between the ports. That will be needed to prevent
> a lot of traffic going into MTU black holes. Especially as TRILL requries
> 1470 byte support which is likey above a lot of paths.

Seems like it would depend on the environments where TRILL was used.
For example, I do not think 1470 would be a problem in most Data
Center or Internet Exchange point uses, for example. Data Centers
sometimes support 9K jumbo frames and the like.

In fact, it is probably bad to focus too much on 1470 -- that is a
required minimum to be sure that reasonable size link state PDUs can
be successfully flooded through the TRILL campus so that routing will
work. However, it would commonly be the case that, for the TRILL
campus to be useful in a particular case, links need to be able to
carry the expected size TRILL Data packets. For example, if there were
two parts of a TRILL campus connected by one or a few TRILL over IP
links and the end stations in each part were assuming they could use
1500 byte Ethernet packets, then the TRILL over IP links would need to
support an MTU based on 1500 + TRILL Header + IP and TRILL over IP
encapsulation. And more if security was being used or there were any
other reasons for additional headers/encapsulation...

> Section 8.4:
>
>    Path MTU discovery [RFC4821] should be useful
>    in determining the IP MTU between a pair of RBridge ports with IP
>    connectivity.
>
> The issue with RFC4821 is that it has requirements on the packetization layer.
> Trill appears to have several components that are useful. However, it will
> require a specification of the procedure to result in a useful tool.

See below.

> Section 8.4:
>
>    TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
>    [RFC7177], can be used to obtain added assurance of the MTU of a
>    link.
>
> Yes, that can confirm working MTUs that are at 1470 or above, but appears
> prevented from working below 1470?

While there is a minimum size for TRILL IS-IS MTU PDUs, determined by
header size, it is well below 1470, probably (depending on whether
secuirty is in use, etc.) below 150 bytes.

> Thus, it appears that there is a lack of mechanism here to actually get a valid
> and functional MTU from TRILL in the cases where the Path MTU is below 1470. If
> I am wrong good, but I think this is an important piece for how to handle the
> next main issue.

How about referencing Section 3 of
https://tools.ietf.org/html/draft-ietf-trill-mtu-negotiation-05
which is currently in IETF Last Call? (The wording of that section is
probably going to be improved based on an OPS review by Brian
Carpenter.)

> UDP encapsulation and IP fragments.
  ----------------------------------
> I see it as a big issue that UDP encapsulation is the native one, and that
> relies on IP fragmentation despite the need for reliable fragmentation. With
> the setup of having to support 1470 MTU on TRILL level some packets will be
> fragmented in many environments. That will lead to a lot of losses, and as
> discussed below a very big problem with middleboxes. The main problem here is
> that if one tries to rely on IP fragments one will have issues with packets
> ending up in black holes. And different problems depending on IPv4 or IPv6.
> IPv6 is lilkely the lesser problem assuming that one have working PMTUD.
>
> There are several ways out of this.
>
> 1. Detect issues and use TCP encapsulation with correctly set MSS to not get IP
> fragements 2. Determine MTU and implement an fragmentation mechanism on top of
> UDP.

So, I don't see that much problem with UDP being the general default
consistent with the TRILL philosophy of defaulting to need zero or
minimal configuration. The default should be to use multicast Hellos
for discovery of neighbors which sure points at UDP to me. Having to
traverse a NAT should be a rare case. Since, in the NAT case, you have
to configure things related to the static binding and the IP
address(es) of peer(s) anyway you can also configure to use a
different encapsulation than UDP, such as TCP, at the same time. I
don't see it as much of a problem if, by default, TRILL won't operate
through a NAT. If you are using UDP and it fragments and fragments are
dropped at a NAT, probably you can't exchange Hellos so you will not
form an adjacency and anything on the other side of the NAT will not
be visible.

> Zero Checksum:
> --------------
>
> Section 5.4:
>
> UDP Checksum - as specified in [RFC0768]
>
> Considering the fast path encapsulation desire, I am surprised to not see any
> mentioning of use of zero checksum here. Raising the zero checksum and forward
> reference would be good I think.
>
> And then Section 8.5:
>
>    The requirements for the usage of the zero UDP Checksum in a UDP
>    tunnel protocol are detailed in [RFC6936]. These requirements apply
>    to the UDP based TRILL over IP encapsulations specified herein
>    (native and VXLAN), which are applications of UDP tunnel.
>
> If you actually intended to allow zero checksum, then you actually should
> document that Trill fulfills the requirements that the applicability statement
> raises. I have not analyzed how well it meets these requirements.
>
> Please review Section 6.2 of RFC 8086 for example how that can be done.

OK. We'll look into it.

> TCP Encapsulation issue
> -----------------------
>
> Section 5.6:
>
> The TCP encapsulation appear to be missing an delimiter format allowing each
> individual TRILL packet/payload to be read out of the TCP's byte stream. In
> other words, a normal implementation has no way of ensuring that the TCP
> payload starts with the start of a new TRILL payload. Multiple small TRILL
> payloads may be included in the same TCP payload, and also only parts as TCP is
> one way of dealing with TRILL packets that are larger than the IP+Encapsulation
> MTU that actually will work.
>
> This comment is based on that there appear to be no length fields included in
> the TRILL header. The most straight forward delimiter is a 2-byte length field
> for the TRILL payload to be encapsulated.

Right. It might also be useful to include some sort of check field, as
is done in BGP, to detect if you are out of sync in parsing the TCP
stream.

Another point is that, while with UDP it seems fine to send packets
with assorted QoS, you don't want to encourage re-ordering of TCP
packets in a stream. So if TCP encapsulation is being used, you want
to use the same DSCP value for the packets in a particular TCP stream.
So, generally, you need to have a TCP connection per priority handling
category. Mapping the 8 priority levels into a smaller number of
handling categories is a normal thing to do so you certainly don't
necessarily need 8 TCP connections. Adding material on this should not
be too hard.

> Section 5.6:
>
> TCP endpoint requirements. I do wonder if an application like TRILL actual
> would need to discuss performance impacting implementation choices or
> limitations. For example use of NAGLE, the requirements on buffer sizes in
> relation to Bandwidth delay products, as buffer memory in a RBridge will impact
> performance.

Well, I'm not sure how deeply this document should get into such
performance issues. What about just saying something about
consideration being given to tuning TCP for performance and pointing
to one or a few other RFCs that talk about this?

> Congestion Control
> ------------------
> First thanks for the effort here.

You're welcome.

> 8.1.2 In Other Environments
>
>    Where UDP based encapsulation headers are used in TRILL over IP in
>    environments other than those discussed in Section 8.1.1, specific
>    congestion control mechanisms are commonly needed.  However, if the
>    traffic being carried by the TRILL over IP link is already congestion
>    controlled and the size and volatility of the TRILL IS-IS link state
>    database is limited, then specific congestion control may not be
>    needed. See [RFC8085] Section 3.1.11 for further guidance.
>
> This is correct, however my question is if the RBridges have any way of knowing
> which traffic is actually congestion controlled, considering that TRILL provides
> an layer 2 abstraction. I wonder if there should be any type of white list of
> the types of layer 2 payloads that can be assumed to be congestion controlled,
> and thus okay to forward over IP paths? I am worried that without any
> recommendation to prevent traffic that is not controlled to be forwarded, can
> lead to congestion issues.
>
> The other issue I think may exist is the issue serial unicast emulation of
> broadcast/multicast creates. As this amplifies the outgoing packet rate with
> a factor of how many addresses are configured for serial unicast this can
> be significant traffic expansion. Thus, I think additional considerations are
> needed here, and maybe rate limiting of the amount of traffic to be multicasted.

OK. We can think about those issues.

> Flow and ECMP
> -------------
>
> Section 8.3:
>
> For example, for TRILL
>    Data, this entropy field could be based on some hash of the
>    Inner.MacDA, Inner.MacSA, and Inner.VLAN or Inner.FGL.
>
> I would appreciate clearer references to what these fields are.

In a TRILL Data packet, the payload after the TRILL Header looks like
an Ethernet frame except that there is always either a VLAN tag or,
alternatively, where the VLAN tag would be, a Fine Grained Label
[RFC7172]. (The preceding is the view in the TRILL RFCs, but there is
an equivalent and equally valid view in which all the fields through
and including the VLAN or FGL tag are part of the TRILL Header.) The
TRILL base protocol specification focuses on Ethernet as a link
technology between TRILL switches, in which case there will be a link
header including an Outer.MacDA and Outer.MacSA fields and possibly an
Outer.VLAN, all before the TRILL Header. See Figure 1 and Figure 2 in
RFC 7172.

Some of the above could be added to the draft for clarity.

> If I understand this correctly, the idea here is to look into the inner
> layer 2 frames, and use the flow equivalents that exists on that level and
> hash that into value that maps the flows onto the source port range.

Yes.

> I think this text should include a summary of the principle and ensure to
> note the important requirement that what is considered flows in the inner
> must not result in being striped over multiple source ports as this may lead to
> reordering issues due to packets taking different paths.

Well, we can add some text. But when would the relative ordering
matter for two TRILL Data packets where the two inner native payloads
have different values for any one or more of these three fields
(Inner.MacDA, Inner.MacSA, and inner VLAN/FGL tag) ? If any of those
fields are different, you are talking about different streams.

> NAT and TRILL over IP:
> Section 8.5:
>
> If one like to use TRILL over IP through a NAT, then there are some very
> important considerations that are missing. First the need for static binding
> configurations or the need for determining ones external address(es) and be
> able to communicate that to the peer RBridges, and in addition ensure that one
> has keep-alives to that the NAT binding never times out.

I think those are good points. There is an additional problem that
TRILL Hellos detect neighbors with which they have 2-way connectivity
by indicating, inside the Hellos that are sent, from what neighbors
Hellos have been received on that port. If a NAT is involved, these
neighbor addresses inside Hellos need to be mapped.

> Next is the issue that there is almost zero chance of getting a IP/UDP
> encapsulation TRILL payload through the NAT if it results in IP fragmentation,
> as NATs don't do defragment and refragmented on the internal side, and an IP
> fragment lacks UDP port and thus can't be matched to binding.

So perhaps the recommendation should be to configure the port to use
TCP if there will be fragmentation.

> Also if you like to run IP/ESP through a NAT, then you most likely need the
> IP/UDP/ESP encapsulation (https://tools.ietf.org/html/rfc3948). Note that this
> will restrict the MTU even further and thus ensure that the 1470 requirement
> cannot be fulfilled even without additional tunnels over an 1500 bytes MTU
> Ethernet infrastructure.
>
> I would note that also firewalls likely have issues with IP fragments for the
> same reason, they require significant amount of state to be verified if they
> should be let through.
>
> In general I think you should create a configuration that has chance to work
> through most middleboxes, but I think you should require static bindings. I
> think that configuration is, and don't laugh now, but IP/UDP/ESP/TCP/TRILL,
> otherwise you will not be able to have both security and reliable fragmentation
> of TRILL packets.

OK. Thanks again for this review. It has pointed out a number of
problems and in thinking about those, I believe a couple of further
problems have come to mind that I mentioned above. We'll work on a
revised draft.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Cheers
>
> Magnus Westerlund


From nobody Sun Jun 25 19:39:28 2017
Return-Path: <kazuhooku@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 7E7BA12869B; Sun, 25 Jun 2017 19:39: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 BmG_KWAWUB90; Sun, 25 Jun 2017 19:39:24 -0700 (PDT)
Received: from mail-pg0-x22a.google.com (mail-pg0-x22a.google.com [IPv6:2607:f8b0:400e:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B2971243F3; Sun, 25 Jun 2017 19:39:24 -0700 (PDT)
Received: by mail-pg0-x22a.google.com with SMTP id f127so42056664pgc.0; Sun, 25 Jun 2017 19:39:24 -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=Pm+/10K7W/yx9xxtrtOgJ+ammek4Ecvf8z5IEUto5dw=; b=vd9bjx9WGIzMtY2d2CAVPMMmQn6baC1S776MMx9F24kPMf0JQo0dDKtfb/IGefz9eL 012luNbUrcHSWztt/nLYGxqhc88wBEiTZr7Y09+PfCWgDPUxDvdYi6R6aaSorolwovCr xFSClPWsNdFIpVpWomNgxPTVJiBmRzh+uD4A5t8nb18skti5M4vfWpGNNhiQQJ4v1sh/ T3eEH9QVAzCw9lz3sTEbjRAc3itCUtnGr0HkK7rV9SCV9ovyGiYW2KQ8t0VW0kT1G+Mh UjNcX3a5XbL/mChqmsPaySiLJ8QB56ZU9gU2Uk4C28oPiDcs6XfAwCmd11zvAKE1GjyD GZEw==
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=Pm+/10K7W/yx9xxtrtOgJ+ammek4Ecvf8z5IEUto5dw=; b=QL5gDUVLeO3Hc7lav1knS3pF7uFl4T9NVgVFqFGSuiS3WYfxJjIDGhYED6IGdt8iuw jOuUmSzlBsMi63yBDVEtEj3ZirtGs3a5Rnq6yahqylvO6mrOs27EVDD7h/XXtQn0T/xe RNdXDoPnsm7exf70lNQc1oqyIqE9LAndjvGsWiBdjKFrNp4uQ+K+Y6jLZ9cbR9/5H80a lYhT0OdSoQcED4QVH74Q60v5tY9J2+275EYkPtJ4epxiTRw2CT36TRsg7eXb//L8kQVv DFnon1Ztr5OJfCxV4B0SJgf68Qa4NDl/kBszGBNi6gwTxjLsRYZ9tnsflgHyW1S5ay4j yJ1A==
X-Gm-Message-State: AKS2vOxhrWOdkDgR1G+IAbbaVAWSaBEV5T/ffxZpTiiQlYJK753h49HF aX4HnogfLErP+eElTfnLLOW4Z5VAdw==
X-Received: by 10.84.198.129 with SMTP id p1mr16997120pld.120.1498444763788; Sun, 25 Jun 2017 19:39:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.130.3 with HTTP; Sun, 25 Jun 2017 19:39:23 -0700 (PDT)
In-Reply-To: <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de>
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Mon, 26 Jun 2017 11:39:23 +0900
Message-ID: <CANatvzygaU9oiof3-5TqnWdxqXOGNyGqPvNhTnpPzYy391CzNw@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
To: Julian Reschke <julian.reschke@gmx.de>
Cc: ietf@ietf.org, httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>,  draft-ietf-httpbis-early-hints@ietf.org,  HTTP Working Group <ietf-http-wg@w3.org>, alexey.melnikov@isode.com
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WaGNJYH2NiP4_62gUxUX0NRpN4k>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 02:39:27 -0000

Hi Julian,

Thank you very much for your comments.

I will create a PR fixing the editorial issues. For the other issues,
my responses in-line.

2017-06-25 19:11 GMT+09:00 Julian Reschke <julian.reschke@gmx.de>:
> On 2017-06-21 18:59, The IESG wrote:
>>
>>
>> The IESG has received a request from the Hypertext Transfer Protocol WG
>> (httpbis) to consider the following document: - 'An HTTP Status Code for
>> Indicating Hints'
>>    <draft-ietf-httpbis-early-hints-03.txt> as Experimental RFC
>> ...
>
>
>
> Here's my feedback...:
>
> 2.  103 Early Hints
>
>    ...
>
>    A server MUST NOT include Content-Length, Transfer-Encoding, or any
>    hop-by-hop header fields ([RFC7230], Section 6.1) in a 103 (Early
>    Hints) response.
>
> That's a bit weird here, because the requirements for C-L and T-E are
> generic to 1xx, and already are stated in RFC 7230. The text above makes it
> sound as if these are specific to 103, which they are not.
>
> For hop-by-hop, I'm not convinced that the requirement is needed here.

I agree that we do not need to talk about C-L and T-E here.

The reasons I added a clause prohibiting the use of hop-by-hop headers
in an 103 response are as follows:
* does not make sense for a response that attempts to send the
metadata of a final response early
* to avoid confusion caused by sending a hop-by-hop header in the 103 response

Without the restriction, a response like below would be valid, which
IMO is confusing at least.

```
HTTP/1.1 103 Early Hints
Connection: close
Link: </style.css>; rel=preload

HTTP/1.1 200 OK
Connection: close
Link: </style.css>; rel=preload
...
```

>    ...
>
>    An intermediary MAY drop the informational response. (...)
>
> That seems to contradict a MUST-level requirement in RFC 7231
> (https://www.greenbytes.de/tech/webdav/rfc7231.html#rfc.section.6.2.p.3)

The statement exists since sending 103 only makes sense when it is
impossible to immediately send a final response.

For example, there is no need for a cache that is in possession of a
freshly-cached final response to send a 103 that was sent from the
origin before sending the final response. I also believe that most
caching proxies that exist today do not cache informational responses,
and that there is no need for us to require them to do so.

Considering the facts, one way to resolve the issue would be to adjust
the statement to something like "An intermediary MAY omit the 103
response when resending a cached response", and argue that re-sending
a cached response is not an action of "forwarding," which is defined
as a MUST in RFC 7231.

But wouldn't it be simpler to just have the "MAY drop" clause for any
intermediary?

>    The following example illustrates a typical message exchange that
>    involves a 103 (Early Hints) response.
>
>    Client request:
>
>      GET / HTTP/1.1
>      Host: example.com
>
> (maybe insert blank line do delimit the message)
>
>    Server response:
>
>      HTTP/1.1 103 Early Hints
>      Link: </style.css>; rel=preload; as=style
>      Link: </script.js>; rel=preload; as=script
>
>      HTTP/1.1 200 OK
>      Date: Fri, 26 May 2017 10:02:11 GMT
>      Content-Length: 1234
>      Content-Type: text/html; charset=utf-8
>      Link: </style.css>; rel=preload; as=style
>      Link: </script.js>; rel=preload; as=script
>
>      <!doctype html>
>      [... rest of the response body is ommitted from the example ...]
>
> The example suggests that early hints are repeated in the final response. Do
> they have to, actually?

Yes. They need to, especially if caching is involved. 103 is an
intermediary response and there is no guarantee (or a requirement) for
a cache to retain the headers included only in the informational
response.

In case of link rel=preload headers, a client can speculatively load
the resources included in the headers while revalidating a
stale-cached response, or a caching proxy can generate a 103 response
from a stale-cached 200 response, while waiting for the origin to
perform revalidation.

>
> 3.  Security Considerations
>
>    Some clients might have issues handling 103 (Early Hints), since
>    informational responses are rarely used in reply to requests not
>    including an Expect header ([RFC7231], Section 5.1.1).
>
> s/header/header field/
>
>    In particular, an HTTP/1.1 client that mishandles an informational
>    response as a final response is likely to consider all responses to
>    the succeeding requests sent over the same connection to be part of
>    the final response.  Such behavior may constitute a cross-origin
>
> s/may/might/ or /can/ (or invoke https://tools.ietf.org/html/rfc8174)
>
>    information disclosure vulnerability in case the client multiplexes
>    requests to different origins onto a single persistent connection.
>
>    ...
>
> 5.  Acknowledgements
>
> Nit: This should be an appendix (the last one).
>
> 6.  Changes
>
> Nit: This should be an appendix.
>
>
> Best regards, Julian



-- 
Kazuho Oku


From nobody Mon Jun 26 01:03:59 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 6EBC8126579; Mon, 26 Jun 2017 01:03:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-weis-gdoi-rekey-ack.all@ietf.org, ietf@ietf.org
Subject: Genart last call review of draft-weis-gdoi-rekey-ack-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149846423732.31797.4914828028458689510@ietfa.amsl.com>
Date: Mon, 26 Jun 2017 01:03:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/aSP4acz3WEqPIk2ZOtStRMQwQ48>
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, 26 Jun 2017 08:03:57 -0000

Reviewer: Roni Even
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-weis-gdoi-rekey-ack-??
Reviewer: Roni Even
Review Date: 2017-06-26
IETF LC End Date: 2017-07-17
IESG Telechat date: Not scheduled for a telechat

Summary:
The document is almost ready for publication as standard track document
Major issues:

Minor issues:

1. In section 2 it says "A GM  receiving the KEK_ACK_REQUESTED attribute can
choose to ignore it, thus appearing as if it does not support the
KEK_ACK_REQUESTED  attribute.". Any reason for the GM to ignore the message? 2.
In section 4 and section 6 it says the the GM SHOULD send an acknowledgement
message. Is there a case when the GM should not send and if not why is this a
SHOULD and not a MUST? 3.  In section 6 "A non-receipt of an Acknowledgement is
an indication that a GM is  either unable or unwilling  to respond".  What
about if the Acknowledgement message was lost? Any reliability procedure?

Nits/editorial comments:

1. In section 6 "Also a GM may be  willing or able to respond with an
GROUPKEY-PUSH ACK " . I cannot parse this sentence in the context of the section



From nobody Mon Jun 26 01:52:35 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 9DA1A129687 for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 01:52:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.127
X-Spam-Level: 
X-Spam-Status: No, score=-6.127 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] 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 15KldWkgmikr for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 01:52:32 -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 6D048126B6E for <ietf@ietf.org>; Mon, 26 Jun 2017 01:52:31 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.39,394,1493679600";  d="scan'208";a="7808487"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta2.baesystems.com with ESMTP; 26 Jun 2017 09:52:28 +0100
X-IronPort-AV: E=Sophos;i="5.39,394,1493679600";  d="scan'208";a="7419004"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasmds016.greenlnk.net with ESMTP; 26 Jun 2017 09:52:28 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.201]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.03.0248.002; Mon, 26 Jun 2017 09:52:28 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Joe Touch <touch@isi.edu>, =?utf-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: I-D Action: draft-thomson-postel-was-wrong-01.txt
Thread-Topic: I-D Action: draft-thomson-postel-was-wrong-01.txt
Thread-Index: AQHS4/ajWP45auakP0OI/9KB5mNdK6IicSuAgABYwYCAADhpgIAARqaAgAEnvQCAAHJvAIAELU4AgAHS6QCAAlWNgIAEGvuAgADk5LCAAHzDAIAENLFg
Date: Mon, 26 Jun 2017 08:52:27 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636DCC9@GLKXM0003v.GREENLNK.net>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu> <8e8d4db9-93fd-5092-68de-6d8de44151c3@nic.cz> <c9202a09-af8b-faf6-b583-694378022dae@isi.edu> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636B715@GLKXM0003v.GREENLNK.net> <d0c4ecc7-1fe9-fc0b-bbe5-8cffb956b6ed@isi.edu>
In-Reply-To: <d0c4ecc7-1fe9-fc0b-bbe5-8cffb956b6ed@isi.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/WQjhUw3DCh63NVQf_V7B28YynQI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 08:52:34 -0000

RXhwbGljaXRseSByZWplY3QgdnMgc2lsZW50bHkgaWdub3JlLiBJIHRvb2sgdGhlIGxhdHRlciB0
byBiZSBhIGFuIGluc3RhbmNlIG9mIHRoZSBsYXR0ZXIsIGJlY2F1c2UgSSBtZWFudCBleHBsaWNp
dCBpbiB0ZXJtcyBvZiB0aGUgc3BlY2lmaWNhdGlvbiwgbm90IHRoZSBpbXBsZW1lbnRhdGlvbi4g
V29yZGluZyBjb3VsZCBvYnZpb3VzbHkgaGF2ZSBiZWVuIGJldHRlci4gSSBjb3VsZCBzZWUgcmVq
ZWN0aW9uIGJlaW5nIG5vaXN5LCBzaWxlbnQgb3Igc29tZXdoZXJlIGluIGJldHdlZW4uDQoNCi0t
IA0KQ2hyaXN0b3BoZXIgRGVhcmxvdmUNClNlbmlvciBQcmluY2lwYWwgRW5naW5lZXINCkJBRSBT
eXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExhYm9yYXRvcmllcw0KX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCg0KVDogwqArNDQgMzMwMCA0Njc1MDAgwqB8IMKgRTogY2hyaXMuZGVhcmxvdmVAYmFlc3lz
dGVtcy5jb20NCg0KQkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UsIENoZWxtc2ZvcmQg
VGVjaG5vbG9neSBQYXJrLCBHcmVhdCBCYWRkb3csIENoZWxtc2ZvcmQsIEVzc2V4IENNMiA4SE4u
DQp3d3cuYmFlc3lzdGVtcy5jb20vYWkNCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNl
IExpbWl0ZWQNClJlZ2lzdGVyZWQgaW4gRW5nbGFuZCAmIFdhbGVzIE5vOiAwMTMzNzQ1MQ0KUmVn
aXN0ZXJlZCBPZmZpY2U6IFN1cnJleSBSZXNlYXJjaCBQYXJrLCBHdWlsZGZvcmQsIFN1cnJleSwg
R1UyIDdZUA0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSm9lIFRvdWNoIFtt
YWlsdG86dG91Y2hAaXNpLmVkdV0gDQpTZW50OiAyMyBKdW5lIDIwMTcgMTg6MzYNClRvOiBEZWFy
bG92ZSwgQ2hyaXN0b3BoZXIgKFVLKTsgUGV0ciDFoHBhxI1lazsgaWV0ZkBpZXRmLm9yZw0KU3Vi
amVjdDogUmU6IEktRCBBY3Rpb246IGRyYWZ0LXRob21zb24tcG9zdGVsLXdhcy13cm9uZy0wMS50
eHQNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLSEgV0FSTklORyAhIC0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0gVGhpcyBtZXNzYWdlIG9yaWdpbmF0ZXMgZnJvbSBvdXRzaWRlIG91ciBvcmdhbmlzYXRp
b24sIGVpdGhlciBmcm9tIGFuIGV4dGVybmFsIHBhcnRuZXIgb3IgZnJvbSB0aGUgaW50ZXJuZXQu
DQpDb25zaWRlciBjYXJlZnVsbHkgd2hldGhlciB5b3Ugc2hvdWxkIGNsaWNrIG9uIGFueSBsaW5r
cywgb3BlbiBhbnkgYXR0YWNobWVudHMgb3IgcmVwbHkuDQpGb2xsb3cgdGhlICdSZXBvcnQgU3Vz
cGljaW91cyBFbWFpbHMnIGxpbmsgb24gSVQgbWF0dGVycyBmb3IgaW5zdHJ1Y3Rpb25zIG9uIHJl
cG9ydGluZyBzdXNwaWNpb3VzIGVtYWlsIG1lc3NhZ2VzLg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCg0KDQpPbiA2LzIzLzIwMTcgMjoy
NSBBTSwgRGVhcmxvdmUsIENocmlzdG9waGVyIChVSykgd3JvdGU6DQo+IEpvZSBUb3VjaCB3cm90
ZToNCj4+IExpYmVyYWwgbWVhbnMgdGhhdCBpZiBpdCdzIHBvc3NpYmx5IHZhbGlkLCB5b3Ugc2hv
dWxkIGFjY2VwdCBpdCBhcyBzdWNoLg0KPiBUaGF0IG5lY2Vzc2l0YXRlcyB0aGUgcHJvdG9jb2wg
ZGVzaWduZXIgZXhwbGljaXRseSBmbGFnZ2luZyBzb21lIHRoaW5ncyBhcyBpbnZhbGlkLiANClRo
YXQncyBxdWl0ZSB0eXBpY2FsLiBNYW55IHByb3RvY29scyBjbGVhcmx5IGluZGljYXRlIGV4cGxp
Y2l0IGludmFsaWQNCmNhc2VzLg0KDQo+IE9idmlvdXMgZXhhbXBsZSBpcyBhIHNob3VsZCBiZSBz
aWduZWQgbWVzc2FnZSBsYWNraW5nIGEgc2lnbmF0dXJlLiBJZiB0YWtpbmcgdGhlIG1vc3QgbGli
ZXJhbCB2aWV3IChhcyBhYm92ZSkgdGhlIHByb3RvY29sIG5lZWRzIHRvIHNheSBzb21ldGhpbmcg
bGlrZSAiaWYgdGhlIHNpZ25hdHVyZSBpcyBtaXNzaW5nIG9yIGludmFsaWQsIHRoZW4gdGhlIG1l
c3NhZ2UgbXVzdCBiZSByZWplY3RlZCIuIEkgZG9uJ3QgdGhpbmsgdGhhdCdzIGFueXRoaW5nIG5l
dywgSSd2ZSBzZWVuIGl0IGRvbmUuDQo+DQo+IEkgY2FuIHNlZSBhdCBsZWFzdCB0aGUgZm9sbG93
aW5nIGNhc2VzIHdoZXJlIG1ha2luZyBpbnRlbnQgY2xlYXIgaXMsIGluIG15IG9waW5pb24gYXQg
bGVhc3QsIGEgZ29vZCBpZGVhOg0KPiAtIFNlY3VyaXR5IGFuZCBvdGhlciBzZW5zaXRpdmUgY2Fz
ZXMgb2YgZmFpbHVyZS4gTmVlZCB0byBzYXkgZXhwbGljaXRseSByZWplY3QuDQpXaGVuIG5vdCBz
cGVjaWZpZWQsICJzaWxlbnRseSBpZ25vcmUiIGlzIGFub3RoZXIgb3B0aW9uLg0KDQo+IC0gTWVj
aGFuaXNtcyBkZXNpZ25lZCBmb3IgZXh0ZW5zaW9ucy4gV2hpbGUgdGhlIFBvc3RlbCBwcmluY2lw
bGUgbWFrZXMgaXQgdW5uZWNlc3NhcnkgdG8gc2F5IHNvLCBpdCByZWFsbHkgZG9lc24ndCBodXJ0
IHNheWluZyB0aGF0IGEgbWVzc2FnZSBzaG91bGRuJ3QgYmUgcmVqZWN0ZWQganVzdCBmb3IgdGhp
cyByZWFzb24uDQpBZ3JlZWQuDQo+IC0gV2hlcmUgd2hhdCB5b3UgcmVjZWl2ZSBpcyBhIGNvbnRh
aW5lciBvZiBtdWx0aXBsZSB0aGluZ3MgKG1lc3NhZ2VzIGluIGEgcGFja2V0LCBUTFZzIGluIGEg
bWVzc2FnZSkuIE1ha2luZyB0aGUgYXNzdW1lZCBkZXBlbmRlbmNlL2luZGVwZW5kZW5jZSBjbGVh
ciBkb2Vzbid0IGh1cnQgKGlmIHJlamVjdGluZy9pZ25vcmluZyBvbmUsIGRvZXMgdGhpcyBpbXBh
Y3Qgb24gdGhlIG90aGVycz8pLg0KPg0KPiBUaGF0J3Mgbm90IHNvbWV0aGluZyB0aGF0IHNwaXJh
bHMgb3V0IG9mIGNvbnRyb2wgaW4gc2l6ZSwgYSBjb3VwbGUgb2Ygc2VudGVuY2VzIHdvdWxkIGNv
dmVyIG1vc3QgY2FzZXMuDQpSaWdodCAtIHRoZSBQb3N0ZWwgUHJpbmNpcGxlIGlzbid0IGEgbGlj
ZW5zZSB0byBiZSBsYXp5IGluIGVpdGhlciBhDQpwcm90b2NvbCBzcGVjIG9yIGltcGxlbWVudGF0
aW9uLg0KDQpKb2UNCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqClRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBh
cmUgY29uZmlkZW50aWFsIHRvIHRoZSBpbnRlbmRlZApyZWNpcGllbnQgYW5kIG1heSBhbHNvIGJl
IHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZApyZWNpcGllbnQgcGxlYXNl
IGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtIGFuZCBub3RpZnkgdGhlIHNlbmRlci4KWW91IHNo
b3VsZCBub3QgY29weSBpdCBvciB1c2UgaXQgZm9yIGFueSBwdXJwb3NlIG5vciBkaXNjbG9zZSBv
cgpkaXN0cmlidXRlIGl0cyBjb250ZW50cyB0byBhbnkgb3RoZXIgcGVyc29uLgoqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
Kgo=


From nobody Mon Jun 26 03:30:17 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 B82B8129AD3; Mon, 26 Jun 2017 03:30:16 -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: ietf@ietf.org, draft-bormann-hybi-ws-wk.all@ietf.org, dromasca@gmail.com
Subject: Opsdir last call review of draft-bormann-hybi-ws-wk-00
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149847301667.31772.155440589471543524@ietfa.amsl.com>
Date: Mon, 26 Jun 2017 03:30:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/POC1Y7Slj10oPibq_1Q1lwUYzxk>
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, 26 Jun 2017 10:30:17 -0000

Reviewer: Dan Romascanu
Review result: Ready

This is a short and clear document that formally updates RFC6455 to extend the
use of the RFC5785 well-known URIs to the URI schemes "ws" and "wss" of the
WebSocket protocol.

>From an operational and manageability point of view this document is Ready. I
do not see any such issues in the extension that the document defines, and an
RFC 5706 review does not apply.

Nit:

in Section 1 s/necessicated/necessitated/



From nobody Mon Jun 26 03:36:50 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 60948129ADE; Mon, 26 Jun 2017 03:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0ZBS9j_2gZe; Mon, 26 Jun 2017 03:36:47 -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 C697E129AD4; Mon, 26 Jun 2017 03:36:46 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.84.68]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MQih7-1dK7nn3T4P-00U4B3; Mon, 26 Jun 2017 12:36:39 +0200
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: ietf@ietf.org, httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>, draft-ietf-httpbis-early-hints@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>, alexey.melnikov@isode.com
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de> <CANatvzygaU9oiof3-5TqnWdxqXOGNyGqPvNhTnpPzYy391CzNw@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <632d93e7-eab5-dcbe-e971-64e3b27ddb4e@gmx.de>
Date: Mon, 26 Jun 2017 12:36:36 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CANatvzygaU9oiof3-5TqnWdxqXOGNyGqPvNhTnpPzYy391CzNw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:db1oQNtjqfgM+JXce198hnScnbE1ALTGbu1HRqP2LxFTRXrKGhf o6KNoSfwsmnt03HuFazMuT+Bb3X8LYMMBFssgHJzxrpk9MU4hKw3wbfwJo6A7FBPdPxAPGI Y4j4ffGwa92X2jVrd+hoLNhwfN7ePvxpjnWTrZk7FF6luFzwRMVAp1SSSR51oeIXe5awcgV zOGc2T16G5MMHfdBE6kow==
X-UI-Out-Filterresults: notjunk:1;V01:K0:vOBeS4zkrNc=:WNj9iVF3AfPySn6Jwdwan5 lR+sdr4H+EkctJtntZESV9oZaZLSnQslWfBU7DMywOhZ65gbSCRZfIi56ITsNxVpO33VM0lgr SAlHQT64NKpspP3iA5NVFvwDE/miW153Bojn7nVSwPoenxCexGcVSyvI4bvj346JyvNEjijvO E+vel9CY8ykfM9bKP+JteMJwZrYlrCrsR1XK8cFVqE5qxYgAWBHq33A1rCXVXPmOuTW2K9vhM FAjEoqJvcLt2VEQEW9k0UJ4a0/IxGnsMW5T6mAjLVR28Zj90purh4N3mGXtaWMHgLD1AdZc/t jHSeZy2SVlBfPwn1y/Vysd7LQzwQdeYSglue3pIKpEtk/6/5ZEn3mo/X9c1Axl1nyGOiRu9AQ x49uGIV6DHbbbrBZB+ehUopkgWUZU/0QfcLpsLXebz5H/uASkwdhZwkQcKA4t0IwvSy+Qc9Jm eFsT+dGpoEZwQ1kebxYyqWSwopyl3SrhFmUVnbcQwLOQv4awTXC0lJIj4+klpUDk2Ge4SB10U IMzYuPruZXfQorFbPInYh3J9B+g8YAChu2Vq6654YN7HzYRh9DhtmZXM6ZzUsqpZ0/efmXQek z5Oa5vfzLfZWTq824H6dT2+QN+tuwC3cXfg8YXgxv8aQzf5QJCRU2KyByoU25Y2+JwUXLot+o fuhzEWXjacAssSdEjn3x8TcV+TrMe2kFFEGIQfaz3CtWWI46OjNeoWkTmZaLxMWWxB/pVmv1L LlU+rT9gHZcuRzOFg5HTCQ6+4yEEItaYVkjAyOAXPultWvdLEF1qZw2tmwGeEtuGGcGygXl+q yiS3wOi
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xAmb7UWPnvGiYiWTXiQvENCnrhE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 10:36:49 -0000

On 2017-06-26 04:39, Kazuho Oku wrote:
> ...
> 2017-06-25 19:11 GMT+09:00 Julian Reschke <julian.reschke@gmx.de>:
>> On 2017-06-21 18:59, The IESG wrote:
>>>
>>>
>>> The IESG has received a request from the Hypertext Transfer Protocol WG
>>> (httpbis) to consider the following document: - 'An HTTP Status Code for
>>> Indicating Hints'
>>>     <draft-ietf-httpbis-early-hints-03.txt> as Experimental RFC
>>> ...
>>
>>
>>
>> Here's my feedback...:
>>
>> 2.  103 Early Hints
>>
>>     ...
>>
>>     A server MUST NOT include Content-Length, Transfer-Encoding, or any
>>     hop-by-hop header fields ([RFC7230], Section 6.1) in a 103 (Early
>>     Hints) response.
>>
>> That's a bit weird here, because the requirements for C-L and T-E are
>> generic to 1xx, and already are stated in RFC 7230. The text above makes it
>> sound as if these are specific to 103, which they are not.
>>
>> For hop-by-hop, I'm not convinced that the requirement is needed here.
> 
> I agree that we do not need to talk about C-L and T-E here.
> 
> The reasons I added a clause prohibiting the use of hop-by-hop headers
> in an 103 response are as follows:
> * does not make sense for a response that attempts to send the
> metadata of a final response early
> * to avoid confusion caused by sending a hop-by-hop header in the 103 response
> 
> Without the restriction, a response like below would be valid, which
> IMO is confusing at least.
> 
> ```
> HTTP/1.1 103 Early Hints
> Connection: close
> Link: </style.css>; rel=preload
> 
> HTTP/1.1 200 OK
> Connection: close
> Link: </style.css>; rel=preload
> ...
> ```

Yes, but does that mean we need a normative requirement? Also, is it 
really obvious that no future hop-by-hop header field could be 
meaningful on a 103?

>>     ...
>>
>>     An intermediary MAY drop the informational response. (...)
>>
>> That seems to contradict a MUST-level requirement in RFC 7231
>> (https://www.greenbytes.de/tech/webdav/rfc7231.html#rfc.section.6.2.p.3)
> 
> The statement exists since sending 103 only makes sense when it is
> impossible to immediately send a final response.
> 
> For example, there is no need for a cache that is in possession of a
> freshly-cached final response to send a 103 that was sent from the
> origin before sending the final response. I also believe that most
> caching proxies that exist today do not cache informational responses,
> and that there is no need for us to require them to do so.
> 
> Considering the facts, one way to resolve the issue would be to adjust
> the statement to something like "An intermediary MAY omit the 103
> response when resending a cached response", and argue that re-sending
> a cached response is not an action of "forwarding," which is defined
> as a MUST in RFC 7231.

Sounds good to me.

> But wouldn't it be simpler to just have the "MAY drop" clause for any
> intermediary?

In that case, the spec would contradict RFC 7231, which is bad position 
to be in...

>>     The following example illustrates a typical message exchange that
>>     involves a 103 (Early Hints) response.
>>
>>     Client request:
>>
>>       GET / HTTP/1.1
>>       Host: example.com
>>
>> (maybe insert blank line do delimit the message)
>>
>>     Server response:
>>
>>       HTTP/1.1 103 Early Hints
>>       Link: </style.css>; rel=preload; as=style
>>       Link: </script.js>; rel=preload; as=script
>>
>>       HTTP/1.1 200 OK
>>       Date: Fri, 26 May 2017 10:02:11 GMT
>>       Content-Length: 1234
>>       Content-Type: text/html; charset=utf-8
>>       Link: </style.css>; rel=preload; as=style
>>       Link: </script.js>; rel=preload; as=script
>>
>>       <!doctype html>
>>       [... rest of the response body is ommitted from the example ...]
>>
>> The example suggests that early hints are repeated in the final response. Do
>> they have to, actually?
> 
> Yes. They need to, especially if caching is involved. 103 is an
> intermediary response and there is no guarantee (or a requirement) for
> a cache to retain the headers included only in the informational
> response.
> 
> In case of link rel=preload headers, a client can speculatively load
> the resources included in the headers while revalidating a
> stale-cached response, or a caching proxy can generate a 103 response
> from a stale-cached 200 response, while waiting for the origin to
> perform revalidation.

What I'm after is a clear statement whether they really need to be 
repeated, as normative language.

> ...

Best regards, Julian


From nobody Mon Jun 26 03:46:44 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 490EE126C83; Mon, 26 Jun 2017 03:46:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level: 
X-Spam-Status: No, score=-14.502 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, 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 Nktz8UQpKSIs; Mon, 26 Jun 2017 03:46:33 -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 EBC20126BF3; Mon, 26 Jun 2017 03:46:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26948; q=dns/txt; s=iport; t=1498473992; x=1499683592; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=RoLa4AqXRcYKWLcP5lEoBus/7R2cQIzGgXaam3UnTKA=; b=BTvhJz8+lAg/Hft13r5nn/pSlN4crCaWcjHbNZogSRgsh8keVwGPn9KQ gLVdh9RRau/UsiPqryPXNRLvHS0OqN9/AG9dqRwU1ARQiHv6bGqvfPuJp qS7zPSrX+S6Y3PpHFSvkC1V0c3IilKZljyIv8ZD2ltBdLA79LKqphgbg0 Y=;
X-IronPort-AV: E=Sophos;i="5.39,395,1493683200";  d="scan'208,217";a="652841325"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jun 2017 10:46:30 +0000
Received: from [10.55.221.37] (ams-bclaise-nitro4.cisco.com [10.55.221.37]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v5QAkThI028434; Mon, 26 Jun 2017 10:46:29 GMT
Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
To: Xufeng Liu <Xufeng_Liu@jabil.com>, Robert Wilton <rwilton@cisco.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "draft-ietf-teas-yang-te-topo.all@ietf.org" <draft-ietf-teas-yang-te-topo.all@ietf.org>, Benoit Claise <bclaise@cisco.com>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com> <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com> <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <04b933e2-189a-6fe2-5d24-310167f91b69@cisco.com>
Date: Mon, 26 Jun 2017 12:46:29 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------6D1C27D0843768AFE393C509"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4U7vP2PQDlImPXJnHDR5m9-x33Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 10:46:36 -0000

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

Hi Xufeng,
> Hi Benoit,
>
>> -----Original Message-----
>> From: Benoit Claise [mailto:bclaise@cisco.com]
>> Sent: Thursday, June 22, 2017 6:12 AM
>> To: Robert Wilton <rwilton@cisco.com>; Xufeng Liu <Xufeng_Liu@jabil.com>;
>> Mahesh Jethanandani <mjethanandani@gmail.com>; yang-doctors@ietf.org
>> Cc: ietf@ietf.org; teas@ietf.org; draft-ietf-teas-yang-te-topo.all@ietf.org
>> Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-
>> 08
>>
>> Dear draft-ietf-teas-yang-te-topo authors,
>>> Hi Xufeng,
>>>
>>> OK, by tooling, I don't mean the pyang plugins that I have been
>>> working on to convert between different types of models.  As you
>>> aware, the TE YANG models can easily be converted to NMDA style since
>>> I have already done it
>>> (https://github.com/rgwilton/ietf-models-to-combined).
>>>
>>> My comment actually relates to the fact the structure used by TE YANG
>>> modules don't match any other YANG modules - they are using their own
>>> unique style of structure.
>> This is an important issue to resolve.
>>> Today, there are three common styles of modules:
>>> (1) IETF style split config/state trees (e.g. ietf-interfaces).
>>> (2) IETF NMDA style combined config/state trees (i.e. where all IETF
>>> modules are heading to).
>>> (3) OpenConfig style modules with the config/state containers
>>> immediately above the config leaves.
>>>
>>> Tooling is likely to be optimized to work with these model structures,
>>> but the TE modules do not fit into any of the three styles above.
>>> They are a yet another OpenConfig-like style, but that is different
>>> enough that tooling that is designed to work with OpenConfig style
>>> YANG modules would likely not work with the TE YANG modules.
>>>
>>> Specifically, for clients that expecting to work with an OpenConfig
>>> style YANG module, then if it knows the path to config leaf X, then
>>> they would expect the applied config value to be available at the path
>>> "../state/X".  But, this doesn't hold for the structure being used in
>>> the TE YANG models.
>>>
>>> I believe strongly that the models being produced by organizations
>>> should be structures in a consistent way, hence why I think that the
>>> published standard version of the TE YANG modules should immediately
>>> align to the NMDA style.
>> Agreed.
>> Here is the OPS and RTG AD message:
>> https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html
>>
>> I understand that the I2RS topology YANG modules will be improved to the
>> NMDA style.
> [Xufeng] The I2RS topology model is already NMDA style, but the NMDA models are not immediately implementable without NETCONF/RESTCONF protocol update. We will need the "-state" module for the I2RS topology model (and for all the top-level models) for now.
Adding -state to the Appendix is a possibility.
"In all cases, the NMDA and non-NMDA modules SHOULD be published in the 
same document, with NMDA modules in the document main body and the 
non-NMDA modules in an Appendix."
See https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html
> While the NMDA is nice, the NMDA discussions have already significantly delayed publishing new models, and doing NMDA without staging will further delay the process.
This is not solving the important issue brought up by Rob Witlon:

    My comment actually relates to the fact the structure used by TE
    YANG modules don't match any other YANG modules - they are using
    their own unique style of structure.

Regards, B.
> Thanks,  Xufeng
>> Regards, Benoit
>>> Thanks,
>>> Rob
>>>
>>>
>>> On 22/06/2017 04:16, Xufeng Liu wrote:
>>>> Hi Rob,
>>>>
>>>> While the tooling is very nice to have, especially for writing new
>>>> models or converting models, we do not have to use it for every
>>>> model. It seems not necessary to use the tooling on this model for
>>>> now. We already know that we can manually convert it to NMDA style if
>>>> needed.
>>>>
>>>> Thanks,
>>>> - Xufeng
>>>>
>>>>> -----Original Message-----
>>>>> From: Robert Wilton [mailto:rwilton@cisco.com]
>>>>> Sent: Wednesday, June 21, 2017 5:34 AM
>>>>> To: Xufeng Liu <Xufeng_Liu@jabil.com>; Mahesh Jethanandani
>>>>> <mjethanandani@gmail.com>; yang-doctors@ietf.org
>>>>> Cc: ietf@ietf.org; teas@ietf.org;
>>>>> draft-ietf-teas-yang-te-topo.all@ietf.org
>>>>> Subject: Re: [Teas] Yangdoctors last call review of
>>>>> draft-ietf-teas-yang-te-topo-
>>>>> 08
>>>>>
>>>>> Hi Xufeng,
>>>>>
>>>>> On 12/06/2017 22:28, Xufeng Liu wrote:
>>>>>> Hi Mahesh,
>>>>>>
>>>>>> Thank you much for the review. We have submitted an updated draft
>>>>> (https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09) to
>>>>> address these issues. More detailed explanations are put below
>>>>> inline.
>>>>>> If the responses and updates are satisfactory, we are ready for the
>>>>>> last call.
>>>>>>
>>>>>> Best regards,
>>>>>> - Xufeng
>>>>>>
>>>>>>> -----Original Message-----
>>>>>>> From: Mahesh Jethanandani [mailto:mjethanandani@gmail.com]
>>>>>>> Sent: Wednesday, May 24, 2017 11:44 AM
>>>>>>> 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
>>>>>>>
>>>>>>> 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?
>>>>>> [Xufeng] Containers that use “presence” are:
>>>>>>      - Container “underlay”
>>>>>>        o  We have changed 13 occurrences of such containers to be
>>>>>> not
>>>>> presence container.
>>>>>>      - Container “te” under augmentation
>>>>>>        o  To indicate that “TE” is enabled (configuration data)
>>>>>>        o  Also used to do augmentation. The “presence” statement can
>>>>> prevent the mandatory child from affecting augmented base model.
>>>>>>      - /nw:networks/nw:network/nw:network-types/te-topology!
>>>>>>        o  A mechanism required by I2RS topology model to specify the
>>>>> topology type.
>>>>>>> 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.
>>>>>> [Xufeng] Yes. These two terms are the same. Figure 12, Figure 13,
>>>>>> and relevant
>>>>> descriptions have been updated to make the document consistent.
>>>>>>> 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.
>>>>>> [Xufeng] We have removed the following groupings
>>>>>>        te-link-augment
>>>>>>        te-node-augment
>>>>>>        te-termination-point-augment
>>>>>>        te-topologies-augment
>>>>>>        te-topology-augment
>>>>>>        te-link-state-underlay-attributes
>>>>>>        te-node-state-derived-notification
>>>>>>        te-topology-type
>>>>>>
>>>>>> The remaining groupings have been kept so that we can:
>>>>>>      - Share the groupings in this model
>>>>>>      - Prepare to be shared by a model augmenting this model
>>>>>>      - Prevent a grouping or configuration section from being too long
>>>>>>      - Improve readability
>>>>>>
>>>>>>> The split between config and state containers does not seem to
>>>>>>> follow any particular pattern.
>>>>>> [Xufeng] The pattern is clear:
>>>>>> For each manageable entity (object), there is a config container
>>>>>> and state
>>>>> container. The configurable properties go into the config container
>>>>> and state properties go into the state container. Such objects are
>>>>> identified by a list item or a presence container so that the
>>>>> “create”, “delete”, and “modify”
>>>>> operations
>>>>> can be performed on them. The non-presence containers do not
>>>>> represent configuration data so they do not introduce such objects.
>>>>>>> It is neither a top level split, as is the case with existing IETF
>>>>>>> models,
>>>>>> [Xufeng] We could not do top level split because the base I2RS
>>>>>> network
>>>>> topology model
>>>>> (https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo-
>>>>> 12) that we augment does not have the top-level split (for its own
>>>>> reasons).
>>>>>>> nor do they follow the OpenConfig style of splitting config and
>>>>>>> state under each relevant leaf,
>>>>>> [Xufeng] The pattern is consistent with this style in principle,
>>>>>> with some
>>>>> adjustments to fit to our multiple levels of hierarchy.
>>>>> This is effectively a new forth style of YANG models that is not
>>>>> consistent with any of the three existing styles, i.e.:
>>>>>     - Current IETF config/state split model style
>>>>>     - NMDA combined config/state tree
>>>>>     - OpenConfig split config/state containers immediately above the
>>>>> config true leaves.
>>>>>
>>>>> Tooling that it designed to work with OpenConfig models will need
>>>>> customization to work with these TE models because the config/state
>>>>> containers will not be where the tooling expects them to be.
>>>>>
>>>>> Thanks,
>>>>> Rob
>>> .
>>>


--------------6D1C27D0843768AFE393C509
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 Xufeng,<br>
    </div>
    <blockquote type="cite"
cite="mid:BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com">
      <pre wrap="">Hi Benoit,

</pre>
      <blockquote type="cite">
        <pre wrap="">-----Original Message-----
From: Benoit Claise [<a class="moz-txt-link-freetext" href="mailto:bclaise@cisco.com">mailto:bclaise@cisco.com</a>]
Sent: Thursday, June 22, 2017 6:12 AM
To: Robert Wilton <a class="moz-txt-link-rfc2396E" href="mailto:rwilton@cisco.com">&lt;rwilton@cisco.com&gt;</a>; Xufeng Liu <a class="moz-txt-link-rfc2396E" href="mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>;
Mahesh Jethanandani <a class="moz-txt-link-rfc2396E" href="mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</a>; <a class="moz-txt-link-abbreviated" href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:teas@ietf.org">teas@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas-yang-te-topo.all@ietf.org</a>
Subject: Re: [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-
08

Dear draft-ietf-teas-yang-te-topo authors,
</pre>
        <blockquote type="cite">
          <pre wrap="">Hi Xufeng,

OK, by tooling, I don't mean the pyang plugins that I have been
working on to convert between different types of models.  As you
aware, the TE YANG models can easily be converted to NMDA style since
I have already done it
(<a class="moz-txt-link-freetext" href="https://github.com/rgwilton/ietf-models-to-combined">https://github.com/rgwilton/ietf-models-to-combined</a>).

My comment actually relates to the fact the structure used by TE YANG
modules don't match any other YANG modules - they are using their own
unique style of structure.
</pre>
        </blockquote>
        <pre wrap="">This is an important issue to resolve.
</pre>
        <blockquote type="cite">
          <pre wrap="">
Today, there are three common styles of modules:
(1) IETF style split config/state trees (e.g. ietf-interfaces).
(2) IETF NMDA style combined config/state trees (i.e. where all IETF
modules are heading to).
(3) OpenConfig style modules with the config/state containers
immediately above the config leaves.

Tooling is likely to be optimized to work with these model structures,
but the TE modules do not fit into any of the three styles above.
They are a yet another OpenConfig-like style, but that is different
enough that tooling that is designed to work with OpenConfig style
YANG modules would likely not work with the TE YANG modules.

Specifically, for clients that expecting to work with an OpenConfig
style YANG module, then if it knows the path to config leaf X, then
they would expect the applied config value to be available at the path
"../state/X".  But, this doesn't hold for the structure being used in
the TE YANG models.

I believe strongly that the models being produced by organizations
should be structures in a consistent way, hence why I think that the
published standard version of the TE YANG modules should immediately
align to the NMDA style.
</pre>
        </blockquote>
        <pre wrap="">Agreed.
Here is the OPS and RTG AD message:
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html</a>

I understand that the I2RS topology YANG modules will be improved to the
NMDA style.
</pre>
      </blockquote>
      <pre wrap="">[Xufeng] The I2RS topology model is already NMDA style, but the NMDA models are not immediately implementable without NETCONF/RESTCONF protocol update. We will need the "-state" module for the I2RS topology model (and for all the top-level models) for now. </pre>
    </blockquote>
    Adding -state to the Appendix is a possibility.<br>
    "<font color="#000000">In all cases, the NMDA and non-NMDA modules
      SHOULD be published in the same document, with NMDA modules in the
      document main body and the non-NMDA modules in an Appendix."<br>
      See
      <a class="moz-txt-link-freetext" href="https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html">https://www.ietf.org/mail-archive/web/netmod/current/msg18252.html</a><br>
    </font>
    <blockquote type="cite"
cite="mid:BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com">
      <pre wrap="">While the NMDA is nice, the NMDA discussions have already significantly delayed publishing new models, and doing NMDA without staging will further delay the process.</pre>
    </blockquote>
    This is not solving the important issue brought up by Rob Witlon:<br>
    <blockquote>My comment actually relates to the fact the structure
      used by TE YANG
      modules don't match any other YANG modules - they are using their
      own
      unique style of structure.</blockquote>
    Regards, B.<br>
    <blockquote type="cite"
cite="mid:BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com">
      <pre wrap="">
Thanks,  Xufeng
</pre>
      <blockquote type="cite">
        <pre wrap="">
Regards, Benoit
</pre>
        <blockquote type="cite">
          <pre wrap="">
Thanks,
Rob


On 22/06/2017 04:16, Xufeng Liu wrote:
</pre>
          <blockquote type="cite">
            <pre wrap="">Hi Rob,

While the tooling is very nice to have, especially for writing new
models or converting models, we do not have to use it for every
model. It seems not necessary to use the tooling on this model for
now. We already know that we can manually convert it to NMDA style if
needed.

Thanks,
- Xufeng

</pre>
            <blockquote type="cite">
              <pre wrap="">-----Original Message-----
From: Robert Wilton [<a class="moz-txt-link-freetext" href="mailto:rwilton@cisco.com">mailto:rwilton@cisco.com</a>]
Sent: Wednesday, June 21, 2017 5:34 AM
To: Xufeng Liu <a class="moz-txt-link-rfc2396E" href="mailto:Xufeng_Liu@jabil.com">&lt;Xufeng_Liu@jabil.com&gt;</a>; Mahesh Jethanandani
<a class="moz-txt-link-rfc2396E" href="mailto:mjethanandani@gmail.com">&lt;mjethanandani@gmail.com&gt;</a>; <a class="moz-txt-link-abbreviated" href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:teas@ietf.org">teas@ietf.org</a>;
<a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas-yang-te-topo.all@ietf.org</a>
Subject: Re: [Teas] Yangdoctors last call review of
draft-ietf-teas-yang-te-topo-
08

Hi Xufeng,

On 12/06/2017 22:28, Xufeng Liu wrote:
</pre>
              <blockquote type="cite">
                <pre wrap="">Hi Mahesh,

Thank you much for the review. We have submitted an updated draft
</pre>
              </blockquote>
              <pre wrap="">(<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09">https://tools.ietf.org/html/draft-ietf-teas-yang-te-topo-09</a>) to
address these issues. More detailed explanations are put below
inline.
</pre>
              <blockquote type="cite">
                <pre wrap="">If the responses and updates are satisfactory, we are ready for the
last call.

Best regards,
- Xufeng

</pre>
                <blockquote type="cite">
                  <pre wrap="">-----Original Message-----
From: Mahesh Jethanandani [<a class="moz-txt-link-freetext" href="mailto:mjethanandani@gmail.com">mailto:mjethanandani@gmail.com</a>]
Sent: Wednesday, May 24, 2017 11:44 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:yang-doctors@ietf.org">yang-doctors@ietf.org</a>
Cc: <a class="moz-txt-link-abbreviated" href="mailto:ietf@ietf.org">ietf@ietf.org</a>; <a class="moz-txt-link-abbreviated" href="mailto:teas@ietf.org">teas@ietf.org</a>;
<a class="moz-txt-link-abbreviated" href="mailto:draft-ietf-teas-yang-te-topo.all@ietf.org">draft-ietf-teas-yang-te-topo.all@ietf.org</a>
Subject: Yangdoctors last call review of
draft-ietf-teas-yang-te-topo-08

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
</pre>
                </blockquote>
              </blockquote>
              <pre wrap="">with Issues”
</pre>
              <blockquote type="cite">
                <blockquote type="cite">
                  <pre wrap="">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
</pre>
                </blockquote>
              </blockquote>
            </blockquote>
          </blockquote>
        </blockquote>
        <pre wrap="">augment.
</pre>
        <blockquote type="cite">
          <blockquote type="cite">
            <blockquote type="cite">
              <blockquote type="cite">
                <blockquote type="cite">
                  <pre wrap="">
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
</pre>
                </blockquote>
              </blockquote>
              <pre wrap="">representing in itself?
</pre>
              <blockquote type="cite">
                <pre wrap="">[Xufeng] Containers that use “presence” are:
    - Container “underlay”
      o  We have changed 13 occurrences of such containers to be
not
</pre>
              </blockquote>
              <pre wrap="">presence container.
</pre>
              <blockquote type="cite">
                <pre wrap="">    - Container “te” under augmentation
      o  To indicate that “TE” is enabled (configuration data)
      o  Also used to do augmentation. The “presence” statement can
</pre>
              </blockquote>
              <pre wrap="">prevent the mandatory child from affecting augmented base model.
</pre>
              <blockquote type="cite">
                <pre wrap="">    - /nw:networks/nw:network/nw:network-types/te-topology!
      o  A mechanism required by I2RS topology model to specify the
</pre>
              </blockquote>
              <pre wrap="">topology type.
</pre>
              <blockquote type="cite">
                <blockquote type="cite">
                  <pre wrap="">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
</pre>
                </blockquote>
              </blockquote>
              <pre wrap="">Model”.
</pre>
              <blockquote type="cite">
                <blockquote type="cite">
                  <pre wrap="">Are these one and the same models? If so, a common term for both
of them would be helpful.
</pre>
                </blockquote>
                <pre wrap="">[Xufeng] Yes. These two terms are the same. Figure 12, Figure 13,
and relevant
</pre>
              </blockquote>
              <pre wrap="">descriptions have been updated to make the document consistent.
</pre>
              <blockquote type="cite">
                <blockquote type="cite">
                  <pre wrap="">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
</pre>
                </blockquote>
              </blockquote>
              <pre wrap="">connectivity-label-restriction-list.
</pre>
              <blockquote type="cite">
                <pre wrap="">[Xufeng] We have removed the following groupings
      te-link-augment
      te-node-augment
      te-termination-point-augment
      te-topologies-augment
      te-topology-augment
      te-link-state-underlay-attributes
      te-node-state-derived-notification
      te-topology-type

The remaining groupings have been kept so that we can:
    - Share the groupings in this model
    - Prepare to be shared by a model augmenting this model
    - Prevent a grouping or configuration section from being too long
    - Improve readability

</pre>
                <blockquote type="cite">
                  <pre wrap="">The split between config and state containers does not seem to
follow any particular pattern.
</pre>
                </blockquote>
                <pre wrap="">[Xufeng] The pattern is clear:
For each manageable entity (object), there is a config container
and state
</pre>
              </blockquote>
              <pre wrap="">container. The configurable properties go into the config container
and state properties go into the state container. Such objects are
identified by a list item or a presence container so that the
“create”, “delete”, and “modify”
operations
can be performed on them. The non-presence containers do not
represent configuration data so they do not introduce such objects.
</pre>
              <blockquote type="cite">
                <blockquote type="cite">
                  <pre wrap="">It is neither a top level split, as is the case with existing IETF
models,
</pre>
                </blockquote>
                <pre wrap="">[Xufeng] We could not do top level split because the base I2RS
network
</pre>
              </blockquote>
              <pre wrap="">topology model
(<a class="moz-txt-link-freetext" href="https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo">https://tools.ietf.org/html/draft-ietf-i2rs-yang-network-topo</a>-
12) that we augment does not have the top-level split (for its own
reasons).
</pre>
              <blockquote type="cite">
                <blockquote type="cite">
                  <pre wrap="">nor do they follow the OpenConfig style of splitting config and
state under each relevant leaf,
</pre>
                </blockquote>
                <pre wrap="">[Xufeng] The pattern is consistent with this style in principle,
with some
</pre>
              </blockquote>
              <pre wrap="">adjustments to fit to our multiple levels of hierarchy.
This is effectively a new forth style of YANG models that is not
consistent with any of the three existing styles, i.e.:
   - Current IETF config/state split model style
   - NMDA combined config/state tree
   - OpenConfig split config/state containers immediately above the
config true leaves.

Tooling that it designed to work with OpenConfig models will need
customization to work with these TE models because the config/state
containers will not be where the tooling expects them to be.

Thanks,
Rob
</pre>
            </blockquote>
          </blockquote>
          <pre wrap="">
.

</pre>
        </blockquote>
      </blockquote>
      <pre wrap="">
</pre>
    </blockquote>
    <br>
  </body>
</html>

--------------6D1C27D0843768AFE393C509--


From nobody Mon Jun 26 05:12:19 2017
Return-Path: <gunter.van_de_velde@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 90481129B2F; Mon, 26 Jun 2017 05:12:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.912
X-Spam-Level: 
X-Spam-Status: No, score=-2.912 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_H5=-1, 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=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 KAPqtudy0M7N; Mon, 26 Jun 2017 05:12:15 -0700 (PDT)
Received: from EUR02-HE1-obe.outbound.protection.outlook.com (mail-eopbgr10121.outbound.protection.outlook.com [40.107.1.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 311DD1294C8; Mon, 26 Jun 2017 05:12:15 -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=036SGzGaKVQKSg0zb9KX2E+EVg4IImvuPqeHyuj52aI=; b=FkUTKR7YcNwFWgQVCJIpmorz1IbiIVTDbHr3luWYsTbrIssSeuJLRezI5769daggCz1dkiXXZkl2AWowb8oviWHbNlggwZMaVyj8ejtkkDvp5V6ZwsZO7p7LIi/MMCSOhPlmpU6fUdTDgifD368yUAF4bSNbMkBbYGk8yMsMzA4=
Received: from AM4PR07MB1715.eurprd07.prod.outlook.com (10.166.133.23) by AM4PR07MB1649.eurprd07.prod.outlook.com (10.166.132.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.5; Mon, 26 Jun 2017 12:12:12 +0000
Received: from AM4PR07MB1715.eurprd07.prod.outlook.com ([fe80::d832:c9c1:9dfa:23af]) by AM4PR07MB1715.eurprd07.prod.outlook.com ([fe80::d832:c9c1:9dfa:23af%13]) with mapi id 15.01.1220.009; Mon, 26 Jun 2017 12:12:12 +0000
From: "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>
CC: "v6ops@ietf.org" <v6ops@ietf.org>, "draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org" <draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>
Subject: Re: [v6ops] Last Call: <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 Prefix Per Host) to Best Current Practice
Thread-Topic: [v6ops] Last Call: <draft-ietf-v6ops-unique-ipv6-prefix-per-host-03.txt> (Unique IPv6 Prefix Per Host) to Best Current Practice
Thread-Index: AQHS7nVwy1Lf3818YU+QsvEn2zlIIw==
Date: Mon, 26 Jun 2017 12:12:12 +0000
Message-ID: <7C2A93A5-F01E-4474-AED3-D01FB9B2F34A@nokia.com>
References: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com> <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com>
In-Reply-To: <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=gunter.van_de_velde@nokia.com; 
x-originating-ip: [212.88.252.216]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM4PR07MB1649; 7:iSAoG0FJQSnULe603OP03OxYOXyZxFCXzThcr5osjqFkXYkcwmnWg82rn/ZqLnwEp+SURyFJ+9In6QhlVDZlz/HW/bfYuobQUgKQxi8mJeUPHrowNBbfRz9IDfoUzIWzqd2lRfFT3Sq0otFWdWM5vYCnHtZBYZGiH/ppMBMoi7fqPakaWwFNtuz4x5nRtQD6KwIW3wg8iRgJpB+Q98eBNe2ZtbAmuNmKDmJqbA4QDLA27pyU57dbaRlqvjhPblUnEy9n0q7cp2nNdlHNqI0Z5QObUvsHj82iZMxvZAXzuc6umqAD7LOK4PPOHRM7LfxYPk4LQ+SNeYx0nMe7+EFHrRr2lZD+i47mbwA7pm3cGPwIJ+tXkFci8QRYyf45mCOATWoX4hk84fc5NxgchwacLlIcmUC1j4PSQ6aP7vKwOuoGkld4kB9KwgnB2MkoIYOKzWCiJFOQFyQzCgrPKUTZqKqPNR35L0gKlr9vj6nKjP1JcNZv8O0nFnkmhVUoEdGk8wu1Hwepg2+WBssp8e0Ntsp7QZ0aK86xbWQ2mSwCk3igWACZHbCklGYFx9nylLbbS/fELShIMFT3HwpPy/i+XO/EY6p0cqFJCHnQQaRGbdAvPA0MdxnCywz5TZEHRCJaaY4iQn3fF049qM6v0dw+0BC77S24n6nHNGP3g6teKF89eJN2mzpvWkfmPF1hltXGT14mNnuG/YuW0D8QClHMY4FzUvzKZyjedvcJbeLXlquI4407kGbP9CaGgfR5J2hnHNBWzTa0cvmls8ovu2A/sYle5TGcaX/GKa5Lu6kszjs=
x-ms-office365-filtering-correlation-id: 597fb72f-1f6d-41b1-dc2b-08d4bc8c937b
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(300000503095)(300135400095)(48565401081)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506067)(300135500095); SRVR:AM4PR07MB1649; 
x-ms-traffictypediagnostic: AM4PR07MB1649:
x-microsoft-antispam-prvs: <AM4PR07MB164954C7A54A81B144BF8214E0DF0@AM4PR07MB1649.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(278178393323532)(120809045254105)(236129657087228); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(3002001)(6055026)(6041248)(20161123564025)(20161123562025)(20161123555025)(20161123560025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:AM4PR07MB1649; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:AM4PR07MB1649; 
x-forefront-prvs: 0350D7A55D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39840400002)(39850400002)(39450400003)(39860400002)(39410400002)(39400400002)(24454002)(51914003)(230783001)(101416001)(86362001)(2906002)(33656002)(3280700002)(3660700001)(76176999)(50986999)(54356999)(2950100002)(14454004)(305945005)(39060400002)(38730400002)(53546010)(81166006)(8676002)(66066001)(25786009)(6116002)(102836003)(3846002)(5250100002)(2501003)(189998001)(36756003)(8936002)(6512007)(53936002)(966005)(6306002)(99286003)(54906002)(7736002)(478600001)(229853002)(2900100001)(4326008)(5660300001)(6246003)(83716003)(6436002)(6486002)(6506006)(82746002)(222643001); DIR:OUT; SFP:1102; SCL:1; SRVR:AM4PR07MB1649; H:AM4PR07MB1715.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
received-spf: None (protection.outlook.com: nokia.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <349B792331A9624391F20B0EDB78CAAD@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jun 2017 12:12:12.0175 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM4PR07MB1649
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nb52tKCqE1P07BFjs-WALXGPfuQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 12:12:18 -0000

SGkgQnJpYW4sIA0KDQpUaGFua3MgZm9yIHRoZSByZXZpZXcuDQoNCkkgbW9kaWZpZWQgdGhlIHJl
ZmVyZW5jZSB0byAvNjQgSVB2NiBwcmVmaXggbGVuZ3RoIGFuZCBzdWdnZXN0ZWQgaW5zdGVhZCAN
CmNvbnNpc3RlbmN5IHdpdGggUkZDNzYwOCBhbmQgdGhhdCBjdXJyZW50bHkgdGhpcyBsaWtlbHkg
bWVhbnMgYSAvNjQgaW4gdGhlIC0wNCB2ZXJzaW9uLg0KDQpBbGwgdGhlIGJlc3QsDQpHLw0KDQpP
biAyNi8wNS8yMDE3LCAyMjoyNCwgIkJyaWFuIEUgQ2FycGVudGVyIiA8YnJpYW4uZS5jYXJwZW50
ZXJAZ21haWwuY29tPiB3cm90ZToNCg0KICAgIEhpLA0KICAgIA0KICAgIEkgc2hvdWxkIGhhdmUg
bm90aWNlZCB0aGlzIGR1cmluZyB0aGUgdjZvcHMgZGlzY3Vzc2lvbnMsIGJ1dCBJIGRpZG4ndCwN
CiAgICBzb3JyeS4NCiAgICANCiAgICBUaGlzIGRyYWZ0IGNpdGVzIFJGQzQ4NjIgKFNMQUFDKSBh
bmQgbWVudGlvbnMgUm91dGVyIEFkdmVydGlzZW1lbnRzDQogICAgKHdpdGhvdXQgYWxzbyBjaXRp
bmcgUkZDNDg2MSwgd2hpY2ggaXMgcG9zc2libHkgYSBtaXN0YWtlKS4gVGhvc2UNCiAgICBkb2N1
bWVudHMgZG8gbm90IHNwZWNpZnkgdGhlIHN1Ym5ldCBwcmVmaXggbGVuZ3RoLiBTbyB0aGUgZHJh
ZnQNCiAgICBzaG91bGRuJ3QgYXNzdW1lIGEgcGFydGljdWxhciBwcmVmaXggbGVuZ3RoIGVpdGhl
ci4gV2UgYWxsIGtub3cgdGhhdA0KICAgIGl0J3MgdXN1YWxseSA2NCB0b2RheSwgYnV0IHRoYXQg
ZG9lc24ndCBhZmZlY3QgdGhlIGFyZ3VtZW50IG1hZGUgYnkNCiAgICB0aGUgZHJhZnQuIFdlIG5l
ZWQgY29uc2lzdGVuY3kgd2l0aCBSRkMgNzYwOCAoQkNQIDE5OCkuDQogICAgDQogICAgUmVnYXJk
cw0KICAgICAgIEJyaWFuIENhcnBlbnRlcg0KICAgIA0KICAgIE9uIDI0LzA1LzIwMTcgMDc6NDEs
IFRoZSBJRVNHIHdyb3RlOg0KICAgID4gDQogICAgPiBUaGUgSUVTRyBoYXMgcmVjZWl2ZWQgYSBy
ZXF1ZXN0IGZyb20gdGhlIElQdjYgT3BlcmF0aW9ucyBXRyAodjZvcHMpDQogICAgPiB0byBjb25z
aWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50OiAtICdVbmlxdWUgSVB2NiBQcmVmaXggUGVyIEhv
c3QnIA0KICAgID4gPGRyYWZ0LWlldGYtdjZvcHMtdW5pcXVlLWlwdjYtcHJlZml4LXBlci1ob3N0
LTAzLnR4dD4gYXMgQmVzdA0KICAgID4gQ3VycmVudCBQcmFjdGljZQ0KICAgID4gDQogICAgPiBU
aGUgSUVTRyBwbGFucyB0byBtYWtlIGEgZGVjaXNpb24gaW4gdGhlIG5leHQgZmV3IHdlZWtzLCBh
bmQNCiAgICA+IHNvbGljaXRzIGZpbmFsIGNvbW1lbnRzIG9uIHRoaXMgYWN0aW9uLiBQbGVhc2Ug
c2VuZCBzdWJzdGFudGl2ZQ0KICAgID4gY29tbWVudHMgdG8gdGhlIGlldGZAaWV0Zi5vcmcgbWFp
bGluZyBsaXN0cyBieSAyMDE3LTA2LTA2Lg0KICAgID4gRXhjZXB0aW9uYWxseSwgY29tbWVudHMg
bWF5IGJlIHNlbnQgdG8gaWVzZ0BpZXRmLm9yZyBpbnN0ZWFkLiBJbg0KICAgID4gZWl0aGVyIGNh
c2UsIHBsZWFzZSByZXRhaW4gdGhlIGJlZ2lubmluZyBvZiB0aGUgU3ViamVjdCBsaW5lIHRvIGFs
bG93DQogICAgPiBhdXRvbWF0ZWQgc29ydGluZy4NCiAgICA+IA0KICAgID4gQWJzdHJhY3QNCiAg
ICA+IA0KICAgID4gDQogICAgPiBJbiBzb21lIElQdjYgZW52aXJvbm1lbnRzLCB0aGUgbmVlZCBo
YXMgYXJpc2VuIGZvciBob3N0cyB0byBiZSBhYmxlIA0KICAgID4gdG8gdXRpbGl6ZSBhIHVuaXF1
ZSBJUHY2IHByZWZpeCwgZXZlbiB0aG91Z2ggdGhlIGxpbmsgb3IgbWVkaWEgbWF5DQogICAgPiBi
ZSBzaGFyZWQuICBUeXBpY2FsbHkgaG9zdHMgKHN1YnNjcmliZXJzKSBvbiBhIHNoYXJlZCBuZXR3
b3JrLA0KICAgID4gZWl0aGVyIHdpcmVkIG9yIHdpcmVsZXNzLCBzdWNoIGFzIEV0aGVybmV0LCBX
aUZpLCBldGMuLCB3aWxsIGFjcXVpcmUNCiAgICA+IHVuaXF1ZSBJUHY2IGFkZHJlc3NlcyBmcm9t
IGEgY29tbW9uIElQdjYgcHJlZml4IHRoYXQgaXMgYWxsb2NhdGVkIG9yIA0KICAgID4gYXNzaWdu
ZWQgZm9yIHVzZSBvbiBhIHNwZWNpZmljIGxpbmsuDQogICAgPiANCiAgICA+IEluIG1vc3QgZGVw
bG95bWVudHMgdG9kYXksIElQdjYgYWRkcmVzcyBhc3NpZ25tZW50IGZyb20gYSBzaW5nbGUNCiAg
ICA+IElQdjYgcHJlZml4IG9uIGEgc2hhcmVkIG5ldHdvcmsgaXMgZG9uZSBieSBlaXRoZXIgdXNp
bmcgSVB2Ng0KICAgID4gc3RhdGVsZXNzIGFkZHJlc3MgYXV0by1jb25maWd1cmF0aW9uIChTTEFB
QykgYW5kL29yIHN0YXRlZnVsIERIQ1B2Ni4NCiAgICA+IFdoaWxlIHRoaXMgaXMgc3RpbGwgdmlh
YmxlIGFuZCBvcGVyYXRlcyBhcyBkZXNpZ25lZCwgdGhlcmUgYXJlIHNvbWUNCiAgICA+IGxhcmdl
IHNjYWxlIGVudmlyb25tZW50cyB3aGVyZSB0aGlzIGNvbmNlcHQgaW50cm9kdWNlcyBzaWduaWZp
Y2FudCANCiAgICA+IHBlcmZvcm1hbmNlIGNoYWxsZW5nZXMgYW5kIGltcGxpY2F0aW9ucywgc3Bl
Y2lmaWNhbGx5IHJlbGF0ZWQgdG8NCiAgICA+IElQdjYgcm91dGVyIGFuZCBuZWlnaGJvciBkaXNj
b3ZlcnkuDQogICAgPiANCiAgICA+IFRoaXMgZG9jdW1lbnQgb3V0bGluZXMgYW4gYXBwcm9hY2gg
dXRpbGlzaW5nIGV4aXN0aW5nIElQdjYgcHJvdG9jb2xzIA0KICAgID4gdG8gYWxsb3cgaG9zdHMg
dG8gYmUgYXNzaWduZWQgYSB1bmlxdWUgSVB2NiBwcmVmaXggKGluc3RlYWQgb2YgYSANCiAgICA+
IHVuaXF1ZSBJUHY2IGFkZHJlc3MgZnJvbSBhIHNoYXJlZCBJUHY2IHByZWZpeCkuICBCZW5lZml0
cyBvZiB1bmlxdWUgDQogICAgPiBJUHY2IHByZWZpeCBvdmVyIGEgdW5pcXVlIElQdjYgYWRkcmVz
cyBmcm9tIHRoZSBzZXJ2aWNlIHByb3ZpZGVyIA0KICAgID4gaW5jbHVkZSBpbXByb3ZlZCBzdWJz
Y3JpYmVyIGlzb2xhdGlvbiBhbmQgZW5oYW5jZWQgc3Vic2NyaWJlciANCiAgICA+IG1hbmFnZW1l
bnQuDQogICAgPiANCiAgICA+IA0KICAgID4gVGhlIGZpbGUgY2FuIGJlIG9idGFpbmVkIHZpYSAN
CiAgICA+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtdjZvcHMt
dW5pcXVlLWlwdjYtcHJlZml4LXBlci1ob3N0Lw0KICAgID4NCiAgICA+ICBJRVNHIGRpc2N1c3Np
b24gY2FuIGJlIHRyYWNrZWQgdmlhIA0KICAgID4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9y
Zy9kb2MvZHJhZnQtaWV0Zi12Nm9wcy11bmlxdWUtaXB2Ni1wcmVmaXgtcGVyLWhvc3QvYmFsbG90
Lw0KICAgID4NCiAgICA+IA0KICAgID4gDQogICAgPiBObyBJUFIgZGVjbGFyYXRpb25zIGhhdmUg
YmVlbiBzdWJtaXR0ZWQgZGlyZWN0bHkgb24gdGhpcyBJLUQuDQogICAgPiANCiAgICA+IA0KICAg
ID4gVGhlIGRvY3VtZW50IGNvbnRhaW5zIHRoZXNlIG5vcm1hdGl2ZSBkb3dud2FyZCByZWZlcmVu
Y2VzLiBTZWUgUkZDDQogICAgPiAzOTY3IGZvciBhZGRpdGlvbmFsIGluZm9ybWF0aW9uOiByZmM2
MTA2OiBJUHY2IFJvdXRlciBBZHZlcnRpc2VtZW50DQogICAgPiBPcHRpb25zIGZvciBETlMgQ29u
ZmlndXJhdGlvbiAoUHJvcG9zZWQgU3RhbmRhcmQgLSBJRVRGIHN0cmVhbSkgDQogICAgPiByZmM0
OTQxOiBQcml2YWN5IEV4dGVuc2lvbnMgZm9yIFN0YXRlbGVzcyBBZGRyZXNzIEF1dG9jb25maWd1
cmF0aW9uDQogICAgPiBpbiBJUHY2IChEcmFmdCBTdGFuZGFyZCAtIElFVEYgc3RyZWFtKSByZmM0
ODYyOiBJUHY2IFN0YXRlbGVzcw0KICAgID4gQWRkcmVzcyBBdXRvY29uZmlndXJhdGlvbiAoRHJh
ZnQgU3RhbmRhcmQgLSBJRVRGIHN0cmVhbSkgcmZjMzMxNToNCiAgICA+IER5bmFtaWMgSG9zdCBD
b25maWd1cmF0aW9uIFByb3RvY29sIGZvciBJUHY2IChESENQdjYpIChQcm9wb3NlZA0KICAgID4g
U3RhbmRhcmQgLSBJRVRGIHN0cmVhbSkNCiAgICA+IA0KICAgID4gDQogICAgPiANCiAgICA+IF9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fIHY2b3BzIG1haWxp
bmcgbGlzdCANCiAgICA+IHY2b3BzQGlldGYub3JnIGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vdjZvcHMgLg0KICAgID4gDQogICAgDQoNCg==


From nobody Mon Jun 26 05:59:24 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 BCC75129B5B; Mon, 26 Jun 2017 05:59:16 -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, FREEMAIL_FROM=0.001, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ExvyYyaGB761; Mon, 26 Jun 2017 05:59:15 -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 A9E4F129B57; Mon, 26 Jun 2017 05:59:14 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.84.68]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MKYpv-1dQqed1hI7-001zV5; Mon, 26 Jun 2017 14:59:12 +0200
Subject: Re: ART Area Review for draft-ietf-calext-caldav-attachments-02
From: Julian Reschke <julian.reschke@gmx.de>
To: IETF Discussion <ietf@ietf.org>, art@ietf.org
References: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de>
Message-ID: <c6352978-a5ce-0196-4f55-a68f3432b21b@gmx.de>
Date: Mon, 26 Jun 2017 14:59:11 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <c04f39e2-79d2-ab9d-59ab-26e51d7ab5fc@gmx.de>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:1kNNqodrTRMO+V676Dz5f4dqM0Txwkoaa1Eevm1EF48ryEI/Phz FsCp/sKLA7wPfjYyv9Mfp4XX8p9Cku0gbxeYzQy2yeV7voBtmm1jdNV4eACg1S3VaZHxGPH rAexX80VthENJxboOFmzHhowgcmbJLLDw1/eidl6CmV7HeZNszypHUj6TJHEJjyimRuCU0K QG0I5XJb1xC7LMG7Oz5FA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:gPDQu/1ee2o=:8wZRx6wZfwRHSmQIU3TKFy yiIC7opYazgqEd7zEIiYPATXwmZW2c7VQ7unryKL/VN5NfMpuBLeeEM/LKjdxicuXZkGpYOE+ ZrKugma2Ubg3Ldwm2JJ/fHMgn2owjBb/WejmNr/8JQ2ydSG2aXHd21J9Q+E2VF3+yraSQqKRj SCWymducSADs99swj8HBcSwFGeC2JVXztQMfALyFoTkXOdlkoUD562jYpWcZlBe1UT6AXG5n6 UPIm+5FmdI/G7tnejkwqqtY9Qt5au1HVCzgqriY4m8MrMwYTyrGRlxH0yRxSgwO09rcJ1BtU+ RKlRucvHTMkiI76Ix5oHKpfUAnGniuXD8eVEp7j1w3NeCbyYyWFo0s/3lOvOpLEkxPsNQjREO ReObibiwKIcOadxYfvXoCXynaGMadUsotFLyiXiD5Bcjmertw5tu8zf7ZIb97nhP/6h/NgnJK rDlrxi+pZe/s6qwjfoG0SCPHghxmlRybBdqklwG7VtLDIkkwY1B4DlfYFrY2192Jm+dTMHexk 7KZvSFYwbIUZNWGmTvsaC5Ju8r3Yq8VnYFC0zRvgYO9e+C2y1VbH1+eG6OvHn5pQK38ok3lsB EmCK/SMnmRj+mo+eG4BGZ3No6SVTLe1IJdmUUy+MLnY5WLPWK0Z89iUcy4nXVC9yBtQ2LGJIY vLMHelEcOwthjQoqwO3H4ltCTBeWiBbWEHesCo+KLX7CDYllNTqYxTxaEKiRkIAlLfOsHpfQk x5gC30jtcxZcE4llL+shUpqSAmPBtTLy0YtaBidBH9g9at4hs/uerPOEBp7/uO1tNxkuF1s0m viEY+fj
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2zdyV0GcTbQvj46yh0kZi-4IOO0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 12:59:17 -0000

On 2017-05-14 16:23, Julian Reschke wrote:
> ...
Another thing that I just noticed: the spec uses Content-Disposition as 
request header field 
(<https://tools.ietf.org/html/draft-ietf-calext-caldav-attachments-02#section-3.4>), 
however it's currently only defined as response header field (RFC6266).

Best regards, Julian


From nobody Mon Jun 26 06:37:49 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 59D1D129BF0 for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 06:37:48 -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 ta4RfcVj0P7Q for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 06:37:41 -0700 (PDT)
Received: from mail-vk0-x22e.google.com (mail-vk0-x22e.google.com [IPv6:2607:f8b0:400c: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 9030A129BA3 for <ietf@ietf.org>; Mon, 26 Jun 2017 06:37:35 -0700 (PDT)
Received: by mail-vk0-x22e.google.com with SMTP id r126so881017vkg.0 for <ietf@ietf.org>; Mon, 26 Jun 2017 06:37:35 -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=uMmfDXX+GQRRHsSEilXlWx3l6NC3X6IIMG192ih7+vo=; b=UTwWPFdOr2o+Kh+qfSGZSm2CDP5VdgRMI4Jm1DUC7TYGmUU7QqxMvE9EA4G4Lr/uhj x5+NJHq90eJX+DAB8xSscbzc6GW+ds7CO1PWLMFmZLDOsIZkraZ5IJbMr/BjeBedQ4Y5 cD3KCBMk5QEXHaL2trEaj9qXM2uRAHR7JhMSxu8lvTg0hr2KyXKkHJ9KDI9dGeFdyOyp 5kc9iXzjEMefBWVdLu2Z+19xlcEvHk737dBYe8FUtLBdi5FXh3OCe4J1PWGknFbauYRY AhRChCbmIjU1Yt/3UPdZo0mIXN6mKdt6leWwFsTEqIfR/LkTz1/lBFSKRQzItHcQjgaJ OCgw==
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=uMmfDXX+GQRRHsSEilXlWx3l6NC3X6IIMG192ih7+vo=; b=HWs4Q3wyrXXmudJvvbWe1Hw7wfkNBT6oqXXijj/j7LWVPEN45MulDWdjjeZuYTefn4 DN6Z6McfUl258JKGafnSrIsaEe53vvwddUkW2LvvwNUBw8pqvNbsp5Q8hsg4VUF9mcIm HB/9vXm3igd6sekQE98GXCHi5b/XcyBupqPWymi5khKNHl7iFvQNLaYIzUH2XLSKgjbq Vw8J3dCt+TxDGoRpKwoG4m3y065VGnoLlD+2Al5tE7T2RoBK+Ar3FQoLDYIFN0cfw2je yHgBcxc55uOYqX15v2aZZ8sgK3+lncteOZdG/5HRx9cDwVX87hnNYu0NslAWoae9UG2Z HtNA==
X-Gm-Message-State: AKS2vOyNlaTuQzzUv4AYole3m6v1SUrHHElvHjJrOkHPZSh69nIVlvMd D+qmjsG/saZKgjAeHw57R6xj+6xM6Wal
X-Received: by 10.31.170.22 with SMTP id t22mr132429vke.100.1498484254403; Mon, 26 Jun 2017 06:37:34 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.167.150 with HTTP; Mon, 26 Jun 2017 06:37:13 -0700 (PDT)
In-Reply-To: <7C2A93A5-F01E-4474-AED3-D01FB9B2F34A@nokia.com>
References: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com> <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com> <7C2A93A5-F01E-4474-AED3-D01FB9B2F34A@nokia.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 26 Jun 2017 22:37:13 +0900
Message-ID: <CAKD1Yr34WEJrHoTLrpW6oBS7tT1TamjztK-a40oXyBkiAp+xEg@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: "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>
Cc: Brian E Carpenter <brian.e.carpenter@gmail.com>, "ietf@ietf.org" <ietf@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>,  "draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org" <draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org>,  "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="001a11415c3eaff5110552dd0d16"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/2Efn59IVdcB_yrzb3kRwBKn_T90>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 13:37:48 -0000

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

Please don't cite RFC 7608. It has nothing to do with IP addressing, only
forwarding, and the topic here is host addressing.

On Mon, Jun 26, 2017 at 9:12 PM, Van De Velde, Gunter (Nokia - BE/Antwerp) <
gunter.van_de_velde@nokia.com> wrote:

> Hi Brian,
>
> Thanks for the review.
>
> I modified the reference to /64 IPv6 prefix length and suggested instead
> consistency with RFC7608 and that currently this likely means a /64 in the
> -04 version.
>
> All the best,
> G/
>
> On 26/05/2017, 22:24, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> wrote:
>
>     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-ipv
> 6-prefix-per-host/
>     >
>     >  IESG discussion can be tracked via
>     > https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv
> 6-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 .
>     >
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

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

<div dir=3D"ltr">Please don&#39;t cite RFC 7608. It has nothing to do with =
IP addressing, only forwarding, and the topic here is host addressing.<div>=
<div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Mon, Jun 26, 2=
017 at 9:12 PM, Van De Velde, Gunter (Nokia - BE/Antwerp) <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:gunter.van_de_velde@nokia.com" target=3D"_blank">gun=
ter.van_de_velde@nokia.com</a><wbr>&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">Hi Brian,<br>
<br>
Thanks for the review.<br>
<br>
I modified the reference to /64 IPv6 prefix length and suggested instead<br=
>
consistency with RFC7608 and that currently this likely means a /64 in the =
-04 version.<br>
<br>
All the best,<br>
G/<br>
<div class=3D"m_-3210048783769125022HOEnZb"><div class=3D"m_-32100487837691=
25022h5"><br>
On 26/05/2017, 22:24, &quot;Brian E Carpenter&quot; &lt;<a href=3D"mailto:b=
rian.e.carpenter@gmail.com" target=3D"_blank">brian.e.carpenter@gmail.com</=
a>&gt; wrote:<br>
<br>
=C2=A0 =C2=A0 Hi,<br>
<br>
=C2=A0 =C2=A0 I should have noticed this during the v6ops discussions, but =
I didn&#39;t,<br>
=C2=A0 =C2=A0 sorry.<br>
<br>
=C2=A0 =C2=A0 This draft cites RFC4862 (SLAAC) and mentions Router Advertis=
ements<br>
=C2=A0 =C2=A0 (without also citing RFC4861, which is possibly a mistake). T=
hose<br>
=C2=A0 =C2=A0 documents do not specify the subnet prefix length. So the dra=
ft<br>
=C2=A0 =C2=A0 shouldn&#39;t assume a particular prefix length either. We al=
l know that<br>
=C2=A0 =C2=A0 it&#39;s usually 64 today, but that doesn&#39;t affect the ar=
gument made by<br>
=C2=A0 =C2=A0 the draft. We need consistency with RFC 7608 (BCP 198).<br>
<br>
=C2=A0 =C2=A0 Regards<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Brian Carpenter<br>
<br>
=C2=A0 =C2=A0 On 24/05/2017 07:41, The IESG wrote:<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; The IESG has received a request from the IPv6 Operations=
 WG (v6ops)<br>
=C2=A0 =C2=A0 &gt; to consider the following document: - &#39;Unique IPv6 P=
refix Per Host&#39;<br>
=C2=A0 =C2=A0 &gt; &lt;draft-ietf-v6ops-unique-ipv6-<wbr>prefix-per-host-03=
.txt&gt; as Best<br>
=C2=A0 =C2=A0 &gt; Current Practice<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; The IESG plans to make a decision in the next few weeks,=
 and<br>
=C2=A0 =C2=A0 &gt; solicits final comments on this action. Please send subs=
tantive<br>
=C2=A0 =C2=A0 &gt; comments to the <a href=3D"mailto:ietf@ietf.org" target=
=3D"_blank">ietf@ietf.org</a> mailing lists by 2017-06-06.<br>
=C2=A0 =C2=A0 &gt; Exceptionally, comments may be sent to <a href=3D"mailto=
:iesg@ietf.org" target=3D"_blank">iesg@ietf.org</a> instead. In<br>
=C2=A0 =C2=A0 &gt; either case, please retain the beginning of the Subject =
line to allow<br>
=C2=A0 =C2=A0 &gt; automated sorting.<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; Abstract<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; In some IPv6 environments, the need has arisen for hosts=
 to be able<br>
=C2=A0 =C2=A0 &gt; to utilize a unique IPv6 prefix, even though the link or=
 media may<br>
=C2=A0 =C2=A0 &gt; be shared.=C2=A0 Typically hosts (subscribers) on a shar=
ed network,<br>
=C2=A0 =C2=A0 &gt; either wired or wireless, such as Ethernet, WiFi, etc., =
will acquire<br>
=C2=A0 =C2=A0 &gt; unique IPv6 addresses from a common IPv6 prefix that is =
allocated or<br>
=C2=A0 =C2=A0 &gt; assigned for use on a specific link.<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; In most deployments today, IPv6 address assignment from =
a single<br>
=C2=A0 =C2=A0 &gt; IPv6 prefix on a shared network is done by either using =
IPv6<br>
=C2=A0 =C2=A0 &gt; stateless address auto-configuration (SLAAC) and/or stat=
eful DHCPv6.<br>
=C2=A0 =C2=A0 &gt; While this is still viable and operates as designed, the=
re are some<br>
=C2=A0 =C2=A0 &gt; large scale environments where this concept introduces s=
ignificant<br>
=C2=A0 =C2=A0 &gt; performance challenges and implications, specifically re=
lated to<br>
=C2=A0 =C2=A0 &gt; IPv6 router and neighbor discovery.<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; This document outlines an approach utilising existing IP=
v6 protocols<br>
=C2=A0 =C2=A0 &gt; to allow hosts to be assigned a unique IPv6 prefix (inst=
ead of a<br>
=C2=A0 =C2=A0 &gt; unique IPv6 address from a shared IPv6 prefix).=C2=A0 Be=
nefits of unique<br>
=C2=A0 =C2=A0 &gt; IPv6 prefix over a unique IPv6 address from the service =
provider<br>
=C2=A0 =C2=A0 &gt; include improved subscriber isolation and enhanced subsc=
riber<br>
=C2=A0 =C2=A0 &gt; management.<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; The file can be obtained via<br>
=C2=A0 =C2=A0 &gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-v=
6ops-unique-ipv6-prefix-per-host/" rel=3D"noreferrer" target=3D"_blank">htt=
ps://datatracker.ietf.org/d<wbr>oc/draft-ietf-v6ops-unique-ipv<wbr>6-prefix=
-per-host/</a><br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;=C2=A0 IESG discussion can be tracked via<br>
=C2=A0 =C2=A0 &gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-v=
6ops-unique-ipv6-prefix-per-host/ballot/" rel=3D"noreferrer" target=3D"_bla=
nk">https://datatracker.ietf.org/d<wbr>oc/draft-ietf-v6ops-unique-ipv<wbr>6=
-prefix-per-host/ballot/</a><br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; No IPR declarations have been submitted directly on this=
 I-D.<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; The document contains these normative downward reference=
s. See RFC<br>
=C2=A0 =C2=A0 &gt; 3967 for additional information: rfc6106: IPv6 Router Ad=
vertisement<br>
=C2=A0 =C2=A0 &gt; Options for DNS Configuration (Proposed Standard - IETF =
stream)<br>
=C2=A0 =C2=A0 &gt; rfc4941: Privacy Extensions for Stateless Address Autoco=
nfiguration<br>
=C2=A0 =C2=A0 &gt; in IPv6 (Draft Standard - IETF stream) rfc4862: IPv6 Sta=
teless<br>
=C2=A0 =C2=A0 &gt; Address Autoconfiguration (Draft Standard - IETF stream)=
 rfc3315:<br>
=C2=A0 =C2=A0 &gt; Dynamic Host Configuration Protocol for IPv6 (DHCPv6) (P=
roposed<br>
=C2=A0 =C2=A0 &gt; Standard - IETF stream)<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt;<br>
=C2=A0 =C2=A0 &gt; ______________________________<wbr>_________________ v6o=
ps mailing list<br>
=C2=A0 =C2=A0 &gt; <a href=3D"mailto:v6ops@ietf.org" target=3D"_blank">v6op=
s@ietf.org</a> <a href=3D"https://www.ietf.org/mailman/listinfo/v6ops" rel=
=3D"noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l<wbr>istinf=
o/v6ops</a> .<br>
=C2=A0 =C2=A0 &gt;<br>
<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>
</div></div></blockquote></div><br></div></div></div>

--001a11415c3eaff5110552dd0d16--


From nobody Mon Jun 26 08:14:17 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 1575F129B9B for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 08:14:16 -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 L4FL1LeX_Skr for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 08:14:14 -0700 (PDT)
Received: from mail-wm0-x234.google.com (mail-wm0-x234.google.com [IPv6:2a00:1450:400c: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 367EB129B47 for <ietf@ietf.org>; Mon, 26 Jun 2017 08:14:14 -0700 (PDT)
Received: by mail-wm0-x234.google.com with SMTP id i127so551647wma.0 for <ietf@ietf.org>; Mon, 26 Jun 2017 08:14:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:message-id:date:user-agent:mime-version :content-language; bh=h1JDYdoZuaRngNVNh/VDxb1Fz7nuGLchEA/zybY7RUQ=; b=jGjJ/bNWugO+dGJ6w2x0X5JrOzLYtFMhnsMgxn4WajMbYDhFr7D2SFa1JpMY9/oD46 IDoZcGzm7TxIdfXxwbWc8EPfUeJhERdcEZugdDeVs2XthpE2lkhO5Baqw1qwsLqXzvjH 57Y3+sej/mnxgdLTIRa0KMfHhlgg97eOan0ZyLb2eulYcrKLPqDV5+v6VQu3fFibeN/N f/Cybk7BjFXF+fwmh/RyF/zVZKL63KgxluOpnGFx1F6lu9U2gnlYQYu0oRlRF0tKcfVd 9PIyfRc+9mtZFHE2BWoXCIOmfq/sBG1eA96cjdemNzYUC+fZ4KsbeWC68z5tAT9nxywG LEgg==
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:message-id:date:user-agent :mime-version:content-language; bh=h1JDYdoZuaRngNVNh/VDxb1Fz7nuGLchEA/zybY7RUQ=; b=qyI5iCM1sB2h7RFTCsUrlfvSR5KlZkAr1+NUNzG0FLWamrW82VXplgXQX54kTRKg1B uk2Cgg73U/WaZMOq63O/Cjy3lRiDk8MLnOaIwH1CoGAJCHUUEEJh3wJ8R4ABJCfBQ0DS xLRoQHEBojbyramXKqPoeG++igcK1pJ9x/on/Vt5Y9TabCfYlZD0IIO+iOX/US6WG4Yv cta0O7aOrcZazeTZtwogeZuLlVJ9T2i9Nwi6p8kJgx7kwCCr+1v/0jMoB3MKdFV8gTEj D5l8a4VdOVHmzFY+xrAdbnDm/FVUOOhTt4O57K+2kRBK1wtmjXk6Y99RqahwgeE3ig/A PGhQ==
X-Gm-Message-State: AKS2vOw5p/vwVVK2AXpk+s0eg7o8bS9Vh89H9O/qtsMqenhzQW9gi0Rs uDfF142Fe0l83uHVM9k=
X-Received: by 10.28.167.207 with SMTP id q198mr60268wme.36.1498490052264; Mon, 26 Jun 2017 08:14:12 -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 y2sm423435wme.12.2017.06.26.08.14.11 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Jun 2017 08:14:11 -0700 (PDT)
From: Stewart Bryant <stewart.bryant@gmail.com>
To: IETF Discussion <ietf@ietf.org>
Subject: Which is the right "RFC2119" Boilerplate?
Message-ID: <a69ab951-ec0a-0c29-57aa-013f969db7be@gmail.com>
Date: Mon, 26 Jun 2017 16:14:05 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------65A79E0083AA5464265F4A10"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/n_4RGiC8wbaj0du2vEI8H6o_80A>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 15:14:16 -0000

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

  I diligently included in a draft the updated "RFC2119" boilerplate 
which includes the reference to RFC8174.

Nits then complains that it does not like the RFC2119 text (which is cut 
and paste from a very recent RFC).

So which is right, nits or the RFC Editor?

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

  == The document seems to lack the recommended RFC 2119 boilerplate, even if
      it appears to use RFC 2119 keywords -- however, there's a paragraph with
      a matching beginning. Boilerplate error?

      RFC 2119, paragraph 2:
         The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
         "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
         this document are to be interpreted as described in RFC 2119.

      ... text found in draft:
         The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
         "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY",
................................................^
         and "OPTIONAL" in this document are to be interpreted as
         described in BCP 14 [RFC2119] [RFC8174] when, and only when, they
         appear in all capitals, as shown here.


      (The document does seem to have the reference to RFC 2119 which the
      ID-Checklist requires).

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

- Stewart


--------------65A79E0083AA5464265F4A10
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> I diligently included in a draft the updated "RFC2119"
      boilerplate which includes the reference to RFC8174.</p>
    <p>Nits then complains that it does not like the RFC2119 text (which
      is cut and paste from a very recent RFC).</p>
    <p>So which is right, nits or the RFC Editor?<br>
    </p>
    <p>=================</p>
    <pre style="color: rgb(0, 0, 0); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial; word-wrap: break-word; white-space: pre-wrap;"> == The document seems to lack the recommended RFC 2119 boilerplate, even if
     it appears to use RFC 2119 keywords -- however, there's a paragraph with
     a matching beginning. Boilerplate error?

     RFC 2119, paragraph 2:
        The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
        this document are to be interpreted as described in RFC 2119.     

     ... text found in draft:
        The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY",
................................................^
        and "OPTIONAL" in this document are to be interpreted as
        described in BCP 14 [RFC2119] [RFC8174] when, and only when, they
        appear in all capitals, as shown here.


     (The document does seem to have the reference to RFC 2119 which the
     ID-Checklist requires).
</pre>
    =================<br>
    <p>- Stewart<br>
    </p>
  </body>
</html>

--------------65A79E0083AA5464265F4A10--


From nobody Mon Jun 26 08:24:30 2017
Return-Path: <alexandre.petrescu@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF99127077 for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 08:24:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.033
X-Spam-Level: 
X-Spam-Status: No, score=-1.033 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wDhrZ8fMfrdF for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 08:24:26 -0700 (PDT)
Received: from sainfoin-smtp-out.extra.cea.fr (sainfoin-smtp-out.extra.cea.fr [132.167.192.228]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EF14D12EAF3 for <ietf@ietf.org>; Mon, 26 Jun 2017 08:24:25 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v5QFONxN012842 for <ietf@ietf.org>; Mon, 26 Jun 2017 17:24:23 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id D4760205032 for <ietf@ietf.org>; Mon, 26 Jun 2017 17:24:23 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id CA5CE2052C8 for <ietf@ietf.org>; Mon, 26 Jun 2017 17:24:23 +0200 (CEST)
Received: from [10.8.34.184] (is227335.intra.cea.fr [10.8.34.184]) by muguet1.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v5QFONvw026204 for <ietf@ietf.org>; Mon, 26 Jun 2017 17:24:23 +0200
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
References: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com> <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com> <7C2A93A5-F01E-4474-AED3-D01FB9B2F34A@nokia.com> <CAKD1Yr34WEJrHoTLrpW6oBS7tT1TamjztK-a40oXyBkiAp+xEg@mail.gmail.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <4579755b-cb6e-539a-9923-936984f914ae@gmail.com>
Date: Mon, 26 Jun 2017 17:24:23 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr34WEJrHoTLrpW6oBS7tT1TamjztK-a40oXyBkiAp+xEg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Oxxo_f9A1pWFn5jSqMe14GnoRZ4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 15:24:29 -0000

Le 26/06/2017 à 15:37, Lorenzo Colitti a écrit :
> Please don't cite RFC 7608. It has nothing to do with IP addressing, 
> only forwarding, and the topic here is host addressing.

I disagree.  In networks there is no addressing without routing.

Alex

> 
> On Mon, Jun 26, 2017 at 9:12 PM, Van De Velde, Gunter (Nokia - 
> BE/Antwerp) <gunter.van_de_velde@nokia.com 
> <mailto:gunter.van_de_velde@nokia.com>> wrote:
> 
>     Hi Brian,
> 
>     Thanks for the review.
> 
>     I modified the reference to /64 IPv6 prefix length and suggested instead
>     consistency with RFC7608 and that currently this likely means a /64
>     in the -04 version.
> 
>     All the best,
>     G/
> 
>     On 26/05/2017, 22:24, "Brian E Carpenter"
>     <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>>
>     wrote:
> 
>          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 <mailto:ietf@ietf.org> mailing
>     lists by 2017-06-06.
>          > Exceptionally, comments may be sent to iesg@ietf.org
>     <mailto: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/
>     <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/
>     <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 <mailto:v6ops@ietf.org>
>     https://www.ietf.org/mailman/listinfo/v6ops
>     <https://www.ietf.org/mailman/listinfo/v6ops> .
>          >
> 
> 
>     _______________________________________________
>     v6ops mailing list
>     v6ops@ietf.org <mailto:v6ops@ietf.org>
>     https://www.ietf.org/mailman/listinfo/v6ops
>     <https://www.ietf.org/mailman/listinfo/v6ops>
> 
> 


From nobody Mon Jun 26 09:09:14 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 A0AC4129C29; Mon, 26 Jun 2017 09:09:12 -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, FREEMAIL_FROM=0.001, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id G6WI9WCJN9_R; Mon, 26 Jun 2017 09:09:10 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (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 4991312EA64; Mon, 26 Jun 2017 09:09:10 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.84.68]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MVJze-1dGCvL2omc-00Yiby; Mon, 26 Jun 2017 18:09:01 +0200
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
To: Yoav Weiss <yoav@yoav.ws>, Kazuho Oku <kazuhooku@gmail.com>
Cc: ietf@ietf.org, httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>, draft-ietf-httpbis-early-hints@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>, alexey.melnikov@isode.com, Mike West <mkwst@chromium.org>
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de> <CANatvzygaU9oiof3-5TqnWdxqXOGNyGqPvNhTnpPzYy391CzNw@mail.gmail.com> <632d93e7-eab5-dcbe-e971-64e3b27ddb4e@gmx.de> <CACj=BEjQQMRh-6de2J_tzF5o=EYvhZZ4_XQQ6DJiEq0wG0zW+g@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <3f4328be-beb7-49f8-0138-bcc570ea405a@gmx.de>
Date: Mon, 26 Jun 2017 18:08:57 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CACj=BEjQQMRh-6de2J_tzF5o=EYvhZZ4_XQQ6DJiEq0wG0zW+g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:THxg2oQWSvmHKIdS7t7CigVB3c6KVy+I2/05Yj4tRlm2goJN5W0 jh6NVymPgZUgkkUCIPMgDxDEohDdtQDKxzKAwMPST6Dcanr5AjzrozPkaf4NeGWY5PnLU7D VrVkN/X7SGnxyJIhXeViCTlz4fCOX0dQfshBvGwIyVUQLgVw5MdMOUETNejnWg12bokIN3W e4lhMebG3rMNbBobxosmw==
X-UI-Out-Filterresults: notjunk:1;V01:K0:V3DT2ira2aE=:NqGglhdKOknvSzgcg+H6gV 4FG2rAX88Y/eMZpDm0AZz8dbjoMp3O0UvyRioDGG7HUcigrHVxUUEYZxVEPkRVP2MCbAKX2HC 9NSLHVWuBeaezMgGVDgN84LzhdAs/EzXPuOypIBKZVgiqBaLHuUQqQNhetyYfNt2g72zt0uyI IBD4uF3QjKByC5AnBJLX2w/MGe6Kif8m6Kvb6WgZsgOwqrbXn+uN6gMS+ePu1scGkkCFnDw9T w8hojbNKhc9I1RHh5ZByUIxPsyGpnNH0oJxAE8SGcoHkaEv+8VbyXbjqOi7R6sSFu5o/Mg9fD 9a8fYhtaud8SUp/Ld9uX8w8wQxOsi12LkfOijNsL7GZ2QXdn1AquiBHVBfoJ8tRZaXcts/baF lNeMaENpDLxNlZ2/MVIRlC/Y+pMsI/nVUSNrw9m64RPooh+hDFJ+dsCRD3Ngu9R7REKy7JIcY VQ07lY5i8p/FF3ERsxSPqyGwqE5Y0ufyDEKWqNcJ4QWNNf0XscGZvq0hnkwvKRKIcvf1ffA8z Lm1hxx09QIN66HbZIfYSZSltcZVHG8eWb7Nx5OaiGyUEGjvDcFTw5t3rxoyVNk12vFs5FgRy1 ADRGaWRGrGSEgkEgcO8HPAqF7gKHRURhLs2/2+kOfgOK36YKTV+cOM01GfC3i3mEovasQu/K3 Lj2wIlw+6tF1Hz5/Cw02LFYSOs6WVIMb+sXRSnDVhAB9t/WJpCY1dwKoHtw3BV2dY/Y9JdaZS kP2JjQsfcPz/tqgNywpuHEtDLtgd53Pwln1vY5LtPpq68+x5J4c7TGc4oTf+aup2v0348AFJi p9KNBJw
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/oOO_-2mek61HODvZtuS2q-V6Glo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 16:09:13 -0000

On 2017-06-26 17:58, Yoav Weiss wrote:
> An issue <https://github.com/w3c/preload/issues/101> raised by Mike West 
> (CCed) got me thinking if Early Hints are at all implementable at the 
> browser level (rather than just used as early push hints at the CDN level).
> 
> Currently, at least in Chromium and WebKit, requests triggered by 
> preload links are not sent until the document is committed, which means 
> that they are not sent immediately when the browser processes them. 
> That's likely to be a short, internal delay.
> However, in the context of Early Hints, that delay can be significant, 
> as it can take hundreds of milliseconds for the renderer process to get 
> created. At the same time, a lot of the logic required to send those 
> requests out sits in the rendering engine.
> 
> I'm not sure what is the solution to bridge that gap, if one exists.
> 
> Cheers,
> Yoav

As the IETF HTTP WG, we can specify the bits on the wire that *allow* a 
client to start fetching things earlier.

*How* the client does that is an implementation detail of the client. If 
I understand the issue correctly, *any* mechanism that would send 
"early" information would have the same problem, right?

Best regards, Julian


From nobody Mon Jun 26 09:12:48 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 B829D127B60 for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 09:12:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Bcf_FfkyMYPI for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 09:12:45 -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 4964512EA58 for <ietf@ietf.org>; Mon, 26 Jun 2017 09:12:44 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.84.68]) by mail.gmx.com (mrgmx101 [212.227.17.168]) with ESMTPSA (Nemesis) id 0Ll0tl-1dzgvU1Bcj-00aitR; Mon, 26 Jun 2017 18:12:41 +0200
Subject: Re: Which is the right "RFC2119" Boilerplate?
To: Stewart Bryant <stewart.bryant@gmail.com>, IETF Discussion <ietf@ietf.org>
References: <a69ab951-ec0a-0c29-57aa-013f969db7be@gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <83ce36c5-3bfd-6d78-4ede-f8df3a9aa60c@gmx.de>
Date: Mon, 26 Jun 2017 18:12:39 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <a69ab951-ec0a-0c29-57aa-013f969db7be@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:QmnAJBrF9luM7bcTaCKgxnKIWH7KxHzKoRmPanngvlZBV846n2Y gffGJ4iysZjTvKzFCrpFY7dYaDLQYWAkpmXQW/g0s7gO4G9T/1FpVdXxt/tdW8OGT1Qh2/A mjInQScssfCOspKgaprMDfl++W38pDsElkk1hkFUmPKLWvEH6jUOC7MYSEtWjK76kHm7EBx HRGH55IpXot2zDeCa413g==
X-UI-Out-Filterresults: notjunk:1;V01:K0:9i9NgFbj3TE=:sRjc4DckmS3lnq1bQBUwyi WU/2m2bREp5/4tB1X0tGnFAVH9coXt8xYzUmED6TXuppHKwz7pcJ6QPK+n9+vDm7CMt1BmlNM 4kzQ/hwzFzhPOYTuhj6Hkfm61kmzuYuxPZH8WHhdA34S6kOSpwJuKVBsyH0KazKnbNmSChAmA c2L7Z48eaX0ASiXj4sOu4ZKrMIRQ3s5U7FbR7en5sWJSIW9BDepS7ChJ2PljRlKTwV1bHt05f +X/RwJHk/RqFu5oh+D1UOUAR9LVwhWATR+XicpVDWWEWbk9stEpEaX9iYheO+7gGRJxPxUdJe XZUIdJujQGxTyuemUlXvv7WfOPIhyUkh7Om3Q8NGNLbZ+IwjXUpaqYOmh/O/X4h9scINMx8jc 8zkwJAkpRc4CxTPTHG24EDPBWsWJI1RHxdODn7rF4LLckVxBD3rYDnwXUbM1xjMW+MpzCkpn3 HCwBxf67wDj0HGbQhbPdcuq8jRd+jAigDb72wDmnXAgPKf4G8H9V28bZS1LyKQmiV71KfxAi5 OQqTlOxbWoVTHDHCWgcMTk8lOfZYDSBrsFhsjuAdkVx423JtksNFKFgjhvigEonl80Kos0gkM //UGWKYwScLKKGAB1mvnMEMqUqcdZteYfJ7qOLgfBBLzlxZ3utdMXptyFjuWvpAJ2kCZvwd5G 9sWqjL5V+zM8bMsSABgKUg3PLEWd6JW+4/nVh+usKNMSgyRTidabHWrMXjX1eYg5QE5PwL72Y GNOp+IT8xD8eVU2uP0YGwRqnF4YeAraJ29vIR0rI0zqAX6O2Xfk3Ei5wr9TRX/R8CLRGUy2AS Dd/J4VP
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nC6GjjF8P7sUvXc1gBOKkejlQvc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 16:12:46 -0000

On 2017-06-26 17:14, Stewart Bryant wrote:
>   I diligently included in a draft the updated "RFC2119" boilerplate 
> which includes the reference to RFC8174.
> 
> Nits then complains that it does not like the RFC2119 text (which is cut 
> and paste from a very recent RFC).
> 
> So which is right, nits or the RFC Editor?
> ...

Seems that idnits needs an update.

Best regards, Julian

PS: would be good if it also accepted non-ASCII characters, at least 
optionally per opt-in...


From nobody Mon Jun 26 09:20: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 5B670129B38; Mon, 26 Jun 2017 09:20:44 -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@ietf.org>
Cc: 99all@ietf.org
Subject: Side Meeting Room Reservations at IETF 99
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: ietf@ietf.org
Message-ID: <149849404436.18380.5199059391438027713.idtracker@ietfa.amsl.com>
Date: Mon, 26 Jun 2017 09:20:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/7gtDm66kQ0BIy4LPAezxUtjBguo>
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, 26 Jun 2017 16:20:44 -0000

As announced on 2017-05-26 the IESG has decided to provide a meeting room at IETF 99 in Prague  in order to facilitate the scheduling of conversational side-meetings.  

The room is available for first-come first-served signup online. The meeting room will hold approximately 30 people and will be configured with a U-shaped table. This experiment will replace AD approval for rooms for side-meetings for potential new topics.

You can sign up for this room by visiting the IETF meeting wiki and navigating to Side Meetings via the Table of Contents. See https://www.ietf.org/registration/MeetingWiki/wiki/doku.php?id=ietf99. You will need to login to the wiki in order to reserve the room. If you’ve registered for an IETF meeting in the recent past, an account has been automatically created for you. If you have trouble logging into the wiki, you can choose to reset your password. 

Please include your name, email and a short description of the meeting when reserving the room, and please limit yourself to no more than a total of three hours during the IETF meeting week. 

Original email announcement of the experiment here: https://mailarchive.ietf.org/arch/msg/ietf/pf3iqgJIHsC0f984mBC1VE4-mBs.

The on-site signup FCFS room (seats about 16) will continue to be available at IETF 99.

Regards,
IETF Secretariat


From nobody Mon Jun 26 09:30:21 2017
Return-Path: <j.schoenwaelder@jacobs-university.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 E4B7312EB14; Mon, 26 Jun 2017 09:30:18 -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] 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 DwuIpwErIsLu; Mon, 26 Jun 2017 09:30:16 -0700 (PDT)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 468F212EAED; Mon, 26 Jun 2017 09:30:16 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id 6EDB1EDF; Mon, 26 Jun 2017 18:30:14 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.217]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id sHO9rLJA4RCi; Mon, 26 Jun 2017 18:30:13 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "Jacobs University CA - G01" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Mon, 26 Jun 2017 18:30:14 +0200 (CEST)
Received: from localhost (demetrius2.jacobs-university.de [212.201.44.47]) by hermes.jacobs-university.de (Postfix) with ESMTP id 4D40C2009F; Mon, 26 Jun 2017 18:30:14 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius2.jacobs-university.de [212.201.44.32]) (amavisd-new, port 10024) with ESMTP id WgYnZ_3zcLuT; Mon, 26 Jun 2017 18:30:14 +0200 (CEST)
Received: from elstar.local (elstar.jacobs.jacobs-university.de [10.50.231.133]) by hermes.jacobs-university.de (Postfix) with ESMTP id 03C122009B; Mon, 26 Jun 2017 18:30:13 +0200 (CEST)
Received: by elstar.local (Postfix, from userid 501) id 7E45B3FD2A1A; Mon, 26 Jun 2017 18:30:10 +0200 (CEST)
Date: Mon, 26 Jun 2017 18:30:10 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: Xufeng Liu <Xufeng_Liu@jabil.com>
Cc: Benoit Claise <bclaise@cisco.com>, Robert Wilton <rwilton@cisco.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "draft-ietf-teas-yang-te-topo.all@ietf.org" <draft-ietf-teas-yang-te-topo.all@ietf.org>
Subject: Re: [yang-doctors] [Teas] Yangdoctors last call review of draft-ietf-teas-yang-te-topo-08
Message-ID: <20170626163010.GA3341@elstar.local>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: Xufeng Liu <Xufeng_Liu@jabil.com>, Benoit Claise <bclaise@cisco.com>, Robert Wilton <rwilton@cisco.com>, Mahesh Jethanandani <mjethanandani@gmail.com>, "yang-doctors@ietf.org" <yang-doctors@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "teas@ietf.org" <teas@ietf.org>, "draft-ietf-teas-yang-te-topo.all@ietf.org" <draft-ietf-teas-yang-te-topo.all@ietf.org>
References: <149564066257.28529.12761629961042171907@ietfa.amsl.com> <BN3PR0201MB08670E55FFB5470F338E998DF1CD0@BN3PR0201MB0867.namprd02.prod.outlook.com> <5d4541d3-9426-787d-e02b-9c2dbc3a5400@cisco.com> <BN3PR0201MB0867315F3E88577B9EEF6584F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com> <3a1c319f-0255-b8ee-ecbd-739568c1dc7f@cisco.com> <1ab3a0d8-de3e-1d7c-2967-97b74b1c68a5@cisco.com> <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BN3PR0201MB0867664CBDA460C283DC8043F1DB0@BN3PR0201MB0867.namprd02.prod.outlook.com>
User-Agent: Mutt/1.6.0 (2016-04-01)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6Jn3aJvwMLmeZDhjRXTEiTiByJA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 16:30:19 -0000

On Thu, Jun 22, 2017 at 01:43:55PM +0000, Xufeng Liu wrote:

> [Xufeng] The I2RS topology model is already NMDA style, but the NMDA
> models are not immediately implementable without NETCONF/RESTCONF
> protocol update. We will need the "-state" module for the I2RS
> topology model (and for all the top-level models) for now. While the
> NMDA is nice, the NMDA discussions have already significantly
> delayed publishing new models, and doing NMDA without staging will
> further delay the process.

Can the config and state trees reasonably be different, i.e., do you
need to be able to distinguish intended config from applied config? If
not, I think you can implement NMDA today without waiting for
NETCONF/RESTCONF protocol updates.

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>


From nobody Mon Jun 26 09:40:53 2017
Return-Path: <rousskov@measurement-factory.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9376312EB0F; Mon, 26 Jun 2017 09:40:51 -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 r5jx7gOkXHNT; Mon, 26 Jun 2017 09:40:49 -0700 (PDT)
Received: from mail.measurement-factory.com (mail.measurement-factory.com [104.237.131.42]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA15412EB17; Mon, 26 Jun 2017 09:40:49 -0700 (PDT)
Received: from [65.102.233.169] (unknown [65.102.233.169]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.measurement-factory.com (Postfix) with ESMTPSA id 94B33E031; Mon, 26 Jun 2017 16:40:48 +0000 (UTC)
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: ietf@ietf.org, httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>, draft-ietf-httpbis-early-hints@ietf.org, HTTP Working Group <ietf-http-wg@w3.org>, alexey.melnikov@isode.com
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de> <CANatvzygaU9oiof3-5TqnWdxqXOGNyGqPvNhTnpPzYy391CzNw@mail.gmail.com> <632d93e7-eab5-dcbe-e971-64e3b27ddb4e@gmx.de>
From: Alex Rousskov <rousskov@measurement-factory.com>
Message-ID: <5a6b71b3-6e0b-4f3d-c7ef-9ee9ddd9f2bf@measurement-factory.com>
Date: Mon, 26 Jun 2017 10:40:48 -0600
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:52.0) Gecko/20100101 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <632d93e7-eab5-dcbe-e971-64e3b27ddb4e@gmx.de>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Ghn4HTwlS0_HiSneAagm-MUVFGA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 16:40:52 -0000

On 06/26/2017 04:36 AM, Julian Reschke wrote:
> On 2017-06-26 04:39, Kazuho Oku wrote:
>> 2017-06-25 19:11 GMT+09:00 Julian Reschke <julian.reschke@gmx.de>:
>>> On 2017-06-21 18:59, The IESG wrote:
>>>>     <draft-ietf-httpbis-early-hints-03.txt> as Experimental RFC


>>> For hop-by-hop, I'm not convinced that the requirement is needed here.

Prohibiting hop-by-hop fields is not only unneeded, it is harmful.


>> The reasons I added a clause prohibiting the use of hop-by-hop headers
>> in an 103 response are as follows:

>> * does not make sense for a response that attempts to send the
>> metadata of a final response early

Those hop-by-hop headers may have nothing to do with the 103 purpose
itself. They may make sense for authentication, tracking, logging, and
many other reasons specific to the deployment environment. As an extreme
example, consider a client that rejects all responses unless they have a
X-Hop-ID hop-by-hop header field. There is no reason to preclude such
client from using the new 103 feature!


>> * to avoid confusion caused by sending a hop-by-hop header in the 103
>> response

Adding unrelated restrictions creates even more confusion and bugs. Yes,
hop-by-hop headers can be misused, but early hints is not about
combating all world evils. A new protocol feature should not affect
standard behaviors unless such changes are absolutely necessary for that
feature functionality. If correct usage of some hop-by-hop headers does
not hurt early responses, then we should not prohibit all hop-by-hop
headers.


>> Without the restriction, a response like below would be valid, which
>> IMO is confusing at least.
>>
>> HTTP/1.1 103 Early Hints
>> Connection: close
>> Link: </style.css>; rel=preload
>>
>> HTTP/1.1 200 OK
>> Connection: close
>> Link: </style.css>; rel=preload

The same can be said about 100 Continue and other 1xx responses. The
early response feature is not the place to address this confusion.


>>>     An intermediary MAY drop the informational response. (...)
>>>
>>> That seems to contradict a MUST-level requirement in RFC 7231
>>> (https://www.greenbytes.de/tech/webdav/rfc7231.html#rfc.section.6.2.p.3)

>> The statement exists since sending 103 only makes sense when it is
>> impossible to immediately send a final response.

The "only" part of that assertion is too restrictive AFAICT. I can
imagine situations where sending 103 immediately before the final
response makes sense, especially when an intermediary is generating 103s
but does not want to fiddle with final responses.


>> Considering the facts, one way to resolve the issue would be to adjust
>> the statement to something like "An intermediary MAY omit the 103
>> response when resending a cached response", and argue that re-sending
>> a cached response is not an action of "forwarding," which is defined
>> as a MUST in RFC 7231.

> Sounds good to me.

When a caching intermediary attempts to validate a previously cached
object and suddenly receives a 103 response, the intermediary does not
yet know whether the cached object is still valid/fresh. Thus, if we
require the intermediary to base its 103 forwarding decision on the
cached object state, such an intermediary would have to store the 103
message until the final response is received. That new storage
requirement creates a significant burden for intermediaries!

IMHO, new 1xx messages should not introduce new storage/forwarding
requirements that depend on future final response status. An old caching
proxy should not violate the new 103 specs by default.

Perhaps the proxy-initiated cache validation transaction can be
considered a transaction between the proxy and the server, with no
"forwarding" involved? In that case, the 103 response is directed at the
proxy itself, and any forwarding rules do not apply! The proxy may, at
its own discretion, generate its own 103 response to the client, of
course. That generation may look like forwarding to an outside observer,
but it is not subject to forwarding requirements.


>> But wouldn't it be simpler to just have the "MAY drop" clause for any
>> intermediary?

> In that case, the spec would contradict RFC 7231, which is bad position
> to be in...

Agreed.


>>> The example suggests that early hints are repeated in the final
>>> response. Do they have to, actually?
>>
>> Yes. They need to, especially if caching is involved. 103 is an
>> intermediary response and there is no guarantee (or a requirement) for
>> a cache to retain the headers included only in the informational
>> response.
>>
>> In case of link rel=preload headers, a client can speculatively load
>> the resources included in the headers while revalidating a
>> stale-cached response, or a caching proxy can generate a 103 response
>> from a stale-cached 200 response, while waiting for the origin to
>> perform revalidation.

> What I'm after is a clear statement whether they really need to be
> repeated, as normative language.
 Based on the discussion, I think it should be the 103 sender decision,
not a protocol-level requirement. I can imagine cases where the final
response should omit some 103 details because the situation has changed
since that 103 was generated. The client should not be required to pay
attention to 103, and the server should not be required to duplicate 103
info.

>    A client MUST NOT interpret the 103 (Early Hints)
>    response header fields as if they applied to the informational
>    response itself

This requirement seems too broad -- a client that does not know about
103s may certainly apply the received 103 header fields to that 103
message. Yes, such a client would make an exception for Content-Length
and similar headers as already required for 1xx handling, but it seems
wrong to place _additional_ MUST-level requirements on an unsuspecting
client.


Overall, it feels like hints should be relayed using a mechanism that
does not abuse existing headers so that there is a clear separation
between the 103 message itself and the hints about the future message.
1xx responses cannot have a body, but perhaps these hints can be encoded
into a new header field? For example:

    HTTP/1.1 103 Hints
    Hints: <encoded Link and other fields here>
    Via: ...
    X-Hop-ID: ...
    Connection: X-Hop-ID


Thank you,

Alex.


From nobody Mon Jun 26 10:16:15 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 15D4C12EB0C; Mon, 26 Jun 2017 10:16:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 7L-oEZXtGeLI; Mon, 26 Jun 2017 10:16:12 -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 0BDB1129BC4; Mon, 26 Jun 2017 10:16:12 -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 boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v5QHFGGQ023397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 26 Jun 2017 10:15:18 -0700 (PDT)
Subject: Re: Tsvart early review of draft-ietf-trill-over-ip-10
To: Donald Eastlake <d3e3e3@gmail.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: tsv-art@ietf.org, draft-ietf-trill-over-ip.all@ietf.org, IETF Discussion <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
References: <149754795560.13109.17521244075940607817@ietfa.amsl.com> <CAF4+nEG-28weDot9R9Z4-05PX1tzBoKZSOHu8BJY2GiRzOv0nA@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <7cc18878-970a-efbe-8488-a4110b9b24e9@isi.edu>
Date: Mon, 26 Jun 2017 10:15:15 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <CAF4+nEG-28weDot9R9Z4-05PX1tzBoKZSOHu8BJY2GiRzOv0nA@mail.gmail.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/j_tYzRBx6ADTyEvX5852DzP8Izw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 17:16:14 -0000

Hi, Donald,


On 6/25/2017 5:07 PM, Donald Eastlake wrote:
> Hi Magnus,
>
> Thanks for the extensive review. See my responses below.
>
> On Thu, Jun 15, 2017 at 1:32 PM, Magnus Westerlund
> <magnus.westerlund@ericsson.com> wrote:
>> Reviewer: Magnus Westerlund
>> Review result: Not Ready
>>
>> Early review of draft-ietf-trill-over-ip-10
>> Reviewer: Magnus Westerlund
>> Review result: Not Ready
>>
>> TSV-ART review comments:
>>
>> I have set this to not ready as there are several issues, some significant that
>> could affect the protocol realization significantly. Some may be me missing
>> things in TRILL, I was not that familiar with it before this review and I have
>> only tried looking up things, not reading the whole earlier specifications. So
>> don't hesitate to push back and provide pointers to things that can resolve
>> issues. The authors and the WG clearly have thought about a lot of issues and
>> dealt with much already.
> OK. Hopefully we can resolve these one way or the other.
>
> ...
>> TCP Encapsulation issue
>> -----------------------
>>
>> Section 5.6:
>>
>> The TCP encapsulation appear to be missing an delimiter format allowing each
>> individual TRILL packet/payload to be read out of the TCP's byte stream. In
>> other words, a normal implementation has no way of ensuring that the TCP
>> payload starts with the start of a new TRILL payload. Multiple small TRILL
>> payloads may be included in the same TCP payload, and also only parts as TCP is
>> one way of dealing with TRILL packets that are larger than the IP+Encapsulation
>> MTU that actually will work.
>>
>> This comment is based on that there appear to be no length fields included in
>> the TRILL header. The most straight forward delimiter is a 2-byte length field
>> for the TRILL payload to be encapsulated.
> Right. It might also be useful to include some sort of check field, as
> is done in BGP, to detect if you are out of sync in parsing the TCP
> stream.

There is nothing in BGP that ever assumes that TCP write boundaries are
preserved. BGP uses markers and length fields to create message
boundaries in TCP's bytestream. The same is needed here.

Note that BGP also never claims to craft TCP packets by 'encapsulating'
a BGP message in a TCP segment. That part of this document needs to be
removed - it not how TCP is ever used.

> Another point is that, while with UDP it seems fine to send packets
> with assorted QoS, you don't want to encourage re-ordering of TCP
> packets in a stream. So if TCP encapsulation is being used,
Again - please, NO. NEVER use this term.

> you want
> to use the same DSCP value for the packets in a particular TCP stream.
Again, this is nonsensical. TCP would set a DSCP for the connection,
never in different ways for individual segments of a connection.


> So, generally, you need to have a TCP connection per priority handling
> category. Mapping the 8 priority levels into a smaller number of
> handling categories is a normal thing to do so you certainly don't
> necessarily need 8 TCP connections. Adding material on this should not
> be too hard.
Perhaps, but please - again, please - omit any mention or implication
that this occurs via encapsulation.

If you want to use TCP, please use it properly.

>
>> Section 5.6:
>>
>> TCP endpoint requirements. I do wonder if an application like TRILL actual
>> would need to discuss performance impacting implementation choices or
>> limitations. For example use of NAGLE, the requirements on buffer sizes in
>> relation to Bandwidth delay products, as buffer memory in a RBridge will impact
>> performance.
> Well, I'm not sure how deeply this document should get into such
> performance issues. What about just saying something about
> consideration being given to tuning TCP for performance and pointing
> to one or a few other RFCs that talk about this?
Because your use of TCP (even if changed to describe it correctly) isn't
listed in those TCP RFCs.

And it's not so simple - NAGLE helps performance for interactive systems
that use single-byte messages (e.g., telnet) and reduces the number of
outstanding "less than full" segments. When used for encapsulation,
turning NAGLE off is the right thing for multibyte messages (e.g., TRILL
messages) and can avoid the "gathering" delay (200 ms stalls when there
isn't enough source data - i.e., incoming TRILL packets - to keep up
with the outgoing segments), but could also generate a large number of
small segments (which can interfere with segment-based congestion
control, vs. ABC).

Unless you want a very poorly performing result, *THIS* is what you need
to drill down into.

Joe


From nobody Mon Jun 26 11:43:00 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 5E70E129B17; Mon, 26 Jun 2017 11:42:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 7MvGN6U9DXCD; Mon, 26 Jun 2017 11:42:52 -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 3A49E1270AC; Mon, 26 Jun 2017 11:42:52 -0700 (PDT)
Received: from [128.9.184.87] ([128.9.184.87]) (authenticated bits=0) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id v5QIgIg6009301 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 26 Jun 2017 11:42:18 -0700 (PDT)
Subject: Re: [trill] Tsvart early review of draft-ietf-trill-over-ip-10
From: Joe Touch <touch@isi.edu>
To: Donald Eastlake <d3e3e3@gmail.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: tsv-art@ietf.org, "trill@ietf.org" <trill@ietf.org>, IETF Discussion <ietf@ietf.org>, draft-ietf-trill-over-ip.all@ietf.org
References: <149754795560.13109.17521244075940607817@ietfa.amsl.com> <CAF4+nEG-28weDot9R9Z4-05PX1tzBoKZSOHu8BJY2GiRzOv0nA@mail.gmail.com> <7cc18878-970a-efbe-8488-a4110b9b24e9@isi.edu>
Message-ID: <c006414f-71d9-6a4b-eaa2-c0e38e87e0ee@isi.edu>
Date: Mon, 26 Jun 2017 11:42:16 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
In-Reply-To: <7cc18878-970a-efbe-8488-a4110b9b24e9@isi.edu>
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/S_8ytXNBYYfA2cH5SyetqzRQlM0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 18:42:54 -0000

PS - the idea that TCP segments within a single connection should ever
have different DSCPs is a good example of why it's a bad idea to even
'think' of TRILL over TCP as direct encapsulation. I.e., that concept is
inherently hazardous and should be avoided.

Joe


On 6/26/2017 10:15 AM, Joe Touch wrote:
> Hi, Donald,
>
>
> On 6/25/2017 5:07 PM, Donald Eastlake wrote:
>> Hi Magnus,
>>
>> Thanks for the extensive review. See my responses below.
>>
>> On Thu, Jun 15, 2017 at 1:32 PM, Magnus Westerlund
>> <magnus.westerlund@ericsson.com> wrote:
>>> Reviewer: Magnus Westerlund
>>> Review result: Not Ready
>>>
>>> Early review of draft-ietf-trill-over-ip-10
>>> Reviewer: Magnus Westerlund
>>> Review result: Not Ready
>>>
>>> TSV-ART review comments:
>>>
>>> I have set this to not ready as there are several issues, some significant that
>>> could affect the protocol realization significantly. Some may be me missing
>>> things in TRILL, I was not that familiar with it before this review and I have
>>> only tried looking up things, not reading the whole earlier specifications. So
>>> don't hesitate to push back and provide pointers to things that can resolve
>>> issues. The authors and the WG clearly have thought about a lot of issues and
>>> dealt with much already.
>> OK. Hopefully we can resolve these one way or the other.
>>
>> ...
>>> TCP Encapsulation issue
>>> -----------------------
>>>
>>> Section 5.6:
>>>
>>> The TCP encapsulation appear to be missing an delimiter format allowing each
>>> individual TRILL packet/payload to be read out of the TCP's byte stream. In
>>> other words, a normal implementation has no way of ensuring that the TCP
>>> payload starts with the start of a new TRILL payload. Multiple small TRILL
>>> payloads may be included in the same TCP payload, and also only parts as TCP is
>>> one way of dealing with TRILL packets that are larger than the IP+Encapsulation
>>> MTU that actually will work.
>>>
>>> This comment is based on that there appear to be no length fields included in
>>> the TRILL header. The most straight forward delimiter is a 2-byte length field
>>> for the TRILL payload to be encapsulated.
>> Right. It might also be useful to include some sort of check field, as
>> is done in BGP, to detect if you are out of sync in parsing the TCP
>> stream.
> There is nothing in BGP that ever assumes that TCP write boundaries are
> preserved. BGP uses markers and length fields to create message
> boundaries in TCP's bytestream. The same is needed here.
>
> Note that BGP also never claims to craft TCP packets by 'encapsulating'
> a BGP message in a TCP segment. That part of this document needs to be
> removed - it not how TCP is ever used.
>
>> Another point is that, while with UDP it seems fine to send packets
>> with assorted QoS, you don't want to encourage re-ordering of TCP
>> packets in a stream. So if TCP encapsulation is being used,
> Again - please, NO. NEVER use this term.
>
>> you want
>> to use the same DSCP value for the packets in a particular TCP stream.
> Again, this is nonsensical. TCP would set a DSCP for the connection,
> never in different ways for individual segments of a connection.
>
>
>> So, generally, you need to have a TCP connection per priority handling
>> category. Mapping the 8 priority levels into a smaller number of
>> handling categories is a normal thing to do so you certainly don't
>> necessarily need 8 TCP connections. Adding material on this should not
>> be too hard.
> Perhaps, but please - again, please - omit any mention or implication
> that this occurs via encapsulation.
>
> If you want to use TCP, please use it properly.
>
>>> Section 5.6:
>>>
>>> TCP endpoint requirements. I do wonder if an application like TRILL actual
>>> would need to discuss performance impacting implementation choices or
>>> limitations. For example use of NAGLE, the requirements on buffer sizes in
>>> relation to Bandwidth delay products, as buffer memory in a RBridge will impact
>>> performance.
>> Well, I'm not sure how deeply this document should get into such
>> performance issues. What about just saying something about
>> consideration being given to tuning TCP for performance and pointing
>> to one or a few other RFCs that talk about this?
> Because your use of TCP (even if changed to describe it correctly) isn't
> listed in those TCP RFCs.
>
> And it's not so simple - NAGLE helps performance for interactive systems
> that use single-byte messages (e.g., telnet) and reduces the number of
> outstanding "less than full" segments. When used for encapsulation,
> turning NAGLE off is the right thing for multibyte messages (e.g., TRILL
> messages) and can avoid the "gathering" delay (200 ms stalls when there
> isn't enough source data - i.e., incoming TRILL packets - to keep up
> with the outgoing segments), but could also generate a large number of
> small segments (which can interfere with segment-based congestion
> control, vs. ABC).
>
> Unless you want a very poorly performing result, *THIS* is what you need
> to drill down into.
>
> Joe
>
> _______________________________________________
> trill mailing list
> trill@ietf.org
> https://www.ietf.org/mailman/listinfo/trill


From nobody Mon Jun 26 12:04:27 2017
Return-Path: <David.Black@dell.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8C112EB4E; Mon, 26 Jun 2017 12:04:25 -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 (1024-bit key) header.d=dell.com header.b=AD7Fxyvr; dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=emc.com header.b=FF2f19Ti
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m4Op5HaFwkEn; Mon, 26 Jun 2017 12:04:21 -0700 (PDT)
Received: from esa7.dell-outbound.iphmx.com (esa7.dell-outbound.iphmx.com [68.232.153.96]) (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 7B24512EB49; Mon, 26 Jun 2017 12:04:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1498503366; x=1530039366; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=7bmGUcIENJgAQDkTWPpxmp8xiAPCp4TMP1NJbeM6UJc=; b=AD7Fxyvrh2yR3CukEi/prueBDU/aTOv7GDaNgsswj/K5/hJkdKHjMTjR NXeuMFxA4adPXt2GCj/zsUTG6qgz1idXJ3x6dfKOOtboQeWrHOcyex3d7 7O9mJWC9+5B5QtuY1UZqEt6zgI7ApD/hS7x/ulTE4qYwpwrVYPSmoWrc3 8=;
Received: from esa5.dell-outbound2.iphmx.com ([68.232.153.203]) by esa7.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jun 2017 13:56:05 -0500
From: "Black, David" <David.Black@dell.com>
Received: from mailuogwdur.emc.com ([128.221.224.79]) by esa5.dell-outbound2.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Jun 2017 00:58:23 +0600
Received: from maildlpprd56.lss.emc.com (maildlpprd56.lss.emc.com [10.106.48.160]) by mailuogwprd54.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v5QJ4Eha028332 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Jun 2017 15:04:16 -0400
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com v5QJ4Eha028332
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=emc.com; s=jan2013; t=1498503857; bh=/mK0Pk3Pm349kX4HfoBi5jS0hoQ=; h=From:To:CC:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=FF2f19Ti1xflbQL+i+1RtceV/iWfJ4WizRAgHxFtCVqjwA75/w30WkAF305E28D5M /KQ9WHRqXS57qlSSPo4pUtbGtrZbhjm/H8sPneSQG5zg2ri84sfk+F1mjd1oPQtbJs jEkSqRSHPsjFQuOpV1QYdmfPFqUK1NWYqSbTQQxY=
X-DKIM: OpenDKIM Filter v2.4.3 mailuogwprd54.lss.emc.com v5QJ4Eha028332
Received: from mailusrhubprd52.lss.emc.com (mailusrhubprd52.lss.emc.com [10.106.48.25]) by maildlpprd56.lss.emc.com (RSA Interceptor); Mon, 26 Jun 2017 15:03:47 -0400
Received: from MXHUB319.corp.emc.com (MXHUB319.corp.emc.com [10.146.3.97]) by mailusrhubprd52.lss.emc.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.0) with ESMTP id v5QJ41AM001658 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Mon, 26 Jun 2017 15:04:02 -0400
Received: from MX307CL04.corp.emc.com ([fe80::849f:5da2:11b:4385]) by MXHUB319.corp.emc.com ([10.146.3.97]) with mapi id 14.03.0352.000; Mon, 26 Jun 2017 15:04:01 -0400
To: Donald Eastlake <d3e3e3@gmail.com>, Magnus Westerlund <magnus.westerlund@ericsson.com>
CC: "tsv-art@ietf.org" <tsv-art@ietf.org>, "draft-ietf-trill-over-ip.all@ietf.org" <draft-ietf-trill-over-ip.all@ietf.org>, IETF Discussion <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Subject: RE: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-10 - ECN & DSCP considerations
Thread-Topic: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-10 - ECN & DSCP considerations
Thread-Index: AdLurvO3SYOqL32fRKuavuJggYEWYw==
Date: Mon, 26 Jun 2017 19:04:01 +0000
Message-ID: <CE03DB3D7B45C245BCA0D243277949362FB4DF88@MX307CL04.corp.emc.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.238.44.149]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Sentrion-Hostname: mailusrhubprd52.lss.emc.com
X-RSA-Classifications: public
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MXkdXp8X7XDk83pdaNb4iZ4K2dg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 19:04:25 -0000

Adding some comments on ECN and DSCP ...

> > Section 4.3:
> >
> >    TRILL over IP implementations MUST support setting the DSCP value in
> >    the outer IP Header of TRILL packets they send by mapping the TRILL
> >    priority and DEI to the DSCP. They MAY support, for a TRILL Data
> >    packet where the native frame payload is an IP packet, mapping the
> >    DSCP in this inner IP packet to the outer IP Header with the default
> >    for that mapping being to copy the DSCP without change.
> >
> > I think it is fine to require that implementations are capable of setti=
ng
> > DSCP values on the outer IP header. However, I fail to see any discussi=
on of
> > the potential issues with actually setting the DSCP values. It is one t=
hing to
> > do this in an IP back bone use case where one can know and have control
> > over the PHB that the DSCP values maps to. But otherwise, over general
> > internet the
> > behavior is not that predictable. One can easily be subject to policers=
 or
> > remapping. Also as the actual DSCP code point usage is domain specific =
this is
> > difficult. Priority reversal is likely the least of the problems that t=
his can
> > run into over general Internet.
>=20
> It sounds like appropriate discussion and warnings about these issues
> would resolve the above comment.

For ECN, see RFC 6040 and draft-ietf-tsvwg-rfc6040update-shim.  In particul=
ar,
copying the inner ECN codepoint to the outer IP header encapsulation withou=
t
requiring decapsulation processing as specified in RFC 6040 or the 6040upda=
te-shim
draft can lose congestion indications from the network and hence is wrong
(it's also wrong wrt RFC 3168, but RFC 6040 and the 6040update-shim drafts =
are
better and more current references).

For DSCPs, start with RFC 2983 - thinking about the validity (or likely val=
idity)
of the outer DSCP at the decapsulator may help in choosing whether to
recommend a uniform model (e.g., copy DSCP out at ingress, copy back in at
egress) or a pipe model (e.g., do something reasonable for outer DSCP at
ingress, ignore it on egress) as the implementation default.

-- DSCP mapping to/from TRILL/Ethernet priorities

> The intent in the draft is to reflect the default relative priority of
> the different priority code points in IEEE Std 802.1Q where priority 1
> is lower than priority 0. At a quick look, it appears to me that RFC
> 2474 requires that 0x001000 be handled as being of a priority not
> lower than the priority with which 0x000000 is handled. Yet RFC 3662,
> which you point to, seems to suggest using 0x001000 as a lower
> priority code point than 0x000000. Given that 3662 not only does not
> update 2474 but is only Informational while 2474 is Standards Track, I
> would say that 2474 dominates and that this draft makes the best
> assumptions it can about default behavior...

Well ... that's a discussion about text in RFCs that are well over a decade
old, and in an area (less-than-best-effort service) where the aspirations
of at least RFC 3662 weren't realized ... but that RFC is not safe to ignor=
e,
either.

In practice, the specification of CS1 for less-than-best-effort service has
been promulgated by RFC 4594 rather than RFC 3662, and RFC 4594 has
had significant "running code" impact on network design and operation.

As Magnus mentioned RFC7657, I strongly suggest starting from the
RFC 7657 discussion of this topic in order to figure out what to do.  I'm
not sure what to recommend, but I do think that starting from
RFC 7657 (rather than RFC 2474 and RFC 3662) is the better approach.

FWIW, the TSVWG WG is in the process of figuring out which DSCP
to recommend for less-than-best-effort-service in place of CS1 - that's
likely to be an active topic of discussion in Prague.=20

Thanks, --David

> -----Original Message-----
> From: Tsv-art [mailto:tsv-art-bounces@ietf.org] On Behalf Of Donald
> Eastlake
> Sent: Sunday, June 25, 2017 8:07 PM
> To: Magnus Westerlund <magnus.westerlund@ericsson.com>
> Cc: tsv-art@ietf.org; draft-ietf-trill-over-ip.all@ietf.org; IETF Discuss=
ion
> <ietf@ietf.org>; trill@ietf.org
> Subject: Re: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-10
>=20
> Hi Magnus,
>=20
> Thanks for the extensive review. See my responses below.
>=20
> On Thu, Jun 15, 2017 at 1:32 PM, Magnus Westerlund
> <magnus.westerlund@ericsson.com> wrote:
> >
> > Reviewer: Magnus Westerlund
> > Review result: Not Ready
> >
> > Early review of draft-ietf-trill-over-ip-10
> > Reviewer: Magnus Westerlund
> > Review result: Not Ready
> >
> > TSV-ART review comments:
> >
> > I have set this to not ready as there are several issues, some signific=
ant that
> > could affect the protocol realization significantly. Some may be me mis=
sing
> > things in TRILL, I was not that familiar with it before this review and=
 I have
> > only tried looking up things, not reading the whole earlier specificati=
ons. So
> > don't hesitate to push back and provide pointers to things that can res=
olve
> > issues. The authors and the WG clearly have thought about a lot of issu=
es
> and
> > dealt with much already.
>=20
> OK. Hopefully we can resolve these one way or the other.
>=20
> > Diffserv usage
> > --------------
> >
> > Section 4.3:
> >
> >    TRILL over IP implementations MUST support setting the DSCP value in
> >    the outer IP Header of TRILL packets they send by mapping the TRILL
> >    priority and DEI to the DSCP. They MAY support, for a TRILL Data
> >    packet where the native frame payload is an IP packet, mapping the
> >    DSCP in this inner IP packet to the outer IP Header with the default
> >    for that mapping being to copy the DSCP without change.
> >
> > I think it is fine to require that implementations are capable  of sett=
ing
> > DSCP values on the outer IP header. However, I fail to see any discussi=
on of
> > the potential issues with actually setting the DSCP values. It is one t=
hing to
> > do this in an IP back bone use case where one can know and have control
> over
> > the PHB that the DSCP values maps to. But otherwise, over general
> internet the
> > behavior is not that predictable. One can easily be subject to policers=
 or
> > remapping. Also as the actual DSCP code point usage is domain specific =
this
> is
> > difficult. Priority reversal is likely the least of the problems that t=
his can
> > run into over general Internet.
>=20
> It sounds like appropriate discussion and warnings about these issues
> would resolve the above comment.
>=20
> > Section 4.3:
> >
> >    The default TRILL priority and DEI to DSCP mapping, which may be
> >    configured per TRILL over IP port, is an follows. Note that the DEI
> >    value does not affect the default mapping and, to provide a
> >    potentially lower priority service than the default priority 0,
> >    priority 1 is considered lower priority than 0. So the priority
> >    sequence from lower to higher priority is 1, 0, 2, 3, 4, 5, 6, 7.
> >
> >       TRILL Priority  DEI  DSCP Field (Binary/decimal)
> >       --------------  ---  -----------------------------
> >                   0   0/1  001000 / 8
> >                   1   0/1  000000 / 0
> >                   2   0/1  010000 / 16
> >                   3   0/1  011000 / 24
> >                   4   0/1  100000 / 32
> >                   5   0/1  101000 / 40
> >                   6   0/1  110000 / 48
> >                   7   0/1  111000 / 56
> >
> > This appear to be an problematic mapping. At least for prio 0 and 1. As
> > priority 1 appears to be intended to be higher than priority 0, it is
> > interesting that it is mapped to CS1, which to quote
> > https://datatracker.ietf.org/doc/rfc7657/:
> >
> > CS1 ('001000') was subsequently designated as the recommended
> >       codepoint for the Lower Effort (LE) PHB [RFC3662].
> >
> > So what is proposed can in a network using default mapping, result in t=
hat
> you
> > get priority 0 to be lower priority than 1. Plus that in some networks =
this can
> > also results in strange remapping that results in a different PHB for C=
S1
> than.
>=20
> The intent in the draft is to reflect the default relative priority of
> the different priority code points in IEEE Std 802.1Q where priority 1
> is lower than priority 0. At a quick look, it appears to me that RFC
> 2474 requires that 0x001000 be handled as being of a priority not
> lower than the priority with which 0x000000 is handled. Yet RFC 3662,
> which you point to, seems to suggest using 0x001000 as a lower
> priority code point than 0x000000. Given that 3662 not only does not
> update 2474 but is only Informational while 2474 is Standards Track, I
> would say that 2474 dominates and that this draft makes the best
> assumptions it can about default behavior...
>=20
> > MTU and Fragmentation
> > ---------------------
> >
> > I think there are two main issue here. The first one is MTUD discovery
> > of the actual IP path MTU between the ports. That will be needed to
> prevent
> > a lot of traffic going into MTU black holes. Especially as TRILL requri=
es
> > 1470 byte support which is likey above a lot of paths.
>=20
> Seems like it would depend on the environments where TRILL was used.
> For example, I do not think 1470 would be a problem in most Data
> Center or Internet Exchange point uses, for example. Data Centers
> sometimes support 9K jumbo frames and the like.
>=20
> In fact, it is probably bad to focus too much on 1470 -- that is a
> required minimum to be sure that reasonable size link state PDUs can
> be successfully flooded through the TRILL campus so that routing will
> work. However, it would commonly be the case that, for the TRILL
> campus to be useful in a particular case, links need to be able to
> carry the expected size TRILL Data packets. For example, if there were
> two parts of a TRILL campus connected by one or a few TRILL over IP
> links and the end stations in each part were assuming they could use
> 1500 byte Ethernet packets, then the TRILL over IP links would need to
> support an MTU based on 1500 + TRILL Header + IP and TRILL over IP
> encapsulation. And more if security was being used or there were any
> other reasons for additional headers/encapsulation...
>=20
> > Section 8.4:
> >
> >    Path MTU discovery [RFC4821] should be useful
> >    in determining the IP MTU between a pair of RBridge ports with IP
> >    connectivity.
> >
> > The issue with RFC4821 is that it has requirements on the packetization
> layer.
> > Trill appears to have several components that are useful. However, it w=
ill
> > require a specification of the procedure to result in a useful tool.
>=20
> See below.
>=20
> > Section 8.4:
> >
> >    TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
> >    [RFC7177], can be used to obtain added assurance of the MTU of a
> >    link.
> >
> > Yes, that can confirm working MTUs that are at 1470 or above, but appea=
rs
> > prevented from working below 1470?
>=20
> While there is a minimum size for TRILL IS-IS MTU PDUs, determined by
> header size, it is well below 1470, probably (depending on whether
> secuirty is in use, etc.) below 150 bytes.
>=20
> > Thus, it appears that there is a lack of mechanism here to actually get=
 a valid
> > and functional MTU from TRILL in the cases where the Path MTU is below
> 1470. If
> > I am wrong good, but I think this is an important piece for how to hand=
le
> the
> > next main issue.
>=20
> How about referencing Section 3 of
> https://tools.ietf.org/html/draft-ietf-trill-mtu-negotiation-05
> which is currently in IETF Last Call? (The wording of that section is
> probably going to be improved based on an OPS review by Brian
> Carpenter.)
>=20
> > UDP encapsulation and IP fragments.
>   ----------------------------------
> > I see it as a big issue that UDP encapsulation is the native one, and t=
hat
> > relies on IP fragmentation despite the need for reliable fragmentation.
> With
> > the setup of having to support 1470 MTU on TRILL level some packets wil=
l
> be
> > fragmented in many environments. That will lead to a lot of losses, and=
 as
> > discussed below a very big problem with middleboxes. The main problem
> here is
> > that if one tries to rely on IP fragments one will have issues with pac=
kets
> > ending up in black holes. And different problems depending on IPv4 or
> IPv6.
> > IPv6 is lilkely the lesser problem assuming that one have working PMTUD=
.
> >
> > There are several ways out of this.
> >
> > 1. Detect issues and use TCP encapsulation with correctly set MSS to no=
t
> get IP
> > fragements 2. Determine MTU and implement an fragmentation
> mechanism on top of
> > UDP.
>=20
> So, I don't see that much problem with UDP being the general default
> consistent with the TRILL philosophy of defaulting to need zero or
> minimal configuration. The default should be to use multicast Hellos
> for discovery of neighbors which sure points at UDP to me. Having to
> traverse a NAT should be a rare case. Since, in the NAT case, you have
> to configure things related to the static binding and the IP
> address(es) of peer(s) anyway you can also configure to use a
> different encapsulation than UDP, such as TCP, at the same time. I
> don't see it as much of a problem if, by default, TRILL won't operate
> through a NAT. If you are using UDP and it fragments and fragments are
> dropped at a NAT, probably you can't exchange Hellos so you will not
> form an adjacency and anything on the other side of the NAT will not
> be visible.
>=20
> > Zero Checksum:
> > --------------
> >
> > Section 5.4:
> >
> > UDP Checksum - as specified in [RFC0768]
> >
> > Considering the fast path encapsulation desire, I am surprised to not s=
ee
> any
> > mentioning of use of zero checksum here. Raising the zero checksum and
> forward
> > reference would be good I think.
> >
> > And then Section 8.5:
> >
> >    The requirements for the usage of the zero UDP Checksum in a UDP
> >    tunnel protocol are detailed in [RFC6936]. These requirements apply
> >    to the UDP based TRILL over IP encapsulations specified herein
> >    (native and VXLAN), which are applications of UDP tunnel.
> >
> > If you actually intended to allow zero checksum, then you actually shou=
ld
> > document that Trill fulfills the requirements that the applicability st=
atement
> > raises. I have not analyzed how well it meets these requirements.
> >
> > Please review Section 6.2 of RFC 8086 for example how that can be done.
>=20
> OK. We'll look into it.
>=20
> > TCP Encapsulation issue
> > -----------------------
> >
> > Section 5.6:
> >
> > The TCP encapsulation appear to be missing an delimiter format allowing
> each
> > individual TRILL packet/payload to be read out of the TCP's byte stream=
. In
> > other words, a normal implementation has no way of ensuring that the TC=
P
> > payload starts with the start of a new TRILL payload. Multiple small TR=
ILL
> > payloads may be included in the same TCP payload, and also only parts a=
s
> TCP is
> > one way of dealing with TRILL packets that are larger than the
> IP+Encapsulation
> > MTU that actually will work.
> >
> > This comment is based on that there appear to be no length fields inclu=
ded
> in
> > the TRILL header. The most straight forward delimiter is a 2-byte lengt=
h
> field
> > for the TRILL payload to be encapsulated.
>=20
> Right. It might also be useful to include some sort of check field, as
> is done in BGP, to detect if you are out of sync in parsing the TCP
> stream.
>=20
> Another point is that, while with UDP it seems fine to send packets
> with assorted QoS, you don't want to encourage re-ordering of TCP
> packets in a stream. So if TCP encapsulation is being used, you want
> to use the same DSCP value for the packets in a particular TCP stream.
> So, generally, you need to have a TCP connection per priority handling
> category. Mapping the 8 priority levels into a smaller number of
> handling categories is a normal thing to do so you certainly don't
> necessarily need 8 TCP connections. Adding material on this should not
> be too hard.
>=20
> > Section 5.6:
> >
> > TCP endpoint requirements. I do wonder if an application like TRILL act=
ual
> > would need to discuss performance impacting implementation choices or
> > limitations. For example use of NAGLE, the requirements on buffer sizes=
 in
> > relation to Bandwidth delay products, as buffer memory in a RBridge wil=
l
> impact
> > performance.
>=20
> Well, I'm not sure how deeply this document should get into such
> performance issues. What about just saying something about
> consideration being given to tuning TCP for performance and pointing
> to one or a few other RFCs that talk about this?
>=20
> > Congestion Control
> > ------------------
> > First thanks for the effort here.
>=20
> You're welcome.
>=20
> > 8.1.2 In Other Environments
> >
> >    Where UDP based encapsulation headers are used in TRILL over IP in
> >    environments other than those discussed in Section 8.1.1, specific
> >    congestion control mechanisms are commonly needed.  However, if the
> >    traffic being carried by the TRILL over IP link is already congestio=
n
> >    controlled and the size and volatility of the TRILL IS-IS link state
> >    database is limited, then specific congestion control may not be
> >    needed. See [RFC8085] Section 3.1.11 for further guidance.
> >
> > This is correct, however my question is if the RBridges have any way of
> knowing
> > which traffic is actually congestion controlled, considering that TRILL
> provides
> > an layer 2 abstraction. I wonder if there should be any type of white l=
ist of
> > the types of layer 2 payloads that can be assumed to be congestion
> controlled,
> > and thus okay to forward over IP paths? I am worried that without any
> > recommendation to prevent traffic that is not controlled to be forwarde=
d,
> can
> > lead to congestion issues.
> >
> > The other issue I think may exist is the issue serial unicast emulation=
 of
> > broadcast/multicast creates. As this amplifies the outgoing packet rate=
 with
> > a factor of how many addresses are configured for serial unicast this c=
an
> > be significant traffic expansion. Thus, I think additional consideratio=
ns are
> > needed here, and maybe rate limiting of the amount of traffic to be
> multicasted.
>=20
> OK. We can think about those issues.
>=20
> > Flow and ECMP
> > -------------
> >
> > Section 8.3:
> >
> > For example, for TRILL
> >    Data, this entropy field could be based on some hash of the
> >    Inner.MacDA, Inner.MacSA, and Inner.VLAN or Inner.FGL.
> >
> > I would appreciate clearer references to what these fields are.
>=20
> In a TRILL Data packet, the payload after the TRILL Header looks like
> an Ethernet frame except that there is always either a VLAN tag or,
> alternatively, where the VLAN tag would be, a Fine Grained Label
> [RFC7172]. (The preceding is the view in the TRILL RFCs, but there is
> an equivalent and equally valid view in which all the fields through
> and including the VLAN or FGL tag are part of the TRILL Header.) The
> TRILL base protocol specification focuses on Ethernet as a link
> technology between TRILL switches, in which case there will be a link
> header including an Outer.MacDA and Outer.MacSA fields and possibly an
> Outer.VLAN, all before the TRILL Header. See Figure 1 and Figure 2 in
> RFC 7172.
>=20
> Some of the above could be added to the draft for clarity.
>=20
> > If I understand this correctly, the idea here is to look into the inner
> > layer 2 frames, and use the flow equivalents that exists on that level =
and
> > hash that into value that maps the flows onto the source port range.
>=20
> Yes.
>=20
> > I think this text should include a summary of the principle and ensure =
to
> > note the important requirement that what is considered flows in the inn=
er
> > must not result in being striped over multiple source ports as this may=
 lead
> to
> > reordering issues due to packets taking different paths.
>=20
> Well, we can add some text. But when would the relative ordering
> matter for two TRILL Data packets where the two inner native payloads
> have different values for any one or more of these three fields
> (Inner.MacDA, Inner.MacSA, and inner VLAN/FGL tag) ? If any of those
> fields are different, you are talking about different streams.
>=20
> > NAT and TRILL over IP:
> > Section 8.5:
> >
> > If one like to use TRILL over IP through a NAT, then there are some ver=
y
> > important considerations that are missing. First the need for static bi=
nding
> > configurations or the need for determining ones external address(es) an=
d
> be
> > able to communicate that to the peer RBridges, and in addition ensure t=
hat
> one
> > has keep-alives to that the NAT binding never times out.
>=20
> I think those are good points. There is an additional problem that
> TRILL Hellos detect neighbors with which they have 2-way connectivity
> by indicating, inside the Hellos that are sent, from what neighbors
> Hellos have been received on that port. If a NAT is involved, these
> neighbor addresses inside Hellos need to be mapped.
>=20
> > Next is the issue that there is almost zero chance of getting a IP/UDP
> > encapsulation TRILL payload through the NAT if it results in IP
> fragmentation,
> > as NATs don't do defragment and refragmented on the internal side, and
> an IP
> > fragment lacks UDP port and thus can't be matched to binding.
>=20
> So perhaps the recommendation should be to configure the port to use
> TCP if there will be fragmentation.
>=20
> > Also if you like to run IP/ESP through a NAT, then you most likely need=
 the
> > IP/UDP/ESP encapsulation (https://tools.ietf.org/html/rfc3948). Note th=
at
> this
> > will restrict the MTU even further and thus ensure that the 1470
> requirement
> > cannot be fulfilled even without additional tunnels over an 1500 bytes =
MTU
> > Ethernet infrastructure.
> >
> > I would note that also firewalls likely have issues with IP fragments f=
or the
> > same reason, they require significant amount of state to be verified if=
 they
> > should be let through.
> >
> > In general I think you should create a configuration that has chance to=
 work
> > through most middleboxes, but I think you should require static binding=
s. I
> > think that configuration is, and don't laugh now, but
> IP/UDP/ESP/TCP/TRILL,
> > otherwise you will not be able to have both security and reliable
> fragmentation
> > of TRILL packets.
>=20
> OK. Thanks again for this review. It has pointed out a number of
> problems and in thinking about those, I believe a couple of further
> problems have come to mind that I mentioned above. We'll work on a
> revised draft.
>=20
> Thanks,
> Donald
> =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
>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>  155 Beaver Street, Milford, MA 01757 USA
>  d3e3e3@gmail.com
>=20
> > Cheers
> >
> > Magnus Westerlund
>=20
> _______________________________________________
> Tsv-art mailing list
> Tsv-art@ietf.org
> https://www.ietf.org/mailman/listinfo/tsv-art


From nobody Mon Jun 26 13:08:37 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 548B812EB2F for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 13:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] 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 w1eFnUNCHNbW for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 13:08:34 -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 238B312EACF for <ietf@ietf.org>; Mon, 26 Jun 2017 13:08:34 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v5QK7oQM017080 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 26 Jun 2017 13:07:51 -0700 (PDT)
Subject: Re: I-D Action: draft-thomson-postel-was-wrong-01.txt
To: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>, =?UTF-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, "ietf@ietf.org" <ietf@ietf.org>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu> <8e8d4db9-93fd-5092-68de-6d8de44151c3@nic.cz> <c9202a09-af8b-faf6-b583-694378022dae@isi.edu> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636B715@GLKXM0003v.GREENLNK.net> <d0c4ecc7-1fe9-fc0b-bbe5-8cffb956b6ed@isi.edu> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636DCC9@GLKXM0003v.GREENLNK.net>
From: Joe Touch <touch@isi.edu>
Message-ID: <8a5e69f8-37f5-516f-172e-696a891e674f@isi.edu>
Date: Mon, 26 Jun 2017 13:07:50 -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: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636DCC9@GLKXM0003v.GREENLNK.net>
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/jxl3-DRWA4Uogr-qB9aR7Ti-z00>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 20:08:35 -0000

On 6/26/2017 1:52 AM, Dearlove, Christopher (UK) wrote:
> Explicitly reject vs silently ignore. I took the latter to be a an instance of the latter
I'm guessing you meant "I took the former as an instance of the latter".
> , because I meant explicit in terms of the specification, not the implementation. Wording could obviously have been better. I could see rejection being noisy, silent or somewhere in between.

I was working off your term "reject" - which is IMO quite different from
"ignore" (more than the difference between "explicitly" and "silently".

Reject usually means some other action is taken, e.g., requiring an
alert to the user, a change in the protocol state, or a response
protocol message.

Joe



From nobody Mon Jun 26 13:52:27 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 41C5112EB67; Mon, 26 Jun 2017 13:52: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 Ghsr3G_akiiQ; Mon, 26 Jun 2017 13:52:23 -0700 (PDT)
Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB60912EB73; Mon, 26 Jun 2017 13:52:23 -0700 (PDT)
Received: by mail-pg0-x22e.google.com with SMTP id u62so5422842pgb.3; Mon, 26 Jun 2017 13:52:23 -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=cFv15AefSQef1cHUPzQVWCl7whrhKwIyXgaUawiMxPE=; b=ieGZ+RxKPXg55BW7AU9ambu6KMntRiLqwAR0EFw/L/nKvORShMU1Cj0d0WV5SEGQzX oTFvsZTTAxnmsyZ8AtGU/eLS24DfiCwaAKDoGAzXn4TeOjeUDU8uG05P9UiaFGLKKwvR Tiu2IdNlyl4CwmEhlsSixD3IXeX6fJfl3V+ZhwYUDNBZRObFFugLaPLe82JAsk2/NKw1 pdK8lIsdehqlpWy1qoAROFp7JPTb3NrjEIiWitlDJzRCxobXPT7SW84fodZeSGDxo54v E+KzCzNm47kzQryEk3ihuscGrVuULcV73lib3MRQxjXvfiLDtXCwUFfMg8R8D8h5s9io wfHw==
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=cFv15AefSQef1cHUPzQVWCl7whrhKwIyXgaUawiMxPE=; b=qU14JRyeJ+qLqtu1dZNcZEhZamF7CGGYvvh9cGz65eI5Qke8Gn2dsm6BIv4+ZUZTs/ 07G2ApssG1ipCX9OKFHLhzH67CdhFmPheWWSXNENVB8fPFfUpQSGJebCQh8gGoEKBHp6 kXBgB8oApMzGtrlLTqCsU/AIV4XIQ80pWucYiNigHqQbjQdFxkdz5r9tIfvWalaHxB00 FFjAwpKDDxvsJXY+CNzmO+d9tqvnMD+aRVwdugPSFNKPaKEpJlPappV3bGv+ls3URA5b OepadbNtkrh3f5PFKliUxVDsd0e9MxW8HL4h2G0/4/Vf9LdrxZDPEitmvvDmAf7cYZV8 aaZA==
X-Gm-Message-State: AKS2vOysuealy6PgBlRkvzPcTOm9WJTk037cN0yT60BAKEU806Ieiw2s ez3fR8Ox4o/A38hL
X-Received: by 10.84.129.111 with SMTP id 102mr2085781plb.221.1498510343294; Mon, 26 Jun 2017 13:52:23 -0700 (PDT)
Received: from [192.168.178.21] (28.216.69.111.dynamic.snap.net.nz. [111.69.216.28]) by smtp.gmail.com with ESMTPSA id 66sm1641797pgh.59.2017.06.26.13.52.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Jun 2017 13:52:22 -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: Lorenzo Colitti <lorenzo@google.com>, "Van De Velde, Gunter (Nokia - BE/Antwerp)" <gunter.van_de_velde@nokia.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org" <draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org>, "v6ops-chairs@ietf.org" <v6ops-chairs@ietf.org>
References: <149556850339.28443.2716896366216678645.idtracker@ietfa.amsl.com> <fa82ceef-7cd6-ab37-aee6-f386266b5c56@gmail.com> <7C2A93A5-F01E-4474-AED3-D01FB9B2F34A@nokia.com> <CAKD1Yr34WEJrHoTLrpW6oBS7tT1TamjztK-a40oXyBkiAp+xEg@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <6c7cf450-d48e-94f4-f705-e24e83d52a44@gmail.com>
Date: Tue, 27 Jun 2017 08:52:22 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAKD1Yr34WEJrHoTLrpW6oBS7tT1TamjztK-a40oXyBkiAp+xEg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nY5hYwqpnzPcUZsxn9p5iHYPDiM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 20:52:26 -0000

On 27/06/2017 01:37, Lorenzo Colitti wrote:
> Please don't cite RFC 7608. It has nothing to do with IP addressing, only
> forwarding, and the topic here is host addressing.

True. I agree that simply stating that it's currently /64 is appropriate.
The point is that /64 isn't an essential property of this solution; it's
an externally determined parameter.

   Brian

> 
> On Mon, Jun 26, 2017 at 9:12 PM, Van De Velde, Gunter (Nokia - BE/Antwerp) <
> gunter.van_de_velde@nokia.com> wrote:
> 
>> Hi Brian,
>>
>> Thanks for the review.
>>
>> I modified the reference to /64 IPv6 prefix length and suggested instead
>> consistency with RFC7608 and that currently this likely means a /64 in the
>> -04 version.
>>
>> All the best,
>> G/
>>
>> On 26/05/2017, 22:24, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
>> wrote:
>>
>>     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-ipv
>> 6-prefix-per-host/
>>     >
>>     >  IESG discussion can be tracked via
>>     > https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv
>> 6-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 .
>>     >
>>
>>
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>>
> 


From nobody Mon Jun 26 15:53:52 2017
Return-Path: <linda.dunbar@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 1FFCD127201; Mon, 26 Jun 2017 15:53:44 -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 A3nZshSfs_qL; Mon, 26 Jun 2017 15:53:42 -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 7231E126E3A; Mon, 26 Jun 2017 15:53:41 -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 DPW51535; Mon, 26 Jun 2017 22:53:40 +0000 (GMT)
Received: from SJCEML701-CHM.china.huawei.com (10.208.112.40) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 26 Jun 2017 23:53:39 +0100
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.142]) by SJCEML701-CHM.china.huawei.com ([169.254.3.186]) with mapi id 14.03.0301.000;  Mon, 26 Jun 2017 15:53:35 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-precis-7613bis@ietf.org" <draft-ietf-precis-7613bis@ietf.org>
Subject: Gen-art last call review of draft-ietf-precis-7613bis-07
Thread-Topic: Gen-art last call review of draft-ietf-precis-7613bis-07
Thread-Index: AdLuzwlSicte5jFwS92cRaxDldpIjA==
Date: Mon, 26 Jun 2017 22:53:35 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F6593D94F9@SJCEML702-CHM.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.138]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F6593D94F9SJCEML702CHMchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020202.59519074.0054, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.142, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 02e33ca69ad4a5f62776656187baf710
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/nrAZqyE-kqmin58kDgyVPo-lN9c>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 22:53:44 -0000

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


Reviewer: Linda Dunbar
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 t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments.

For more information, please see the FAQ at

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

Document: draft-ietf-precis-7613bis
Reviewer: Linda Dunbar
Review Date: 2017-06-25
IETF LC End Date: 2017-06-27
IESG Telechat date: 2017-07-06

Summary:
The document is written very clear. Even for a person who is not familiar w=
ith the App area, I can follow through the description. The document is rea=
dy for publication as standard track document Major issues:

One Minor issue:

Page 6 last paragraph has:
      SASL mechanisms SHOULD delay any case mapping to the last possible mo=
ment, such as when doing a lookup by username, performing username comparis=
ons, or generating a cryptographic salt from a username (if the last possib=
le moment happens on the server, then decisions about case mapping can be a=
 matter of deployment policy). In keeping with [RFC4422], SASL mechanisms a=
re not to apply this or any other profile to authorization identifiers, onl=
y to authentication identifiers.

What does "last possible moment" mean? When I read it, I thought it meant w=
ait until you got all the characters. But the next  sentence mentions "..ha=
ppens on the server". How is the "server" related to the entity that check =
the user name & password?

Best Regards,

Linda Dunbar




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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left:=
 #800000 2px solid; } --></style>
</head>
<body>
<font face=3D"Times New Roman" size=3D"2"><span style=3D"font-size:11pt;">
<div>&nbsp;</div>
<div><font face=3D"Calibri">Reviewer: Linda Dunbar</font></div>
<div><font face=3D"Calibri">Review result: Ready</font></div>
<div><font face=3D"Calibri">&nbsp;</font></div>
<div><font face=3D"Calibri">I am the assigned Gen-ART reviewer for this dra=
ft. The General Area Review Team (Gen-ART) reviews all IETF documents being=
 processed by the IESG for the IETF Chair.&nbsp; Please treat these comment=
s just like any other last call comments.</font></div>
<div><font face=3D"Calibri">&nbsp;</font></div>
<div><font face=3D"Calibri">For more information, please see the FAQ at</fo=
nt></div>
<div><font face=3D"Calibri">&nbsp;</font></div>
<div><font face=3D"Calibri">&lt;<a href=3D"https://trac.ietf.org/trac/gen/w=
iki/GenArtfaq">https://trac.ietf.org/trac/gen/wiki/GenArtfaq</a>&gt;.</font=
></div>
<div><font face=3D"Calibri">&nbsp;</font></div>
<div><font face=3D"Calibri">Document: draft-ietf-precis-7613bis</font></div=
>
<div><font face=3D"Calibri">Reviewer: Linda Dunbar</font></div>
<div><font face=3D"Calibri">Review Date: 2017-06-25</font></div>
<div><font face=3D"Calibri">IETF LC End Date: 2017-06-27</font></div>
<div><font face=3D"Calibri">IESG Telechat date: 2017-07-06</font></div>
<div>&nbsp;</div>
<div><font face=3D"Calibri">Summary:</font></div>
<div><font face=3D"Calibri">The document is written very clear. Even for a =
person who is not familiar with the App area, I can follow through the desc=
ription. The document is ready for publication as standard track document M=
ajor issues:</font></div>
<div><font face=3D"Calibri">&nbsp;</font></div>
<div><font face=3D"Calibri">One Minor issue:</font></div>
<div><font face=3D"Calibri">&nbsp;</font></div>
<div><font face=3D"Calibri">Page 6 last paragraph has: </font></div>
<div style=3D"padding-left:36pt;"><font face=3D"Calibri"><i>SASL mechanisms=
 SHOULD delay any case</i><i> </i><i>mapping to the last possible moment, s=
uch as when doing a lookup</i><i> </i><i>by username, performing username c=
omparisons, or generating a</i><i> </i><i>cryptographic
salt from a username (if the last possible moment</i><i> </i><i>happens on =
the server, then decisions about case mapping can be a</i><i> </i><i>matter=
 of deployment policy). In keeping with [RFC4422], SASL</i><i> </i><i>mecha=
nisms are not to apply this or any
other profile to</i><i> </i><i>authorization identifiers, only to authentic=
ation identifiers.</i></font></div>
<div>&nbsp;</div>
<div><font face=3D"Calibri">What does &quot;last possible moment&quot; mean=
? When I read it, I thought it meant wait until you got all the characters.=
 But the next  sentence mentions &quot;..happens on the server&quot;. How i=
s the &quot;server&quot; related to the entity that check the user
name &amp; password? </font></div>
<div><font face=3D"Calibri">&nbsp;</font></div>
<div><font face=3D"Calibri">Best Regards, </font></div>
<div>&nbsp;</div>
<div><font face=3D"Calibri">Linda Dunbar</font></div>
<div>&nbsp;</div>
<div>&nbsp;</div>
<div>&nbsp;</div>
</span></font>
</body>
</html>

--_000_4A95BA014132FF49AE685FAB4B9F17F6593D94F9SJCEML702CHMchi_--


From nobody Mon Jun 26 16:48:47 2017
Return-Path: <peter@filament.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8730312EB7D for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 16:48:39 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=filament-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 4rOGwuvvPEV9 for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 16:48:36 -0700 (PDT)
Received: from mail-it0-x22e.google.com (mail-it0-x22e.google.com [IPv6:2607:f8b0:4001:c0b::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97A61126CD6 for <ietf@ietf.org>; Mon, 26 Jun 2017 16:48:36 -0700 (PDT)
Received: by mail-it0-x22e.google.com with SMTP id b205so7323032itg.1 for <ietf@ietf.org>; Mon, 26 Jun 2017 16:48:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=filament-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ctWzBz5Sa/qA5u2SfM2HjW4lPHM1PoJajvbDEgvqcRc=; b=ZF4U9AMSxJ05zRAhHbXNJbCgil7KJjrLKy1h0iYd23LM5/YvmLUl1eAg8vT2bFFXhC moEH4EoPvZvu8ktviT5vIva+7rupEI9m7cuIt1bcTIfMdB+35WGGsRVwxb1bygbPSinA Wy68BVcghl9RKXj4z2bQKQIIkhsP1QK2uWfFu8ImOpKjZyZi4Uv8SqyXcuF/efGNdJ0k cW/b3VoxNTyGYiMV1SffAV35widaGx5V2ermrKfx7GKWRFzD+nemBiuN7VS9+5NLyHtz P0C9OonU+dy6unYiBWNFU9UjfRnZ1FRlrjnjvlGxdwrI9I7YT5Rz/vLshCPtRzmjZ4c7 kphA==
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=ctWzBz5Sa/qA5u2SfM2HjW4lPHM1PoJajvbDEgvqcRc=; b=HJbSs7xTw2YHQWNwGhYrZfwsLWczTl7/ioEPGlzee8Hq3cZbu63wEaqERE4VlacuBd oO5zbc44F3h2c4SRBE8gxBYTS6tHNxZGoIV9jNxox82fgIZ/pVyeIkjPWxh0RMHtm/xx SJz4huEdCyn42auM94ukC2WqnNfrVOiJiF8oivRRk8g5DGggErNq0vlJRYnkIMM87B0t +5X+C2C+6XxnwW6BVkrFgBRoXMJ9qrGXK9la2+9bFzfo79pCc0vkZOR0/M4t9QbsgYTb WQUdtGBPhGfcTpPHCpkVyPficAya+hkJqkXCj9kABkE408JBlilXrd+D0+HY6l0A1P55 BbtA==
X-Gm-Message-State: AKS2vOwqqeDk4pNsO9TPiIEIMhnSVYKaG2Dz3g670kWyfy/lBm/mZpUt ghMIrDyRSNxvB3JT
X-Received: by 10.36.88.196 with SMTP id f187mr196964itb.86.1498520915867; Mon, 26 Jun 2017 16:48:35 -0700 (PDT)
Received: from aither.local ([2601:282:4202:67d3:50b:8144:6d4:65e9]) by smtp.gmail.com with ESMTPSA id e34sm796098ioj.62.2017.06.26.16.48.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Jun 2017 16:48:35 -0700 (PDT)
Subject: Re: Gen-art last call review of draft-ietf-precis-7613bis-07
To: Linda Dunbar <linda.dunbar@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <4A95BA014132FF49AE685FAB4B9F17F6593D94F9@SJCEML702-CHM.china.huawei.com>
Cc: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-precis-7613bis@ietf.org" <draft-ietf-precis-7613bis@ietf.org>, "precis@ietf.org" <precis@ietf.org>
From: Peter Saint-Andre - Filament <peter@filament.com>
Message-ID: <3feb4084-d038-9253-fc48-e739d846102f@filament.com>
Date: Mon, 26 Jun 2017 17:48:34 -0600
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: <4A95BA014132FF49AE685FAB4B9F17F6593D94F9@SJCEML702-CHM.china.huawei.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/j9GormYPIWZ-coUAloeZm5FPos4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 26 Jun 2017 23:48:40 -0000

Hi Linda,

Thanks for your review. Comments inline.

On 6/26/17 4:53 PM, Linda Dunbar wrote:
>  
> Reviewer: Linda Dunbar
> 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-precis-7613bis
> Reviewer: Linda Dunbar
> Review Date: 2017-06-25
> IETF LC End Date: 2017-06-27
> IESG Telechat date: 2017-07-06
>  
> Summary:
> The document is written very clear. Even for a person who is not
> familiar with the App area, I can follow through the description. The
> document is ready for publication as standard track document Major issues:
>  
> One Minor issue:
>  
> Page 6 last paragraph has:
> /SASL mechanisms SHOULD delay any case////mapping to the last possible
> moment, such as when doing a lookup////by username, performing username
> comparisons, or generating a////cryptographic salt from a username (if
> the last possible moment////happens on the server, then decisions about
> case mapping can be a////matter of deployment policy). In keeping with
> [RFC4422], SASL////mechanisms are not to apply this or any other profile
> to////authorization identifiers, only to authentication identifiers./
>  
> What does "last possible moment" mean? When I read it, I thought it
> meant wait until you got all the characters. But the next sentence
> mentions "..happens on the server". How is the "server" related to the
> entity that check the user name & password? 

Many authentication decisions happen on an application server to which a
user-oriented client connects (think of an email client connecting to an
email server). By "last possible moment" we're referring to processing
within the application server or an authentication module thereof - for
instance, instead of performing case mapping on first receiving data
from the client (thus implying that the case information is lost through
most of the processing stages), it's better to lose that information
only at the very end. Do you feel it would it help to add a more
detailed description of the reasoning here?

Peter

-- 
Peter Saint-Andre
https://filament.com/


From nobody Mon Jun 26 18:05:32 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 291F4127909 for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 18:05:30 -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=M684uoeC; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PzaM0TP+
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zW7zwH1vRxGg for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 18:05:27 -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 1D23012741D for <ietf@ietf.org>; Mon, 26 Jun 2017 18:05:27 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailnew.nyi.internal (Postfix) with ESMTP id 768DF10F2; Mon, 26 Jun 2017 21:05:26 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 26 Jun 2017 21:05:26 -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=bQw13jWofEUK1FLUQ3 UFxNnf9LAp2ctWRD0W1EHevfI=; b=M684uoeCZbr7oCmlT2PSRjsI7WdsMJ2l/i WRRRGWGD73p2xvIbDw44Ol8fDTBP2pffBDGLI6ngZdxMYg9QkmxAOmO9auH+wSMJ snh0b1KJeDh2xK26nNMI0FEek+Jm2u1GyZueY4T4fCJE2ruL4KgymTwjNxvDuPSc MUpNe705gNmAjCUimqGiYi9zgo9np4oPjVzmP4GUo7jxhjmnUjnjCty7GFVtK5Xh 3fn0pKrj9NlqZ56grDqDmFNcHGhconqApOPJS1e8DdVbh1x/s3jTMXFX+l2tYi98 joWI+VzH6BD0k8tkPQD6UrhsgV+xZIfYeapjJPF2V5Pv3102Eglw==
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=bQw13jWofEUK1FLUQ3UFxNnf9LAp2ctWRD0W1EHevfI=; b=PzaM0TP+ 0q8FejbO7B0qUSRBb18zoWUg0lG4UPcFTefZVv/Twfww0fC47+E8avQUlvzc3Qri aD55Kwtj0Q80q0MG3G5xPC0U77Nm3qdZtMfs9voYFsARou+7695Kyl7taosKPaH1 ePQi+YALwOCgrAHp8w1PGSSqVg4YX2zGDm5ACpsJgmiDzB0zkXsOB1nPMoF7qCO0 JgBtU+7MEWf5Ee2PtF19tuQATwOLYLyvgw132CHbyTWJCuZJGkVtJ5L9+l/MGnei jkadvDow0h9oc8FdwHruOXm+JvtscrxMwhabfs1kO7q98Qr3bxgkz2wjb0p6Qwq8 gBT4D5SKPxjp4Q==
X-ME-Sender: <xms:Vq9RWdfcm2sEPrfKERO9Nx-l2U6OI0BVO_Z6qui-78WzLEXj_D9M3A>
X-Sasl-enc: +Vzb9mVBnLpC1fubtjZ9Cb5bxvYbj4JTNDehenLfo/h6 1498525525
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 5E2F87E51B; Mon, 26 Jun 2017 21:05:24 -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-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CANatvzygaU9oiof3-5TqnWdxqXOGNyGqPvNhTnpPzYy391CzNw@mail.gmail.com>
Date: Tue, 27 Jun 2017 11:05:21 +1000
Cc: "Julian F. Reschke" <julian.reschke@gmx.de>, IETF Discussion Mailing List <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>, Alexey Melnikov <alexey.melnikov@isode.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4042E64B-95FB-4866-BD0E-739DF21282CD@mnot.net>
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de> <CANatvzygaU9oiof3-5TqnWdxqXOGNyGqPvNhTnpPzYy391CzNw@mail.gmail.com>
To: Kazuho Oku <kazuhooku@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/v5oG6Gj6VcbCUlb3xUMuq845Ya0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 01:05:30 -0000

> On 26 Jun 2017, at 12:39 pm, Kazuho Oku <kazuhooku@gmail.com> wrote:

> The reasons I added a clause prohibiting the use of hop-by-hop headers
> in an 103 response are as follows:
> * does not make sense for a response that attempts to send the
> metadata of a final response early
> * to avoid confusion caused by sending a hop-by-hop header in the 103 =
response
>=20
> Without the restriction, a response like below would be valid, which
> IMO is confusing at least.
>=20
> ```
> HTTP/1.1 103 Early Hints
> Connection: close
> Link: </style.css>; rel=3Dpreload
>=20
> HTTP/1.1 200 OK
> Connection: close
> Link: </style.css>; rel=3Dpreload
> ...
> ```

Perhaps you could just give guidance that only the headers intended as =
early hints should be sent?


> The statement exists since sending 103 only makes sense when it is
> impossible to immediately send a final response.
>=20
> For example, there is no need for a cache that is in possession of a
> freshly-cached final response to send a 103 that was sent from the
> origin before sending the final response. I also believe that most
> caching proxies that exist today do not cache informational responses,
> and that there is no need for us to require them to do so.
>=20
> Considering the facts, one way to resolve the issue would be to adjust
> the statement to something like "An intermediary MAY omit the 103
> response when resending a cached response", and argue that re-sending
> a cached response is not an action of "forwarding," which is defined
> as a MUST in RFC 7231.
>=20
> But wouldn't it be simpler to just have the "MAY drop" clause for any
> intermediary?

Re-specifying HTTP for a special case isn't a good idea. I think you =
could mention that gateways can decide not to forward a 103 response at =
their discretion / depending on their configuration, but I don't know if =
I'd put a requirement around it. Also, see below.

As an aside -- HTTP only specifies very general requirements for =
gateways; by their nature, they're black boxes (the back-end protocol =
*can* be HTTP, but it doesn't have to be, and how they connect the two =
sides in that case is also unspecified). So I wouldn't go into too much =
detail about their operation.


> Yes. They need to, especially if caching is involved. 103 is an
> intermediary response and there is no guarantee (or a requirement) for
> a cache to retain the headers included only in the informational
> response.
>=20
> In case of link rel=3Dpreload headers, a client can speculatively load
> the resources included in the headers while revalidating a
> stale-cached response, or a caching proxy can generate a 103 response
> from a stale-cached 200 response, while waiting for the origin to
> perform revalidation.

The underlying problem here is that the caching model doesn't talk about =
final and non-final responses.=20

I've raised <https://github.com/httpwg/http11bis/issues/29>. I don't =
think that you need to specify anything about this.


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


From nobody Mon Jun 26 18:41:35 2017
Return-Path: <peter@filament.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A63311286CA for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 18:41:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=filament-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 c5JinB61Uh05 for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 18:41:18 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::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 CEFE11286D6 for <ietf@ietf.org>; Mon, 26 Jun 2017 18:41:15 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id h134so10364428iof.2 for <ietf@ietf.org>; Mon, 26 Jun 2017 18:41:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=filament-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=dFD9Zk6KlY8UN368gfze5cwKU3iepFsuuBSNkFkZ6yU=; b=xMxx7oNdR0r2xNgCiGkCcOTTkfebjJYmN76oDjxWkjcqAolT9Ke1bP71ZyxocgpVSI jRSMecL/fig2aN5WTZrtJgWN4V2HGcybxVwP0aYrDCO5mkUwu2WY44mjskC5pJ21rJCQ j7yZ0R9yimlQpBVDtOoBxRIfzycfLtfjucNBmX8c8BkHh6SFH4bTF5BFJVU9j6vFK4up FWZb55Zlq0JHJn0HOfDppMJGBHaq3VdUyINL2LWhcCgfFkh732qD5n/DE7YOSrUS5co7 6T4yXvJi/RD4EcfFR9wTE3JN+UzRnWADyXbm3dQS/2fbNvHQvYDgijUI+9mjjqAqttPR jlVA==
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=dFD9Zk6KlY8UN368gfze5cwKU3iepFsuuBSNkFkZ6yU=; b=sSL49Ga6FnonB7g8Hx3omSdA0epxawjhztqZtZ3tJu87/8Fikrc+oOAdfm3q/2LUMr 29WezMRFyuIJzX+vTnbpLIg2Hop5BADBDENaeMukf5nuWco9otu7R2E/7EEyHUPwVFIN fVBAjtw+llO94Ljf96myGHsYNwwDchwOvKmAbS/gmSUW6pUMv7eAgaaTbZf0994eJheU qwHCKW0XqXurbbni8SZtrgtZzdDQJ+PKjj0FvxHocrch8TR5YDqbNP2v3MO3fm8z01Kv MYjtbHwzInc8ehX6/MFzLOxGOp43TfxeARzEcqTkHxrAxu9S86I9ovP1h5F4iDNZfSYm ga7A==
X-Gm-Message-State: AKS2vOy6t9j5t7UdKlU++GArAqse/xnb9/kxId7ofH+qyPaoc0cjIGlM thvoHWE4Gtdp2Z91
X-Received: by 10.107.169.28 with SMTP id s28mr4696808ioe.1.1498527675181; Mon, 26 Jun 2017 18:41:15 -0700 (PDT)
Received: from aither.local ([2601:282:4202:67d3:5c8c:f89e:d54d:fabe]) by smtp.gmail.com with ESMTPSA id z64sm916712iod.55.2017.06.26.18.41.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Jun 2017 18:41:11 -0700 (PDT)
Subject: Re: [precis] Gen-art last call review of draft-ietf-precis-7613bis-07
To: Peter Saint-Andre - Filament <peter@filament.com>, Linda Dunbar <linda.dunbar@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <4A95BA014132FF49AE685FAB4B9F17F6593D94F9@SJCEML702-CHM.china.huawei.com> <3feb4084-d038-9253-fc48-e739d846102f@filament.com>
Cc: "precis@ietf.org" <precis@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-precis-7613bis@ietf.org" <draft-ietf-precis-7613bis@ietf.org>
From: Peter Saint-Andre - Filament <peter@filament.com>
Message-ID: <f070d840-792d-8447-4e2a-f919019adff1@filament.com>
Date: Mon, 26 Jun 2017 19:41:09 -0600
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: <3feb4084-d038-9253-fc48-e739d846102f@filament.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5N1hyhB0gZVt48zneUOQi8AfHm4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 01:41:20 -0000

On 6/26/17 5:48 PM, Peter Saint-Andre - Filament wrote:
> Hi Linda,
> 
> Thanks for your review. Comments inline.
> 
> On 6/26/17 4:53 PM, Linda Dunbar wrote:
>>  
>> Reviewer: Linda Dunbar
>> 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-precis-7613bis
>> Reviewer: Linda Dunbar
>> Review Date: 2017-06-25
>> IETF LC End Date: 2017-06-27
>> IESG Telechat date: 2017-07-06
>>  
>> Summary:
>> The document is written very clear. Even for a person who is not
>> familiar with the App area, I can follow through the description. The
>> document is ready for publication as standard track document Major issues:
>>  
>> One Minor issue:
>>  
>> Page 6 last paragraph has:
>> /SASL mechanisms SHOULD delay any case////mapping to the last possible
>> moment, such as when doing a lookup////by username, performing username
>> comparisons, or generating a////cryptographic salt from a username (if
>> the last possible moment////happens on the server, then decisions about
>> case mapping can be a////matter of deployment policy). In keeping with
>> [RFC4422], SASL////mechanisms are not to apply this or any other profile
>> to////authorization identifiers, only to authentication identifiers./
>>  
>> What does "last possible moment" mean? When I read it, I thought it
>> meant wait until you got all the characters. But the next sentence
>> mentions "..happens on the server". How is the "server" related to the
>> entity that check the user name & password? 
> 
> Many authentication decisions happen on an application server to which a
> user-oriented client connects (think of an email client connecting to an
> email server). By "last possible moment" we're referring to processing
> within the application server or an authentication module thereof - for
> instance, instead of performing case mapping on first receiving data
> from the client (thus implying that the case information is lost through
> most of the processing stages), it's better to lose that information
> only at the very end. Do you feel it would it help to add a more
> detailed description of the reasoning here?

Here is a proposed adjustment to the text:

OLD

      SASL mechanisms SHOULD delay any case
      mapping to the last possible moment, such as when doing a lookup
      by username...

NEW

      Because case mapping results in
      information loss, in order to retain that information for as long
      as possible during processing, implementations SHOULD delay any
      case mapping to the last possible moment, such as when doing a
      lookup by username...

Peter


From nobody Mon Jun 26 20:29:35 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 C568F1287A7 for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 20:29:34 -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 Eubd7UskgdXh for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 20:29:33 -0700 (PDT)
Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (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 6337C1286D6 for <ietf@ietf.org>; Mon, 26 Jun 2017 20:29:33 -0700 (PDT)
X-AuditID: 12074422-589ff70000007c64-fe-5951d11b41fc
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-5.mit.edu (Symantec Messaging Gateway) with SMTP id EC.20.31844.B11D1595; Mon, 26 Jun 2017 23:29:32 -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 v5R3TU8v019657; Mon, 26 Jun 2017 23:29: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 v5R3TQZb010586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 26 Jun 2017 23:29:29 -0400
Date: Mon, 26 Jun 2017 22:29:26 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, IETF Discussion <ietf@ietf.org>
Subject: Re: Which is the right "RFC2119" Boilerplate?
Message-ID: <20170627032926.GD68391@kduck.kaduk.org>
References: <a69ab951-ec0a-0c29-57aa-013f969db7be@gmail.com> <83ce36c5-3bfd-6d78-4ede-f8df3a9aa60c@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <83ce36c5-3bfd-6d78-4ede-f8df3a9aa60c@gmx.de>
User-Agent: Mutt/1.7.1 (2016-10-04)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrHIsWRmVeSWpSXmKPExsUixCmqrCtzMTDSYOtLRotnG+ezWGx++IbV 4tSDRAdmj52z7rJ7fPgY57FkyU+mAOYoLpuU1JzMstQifbsEroxJj7+yF5xmqbh5dA9rA+MB 5i5GTg4JAROJF/tPgNlCAouZJJpvuHYxcgHZGxklPv9fzQzhXGWSWL/mECtIFYuAqsSuX3/A OtgEVCQaui+D2SICWhK37+1lBLGZBfwk7u96DRYXFjCTWHt4NVgvL9C2zb/esENsy5G4/fUt I0RcUOLkzCcsEL1aEjf+vWTqYuQAsqUllv/jAAlzClhJLN94H6xEVEBZ4u/heywTGAVmIeme haR7FkL3AkbmVYyyKblVurmJmTnFqcm6xcmJeXmpRbqmermZJXqpKaWbGEFBy+6itINx4j+v Q4wCHIxKPLw/mAIjhVgTy4orcw8xSnIwKYnyCi0FCvEl5adUZiQWZ8QXleakFh9ilOBgVhLh 9T0DlONNSaysSi3Kh0lJc7AoifOKazRGCAmkJ5akZqemFqQWwWRlODiUJHiVLgA1ChalpqdW pGXmlCCkmTg4QYbzAA0vOw4yvLggMbc4Mx0if4pRl6Ppw5YvTEIsefl5qVLivN/OARUJgBRl lObBzQElG4ns/TWvGMWB3hLm/QNSxQNMVHCTXgEtYQJawjIvAGRJSSJCSqqBUeTqfv0SXhN3 reOl277VcZzeKVEv9fE7h+ZeQYPl3ituyr/2Kfip4hT8vPT1VB62P6blAk3Tv1UmWfIcb+QL /C0ZqfR62Yqk9bcFbZ06eG2NLnH6c9+ct8MlVl7m8cqkI6p/9uenr/nmlbT/zKzqTaUx7Olu 83cynvqateikdlBPVLCnitgnJZbijERDLeai4kQADH0X1BEDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gRT9kN_EWAUSCrZJ69xH87WG7-M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 03:29:35 -0000

On Mon, Jun 26, 2017 at 06:12:39PM +0200, Julian Reschke wrote:
> On 2017-06-26 17:14, Stewart Bryant wrote:
> >   I diligently included in a draft the updated "RFC2119" boilerplate 
> > which includes the reference to RFC8174.
> > 
> > Nits then complains that it does not like the RFC2119 text (which is cut 
> > and paste from a very recent RFC).
> > 
> > So which is right, nits or the RFC Editor?
> > ...
> 
> Seems that idnits needs an update.

Seems that it does, indeed.

And perhaps Stewart should look at the Errata for RFC 2119, if he has not already.

-Ben


From nobody Mon Jun 26 20:52:20 2017
Return-Path: <kazuhooku@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 C7637127136 for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 20:52:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 8keTyUKZMsO4 for <ietf@ietfa.amsl.com>; Mon, 26 Jun 2017 20:52:15 -0700 (PDT)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::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 C76E51243F3 for <ietf@ietf.org>; Mon, 26 Jun 2017 20:52:15 -0700 (PDT)
Received: by mail-pf0-x231.google.com with SMTP id q86so9789911pfl.3 for <ietf@ietf.org>; Mon, 26 Jun 2017 20:52: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:content-transfer-encoding; bh=oh1AtaitlhmXGfyNL/5cvOJimO5IhUJIcOEn8vTK3iM=; b=PLk36J8WgITrzArVaiqU6fSyEkqwPe4BPPXTfkm+ZCp83MYIDqPKubsAdmcuKvVTwY 1Dz3TkLdAYlrzCXMf3bwOxiWlE6KqDFDOUXcp7eX29rAqmHHTPZ8vcL+ygMT1FqaGQ56 H0nbGfiTM9HpFFk7uH9gJGzDexkystxRWUvqcipN5Mfjv/J3gPNEePniNWCF0QYzeT1S YMm16AHmvFpTgM1sexKJQWRNoagsJjsC6/rDLXe7odY1L/MESZYzVS7R1Ci0OigVjHol tylW5NLRK2YR2lWKtvZ3SMsAVmx5qaNjtJmaIcnrRs50jZ0HyqgSxu+6CTDcC1h7EN0j uzHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=oh1AtaitlhmXGfyNL/5cvOJimO5IhUJIcOEn8vTK3iM=; b=CFtXsz0Yns7L3ANGKQNXcyQMQZ/ecusOmqQxYo74mvruqbO/0KIXuvt0OEc3001AkG +qa7PAFxhXQM06p8Bp4TScddjmzug+dx6xB3F3qOMbOX1VBaTFfKS6WtokX2QR0/d8ZQ S5ybGWkUgDbn/39Ce0nhrzmwC/fr7tXKITugyz2m12p3uQkMUzCiXh/1a7cbFhgzXpib 2Eqp58x323UQGJcx9iJTX1K9/56c0Ep4QTcPicwYOVwU7HcOv3DxiHUDIFxf+EeJbyHq 4p2NTgJP9sYptFnSuqNr61Wf/rmaOCYxNc3WnUMlYfgoAHm81m/Js67QgYxpI27Nw2W4 bP/g==
X-Gm-Message-State: AKS2vOw5x5MegjOGVrLluMsy4OuBFWUlQCnd4vbYAa6ahnTXMntap8+i 2FBEOJkrBV8NPogIFoVqC88vT+6GWvzFIxE=
X-Received: by 10.99.152.18 with SMTP id q18mr3237005pgd.91.1498535535220; Mon, 26 Jun 2017 20:52:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.130.3 with HTTP; Mon, 26 Jun 2017 20:52:14 -0700 (PDT)
In-Reply-To: <4042E64B-95FB-4866-BD0E-739DF21282CD@mnot.net>
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de> <CANatvzygaU9oiof3-5TqnWdxqXOGNyGqPvNhTnpPzYy391CzNw@mail.gmail.com> <4042E64B-95FB-4866-BD0E-739DF21282CD@mnot.net>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Tue, 27 Jun 2017 12:52:14 +0900
Message-ID: <CANatvzyKP89vQyfJR8gm7Ubgu88fi1nwEY3PULNCB+5ViHjZmg@mail.gmail.com>
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
To: Mark Nottingham <mnot@mnot.net>
Cc: "Julian F. Reschke" <julian.reschke@gmx.de>, IETF Discussion Mailing List <ietf@ietf.org>,  HTTP Working Group <ietf-http-wg@w3.org>, Alexey Melnikov <alexey.melnikov@isode.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pnn1Jncwddhfia6umB_pwtCMB5w>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 03:52:18 -0000

Hi Mark, Julian,

Thank you for your comments / suggestions.

I have created a pull request that hopefully would address the issues
being raised: https://github.com/httpwg/http-extensions/pull/363;
please let me know what you think.

The PR removes the statements that have been pointed out either as
redundant or in contradiction with RFC 723x. It also gives guidance to
servers how they should generate the 103 headers.

Regarding the action of an intermediary, I like the Mark's view
(stated in the new GitHub issue) that caches are expected to store
only final responses and that it should be clarified in the next
revision of HTTP. Considering that way, I think we do not need to
specify how a intermediary needs to deal with a 103 response (except
for the fact that a HTTP/2 gateway might create a HTTP/2 push based on
the information found in the informational response).

2017-06-27 10:05 GMT+09:00 Mark Nottingham <mnot@mnot.net>:
>
>> On 26 Jun 2017, at 12:39 pm, Kazuho Oku <kazuhooku@gmail.com> wrote:
>
>> The reasons I added a clause prohibiting the use of hop-by-hop headers
>> in an 103 response are as follows:
>> * does not make sense for a response that attempts to send the
>> metadata of a final response early
>> * to avoid confusion caused by sending a hop-by-hop header in the 103 re=
sponse
>>
>> Without the restriction, a response like below would be valid, which
>> IMO is confusing at least.
>>
>> ```
>> HTTP/1.1 103 Early Hints
>> Connection: close
>> Link: </style.css>; rel=3Dpreload
>>
>> HTTP/1.1 200 OK
>> Connection: close
>> Link: </style.css>; rel=3Dpreload
>> ...
>> ```
>
> Perhaps you could just give guidance that only the headers intended as ea=
rly hints should be sent?
>
>
>> The statement exists since sending 103 only makes sense when it is
>> impossible to immediately send a final response.
>>
>> For example, there is no need for a cache that is in possession of a
>> freshly-cached final response to send a 103 that was sent from the
>> origin before sending the final response. I also believe that most
>> caching proxies that exist today do not cache informational responses,
>> and that there is no need for us to require them to do so.
>>
>> Considering the facts, one way to resolve the issue would be to adjust
>> the statement to something like "An intermediary MAY omit the 103
>> response when resending a cached response", and argue that re-sending
>> a cached response is not an action of "forwarding," which is defined
>> as a MUST in RFC 7231.
>>
>> But wouldn't it be simpler to just have the "MAY drop" clause for any
>> intermediary?
>
> Re-specifying HTTP for a special case isn't a good idea. I think you coul=
d mention that gateways can decide not to forward a 103 response at their d=
iscretion / depending on their configuration, but I don't know if I'd put a=
 requirement around it. Also, see below.
>
> As an aside -- HTTP only specifies very general requirements for gateways=
; by their nature, they're black boxes (the back-end protocol *can* be HTTP=
, but it doesn't have to be, and how they connect the two sides in that cas=
e is also unspecified). So I wouldn't go into too much detail about their o=
peration.
>
>
>> Yes. They need to, especially if caching is involved. 103 is an
>> intermediary response and there is no guarantee (or a requirement) for
>> a cache to retain the headers included only in the informational
>> response.
>>
>> In case of link rel=3Dpreload headers, a client can speculatively load
>> the resources included in the headers while revalidating a
>> stale-cached response, or a caching proxy can generate a 103 response
>> from a stale-cached 200 response, while waiting for the origin to
>> perform revalidation.
>
> The underlying problem here is that the caching model doesn't talk about =
final and non-final responses.
>
> I've raised <https://github.com/httpwg/http11bis/issues/29>. I don't thin=
k that you need to specify anything about this.
>
>
> --
> Mark Nottingham   https://www.mnot.net/
>



--=20
Kazuho Oku


From nobody Mon Jun 26 22:29:39 2017
Return-Path: <w@1wt.eu>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E5EF1287A7; Mon, 26 Jun 2017 22:29:37 -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, 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 DXba4Z89l9N2; Mon, 26 Jun 2017 22:29:35 -0700 (PDT)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 19AA21200E5; Mon, 26 Jun 2017 22:29:34 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id v5R5TSQQ005592; Tue, 27 Jun 2017 07:29:28 +0200
Date: Tue, 27 Jun 2017 07:29:28 +0200
From: Willy Tarreau <w@1wt.eu>
To: ietf@ietf.org
Cc: IETF-Announce <ietf-announce@ietf.org>, httpbis-chairs@ietf.org, Mark Nottingham <mnot@mnot.net>, draft-ietf-httpbis-early-hints@ietf.org, ietf-http-wg@w3.org, alexey.melnikov@isode.com
Subject: Re: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status  Code for Indicating Hints) to Experimental RFC
Message-ID: <20170627052928.GA5568@1wt.eu>
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/liRJ_8jE0dD-9vxOYDWMVNru_7M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 05:29:37 -0000

On Wed, Jun 21, 2017 at 09:59:32AM -0700, The IESG wrote:
> 
> The IESG has received a request from the Hypertext Transfer Protocol WG
> (httpbis) to consider the following document: - 'An HTTP Status Code for
> Indicating Hints'
>   <draft-ietf-httpbis-early-hints-03.txt> as Experimental RFC

I've just noticed that it's never mentionned that a client should be
prepared to receive multiple 103 responses as any informational response
(or at least I did not notice).

I think that indicating that multiple responses MAY be sent with complementary
and/or possibly overlapping links, it may help grasp the overall principle
and the relation between these informational responses and the final one.

The case I'm having in mind is the same as described in the PR comment, a
server-side gateway could speculatively send a 103 with a few site-specific
links while the server provides another 103 with some resource-specific
links.

Willy


From nobody Tue Jun 27 01:17:21 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 07A5D129417 for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 01:17: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 wsXH9FbEI5SB for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 01:17:18 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9849412009C for <ietf@ietf.org>; Tue, 27 Jun 2017 01:17:18 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id i127so18692420wma.0 for <ietf@ietf.org>; Tue, 27 Jun 2017 01:17:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=references:in-reply-to:mime-version:content-transfer-encoding :message-id:cc:from:subject:date:to; bh=durv7cgcz4P11SxvbbYW61M7OqVuYKp1BJCZCTsMtoU=; b=qcN7c0+Yy5ZayVhQRmaLM9H87VfMcm/j+L5jyw//OW0CJ/wRteQHs288ZpprOMfLjf KhQ8J3DUh4rFEtlbI9K1IGA7JDIBF7c/6zS26zgkL+rltkw+wfxSYLAqWQTSm9zK2D4B YytLfaGvnJ+M0eJbpjCTRDUvJaCq7z9VXqthrbq4oLvdcP07ddxeY6anoOXioEmnKVrO iTKd9587V3fLphiUHKFIhYyb7wqp1OvmYjrlr4q18OTDefw1qtlKqoRHL+Qe1E2OflZM 00DyTB8nAizot2fuX0h7AZTdROusmyNGeoFjzXBN5ctFyKI+S5qMEGS7n+Z7l02XS/Sl Br3w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:in-reply-to:mime-version :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=durv7cgcz4P11SxvbbYW61M7OqVuYKp1BJCZCTsMtoU=; b=iaXGXSUWnb+aeRVvVo83dI64K/mVHOHmOMemc5ky+oR67MdUEkllLekeOUYPlP5Y3j FwYULfeWAnEdYyAKaWiNQeFgJy51ZfoKAcHREpSuCsu8hFr/Qe5XHCZnOT3r5rX6ZXv5 eRZpsv60t/VA56UCVD3X3S+1heCx5s6xfiKHi7SN86Y8uCqVEdFcZeEAwuFkpfrlmToM 9g40m0iPScAX9Qgn6Eq+L9R6dMM4looOJdbSCO91UaSOSE0skAnWV6DxAi0pP4i26R+x u2yhMBSfpowYgznsctwqO4y5GNZrrQZfZL57rd3UYMbI/Tyvu2yMCBLKJNh9rvMJPkqk 9mRA==
X-Gm-Message-State: AKS2vOwT8hNLIrwmPq1qiunk5OvnH3ti3KM6HBVXIBsZs79t4VgWFh9f 2muMpMnpOd7AvA==
X-Received: by 10.28.105.218 with SMTP id z87mr2423620wmh.121.1498551437052; Tue, 27 Jun 2017 01:17:17 -0700 (PDT)
Received: from [192.168.2.141] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id m187sm1809596wmb.10.2017.06.27.01.17.16 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 27 Jun 2017 01:17:16 -0700 (PDT)
References: <a69ab951-ec0a-0c29-57aa-013f969db7be@gmail.com> <83ce36c5-3bfd-6d78-4ede-f8df3a9aa60c@gmx.de> <20170627032926.GD68391@kduck.kaduk.org>
In-Reply-To: <20170627032926.GD68391@kduck.kaduk.org>
Mime-Version: 1.0 (1.0)
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=us-ascii
Message-Id: <BB6A4223-8443-46ED-8F43-5A18EA2074CE@gmail.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, IETF Discussion <ietf@ietf.org>
X-Mailer: iPad Mail (13G36)
From: Gmail <stewart.bryant@gmail.com>
Subject: Re: Which is the right "RFC2119" Boilerplate?
Date: Tue, 27 Jun 2017 09:17:15 +0100
To: Benjamin Kaduk <kaduk@mit.edu>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Zd5ZErEDNzW2zl5JvEIXuO2KZTs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 08:17:20 -0000

Sent from my iPad

> On 27 Jun 2017, at 04:29, Benjamin Kaduk <kaduk@mit.edu> wrote:
>=20
> And perhaps Stewart should look at the Errata for RFC 2119, if he has not a=
lready.

It has been my long standing concern that for all practical purposes no one l=
ook at errata! Indeed I doubt that many will until the RFC Editor appends th=
e verified errata to RFCs, or takes some similar approach with them.

In this case I looked at the errata and could not see anything, what did I m=
iss?

At a different level maybe we need an xml tag that  includes the 2119 boiler=
plate?

Stewart=


From nobody Tue Jun 27 01:45:43 2017
Return-Path: <barryleiba.mailing.lists@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 75D15127333 for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 01:45:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Level: 
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LAl5-HLiIW-d for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 01:45:41 -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 13A04126C23 for <ietf@ietf.org>; Tue, 27 Jun 2017 01:45:41 -0700 (PDT)
Received: by mail-qt0-x234.google.com with SMTP id i2so19252864qta.3 for <ietf@ietf.org>; Tue, 27 Jun 2017 01:45:41 -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=jlNXEbjPdlCuazGFwSrH1NyMS5R4wM1R9RHZmZB5YVI=; b=IINOaGOHzMkCJAiSkkXNNFef6Ci/5hMds2HdlxRex8THNtc7F1C9RvVR5FSY09J9sW V6XBjPEoGHLBs8kv8WH+/CdE/QqrJcHZnEIU4L0673Ue5DCHRUEd4aLuPLSi94sszKqn LvD8IOJwmpv6jQB3tqBAjkUjIX1XoXPbpvXmvFuYG/6i6vxqNl9q9UT352jqofrcO8Kh XWd8s2uWQUEt+BKpl6Gvyi5et+qPau8LnphMrdhLThBd0BLo55EEOWVgODrn9Pksi7KT 5zAtaOAPoe7unMK/srTwfqokJnrokkmLVI1Xo2ffv7u7hUJknY/AQ4xt6i2Bls/94L5X SKtg==
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=jlNXEbjPdlCuazGFwSrH1NyMS5R4wM1R9RHZmZB5YVI=; b=e4T0U+kn+iI4gY/J5GxBrjYPx3SDOEVKEOMqYtOpcy0aDlV83Pf9fMd3LQmf9eEwnq +yk2Haj51FnmgzLwXctAMA0NfTCIsOHre8x5Sv+hZSWgdcfydUeN7Tu3Pjzksfnb4+hK eQ+PwbYcwgH3RUUv9Xl22crSJyCdtyuMEfvE+wqc6IuDxleBcZ5AfEBppV+RXHjEc5+O TYXoVmVzj89uA+7j2phJkrt9TJktQsndz0bBagjwrdQMLgSZBxsoPwP4JQADRyiZCwll BF9fvhSup82pQRu/JpLuRHa7y/crwDa4Vi0GIXuiHoMzn78sVl91qql1iJAidF7F87U6 sbUA==
X-Gm-Message-State: AKS2vOwXfkk3B3ao7l4Bz5HeQtzltT0cHYM4TEybEn9SfSfx19dW/xdX ft0au0e/sCnOsSiWnBM4IKYlKwFRHg==
X-Received: by 10.200.53.151 with SMTP id k23mr5428324qtb.104.1498553140288; Tue, 27 Jun 2017 01:45:40 -0700 (PDT)
MIME-Version: 1.0
Sender: barryleiba.mailing.lists@gmail.com
Received: by 10.200.36.14 with HTTP; Tue, 27 Jun 2017 01:45:39 -0700 (PDT)
In-Reply-To: <a69ab951-ec0a-0c29-57aa-013f969db7be@gmail.com>
References: <a69ab951-ec0a-0c29-57aa-013f969db7be@gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 27 Jun 2017 10:45:39 +0200
X-Google-Sender-Auth: CZ0NdhgfQPM2QHTmE_HKDQQBf88
Message-ID: <CAC4RtVB73xfvw_dn-Sg3agd0DwVrboj-E2kqfPRwpSe6no0VOw@mail.gmail.com>
Subject: Re: Which is the right "RFC2119" Boilerplate?
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/lqqKHBe3lHicybQWKR3TBmWpG38>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 08:45:42 -0000

Henrik is aware that idnits needs to be updated, and is working on
that.  He's been in contact with me about it.  (I actually thought
he'd already put the fix up, but I guess not.)

Barry


On Mon, Jun 26, 2017 at 5:14 PM, Stewart Bryant
<stewart.bryant@gmail.com> wrote:
>  I diligently included in a draft the updated "RFC2119" boilerplate which
> includes the reference to RFC8174.
>
> Nits then complains that it does not like the RFC2119 text (which is cut and
> paste from a very recent RFC).
>
> So which is right, nits or the RFC Editor?
>
> =================
>
>  == The document seems to lack the recommended RFC 2119 boilerplate, even if
>      it appears to use RFC 2119 keywords -- however, there's a paragraph
> with
>      a matching beginning. Boilerplate error?
>
>      RFC 2119, paragraph 2:
>         The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>         "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
>         this document are to be interpreted as described in RFC 2119.
>
>      ... text found in draft:
>         The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
>         "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY",
> ................................................^
>         and "OPTIONAL" in this document are to be interpreted as
>         described in BCP 14 [RFC2119] [RFC8174] when, and only when, they
>         appear in all capitals, as shown here.
>
>
>      (The document does seem to have the reference to RFC 2119 which the
>      ID-Checklist requires).
>
> =================
>
> - Stewart


From nobody Tue Jun 27 01:54:15 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 C184D127B5A for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 01:54:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.92
X-Spam-Level: 
X-Spam-Status: No, score=-6.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 ivdIcB5AvBlJ for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 01:54:12 -0700 (PDT)
Received: from ukmta2.baesystems.com (ukmta2.baesystems.com [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 8A3B1126DEE for <ietf@ietf.org>; Tue, 27 Jun 2017 01:54:11 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.39,399,1493679600";  d="scan'208";a="8027443"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta2.baesystems.com with ESMTP; 27 Jun 2017 09:54:09 +0100
X-IronPort-AV: E=Sophos;i="5.39,399,1493679600";  d="scan'208";a="7606911"
Received: from glkxh0004v.greenlnk.net ([10.109.2.35]) by baemasmds016.greenlnk.net with ESMTP; 27 Jun 2017 09:54:09 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.201]) by GLKXH0004V.GREENLNK.net ([10.109.2.35]) with mapi id 14.03.0248.002; Tue, 27 Jun 2017 09:53:48 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Joe Touch <touch@isi.edu>, =?utf-8?B?UGV0ciDFoHBhxI1law==?= <petr.spacek@nic.cz>, "ietf@ietf.org" <ietf@ietf.org>
Subject: RE: I-D Action: draft-thomson-postel-was-wrong-01.txt
Thread-Topic: I-D Action: draft-thomson-postel-was-wrong-01.txt
Thread-Index: AQHS4/ajWP45auakP0OI/9KB5mNdK6IicSuAgABYwYCAADhpgIAARqaAgAEnvQCAAHJvAIAELU4AgAHS6QCAAlWNgIAEGvuAgADk5LCAAHzDAIAENLFggACs1gCAAOYs4A==
Date: Tue, 27 Jun 2017 08:53:43 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636E0DA@GLKXM0003v.GREENLNK.net>
References: <149727416998.10345.14056211125888203672@ietfa.amsl.com> <20170613033859.GA71771@shrubbery.net> <0658C4E3DBD74293BF3A2CBB@PSB> <20170613142820.GA21291@shrubbery.net> <a9a32f87-825f-090a-44d4-7fb129771f02@huitema.net> <7c762c83-2c94-f46f-e8bc-a18e7887d714@isi.edu> <db4218d7-59b4-7dd8-2cf6-ed9673960cac@nic.cz> <4d1f6a3f-dab9-41a3-7302-bd87a519bbb9@isi.edu> <f69679ba-f69c-b063-943f-6994489c526d@nic.cz> <2b8c3aca-d6f8-e778-3da3-80d2b4e1598b@isi.edu> <8e8d4db9-93fd-5092-68de-6d8de44151c3@nic.cz> <c9202a09-af8b-faf6-b583-694378022dae@isi.edu> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636B715@GLKXM0003v.GREENLNK.net> <d0c4ecc7-1fe9-fc0b-bbe5-8cffb956b6ed@isi.edu> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636DCC9@GLKXM0003v.GREENLNK.net> <8a5e69f8-37f5-516f-172e-696a891e674f@isi.edu>
In-Reply-To: <8a5e69f8-37f5-516f-172e-696a891e674f@isi.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.109.62.6]
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PzaGlCTU-QAfIx_l-tzP6RwTCzk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 08:54:14 -0000

T0suIEkgd2FudChlZCkgYSB0ZXJtIGNvdmVyaW5nIGJvdGguIEkganVzdCB0b29rIGEgbG9vayBh
dCBhIGRyYWZ0IHN0YW5kYXJkIChub3QgYW4gSUVURiBvbmUsIGJ1dCB1c2VzIHNldmVyYWwgUkZD
cywgc28gaXQncyBwYXJ0bHkgZnJvbSB0aGF0IGN1bHR1cmUpIGFuZCBpdCB1c2VzIHRoZSBmb3Jt
dWxhdGlvbiAidGhlIG1lc3NhZ2UgaXMgaW52YWxpZCIuDQoNCi0tIA0KQ2hyaXN0b3BoZXIgRGVh
cmxvdmUNClNlbmlvciBQcmluY2lwYWwgRW5naW5lZXINCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50
ZWxsaWdlbmNlIExhYm9yYXRvcmllcw0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCg0KVDogwqArNDQgMzMw
MCA0Njc1MDAgwqB8IMKgRTogY2hyaXMuZGVhcmxvdmVAYmFlc3lzdGVtcy5jb20NCg0KQkFFIFN5
c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UsIENoZWxtc2ZvcmQgVGVjaG5vbG9neSBQYXJrLCBH
cmVhdCBCYWRkb3csIENoZWxtc2ZvcmQsIEVzc2V4IENNMiA4SE4uDQp3d3cuYmFlc3lzdGVtcy5j
b20vYWkNCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlIExpbWl0ZWQNClJlZ2lzdGVy
ZWQgaW4gRW5nbGFuZCAmIFdhbGVzIE5vOiAwMTMzNzQ1MQ0KUmVnaXN0ZXJlZCBPZmZpY2U6IFN1
cnJleSBSZXNlYXJjaCBQYXJrLCBHdWlsZGZvcmQsIFN1cnJleSwgR1UyIDdZUA0KDQotLS0tLU9y
aWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogSm9lIFRvdWNoIFttYWlsdG86dG91Y2hAaXNpLmVk
dV0gDQpTZW50OiAyNiBKdW5lIDIwMTcgMjE6MDgNClRvOiBEZWFybG92ZSwgQ2hyaXN0b3BoZXIg
KFVLKTsgUGV0ciDFoHBhxI1lazsgaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IEktRCBBY3Rp
b246IGRyYWZ0LXRob21zb24tcG9zdGVsLXdhcy13cm9uZy0wMS50eHQNCg0KLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLSEgV0FSTklORyAhIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0gVGhpcyBtZXNzYWdl
IG9yaWdpbmF0ZXMgZnJvbSBvdXRzaWRlIG91ciBvcmdhbmlzYXRpb24sIGVpdGhlciBmcm9tIGFu
IGV4dGVybmFsIHBhcnRuZXIgb3IgZnJvbSB0aGUgaW50ZXJuZXQuDQpDb25zaWRlciBjYXJlZnVs
bHkgd2hldGhlciB5b3Ugc2hvdWxkIGNsaWNrIG9uIGFueSBsaW5rcywgb3BlbiBhbnkgYXR0YWNo
bWVudHMgb3IgcmVwbHkuDQpGb2xsb3cgdGhlICdSZXBvcnQgU3VzcGljaW91cyBFbWFpbHMnIGxp
bmsgb24gSVQgbWF0dGVycyBmb3IgaW5zdHJ1Y3Rpb25zIG9uIHJlcG9ydGluZyBzdXNwaWNpb3Vz
IGVtYWlsIG1lc3NhZ2VzLg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0NCg0KDQpPbiA2LzI2LzIwMTcgMTo1MiBBTSwgRGVhcmxvdmUsIENo
cmlzdG9waGVyIChVSykgd3JvdGU6DQo+IEV4cGxpY2l0bHkgcmVqZWN0IHZzIHNpbGVudGx5IGln
bm9yZS4gSSB0b29rIHRoZSBsYXR0ZXIgdG8gYmUgYSBhbiBpbnN0YW5jZSBvZiB0aGUgbGF0dGVy
DQpJJ20gZ3Vlc3NpbmcgeW91IG1lYW50ICJJIHRvb2sgdGhlIGZvcm1lciBhcyBhbiBpbnN0YW5j
ZSBvZiB0aGUgbGF0dGVyIi4NCj4gLCBiZWNhdXNlIEkgbWVhbnQgZXhwbGljaXQgaW4gdGVybXMg
b2YgdGhlIHNwZWNpZmljYXRpb24sIG5vdCB0aGUgaW1wbGVtZW50YXRpb24uIFdvcmRpbmcgY291
bGQgb2J2aW91c2x5IGhhdmUgYmVlbiBiZXR0ZXIuIEkgY291bGQgc2VlIHJlamVjdGlvbiBiZWlu
ZyBub2lzeSwgc2lsZW50IG9yIHNvbWV3aGVyZSBpbiBiZXR3ZWVuLg0KDQpJIHdhcyB3b3JraW5n
IG9mZiB5b3VyIHRlcm0gInJlamVjdCIgLSB3aGljaCBpcyBJTU8gcXVpdGUgZGlmZmVyZW50IGZy
b20NCiJpZ25vcmUiIChtb3JlIHRoYW4gdGhlIGRpZmZlcmVuY2UgYmV0d2VlbiAiZXhwbGljaXRs
eSIgYW5kICJzaWxlbnRseSIuDQoNClJlamVjdCB1c3VhbGx5IG1lYW5zIHNvbWUgb3RoZXIgYWN0
aW9uIGlzIHRha2VuLCBlLmcuLCByZXF1aXJpbmcgYW4NCmFsZXJ0IHRvIHRoZSB1c2VyLCBhIGNo
YW5nZSBpbiB0aGUgcHJvdG9jb2wgc3RhdGUsIG9yIGEgcmVzcG9uc2UNCnByb3RvY29sIG1lc3Nh
Z2UuDQoNCkpvZQ0KDQoNCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqClRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50
cyBhcmUgY29uZmlkZW50aWFsIHRvIHRoZSBpbnRlbmRlZApyZWNpcGllbnQgYW5kIG1heSBhbHNv
IGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZApyZWNpcGllbnQgcGxl
YXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtIGFuZCBub3RpZnkgdGhlIHNlbmRlci4KWW91
IHNob3VsZCBub3QgY29weSBpdCBvciB1c2UgaXQgZm9yIGFueSBwdXJwb3NlIG5vciBkaXNjbG9z
ZSBvcgpkaXN0cmlidXRlIGl0cyBjb250ZW50cyB0byBhbnkgb3RoZXIgcGVyc29uLgoqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKgo=


From nobody Tue Jun 27 02:01:13 2017
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30B7812700F for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 02:01:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level: 
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_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=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64C1F_43uM9X for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 02:01:08 -0700 (PDT)
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01on0131.outbound.protection.outlook.com [104.47.0.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 13629129432 for <ietf@ietf.org>; Tue, 27 Jun 2017 02:01:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector1-btconnect-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=vZ8v8rKPgQbMMokDkTJHbodIjoIUhKOEsdgRghQv8Jk=; b=J8YgUEup2uBl3+8PGQVIYhyGdQ8XwQQIiRKE/sb52zrOz+u8B/AxZ+pfBGC9g529jo6bCjCZk8rmmU/yOmqobJTJqvop0P5IOLslsSkxosRIvBRD4JTKUAADBozCGeC0cTvAcatAUHNU+Kc2vvfUyxR6pqvgefEWra8aNFpI/oQ=
Authentication-Results: standardstrack.com; dkim=none (message not signed) header.d=none;standardstrack.com; dmarc=none action=none header.from=btconnect.com;
Received: from pc6 (86.176.10.253) by HE1PR07MB1564.eurprd07.prod.outlook.com (2a01:111:e400:7a2d::14) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.5; Tue, 27 Jun 2017 09:01:04 +0000
Message-ID: <040001d2ef23$64b8eb60$4001a8c0@gateway.2wire.net>
From: "tom p." <daedulus@btconnect.com>
To: "Eric Burger" <eburger@standardstrack.com>, <ietf@ietf.org>
References: <63406DFB-217A-4306-B717-E86D97BA2AA9@cooperw.in> <709494B2-53ED-4483-9B1C-3855D81CD120@gmail.com> <25CD3E0C-A03D-49A3-8375-AD4D834BF94B@gondrom.org> <E01EDC06-5AEE-4957-AA46-DA87AF9D46C1@standardstrack.com>
Subject: Re: Saturday as start day
Date: Tue, 27 Jun 2017 09:28:43 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 8bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Originating-IP: [86.176.10.253]
X-ClientProxiedBy: VI1PR09CA0070.eurprd09.prod.outlook.com (2603:10a6:802:29::14) To HE1PR07MB1564.eurprd07.prod.outlook.com (2a01:111:e400:7a2d::14)
X-MS-Office365-Filtering-Correlation-Id: 56039d53-d300-46ca-0b57-08d4bd3b0abc
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095); SRVR:HE1PR07MB1564; 
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 3:BWyZOGq+xWr9nk96VwhFjvtYlyVTI7X5VC/Y/ITc/cxWHQ48WP3zNkE5KM4g1N/CQIpdPy4rWTPXSd8ZVAruoDBGtQhccsnAfN1KZVF30fOlfZi/l74Gih+9GwWiQ9MmrCTEuaHM+rBQl72tiNdm28H5gndVDHKgZlwxJpKPzVZtB+tMndbCIkZ7xL1znnuRSswHSCf1faC3gsCUAaHCAiKeFXb/YexC0G+EL7HVVPwZuHmxT9jl0UfTdGEr+0Pzu4m82/rVih8PdgP50Jksfw2wVt5oas4/DqEXKsfo7a9/zb5KzUFO3M5gADRe20ZpHqRIOsT9HdSwR53lXalBItOVl0jRt8p+N4ZqGRWfV9125MKwipbmchQki5wHrp8zHH/paNkZt7/xN6qXO9HReke0Ws194uVrt4I1tvMrSExH5DYJO4ZKV14lP0gnOBwtE5fqzttTj3HIclLuv9E1svTIsiqNeGsP7jtQ5RhjySbvSeRubn82s24z0GtcRbo+QewF2PnrOT4e+fHmO/HdZ523PFqBCBdWWqNP2N1KaZApP5GJ2HdIlkSO3UsoLWhDip6IxPNee2y4JfxrvC3z9i8G1ipNJeoEegCqLOAP3wGlyRTzDVzByv1f5CPRmcpjhBBN/URffjvBCQJiBa8vyythm80L3BpGaBJm5hjOi1cKkGzkCwGGkQiT9IpyN2OA
X-MS-PublicTrafficType: Email
X-MS-TrafficTypeDiagnostic: HE1PR07MB1564:
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 25:R2Cl3JzH3WIaKBOBZMO6j/Gkb+5akUaQQ+q2KHCz050vPKRNThwGjkfqTV0rzWVMvBW05q0aVGn/5drezsVYzXgNXOdO9HeyvRLw7CEZp/SpHJfLxJJ9/6HdqGvBCdEfoQt0CmzplLwfXXOT/prIpsw7MBzuQqlxdQ2vioc3+ytWG5CA4Ecgj+GsgNSXldgdDjcEtCY/zHCvnxUn1hdTrmVC1NVaXOI0K0tmGE7raRUXtIcqjAwDPzSt+yAvLv3teKZiqzgyxVkTXC6bKGZUs6TQleHEAgthgn/kklr/ltf2w5XtQzabZSceGFJRuEupAF1LFeBmiw6RXZ2Ps4fQBym9IxWDlCNYKmuBYVDa0jsG5UmCvvXdauWq8ql5qOerB01cGtAoCYWkFOvmYW2UK9UMa68wRccFnzj0/LB0xbrqKX2pAE/IJ24uIZEqNvudFq/evK8mwGdmFKCTjoQRqdcF5Kw13L4Sm1Pcu6Xow6pRvV0sbTXARNoCNJy1/uEquLyPgbNU4+pHKuL2CObLS/4KaBL+QA4sZ7HjArBtAc1QS4Bgh187yWZJGz7sCGmCS/yEQEkc9ABWpaHkCzQjnd5A/s2xlGmh+1QstANAXOF2X8d8MVdd5ZOdtIDvq5xVNB8wWAeU5rJyFhaZ8jVvhETbZHslmtavqcH5pswaa66M04wJomzBuBA5kXcU3LUFD2RiUxJPzRQwh1MTgmFSoFy2rKuUQkIDGGJjixnY1hYHJ/ESCr+kV5Byx3PZxPXIyP+3ixxxruOHwjQoWFHO/413RKeOOQ7Cfg3HmizfGNeSavd/w/22Z7uwke3YMwsyV/+wtmvGS/vEFiC2WvLs1OlS3AYlONZUBIJ9LfNQDdO06QYuLUVloa89Fyua2EysdiN6yLCxxVwGj3KKHZijKpBZmxBw+Eyjki71KMFRMcY=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 31:mTsuy3eUYal9jxxE6L72wjOgpI45qPvaaUuFoI4e7R45P88axcec7ZhB1zIr0qpGevDmgIZXAd+0eL45GkwV6nyLwdQj6t2kIL4p0jpHfaeEcNKdC4DDsxu4sh4BI1SDCbOYbQOnf1BYAOX7+C5uMeORy8xq1bZsNnA0LPtaL2aGovQciIuhK6veI+A7Icz68rb5X2uq90EFumquUGr8sG0onA92I3qFSdtD+a6Iu0Ul8wDxl1BddY6ibuefFQHGhCJIIx/5tWCi180gfkn9H7a+m0aH1a6YY7amYMMWRLy8TBVce/n8vOejmPexBf90NZafwaNyJMLbNGYzBu1lWFIGJUCpjqLe0nvXHU99k7ue0NgOBuerae4dSieOQvGZtQOG8OcSlBj0o1OhOsvco2UIOtKGop5y2NCHSt9PVAubSurniZzOefCXc6mp1ZA2HDiLtld+cE41tLKKdf8nU10tuzludOqj8LS0AaofJdh8nj15nwcgq2u8Xpp64750NAhWyFooJoXtkv6FymxuIhWLPa1rP8OkYIDtmSzcmRm1wL+lMBBlPU37OqrpOdUilwS3+X2rXK+/uTnJ0U1eOSqCEDNREhyN+Iq6Zfk1rLpb2FrNSwcwdOjMktXsfZ547RjBbF9LJaY03xuJy3QRCwDjaRmEsdjbsLi/KlTuBG4H4rFH3wXBTNaydoFwdbJa7ULemyzEh676v61k0ui6xQ==
X-Microsoft-Antispam-PRVS: <HE1PR07MB15647E101C82752FBF20460EC6DC0@HE1PR07MB1564.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(236129657087228)(48057245064654)(247924648384137); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(10201501046)(100000703101)(100105400095)(6041248)(20161123562025)(20161123560025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(20161123558100)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:HE1PR07MB1564; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:HE1PR07MB1564; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTY0OzQ6SGlRa3Z0NTVEK2RtR2lqNzRQVEM2djRrMjNT?= =?utf-8?B?NXFqdUY3T2daeWdnVy9WNkdsQjZiSGFhNEM0V0trbzhlMW5GWWtuMjlXQnh5?= =?utf-8?B?cWd2ZERzWnlLVkR6MCtSV2hzUkttVGpueEd5RHBMZTVsYmxFNXV2TXk5TTFF?= =?utf-8?B?V3hzd292ZnNSSDlha1N6TUlwaCtOb09SWU1JVDc4QXBXOEJSWUdSRjJEUGZ0?= =?utf-8?B?WERLY2lxNkFvYU94Uk1XMTZtTmpqRlI2TnA5UUZsUW5oWnhiamhySEhDTXQv?= =?utf-8?B?NFBOT3cvNFZkMFdleGkzVUl2elNOTzFQeERsZUFnbUFkS2VqSkhQSlNLS2g3?= =?utf-8?B?L3M0MlRQVmpRTmFjYjlPZGFvYVQ0QllTQ0dTeStqaWg4b0hQQjNyZW13NUUr?= =?utf-8?B?U1Y1RzViVXpsMDdIUE4ycXpJKzdqRVNFZGZrOUNBTDVHMFJZWDZBcGI1dXd1?= =?utf-8?B?K1B4U0tOM2J5SzhVajlnMUIwZGc0cCtwdDExNklxbHBpRDBOY3RxeGZQYWpI?= =?utf-8?B?aXJDVzc0YTNYZ1BMRXUyeFpSYk9rVzJRbEZDN3FpTUQ3TCtyT1g1NnBqczJU?= =?utf-8?B?RStKNCs5R1I3bUp3NUgzYTlWQk1PcnI4bjhFZ2k2VGpvMG9JekdYa3dSRGVM?= =?utf-8?B?aDhuUnNlNFBmbTNjenlkYzVGMkRaSXk4eE02RHc2aWRNTFQ5S01ycC9pWXpB?= =?utf-8?B?dHd4c3pNcUVCZkE0Zm5JL0FySkNQU0VnYVk2TWZkNmR0YUZydTBxeklXMVpS?= =?utf-8?B?ZS9mMmhNbkExQmJqMUw0UlhobjM0ZFFpOFhqL3ZuM2dzRTIwLzdoYWxSRkJO?= =?utf-8?B?UWpWRWFBVW03QTFPODIxNlp4SG9Pa0tnZmJodXlyeWhXczkzTVJZS1o5ZWJq?= =?utf-8?B?QS9BWG5PTUtQVWpBdHI0OUN3ZVZrZ0VpK014NGNVQUZCM1FvTlV1L3RIckxH?= =?utf-8?B?bUVoS0NJZS84d1puSFc5MS8wSGt4d1duMkE4K1J5OXkrazRNSzJ3WGw2Y1o2?= =?utf-8?B?VGxlU2ZmazRjdlRYYW1TZmpPTktCaUN6bnhhL3UwY1FmMDBWdXk3RjFOWXl0?= =?utf-8?B?d3FyUEJwN090emZ1OVVJTXUwK211OHk1eUpmVjFrcmIvN0dGNmZ1WlNUZ0do?= =?utf-8?B?UHhmNlM4a08va2p2bFFvM1lNUGM1LzdOWWxVdlZGaUplL0QybjZ5cFBwaDZI?= =?utf-8?B?eWJ6MUYzRHljWU9mZzFHcGdZOHZ3NXlteHc0N3RBR2ZIRXk3MnVQZ25oQy9K?= =?utf-8?B?VmJpRnVGclFnVE1BK1VvNDJIVVF6aWFpdUwzYXQxcFBuTFEya01BbHhXa0Vq?= =?utf-8?B?eUEwcXJxYnpyYjJLTUdjWjJqWU5ETFZteWJrNk1pby84cTJyK3NkMmR6OWVJ?= =?utf-8?B?OEMrblFsZmZhUFAvczgxV3hSbjZFeTRnQ21EWTFORnBjckdyd0cxODBSbys3?= =?utf-8?B?ZGk0OWhyL1BwYlFzSk5RYVJ0aUVGSTV2dXlqZ2hWMC9OZ3NVUEFlZUN2M0Vu?= =?utf-8?B?d2hlMGhtQjZERjRhRlg4MXhSSHhjSTFtMXl4OWZzT0ZORndKREZIMkd6QXJG?= =?utf-8?B?Y0lKd0FxR241b0ZIYktaWG1sWkNzUWRNZVdDZEFmNXh2Z3hMR3Z6bE9penhi?= =?utf-8?B?UzBITWdRaDV6THphRTZEQkZrYU8yS2FZMmN0R3IweGV1U2NsMHFlcEdmNlFs?= =?utf-8?Q?CKRzBxz+rawBQ3xtzL82E4DDcwQ53VC/vPgq2j?=
X-Forefront-PRVS: 0351D213B3
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6009001)(39450400003)(39840400002)(39860400002)(39400400002)(39850400002)(39410400002)(13464003)(377454003)(53754006)(24454002)(53936002)(6486002)(3480700004)(50226002)(53546010)(38730400002)(229853002)(86362001)(6496005)(44736005)(305945005)(9686003)(50466002)(81816999)(61296003)(50986999)(81686999)(76176999)(44716002)(47776003)(6246003)(62236002)(25786009)(2870700001)(6666003)(42186005)(66066001)(478600001)(189998001)(8676002)(33646002)(23676002)(3846002)(4720700003)(84392002)(6116002)(5660300001)(93886004)(81166006)(14496001)(2906002)(5820100001); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB1564; H:pc6; FPR:; SPF:None; MLV:sfv;  LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTY0OzIzOlVMaElERVZwUE1QQnZ6b0x0NHRaQ0t5Rko4?= =?utf-8?B?SXhlSG9yY2JzSStXSWhUUzZsSVhXNHhZaWNWRHhEdlFXZmh4V2tzMzBlTFdQ?= =?utf-8?B?RTgzK01INGtiUlJNOUJwa0JYMXpiYmxLdVdYT3BWSEJHQ0lsaE93YjRDb3hG?= =?utf-8?B?R2VjTWRoU1c3N1QyK1dlN1pDdUNqemVaaGQvclA2dFhtcGs0TkVaeFpVL0ZX?= =?utf-8?B?NTYvTk5BeGJZRllNSWlVbXI3ZldjdVQzREZINVIyN2R6dWVLcVF4UmtWTjlq?= =?utf-8?B?OEMzc1haRWVLUXg1bFJ4Y0xrcUNKVUVXcjhXVUZqQVRhU2o1TTdXdzZtWUtW?= =?utf-8?B?QjdCN255M25IQW9pR2EycWdsa3dRNnVHTSt3KzZvOUlucVJEaG9KVmtGZ0tN?= =?utf-8?B?UkErdVpKcnBSZDczOTdBWEVBWEY5SFBpYmZiMDFla0VqKytSK09JYUs3OTg4?= =?utf-8?B?QkRIcWRMelcxVW9oRVF6b3U3dHNTR2sxU3poWGs5M01CbFVEcmxNd29qTXc1?= =?utf-8?B?Q0hZcG9XdGFISkpJbVFzcHVxR3lDS0NLZFRUT1o4TmpGOEhCYXJFemdIcXNC?= =?utf-8?B?OVJCVVFHeU5ZY2xqZVFraEhSLzVNRUI0Mlg0NUtZMWFnOSt2MEtkVlJNT2xk?= =?utf-8?B?bFFtOHdVdkV3aktuOTBvam9KdE5qazEvcmpTdGtNODNpckQzL2ZQYUpzd2Ir?= =?utf-8?B?QnJOenlRdCthWXVVV2k1VzFzQzdKSkp5QzAzMzdPUGlDelAvY2czdmpST1pO?= =?utf-8?B?S0pWcWRWQ2Nya0lvQk5kb0VneWZvNTd5M2FCUmpmUzVhTnk1ZjRDRjZ3dTZk?= =?utf-8?B?dG05SGp3UWlKT1VjbUpvdlRJM0c1WXFVRzBmUDlSc0J4ZWhRZmROOGdaY3pJ?= =?utf-8?B?S2gxaVJiZ1NmUFJzVXkrVnUyTzAwaUJLemViNi9XUG5YL2g2NVAwcGJRZExH?= =?utf-8?B?U2dMeGpudktnVXBGTGE0U1JvTHRzZFJ5SUl2MGNzbExWZ3YwdDlFRGZYcExV?= =?utf-8?B?cFpUSDVzRHkzSXVSS3B5Z090SDB0c2RYWkk5cEw2OFdibWFzYWphaE8yZzBi?= =?utf-8?B?b1IvZ0YwVVpMbkhSa2ZWaDdRWHBROENxV0Z2Q0pMOXEzWGVXU25vQThqekx1?= =?utf-8?B?WGl6U3pZQzc2WHJtWmlZQmFlUFpreWVJVFhwR1FqV29LaU11YVdOaXJOM3FW?= =?utf-8?B?Yk1CRzF2R3JSREVwM3JTRDdWRzNvQ0xRaDFjWU5JTWMwazlxbm53Zi9VSU91?= =?utf-8?B?RnhYaFo4cmlxZDFrQVgvVTNkRzI0R084NldoSUZBWEVIYVBtclB4a05LK2FY?= =?utf-8?B?Q3AyTGlzeEhLbGppNjF5djJ0WFFjT2tTUE5aWTM0UHZKQ0RrNTl1TkRPd0hM?= =?utf-8?B?ZGpkeHVDd3I4dmE5d21ZWjlXL2N2ckdYTlNpRVRnYnhmTE9mM0R4N0RlYnNG?= =?utf-8?B?OThEU083dktaeCtlQUR3U3l0c0RQNmlwOUVnVmJrSmtEZ0JDZncxVzNYeVd2?= =?utf-8?B?VzZmK2VDc1JYSVhzUEhSNk1mTldLM0pYbWxXOVhwYlUxUlF2aFF3WG1RYkZm?= =?utf-8?B?QlFxVWZ2d2NKeFlwMkFYdjBQci9uckw2bGtIUmVyYnE3dDlsSStJTk5oTHg2?= =?utf-8?B?SkNYejJTQnU3SlZLTDk0TUF6YjZnQWpKV2k2SVQyMVRzTU9uREJNOHBYWHBE?= =?utf-8?B?Qi9IZVdFQ3hCbTlqa2RBQ3h1RjU1RVFDYlhacWsyKzE5YVhtQ0pEZVJSNjMr?= =?utf-8?B?akIzcmNtSlVjNHQ3UlFncGpEbUdITDdFV1puODVFL1ZTTkZvYzNJMWlvb2VK?= =?utf-8?Q?+TzufskN8xW+w?=
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtIRTFQUjA3TUIxNTY0OzY6bzV4QWlieTloR1M4OFltR0hJSGU2UllNNEIv?= =?utf-8?B?cm1Pa3dkWDRaYkhNRXoxa0VxMUJYaUFsMGJNZGk5OCsyN0oxYm84TW16eFo2?= =?utf-8?B?Nys1WFdGLzBjNTdtTjRzVEw5RUNENWFoWFlWS2F0U2U4TjdVNWgxQmR6Y24x?= =?utf-8?B?cG1IYlBQQ215T0pJS2hnME9IL09QVG8vTHI1dGVnRU9qUVlNUWc4Zksxa0FE?= =?utf-8?B?Y3hheWlSeTArQzh0Z3dSdm5sSXFsTDljT05ScFFRZVltYWtDNURvQ0RmU0s4?= =?utf-8?B?MnIyZWI3MnRUMnY1UzZ3ZmNVcmYzZkdISE9WVndTRXZOa2V6dm91RWk0VFpJ?= =?utf-8?B?OU13NXRBUlF0b0xCWkNpellZb2t6bDdqWVhyd0tHOEpyMXJ1VStqeFczbkpV?= =?utf-8?B?cVV1Y21wUXUvcndndFlQbG43NnBMVEtMbXRuL24xSFk5OGNrSWZRdGNRMTN6?= =?utf-8?B?MWJoY2dwWThlUm5Xa2xzak9OcjlTd3dJcEQ5ZFZyRTVXT2p2SlhVd1g5Nko0?= =?utf-8?B?bUczbk9JcWV1VSs4SzAyVU4rUTIxcWhiYVBvNWQ2NHVVUUNSdHMzdlZMK3RC?= =?utf-8?B?WGRhV3U2eWJWL1N5QnBOaEEyM1E3eGZNOUNMYk5JMTZvSG9GL2hDc2svL05J?= =?utf-8?B?NGg1OHRxSVEwSXg1RzNrTWpEdjAwcEV3dkJWSGNDVmd0dHoxY3RCVy9iTFV1?= =?utf-8?B?QXl3Wi9UU2FldTlabVJ2UU4rRXY0cUJCMFJ0d09iMnpldWQrQnhrdi9VbmJ0?= =?utf-8?B?VGNaRGVMdHZucnRIZHJyL0xhVUkvek9QSXNNMWswdHFTNjFtRlN5aDZETUkr?= =?utf-8?B?Q0JWMkdwT3RRcE45NG9KS3ZzYlFGM0lTZWlRVExIdm5Ddk10Tzh4T3FEdGRp?= =?utf-8?B?R2xBWWlFWXFpak9McnFUVHVKZ1lEYTVyYnVOdGR6a1RubzJ6ZGRRc1VrcUlJ?= =?utf-8?B?VGJNVWRoL3owb0lMZDV2Z1hXVHVkUGtwcVZDNG1MdkJBYTFBWS9rWWRZbVJY?= =?utf-8?B?bG9rK1BHODFSZGRLaUs1bkRScERNcDF1ZXhkenFwRHFuWWNLOERWUzVtOEhB?= =?utf-8?B?c21Zbm1yVVkwSW8zVjMzaDBnLzBkYUJvNzg3ZStIT2VQM0NydkxEQ01TTXpI?= =?utf-8?B?Tno0ZTJ4UVQwbnAxV3NkeVdod0N0U2F6Rm94bDByWnVvV1V6UlNxOXNwUDhz?= =?utf-8?B?ZlFMK2JBRWw1VmQrQjVwbmNpU0FYQ0tJL1ZDMmh4dlkzdHlZWnhtVHVLQXo1?= =?utf-8?B?TlU4R3VDMDB0ajYwcjN1cjY5UVhLd2ZnS2ZOdTFreDJtNjJMSk03eHZhN2Fw?= =?utf-8?Q?WJkhsfDu9mulax3Usr3eyc7dlLs8ECg=3D?=
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 5:Lu7drcZm2F1swnacXkw7wY97JEYqF82zsDfNXDlBUYZJRqR8Jatc4fip2xZA3sdmJhn0Ixn++sHVt8GB8iR9PJw0yOhu+jXnGCY/NP4hX4rMdrPbLOv8eb59nixnND5nIn1a1/B7g27MzAwcQR/tc9cBr92Ne7nRS40TuP36wHdYHOmY3EhXjqRP3Eh5erhhnTTVHGxJaV3PYYLGPgjWuddGMGjt3beoGKZz8R+Nr8Dcty4j+ieDMgb1wH0FU/It4M6LlVIDDrn45lIVaGkWCtGZNw/ga2dC6fPNm29rLrLf0BPYm46Ndpz/mUkQ5wM3HtJk/ps0NfrvTqobRN+KQJkPFl2MD5rn555ehs9KW8hkUmxlt046Cyb08Ren6LicNxU4ZtUPv4eOEjww9F3lddakK2Jqc17wHEi5Xo6e8JlgKokBwNkrQPmPOh0A/y2rquBi3UUXQtJXPBgIKbjFxCIEBZ/Xj8ko/0IMgnPfyE2REe2PCgwsUElW9om8m5AV; 24:dRccqyd5Gxz1MHWiB/ZOYOPxfyqrjTlMEppUZXpU/XdmXHEwmIUcYk1jHzerN6dai8xEe3QnSzhJqOMZIK+H01N4IMS2PBvzP/l+85TTiYA=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; HE1PR07MB1564; 7:jlHTwNNBP+cE6+8ApQo/41Hh9emVKObhSlW5Ksap8/VmxMPrGmSqLLsWNgNfspfL0LYn9aKRCdnzKVy36Hd19MVkR6vykkVIhGegc3JKI/VQhTiUjZMmay9ThHB+0rIKL+yk//cADTYgVhdJHtiOAXg0aQ+qjVNbsbaryIEEdN40+oGzD/sOv9Hg4by1tuOYKZXlExYlhiKeFZXTbCfkrRqtThaLpKjhAzDX337TW+jOFXRXs0EqlbohygjkBer4ssGPltCr5cXpOxZfvLKZcSyCuu9hL5eH8Klb4DvT9SBw83LzoOAJpzeh/PoA7SohDtG7GF0N3PGzXb6ua5S+FsUiIeKmdqYfDR7iSIV5mTNx86cebJ4vaG+Xc3d0PjkzbbGO7J1Zeshc9Zma/uWcQJl3z+mq5mTSXS3uYEIk+K3hFpBdQlbehjmUJMe+Z52LbZzKHJ0ASU9/0CG/RgFt5bjslKBHIGL0D2ltpPIjcRA4ENDACG98tixXrrIrpG4WXwdQDIcAY4W22956/WDbQEi8cLo+nP3FTEV9gGzEZJftsXTyqLv/6JA+1cHdK9Bl98IXk4a3WlayPAP497fDXVHYI23MnYw0n57goQuRScOly+iEkv/BtEy44qH5IezALjWONmIP3fcZmBWuYouYvQxQe0DwuVlSNOIET7XGjFLr2HtIcZrvHKBSwpElKmGR2gfilv3ZjEdXFdTs9OwaUA6oqW8UP2I+I+h/gzT9G/nW3OTJBzwGwTwPQbIBzn61G7BsJk7S55cpgnYXJnbbu1bbFr/tt4VTq9RoqnWWE1k=
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Jun 2017 09:01:04.2523 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB1564
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/4db7ljHlbgEtbQmlMDQcgiASfAM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 09:01:12 -0000

----- Original Message -----
From: "Eric Burger" <eburger@standardstrack.com>
To: <ietf@ietf.org>
Sent: Saturday, June 24, 2017 10:03 PM

On the one hand, I won’t be working on Saturday.

On the other hand, as someone on a limited budget (read university)
paying for someone else (read student) to go to the IETF, that Saturday
night stay has a big impact on airfare.

So long as we don’t have Saturday creep in as a ‘regular’ IETF working
day, I’m for the change.

<tp>

Eric

I am not sure which way round your comment on budgets is intended but
for me, staying over for a Saturday night makes the transatlantic
airfare much cheaper so I always travel on Saturday even if there is
nothing to do on Sunday (except deal with jetlag).

Friday travel is busy and congested, especially next month in the
holiday season, so I would never travel on Friday.

Tom Petch

> On Jun 23, 2017, at 1:39 AM, Tobias Gondrom
<tobias.gondrom@gondrom.org> wrote:
>
> I also agree. This is good idea.
> (with my individual hat on... ;-) )
> Best regards, Tobias
>
> On June 21, 2017 8:46:57 PM GMT+08:00, Bob Hinden
<bob.hinden@gmail.com> wrote:
> Alissa,
>
>  On Jun 21, 2017, at 3:34 PM, Alissa Cooper <alissa@cooperw.in> wrote:
>
>  Hi all,
>
>  Based on a suggestion from Paul Hoffman, the IESG believes it would
be beneficial to denote the official start of IETF meetings to be on
Saturday rather than Sunday, starting with IETF 100. We believe this
would be sensible given that events such as the hackathon and code
sprint start on Saturday, and may make it easier for some participants
to get travel approval to attend those events. This change would be
reflected in the dates posted on the IETF web site and sent out in email
announcements. We are not proposing any changes in terms of the
scheduling of any meeting-related events, the full availability of the
meeting network starting on Sunday, the opening of on-site registration,
or the meeting fee.
>
>
> I think this is a fine idea, essentially formalizing what has happened
informally.  I suspect once in effect it will push the network to be
deployed earlier, but given current Saturday events, that was also
probably going to happen at some point.
>
> Thanks,
> Bob
>
>  If you have feedback about this change, please send it to
ietf@ietf.org, or exceptionally to iesg@ietf.org, by July 5, 2017.


From nobody Tue Jun 27 07:28:06 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 D14C5129B35 for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 07:28:04 -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=cooperw.in header.b=lqLpc3w/; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CdnjdXbJ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id itJCebOrKMBn for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 07:28:03 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 491C6129B44 for <ietf@ietf.org>; Tue, 27 Jun 2017 07:28:02 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id ADDFC211DD for <ietf@ietf.org>; Tue, 27 Jun 2017 10:28:01 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Tue, 27 Jun 2017 10:28:01 -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:subject:to:x-me-sender:x-me-sender:x-sasl-enc :x-sasl-enc; s=fm1; bh=Vn1+edLTOc/XU+/vU2XOSv2cvAW8DIjjHymkfvS+j QQ=; b=lqLpc3w/L/jYS63tB50Z6KkxiroyLPNbyO/nNRcWRBwvCJAjL23BcVAiz sLx+Xo1mXgsjz9Y320/d8eZ3m4QaskLvL3bKiAOD0iv0CxJ7k4turTS9tPnKuXAv TXdNJg23WiQgiZ324dk5nqSyhnqItAlkF1+eERiMsoi7XhtyaXJAvG3vxRrNHifF uyun55i2C0QRRe3ijP28JZR6B/WFX07JO0thTgithROPa7FDQz4kWV6fQ8zK+x8/ x6DHvbVJOE6A2G+aV+vJZv3UWfY+esZ19Ye7OMFSghF3SWqwXdcQDF4YAhWjI73n bR6GIuEQs4vTXCcRPF+L0Eq/seBrw==
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:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=Vn1+edLTOc/XU+/vU2 XOSv2cvAW8DIjjHymkfvS+jQQ=; b=CdnjdXbJu5Ml+jkmZMt5SELss9t5kpV9q1 mCfVo5hByWcMPzUahBQthStqz+S3H1brVt47RZ4sbzhmxO6Lrh/Dx00xM19DMJNu frUf1nLHLfXYPcdFyIAnEk5BRb0M6ZYQRwqLd+B/JCrcykk2YGzqxV6JN8es10V9 C/mNzzZSDGequ9k2hquXUdj+DV0P3nHos0BIipdNnKIowKyCI/q1gi5YTURLM2Hr OQv6LF10UxOut0iw5uidWtzQXjNJVw6wN2u3zbhMaDvzRrsqNvvBq3RDwsEDZiSV YJu8QGwjIE8Srqk0jJqv/7QxaF010JWi6x9AgBipNz6gw487ureQ==
X-ME-Sender: <xms:cWtSWRcdoo0L5ppkWsucnx_XNaiJjTvLVIeV5asKWFgEGtFRZrsajw>
X-Sasl-enc: nPqTYGYq+m4uV09ZRnw+SOq4CuDiddxEL5kKSonP1nze 1498573681
Received: from sjc-alcoop-8812.cisco.com (unknown [128.107.241.187]) by mail.messagingengine.com (Postfix) with ESMTPA id 2D8E57E5C8 for <ietf@ietf.org>; Tue, 27 Jun 2017 10:28:01 -0400 (EDT)
From: Alissa Cooper <alissa@cooperw.in>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Maternity leave plans
Message-Id: <14CBCF3A-526F-40F0-B9E8-DF8760F7B0AB@cooperw.in>
Date: Tue, 27 Jun 2017 10:27:59 -0400
To: ietf <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/SMYdtfIrvIayMBtykyqTSTBSilY>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 14:28:05 -0000

Hi all,

My maternity leave is going to be starting some time within the next =
month. I will miss seeing those in attendance at IETF 99 but look =
forward to seeing everyone at IETF 100 and on the mailing lists before =
then.

Several of my fellow ADs will be helping to cover my responsibilities =
once I go on leave. Suresh Krishnan will be chairing the plenary at IETF =
99 and handling external communications. Mirja Kuehlewind will be =
managing the IESG and shepherding MTGVENUE. Eric Rescorla will be =
handling IAOC and administrative matters. Others on the IESG and IAB are =
also available to pitch in if necessary. Many thanks to them all for =
helping out! I expect to be back working full-time within a few months.

Feel free to reach out to me if you have questions.

Alissa Cooper
IETF Chair=


From nobody Tue Jun 27 07:42:51 2017
Return-Path: <erosen@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 0322B129B39; Tue, 27 Jun 2017 07:42:31 -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=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 66yV6WF2naLX; Tue, 27 Jun 2017 07:42:27 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0121.outbound.protection.outlook.com [104.47.40.121]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4C7C9129B36; Tue, 27 Jun 2017 07:42:24 -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=NpwP6VB91rsV6D4E27QdxVpEt7NI8VS+ClxA+Dtrq+4=; b=C+jJCpFr8wYlpqzGnEL8eP8lfbJxaMMpjQAw4Pnq89T9lp2XLcFbbdUAiSNC2tN1rLHell83rCuC0OKgWw39NI9bhBiDCMzSNtdV4pE5FnQTxhxLM4lUTUXrdRRaFpZxeq4V1dN6BWJzWo9LFW2ouVUWDMOT85Knd0W69LFtyBo=
Authentication-Results: juniper.net; dkim=none (message not signed) header.d=none;juniper.net; dmarc=none action=none header.from=juniper.net;
Received: from [172.29.32.126] (66.129.241.14) by SN1PR05MB2190.namprd05.prod.outlook.com (10.169.124.138) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.5; Tue, 27 Jun 2017 14:42:21 +0000
From: Eric C Rosen <erosen@juniper.net>
Subject: Re: Genart last call review of draft-ietf-bier-architecture-07
To: Dan Romascanu <dromasca@gmail.com>, gen-art@ietf.org
Cc: bier@ietf.org, ietf@ietf.org, draft-ietf-bier-architecture.all@ietf.org
References: <149838804788.3251.829139224134758886@ietfa.amsl.com>
Message-ID: <7d872d02-4154-989d-e83d-4d7408cc6073@juniper.net>
Date: Tue, 27 Jun 2017 10:42:17 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <149838804788.3251.829139224134758886@ietfa.amsl.com>
Content-Type: multipart/alternative; boundary="------------E498FDE51A985A384882B11F"
Content-Language: en-US
X-Originating-IP: [66.129.241.14]
X-ClientProxiedBy: DM5PR21CA0011.namprd21.prod.outlook.com (10.173.176.149) To SN1PR05MB2190.namprd05.prod.outlook.com (10.169.124.138)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 47696ead-1489-4ef0-bb56-08d4bd6ab8b9
X-MS-Office365-Filtering-HT: Tenant
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(48565401081)(300000503095)(300135400095)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506067)(300135500095); SRVR:SN1PR05MB2190; 
X-Microsoft-Exchange-Diagnostics: 1; SN1PR05MB2190; 3:CQXVut/TuD2ArGfSf/Lhx0G9L3O/TcBmCy2ODUxH9DPTDVRLkdiwVcdGYTJLH8FooGTQJagIxfjlMNmGqqPIwc4maqp800qOeBPUR1HYGYgPGtKOSps5pvathw7aeXWx2IGPbU52Ipk7vIKFUhTNCw8pHbHkaSdtf5iqYuQkBKgvkIJAxJ4AuIvz6MAwRUpQXyy1I0G6q9whPHfBePdr5z12dqxigoZlw92CzBeaQSrF1jBG0z/ONTHS2kS3gwN7QvkWusQ2lwnwJxS4tw0j2V1Ka2fcWDXwH2Dxiqms67F6LFOGHXyh0ywrzWFTDEXS3Nv6Q/u6WBlrphgKJenIBjImx9wmE8+nQSk74Hl1qOlZrG2V3FDwYqGkr+4+WMsK/W1QfeHhGHqsltaHx4/V1T8b/xQ9zkPLGDKlg+OuBodytzLrn9QQHHU8av0tcbaOAj8cmIImbIbqe8a4S1o+Gej+hd5rUSFyJRkmNnsZxXec/CssAZ3Aym0fh1G0mz8ejrQ96JbO3dJ+fWfDqwR5xuRQzA2SYHWO2AC92IqXVaZ9NijCM/crfv4G6ec8JbjLq/RYqhaNufhlx//TA07/Whz4zkaFEDS4T1SDXXW4BTouZjaYfB+sypwU+bLm2B5NctccYBqdXkDwaF/OMMI1IfsmgXJtgTi2TIpwMlMr1e5JzOlRxIlBX/YzUiOIgWfj2xM7IV+CL1JOcpKuOW8l+F+0VppkEeb4Y5QJBWct42bL9OctVIRpepDPZvnoEpSgwciuG6WYkwHtFaKj6rFcNQ==
X-MS-TrafficTypeDiagnostic: SN1PR05MB2190:
X-Microsoft-Exchange-Diagnostics: 1; SN1PR05MB2190; 25:O6UXzrixNWGKN8b28x+stOr4ZicmuHxCoezTQKS8O6bdY8A9UQbPgWp3tzSygDRPaVx5virOTLCrGQMuf1wJtwQpPPWJ3TFp+9Ujw9OCbCFk2iy2ipuK/PY0Q5NxAQ018pPr5x1BipmAYiAglLd+uc/jD6rPOzzbBe6RWoprEuX2/IrGZC8N+bu6821iyb9nkV3HrHDnat1FcWAjxTF9OqjcR5d2a0jGpPd8RXGCxkKW/ABQsl/6LtzL9aB3a387SJgxwMfC3fCVnnP4WWni//BHOcjRAagpFWC5qIKHqJ8CqhCksrBi9v0VUQQX440VDyQVwajt1/k4gV4dicKyCmm6lJYsELyvI/v58lnDMTDcoCJMR+eGkCWEelRoaS6P36cA8p9cqDE5kgxYEF3R7MW/MIIcAPYYftAdPH9O3dFfcz0cyz2MtG2RmO7pbhmkKZkf51jZVIEKyB4JETEYSOT6+2WTCMRzkaNyJpx+szCufcjumSyrhlJlK7cZeVA7+zg59UxlGiVP3X8oasM8afoJtcNJlZvlwmybtan4lIR7NE3c2jAQE98PmCUxsJFY0zqzvhGeQFT7Ey2EKFTHnYjIZXzRYNHuZLJqJNvoYopr2zYT5PuVA4vUjz7EUugUD9lqZTX30KP1F9bQuuH4EM9A6ien9ATctYWq2H8rECS+h5vXeJSCmD0R7XDvbUgdML0laihEmgkON6ukrxz4KtsLJcr/aXiqX/mIoljb2CzTS5ooji10gW2ZF3fEkeget2Trf/k+V4TYlhLx/FZb7Gn+ZYG5nhfobQLluq9r2TXcoFh7cw4o8Awu+rMYBq3HQTAHiRoflEKfnGyGSPTuUlrj6PT6GGyyyaCmFAwm7a4bww36meMBULQrWABfhyFeCos6eUpzSzI050kMnRJUuh8fSl95MzEGhs0JU/eOBOM=
X-Microsoft-Exchange-Diagnostics: 1; SN1PR05MB2190; 31:qd8Q8/cCdTATCxm14yezT0iRa15vGioFKXEfudbD0D4NlLswxpP0rNGQ2id+1Ios8MFe83uo5hlhshUAIyup3/Qc9cGu5LyEzqU8QOLauS60rO7yz3NXKEWSJtGjF+p5SkqlcVFAwX+AfYKTzcFgtQabteVdv/ko+sFGQtQe3KbWykIyRW3zgcCUDu1zIHulG93X+qOOZxuWIqwNJ2ZgyBUgoKxRV9xd7Dwv4BtwSZljVF0c8k6MOSAIa1DRhHgqk2ObIfAbWeWOyuYZBq2bvewpBbSB3SWG2yf6ysrwXqh/8kyCohNZKJkQhBpQikjLDQ2r0dEJr9crZB2XOP13Om1zQuDSV1LDABSjR2Lu3/mvnhbdCu1RV9pHkbfanDWon0I+psk1lRoPQo8A3E+6RCqEKmZ/Fpls0WLOtlpCZ0l5a6ekbcbCMXMIIu+b+BH8QwzLrGZ28bwLsknjIm53q1Ik4woN6KenuToWrwfjh5VMMxIDuVE6lJZnuRqz1NFX5qWbKUS0d9htsHKi7Azg3DYq8kxoFP9v2H58jriE/2DKzZdPnmMZSeZYU2waL8x/EKbIXOWSrskCptnHSccLRsZtnvu6ewZQnDzhW9/O79XR4se/F6trGEVDUJ6z1rl6+c463lKP2+Zi0YPwlYS/a8011OjPfFLPh4P4VW2JOMs=
X-Microsoft-Exchange-Diagnostics: 1; SN1PR05MB2190; 20:S+SBNyys6ColhxADPmT9U7gp/VKphTtND+EU5FMjJmDZ4p7bX+Uc/Yl2XY4iT3aV3M7b6oXveyepD3Dl+NKAcrjQ4KDSN/64lp4mWfqWz2cmj3yBkNKzvy9vuVtPa4m59rbdBwTby93sp538hLzLKd3Jx2RaWomwbhy9ohP4mxN67gjsc1N/MNxVkefz40oIfONXtBq97SBy5n34xY1AVtfdK0d5dyIOV0T12XC2+c0QI7PwPFmRftySiP/FDrjGDxNH2uCCXeyvuqAVqqLGcy98VV3wMZg8XCvS3oyzzE3D6putZGVODL0moVPM4bWQgSx4jXS6kcO/afjxWMmWZ2tucc/mzy8tWs8YqaqHUYzQ9qM7/R/IC5iKwHceGJq+sEq0cOMro7ubXuudahpd7oQWj/sFtoan8WXKr3/PGNBzAaZGbWGVitn150oVLQhKiO/6j1oSSdDS0Q9vkTGsI0ajD4IFmErlbbfL9b0s6odUw8j1+7Ps7vQC199745ksqzj5J+Lc5trSpv/lZDdoGk/CIDb8ZFkaVUM7x5YHxFKcvZG3fr8iT4CDVDlYS0vZjtXwsEf0WyjoObxaK4dDT68/p+Xlg6WA6Lh7Z2qrZK0=
X-Microsoft-Antispam-PRVS: <SN1PR05MB219001C8C19C51F3C62E1982D4DC0@SN1PR05MB2190.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(278178393323532)(236129657087228)(148574349560750)(256282310955234); 
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(100000703101)(100105400095)(10201501046)(3002001)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123558100)(20161123562025)(20161123555025)(20161123560025)(20161123564025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:SN1PR05MB2190; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SN1PR05MB2190; 
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; SN1PR05MB2190; 4:NJy6EktaQLcALkDRtnD53+5Eh3p17k7+50f3yRryPs?= =?us-ascii?Q?nRkakkyIv+2bZr8IOPd/NGriMSqr1n4I+clGl2BreWnWS3fDvokbT2S7Ax07?= =?us-ascii?Q?18lwq3Gv5xM5QKmGv2E5S7BukQYflv69sSUqp3mD7YoQggCxtla60PvCfkj/?= =?us-ascii?Q?0tlI7pmxppzWtyArXhCSnZqPbHZQoCXyZEFjaYlI0qY0u1m+mhctukrdUoYe?= =?us-ascii?Q?oo83MQUKWY0x6Zpxi6fuUg5TO1Jm5BkmUz8gbTyqFDh0+QBiVoHMn3s+Og9G?= =?us-ascii?Q?EBMpLat7ymBXvsSAw91S5OXszAlZ0eRgq3rqEK8amxH5gYF3sEwHdXzDG8mc?= =?us-ascii?Q?8bxgBTdo+1rKcUmx2MzEAk0YI2zfNcplB2J+A5Hc4yuK8SkmydGIZOua5a0z?= =?us-ascii?Q?Uk46u2/mk9RkxtzzHX35WnWh6s93nNji5/WCljrYk7yU5fR1fgGGEqaOjbnX?= =?us-ascii?Q?aHXUoI0nm4pcxrVyJwYLcmXzDxFFUySFJKUfanm8eez/EWvN/mKlKQAJxlSf?= =?us-ascii?Q?RBz+5b+RB3a6245FnTV2nmtBCmUpJmrO7240qOT/g/7T+dctGRFaVwMAYjhm?= =?us-ascii?Q?XFjGqh34ssOvxjur2WShMWFmr63xMc1PImsQbn5TqDZfWahKkdIbyoI6biZq?= =?us-ascii?Q?jvIrnFkvq0kvlHkkifV4A7BRTmo6syfMr8MJlyTguLhrOoyyy/LJ427r49u+?= =?us-ascii?Q?GUdv10ezRNwJLStMF8SYXv5bpk3gxjeXT7LR83qA49DJK4t3cYvwT1vCtMWO?= =?us-ascii?Q?nsALEQlenzJ1nKucVqYBgtXOTVKJ9gQWrh8gkROpRHO/RACwyqmUNje6Pyhn?= =?us-ascii?Q?WCQIbIbBy4QV6SsHZSvjJ2gu4qYZ33I8DiMLZOFZaLKZeZdTtMie7+f8U+mE?= =?us-ascii?Q?ODrqgWj99RUhvgxKpY2cr6RFAiGbqGNVRTCWW4Tb/Oq36lviSxnH0vr64tKJ?= =?us-ascii?Q?nTGsl0FtrGD+pASfN3+61vSLx4ayQZsyDVjvwDXkhqbGOD5uN0kbdS55appW?= =?us-ascii?Q?9IsGxIju4mQLMu2SG4sJMZwOX/pnU0w0FBB65FY8pfd0pOEfgCnh5OKVSxbq?= =?us-ascii?Q?brCsB2DJH7R4QQa320xbVUEqph+KCyEOvwk5od2BOqjCTpyXthyrRWsMMt7+?= =?us-ascii?Q?sLvWvEEaWXsGowfgZaNJ7rfPydW6jkzl4OK0qx6MY1GdrySXPZ5r1qGudLxZ?= =?us-ascii?Q?d3WOMwkcO+wXd3du1mFZshWZq/PJRClvdN0ZsdB6vHPDZ4G1MwRp3iAHg15Z?= =?us-ascii?Q?EbPEKgRYq2PzGy8/P37+/T7bRwRTcFadqOYVeFcjpyPJZUSGEGRXm54SqyD9?= =?us-ascii?Q?3ZKClBC15Q+JvoVslTWCc=3D?=
X-Forefront-PRVS: 0351D213B3
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6049001)(39860400002)(39850400002)(39410400002)(39400400002)(39840400002)(39450400003)(377454003)(377424004)(24454002)(38730400002)(2906002)(6116002)(3846002)(65806001)(66066001)(64126003)(42186005)(36756003)(33646002)(236005)(53936002)(54896002)(6246003)(4326008)(110136004)(25786009)(53546010)(606005)(478600001)(7736002)(90366009)(31686004)(270700001)(7906003)(5660300001)(81166006)(6306002)(6486002)(230783001)(77096006)(189998001)(2950100002)(4001350100001)(6666003)(31696002)(229853002)(84326002)(76176999)(86362001)(50986999)(8676002)(83506001)(54356999); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR05MB2190; H:[172.29.32.126]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; SN1PR05MB2190; 23:hPzSG7Dw7OLuRe32q7qziVMRhxxj9VVMtnRHDa6mG?= =?us-ascii?Q?i9zp35AfqzLZqKutxNSV4GqAb7XbEaiRe13nfeIeempalxF5TCwCsWEEWod/?= =?us-ascii?Q?KHD5GywikPaschxduf9B5EVmxN+oaHjmuoJEG0BKT+LLfl9Ku4M2Vg1+8nIv?= =?us-ascii?Q?QLPoEDiq3XPJwbw3cTWJPJ2fFsAL4yuIfnIq4XSWpPkBybUxlUbbq4rL7aJI?= =?us-ascii?Q?aElyfE3TKu7iXsRj6+8okfJ3tkz4k6FfGyJh0AIIZmQCcUT5Sd7YIOQre9yy?= =?us-ascii?Q?p7ClEzzVh2ZXu1N1oqpGwDkbbabZe3gxB9TpGpHueBnv83/BntYFP7oAZbvA?= =?us-ascii?Q?VTZQzbpfdY4qF6Ey21zJsiJU8A0NeepKELOjM19vzCUJUX1F2/MxwAALhWwU?= =?us-ascii?Q?Ykbe8TA77esjQ45cdux6qgkFSvhNDkT8swYvc4DTxc7PYSErIjJiN638EmNL?= =?us-ascii?Q?TYmYRf5Bas3kmdftHhh0oD9r+Gy8bVNdJTJdKlQHVUjSIJtYheK0R+Rr2Mqb?= =?us-ascii?Q?aUhCEe+hLwy4U+rRpSrUFkO+SD+0wRR8FUDUgYhqAadfY1S3R6B6dvUXJX+Y?= =?us-ascii?Q?yMNxht5tvA3KKKqiSnKCUszIYKmuF62lj0Icz8QbJc0wfsQNvoA6hQzEHfG1?= =?us-ascii?Q?MGMrKpXCzGe3lbrpzrKUbKSzrmVXrGhBhcF05EfqR3SGK85GhsMvPOXKSlYA?= =?us-ascii?Q?HxkYvXJzm3kq/pkU/1PdeEJlmfCif9jnjLNlePb+bWMfDgRVyqtwbsnRGmZ/?= =?us-ascii?Q?rF9hHokWvHF91aBDDL4kA+ff+seWayNbbAWHNXR35rPFfVjr5ZtPYdlLzXeJ?= =?us-ascii?Q?2ogefVD+iPF0Rvw0JqfXUiAoHQ30boKL16jDsnJlBtwV39lHmXynUENW3nHU?= =?us-ascii?Q?cDKNzmUWxKUM1DBoeLFFyYHENN2/w4kOsTnnVrAMcK3j7HSmYYvrl4L726nz?= =?us-ascii?Q?0KamSI8mjGSYMrVX87LMJNeGRKuZg8VbwtT5ilfMKpsGLRDNF6D1w7H10llm?= =?us-ascii?Q?q9qs+7Xwk8EHlYXOd7BgLvRILamohE3TEHmzmMikNlpzv5KPzrJXpcjwILFf?= =?us-ascii?Q?1HgEgsbmzANCpFj/s44Kg6g4g6+HDqhfuU3kr5y1eH9xXnlep21tOn383RaD?= =?us-ascii?Q?OyQTPNTlLpsr2+cIBGjvZ+J427xd8qokvIEAQD0eDtA01ruFO206xjJj4XDU?= =?us-ascii?Q?ZbiMyJWySbyTDweZa+IuFc/YolAQ2JG7H9co8v5cl/U/HZPoPvNShuSk40xx?= =?us-ascii?Q?vYgr1bURFwj4vQfBhuQC3xvbz6mavptoy4mkFt3VC7bYxdV6+U9K1hO9QTZN?= =?us-ascii?Q?BTWExi5j2DVS30I0sm1dVrqaDvX1z7YvvZ/0xwCL5Ti13iX0OgjRD0+unucV?= =?us-ascii?Q?1iG8A=3D=3D?=
X-Microsoft-Exchange-Diagnostics: =?us-ascii?Q?1; SN1PR05MB2190; 6:GdKNjLAvMnLHWWP5wb04hfSMmxH1UGwmylhOvR97Hf?= =?us-ascii?Q?dR/dDPrqKdobzbfWQsb4miipD3j+BzlfzQE5OAQB1xyLHVtJtxvgudbZNNzr?= =?us-ascii?Q?RvD4nJ5kFti0/A9ELMqk2Bo1nHYTbWmoEf6w+9NjIw1PqzndK+XFo1DaiwJs?= =?us-ascii?Q?MH2Lk46cCxCDAJpbRnGaZIBiYoejDD0ejnTo7tv29vYzgNmyYPY1CLHov0DF?= =?us-ascii?Q?F6OP9mrg+47TLIzx46RRIce5xiOJqxI7uAnima1uPYT+OtpJnLSrVtcPqSag?= =?us-ascii?Q?rAMdojlNgOI8NGHBMIFxHkGF+7FDJKQzZ9em4airaYTOwBN9hGHeO7iON3Mw?= =?us-ascii?Q?ALCxoEnb5XCZt3nGhsVmT3zfAOUW2bU7GCj5DTwaguNTd6a386W6uBol9iG2?= =?us-ascii?Q?t0cOwGGckstWxLdYHHN0yZkJyYKZYnL3GISCz9CfDTFWHTQ0zB1nx4XCq5d4?= =?us-ascii?Q?ukySoYdb3KX9TXbJJuNvas7vAprYUrTwp9lmz+R2kMKkx/6zdZi/rdnG3ZU3?= =?us-ascii?Q?u7yGQakLE7swNDMNhkMGiB9evmUzMekJgYWEbW3vztUsb0U4q+t7j3gi7q2p?= =?us-ascii?Q?BzsO47hLY0kjcPpnhZJQgQ5lG2rZ6w+uCgNldcXDse/8/tak8XVfPECEHhIy?= =?us-ascii?Q?1NCX/UfU804hXoFo0ckT93fDRPJ/M3h0mHUYTzDsrmdhxrZMpmjXmC8awUoS?= =?us-ascii?Q?zaEKYTe8TtxGKarS1H3rvW/KPLx0ottc2sN/MRKRhvxpgtFrFG2vvcEXNI6W?= =?us-ascii?Q?ArPSUlpif+pOXeFJzjgXWgyIDLNsh1Bj5ZVgAoKgLc9gmKBvV2IaUdhRrvUb?= =?us-ascii?Q?NU703NiiMssw0yDOpTiTmlZHwzwKSDNLNksiHPe2/Z7ITwL6yrT2DpvL2Z4n?= =?us-ascii?Q?oleuJTVUBKUgGEoZO5vSQFQkJFc/4mIAmGzfTNw9OMDfqFAdyZx6BzeV+64S?= =?us-ascii?Q?+yVsGEk0SmWbnKVM+Ri0GNvkR5V2MPDXRRI9k2qp3omOpfHJLgK/YeCfQhc4?= =?us-ascii?Q?wwKVh7zj8001j7uYwmH2bS?=
X-Microsoft-Exchange-Diagnostics: 1; SN1PR05MB2190; 5:x8Va6z7bpCiHg9nmA8WLo/E4BRDQC/C7YRZz4M82sgENPZqPjrXj42UvEpR8T2fA0fgucBVd8tQv18BxC5aHXIhLqhy8mxzkRGF83yM7zcfXf53D8m1+NTovGywIZYRbz235OvXBuuEc1LqC1X/ZSGp+cksYOLeCOr2aJM9pS427T5ZLtCU1E+OZ7mBGgkwkiSa5EXdfc/wnvPssqMT9RPmG4pb/Bus+fOdtb7c6nEsG2HRKf2vofHJq40yXgMWfWnhgNkEEgaRI2nZ5hjaEWo8z4LKQgOXz21izWUETMlQWXloi9I7wIdfu4f0RF0OrcvMXGvc2DGeYENSth65kJuceR8b1xvpPVp+3/DMn8sC5KYkVXt1b5yQl1uHu3pyR4hSxU1D0MqUsRMx99MdboMC058nybXmR9+pOrWOB2umwfdurhqnSHdYUfAwYRgOFi7BvrwvprhC1ReEL/BcIL18tMnh4y3ftpaF/92knY2TzGe5aj2b2mW1dU8b2r06B; 24:1chR2lblZ9dLDKwKgPF5U4G5biUIOARU9JJvEp2r7Rd2/aaPY4ZciX6svKtNguVGX6iyf8R4SKBoRoMHV3tpOmow/5ZTpddF0Ie93I55JZE=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; SN1PR05MB2190; 7:Zg+OnE9jzJXriCZUUtG4BDiq1xyYvCDa6BhDiIh78nAVuwMlEibzDPE++yF8DAjmPeEnipeH2NjQVI2+jG9d6hNFr3Cw23yEXlnKLtc29u2egAo//sZ+0qsjmtycASNf15NWC2BZjsplpJIpX1mKM6ekHVlQvdQ3d1AGgnu20yvZzjSc+HTYR2W7pc/EJK+IYb7CWgbA1pgQJba5MGoZtZwRSgY4S2rxeG+EIyTusSKvHmQPERq1BIBbK+KF1xmUu0UGTozqXalXU0QJf6jhejCvq/T6ALanjG7egdjSoYPN2WkpIS9TgLZS54pY5WGDfU8ZFwnJUfTB9CTK2UIMOr0WMjQWQbjuCCaYtKRkWX0QKvk0oZMV8h2aR+Aq1t+JzOY4qX/52tsD4Hp372BWkyZXvD2YKNe8W8bUaNw4iRPd97TjV7QzVSXWrQcHofxQhs1gPAEeTCtSXok/lMZLVJF+NAihRO4ZYNZ4LtgjGvQwXsiFmDtjNKYAB3TCSqK3OULO5IK0uj/mnEau7ISVzUVvQdIBcFXhe0TvKgcKP+1jVR3bTD8rZd5H5sBnLw6Y7nsLAkpz8YKi+TokduWLBnPqKIg4njHJqfmo0X84otReLi/CAkT6JhJkLu4jMpH/6wy4uFhAnt2uHuwX2PucpL1agrwf5MKp1kf3ZvNxSzKbGI4B9y4/qjWhTYQqhW4+tcaz9LKhS9NrtNnMbRFshQ0UWgboH6djwi3aBUy9MY1/dOsJhbzecBQrsxrGRqke34bczG3fGWoqTRgif2G/DncodSPLf0JI9axkpf/i+zg=
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Jun 2017 14:42:21.8195 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR05MB2190
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/SRk0SLm0mhcq-34WWYVSV0xsr_Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 14:42:31 -0000

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

On 6/25/2017 6:54 AM, Dan Romascanu wrote:
> 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-bier-architecture-??
> Reviewer: Dan Romascanu
> Review Date: 2017-06-25
> IETF LC End Date: 2017-06-29
> IESG Telechat date: 2017-07-06
>
> Summary:
>
> This document specifies a new architecture known as "Bit Index Explicit
> Replication" (BIER) for the forwarding of multicast data packets through a
> "multicast domain".  It does not require a protocol for explicitly building
> multicast distribution trees, nor does it require intermediate nodes to
> maintain any per-flow state. This architecture is .  While the Abstract and
> Introduction of the document mentions Architecture as the principal scope, this
> document goes well beyond the scope of a typical architectural document.
> including detailed definitions of the procedures, terminology and normative
> algorithms required for BIER.
>
> The document is clear and detailed. Because of its structure, I am missing some
> information that usually can be found in architecture documents. I included
> these in the 'minor issues' list. Although none of these may be a show-stopper,
> I believe that addressing these before document approval can improve the
> quality of the document and of the overall BIER work.
>
> Major issues:
>
> Minor issues:
>
> 1. As the document is targeting 'Experimental' it would be useful to mention
> what is the scope of the experiment.The charter actually says:
>
> ' The scope of the experiment will be
> documented in the output of the Working Group.'
>
> Would not the Architecture document be the right place for this? If not, is
> there another document that deals or is planned to define the scope of the
> experiment?

I don't really know what is meant by "the experiment" or "scope of the 
experiment", but I'm pretty sure it is not relevant to the architecture 
(or to the forwarding rules).

I don't know if there is another document discussing "scope of the 
experiment", or if such a document is actually needed.  That would be a 
question for the WG chairs.

> 2. While the Abstract and Introduction of the document mentions Architecture as
> the principal scope, this document is different from a typical architectural
> document. While it defines well the procedures, terminology and normative
> algorithms required for BIER Intra-domain forwarding, it goes well beyond the
> level of detail that other similar documents go. Specifications of the
> procedures and normative algorithm should be mentioned in Abstract and
> Introduction, they occupy the same or more space than architecture.

I can add a few sentences to the abstract and introduction to make it 
clear that the procedures for fowarding BIER packets within a BIER 
domain specified in this document.

> 3. On the other hand I am missing the relationship with other work items in the
> BIER charter - there is no manageability section for example, there is no
> reference to the performance impact in networks. Maybe these are dealt with in
> a different document or documents or BIER, if so it would be good at least to
> mention and reference these here.

There is no requirement to include a manageability section.

I believe there is ongoing work having to do with Operations and 
Management of BIER, but as that does not help to understand the 
architecture (or forwarding procedures), I don't think it would be 
appropriate to reference that work.

With regard to the performance impact, if the question is speed of 
forwarding, there is mention of the fact that the number of lookups 
needed to forward a BIER packet is on the order of the number of 
neighbors.   I don't know what else can really be said at this level of 
detail, as the actual forwarding performance will depend a great deal on 
the implementation.  I'm not worried too much about that, because if 
BIER implementations do not perform well, the technology will not catch on.

> 4. I also would have expected the architecture document to refer the use cases
> document and note which of the use cases are being addressed and how -
> draft-ietf-bier-use-cases is not even included in the references.

I don't see any reason why the architecture document should reference 
the "use cases" document.  An explanation of how to apply the 
architecture to each use case is not within the scope of the 
architecture document.

> 5. Sections 3 to 6 mentioned repeatedly provisioning. As there is no Operations
> and Manageability section as in many other Routing Area documents, it is not
> clear how this is expected to happen.

How OAM is "expected to happen" would be outside the scope of this 
document.

> For example draft-ietf-bier-bier-yang is
> not mentioned or referred. I suggest adding a note (and maybe references) for
> clarity.

I don't see any reason to reference that document.

> 6. In section 8 I found:
>
> 'Every BFR must be provisioned to know which of its interfaces lead to
>     a BIER domain and which do not.  If two interfaces lead to different
>     BIER domains, the BFR must be provisioned to know that those two
>     interfaces lead to different BIER domains. '
>
> It seems that the two 'must' in these sentences would rather be capitalized.
>
>

I will make that change.


--------------E498FDE51A985A384882B11F
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 6/25/2017 6:54 AM, Dan Romascanu wrote:<br>
    <blockquote type="cite"
      cite="mid:149838804788.3251.829139224134758886@ietfa.amsl.com">
      <pre wrap="">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

<a class="moz-txt-link-rfc2396E" href="https://trac.ietf.org/trac/gen/wiki/GenArtfaq">&lt;https://trac.ietf.org/trac/gen/wiki/GenArtfaq&gt;</a>.

Document: draft-ietf-bier-architecture-??
Reviewer: Dan Romascanu
Review Date: 2017-06-25
IETF LC End Date: 2017-06-29
IESG Telechat date: 2017-07-06

Summary:

This document specifies a new architecture known as "Bit Index Explicit
Replication" (BIER) for the forwarding of multicast data packets through a
"multicast domain".  It does not require a protocol for explicitly building
multicast distribution trees, nor does it require intermediate nodes to
maintain any per-flow state. This architecture is .  While the Abstract and
Introduction of the document mentions Architecture as the principal scope, this
document goes well beyond the scope of a typical architectural document.
including detailed definitions of the procedures, terminology and normative
algorithms required for BIER.

The document is clear and detailed. Because of its structure, I am missing some
information that usually can be found in architecture documents. I included
these in the 'minor issues' list. Although none of these may be a show-stopper,
I believe that addressing these before document approval can improve the
quality of the document and of the overall BIER work.

Major issues:

Minor issues:

1. As the document is targeting 'Experimental' it would be useful to mention
what is the scope of the experiment.The charter actually says:

' The scope of the experiment will be
documented in the output of the Working Group.'

Would not the Architecture document be the right place for this? If not, is
there another document that deals or is planned to define the scope of the
experiment?</pre>
    </blockquote>
    <br>
    I don't really know what is meant by "the experiment" or "scope of
    the experiment", but I'm pretty sure it is not relevant to the
    architecture (or to the forwarding rules).<br>
    <br>
    I don't know if there is another document discussing "scope of the
    experiment", or if such a document is actually needed.  That would
    be a question for the WG chairs.<br>
    <br>
    <blockquote type="cite"
      cite="mid:149838804788.3251.829139224134758886@ietfa.amsl.com">
      <pre wrap="">2. While the Abstract and Introduction of the document mentions Architecture as
the principal scope, this document is different from a typical architectural
document. While it defines well the procedures, terminology and normative
algorithms required for BIER Intra-domain forwarding, it goes well beyond the
level of detail that other similar documents go. Specifications of the
procedures and normative algorithm should be mentioned in Abstract and
Introduction, they occupy the same or more space than architecture.</pre>
    </blockquote>
    <br>
    I can add a few sentences to the abstract and introduction to make
    it clear that the procedures for fowarding BIER packets within a
    BIER domain specified in this document.  <br>
    <br>
    <blockquote type="cite"
      cite="mid:149838804788.3251.829139224134758886@ietfa.amsl.com">
      <pre wrap="">
3. On the other hand I am missing the relationship with other work items in the
BIER charter - there is no manageability section for example, there is no
reference to the performance impact in networks. Maybe these are dealt with in
a different document or documents or BIER, if so it would be good at least to
mention and reference these here.</pre>
    </blockquote>
    <br>
    There is no requirement to include a manageability section.<br>
    <br>
    I believe there is ongoing work having to do with Operations and
    Management of BIER, but as that does not help to understand the
    architecture (or forwarding procedures), I don't think it would be
    appropriate to reference that work.<br>
    <br>
    With regard to the performance impact, if the question is speed of
    forwarding, there is mention of the fact that the number of lookups
    needed to forward a BIER packet is on the order of the number of
    neighbors.   I don't know what else can really be said at this level
    of detail, as the actual forwarding performance will depend a great
    deal on the implementation.  I'm not worried too much about that,
    because if BIER implementations do not perform well, the technology
    will not catch on.<br>
    <br>
    <blockquote type="cite"
      cite="mid:149838804788.3251.829139224134758886@ietfa.amsl.com">
      <pre wrap="">4. I also would have expected the architecture document to refer the use cases
document and note which of the use cases are being addressed and how -
draft-ietf-bier-use-cases is not even included in the references.</pre>
    </blockquote>
    <br>
    I don't see any reason why the architecture document should
    reference the "use cases" document.  An explanation of how to apply
    the architecture to each use case is not within the scope of the
    architecture document.  <br>
    <br>
    <blockquote type="cite"
      cite="mid:149838804788.3251.829139224134758886@ietfa.amsl.com">
      <pre wrap="">
5. Sections 3 to 6 mentioned repeatedly provisioning. As there is no Operations
and Manageability section as in many other Routing Area documents, it is not
clear how this is expected to happen. </pre>
    </blockquote>
    <br>
    How OAM is "expected to happen" would be outside the scope of this
    document. <br>
    <br>
    <blockquote type="cite"
      cite="mid:149838804788.3251.829139224134758886@ietfa.amsl.com">
      <pre wrap="">For example draft-ietf-bier-bier-yang is
not mentioned or referred. I suggest adding a note (and maybe references) for
clarity.</pre>
    </blockquote>
    <br>
    I don't see any reason to reference that document.  <br>
    <br>
    <blockquote type="cite"
      cite="mid:149838804788.3251.829139224134758886@ietfa.amsl.com">
      <pre wrap="">
6. In section 8 I found:

'Every BFR must be provisioned to know which of its interfaces lead to
   a BIER domain and which do not.  If two interfaces lead to different
   BIER domains, the BFR must be provisioned to know that those two
   interfaces lead to different BIER domains. '

It seems that the two 'must' in these sentences would rather be capitalized.


</pre>
    </blockquote>
    <br>
    I will make that change.<br>
    <br>
  </body>
</html>

--------------E498FDE51A985A384882B11F--


From nobody Tue Jun 27 07:47:06 2017
Return-Path: <gabrielkwaye@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 AD2D4127369 for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 07:47:05 -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 X0kDQkwJb9bJ for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 07:47:04 -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 A703A127137 for <ietf@ietf.org>; Tue, 27 Jun 2017 07:47:03 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id b207so18544444lfg.2 for <ietf@ietf.org>; Tue, 27 Jun 2017 07:47:03 -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=jvakjqAgTQIH2XeK2dF+sacI+LhATigPYsZ7OHMlh1k=; b=sMAzrnDC6lpt0PuYrbotbZLJg3JA0fgbKMpTWXM4r9buroyj/hL8mhNOPDbpLhavnj o2H9ER93pAMFx3M9USAPYaRq2CqtwW4l76RRFaWAbTGa2HEtJgTUeMpWXtLzktpFu02N vIibyR5uKii4+9qeulBpEFBtnCbsYW+AU9IWtyFo//vBP0lCyzA568UuYwNBECDCNWSn yB6OOWuhoieaBhcAd2gul3DXLAiqY4Fdxy1ygN56/l76rFMEprgxM9iFtoS/iMt4y/Bk 0/UGh7I/AIo51+DILSx2V9WLSd36vf+K++ZbUenG+df6+Z5JofDZK1Rm11a9ngbcGjrY fkLQ==
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=jvakjqAgTQIH2XeK2dF+sacI+LhATigPYsZ7OHMlh1k=; b=iDAYHbM60xrGZEd2FYOjC8+/OSkVqMqAxUnnl1Ef9f76n7CpiDnhZ8hzz6ekDoB1WT d8QTllQn+fEBXdbBD2sFsYXdLFxr7lBdmJelOYddTu120JJR+uvKuKVAg1FNDqaKlpS5 fHB/na7OVZheMsMfJcVASVZXhheyNth3m4IEXCxtpgHGd5nvFi8jWkb/q3n51QZg6L5D rPBQx5BrFN+/cDAIZZ8bfnvxNb7JhJDg4KUIWCd4HTIo0VIUrzNBXGwXvxZ2Rh4WE52L aoXA29F7/q76KjplMjnT3QaMGau0jBGJFV1m7NwnQ1opaKvzRw/KWJE+WgG89kjWMJ6b qCrg==
X-Gm-Message-State: AKS2vOwYiDlQF3u4xKxC3qdd5FvQ6f6mOkCoVSqO8NiDTGIxcNOgdWCY YT92aQqiPgmhNxz0itEnkiIT4T4Rqw==
X-Received: by 10.46.84.28 with SMTP id i28mr1672879ljb.44.1498574821926; Tue, 27 Jun 2017 07:47:01 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.199.139 with HTTP; Tue, 27 Jun 2017 07:47:01 -0700 (PDT)
In-Reply-To: <14CBCF3A-526F-40F0-B9E8-DF8760F7B0AB@cooperw.in>
References: <14CBCF3A-526F-40F0-B9E8-DF8760F7B0AB@cooperw.in>
From: Kwaye Kant <gabrielkwaye@gmail.com>
Date: Tue, 27 Jun 2017 15:47:01 +0100
Message-ID: <CALRvV169_BugowMsgOcf+Uos=YNtT0P1O=oZjLMqtpB=iaMvkg@mail.gmail.com>
Subject: Re: Maternity leave plans
To: Alissa Cooper <alissa@cooperw.in>
Cc: ietf <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="f403045fc328ee2cf80552f223a1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/yugIxehzlUQ5ErPUOBIKGhUKIcE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 14:47:06 -0000

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

Hi Alissa,

I wish you good luck and come back safely.

Regards

2017-06-27 15:27 GMT+01:00 Alissa Cooper <alissa@cooperw.in>:

> Hi all,
>
> My maternity leave is going to be starting some time within the next
> month. I will miss seeing those in attendance at IETF 99 but look forward
> to seeing everyone at IETF 100 and on the mailing lists before then.
>
> Several of my fellow ADs will be helping to cover my responsibilities onc=
e
> I go on leave. Suresh Krishnan will be chairing the plenary at IETF 99 an=
d
> handling external communications. Mirja Kuehlewind will be managing the
> IESG and shepherding MTGVENUE. Eric Rescorla will be handling IAOC and
> administrative matters. Others on the IESG and IAB are also available to
> pitch in if necessary. Many thanks to them all for helping out! I expect =
to
> be back working full-time within a few months.
>
> Feel free to reach out to me if you have questions.
>
> Alissa Cooper
> IETF Chair
>



--=20

*Gabriel Kant KWAYE*

Tel:+237 677 315 145
Boulevard de la Libert=C3=A9
Akwa, Douala

--f403045fc328ee2cf80552f223a1
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:tahoma,s=
ans-serif;font-size:small;color:#3d85c6">Hi Alissa,</div><div class=3D"gmai=
l_default" style=3D"font-family:tahoma,sans-serif;font-size:small;color:#3d=
85c6"><br></div><div class=3D"gmail_default" style=3D"font-family:tahoma,sa=
ns-serif;font-size:small;color:#3d85c6">I wish you good luck and come back =
safely.</div><div class=3D"gmail_default" style=3D"font-family:tahoma,sans-=
serif;font-size:small;color:#3d85c6"><br></div><div class=3D"gmail_default"=
 style=3D"font-family:tahoma,sans-serif;font-size:small;color:#3d85c6">Rega=
rds</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">20=
17-06-27 15:27 GMT+01:00 Alissa Cooper <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:alissa@cooperw.in" target=3D"_blank">alissa@cooperw.in</a>&gt;</span>:<=
br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left=
:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
My maternity leave is going to be starting some time within the next month.=
 I will miss seeing those in attendance at IETF 99 but look forward to seei=
ng everyone at IETF 100 and on the mailing lists before then.<br>
<br>
Several of my fellow ADs will be helping to cover my responsibilities once =
I go on leave. Suresh Krishnan will be chairing the plenary at IETF 99 and =
handling external communications. Mirja Kuehlewind will be managing the IES=
G and shepherding MTGVENUE. Eric Rescorla will be handling IAOC and adminis=
trative matters. Others on the IESG and IAB are also available to pitch in =
if necessary. Many thanks to them all for helping out! I expect to be back =
working full-time within a few months.<br>
<br>
Feel free to reach out to me if you have questions.<br>
<span class=3D"HOEnZb"><font color=3D"#888888"><br>
Alissa Cooper<br>
IETF Chair<br>
</font></span></blockquote></div><br><br clear=3D"all"><div><br></div>-- <b=
r><div class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div di=
r=3D"ltr"><div><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=
=3D"ltr"><div dir=3D"ltr"><table border=3D"0" cellspacing=3D"0" cellpadding=
=3D"0" style=3D"border-collapse:collapse;border:none">
 <tbody><tr>
  <td width=3D"252" valign=3D"top" style=3D"width:189.0pt;padding:0in 5.4pt=
 0in 5.4pt">
  <p style=3D"margin-bottom:0.0001pt;line-height:115%;background-image:init=
ial;background-position:initial;background-repeat:initial"><b><span style=
=3D"font-size:9.5pt;line-height:115%;font-family:&quot;Verdana&quot;,&quot;=
sans-serif&quot;;color:#660000">Gabriel Kant KWAYE</span></b></p><p style=
=3D"margin-bottom:0.0001pt;line-height:115%;background-image:initial;backgr=
ound-position:initial;background-repeat:initial"><span style=3D"font-size:9=
.5pt;line-height:115%;color:rgb(153,153,153)"><font face=3D"Arial, sans-ser=
if">
  Tel:+237 677 315 145=C2=A0<br></font></span><span style=3D"color:rgb(153,=
153,153);font-family:Arial,sans-serif;font-size:9.5pt">Boulevard de la Libe=
rt=C3=A9<br></span><span style=3D"color:rgb(153,153,153);font-family:Arial,=
sans-serif;font-size:9.5pt">Akwa, Douala</span></p>
  <br></td>
  <td width=3D"371" valign=3D"top" style=3D"width:278.5pt;padding:0in 5.4pt=
 0in 5.4pt">
  <p style=3D"margin-bottom:0in;margin-bottom:.0001pt;line-height:normal"><=
br></p>
  </td>
 </tr>
</tbody></table></div></div></div></div></div></div></div></div>
</div>

--f403045fc328ee2cf80552f223a1--


From nobody Tue Jun 27 08:16:45 2017
Return-Path: <Michael.Bishop@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 EE8D412EB6F; Mon, 26 Jun 2017 13:53:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.379
X-Spam-Level: 
X-Spam-Status: No, score=-0.379 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URI_HEX=1.122, URI_NOVOWEL=0.5] autolearn=no 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 QBSorN7GARPi; Mon, 26 Jun 2017 13:53:37 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0136.outbound.protection.outlook.com [104.47.40.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9479612EB71; Mon, 26 Jun 2017 13:53:37 -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=dQnpeWnP6nf94gMlwUgDqSda/lxhbKtGttOdOuYA91I=; b=ZWdf+ucxMESz3mhmMi9BQH346hg9+Ll+kg2KOdN9+ISWnEfBnxSqW/xA50oq86frK0uTDQ0L4UgeA7jKl/zbkUr7o8+scgIIpLsz/xb7jI9hOzG430RiJhrBG2xwqOr07CuEj9hUleoyv9h/17vMbQISUZkbdZXNKm6Hj6Rb8IM=
Received: from MWHPR21MB0141.namprd21.prod.outlook.com (10.173.52.11) by MWHPR21MB0176.namprd21.prod.outlook.com (10.173.52.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.1; Mon, 26 Jun 2017 20:53:36 +0000
Received: from MWHPR21MB0141.namprd21.prod.outlook.com ([10.173.52.11]) by MWHPR21MB0141.namprd21.prod.outlook.com ([10.173.52.11]) with mapi id 15.01.1240.001; Mon, 26 Jun 2017 20:53:36 +0000
From: Mike Bishop <Michael.Bishop@microsoft.com>
To: Yoav Weiss <yoav@yoav.ws>, Julian Reschke <julian.reschke@gmx.de>, "Kazuho Oku" <kazuhooku@gmail.com>
CC: "ietf@ietf.org" <ietf@ietf.org>, "httpbis-chairs@ietf.org" <httpbis-chairs@ietf.org>, Mark Nottingham <mnot@mnot.net>, "draft-ietf-httpbis-early-hints@ietf.org" <draft-ietf-httpbis-early-hints@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>, "alexey.melnikov@isode.com" <alexey.melnikov@isode.com>, Mike West <mkwst@chromium.org>
Subject: RE: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
Thread-Topic: Last Call: <draft-ietf-httpbis-early-hints-03.txt> (An HTTP Status Code for Indicating Hints) to Experimental RFC
Thread-Index: AQHS7ZwTt8yFTEdhDEC/5hQP2yHzz6I2b56AgACFVQCAAFnzAIAAUb/w
Date: Mon, 26 Jun 2017 20:53:36 +0000
Message-ID: <MWHPR21MB014165751D58AFC33BF6993F87DF0@MWHPR21MB0141.namprd21.prod.outlook.com>
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <dcdff226-e12d-bb83-982f-8253f46ae935@gmx.de> <CANatvzygaU9oiof3-5TqnWdxqXOGNyGqPvNhTnpPzYy391CzNw@mail.gmail.com> <632d93e7-eab5-dcbe-e971-64e3b27ddb4e@gmx.de> <CACj=BEjQQMRh-6de2J_tzF5o=EYvhZZ4_XQQ6DJiEq0wG0zW+g@mail.gmail.com>
In-Reply-To: <CACj=BEjQQMRh-6de2J_tzF5o=EYvhZZ4_XQQ6DJiEq0wG0zW+g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: yoav.ws; dkim=none (message not signed) header.d=none;yoav.ws; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:f::de]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR21MB0176; 7:x22X+NSMf78uf9xG/ObV/cyM7fvgLS5V7KUMkYPxuXN0dHjANkK48vKKy5PA6vA6N3wrAKSkJDw6OWaQhiXoM5UNJfF8IRIGw3gS47lqRziGukDj+QTk9qcKVQLHboBIg4GjI6ZEg86X7Jcs07PiDvCyI7Kv8OQ1c31KLKtuMahXixPsfZcVEShRfTg/f4maXGMHkqSm4QgEDIo4z1GjLBGLK5akd2Xb17+Q5+Ybzzt8laHrCBUTP+KUI6sZ4GvtzF8ZlajwZCICZs/zU0rlH0r221BJ9T4e4SnQv5XUsyw5FRFrIVL6nMtVVKLIHMsJEpWBthOr73FU9IReehh4eW5BP4mz6gI6eMKsnun/TbNj72CdbRnaSoZg9LYyW2prjBGCLgafDTzE2CCRHtQTDBwmXH0NXA5TviRrd85dMhhekiVVDLcAPBpXXW/s/+mRZp7b2pQ+eUeGq2SlOBHA37zsPRKEz48THpdlREuH3kKAXJMX0IqvOoEldvkfI6rAEoo+8HzVs6rVzip2GKdGdbVIl/SnMwrE7SZIkdjQ4GncT3Gu6tdvafesuVDsM8N7uyRAbx2yTQYxqA0hprtcupOq8W2jkZ77NWGFnxuzuNFGNbqmHoNl1dnagiwJXtJo8k/+efhyW/+reLEkFAkJPWpdTYh1XfordRblstEqk/mTcZaaCHkOMeWQH8GbmE/TEig7w+QkEaL+KZWcTQF/NlV2Q8JaXaQRdnduthgcsJNkWKpEPCLWTh5RQqp9VE3wQ0RGJ0Y0PgFq7ggYCBEppu5U5kT+iqFQZr28C68Qn8b8x8wp68qHleiycQrgOxq+
x-ms-office365-filtering-correlation-id: 62e05002-32f8-43a6-55fe-08d4bcd56a3b
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254075)(48565401081)(300000503095)(300135400095)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506067)(300135500095); SRVR:MWHPR21MB0176; 
x-ms-traffictypediagnostic: MWHPR21MB0176:
x-microsoft-antispam-prvs: <MWHPR21MB0176471939DB09B0B816629787DF0@MWHPR21MB0176.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(151999592597050)(278178393323532)(158342451672863)(26323138287068)(133145235818549)(26388249023172)(236129657087228)(189930954265078)(148574349560750)(219752817060721);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(10201501046)(3002001)(93006095)(93001095)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123558100)(20161123564025)(20161123560025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123555025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:MWHPR21MB0176; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:MWHPR21MB0176; 
x-forefront-prvs: 0350D7A55D
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(39400400002)(39450400003)(39410400002)(39840400002)(39850400002)(377454003)(24454002)(377424004)(606005)(102836003)(53546010)(229853002)(14454004)(478600001)(7696004)(50986999)(6116002)(3280700002)(2906002)(72206003)(76176999)(2900100001)(5660300001)(54356999)(77096006)(7416002)(790700001)(230783001)(8936002)(10090500001)(25786009)(189998001)(55016002)(54906002)(38730400002)(3660700001)(93886004)(6306002)(236005)(54896002)(74316002)(19609705001)(5005710100001)(7906003)(8990500004)(33656002)(86612001)(4326008)(8676002)(99286003)(39060400002)(68736007)(122556002)(6246003)(2950100002)(53936002)(10290500003)(6506006)(86362001)(9686003)(81166006)(7736002)(6436002)(8666007); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0176; H:MWHPR21MB0141.namprd21.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR21MB014165751D58AFC33BF6993F87DF0MWHPR21MB0141namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Jun 2017 20:53:36.1180 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0176
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qats099YwERNVy0oi4F1-pIdSfM>
X-Mailman-Approved-At: Tue, 27 Jun 2017 08:16:42 -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: Mon, 26 Jun 2017 20:53:41 -0000

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

QmVjYXVzZSBvdXIgbGF5ZXIgZG9lc27igJl0IGhhdmUgYWNjZXNzIHRvIHRoZSByZW5kZXJlciAo
dGhlIGlzc3VlIGJlbG93KSwgd2UgY3VycmVudGx5IG9ubHkgcHJlLXJlc29sdmUgYW5kIHByZS1j
b25uZWN0LCBldmVuIGlmIHRoZXJl4oCZcyBhIHByZWxvYWQgbGluay4gIEl04oCZcyBzdGlsbCBh
IGxhdGVuY3kgd2luLCBldmVuIGlmIHdlIGhhdmUgdG8gd2FpdCBvbiB0aGUgcmVuZGVyZXIgdG8g
bGF1bmNoIHRoZSBhY3R1YWwgcmVzb3VyY2UgcmVxdWVzdC4gIFdlIGN1cnJlbnRseSBkb27igJl0
IHByb2Nlc3MgYW55IGhlYWRlcnMgb3V0IG9mIGludGVybWVkaWF0ZSByZXNwb25zZXMsIHNvIHRo
ZXJl4oCZZCBiZSB3b3JrIGhlcmUsIGJ1dCB0aGF04oCZcyBubyBkaWZmZXJlbnQgZnJvbSBhbnkg
b3RoZXIgbmV3IGZlYXR1cmUgd2Ugd2FudCB0byBhZGQgc3VwcG9ydCBmb3IuDQoNCkZyb206IFlv
YXYgV2Vpc3MgW21haWx0bzp5b2F2QHlvYXYud3NdDQpTZW50OiBNb25kYXksIEp1bmUgMjYsIDIw
MTcgODo1OSBBTQ0KVG86IEp1bGlhbiBSZXNjaGtlIDxqdWxpYW4ucmVzY2hrZUBnbXguZGU+OyBL
YXp1aG8gT2t1IDxrYXp1aG9va3VAZ21haWwuY29tPg0KQ2M6IGlldGZAaWV0Zi5vcmc7IGh0dHBi
aXMtY2hhaXJzQGlldGYub3JnOyBNYXJrIE5vdHRpbmdoYW0gPG1ub3RAbW5vdC5uZXQ+OyBkcmFm
dC1pZXRmLWh0dHBiaXMtZWFybHktaGludHNAaWV0Zi5vcmc7IEhUVFAgV29ya2luZyBHcm91cCA8
aWV0Zi1odHRwLXdnQHczLm9yZz47IGFsZXhleS5tZWxuaWtvdkBpc29kZS5jb207IE1pa2UgV2Vz
dCA8bWt3c3RAY2hyb21pdW0ub3JnPg0KU3ViamVjdDogUmU6IExhc3QgQ2FsbDogPGRyYWZ0LWll
dGYtaHR0cGJpcy1lYXJseS1oaW50cy0wMy50eHQ+IChBbiBIVFRQIFN0YXR1cyBDb2RlIGZvciBJ
bmRpY2F0aW5nIEhpbnRzKSB0byBFeHBlcmltZW50YWwgUkZDDQoNCkFuIGlzc3VlPGh0dHBzOi8v
bmEwMS5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJG
Z2l0aHViLmNvbSUyRnczYyUyRnByZWxvYWQlMkZpc3N1ZXMlMkYxMDEmZGF0YT0wMiU3QzAxJTdD
TWljaGFlbC5CaXNob3AlNDBtaWNyb3NvZnQuY29tJTdDY2U3ZTRkZDA1N2RlNGYyZjFkODEwOGQ0
YmNhY2I5OWMlN0M3MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM2
MzQwODk3NDE3NDY5NDc0JnNkYXRhPTlKZlZMSGR3cEhpaGVGZ1Z2QUpmUHk4VUpFcHRMeTRldTQ2
aVlXQlpTUjAlM0QmcmVzZXJ2ZWQ9MD4gcmFpc2VkIGJ5IE1pa2UgV2VzdCAoQ0NlZCkgZ290IG1l
IHRoaW5raW5nIGlmIEVhcmx5IEhpbnRzIGFyZSBhdCBhbGwgaW1wbGVtZW50YWJsZSBhdCB0aGUg
YnJvd3NlciBsZXZlbCAocmF0aGVyIHRoYW4ganVzdCB1c2VkIGFzIGVhcmx5IHB1c2ggaGludHMg
YXQgdGhlIENETiBsZXZlbCkuDQoNCkN1cnJlbnRseSwgYXQgbGVhc3QgaW4gQ2hyb21pdW0gYW5k
IFdlYktpdCwgcmVxdWVzdHMgdHJpZ2dlcmVkIGJ5IHByZWxvYWQgbGlua3MgYXJlIG5vdCBzZW50
IHVudGlsIHRoZSBkb2N1bWVudCBpcyBjb21taXR0ZWQsIHdoaWNoIG1lYW5zIHRoYXQgdGhleSBh
cmUgbm90IHNlbnQgaW1tZWRpYXRlbHkgd2hlbiB0aGUgYnJvd3NlciBwcm9jZXNzZXMgdGhlbS4g
VGhhdCdzIGxpa2VseSB0byBiZSBhIHNob3J0LCBpbnRlcm5hbCBkZWxheS4NCkhvd2V2ZXIsIGlu
IHRoZSBjb250ZXh0IG9mIEVhcmx5IEhpbnRzLCB0aGF0IGRlbGF5IGNhbiBiZSBzaWduaWZpY2Fu
dCwgYXMgaXQgY2FuIHRha2UgaHVuZHJlZHMgb2YgbWlsbGlzZWNvbmRzIGZvciB0aGUgcmVuZGVy
ZXIgcHJvY2VzcyB0byBnZXQgY3JlYXRlZC4gQXQgdGhlIHNhbWUgdGltZSwgYSBsb3Qgb2YgdGhl
IGxvZ2ljIHJlcXVpcmVkIHRvIHNlbmQgdGhvc2UgcmVxdWVzdHMgb3V0IHNpdHMgaW4gdGhlIHJl
bmRlcmluZyBlbmdpbmUuDQoNCkknbSBub3Qgc3VyZSB3aGF0IGlzIHRoZSBzb2x1dGlvbiB0byBi
cmlkZ2UgdGhhdCBnYXAsIGlmIG9uZSBleGlzdHMuDQoNCkNoZWVycywNCllvYXYNCg0KT24gTW9u
LCBKdW4gMjYsIDIwMTcgYXQgMTI6NDEgUE0gSnVsaWFuIFJlc2Noa2UgPGp1bGlhbi5yZXNjaGtl
QGdteC5kZTxtYWlsdG86anVsaWFuLnJlc2Noa2VAZ214LmRlPj4gd3JvdGU6DQpPbiAyMDE3LTA2
LTI2IDA0OjM5LCBLYXp1aG8gT2t1IHdyb3RlOg0KPiAuLi4NCj4gMjAxNy0wNi0yNSAxOToxMSBH
TVQrMDk6MDAgSnVsaWFuIFJlc2Noa2UgPGp1bGlhbi5yZXNjaGtlQGdteC5kZTxtYWlsdG86anVs
aWFuLnJlc2Noa2VAZ214LmRlPj46DQo+PiBPbiAyMDE3LTA2LTIxIDE4OjU5LCBUaGUgSUVTRyB3
cm90ZToNCj4+Pg0KPj4+DQo+Pj4gVGhlIElFU0cgaGFzIHJlY2VpdmVkIGEgcmVxdWVzdCBmcm9t
IHRoZSBIeXBlcnRleHQgVHJhbnNmZXIgUHJvdG9jb2wgV0cNCj4+PiAoaHR0cGJpcykgdG8gY29u
c2lkZXIgdGhlIGZvbGxvd2luZyBkb2N1bWVudDogLSAnQW4gSFRUUCBTdGF0dXMgQ29kZSBmb3IN
Cj4+PiBJbmRpY2F0aW5nIEhpbnRzJw0KPj4+ICAgICA8ZHJhZnQtaWV0Zi1odHRwYmlzLWVhcmx5
LWhpbnRzLTAzLnR4dD4gYXMgRXhwZXJpbWVudGFsIFJGQw0KPj4+IC4uLg0KPj4NCj4+DQo+Pg0K
Pj4gSGVyZSdzIG15IGZlZWRiYWNrLi4uOg0KPj4NCj4+IDIuICAxMDMgRWFybHkgSGludHMNCj4+
DQo+PiAgICAgLi4uDQo+Pg0KPj4gICAgIEEgc2VydmVyIE1VU1QgTk9UIGluY2x1ZGUgQ29udGVu
dC1MZW5ndGgsIFRyYW5zZmVyLUVuY29kaW5nLCBvciBhbnkNCj4+ICAgICBob3AtYnktaG9wIGhl
YWRlciBmaWVsZHMgKFtSRkM3MjMwXSwgU2VjdGlvbiA2LjEpIGluIGEgMTAzIChFYXJseQ0KPj4g
ICAgIEhpbnRzKSByZXNwb25zZS4NCj4+DQo+PiBUaGF0J3MgYSBiaXQgd2VpcmQgaGVyZSwgYmVj
YXVzZSB0aGUgcmVxdWlyZW1lbnRzIGZvciBDLUwgYW5kIFQtRSBhcmUNCj4+IGdlbmVyaWMgdG8g
MXh4LCBhbmQgYWxyZWFkeSBhcmUgc3RhdGVkIGluIFJGQyA3MjMwLiBUaGUgdGV4dCBhYm92ZSBt
YWtlcyBpdA0KPj4gc291bmQgYXMgaWYgdGhlc2UgYXJlIHNwZWNpZmljIHRvIDEwMywgd2hpY2gg
dGhleSBhcmUgbm90Lg0KPj4NCj4+IEZvciBob3AtYnktaG9wLCBJJ20gbm90IGNvbnZpbmNlZCB0
aGF0IHRoZSByZXF1aXJlbWVudCBpcyBuZWVkZWQgaGVyZS4NCj4NCj4gSSBhZ3JlZSB0aGF0IHdl
IGRvIG5vdCBuZWVkIHRvIHRhbGsgYWJvdXQgQy1MIGFuZCBULUUgaGVyZS4NCj4NCj4gVGhlIHJl
YXNvbnMgSSBhZGRlZCBhIGNsYXVzZSBwcm9oaWJpdGluZyB0aGUgdXNlIG9mIGhvcC1ieS1ob3Ag
aGVhZGVycw0KPiBpbiBhbiAxMDMgcmVzcG9uc2UgYXJlIGFzIGZvbGxvd3M6DQo+ICogZG9lcyBu
b3QgbWFrZSBzZW5zZSBmb3IgYSByZXNwb25zZSB0aGF0IGF0dGVtcHRzIHRvIHNlbmQgdGhlDQo+
IG1ldGFkYXRhIG9mIGEgZmluYWwgcmVzcG9uc2UgZWFybHkNCj4gKiB0byBhdm9pZCBjb25mdXNp
b24gY2F1c2VkIGJ5IHNlbmRpbmcgYSBob3AtYnktaG9wIGhlYWRlciBpbiB0aGUgMTAzIHJlc3Bv
bnNlDQo+DQo+IFdpdGhvdXQgdGhlIHJlc3RyaWN0aW9uLCBhIHJlc3BvbnNlIGxpa2UgYmVsb3cg
d291bGQgYmUgdmFsaWQsIHdoaWNoDQo+IElNTyBpcyBjb25mdXNpbmcgYXQgbGVhc3QuDQo+DQo+
IGBgYA0KPiBIVFRQLzEuMSAxMDMgRWFybHkgSGludHMNCj4gQ29ubmVjdGlvbjogY2xvc2UNCj4g
TGluazogPC9zdHlsZS5jc3M+OyByZWw9cHJlbG9hZA0KPg0KPiBIVFRQLzEuMSAyMDAgT0sNCj4g
Q29ubmVjdGlvbjogY2xvc2UNCj4gTGluazogPC9zdHlsZS5jc3M+OyByZWw9cHJlbG9hZA0KPiAu
Li4NCj4gYGBgDQoNClllcywgYnV0IGRvZXMgdGhhdCBtZWFuIHdlIG5lZWQgYSBub3JtYXRpdmUg
cmVxdWlyZW1lbnQ/IEFsc28sIGlzIGl0DQpyZWFsbHkgb2J2aW91cyB0aGF0IG5vIGZ1dHVyZSBo
b3AtYnktaG9wIGhlYWRlciBmaWVsZCBjb3VsZCBiZQ0KbWVhbmluZ2Z1bCBvbiBhIDEwMz8NCg0K
Pj4gICAgIC4uLg0KPj4NCj4+ICAgICBBbiBpbnRlcm1lZGlhcnkgTUFZIGRyb3AgdGhlIGluZm9y
bWF0aW9uYWwgcmVzcG9uc2UuICguLi4pDQo+Pg0KPj4gVGhhdCBzZWVtcyB0byBjb250cmFkaWN0
IGEgTVVTVC1sZXZlbCByZXF1aXJlbWVudCBpbiBSRkMgNzIzMQ0KPj4gKGh0dHBzOi8vd3d3Lmdy
ZWVuYnl0ZXMuZGUvdGVjaC93ZWJkYXYvcmZjNzIzMS5odG1sI3JmYy5zZWN0aW9uLjYuMi5wLjM8
aHR0cHM6Ly9uYTAxLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMl
M0ElMkYlMkZ3d3cuZ3JlZW5ieXRlcy5kZSUyRnRlY2glMkZ3ZWJkYXYlMkZyZmM3MjMxLmh0bWwl
MjNyZmMuc2VjdGlvbi42LjIucC4zJmRhdGE9MDIlN0MwMSU3Q01pY2hhZWwuQmlzaG9wJTQwbWlj
cm9zb2Z0LmNvbSU3Q2NlN2U0ZGQwNTdkZTRmMmYxZDgxMDhkNGJjYWNiOTljJTdDNzJmOTg4YmY4
NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDclN0MxJTdDMCU3QzYzNjM0MDg5NzQxNzQ2OTQ3NCZzZGF0
YT1mSlB4ZlNyRWU5RDNuNmxBcDBybWlqblNHVGFvbzJ5VDRaWmF0b0JJNUZZJTNEJnJlc2VydmVk
PTA+KQ0KPg0KPiBUaGUgc3RhdGVtZW50IGV4aXN0cyBzaW5jZSBzZW5kaW5nIDEwMyBvbmx5IG1h
a2VzIHNlbnNlIHdoZW4gaXQgaXMNCj4gaW1wb3NzaWJsZSB0byBpbW1lZGlhdGVseSBzZW5kIGEg
ZmluYWwgcmVzcG9uc2UuDQo+DQo+IEZvciBleGFtcGxlLCB0aGVyZSBpcyBubyBuZWVkIGZvciBh
IGNhY2hlIHRoYXQgaXMgaW4gcG9zc2Vzc2lvbiBvZiBhDQo+IGZyZXNobHktY2FjaGVkIGZpbmFs
IHJlc3BvbnNlIHRvIHNlbmQgYSAxMDMgdGhhdCB3YXMgc2VudCBmcm9tIHRoZQ0KPiBvcmlnaW4g
YmVmb3JlIHNlbmRpbmcgdGhlIGZpbmFsIHJlc3BvbnNlLiBJIGFsc28gYmVsaWV2ZSB0aGF0IG1v
c3QNCj4gY2FjaGluZyBwcm94aWVzIHRoYXQgZXhpc3QgdG9kYXkgZG8gbm90IGNhY2hlIGluZm9y
bWF0aW9uYWwgcmVzcG9uc2VzLA0KPiBhbmQgdGhhdCB0aGVyZSBpcyBubyBuZWVkIGZvciB1cyB0
byByZXF1aXJlIHRoZW0gdG8gZG8gc28uDQo+DQo+IENvbnNpZGVyaW5nIHRoZSBmYWN0cywgb25l
IHdheSB0byByZXNvbHZlIHRoZSBpc3N1ZSB3b3VsZCBiZSB0byBhZGp1c3QNCj4gdGhlIHN0YXRl
bWVudCB0byBzb21ldGhpbmcgbGlrZSAiQW4gaW50ZXJtZWRpYXJ5IE1BWSBvbWl0IHRoZSAxMDMN
Cj4gcmVzcG9uc2Ugd2hlbiByZXNlbmRpbmcgYSBjYWNoZWQgcmVzcG9uc2UiLCBhbmQgYXJndWUg
dGhhdCByZS1zZW5kaW5nDQo+IGEgY2FjaGVkIHJlc3BvbnNlIGlzIG5vdCBhbiBhY3Rpb24gb2Yg
ImZvcndhcmRpbmcsIiB3aGljaCBpcyBkZWZpbmVkDQo+IGFzIGEgTVVTVCBpbiBSRkMgNzIzMS4N
Cg0KU291bmRzIGdvb2QgdG8gbWUuDQoNCj4gQnV0IHdvdWxkbid0IGl0IGJlIHNpbXBsZXIgdG8g
anVzdCBoYXZlIHRoZSAiTUFZIGRyb3AiIGNsYXVzZSBmb3IgYW55DQo+IGludGVybWVkaWFyeT8N
Cg0KSW4gdGhhdCBjYXNlLCB0aGUgc3BlYyB3b3VsZCBjb250cmFkaWN0IFJGQyA3MjMxLCB3aGlj
aCBpcyBiYWQgcG9zaXRpb24NCnRvIGJlIGluLi4uDQoNCj4+ICAgICBUaGUgZm9sbG93aW5nIGV4
YW1wbGUgaWxsdXN0cmF0ZXMgYSB0eXBpY2FsIG1lc3NhZ2UgZXhjaGFuZ2UgdGhhdA0KPj4gICAg
IGludm9sdmVzIGEgMTAzIChFYXJseSBIaW50cykgcmVzcG9uc2UuDQo+Pg0KPj4gICAgIENsaWVu
dCByZXF1ZXN0Og0KPj4NCj4+ICAgICAgIEdFVCAvIEhUVFAvMS4xDQo+PiAgICAgICBIb3N0OiBl
eGFtcGxlLmNvbTxodHRwczovL25hMDEuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20v
P3VybD1odHRwJTNBJTJGJTJGZXhhbXBsZS5jb20mZGF0YT0wMiU3QzAxJTdDTWljaGFlbC5CaXNo
b3AlNDBtaWNyb3NvZnQuY29tJTdDY2U3ZTRkZDA1N2RlNGYyZjFkODEwOGQ0YmNhY2I5OWMlN0M3
MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM2MzQwODk3NDE3NDc5
NDg3JnNkYXRhPUNQRmlWRjBQM1hnR1FTOUVhTEtHVkJ2RkxrWm1ZVEVldmwybSUyQlZmS0dwSSUz
RCZyZXNlcnZlZD0wPg0KPj4NCj4+IChtYXliZSBpbnNlcnQgYmxhbmsgbGluZSBkbyBkZWxpbWl0
IHRoZSBtZXNzYWdlKQ0KPj4NCj4+ICAgICBTZXJ2ZXIgcmVzcG9uc2U6DQo+Pg0KPj4gICAgICAg
SFRUUC8xLjEgMTAzIEVhcmx5IEhpbnRzDQo+PiAgICAgICBMaW5rOiA8L3N0eWxlLmNzcz47IHJl
bD1wcmVsb2FkOyBhcz1zdHlsZQ0KPj4gICAgICAgTGluazogPC9zY3JpcHQuanM+OyByZWw9cHJl
bG9hZDsgYXM9c2NyaXB0DQo+Pg0KPj4gICAgICAgSFRUUC8xLjEgMjAwIE9LDQo+PiAgICAgICBE
YXRlOiBGcmksIDI2IE1heSAyMDE3IDEwOjAyOjExIEdNVA0KPj4gICAgICAgQ29udGVudC1MZW5n
dGg6IDEyMzQNCj4+ICAgICAgIENvbnRlbnQtVHlwZTogdGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04
DQo+PiAgICAgICBMaW5rOiA8L3N0eWxlLmNzcz47IHJlbD1wcmVsb2FkOyBhcz1zdHlsZQ0KPj4g
ICAgICAgTGluazogPC9zY3JpcHQuanM+OyByZWw9cHJlbG9hZDsgYXM9c2NyaXB0DQo+Pg0KPj4g
ICAgICAgPCFkb2N0eXBlIGh0bWw+DQo+PiAgICAgICBbLi4uIHJlc3Qgb2YgdGhlIHJlc3BvbnNl
IGJvZHkgaXMgb21taXR0ZWQgZnJvbSB0aGUgZXhhbXBsZSAuLi5dDQo+Pg0KPj4gVGhlIGV4YW1w
bGUgc3VnZ2VzdHMgdGhhdCBlYXJseSBoaW50cyBhcmUgcmVwZWF0ZWQgaW4gdGhlIGZpbmFsIHJl
c3BvbnNlLiBEbw0KPj4gdGhleSBoYXZlIHRvLCBhY3R1YWxseT8NCj4NCj4gWWVzLiBUaGV5IG5l
ZWQgdG8sIGVzcGVjaWFsbHkgaWYgY2FjaGluZyBpcyBpbnZvbHZlZC4gMTAzIGlzIGFuDQo+IGlu
dGVybWVkaWFyeSByZXNwb25zZSBhbmQgdGhlcmUgaXMgbm8gZ3VhcmFudGVlIChvciBhIHJlcXVp
cmVtZW50KSBmb3INCj4gYSBjYWNoZSB0byByZXRhaW4gdGhlIGhlYWRlcnMgaW5jbHVkZWQgb25s
eSBpbiB0aGUgaW5mb3JtYXRpb25hbA0KPiByZXNwb25zZS4NCj4NCj4gSW4gY2FzZSBvZiBsaW5r
IHJlbD1wcmVsb2FkIGhlYWRlcnMsIGEgY2xpZW50IGNhbiBzcGVjdWxhdGl2ZWx5IGxvYWQNCj4g
dGhlIHJlc291cmNlcyBpbmNsdWRlZCBpbiB0aGUgaGVhZGVycyB3aGlsZSByZXZhbGlkYXRpbmcg
YQ0KPiBzdGFsZS1jYWNoZWQgcmVzcG9uc2UsIG9yIGEgY2FjaGluZyBwcm94eSBjYW4gZ2VuZXJh
dGUgYSAxMDMgcmVzcG9uc2UNCj4gZnJvbSBhIHN0YWxlLWNhY2hlZCAyMDAgcmVzcG9uc2UsIHdo
aWxlIHdhaXRpbmcgZm9yIHRoZSBvcmlnaW4gdG8NCj4gcGVyZm9ybSByZXZhbGlkYXRpb24uDQoN
CldoYXQgSSdtIGFmdGVyIGlzIGEgY2xlYXIgc3RhdGVtZW50IHdoZXRoZXIgdGhleSByZWFsbHkg
bmVlZCB0byBiZQ0KcmVwZWF0ZWQsIGFzIG5vcm1hdGl2ZSBsYW5ndWFnZS4NCg0KPiAuLi4NCg0K
QmVzdCByZWdhcmRzLCBKdWxpYW4NCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z
b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJw
bGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25v
cm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0K
QHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAx
LjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24x
O30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRz
IHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtp
ZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1h
cCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRp
Zl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVy
cGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5C
ZWNhdXNlIG91ciBsYXllciBkb2VzbuKAmXQgaGF2ZSBhY2Nlc3MgdG8gdGhlIHJlbmRlcmVyICh0
aGUgaXNzdWUgYmVsb3cpLCB3ZSBjdXJyZW50bHkgb25seSBwcmUtcmVzb2x2ZSBhbmQgcHJlLWNv
bm5lY3QsIGV2ZW4gaWYgdGhlcmXigJlzIGEgcHJlbG9hZCBsaW5rLiZuYnNwOyBJdOKAmXMgc3Rp
bGwgYSBsYXRlbmN5IHdpbiwgZXZlbiBpZiB3ZSBoYXZlIHRvIHdhaXQgb24gdGhlIHJlbmRlcmVy
IHRvIGxhdW5jaCB0aGUgYWN0dWFsDQogcmVzb3VyY2UgcmVxdWVzdC4mbmJzcDsgV2UgY3VycmVu
dGx5IGRvbuKAmXQgcHJvY2VzcyBhbnkgaGVhZGVycyBvdXQgb2YgaW50ZXJtZWRpYXRlIHJlc3Bv
bnNlcywgc28gdGhlcmXigJlkIGJlIHdvcmsgaGVyZSwgYnV0IHRoYXTigJlzIG5vIGRpZmZlcmVu
dCBmcm9tIGFueSBvdGhlciBuZXcgZmVhdHVyZSB3ZSB3YW50IHRvIGFkZCBzdXBwb3J0IGZvci48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IFlvYXYgV2Vpc3MgW21haWx0bzp5
b2F2QHlvYXYud3NdIDxicj4NCjxiPlNlbnQ6PC9iPiBNb25kYXksIEp1bmUgMjYsIDIwMTcgODo1
OSBBTTxicj4NCjxiPlRvOjwvYj4gSnVsaWFuIFJlc2Noa2UgJmx0O2p1bGlhbi5yZXNjaGtlQGdt
eC5kZSZndDs7IEthenVobyBPa3UgJmx0O2thenVob29rdUBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+
Q2M6PC9iPiBpZXRmQGlldGYub3JnOyBodHRwYmlzLWNoYWlyc0BpZXRmLm9yZzsgTWFyayBOb3R0
aW5naGFtICZsdDttbm90QG1ub3QubmV0Jmd0OzsgZHJhZnQtaWV0Zi1odHRwYmlzLWVhcmx5LWhp
bnRzQGlldGYub3JnOyBIVFRQIFdvcmtpbmcgR3JvdXAgJmx0O2lldGYtaHR0cC13Z0B3My5vcmcm
Z3Q7OyBhbGV4ZXkubWVsbmlrb3ZAaXNvZGUuY29tOyBNaWtlIFdlc3QgJmx0O21rd3N0QGNocm9t
aXVtLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IExhc3QgQ2FsbDogJmx0O2RyYWZ0
LWlldGYtaHR0cGJpcy1lYXJseS1oaW50cy0wMy50eHQmZ3Q7IChBbiBIVFRQIFN0YXR1cyBDb2Rl
IGZvciBJbmRpY2F0aW5nIEhpbnRzKSB0byBFeHBlcmltZW50YWwgUkZDPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5BbiA8YSBocmVmPSJodHRwczovL25hMDEuc2FmZWxpbmtzLnByb3Rl
Y3Rpb24ub3V0bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUyRmdpdGh1Yi5jb20lMkZ3M2MlMkZw
cmVsb2FkJTJGaXNzdWVzJTJGMTAxJmFtcDtkYXRhPTAyJTdDMDElN0NNaWNoYWVsLkJpc2hvcCU0
MG1pY3Jvc29mdC5jb20lN0NjZTdlNGRkMDU3ZGU0ZjJmMWQ4MTA4ZDRiY2FjYjk5YyU3QzcyZjk4
OGJmODZmMTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3JTdDMSU3QzAlN0M2MzYzNDA4OTc0MTc0Njk0NzQm
YW1wO3NkYXRhPTlKZlZMSGR3cEhpaGVGZ1Z2QUpmUHk4VUpFcHRMeTRldTQ2aVlXQlpTUjAlM0Qm
YW1wO3Jlc2VydmVkPTAiPg0KaXNzdWU8L2E+IHJhaXNlZCBieSBNaWtlIFdlc3QgKENDZWQpIGdv
dCBtZSB0aGlua2luZyBpZiBFYXJseSBIaW50cyBhcmUgYXQgYWxsIGltcGxlbWVudGFibGUgYXQg
dGhlIGJyb3dzZXIgbGV2ZWwgKHJhdGhlciB0aGFuIGp1c3QgdXNlZCBhcyBlYXJseSBwdXNoIGhp
bnRzIGF0IHRoZSBDRE4gbGV2ZWwpLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxicj4NCkN1cnJlbnRseSwgYXQgbGVhc3QgaW4gQ2hyb21pdW0gYW5kIFdlYktp
dCwgcmVxdWVzdHMgdHJpZ2dlcmVkIGJ5IHByZWxvYWQgbGlua3MgYXJlIG5vdCBzZW50IHVudGls
IHRoZSBkb2N1bWVudCBpcyBjb21taXR0ZWQsIHdoaWNoIG1lYW5zIHRoYXQgdGhleSBhcmUgbm90
IHNlbnQgaW1tZWRpYXRlbHkgd2hlbiB0aGUgYnJvd3NlciBwcm9jZXNzZXMgdGhlbS4gVGhhdCdz
IGxpa2VseSB0byBiZSBhIHNob3J0LCBpbnRlcm5hbCBkZWxheS48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhvd2V2ZXIsIGluIHRoZSBjb250ZXh0
IG9mIEVhcmx5IEhpbnRzLCB0aGF0IGRlbGF5IGNhbiBiZSBzaWduaWZpY2FudCwgYXMgaXQgY2Fu
IHRha2UgaHVuZHJlZHMgb2YgbWlsbGlzZWNvbmRzIGZvciB0aGUgcmVuZGVyZXIgcHJvY2VzcyB0
byBnZXQgY3JlYXRlZC4gQXQgdGhlIHNhbWUgdGltZSwgYSBsb3Qgb2YgdGhlIGxvZ2ljIHJlcXVp
cmVkIHRvIHNlbmQgdGhvc2UgcmVxdWVzdHMgb3V0IHNpdHMgaW4gdGhlDQogcmVuZGVyaW5nIGVu
Z2luZS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+SSdtIG5vdCBzdXJlIHdoYXQgaXMgdGhlIHNvbHV0aW9uIHRvIGJyaWRnZSB0aGF0IGdhcCwg
aWYgb25lIGV4aXN0cy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+Q2hlZXJzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+WW9hdjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPk9uIE1vbiwgSnVuIDI2LCAyMDE3IGF0IDEyOjQxIFBNIEp1bGlhbiBS
ZXNjaGtlICZsdDs8YSBocmVmPSJtYWlsdG86anVsaWFuLnJlc2Noa2VAZ214LmRlIj5qdWxpYW4u
cmVzY2hrZUBnbXguZGU8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJs
b2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4w
cHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmln
aHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBw
dCI+T24gMjAxNy0wNi0yNiAwNDozOSwgS2F6dWhvIE9rdSB3cm90ZTo8YnI+DQomZ3Q7IC4uLjxi
cj4NCiZndDsgMjAxNy0wNi0yNSAxOToxMSBHTVQmIzQzOzA5OjAwIEp1bGlhbiBSZXNjaGtlICZs
dDs8YSBocmVmPSJtYWlsdG86anVsaWFuLnJlc2Noa2VAZ214LmRlIiB0YXJnZXQ9Il9ibGFuayI+
anVsaWFuLnJlc2Noa2VAZ214LmRlPC9hPiZndDs6PGJyPg0KJmd0OyZndDsgT24gMjAxNy0wNi0y
MSAxODo1OSwgVGhlIElFU0cgd3JvdGU6PGJyPg0KJmd0OyZndDsmZ3Q7PGJyPg0KJmd0OyZndDsm
Z3Q7PGJyPg0KJmd0OyZndDsmZ3Q7IFRoZSBJRVNHIGhhcyByZWNlaXZlZCBhIHJlcXVlc3QgZnJv
bSB0aGUgSHlwZXJ0ZXh0IFRyYW5zZmVyIFByb3RvY29sIFdHPGJyPg0KJmd0OyZndDsmZ3Q7ICho
dHRwYmlzKSB0byBjb25zaWRlciB0aGUgZm9sbG93aW5nIGRvY3VtZW50OiAtICdBbiBIVFRQIFN0
YXR1cyBDb2RlIGZvcjxicj4NCiZndDsmZ3Q7Jmd0OyBJbmRpY2F0aW5nIEhpbnRzJzxicj4NCiZn
dDsmZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7Jmx0O2RyYWZ0LWlldGYtaHR0cGJpcy1lYXJs
eS1oaW50cy0wMy50eHQmZ3Q7IGFzIEV4cGVyaW1lbnRhbCBSRkM8YnI+DQomZ3Q7Jmd0OyZndDsg
Li4uPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZn
dDsgSGVyZSdzIG15IGZlZWRiYWNrLi4uOjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgMi4m
bmJzcDsgMTAzIEVhcmx5IEhpbnRzPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAm
bmJzcDsgJm5ic3A7Li4uPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsg
Jm5ic3A7QSBzZXJ2ZXIgTVVTVCBOT1QgaW5jbHVkZSBDb250ZW50LUxlbmd0aCwgVHJhbnNmZXIt
RW5jb2RpbmcsIG9yIGFueTxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtob3AtYnkt
aG9wIGhlYWRlciBmaWVsZHMgKFtSRkM3MjMwXSwgU2VjdGlvbiA2LjEpIGluIGEgMTAzIChFYXJs
eTxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtIaW50cykgcmVzcG9uc2UuPGJyPg0K
Jmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyBUaGF0J3MgYSBiaXQgd2VpcmQgaGVyZSwgYmVjYXVzZSB0
aGUgcmVxdWlyZW1lbnRzIGZvciBDLUwgYW5kIFQtRSBhcmU8YnI+DQomZ3Q7Jmd0OyBnZW5lcmlj
IHRvIDF4eCwgYW5kIGFscmVhZHkgYXJlIHN0YXRlZCBpbiBSRkMgNzIzMC4gVGhlIHRleHQgYWJv
dmUgbWFrZXMgaXQ8YnI+DQomZ3Q7Jmd0OyBzb3VuZCBhcyBpZiB0aGVzZSBhcmUgc3BlY2lmaWMg
dG8gMTAzLCB3aGljaCB0aGV5IGFyZSBub3QuPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyBG
b3IgaG9wLWJ5LWhvcCwgSSdtIG5vdCBjb252aW5jZWQgdGhhdCB0aGUgcmVxdWlyZW1lbnQgaXMg
bmVlZGVkIGhlcmUuPGJyPg0KJmd0Ozxicj4NCiZndDsgSSBhZ3JlZSB0aGF0IHdlIGRvIG5vdCBu
ZWVkIHRvIHRhbGsgYWJvdXQgQy1MIGFuZCBULUUgaGVyZS48YnI+DQomZ3Q7PGJyPg0KJmd0OyBU
aGUgcmVhc29ucyBJIGFkZGVkIGEgY2xhdXNlIHByb2hpYml0aW5nIHRoZSB1c2Ugb2YgaG9wLWJ5
LWhvcCBoZWFkZXJzPGJyPg0KJmd0OyBpbiBhbiAxMDMgcmVzcG9uc2UgYXJlIGFzIGZvbGxvd3M6
PGJyPg0KJmd0OyAqIGRvZXMgbm90IG1ha2Ugc2Vuc2UgZm9yIGEgcmVzcG9uc2UgdGhhdCBhdHRl
bXB0cyB0byBzZW5kIHRoZTxicj4NCiZndDsgbWV0YWRhdGEgb2YgYSBmaW5hbCByZXNwb25zZSBl
YXJseTxicj4NCiZndDsgKiB0byBhdm9pZCBjb25mdXNpb24gY2F1c2VkIGJ5IHNlbmRpbmcgYSBo
b3AtYnktaG9wIGhlYWRlciBpbiB0aGUgMTAzIHJlc3BvbnNlPGJyPg0KJmd0Ozxicj4NCiZndDsg
V2l0aG91dCB0aGUgcmVzdHJpY3Rpb24sIGEgcmVzcG9uc2UgbGlrZSBiZWxvdyB3b3VsZCBiZSB2
YWxpZCwgd2hpY2g8YnI+DQomZ3Q7IElNTyBpcyBjb25mdXNpbmcgYXQgbGVhc3QuPGJyPg0KJmd0
Ozxicj4NCiZndDsgYGBgPGJyPg0KJmd0OyBIVFRQLzEuMSAxMDMgRWFybHkgSGludHM8YnI+DQom
Z3Q7IENvbm5lY3Rpb246IGNsb3NlPGJyPg0KJmd0OyBMaW5rOiAmbHQ7L3N0eWxlLmNzcyZndDs7
IHJlbD1wcmVsb2FkPGJyPg0KJmd0Ozxicj4NCiZndDsgSFRUUC8xLjEgMjAwIE9LPGJyPg0KJmd0
OyBDb25uZWN0aW9uOiBjbG9zZTxicj4NCiZndDsgTGluazogJmx0Oy9zdHlsZS5jc3MmZ3Q7OyBy
ZWw9cHJlbG9hZDxicj4NCiZndDsgLi4uPGJyPg0KJmd0OyBgYGA8YnI+DQo8YnI+DQpZZXMsIGJ1
dCBkb2VzIHRoYXQgbWVhbiB3ZSBuZWVkIGEgbm9ybWF0aXZlIHJlcXVpcmVtZW50PyBBbHNvLCBp
cyBpdDxicj4NCnJlYWxseSBvYnZpb3VzIHRoYXQgbm8gZnV0dXJlIGhvcC1ieS1ob3AgaGVhZGVy
IGZpZWxkIGNvdWxkIGJlPGJyPg0KbWVhbmluZ2Z1bCBvbiBhIDEwMz88YnI+DQo8YnI+DQomZ3Q7
Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7Li4uPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZu
YnNwOyAmbmJzcDsgJm5ic3A7QW4gaW50ZXJtZWRpYXJ5IE1BWSBkcm9wIHRoZSBpbmZvcm1hdGlv
bmFsIHJlc3BvbnNlLiAoLi4uKTxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgVGhhdCBzZWVt
cyB0byBjb250cmFkaWN0IGEgTVVTVC1sZXZlbCByZXF1aXJlbWVudCBpbiBSRkMgNzIzMTxicj4N
CiZndDsmZ3Q7ICg8YSBocmVmPSJodHRwczovL25hMDEuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0
bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUyRnd3dy5ncmVlbmJ5dGVzLmRlJTJGdGVjaCUyRndl
YmRhdiUyRnJmYzcyMzEuaHRtbCUyM3JmYy5zZWN0aW9uLjYuMi5wLjMmYW1wO2RhdGE9MDIlN0Mw
MSU3Q01pY2hhZWwuQmlzaG9wJTQwbWljcm9zb2Z0LmNvbSU3Q2NlN2U0ZGQwNTdkZTRmMmYxZDgx
MDhkNGJjYWNiOTljJTdDNzJmOTg4YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDclN0MxJTdDMCU3
QzYzNjM0MDg5NzQxNzQ2OTQ3NCZhbXA7c2RhdGE9ZkpQeGZTckVlOUQzbjZsQXAwcm1pam5TR1Rh
b28yeVQ0WlphdG9CSTVGWSUzRCZhbXA7cmVzZXJ2ZWQ9MCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBz
Oi8vd3d3LmdyZWVuYnl0ZXMuZGUvdGVjaC93ZWJkYXYvcmZjNzIzMS5odG1sI3JmYy5zZWN0aW9u
LjYuMi5wLjM8L2E+KTxicj4NCiZndDs8YnI+DQomZ3Q7IFRoZSBzdGF0ZW1lbnQgZXhpc3RzIHNp
bmNlIHNlbmRpbmcgMTAzIG9ubHkgbWFrZXMgc2Vuc2Ugd2hlbiBpdCBpczxicj4NCiZndDsgaW1w
b3NzaWJsZSB0byBpbW1lZGlhdGVseSBzZW5kIGEgZmluYWwgcmVzcG9uc2UuPGJyPg0KJmd0Ozxi
cj4NCiZndDsgRm9yIGV4YW1wbGUsIHRoZXJlIGlzIG5vIG5lZWQgZm9yIGEgY2FjaGUgdGhhdCBp
cyBpbiBwb3NzZXNzaW9uIG9mIGE8YnI+DQomZ3Q7IGZyZXNobHktY2FjaGVkIGZpbmFsIHJlc3Bv
bnNlIHRvIHNlbmQgYSAxMDMgdGhhdCB3YXMgc2VudCBmcm9tIHRoZTxicj4NCiZndDsgb3JpZ2lu
IGJlZm9yZSBzZW5kaW5nIHRoZSBmaW5hbCByZXNwb25zZS4gSSBhbHNvIGJlbGlldmUgdGhhdCBt
b3N0PGJyPg0KJmd0OyBjYWNoaW5nIHByb3hpZXMgdGhhdCBleGlzdCB0b2RheSBkbyBub3QgY2Fj
aGUgaW5mb3JtYXRpb25hbCByZXNwb25zZXMsPGJyPg0KJmd0OyBhbmQgdGhhdCB0aGVyZSBpcyBu
byBuZWVkIGZvciB1cyB0byByZXF1aXJlIHRoZW0gdG8gZG8gc28uPGJyPg0KJmd0Ozxicj4NCiZn
dDsgQ29uc2lkZXJpbmcgdGhlIGZhY3RzLCBvbmUgd2F5IHRvIHJlc29sdmUgdGhlIGlzc3VlIHdv
dWxkIGJlIHRvIGFkanVzdDxicj4NCiZndDsgdGhlIHN0YXRlbWVudCB0byBzb21ldGhpbmcgbGlr
ZSAmcXVvdDtBbiBpbnRlcm1lZGlhcnkgTUFZIG9taXQgdGhlIDEwMzxicj4NCiZndDsgcmVzcG9u
c2Ugd2hlbiByZXNlbmRpbmcgYSBjYWNoZWQgcmVzcG9uc2UmcXVvdDssIGFuZCBhcmd1ZSB0aGF0
IHJlLXNlbmRpbmc8YnI+DQomZ3Q7IGEgY2FjaGVkIHJlc3BvbnNlIGlzIG5vdCBhbiBhY3Rpb24g
b2YgJnF1b3Q7Zm9yd2FyZGluZywmcXVvdDsgd2hpY2ggaXMgZGVmaW5lZDxicj4NCiZndDsgYXMg
YSBNVVNUIGluIFJGQyA3MjMxLjxicj4NCjxicj4NClNvdW5kcyBnb29kIHRvIG1lLjxicj4NCjxi
cj4NCiZndDsgQnV0IHdvdWxkbid0IGl0IGJlIHNpbXBsZXIgdG8ganVzdCBoYXZlIHRoZSAmcXVv
dDtNQVkgZHJvcCZxdW90OyBjbGF1c2UgZm9yIGFueTxicj4NCiZndDsgaW50ZXJtZWRpYXJ5Pzxi
cj4NCjxicj4NCkluIHRoYXQgY2FzZSwgdGhlIHNwZWMgd291bGQgY29udHJhZGljdCBSRkMgNzIz
MSwgd2hpY2ggaXMgYmFkIHBvc2l0aW9uPGJyPg0KdG8gYmUgaW4uLi48YnI+DQo8YnI+DQomZ3Q7
Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7VGhlIGZvbGxvd2luZyBleGFtcGxlIGlsbHVzdHJhdGVz
IGEgdHlwaWNhbCBtZXNzYWdlIGV4Y2hhbmdlIHRoYXQ8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJz
cDsgJm5ic3A7aW52b2x2ZXMgYSAxMDMgKEVhcmx5IEhpbnRzKSByZXNwb25zZS48YnI+DQomZ3Q7
Jmd0Ozxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDtDbGllbnQgcmVxdWVzdDo8YnI+
DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7R0VUIC8g
SFRUUC8xLjE8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO0hvc3Q6IDxh
IGhyZWY9Imh0dHBzOi8vbmEwMS5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJs
PWh0dHAlM0ElMkYlMkZleGFtcGxlLmNvbSZhbXA7ZGF0YT0wMiU3QzAxJTdDTWljaGFlbC5CaXNo
b3AlNDBtaWNyb3NvZnQuY29tJTdDY2U3ZTRkZDA1N2RlNGYyZjFkODEwOGQ0YmNhY2I5OWMlN0M3
MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM2MzQwODk3NDE3NDc5
NDg3JmFtcDtzZGF0YT1DUEZpVkYwUDNYZ0dRUzlFYUxLR1ZCdkZMa1ptWVRFZXZsMm0lMkJWZktH
cEklM0QmYW1wO3Jlc2VydmVkPTAiIHRhcmdldD0iX2JsYW5rIj4NCmV4YW1wbGUuY29tPC9hPjxi
cj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgKG1heWJlIGluc2VydCBibGFuayBsaW5lIGRvIGRl
bGltaXQgdGhlIG1lc3NhZ2UpPGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJz
cDsgJm5ic3A7U2VydmVyIHJlc3BvbnNlOjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtIVFRQLzEuMSAxMDMgRWFybHkgSGludHM8YnI+DQomZ3Q7
Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO0xpbms6ICZsdDsvc3R5bGUuY3NzJmd0Ozsg
cmVsPXByZWxvYWQ7IGFzPXN0eWxlPGJyPg0KJmd0OyZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDtMaW5rOiAmbHQ7L3NjcmlwdC5qcyZndDs7IHJlbD1wcmVsb2FkOyBhcz1zY3JpcHQ8YnI+
DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7SFRUUC8x
LjEgMjAwIE9LPGJyPg0KJmd0OyZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtEYXRlOiBG
cmksIDI2IE1heSAyMDE3IDEwOjAyOjExIEdNVDxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7Q29udGVudC1MZW5ndGg6IDEyMzQ8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwO0NvbnRlbnQtVHlwZTogdGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04PGJy
Pg0KJmd0OyZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtMaW5rOiAmbHQ7L3N0eWxlLmNz
cyZndDs7IHJlbD1wcmVsb2FkOyBhcz1zdHlsZTxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7TGluazogJmx0Oy9zY3JpcHQuanMmZ3Q7OyByZWw9cHJlbG9hZDsgYXM9c2Ny
aXB0PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
OyZsdDshZG9jdHlwZSBodG1sJmd0Ozxicj4NCiZndDsmZ3Q7Jm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7Wy4uLiByZXN0IG9mIHRoZSByZXNwb25zZSBib2R5IGlzIG9tbWl0dGVkIGZyb20gdGhl
IGV4YW1wbGUgLi4uXTxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgVGhlIGV4YW1wbGUgc3Vn
Z2VzdHMgdGhhdCBlYXJseSBoaW50cyBhcmUgcmVwZWF0ZWQgaW4gdGhlIGZpbmFsIHJlc3BvbnNl
LiBEbzxicj4NCiZndDsmZ3Q7IHRoZXkgaGF2ZSB0bywgYWN0dWFsbHk/PGJyPg0KJmd0Ozxicj4N
CiZndDsgWWVzLiBUaGV5IG5lZWQgdG8sIGVzcGVjaWFsbHkgaWYgY2FjaGluZyBpcyBpbnZvbHZl
ZC4gMTAzIGlzIGFuPGJyPg0KJmd0OyBpbnRlcm1lZGlhcnkgcmVzcG9uc2UgYW5kIHRoZXJlIGlz
IG5vIGd1YXJhbnRlZSAob3IgYSByZXF1aXJlbWVudCkgZm9yPGJyPg0KJmd0OyBhIGNhY2hlIHRv
IHJldGFpbiB0aGUgaGVhZGVycyBpbmNsdWRlZCBvbmx5IGluIHRoZSBpbmZvcm1hdGlvbmFsPGJy
Pg0KJmd0OyByZXNwb25zZS48YnI+DQomZ3Q7PGJyPg0KJmd0OyBJbiBjYXNlIG9mIGxpbmsgcmVs
PXByZWxvYWQgaGVhZGVycywgYSBjbGllbnQgY2FuIHNwZWN1bGF0aXZlbHkgbG9hZDxicj4NCiZn
dDsgdGhlIHJlc291cmNlcyBpbmNsdWRlZCBpbiB0aGUgaGVhZGVycyB3aGlsZSByZXZhbGlkYXRp
bmcgYTxicj4NCiZndDsgc3RhbGUtY2FjaGVkIHJlc3BvbnNlLCBvciBhIGNhY2hpbmcgcHJveHkg
Y2FuIGdlbmVyYXRlIGEgMTAzIHJlc3BvbnNlPGJyPg0KJmd0OyBmcm9tIGEgc3RhbGUtY2FjaGVk
IDIwMCByZXNwb25zZSwgd2hpbGUgd2FpdGluZyBmb3IgdGhlIG9yaWdpbiB0bzxicj4NCiZndDsg
cGVyZm9ybSByZXZhbGlkYXRpb24uPGJyPg0KPGJyPg0KV2hhdCBJJ20gYWZ0ZXIgaXMgYSBjbGVh
ciBzdGF0ZW1lbnQgd2hldGhlciB0aGV5IHJlYWxseSBuZWVkIHRvIGJlPGJyPg0KcmVwZWF0ZWQs
IGFzIG5vcm1hdGl2ZSBsYW5ndWFnZS48YnI+DQo8YnI+DQomZ3Q7IC4uLjxicj4NCjxicj4NCkJl
c3QgcmVnYXJkcywgSnVsaWFuPG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_MWHPR21MB014165751D58AFC33BF6993F87DF0MWHPR21MB0141namp_--


From nobody Tue Jun 27 10:13:19 2017
Return-Path: <magnus.westerlund@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 820C812EA53; Tue, 27 Jun 2017 10:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.219
X-Spam-Level: 
X-Spam-Status: No, score=-4.219 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, 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 Wz8GK2vFBeYK; Tue, 27 Jun 2017 10:13:14 -0700 (PDT)
Received: from sesbmg23.ericsson.net (sesbmg23.ericsson.net [193.180.251.37]) (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 E0BA012EA67; Tue, 27 Jun 2017 10:13:11 -0700 (PDT)
X-AuditID: c1b4fb25-eedff700000016ef-ab-595292257858
Received: from ESESSHC023.ericsson.se (Unknown_Domain [153.88.183.87]) by sesbmg23.ericsson.net (Symantec Mail Security) with SMTP id CE.46.05871.52292595; Tue, 27 Jun 2017 19:13:10 +0200 (CEST)
Received: from ESESSMB103.ericsson.se ([169.254.3.195]) by ESESSHC023.ericsson.se ([153.88.183.87]) with mapi id 14.03.0352.000; Tue, 27 Jun 2017 19:13:09 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: Donald Eastlake <d3e3e3@gmail.com>
CC: "tsv-art@ietf.org" <tsv-art@ietf.org>, "trill@ietf.org" <trill@ietf.org>,  IETF Discussion <ietf@ietf.org>, "draft-ietf-trill-over-ip.all@ietf.org" <draft-ietf-trill-over-ip.all@ietf.org>
Subject: Re: Tsvart early review of draft-ietf-trill-over-ip-10
Thread-Topic: Tsvart early review of draft-ietf-trill-over-ip-10
Thread-Index: AQHS7hA1g07jSLuZY0i4jyhkqH3mRw==
Date: Tue, 27 Jun 2017 17:13:09 +0000
Message-ID: <52E4A8FC978E0241AE652516E24CAF0029AC2251@ESESSMB103.ericsson.se>
References: <149754795560.13109.17521244075940607817@ietfa.amsl.com> <CAF4+nEG-28weDot9R9Z4-05PX1tzBoKZSOHu8BJY2GiRzOv0nA@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [153.88.183.147]
Content-Type: multipart/alternative; boundary="_000_52E4A8FC978E0241AE652516E24CAF0029AC2251ESESSMB103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprOIsWRmVeSWpSXmKPExsUyM2J7uK7apKBIg44mbouD2zUtPn+dxm7x bON8Fov3k7ezWczas4jFgdVj56y77B5LlvxkCmCK4rJJSc3JLEst0rdL4MrovTiZteBcO3PF y/3VDYwPdjF1MXJySAiYSHTfOApkc3EICRxhlNh9sJ8dwlnCKNGwuJEVpIpNwELi5o9GNhBb REBN4vXyBSwgRcwChxgljqzoBOrg4BAWsJe4skwMosZBYuHadnYIW0+ipX8fG0gJi4CqxJGX ESBhXgFficW/30Et7maUmPxkLdhFjAKyEve/32MBsZkFxCVuPZkPdamAxJI955khbFGJl4// sYLMlBBQkpi2NQ2iPF/i/e5+Joj5ghInZz5hmcAoPAvJpFlIymYhKYOI60gs2P2JDcLWlli2 8DUzjH3mwGMmZPEFjOyrGEWLU4uTctONjPVSizKTi4vz8/TyUks2MQKj6+CW36o7GC+/cTzE KMDBqMTDu6EtKFKINbGsuDIXGGYczEoivPm9QCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8jvsu RAgJpCeWpGanphakFsFkmTg4pRoYU5fo+p9+8ivfbMqGOHvpqMYn/lprbhpNMlkg8nS7mOux NWdnWh9b4C/wZZfn1suLf9xrmRKXOt3oQsa/U94FtutFH2ct8jq3vZTp217vgLMXli8wzu5Y mh48j0mlvE5/Q2Yid1zypxP7jR5zbH1yWk9iq8VEL/aC9CN3unhYTp1x2LvPWfnfciWW4oxE Qy3mouJEAGT7B/mqAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p_-P0Xa-WN-yNKGKHs8vAArxeAc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 17:13:17 -0000

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

Hi Donald,

After having read your response I think there is an important question abou=
t the applicability of this document that affects several of the issues bel=
ow and what solution you need. That is the question of what type of paths o=
ne expect to get Trill over IP working over. Because if the target is gener=
al Internet and also through middleboxes such as NATs and Firewall (Not int=
ending to block) then there are a lot more work to ensure this. If you for =
example changes the applicability to require any on path middleboxes to ful=
fill certain requirements things can be more easily addressed.


Den 2017-06-26 kl. 02:07, skrev Donald Eastlake:

Hi Magnus,

Thanks for the extensive review. See my responses below.

On Thu, Jun 15, 2017 at 1:32 PM, Magnus Westerlund
<magnus.westerlund@ericsson.com><mailto:magnus.westerlund@ericsson.com> wro=
te:



Diffserv usage
--------------

Section 4.3:

   TRILL over IP implementations MUST support setting the DSCP value in
   the outer IP Header of TRILL packets they send by mapping the TRILL
   priority and DEI to the DSCP. They MAY support, for a TRILL Data
   packet where the native frame payload is an IP packet, mapping the
   DSCP in this inner IP packet to the outer IP Header with the default
   for that mapping being to copy the DSCP without change.

I think it is fine to require that implementations are capable  of setting
DSCP values on the outer IP header. However, I fail to see any discussion o=
f
the potential issues with actually setting the DSCP values. It is one thing=
 to
do this in an IP back bone use case where one can know and have control ove=
r
the PHB that the DSCP values maps to. But otherwise, over general internet =
the
behavior is not that predictable. One can easily be subject to policers or
remapping. Also as the actual DSCP code point usage is domain specific this=
 is
difficult. Priority reversal is likely the least of the problems that this =
can
run into over general Internet.



It sounds like appropriate discussion and warnings about these issues
would resolve the above comment.

I would note that the choice of encapsulation here do becomes important. Yo=
ur's and Joe Touch's observation that for TCP, you can only have a single D=
SCP marking per TCP connection for example. For others, see the discussion =
in Section 5.1 of https://datatracker.ietf.org/doc/rfc7657/ on this issue.

David Black also raised an important question if one should treat this as a=
 tunnel with a single predictable behavior or let the inner networks markin=
g show through. Establishing a tunnel with a single PHB has less risk of ru=
nning into issues than multiple different markings.







Section 4.3:

   The default TRILL priority and DEI to DSCP mapping, which may be
   configured per TRILL over IP port, is an follows. Note that the DEI
   value does not affect the default mapping and, to provide a
   potentially lower priority service than the default priority 0,
   priority 1 is considered lower priority than 0. So the priority
   sequence from lower to higher priority is 1, 0, 2, 3, 4, 5, 6, 7.

      TRILL Priority  DEI  DSCP Field (Binary/decimal)
      --------------  ---  -----------------------------
                  0   0/1  001000 / 8
                  1   0/1  000000 / 0
                  2   0/1  010000 / 16
                  3   0/1  011000 / 24
                  4   0/1  100000 / 32
                  5   0/1  101000 / 40
                  6   0/1  110000 / 48
                  7   0/1  111000 / 56

This appear to be an problematic mapping. At least for prio 0 and 1. As
priority 1 appears to be intended to be higher than priority 0, it is
interesting that it is mapped to CS1, which to quote
https://datatracker.ietf.org/doc/rfc7657/:

CS1 ('001000') was subsequently designated as the recommended
      codepoint for the Lower Effort (LE) PHB [RFC3662].

So what is proposed can in a network using default mapping, result in that =
you
get priority 0 to be lower priority than 1. Plus that in some networks this=
 can
also results in strange remapping that results in a different PHB for CS1 t=
han.



The intent in the draft is to reflect the default relative priority of
the different priority code points in IEEE Std 802.1Q where priority 1
is lower than priority 0. At a quick look, it appears to me that RFC
2474 requires that 0x001000 be handled as being of a priority not
lower than the priority with which 0x000000 is handled. Yet RFC 3662,
which you point to, seems to suggest using 0x001000 as a lower
priority code point than 0x000000. Given that 3662 not only does not
update 2474 but is only Informational while 2474 is Standards Track, I
would say that 2474 dominates and that this draft makes the best
assumptions it can about default behavior...

David Black provide a good answer on this.






MTU and Fragmentation
---------------------

I think there are two main issue here. The first one is MTUD discovery
of the actual IP path MTU between the ports. That will be needed to prevent
a lot of traffic going into MTU black holes. Especially as TRILL requries
1470 byte support which is likey above a lot of paths.



Seems like it would depend on the environments where TRILL was used.
For example, I do not think 1470 would be a problem in most Data
Center or Internet Exchange point uses, for example. Data Centers
sometimes support 9K jumbo frames and the like.

In fact, it is probably bad to focus too much on 1470 -- that is a
required minimum to be sure that reasonable size link state PDUs can
be successfully flooded through the TRILL campus so that routing will
work. However, it would commonly be the case that, for the TRILL
campus to be useful in a particular case, links need to be able to
carry the expected size TRILL Data packets. For example, if there were
two parts of a TRILL campus connected by one or a few TRILL over IP
links and the end stations in each part were assuming they could use
1500 byte Ethernet packets, then the TRILL over IP links would need to
support an MTU based on 1500 + TRILL Header + IP and TRILL over IP
encapsulation. And more if security was being used or there were any
other reasons for additional headers/encapsulation...

Yes, and over general Internet you should be happy if you get 1500 bytes of=
 IP MTU, it may easily be lower with a couple of additional tunnel headers.=
 Thus, what you say is the goal is not feasible without a solution that sup=
ports fragmentation and reassembly, enabling one TRILL packet to be sent in=
 multiple IP packets. The re-assembly do requires buffering and not somethi=
ng to easily perform on a router fast path. And attempting to use IP fragme=
ntation is likely doomed if you have any type of NAT or Firewall in the way=
.

This points to a dedicated solution or using a transport protocol that supp=
orts carrying arbitrary data sizes, like TCP or SCTP. And you need to use t=
he byte-stream API of TCP to achieve this.






Section 8.4:

   Path MTU discovery [RFC4821] should be useful
   in determining the IP MTU between a pair of RBridge ports with IP
   connectivity.

The issue with RFC4821 is that it has requirements on the packetization lay=
er.
Trill appears to have several components that are useful. However, it will
require a specification of the procedure to result in a useful tool.



See below.



Section 8.4:

   TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
   [RFC7177], can be used to obtain added assurance of the MTU of a
   link.

Yes, that can confirm working MTUs that are at 1470 or above, but appears
prevented from working below 1470?



While there is a minimum size for TRILL IS-IS MTU PDUs, determined by
header size, it is well below 1470, probably (depending on whether
secuirty is in use, etc.) below 150 bytes.

Okay, if you say so, it was not obvious from the spec that is was allowed t=
o probe for paths with lesser MTUs than 1470.






Thus, it appears that there is a lack of mechanism here to actually get a v=
alid
and functional MTU from TRILL in the cases where the Path MTU is below 1470=
. If
I am wrong good, but I think this is an important piece for how to handle t=
he
next main issue.



How about referencing Section 3 of
https://tools.ietf.org/html/draft-ietf-trill-mtu-negotiation-05
which is currently in IETF Last Call? (The wording of that section is
probably going to be improved based on an OPS review by Brian
Carpenter.)

I looked at this, and it appears to have the same issue, that it can't prob=
e for MTU values below 1470.


   2) RB1 tries to send an MTU-probe padded to the size 1470.

      a) If RB1 fails to receive an MTU-ack from RB2 after k tries, RB1
         sets the "failed minimum MTU test" flag for RB2 in RB1's Hello
         and stop.


But, the algorithm clearly performs a binary search for the MTU. If
one look at RFC 4821 one will notice that there are some additional conside=
rations
there how to make the probing better and robuster. But, cleary Trill has so=
me other
criterias for what is a success. Verification that Sz works appears suffici=
ent,
and there are no need to probe further upwards.








UDP encapsulation and IP fragments.


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


I see it as a big issue that UDP encapsulation is the native one, and that
relies on IP fragmentation despite the need for reliable fragmentation. Wit=
h
the setup of having to support 1470 MTU on TRILL level some packets will be
fragmented in many environments. That will lead to a lot of losses, and as
discussed below a very big problem with middleboxes. The main problem here =
is
that if one tries to rely on IP fragments one will have issues with packets
ending up in black holes. And different problems depending on IPv4 or IPv6.
IPv6 is lilkely the lesser problem assuming that one have working PMTUD.

There are several ways out of this.

1. Detect issues and use TCP encapsulation with correctly set MSS to not ge=
t IP
fragements 2. Determine MTU and implement an fragmentation mechanism on top=
 of
UDP.



So, I don't see that much problem with UDP being the general default
consistent with the TRILL philosophy of defaulting to need zero or
minimal configuration. The default should be to use multicast Hellos
for discovery of neighbors which sure points at UDP to me. Having to
traverse a NAT should be a rare case. Since, in the NAT case, you have
to configure things related to the static binding and the IP
address(es) of peer(s) anyway you can also configure to use a
different encapsulation than UDP, such as TCP, at the same time. I
don't see it as much of a problem if, by default, TRILL won't operate
through a NAT. If you are using UDP and it fragments and fragments are
dropped at a NAT, probably you can't exchange Hellos so you will not
form an adjacency and anything on the other side of the NAT will not
be visible.

Yes, but this is the issue of applicability and documenting that applicabil=
ity. I don't know what goals and requirements that exist for Trill. If the =
WG are fine with some restrictions, then document them and focus on solving=
 the issues that must be solved.

You can clearly choose to require TCP for cases where the IP MTU is insuffi=
cient for carrying the Sz sized trill packets between the RBs using UDP.






Zero Checksum:
--------------

Section 5.4:

UDP Checksum - as specified in [RFC0768]

Considering the fast path encapsulation desire, I am surprised to not see a=
ny
mentioning of use of zero checksum here. Raising the zero checksum and forw=
ard
reference would be good I think.

And then Section 8.5:

   The requirements for the usage of the zero UDP Checksum in a UDP
   tunnel protocol are detailed in [RFC6936]. These requirements apply
   to the UDP based TRILL over IP encapsulations specified herein
   (native and VXLAN), which are applications of UDP tunnel.

If you actually intended to allow zero checksum, then you actually should
document that Trill fulfills the requirements that the applicability statem=
ent
raises. I have not analyzed how well it meets these requirements.

Please review Section 6.2 of RFC 8086 for example how that can be done.



OK. We'll look into it.



TCP Encapsulation issue
-----------------------

Section 5.6:

The TCP encapsulation appear to be missing an delimiter format allowing eac=
h
individual TRILL packet/payload to be read out of the TCP's byte stream. In
other words, a normal implementation has no way of ensuring that the TCP
payload starts with the start of a new TRILL payload. Multiple small TRILL
payloads may be included in the same TCP payload, and also only parts as TC=
P is
one way of dealing with TRILL packets that are larger than the IP+Encapsula=
tion
MTU that actually will work.

This comment is based on that there appear to be no length fields included =
in
the TRILL header. The most straight forward delimiter is a 2-byte length fi=
eld
for the TRILL payload to be encapsulated.



Right. It might also be useful to include some sort of check field, as
is done in BGP, to detect if you are out of sync in parsing the TCP
stream.

As you need to actually perform re-assembly, the solution is to use the byt=
e stream semantics the TCP API provides and have a framing for each packet.




Another point is that, while with UDP it seems fine to send packets
with assorted QoS, you don't want to encourage re-ordering of TCP
packets in a stream. So if TCP encapsulation is being used, you want
to use the same DSCP value for the packets in a particular TCP stream.
So, generally, you need to have a TCP connection per priority handling
category. Mapping the 8 priority levels into a smaller number of
handling categories is a normal thing to do so you certainly don't
necessarily need 8 TCP connections. Adding material on this should not
be too hard.

Yes, agreed it is a possibility and points into possible considerations tha=
t David raised.






Section 5.6:

TCP endpoint requirements. I do wonder if an application like TRILL actual
would need to discuss performance impacting implementation choices or
limitations. For example use of NAGLE, the requirements on buffer sizes in
relation to Bandwidth delay products, as buffer memory in a RBridge will im=
pact
performance.



Well, I'm not sure how deeply this document should get into such
performance issues. What about just saying something about
consideration being given to tuning TCP for performance and pointing
to one or a few other RFCs that talk about this?

As Joe said, these are important considerations. If your intention is to en=
able this to run at substantial fractions of line rates of the interfaces. =
Then this do require considerations.






Congestion Control
------------------
First thanks for the effort here.



You're welcome.



8.1.2 In Other Environments

   Where UDP based encapsulation headers are used in TRILL over IP in
   environments other than those discussed in Section 8.1.1, specific
   congestion control mechanisms are commonly needed.  However, if the
   traffic being carried by the TRILL over IP link is already congestion
   controlled and the size and volatility of the TRILL IS-IS link state
   database is limited, then specific congestion control may not be
   needed. See [RFC8085] Section 3.1.11 for further guidance.

This is correct, however my question is if the RBridges have any way of kno=
wing
which traffic is actually congestion controlled, considering that TRILL pro=
vides
an layer 2 abstraction. I wonder if there should be any type of white list =
of
the types of layer 2 payloads that can be assumed to be congestion controll=
ed,
and thus okay to forward over IP paths? I am worried that without any
recommendation to prevent traffic that is not controlled to be forwarded, c=
an
lead to congestion issues.

The other issue I think may exist is the issue serial unicast emulation of
broadcast/multicast creates. As this amplifies the outgoing packet rate wit=
h
a factor of how many addresses are configured for serial unicast this can
be significant traffic expansion. Thus, I think additional considerations a=
re
needed here, and maybe rate limiting of the amount of traffic to be multica=
sted.



OK. We can think about those issues.



Flow and ECMP
-------------

Section 8.3:

For example, for TRILL
   Data, this entropy field could be based on some hash of the
   Inner.MacDA, Inner.MacSA, and Inner.VLAN or Inner.FGL.

I would appreciate clearer references to what these fields are.



In a TRILL Data packet, the payload after the TRILL Header looks like
an Ethernet frame except that there is always either a VLAN tag or,
alternatively, where the VLAN tag would be, a Fine Grained Label
[RFC7172]. (The preceding is the view in the TRILL RFCs, but there is
an equivalent and equally valid view in which all the fields through
and including the VLAN or FGL tag are part of the TRILL Header.) The
TRILL base protocol specification focuses on Ethernet as a link
technology between TRILL switches, in which case there will be a link
header including an Outer.MacDA and Outer.MacSA fields and possibly an
Outer.VLAN, all before the TRILL Header. See Figure 1 and Figure 2 in
RFC 7172.

Some of the above could be added to the draft for clarity.



If I understand this correctly, the idea here is to look into the inner
layer 2 frames, and use the flow equivalents that exists on that level and
hash that into value that maps the flows onto the source port range.



Yes.



I think this text should include a summary of the principle and ensure to
note the important requirement that what is considered flows in the inner
must not result in being striped over multiple source ports as this may lea=
d to
reordering issues due to packets taking different paths.



Well, we can add some text. But when would the relative ordering
matter for two TRILL Data packets where the two inner native payloads
have different values for any one or more of these three fields
(Inner.MacDA, Inner.MacSA, and inner VLAN/FGL tag) ? If any of those
fields are different, you are talking about different streams.

Okay, then this is very straightforward.






NAT and TRILL over IP:
Section 8.5:

If one like to use TRILL over IP through a NAT, then there are some very
important considerations that are missing. First the need for static bindin=
g
configurations or the need for determining ones external address(es) and be
able to communicate that to the peer RBridges, and in addition ensure that =
one
has keep-alives to that the NAT binding never times out.



I think those are good points. There is an additional problem that
TRILL Hellos detect neighbors with which they have 2-way connectivity
by indicating, inside the Hellos that are sent, from what neighbors
Hellos have been received on that port. If a NAT is involved, these
neighbor addresses inside Hellos need to be mapped.

Yes, and the question is how that can be handled, by the receiver of the pa=
cket, or if the sender needs to determine what address it uses and provide =
that in the HELLOs. If the first is possible that can simplify a lot.






Next is the issue that there is almost zero chance of getting a IP/UDP
encapsulation TRILL payload through the NAT if it results in IP fragmentati=
on,
as NATs don't do defragment and refragmented on the internal side, and an I=
P
fragment lacks UDP port and thus can't be matched to binding.



So perhaps the recommendation should be to configure the port to use
TCP if there will be fragmentation.


Yes, I think that are likely the simplest solution for you.





Also if you like to run IP/ESP through a NAT, then you most likely need the
IP/UDP/ESP encapsulation (https://tools.ietf.org/html/rfc3948). Note that t=
his
will restrict the MTU even further and thus ensure that the 1470 requiremen=
t
cannot be fulfilled even without additional tunnels over an 1500 bytes MTU
Ethernet infrastructure.

I would note that also firewalls likely have issues with IP fragments for t=
he
same reason, they require significant amount of state to be verified if the=
y
should be let through.

In general I think you should create a configuration that has chance to wor=
k
through most middleboxes, but I think you should require static bindings. I
think that configuration is, and don't laugh now, but IP/UDP/ESP/TCP/TRILL,
otherwise you will not be able to have both security and reliable fragmenta=
tion
of TRILL packets.



OK. Thanks again for this review. It has pointed out a number of
problems and in thinking about those, I believe a couple of further
problems have come to mind that I mentioned above. We'll work on a
revised draft.





Cheers

Magnus Westerlund

----------------------------------------------------------------------
Media Technologies, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com<mailto=
:magnus.westerlund@ericsson.com>
----------------------------------------------------------------------

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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body text=3D"#000000" bgcolor=3D"#FFFFFF">
<div class=3D"moz-cite-prefix">Hi Donald,<br>
<br>
After having read your response I think there is an important question abou=
t the applicability of this document that affects several of the issues bel=
ow and what solution you need. That is the question of what type of paths o=
ne expect to get Trill over IP working
 over. Because if the target is general Internet and also through middlebox=
es such as NATs and Firewall (Not intending to block) then there are a lot =
more work to ensure this. If you for example changes the applicability to r=
equire any on path middleboxes to
 fulfill certain requirements things can be more easily addressed. <br>
<br>
<br>
Den 2017-06-26 kl. 02:07, skrev Donald Eastlake:<br>
</div>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">Hi Magnus,=0A=
=0A=
Thanks for the extensive review. See my responses below.=0A=
=0A=
On Thu, Jun 15, 2017 at 1:32 PM, Magnus Westerlund=0A=
<a class=3D"moz-txt-link-rfc2396E" href=3D"mailto:magnus.westerlund@ericsso=
n.com">&lt;magnus.westerlund@ericsson.com&gt;</a> wrote:=0A=
</pre>
<br>
<blockquote type=3D"cite">
<pre wrap=3D"">Diffserv usage=0A=
--------------=0A=
=0A=
Section 4.3:=0A=
=0A=
   TRILL over IP implementations MUST support setting the DSCP value in=0A=
   the outer IP Header of TRILL packets they send by mapping the TRILL=0A=
   priority and DEI to the DSCP. They MAY support, for a TRILL Data=0A=
   packet where the native frame payload is an IP packet, mapping the=0A=
   DSCP in this inner IP packet to the outer IP Header with the default=0A=
   for that mapping being to copy the DSCP without change.=0A=
=0A=
I think it is fine to require that implementations are capable  of setting=
=0A=
DSCP values on the outer IP header. However, I fail to see any discussion o=
f=0A=
the potential issues with actually setting the DSCP values. It is one thing=
 to=0A=
do this in an IP back bone use case where one can know and have control ove=
r=0A=
the PHB that the DSCP values maps to. But otherwise, over general internet =
the=0A=
behavior is not that predictable. One can easily be subject to policers or=
=0A=
remapping. Also as the actual DSCP code point usage is domain specific this=
 is=0A=
difficult. Priority reversal is likely the least of the problems that this =
can=0A=
run into over general Internet.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
It sounds like appropriate discussion and warnings about these issues=0A=
would resolve the above comment.</pre>
</blockquote>
<br>
I would note that the choice of encapsulation here do becomes important. Yo=
ur's and Joe Touch's observation that for TCP, you can only have a single D=
SCP marking per TCP connection for example. For others, see the discussion =
in Section 5.1 of
<a class=3D"moz-txt-link-freetext" href=3D"https://datatracker.ietf.org/doc=
/rfc7657/">
https://datatracker.ietf.org/doc/rfc7657/</a> on this issue. <br>
<br>
David Black also raised an important question if one should treat this as a=
 tunnel with a single predictable behavior or let the inner networks markin=
g show through. Establishing a tunnel with a single PHB has less risk of ru=
nning into issues than multiple
 different markings. <br>
<br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">Section 4.3:=0A=
=0A=
   The default TRILL priority and DEI to DSCP mapping, which may be=0A=
   configured per TRILL over IP port, is an follows. Note that the DEI=0A=
   value does not affect the default mapping and, to provide a=0A=
   potentially lower priority service than the default priority 0,=0A=
   priority 1 is considered lower priority than 0. So the priority=0A=
   sequence from lower to higher priority is 1, 0, 2, 3, 4, 5, 6, 7.=0A=
=0A=
      TRILL Priority  DEI  DSCP Field (Binary/decimal)=0A=
      --------------  ---  -----------------------------=0A=
                  0   0/1  001000 / 8=0A=
                  1   0/1  000000 / 0=0A=
                  2   0/1  010000 / 16=0A=
                  3   0/1  011000 / 24=0A=
                  4   0/1  100000 / 32=0A=
                  5   0/1  101000 / 40=0A=
                  6   0/1  110000 / 48=0A=
                  7   0/1  111000 / 56=0A=
=0A=
This appear to be an problematic mapping. At least for prio 0 and 1. As=0A=
priority 1 appears to be intended to be higher than priority 0, it is=0A=
interesting that it is mapped to CS1, which to quote=0A=
<a class=3D"moz-txt-link-freetext" href=3D"https://datatracker.ietf.org/doc=
/rfc7657/">https://datatracker.ietf.org/doc/rfc7657/</a>:=0A=
=0A=
CS1 ('001000') was subsequently designated as the recommended=0A=
      codepoint for the Lower Effort (LE) PHB [RFC3662].=0A=
=0A=
So what is proposed can in a network using default mapping, result in that =
you=0A=
get priority 0 to be lower priority than 1. Plus that in some networks this=
 can=0A=
also results in strange remapping that results in a different PHB for CS1 t=
han.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
The intent in the draft is to reflect the default relative priority of=0A=
the different priority code points in IEEE Std 802.1Q where priority 1=0A=
is lower than priority 0. At a quick look, it appears to me that RFC=0A=
2474 requires that 0x001000 be handled as being of a priority not=0A=
lower than the priority with which 0x000000 is handled. Yet RFC 3662,=0A=
which you point to, seems to suggest using 0x001000 as a lower=0A=
priority code point than 0x000000. Given that 3662 not only does not=0A=
update 2474 but is only Informational while 2474 is Standards Track, I=0A=
would say that 2474 dominates and that this draft makes the best=0A=
assumptions it can about default behavior...</pre>
</blockquote>
<br>
David Black provide a good answer on this. <br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">MTU and Fragmentation=0A=
---------------------=0A=
=0A=
I think there are two main issue here. The first one is MTUD discovery=0A=
of the actual IP path MTU between the ports. That will be needed to prevent=
=0A=
a lot of traffic going into MTU black holes. Especially as TRILL requries=
=0A=
1470 byte support which is likey above a lot of paths.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
Seems like it would depend on the environments where TRILL was used.=0A=
For example, I do not think 1470 would be a problem in most Data=0A=
Center or Internet Exchange point uses, for example. Data Centers=0A=
sometimes support 9K jumbo frames and the like.=0A=
=0A=
In fact, it is probably bad to focus too much on 1470 -- that is a=0A=
required minimum to be sure that reasonable size link state PDUs can=0A=
be successfully flooded through the TRILL campus so that routing will=0A=
work. However, it would commonly be the case that, for the TRILL=0A=
campus to be useful in a particular case, links need to be able to=0A=
carry the expected size TRILL Data packets. For example, if there were=0A=
two parts of a TRILL campus connected by one or a few TRILL over IP=0A=
links and the end stations in each part were assuming they could use=0A=
1500 byte Ethernet packets, then the TRILL over IP links would need to=0A=
support an MTU based on 1500 &#43; TRILL Header &#43; IP and TRILL over IP=
=0A=
encapsulation. And more if security was being used or there were any=0A=
other reasons for additional headers/encapsulation...</pre>
</blockquote>
<br>
Yes, and over general Internet you should be happy if you get 1500 bytes of=
 IP MTU, it may easily be lower with a couple of additional tunnel headers.=
 Thus, what you say is the goal is not feasible without a solution that sup=
ports fragmentation and reassembly,
 enabling one TRILL packet to be sent in multiple IP packets. The re-assemb=
ly do requires buffering and not something to easily perform on a router fa=
st path. And attempting to use IP fragmentation is likely doomed if you hav=
e any type of NAT or Firewall in
 the way. <br>
<br>
This points to a dedicated solution or using a transport protocol that supp=
orts carrying arbitrary data sizes, like TCP or SCTP. And you need to use t=
he byte-stream API of TCP to achieve this.
<br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">Section 8.4:=0A=
=0A=
   Path MTU discovery [RFC4821] should be useful=0A=
   in determining the IP MTU between a pair of RBridge ports with IP=0A=
   connectivity.=0A=
=0A=
The issue with RFC4821 is that it has requirements on the packetization lay=
er.=0A=
Trill appears to have several components that are useful. However, it will=
=0A=
require a specification of the procedure to result in a useful tool.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
See below.=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">Section 8.4:=0A=
=0A=
   TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in=0A=
   [RFC7177], can be used to obtain added assurance of the MTU of a=0A=
   link.=0A=
=0A=
Yes, that can confirm working MTUs that are at 1470 or above, but appears=
=0A=
prevented from working below 1470?=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
While there is a minimum size for TRILL IS-IS MTU PDUs, determined by=0A=
header size, it is well below 1470, probably (depending on whether=0A=
secuirty is in use, etc.) below 150 bytes.</pre>
</blockquote>
<br>
Okay, if you say so, it was not obvious from the spec that is was allowed t=
o probe for paths with lesser MTUs than 1470.
<br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">Thus, it appears that there is a lack of mechanism here to a=
ctually get a valid=0A=
and functional MTU from TRILL in the cases where the Path MTU is below 1470=
. If=0A=
I am wrong good, but I think this is an important piece for how to handle t=
he=0A=
next main issue.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
How about referencing Section 3 of=0A=
<a class=3D"moz-txt-link-freetext" href=3D"https://tools.ietf.org/html/draf=
t-ietf-trill-mtu-negotiation-05">https://tools.ietf.org/html/draft-ietf-tri=
ll-mtu-negotiation-05</a>=0A=
which is currently in IETF Last Call? (The wording of that section is=0A=
probably going to be improved based on an OPS review by Brian=0A=
Carpenter.)</pre>
</blockquote>
<br>
I looked at this, and it appears to have the same issue, that it can't prob=
e for MTU values below 1470.
<br>
<br>
<pre class=3D"newpage">   2) RB1 tries to send an MTU-probe padded to the s=
ize 1470.=0A=
=0A=
      a) If RB1 fails to receive an MTU-ack from RB2 after k tries, RB1=0A=
         sets the &quot;failed minimum MTU test&quot; flag for RB2 in RB1's=
 Hello=0A=
         and stop.=0A=
=0A=
=0A=
But, the algorithm clearly performs a binary search for the MTU. If =0A=
one look at RFC 4821 one will notice that there are some additional conside=
rations=0A=
there how to make the probing better and robuster. But, cleary Trill has so=
me other=0A=
criterias for what is a success. Verification that Sz works appears suffici=
ent, =0A=
and there are no need to probe further upwards. =0A=
</pre>
<br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">UDP encapsulation and IP fragments.=0A=
</pre>
</blockquote>
<pre wrap=3D"">  ----------------------------------=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">I see it as a big issue that UDP encapsulation is the native=
 one, and that=0A=
relies on IP fragmentation despite the need for reliable fragmentation. Wit=
h=0A=
the setup of having to support 1470 MTU on TRILL level some packets will be=
=0A=
fragmented in many environments. That will lead to a lot of losses, and as=
=0A=
discussed below a very big problem with middleboxes. The main problem here =
is=0A=
that if one tries to rely on IP fragments one will have issues with packets=
=0A=
ending up in black holes. And different problems depending on IPv4 or IPv6.=
=0A=
IPv6 is lilkely the lesser problem assuming that one have working PMTUD.=0A=
=0A=
There are several ways out of this.=0A=
=0A=
1. Detect issues and use TCP encapsulation with correctly set MSS to not ge=
t IP=0A=
fragements 2. Determine MTU and implement an fragmentation mechanism on top=
 of=0A=
UDP.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
So, I don't see that much problem with UDP being the general default=0A=
consistent with the TRILL philosophy of defaulting to need zero or=0A=
minimal configuration. The default should be to use multicast Hellos=0A=
for discovery of neighbors which sure points at UDP to me. Having to=0A=
traverse a NAT should be a rare case. Since, in the NAT case, you have=0A=
to configure things related to the static binding and the IP=0A=
address(es) of peer(s) anyway you can also configure to use a=0A=
different encapsulation than UDP, such as TCP, at the same time. I=0A=
don't see it as much of a problem if, by default, TRILL won't operate=0A=
through a NAT. If you are using UDP and it fragments and fragments are=0A=
dropped at a NAT, probably you can't exchange Hellos so you will not=0A=
form an adjacency and anything on the other side of the NAT will not=0A=
be visible.</pre>
</blockquote>
<br>
Yes, but this is the issue of applicability and documenting that applicabil=
ity. I don't know what goals and requirements that exist for Trill. If the =
WG are fine with some restrictions, then document them and focus on solving=
 the issues that must be solved.
<br>
<br>
You can clearly choose to require TCP for cases where the IP MTU is insuffi=
cient for carrying the Sz sized trill packets between the RBs using UDP.
<br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">Zero Checksum:=0A=
--------------=0A=
=0A=
Section 5.4:=0A=
=0A=
UDP Checksum - as specified in [RFC0768]=0A=
=0A=
Considering the fast path encapsulation desire, I am surprised to not see a=
ny=0A=
mentioning of use of zero checksum here. Raising the zero checksum and forw=
ard=0A=
reference would be good I think.=0A=
=0A=
And then Section 8.5:=0A=
=0A=
   The requirements for the usage of the zero UDP Checksum in a UDP=0A=
   tunnel protocol are detailed in [RFC6936]. These requirements apply=0A=
   to the UDP based TRILL over IP encapsulations specified herein=0A=
   (native and VXLAN), which are applications of UDP tunnel.=0A=
=0A=
If you actually intended to allow zero checksum, then you actually should=
=0A=
document that Trill fulfills the requirements that the applicability statem=
ent=0A=
raises. I have not analyzed how well it meets these requirements.=0A=
=0A=
Please review Section 6.2 of RFC 8086 for example how that can be done.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
OK. We'll look into it.=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">TCP Encapsulation issue=0A=
-----------------------=0A=
=0A=
Section 5.6:=0A=
=0A=
The TCP encapsulation appear to be missing an delimiter format allowing eac=
h=0A=
individual TRILL packet/payload to be read out of the TCP's byte stream. In=
=0A=
other words, a normal implementation has no way of ensuring that the TCP=0A=
payload starts with the start of a new TRILL payload. Multiple small TRILL=
=0A=
payloads may be included in the same TCP payload, and also only parts as TC=
P is=0A=
one way of dealing with TRILL packets that are larger than the IP&#43;Encap=
sulation=0A=
MTU that actually will work.=0A=
=0A=
This comment is based on that there appear to be no length fields included =
in=0A=
the TRILL header. The most straight forward delimiter is a 2-byte length fi=
eld=0A=
for the TRILL payload to be encapsulated.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
Right. It might also be useful to include some sort of check field, as=0A=
is done in BGP, to detect if you are out of sync in parsing the TCP=0A=
stream.</pre>
</blockquote>
<br>
As you need to actually perform re-assembly, the solution is to use the byt=
e stream semantics the TCP API provides and have a framing for each packet.
<br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
Another point is that, while with UDP it seems fine to send packets=0A=
with assorted QoS, you don't want to encourage re-ordering of TCP=0A=
packets in a stream. So if TCP encapsulation is being used, you want=0A=
to use the same DSCP value for the packets in a particular TCP stream.=0A=
So, generally, you need to have a TCP connection per priority handling=0A=
category. Mapping the 8 priority levels into a smaller number of=0A=
handling categories is a normal thing to do so you certainly don't=0A=
necessarily need 8 TCP connections. Adding material on this should not=0A=
be too hard.</pre>
</blockquote>
<br>
Yes, agreed it is a possibility and points into possible considerations tha=
t David raised.
<br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">Section 5.6:=0A=
=0A=
TCP endpoint requirements. I do wonder if an application like TRILL actual=
=0A=
would need to discuss performance impacting implementation choices or=0A=
limitations. For example use of NAGLE, the requirements on buffer sizes in=
=0A=
relation to Bandwidth delay products, as buffer memory in a RBridge will im=
pact=0A=
performance.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
Well, I'm not sure how deeply this document should get into such=0A=
performance issues. What about just saying something about=0A=
consideration being given to tuning TCP for performance and pointing=0A=
to one or a few other RFCs that talk about this?</pre>
</blockquote>
<br>
As Joe said, these are important considerations. If your intention is to en=
able this to run at substantial fractions of line rates of the interfaces. =
Then this do require considerations.
<br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">Congestion Control=0A=
------------------=0A=
First thanks for the effort here.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
You're welcome.=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">8.1.2 In Other Environments=0A=
=0A=
   Where UDP based encapsulation headers are used in TRILL over IP in=0A=
   environments other than those discussed in Section 8.1.1, specific=0A=
   congestion control mechanisms are commonly needed.  However, if the=0A=
   traffic being carried by the TRILL over IP link is already congestion=0A=
   controlled and the size and volatility of the TRILL IS-IS link state=0A=
   database is limited, then specific congestion control may not be=0A=
   needed. See [RFC8085] Section 3.1.11 for further guidance.=0A=
=0A=
This is correct, however my question is if the RBridges have any way of kno=
wing=0A=
which traffic is actually congestion controlled, considering that TRILL pro=
vides=0A=
an layer 2 abstraction. I wonder if there should be any type of white list =
of=0A=
the types of layer 2 payloads that can be assumed to be congestion controll=
ed,=0A=
and thus okay to forward over IP paths? I am worried that without any=0A=
recommendation to prevent traffic that is not controlled to be forwarded, c=
an=0A=
lead to congestion issues.=0A=
=0A=
The other issue I think may exist is the issue serial unicast emulation of=
=0A=
broadcast/multicast creates. As this amplifies the outgoing packet rate wit=
h=0A=
a factor of how many addresses are configured for serial unicast this can=
=0A=
be significant traffic expansion. Thus, I think additional considerations a=
re=0A=
needed here, and maybe rate limiting of the amount of traffic to be multica=
sted.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
OK. We can think about those issues.=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">Flow and ECMP=0A=
-------------=0A=
=0A=
Section 8.3:=0A=
=0A=
For example, for TRILL=0A=
   Data, this entropy field could be based on some hash of the=0A=
   Inner.MacDA, Inner.MacSA, and Inner.VLAN or Inner.FGL.=0A=
=0A=
I would appreciate clearer references to what these fields are.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
In a TRILL Data packet, the payload after the TRILL Header looks like=0A=
an Ethernet frame except that there is always either a VLAN tag or,=0A=
alternatively, where the VLAN tag would be, a Fine Grained Label=0A=
[RFC7172]. (The preceding is the view in the TRILL RFCs, but there is=0A=
an equivalent and equally valid view in which all the fields through=0A=
and including the VLAN or FGL tag are part of the TRILL Header.) The=0A=
TRILL base protocol specification focuses on Ethernet as a link=0A=
technology between TRILL switches, in which case there will be a link=0A=
header including an Outer.MacDA and Outer.MacSA fields and possibly an=0A=
Outer.VLAN, all before the TRILL Header. See Figure 1 and Figure 2 in=0A=
RFC 7172.=0A=
=0A=
Some of the above could be added to the draft for clarity.=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">If I understand this correctly, the idea here is to look int=
o the inner=0A=
layer 2 frames, and use the flow equivalents that exists on that level and=
=0A=
hash that into value that maps the flows onto the source port range.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
Yes.=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">I think this text should include a summary of the principle =
and ensure to=0A=
note the important requirement that what is considered flows in the inner=
=0A=
must not result in being striped over multiple source ports as this may lea=
d to=0A=
reordering issues due to packets taking different paths.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
Well, we can add some text. But when would the relative ordering=0A=
matter for two TRILL Data packets where the two inner native payloads=0A=
have different values for any one or more of these three fields=0A=
(Inner.MacDA, Inner.MacSA, and inner VLAN/FGL tag) ? If any of those=0A=
fields are different, you are talking about different streams.</pre>
</blockquote>
<br>
Okay, then this is very straightforward. <br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">NAT and TRILL over IP:=0A=
Section 8.5:=0A=
=0A=
If one like to use TRILL over IP through a NAT, then there are some very=0A=
important considerations that are missing. First the need for static bindin=
g=0A=
configurations or the need for determining ones external address(es) and be=
=0A=
able to communicate that to the peer RBridges, and in addition ensure that =
one=0A=
has keep-alives to that the NAT binding never times out.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
I think those are good points. There is an additional problem that=0A=
TRILL Hellos detect neighbors with which they have 2-way connectivity=0A=
by indicating, inside the Hellos that are sent, from what neighbors=0A=
Hellos have been received on that port. If a NAT is involved, these=0A=
neighbor addresses inside Hellos need to be mapped.</pre>
</blockquote>
<br>
Yes, and the question is how that can be handled, by the receiver of the pa=
cket, or if the sender needs to determine what address it uses and provide =
that in the HELLOs. If the first is possible that can simplify a lot.
<br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">Next is the issue that there is almost zero chance of gettin=
g a IP/UDP=0A=
encapsulation TRILL payload through the NAT if it results in IP fragmentati=
on,=0A=
as NATs don't do defragment and refragmented on the internal side, and an I=
P=0A=
fragment lacks UDP port and thus can't be matched to binding.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
So perhaps the recommendation should be to configure the port to use=0A=
TCP if there will be fragmentation.=0A=
</pre>
</blockquote>
<br>
Yes, I think that are likely the simplest solution for you. <br>
<br>
<blockquote type=3D"cite" cite=3D"mid:CAF4&#43;nEG-28weDot9R9Z4-05PX1tzBoKZ=
SOHu8BJY2GiRzOv0nA@mail.gmail.com">
<pre wrap=3D"">=0A=
</pre>
<blockquote type=3D"cite">
<pre wrap=3D"">Also if you like to run IP/ESP through a NAT, then you most =
likely need the=0A=
IP/UDP/ESP encapsulation (<a class=3D"moz-txt-link-freetext" href=3D"https:=
//tools.ietf.org/html/rfc3948">https://tools.ietf.org/html/rfc3948</a>). No=
te that this=0A=
will restrict the MTU even further and thus ensure that the 1470 requiremen=
t=0A=
cannot be fulfilled even without additional tunnels over an 1500 bytes MTU=
=0A=
Ethernet infrastructure.=0A=
=0A=
I would note that also firewalls likely have issues with IP fragments for t=
he=0A=
same reason, they require significant amount of state to be verified if the=
y=0A=
should be let through.=0A=
=0A=
In general I think you should create a configuration that has chance to wor=
k=0A=
through most middleboxes, but I think you should require static bindings. I=
=0A=
think that configuration is, and don't laugh now, but IP/UDP/ESP/TCP/TRILL,=
=0A=
otherwise you will not be able to have both security and reliable fragmenta=
tion=0A=
of TRILL packets.=0A=
</pre>
</blockquote>
<pre wrap=3D"">=0A=
OK. Thanks again for this review. It has pointed out a number of=0A=
problems and in thinking about those, I believe a couple of further=0A=
problems have come to mind that I mentioned above. We'll work on a=0A=
revised draft.=0A=
=0A=
=0A=
</pre>
</blockquote>
<pre class=3D"moz-signature" cols=3D"72">=0A=
Cheers =0A=
=0A=
Magnus Westerlund =0A=
=0A=
----------------------------------------------------------------------=0A=
Media Technologies, Ericsson Research=0A=
----------------------------------------------------------------------=0A=
Ericsson AB                 | Phone  &#43;46 10 7148287=0A=
Torshamnsgatan 23           | Mobile &#43;46 73 0949079=0A=
SE-164 80 Stockholm, Sweden | mailto: <a class=3D"moz-txt-link-abbreviated"=
 href=3D"mailto:magnus.westerlund@ericsson.com">magnus.westerlund@ericsson.=
com</a>=0A=
----------------------------------------------------------------------</pre=
>
</body>
</html>

--_000_52E4A8FC978E0241AE652516E24CAF0029AC2251ESESSMB103erics_--


From nobody Tue Jun 27 10:48:11 2017
Return-Path: <michelle.cotton@iana.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 D466E128990 for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 10:48:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.189
X-Spam-Level: 
X-Spam-Status: No, score=-4.189 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=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 KaZRnwdD1Rqt for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 10:48:07 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C595212009C for <ietf@ietf.org>; Tue, 27 Jun 2017 10:48:07 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Tue, 27 Jun 2017 10:48:05 -0700
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1178.000; Tue, 27 Jun 2017 10:48:05 -0700
From: Michelle Cotton <michelle.cotton@iana.org>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: IANA Services Focus Groups
Thread-Topic: IANA Services Focus Groups
Thread-Index: AQHS722Hf0WY0ywJV06LqW/NGFlwMw==
Date: Tue, 27 Jun 2017 17:48:04 +0000
Message-ID: <64A7D598-66D0-44B2-90D9-9EF6D32181BB@iana.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.23.0.170610
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha256; boundary="B_3581405284_182401540"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/9uWppqhAWI68aAchtMXTcqVxOCQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 17:48:10 -0000

--B_3581405284_182401540
Content-type: multipart/alternative;
	boundary="B_3581405284_993644457"


--B_3581405284_993644457
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Attention IETF Participants:

    =20

During the upcoming Prague IETF, we are looking for volunteers to meet with=
 the IANA Services team to discuss user experience with the use of protocol =
parameter registries. We are looking for a broad cross-section of users, fro=
m those who are heavily involved in the IETF and IANA Services processes, to=
 newcomers who have had limited experience.

=20

We would like to either meet one-on-one or in small groups to get different=
 perspectives.=C2=A0 Some of the topics we will cover include:

    -Submitting requests for protocol parameter registrations

    -Website/Registry usage and navigation

    -Feedback on I-D reviews

=C2=A0=C2=A0=C2=A0 -Expert review interactions

=20

If you are interested in meeting with us, please send an email to iana@iana=
.org with =E2=80=9CIETF-99 Focus Groups=E2=80=9D in the subject line.

Please include your contact information and what type of user you are of IA=
NA Services (template provided below).=C2=A0 We cannot guarantee meeting with ev=
eryone, but we will do our best to work around the meetings schedule to find=
 time.=C2=A0 Meetings will take place at the IANA Services Office Hours desk or =
other room TBD.=C2=A0 We will contact you regarding specific meeting day/times.=C2=
=A0 We will be scheduling meetings based on the responses/interest we receive.

=20

Please DO NOT reply to this email.

=20

Thank you and we look forward to seeing you in Prague.

=20

Michelle Cotton

Protocol Parameters Engagement Manager

IANA Services

ICANN/PTI

=20

Copy and paste template:=20

=20

Subject: IETF-99 Focus Groups

=20

Name:

Email:

=20

Focus area for feedback:

(describe areas here where you have experience and specific feedback if you=
 like. Examples: Do you submit registration requests? Do you review the prot=
ocol parameter registries? Are you a document author? Are you an IESG design=
ated Expert? Do you submit early allocation requests for your working group?=
 =C2=A0ETC.)

=20

Availability:=20

Monday-Thursday

When are you available?=C2=A0 What meeting timeslots might you be available to =
meet?

See agenda at: https://datatracker.ietf.org/meeting/99/agenda.html

=20

=20

=20

=20

=20

=20

=20

    =20

=20

=20


--B_3581405284_993644457
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta name=3DTitle c=
ontent=3D""><meta name=3DKeywords content=3D""><meta http-equiv=3DContent-Type conte=
nt=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft Word 1=
5 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Arial;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Courier New";
	panose-1:2 7 3 9 2 2 5 2 4 4;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"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:12.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.msoIns
	{mso-style-type:export-only;
	mso-style-name:"";
	text-decoration:underline;
	color:teal;}
.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:571545290;
	mso-list-type:hybrid;
	mso-list-template-ids:1575247432 893708304 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:27.0pt;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:DengXian;
	mso-bidi-font-family:Arial;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:63.0pt;
	text-indent:-.25in;
	font-family:"Courier New",serif;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:99.0pt;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:135.0pt;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:171.0pt;
	text-indent:-.25in;
	font-family:"Courier New",serif;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:207.0pt;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:243.0pt;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:279.0pt;
	text-indent:-.25in;
	font-family:"Courier New",serif;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:=EF=82=A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:315.0pt;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style></head><body bgcolor=3Dwhite lang=3DEN-US link=3D"#0563C1" vlink=3D"#954=
F72"><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'font-size:11.0p=
t'>Attention IETF Participants:<o:p></o:p></span></p><p class=3DMsoNormal><spa=
n style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></span><=
/p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>During the upcoming Pra=
gue IETF, we are looking for volunteers to meet with the IANA Services team =
to discuss user experience with the use of protocol parameter registries.&nb=
sp;We are looking for a broad cross-section of users, from those who are hea=
vily involved in the IETF and IANA Services processes, to newcomers who have=
 had limited experience.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt'>We would like to either meet one-on-one or in small gr=
oups to get different perspectives.=C2=A0 Some of the topics we will cover inclu=
de:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&=
nbsp;&nbsp;&nbsp;&nbsp;-Submitting requests for protocol parameter registrat=
ions<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>=
&nbsp;&nbsp;&nbsp;&nbsp;-Website/Registry usage and navigation<o:p></o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;&nbsp;&nbsp;=
&nbsp;-Feedback on I-D reviews<o:p></o:p></span></p><p class=3DMsoNormal><span=
 style=3D'font-size:11.0pt'>=C2=A0=C2=A0=C2=A0 -Expert review interactions<o:p></o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>If you are interes=
ted in meeting with us, please send an email to <a href=3D"mailto:iana@iana.or=
g">iana@iana.org</a> with =E2=80=9CIETF-99 Focus Groups=E2=80=9D in the subject line.<o:=
p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Please =
include your contact information and what type of user you are of IANA Servi=
ces (template provided below).=C2=A0 We cannot guarantee meeting with everyone, =
but we will do our best to work around the meetings schedule to find time.=C2=A0=
 Meetings will take place at the IANA Services Office Hours desk or other ro=
om TBD.=C2=A0 We will contact you regarding specific meeting day/times.=C2=A0 We wil=
l be scheduling meetings based on the responses/interest we receive.<o:p></o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Please DO =
NOT reply to this email.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span sty=
le=3D'font-size:11.0pt'>Thank you and we look forward to seeing you in Prague.=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p=
>&nbsp;</o:p></span></p><p class=3DMsoNormal><span lang=3Dfr style=3D'font-size:11=
.0pt'>Michelle Cotton<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3Dfr =
style=3D'font-size:11.0pt'>Protocol Parameters Engagement Manager<o:p></o:p></=
span></p><p class=3DMsoNormal><span lang=3Dfr style=3D'font-size:11.0pt'>IANA Serv=
ices<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3Dfr style=3D'font-size:=
11.0pt'>ICANN/PTI<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-=
size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:11.0pt'>Copy and paste template: <o:p></o:p></span></p><p class=3DMsoNo=
rmal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMso=
Normal><span style=3D'font-size:11.0pt'>Subject: IETF-99 Focus Groups<o:p></o:=
p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</=
o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Name:<o:p><=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Email:<o:p=
></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nb=
sp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>Focus =
area for feedback:<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font=
-size:11.0pt'>(describe areas here where you have experience and specific fe=
edback if you like. Examples: Do you submit registration requests? Do you re=
view the protocol parameter registries? Are you a document author? Are you a=
n IESG designated Expert? Do you submit early allocation requests for your w=
orking group? =C2=A0ETC.)<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'f=
ont-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D=
'font-size:11.0pt'>Availability: <o:p></o:p></span></p><p class=3DMsoNormal><s=
pan style=3D'font-size:11.0pt'>Monday-Thursday<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:11.0pt'>When are you available?=C2=A0 What meeti=
ng timeslots might you be available to meet?<o:p></o:p></span></p><p class=3DM=
soNormal><span style=3D'font-size:11.0pt'>See agenda at:</span> <span style=3D'f=
ont-size:11.0pt'><a href=3D"https://datatracker.ietf.org/meeting/99/agenda.htm=
l">https://datatracker.ietf.org/meeting/99/agenda.html</a><o:p></o:p></span>=
</p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></spa=
n></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></s=
pan></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o:p=
></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;</o=
:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'><o:p>&nbsp=
;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:11.0pt'>&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'=
font-size:11.0pt'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:11.0pt'><o:p>&nbsp;</o:p></span></p></div></body></html>

--B_3581405284_993644457--

--B_3581405284_182401540
Content-Type: application/pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIISBAYJKoZIhvcNAQcCoIIR9TCCEfECAQExDzANBglghkgBZQMEAgEFADALBgkqhkiG9w0B
BwGggg+5MIIFqDCCBJCgAwIBAgIQCuvDwxHaHKymSygUiz0IATANBgkqhkiG9w0BAQsFADBl
MQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGln
aWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBTSEEyIEFzc3VyZWQgSUQgQ0EwHhcNMTYx
MDAzMDAwMDAwWhcNMTkxMDAzMTIwMDAwWjCBxTELMAkGA1UEBhMCVVMxEzARBgNVBAgTCkNh
bGlmb3JuaWExFDASBgNVBAcTC0xvcyBBbmdlbGVzMTwwOgYDVQQKEzNJbnRlcm5ldCBDb3Jw
b3JhdGlvbiBmb3IgQXNzaWduZWQgTmFtZXMgYW5kIE51bWJlcnMxJDAiBgNVBAMTG01pY2hl
bGxlIENvdHRvbiBJQU5BIDNPY3QxNjEnMCUGCSqGSIb3DQEJARYYbWljaGVsbGUuY290dG9u
QGlhbmEub3JnMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA6V4aMB8RQMy4vQOd
nvINsoYARWq26DERE228XVCA7SxnxpHKRAgnpV4iBoL5rgjsiJy5utpRlbCZcV7PVaVp6yxM
ozNUSzmiSu+O04PyYWjvJRzSLda6W0hc8B766JDK3V8QVX+5Pnt9E2JxyYL6j5zTrD/kZGTB
XpaRNBF5DorhvPEwXNuRyWt5yD3m4vMwinCahC+5DB78PlxvbbEgTLenW8ZnSOunflX11Q8W
XkYBAHEWLSDEO8MY4t7b7FBTWoDA6arnmiJApfBm+tfJ9VPto6KX1YWWuUMrmg7PVF6jfiuW
ncwVZzed6VBW9Sp1oVKWP3GXraq0glyTutf5MQIDAQABo4IB8TCCAe0wHwYDVR0jBBgwFoAU
5wIjgABP2Ne8lAvZP3Q5STI8inkwHQYDVR0OBBYEFD4OJSm8pR0KSROJ2Te94XiGhEJAMAwG
A1UdEwEB/wQCMAAwIwYDVR0RBBwwGoEYbWljaGVsbGUuY290dG9uQGlhbmEub3JnMA4GA1Ud
DwEB/wQEAwIFoDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwQwYDVR0gBDwwOjA4
BgpghkgBhv1sBAECMCowKAYIKwYBBQUHAgEWHGh0dHBzOi8vd3d3LmRpZ2ljZXJ0LmNvbS9D
UFMwgYgGA1UdHwSBgDB+MD2gO6A5hjdodHRwOi8vY3JsMy5kaWdpY2VydC5jb20vRGlnaUNl
cnRTSEEyQXNzdXJlZElEQ0EtZzIuY3JsMD2gO6A5hjdodHRwOi8vY3JsNC5kaWdpY2VydC5j
b20vRGlnaUNlcnRTSEEyQXNzdXJlZElEQ0EtZzIuY3JsMHkGCCsGAQUFBwEBBG0wazAkBggr
BgEFBQcwAYYYaHR0cDovL29jc3AuZGlnaWNlcnQuY29tMEMGCCsGAQUFBzAChjdodHRwOi8v
Y2FjZXJ0cy5kaWdpY2VydC5jb20vRGlnaUNlcnRTSEEyQXNzdXJlZElEQ0EuY3J0MA0GCSqG
SIb3DQEBCwUAA4IBAQCFn08dbc9474OYmBeeFe4I08uzdP/Glg78Au1o7+IhufO+BN/fqn31
VhE7Q2aYCh28LF99PbdJ2IOBsz+BUGlrz7C0UvrHjmbXBTuR/gHez2Hmk6SOu0o4anLJqVFl
xMzQtpBQXWM0K8GlyqDlPtiWQDORtUsMOXnL2+smNqb5xoz1SyK30KEMMeq9ZndDuBpM1Gyh
7JdgiLypKnYfRc1c1INCWiDlvpTA+C60BZSv5e/k1GMW0USd7TZTzphQxKmLNRUXUxRjub3H
Yiby5y1hTnUyalL6HHbYVJX8bOgmaaOAjLvsJzX0rHRaMYlFbC4CgNlQNExJd4Xt7c39ghay
MIIGTjCCBTagAwIBAgIQBK55YGZmkBq5xX+mbFvczTANBgkqhkiG9w0BAQsFADBlMQswCQYD
VQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQgSW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQu
Y29tMSQwIgYDVQQDExtEaWdpQ2VydCBBc3N1cmVkIElEIFJvb3QgQ0EwHhcNMTMxMTA1MTIw
MDAwWhcNMjgxMTA1MTIwMDAwWjBlMQswCQYDVQQGEwJVUzEVMBMGA1UEChMMRGlnaUNlcnQg
SW5jMRkwFwYDVQQLExB3d3cuZGlnaWNlcnQuY29tMSQwIgYDVQQDExtEaWdpQ2VydCBTSEEy
IEFzc3VyZWQgSUQgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDc+BEjP2q1
78AneRstBYeiEEMx3w7UFRtPd6Qizj6McPC+B47dJyq8AR22LArK3WlYH0HtagUf2mN4WR4i
LCv4un7JNTtW8R98Qn4lsCMZxkU41z1E+SB8YK4csFoYBL6PO/ep8JSapgxjSbZBF1NAMr1P
5lB6UB8lRejxia/N/17/UPPwFxH/vcWJ9b1iudj7jkUEhW2ZzcVITf0mqwI2Reo2119q4hqC
QQrc6dn1kReOxiGtODwT5h5/ZpzVTdlG2vbPUqd9OyTDtMFRNcab69TvfuR7A+FEvXoLN+BP
y4KKDXEY5KbgiSwb87JzPMGwkp4Yfb2rfcV9CKEswp9zAgMBAAGjggL4MIIC9DASBgNVHRMB
Af8ECDAGAQH/AgEAMA4GA1UdDwEB/wQEAwIBhjA0BggrBgEFBQcBAQQoMCYwJAYIKwYBBQUH
MAGGGGh0dHA6Ly9vY3NwLmRpZ2ljZXJ0LmNvbTCBgQYDVR0fBHoweDA6oDigNoY0aHR0cDov
L2NybDQuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENBLmNybDA6oDigNoY0
aHR0cDovL2NybDMuZGlnaWNlcnQuY29tL0RpZ2lDZXJ0QXNzdXJlZElEUm9vdENBLmNybDAd
BgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwggGzBgNVHSAEggGqMIIBpjCCAaIGCmCG
SAGG/WwAAgQwggGSMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy5kaWdpY2VydC5jb20vQ1BT
MIIBZAYIKwYBBQUHAgIwggFWHoIBUgBBAG4AeQAgAHUAcwBlACAAbwBmACAAdABoAGkAcwAg
AEMAZQByAHQAaQBmAGkAYwBhAHQAZQAgAGMAbwBuAHMAdABpAHQAdQB0AGUAcwAgAGEAYwBj
AGUAcAB0AGEAbgBjAGUAIABvAGYAIAB0AGgAZQAgAEQAaQBnAGkAQwBlAHIAdAAgAEMAUAAv
AEMAUABTACAAYQBuAGQAIAB0AGgAZQAgAFIAZQBsAHkAaQBuAGcAIABQAGEAcgB0AHkAIABB
AGcAcgBlAGUAbQBlAG4AdAAgAHcAaABpAGMAaAAgAGwAaQBtAGkAdAAgAGwAaQBhAGIAaQBs
AGkAdAB5ACAAYQBuAGQAIABhAHIAZQAgAGkAbgBjAG8AcgBwAG8AcgBhAHQAZQBkACAAaABl
AHIAZQBpAG4AIABiAHkAIAByAGUAZgBlAHIAZQBuAGMAZQAuMB0GA1UdDgQWBBTnAiOAAE/Y
17yUC9k/dDlJMjyKeTAfBgNVHSMEGDAWgBRF66Kv9JLLgjEtUYunpyGd823IDzANBgkqhkiG
9w0BAQsFAAOCAQEATtSJJ7n9HYd3fg8oBZDxCi/JOz69k5yQxq/6kVGHMlRr6MrBcVFcmY61
+uBiGZmmB5p8Eyfb5QKihBLZFfYKRFfENI9tcx861qABPd7jguRFa7LrJf2AXh05kL5bQvbO
kWDj+aBWDEgQzjNoe82Tq/Bqy09YD7l7XRsEgZ6nIuJXSSfukpMIvmkIUwI6Ll3IGfRQgE4C
2bBdkbSTh/mWloFVQI5m7YLYuyhf7Uxh7QZYKBlTEUS8RyApsgRs2IlUmTt122d4LB6SeMZV
PVgSETJuvUMMTTTbe8ZC2+y+q5thTAaS447fISpQVwTAYKI11SSeZjcJSc/V+GWz4OJuwjCC
A7cwggKfoAMCAQICEAzn4OUX2Eb+j+Vg/BvwMDkwDQYJKoZIhvcNAQEFBQAwZTELMAkGA1UE
BhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IEluYzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNv
bTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJlZCBJRCBSb290IENBMB4XDTA2MTExMDAwMDAw
MFoXDTMxMTExMDAwMDAwMFowZTELMAkGA1UEBhMCVVMxFTATBgNVBAoTDERpZ2lDZXJ0IElu
YzEZMBcGA1UECxMQd3d3LmRpZ2ljZXJ0LmNvbTEkMCIGA1UEAxMbRGlnaUNlcnQgQXNzdXJl
ZCBJRCBSb290IENBMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEArQ4VzuRDgFyx
h/O3YPlxEqWu3CaUiKr0zvUgOShYYAz4gNqpFZUyYTy1sSiEiorcnwoMgxd6j5Csiud5U1wx
hCr2D5gyNnbM3t08qKLvavsh8lJh358g1x/isdn+GGTSEltf+VgYNbxHzaE2+Wt/1LA4PsEb
w4wz2dgvGP4oD7Ong9bDbkTAYTWWFv5ZnIt2bdfxoksNK/8LctqeYNCOkDXGeFWHIKHP5W0K
yEl8MZgzbCLph9AyWqK6E4IR7TkXnZk6cqHm+qTZ1Rcxda6FfSKuPwFGhvYoecix2uRXF8R+
HA6wtJKmVrO9spftqqfwt8WoP5UW0P+hlusIXxh3TwIDAQABo2MwYTAOBgNVHQ8BAf8EBAMC
AYYwDwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUReuir/SSy4IxLVGLp6chnfNtyA8wHwYD
VR0jBBgwFoAUReuir/SSy4IxLVGLp6chnfNtyA8wDQYJKoZIhvcNAQEFBQADggEBAKIOvN/i
7fDjcnN6ZJS/93Jm2DLkQnVirofr8tXZ3lazn8zOFCi5DZdgXBJMWOTTPYNJRViXNWkaqEfq
VsZ5qxLYZ4GE338JPJTmuCYsIL09syiJ91//IuKXhB/pZe+H4N/BZ0mzXeuyCSrrJu14vn0/
K/O3JjVtX4kBtklbnwEFm6s9JcHMtn/C8W+GxvpkaOuBLZTrQrf6jB7dYvG+UGe3bL3z8R9r
DDYHFn83fKlbbXrxEkZgg9cnBL5Lzpe+w2cqaBHfgOcMM2a/Ew0UbvN/H2MQHvqNGyVtbI+l
t2EBsdKjJqEQcZ2t4sP5w5lRtysHCM4u5lCyp/oKRS+i8PIxggIPMIICCwIBATB5MGUxCzAJ
BgNVBAYTAlVTMRUwEwYDVQQKEwxEaWdpQ2VydCBJbmMxGTAXBgNVBAsTEHd3dy5kaWdpY2Vy
dC5jb20xJDAiBgNVBAMTG0RpZ2lDZXJ0IFNIQTIgQXNzdXJlZCBJRCBDQQIQCuvDwxHaHKym
SygUiz0IATANBglghkgBZQMEAgEFAKBpMC8GCSqGSIb3DQEJBDEiBCACfNOnTzG13dIxeN0w
vSd04c7CLAmrjGGspgTnIwFz3DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0xNzA2MjcxNzQ4MDRaMA0GCSqGSIb3DQEBAQUABIIBAC5iqd878AJWB2GcOvfj
meLUxcmSZ0IRBfvqIT8EFX4wuL97r618/aeSnVZpnIO3hIEBphjieL3S4O1ItjVtH9E4qsDd
clDnymfBtm6K4iAU2LhD816SeH/fOqqHgtTBccSbHUx4RSkLKX4uiwBYv99Af4D5R/TD6s/k
wyCQfsyqdAJu2vJ4OQ1m1rGSTUyjHBhu6qiw8fVjsC6dnsf7ZTOu5jJdyd5RM3NmSY3izbUQ
ioTODqfO2o6FeAKImOZNl/xi0MnMko/lB4vvhRWW0NL3CGN6r2zEao5CGJr/xBfY3cgfD/GY
uLXCHO+DpYJML9Wp+Rdd1/Rev9YxJf1AMus=

--B_3581405284_182401540--


From nobody Tue Jun 27 10:57:07 2017
Return-Path: <Jeff.Hodges@kingsmountain.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 60596126C3D for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 10:57:06 -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_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lvZAh2p-zRXA for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 10:57:04 -0700 (PDT)
Received: from gproxy9.mail.unifiedlayer.com (gproxy9-pub.mail.unifiedlayer.com [69.89.20.122]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53863126C83 for <ietf@ietf.org>; Tue, 27 Jun 2017 10:57:04 -0700 (PDT)
Received: from cmgw2 (unknown [10.0.90.83]) by gproxy9.mail.unifiedlayer.com (Postfix) with ESMTP id A72B11E07F1 for <ietf@ietf.org>; Tue, 27 Jun 2017 11:57:02 -0600 (MDT)
Received: from box514.bluehost.com ([74.220.219.114]) by cmgw2 with  id dtwz1v00s2UhLwi01tx2fN; Tue, 27 Jun 2017 11:57:02 -0600
X-Authority-Analysis: v=2.2 cv=Z7GcJDZA c=1 sm=1 tr=0 a=9W6Fsu4pMcyimqnCr1W0/w==:117 a=9W6Fsu4pMcyimqnCr1W0/w==:17 a=IkcTkHD0fZMA:10 a=LWSFodeU3zMA:10 a=0c0aGqK81aWcM6tr4AcA:9 a=QEXdDO2ut3YA:10
Received: from [173.224.162.69] (port=39781 helo=[10.225.80.38]) by box514.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1dPujT-000Q5t-FV; Tue, 27 Jun 2017 11:56:59 -0600
To: IAB Chair <iab-chair@iab.org>
From: =JeffH <Jeff.Hodges@KingsMountain.com>
Subject: Re: Call for Participation, Workshop on Internet naming systems
Cc: ietf@ietf.org
Message-ID: <011b97dd-9017-cac4-1f9b-05b5869393fb@KingsMountain.com>
Date: Tue, 27 Jun 2017 10:56:54 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box514.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - KingsMountain.com
X-BWhitelist: no
X-Source-IP: 173.224.162.69
X-Exim-ID: 1dPujT-000Q5t-FV
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-Source-Sender: ([10.225.80.38]) [173.224.162.69]:39781
X-Source-Auth: jeff.hodges+kingsmountain.com
X-Email-Count: 2
X-Source-Cap: a2luZ3Ntb3U7a2luZ3Ntb3U7Ym94NTE0LmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/zrq90swWSTHAJbe1YeCLqh28LA4>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 17:57:06 -0000

 > [...]
 >
 > There are now multiple challenges to maintaining that commonality of
 > understanding.
 >
 >   Some naming systems wish to use URIs to identify both a service and
 >   the method of resolution used to map the name to a serving node.
 >   Because there is no common facility for varying the resolution
 >   method in the URI structure, those naming systems must either mint
 >   new URI schemes for each resolution service or infer the resolution
 >   method from a reserved name or pattern. Both methods are currently
 >   difficult and costly, and the effort thus scales poorly.
 >   [...]

Might y'all have pointers to said "naming systems", e.g., specs, 
websites, etc?

thx,

=JeffH






From nobody Tue Jun 27 13:22:24 2017
Return-Path: <linda.dunbar@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 6E74D126B71; Tue, 27 Jun 2017 13:22:18 -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 kab8yM_smbd0; Tue, 27 Jun 2017 13:22:16 -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 1AE1D1200ED; Tue, 27 Jun 2017 13:22:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DPY04760; Tue, 27 Jun 2017 20:22:13 +0000 (GMT)
Received: from SJCEML703-CHM.china.huawei.com (10.208.112.39) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 27 Jun 2017 21:22:11 +0100
Received: from SJCEML702-CHM.china.huawei.com ([169.254.4.142]) by SJCEML703-CHM.china.huawei.com ([169.254.5.136]) with mapi id 14.03.0301.000;  Tue, 27 Jun 2017 13:22:05 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Peter Saint-Andre - Filament <peter@filament.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "precis@ietf.org" <precis@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-precis-7613bis@ietf.org" <draft-ietf-precis-7613bis@ietf.org>
Subject: RE: [precis] Gen-art last call review of draft-ietf-precis-7613bis-07
Thread-Topic: [precis] Gen-art last call review of draft-ietf-precis-7613bis-07
Thread-Index: AdLuzwlSicte5jFwS92cRaxDldpIjAAQlv4AAAPukoAAGGnvQA==
Date: Tue, 27 Jun 2017 20:22:05 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F6593D9AA6@SJCEML702-CHM.china.huawei.com>
References: <4A95BA014132FF49AE685FAB4B9F17F6593D94F9@SJCEML702-CHM.china.huawei.com> <3feb4084-d038-9253-fc48-e739d846102f@filament.com> <f070d840-792d-8447-4e2a-f919019adff1@filament.com>
In-Reply-To: <f070d840-792d-8447-4e2a-f919019adff1@filament.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.192.11.138]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5952BE75.0116, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.4.142, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: befc2f0ab0b180b3a3ba228e0f21ff5f
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PQDqQk9mDyctReGcmY9TDWlkvjM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 27 Jun 2017 20:22:18 -0000

Peter,=20

Thank you very much for the explanation and the revised wording. Your new w=
ording is much clearer and help people to understand why to postpone the ch=
ecking.=20

Thank you.=20

Linda Dunbar

-----Original Message-----
From: Peter Saint-Andre - Filament [mailto:peter@filament.com]=20
Sent: Monday, June 26, 2017 8:41 PM
To: Peter Saint-Andre - Filament <peter@filament.com>; Linda Dunbar <linda.=
dunbar@huawei.com>; gen-art@ietf.org
Cc: precis@ietf.org; ietf@ietf.org; draft-ietf-precis-7613bis@ietf.org
Subject: Re: [precis] Gen-art last call review of draft-ietf-precis-7613bis=
-07

On 6/26/17 5:48 PM, Peter Saint-Andre - Filament wrote:
> Hi Linda,
>=20
> Thanks for your review. Comments inline.
>=20
> On 6/26/17 4:53 PM, Linda Dunbar wrote:
>> =20
>> Reviewer: Linda Dunbar
>> Review result: Ready
>> =20
>> I am the assigned Gen-ART reviewer for this draft. The General Area=20
>> Review Team (Gen-ART) reviews all IETF documents being processed by=20
>> the IESG for the IETF Chair.  Please treat these comments just like=20
>> any other last call comments.
>> =20
>> For more information, please see the FAQ at
>> =20
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>> =20
>> Document: draft-ietf-precis-7613bis
>> Reviewer: Linda Dunbar
>> Review Date: 2017-06-25
>> IETF LC End Date: 2017-06-27
>> IESG Telechat date: 2017-07-06
>> =20
>> Summary:
>> The document is written very clear. Even for a person who is not=20
>> familiar with the App area, I can follow through the description. The=20
>> document is ready for publication as standard track document Major issue=
s:
>> =20
>> One Minor issue:
>> =20
>> Page 6 last paragraph has:
>> /SASL mechanisms SHOULD delay any case////mapping to the last=20
>> possible moment, such as when doing a lookup////by username,=20
>> performing username comparisons, or generating a////cryptographic=20
>> salt from a username (if the last possible moment////happens on the=20
>> server, then decisions about case mapping can be a////matter of=20
>> deployment policy). In keeping with [RFC4422], SASL////mechanisms are=20
>> not to apply this or any other profile to////authorization=20
>> identifiers, only to authentication identifiers./
>> =20
>> What does "last possible moment" mean? When I read it, I thought it=20
>> meant wait until you got all the characters. But the next sentence=20
>> mentions "..happens on the server". How is the "server" related to=20
>> the entity that check the user name & password?
>=20
> Many authentication decisions happen on an application server to which=20
> a user-oriented client connects (think of an email client connecting=20
> to an email server). By "last possible moment" we're referring to=20
> processing within the application server or an authentication module=20
> thereof - for instance, instead of performing case mapping on first=20
> receiving data from the client (thus implying that the case=20
> information is lost through most of the processing stages), it's=20
> better to lose that information only at the very end. Do you feel it=20
> would it help to add a more detailed description of the reasoning here?

Here is a proposed adjustment to the text:

OLD

      SASL mechanisms SHOULD delay any case
      mapping to the last possible moment, such as when doing a lookup
      by username...

NEW

      Because case mapping results in
      information loss, in order to retain that information for as long
      as possible during processing, implementations SHOULD delay any
      case mapping to the last possible moment, such as when doing a
      lookup by username...

Peter


From nobody Tue Jun 27 13:30:05 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 8E2D0126B71; Tue, 27 Jun 2017 13:29:57 -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: mpls@ietf.org, draft-ietf-mpls-rfc3107bis.all@ietf.org, ietf@ietf.org
Subject: Rtgdir last call review of draft-ietf-mpls-rfc3107bis-02
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149859539754.31085.2059230421371020521@ietfa.amsl.com>
Date: Tue, 27 Jun 2017 13:29:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/X7foEktrhUx7Ah4VDvg_fJ8qWjA>
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, 27 Jun 2017 20:29:58 -0000

Reviewer: Stewart Bryant
Review result: Ready

Firstly my apologies for the lateness of this review.

This is a very well written draft, and can proceed as is.

Useful clarity might be added to Section 4 (dataplane) by the inclusion of some
figures. I say this as someone that finds it easier to take in information in
that format, so that is a personal preference comment, the text is correct and
technically sufficient.

There is an intriguing piece of text in the dataplane section "While this may
be useful in certain scenarios, it may provide unintended results in other
scenarios." which I think might be usefully expanded to give at least one
example of a use, and an unintended consequence.

In the introduction it says: "In [RFC3107], this feature was controlled by a
BGP Capability Code that has never been implemented, and is now essentially
obsolete." which left me wondering whether there was the intention to formally
deprecate the feature through the RFC system.


From nobody Tue Jun 27 18:07: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 2A637129B2B; Tue, 27 Jun 2017 18:07:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=LBsEtERT; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=USNuUPJJ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jSJeV-lCyF8P; Tue, 27 Jun 2017 18:07:11 -0700 (PDT)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 254D9129B22; Tue, 27 Jun 2017 18:07:11 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 7D98120905; Tue, 27 Jun 2017 21:07:10 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute3.internal (MEProxy); Tue, 27 Jun 2017 21:07:10 -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=GZnmsEEMZYlFDGw8+d wDcl54agz1EjZDIhsQRiC47oY=; b=LBsEtERTh/NjVFhinBBMz/gNsExgz6PxYh LgU4oCp5FxeU4S1U4RvXH7ma3U2duNcqw54xqZ5jyhK3JtceA1jCeRtPuViYpO0k NcdIn+ZdqCdzmDLQ9LaTYSgWLxJ4mhh0MR0LEdj7aQfXsHxb+TJrTbCush2JxtJv jfGJnl3Z89LHk2Rq/OamUkWK+EJcSDdW2L2DAfUHPbapLurv7rLS/8Knmg6ACFfE b9qKRrnHRMpqdS57Iax0/wtqohZf8rNTC6klnPfHw53u0e1MJK5TxG62T9lWPp/L KhfXNV7A1m8zPSFEUGWPqXV81FuaSrCvxGfM8nZDIAxa4+mzhquA==
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=GZnmsEEMZYlFDGw8+dwDcl54agz1EjZDIhsQRiC47oY=; b=USNuUPJJ ge2q6yiifUl7odG6MmI4YVaySDnKqxboT7XyAnhYDVmfcQAgkBrScUuSo0UYrY7A NJvfOE5WBK/ptG7SbwEReFK9YIxSOoBbJT+MLKNNlLHF5zzTUwvUk1Zn5xtAo+8x y5a2E2FrBHEftBC5EF4WmNtcthEAYVdgaYsiMhf/IleA7o3yZOFV3d5axgYnydqr MkHrPkZvZwLeYA4CgiK5VBIS+9OKF4r2ICRdXf0zSUP4bTXoyYsIbMgJP5gCmjxX lUmWyE3DK0glsoZOCbyR5O19It9raPWyOzYbmD2I3WS00p598vr7ZJnjKekuKWJ2 hfx/hO+qdV+Mhw==
X-ME-Sender: <xms:PgFTWR-_P2NSt-XG9KZcyIG-gJIlkzkHtXrCIhC_p7dHi30FPRivtQ>
X-Sasl-enc: bVxfCTp5ORDOVHaSn63extw0Z8P8Zq1oEsoJmj4Bm54f 1498612029
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 338DF7E766; Tue, 27 Jun 2017 21:07:07 -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-ietf-httpbis-early-hints-03.txt> (An HTTP Status  Code for Indicating Hints) to Experimental RFC
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20170627052928.GA5568@1wt.eu>
Date: Wed, 28 Jun 2017 11:07:07 +1000
Cc: ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>, httpbis-chairs@ietf.org, draft-ietf-httpbis-early-hints@ietf.org, ietf-http-wg@w3.org, Alexey Melnikov <alexey.melnikov@isode.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <114853C3-36EC-426B-83D7-5101EB2A523D@mnot.net>
References: <149806437201.15854.12299810594896460001.idtracker@ietfa.amsl.com> <20170627052928.GA5568@1wt.eu>
To: Willy Tarreau <w@1wt.eu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/pvWLZKGDxyLz_eRMXgpjs1uuTrk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 01:07:13 -0000

Fair enough, but I wouldn't place requirements around this; just note it =
as something that might happen.


> On 27 Jun 2017, at 3:29 pm, Willy Tarreau <w@1wt.eu> wrote:
>=20
> On Wed, Jun 21, 2017 at 09:59:32AM -0700, The IESG wrote:
>>=20
>> The IESG has received a request from the Hypertext Transfer Protocol =
WG
>> (httpbis) to consider the following document: - 'An HTTP Status Code =
for
>> Indicating Hints'
>>  <draft-ietf-httpbis-early-hints-03.txt> as Experimental RFC
>=20
> I've just noticed that it's never mentionned that a client should be
> prepared to receive multiple 103 responses as any informational =
response
> (or at least I did not notice).
>=20
> I think that indicating that multiple responses MAY be sent with =
complementary
> and/or possibly overlapping links, it may help grasp the overall =
principle
> and the relation between these informational responses and the final =
one.
>=20
> The case I'm having in mind is the same as described in the PR =
comment, a
> server-side gateway could speculatively send a 103 with a few =
site-specific
> links while the server provides another 103 with some =
resource-specific
> links.
>=20
> Willy

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


From nobody Tue Jun 27 18:16:11 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 D4E941273E2 for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 18:16:09 -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 g3jl2quvV-UK for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 18:16:07 -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 2E5A6127286 for <ietf@ietf.org>; Tue, 27 Jun 2017 18:16:06 -0700 (PDT)
X-AuditID: 1209190c-2d3ff700000076d7-ef-59530355727d
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 9B.4B.30423.55303595; Tue, 27 Jun 2017 21:16:05 -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 v5S1G4g3029285; Tue, 27 Jun 2017 21:16:05 -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 v5S1G1FQ014660 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 27 Jun 2017 21:16:03 -0400
Date: Tue, 27 Jun 2017 20:16:00 -0500
From: Benjamin Kaduk <kaduk@mit.edu>
To: Gmail <stewart.bryant@gmail.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, IETF Discussion <ietf@ietf.org>
Subject: Re: Which is the right "RFC2119" Boilerplate?
Message-ID: <20170628011600.GG68391@kduck.kaduk.org>
References: <a69ab951-ec0a-0c29-57aa-013f969db7be@gmail.com> <83ce36c5-3bfd-6d78-4ede-f8df3a9aa60c@gmx.de> <20170627032926.GD68391@kduck.kaduk.org> <BB6A4223-8443-46ED-8F43-5A18EA2074CE@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <BB6A4223-8443-46ED-8F43-5A18EA2074CE@gmail.com>
User-Agent: Mutt/1.7.1 (2016-10-04)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpgleLIzCtJLcpLzFFi42IRYrdT0Q1lDo40uLrSwuLZxvksFpsfvmG1 OPUg0YHZY+esu+weHz7GeSxZ8pMpgDmKyyYlNSezLLVI3y6BK2NryyXmgr0cFatXb2JuYLzI 1sXIySEhYCJx891bIJuLQ0hgMZPEhsNNzBDORkaJJY3foJyrTBKHNs9gBWlhEVCV+Hx3G5jN JqAi0dB9mRnEFgGyNz+awQhiMwt4S7zd3cIEYgsLmEmsPbwarJ4XaN21Tfeghp5ilHg7cxU7 REJQ4uTMJywQzVoSN/69BGrmALKlJZb/4wAJcwrYSrQ8XAxWIiqgLPH38D2WCYwCs5B0z0LS PQuhewEj8ypG2ZTcKt3cxMyc4tRk3eLkxLy81CJdQ73czBK91JTSTYygwOWU5NnBeOaN1yFG AQ5GJR5ejcigSCHWxLLiytxDjJIcTEqivHu/AIX4kvJTKjMSizPii0pzUosPMUpwMCuJ8LJs BsrxpiRWVqUW5cOkpDlYlMR5JTQaI4QE0hNLUrNTUwtSi2CyMhwcShK8h5iCI4UEi1LTUyvS MnNKENJMHJwgw3mAhvtdBRleXJCYW5yZDpE/xajLce7q7i9MQix5+XmpUuK8hYxAgwRAijJK 8+DmgBKORPb+mleM4kBvCfNmgKzjASYruEmvgJYwgXwwLwBkSUkiQkqqgfGQE8emU8vZNDxW tnuw5xdO0iw43sG2doJXX/2kZ1e1Xkqoz0kQfv5O/snBlNU/WM27PEUmPP57qX3tU8/UlQ6X O+vazQWTvr++I7Z0uueT2xr8rqINVltaEq7uYDlRbvLls/jB1QtvpO6VOz3pFLfOW7d+lvJD t+aI1e6Y0zpDct/1I2cqrG4qsRRnJBpqMRcVJwIAAJgh/xMDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/t5Ay7u2YCJkyhD5SD4v5awu9xLQ>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 01:16:10 -0000

On Tue, Jun 27, 2017 at 09:17:15AM +0100, Gmail wrote:
> 
> 
> Sent from my iPad
> 
> > On 27 Jun 2017, at 04:29, Benjamin Kaduk <kaduk@mit.edu> wrote:
> > 
> > And perhaps Stewart should look at the Errata for RFC 2119, if he has not already.
> 
> It has been my long standing concern that for all practical purposes no one look at errata! Indeed I doubt that many will until the RFC Editor appends the verified errata to RFCs, or takes some similar approach with them.

Part of why I always use the https://tools.ietf.org/html/rfcNNNN URLs is that
they do indicate when errata exist.

> In this case I looked at the errata and could not see anything, what did I miss?
> 

Hmm, there are more errata here than I remembered; sorry for making you do
guesswork.  I was thinking of EID 499, which adds "NOT RECOMMENDED" to
the list in the boilerplate, and is the first difference that idnits was
complaining about, if I was reading its output correctly.

> At a different level maybe we need an xml tag that  includes the 2119 boilerplate?

Seems useful.

-Ben


From nobody Tue Jun 27 20:00:16 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 C3EC9129AD7 for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 20:00:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level: 
X-Spam-Status: No, score=-1.699 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] 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 7gHJg3YGtwJi for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 20:00:13 -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 10E8E124B0A for <ietf@ietf.org>; Tue, 27 Jun 2017 20:00:13 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id 32so39891282qtv.1 for <ietf@ietf.org>; Tue, 27 Jun 2017 20:00:12 -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=GAuJx6SNGvxf50If/Fvdp9KGaYDJWPYsGjFiUKZuGtg=; b=vQTm5RjlbUCS6qj8HeOkiukwu0+TNB1hnewWeDaoef9FXKjHMbKlM0U6WZs7YMXmMe 0d2caz0lfkafYtI7mJDxuB5Bm/2aTD+Xr/8vFR9bdZoHWIQjGidrIhAVN/8cBeD2K2yY IRyYVjE2MqgOJ4u7vrVToCGj0DfaiYurmcbW8evG4+s4I1/33e3IBQ0Z5mSXSIouTuDX BUBac7PJQRDDphklCdhgVBy7g9240Zz+TmG6clkrCXjOsdwL0FyBSmEkihkai+6hqXXq ru43eM+uz6+7Mw0dqVmYvgfGtNV3rfwCGacjg/4T3ZPV+rNvDQcx8f8UY7B91LMyj3il IYQg==
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=GAuJx6SNGvxf50If/Fvdp9KGaYDJWPYsGjFiUKZuGtg=; b=f1MB1xLfysZ5mX+AXGJButD9cP/wuV3XSl+ubA6J82n9vsZuvfN/5KHSCW6Qq+QCFj UqdknSBo/aTDBFw7hzZ5hHnY2q1ReWWsyPlkD2N+uvqz6CIxYxD+bNUHhbxF9dIhTW3S Bqu68znEFi4p04KgQGU06mvg5SmRu+sXYjCqthYwEj1aCmBWclByXmRnG+X4H+lVKx3L f3bDaWwvU7lvhoCRpylWkc+ALNAHJXYaqJE+i+y40PFVrTMkiRNaPWUZ0AOpvP9NUMDv UMkEApXtBZP86dMb0ntgfvyUk6ti4kkRu5WTgEeWXaZ5pAw0ctRscmpp1IPc/960CgIh 5eyA==
X-Gm-Message-State: AKS2vOyuagZsiPEirZwEQ8X0t/Ej8hJOyxXD/D+Mjl3dEeNw1sjLPC7f /cBIhHQgMgV8GyTyMMoZZYE2Cl6v2A==
X-Received: by 10.237.43.134 with SMTP id e6mr10183856qtd.131.1498618812234; Tue, 27 Jun 2017 20:00:12 -0700 (PDT)
MIME-Version: 1.0
Sender: hallam@gmail.com
Received: by 10.140.102.79 with HTTP; Tue, 27 Jun 2017 20:00:11 -0700 (PDT)
In-Reply-To: <011b97dd-9017-cac4-1f9b-05b5869393fb@KingsMountain.com>
References: <011b97dd-9017-cac4-1f9b-05b5869393fb@KingsMountain.com>
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Tue, 27 Jun 2017 23:00:11 -0400
X-Google-Sender-Auth: qz6hJVPN1KGotCJyGq6yTRZVPd0
Message-ID: <CAMm+LwjrMYKEZ4mtwZoELBiD7zDtSB7sZifmOs4opAg4djYkUA@mail.gmail.com>
Subject: Re: Call for Participation, Workshop on Internet naming systems
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>
Cc: IAB Chair <iab-chair@iab.org>, IETF Discussion Mailing List <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="001a114ecf00f503000552fc61a6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/frnLB5JioU5JsWmuCpb6Cdd_V34>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 03:00:15 -0000

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

I am also rather unclear about what is being asked about.

Rather a lot of buzzwords that do not identify distinct concepts for me.

On Tue, Jun 27, 2017 at 1:56 PM, =JeffH <Jeff.Hodges@kingsmountain.com>
wrote:

> > [...]
> >
> > There are now multiple challenges to maintaining that commonality of
> > understanding.
> >
> >   Some naming systems wish to use URIs to identify both a service and
> >   the method of resolution used to map the name to a serving node.
> >   Because there is no common facility for varying the resolution
> >   method in the URI structure, those naming systems must either mint
> >   new URI schemes for each resolution service or infer the resolution
> >   method from a reserved name or pattern. Both methods are currently
> >   difficult and costly, and the effort thus scales poorly.
> >   [...]
>
> Might y'all have pointers to said "naming systems", e.g., specs, websites,
> etc?
>
> thx,
>
> =JeffH
>
>
>
>
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-size:small">I a=
m also rather unclear about what is being asked about.</div><div class=3D"g=
mail_default" style=3D"font-size:small"><br></div><div class=3D"gmail_defau=
lt" style=3D"font-size:small">Rather a lot of buzzwords that do not identif=
y distinct concepts for me.</div></div><div class=3D"gmail_extra"><br><div =
class=3D"gmail_quote">On Tue, Jun 27, 2017 at 1:56 PM, =3DJeffH <span dir=
=3D"ltr">&lt;<a href=3D"mailto:Jeff.Hodges@kingsmountain.com" target=3D"_bl=
ank">Jeff.Hodges@kingsmountain.com</a>&gt;</span> wrote:<br><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex">&gt; [...]<span class=3D""><br>
&gt;<br>
&gt; There are now multiple challenges to maintaining that commonality of<b=
r>
&gt; understanding.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0Some naming systems wish to use URIs to identify both a se=
rvice and<br>
&gt;=C2=A0 =C2=A0the method of resolution used to map the name to a serving=
 node.<br>
&gt;=C2=A0 =C2=A0Because there is no common facility for varying the resolu=
tion<br>
&gt;=C2=A0 =C2=A0method in the URI structure, those naming systems must eit=
her mint<br>
&gt;=C2=A0 =C2=A0new URI schemes for each resolution service or infer the r=
esolution<br>
&gt;=C2=A0 =C2=A0method from a reserved name or pattern. Both methods are c=
urrently<br>
&gt;=C2=A0 =C2=A0difficult and costly, and the effort thus scales poorly.<b=
r></span>
&gt;=C2=A0 =C2=A0[...]<br>
<br>
Might y&#39;all have pointers to said &quot;naming systems&quot;, e.g., spe=
cs, websites, etc?<br>
<br>
thx,<br>
<br>
=3DJeffH<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div>

--001a114ecf00f503000552fc61a6--


From nobody Tue Jun 27 23:50:48 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 8890412EA52 for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 23:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 IJk_nGAiTBfm for <ietf@ietfa.amsl.com>; Tue, 27 Jun 2017 23:50:44 -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 303EE129B8B for <ietf@ietf.org>; Tue, 27 Jun 2017 23:50:43 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id 32so42339948qtv.1 for <ietf@ietf.org>; Tue, 27 Jun 2017 23:50:43 -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=PrkCP8KMwisPr3Uzo1s7BevgHcief+zzCLbdaGqZbmk=; b=dsheE470dSLkjic/opJHoUdKpHoTt7jjir3Rca7tCdGhruHMO331v6VFHUzaK0u6ra bByTHg2lzY0loPvY8iZw1cLQ0nKUM3un04H08FKhWNySawo2hpj1gmka3eARO8s2SJ8z /L42p6jBnkiZsp/rXsKFre2y5YkZm0u3bc2BFgV3Qz6psDWO+SRWYgG8CrJ4hD2Vk8Ra I1O20UbuM/KdMXFCtO8e1zC+QIP35Tx2laivyTf6X+P4frtcjzkP+qAYewY2ngnVXV54 6ro7CNFuAubmyut41nfARK4p1AYHwei+XAn7QNOncm0gNITOK0kTp9wn/Rr+HSWawP0/ ba9w==
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=PrkCP8KMwisPr3Uzo1s7BevgHcief+zzCLbdaGqZbmk=; b=lzKScfp5Qb4GGJttqtLiaBe+ClSty5qBCRGmeniSXVl1q9N4jACnTJAuCqaBagFbOp Yz5VQKPjOePBE4j5+QaY0V5gmechiHoobj4M0SFsyg4PnDcn/v3B1u4W38BS06cURNCo usM52CpnDnOW1nQrH2KrJYuQ6EH6Ud/ZntEAbRufG59LzLunb7C+M97m9eorJe9CGSH1 vvqE7cSTyLXIZ1UF+g5RCrRLwJTk7iafQJCivEG5OHjti0OHOBwIB5rhH9uu5oLCY86e tsB4U9tv1W54G/8U8gDWO+HSa21m8idRvuNIaocSxU89Y1XRkAZhRkP53Nfbxtn3Nrka SVlw==
X-Gm-Message-State: AKS2vOxvbG94a2K6gw+PUOjaES5CsSxFBRnSmvvbZKTI6qUMP9/uDxc1 Q/Ms4r6/6+Q8DuHt79Xmrf53VDy/gA==
X-Received: by 10.237.44.7 with SMTP id f7mr12093897qtd.52.1498632641990; Tue, 27 Jun 2017 23:50:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.200.34.9 with HTTP; Tue, 27 Jun 2017 23:50:11 -0700 (PDT)
In-Reply-To: <011b97dd-9017-cac4-1f9b-05b5869393fb@KingsMountain.com>
References: <011b97dd-9017-cac4-1f9b-05b5869393fb@KingsMountain.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 28 Jun 2017 08:50:11 +0200
Message-ID: <CA+9kkMABE6E6hMvOL3t9tfM6ptDEf7D2uP=2ZLEcF2ic9Z50MA@mail.gmail.com>
Subject: Re: Call for Participation, Workshop on Internet naming systems
To: "=JeffH" <Jeff.Hodges@kingsmountain.com>,  Internet Architecture Board <iab@iab.org>
Cc: IETF <ietf@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c05df9046548a0552ff9aa0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/G3s4QxMcTuWT9GoiaIbn0F8-eIs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 06:50:47 -0000

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

Hi Jeff,

On Tue, Jun 27, 2017 at 7:56 PM, =JeffH <Jeff.Hodges@kingsmountain.com>
wrote:

> > [...]
> >
> > There are now multiple challenges to maintaining that commonality of
> > understanding.
> >
> >   Some naming systems wish to use URIs to identify both a service and
> >   the method of resolution used to map the name to a serving node.
> >   Because there is no common facility for varying the resolution
> >   method in the URI structure, those naming systems must either mint
> >   new URI schemes for each resolution service or infer the resolution
> >   method from a reserved name or pattern. Both methods are currently
> >   difficult and costly, and the effort thus scales poorly.
> >   [...]
>

Might y'all have pointers to said "naming systems", e.g., specs, websites,
> etc?
>
>
The most recent example in the IETF came up in the reservation of .onion.
As you probably recall, the system envisioned there uses the TOR system for
node resolution, rather than the DNS, but the proponents wanted to use the
names with standard URI schemes.  Reserving that name was a very long
process in which a lot of discussion was needed, and it has kicked off
significant follow on work that suggests the model does not scale well.

One other option discussed with them was moving away from standard URI
schemes and minting URI schemes like https-tor://tor-node/, instead.  That
would work, because the specification of the scheme could describe the
resolution required.  But they would need a new scheme for every
application protocol wanting to use the resolution (so email, xmpp, etc.
would each need to be created and deployed).  Getting deployment of those
schemes was seen to be even harder.

While I hope this example helps illustrate the problem, I want to be clear
that this example isn't the focus of the workshop. The workshop wants to
look at the collection of issues named in the CFP to see if there are
common root causes and potential solutions.

regards,

Ted


> thx,
>
> =JeffH
>
>
>
>
>
>

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

<div dir=3D"ltr">Hi Jeff,<br><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Tue, Jun 27, 2017 at 7:56 PM, =3DJeffH <span dir=3D"ltr">&lt=
;<a href=3D"mailto:Jeff.Hodges@kingsmountain.com" target=3D"_blank">Jeff.Ho=
dges@kingsmountain.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">&gt; [...]<span class=3D"gmail-"><br>
&gt;<br>
&gt; There are now multiple challenges to maintaining that commonality of<b=
r>
&gt; understanding.<br>
&gt;<br>
&gt;=C2=A0 =C2=A0Some naming systems wish to use URIs to identify both a se=
rvice and<br>
&gt;=C2=A0 =C2=A0the method of resolution used to map the name to a serving=
 node.<br>
&gt;=C2=A0 =C2=A0Because there is no common facility for varying the resolu=
tion<br>
&gt;=C2=A0 =C2=A0method in the URI structure, those naming systems must eit=
her mint<br>
&gt;=C2=A0 =C2=A0new URI schemes for each resolution service or infer the r=
esolution<br>
&gt;=C2=A0 =C2=A0method from a reserved name or pattern. Both methods are c=
urrently<br>
&gt;=C2=A0 =C2=A0difficult and costly, and the effort thus scales poorly.<b=
r></span>
&gt;=C2=A0 =C2=A0[...]<br>
=C2=A0</blockquote><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">
Might y&#39;all have pointers to said &quot;naming systems&quot;, e.g., spe=
cs, websites, etc?<br>
<br></blockquote><div><br><div>The most recent example in the IETF came up =
in the reservation of=20
.onion.=C2=A0 As you probably recall, the system envisioned there uses the =
TOR system for node=20
resolution, rather than the DNS, but the proponents wanted to use the names=
 with standard URI schemes.=C2=A0 Reserving that name was a very long=20
process in which a lot of discussion was needed, and it has kicked off sign=
ificant follow on work that suggests the=20
model does not scale well.=C2=A0 <br><br>One other option discussed with th=
em was moving away from standard URI schemes and minting URI=20
schemes like https-tor://tor-node/, instead.=C2=A0 That would work, because=
 the specification of the scheme could describe the resolution required.=C2=
=A0 But they would need a new scheme for
 every application protocol wanting to use the resolution (so email, xmpp, =
etc.=20
would each need to be created and deployed).=C2=A0 Getting deployment of=20
those schemes was seen to be even harder.<br><br></div><div>While I hope th=
is example helps illustrate the problem, I want to be clear that this examp=
le isn&#39;t the focus of the workshop. The workshop wants to look at the c=
ollection of issues named in the CFP to see if there are common root causes=
 and potential solutions.<br><br></div><div>regards,<br><br></div>Ted<br>=
=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
thx,<br>
<br>
=3DJeffH<br>
<br>
<br>
<br>
<br>
<br>
</blockquote></div><br></div></div>

--94eb2c05df9046548a0552ff9aa0--


From nobody Wed Jun 28 00:01:59 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 26311129C04 for <ietf@ietfa.amsl.com>; Wed, 28 Jun 2017 00:01:58 -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, FREEMAIL_FROM=0.001, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c6oswWMJ13Os for <ietf@ietfa.amsl.com>; Wed, 28 Jun 2017 00:01:55 -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 06EF0126DD9 for <ietf@ietf.org>; Wed, 28 Jun 2017 00:01:54 -0700 (PDT)
Received: from [192.168.178.20] ([93.217.69.185]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0M8JyQ-1dcoZi2h0s-00w0Dw; Wed, 28 Jun 2017 09:01:48 +0200
Subject: Re: Which is the right "RFC2119" Boilerplate?
To: Benjamin Kaduk <kaduk@mit.edu>, Gmail <stewart.bryant@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
References: <a69ab951-ec0a-0c29-57aa-013f969db7be@gmail.com> <83ce36c5-3bfd-6d78-4ede-f8df3a9aa60c@gmx.de> <20170627032926.GD68391@kduck.kaduk.org> <BB6A4223-8443-46ED-8F43-5A18EA2074CE@gmail.com> <20170628011600.GG68391@kduck.kaduk.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <b4b74ebb-06f8-edb5-7280-74e83d9b9a9f@gmx.de>
Date: Wed, 28 Jun 2017 09:01:46 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <20170628011600.GG68391@kduck.kaduk.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:qHqQlOZFt/wY4aB3VIdmo1VtXgLTIB5tJ0M8ESJHwJCLJ+pTWjG xH5o6+4w25NyUxnsjij8e1lnXTZ3blIgln3bW/SvlUebQbSFPEQo9akdetOo3+Vuf6TkkIs 8+d2+RXP7aVZZ+Cs8A0MBPmRuVoQv3AeWIObGVPJZSWT5gAELvO1HZ3GS7jNEKQT5fu696Y oxYQsWJnaHWRW2VRYMEhg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:62uZGHezq5M=:vekkxvQCGT3C4w1HPJ64Cm ob1zXHtLd53+Rh1zdqEIA7oDFGJbZxh5KEBFRDX/OXB/iU3KFyabmN2VGxuA1T85sFAgYls64 LQI7MH9yH6iDdisVpivlFpS9b9ZdiSW3oH/3wLBXXUmK4LPJqYbFxTOeSx5gKHK+S6sN5nOps AmS36/+7rj2kUGb0w4/jc08MNl6AM3nU6xT7Zpn55HG9cVR9nlaaXkgqwnDCwF2cr0FShOlkE IYWcIcZPZFqbZpX6+Rb1dKVJWr1IFxvPqPYrCLby1pF4jKF4dQ/7iGNV9EXhMD1vQqklNArBY 9LDzmtGjVX/VFbJ4yxebR3SQmvIhE9h4OVkbzoND4uIuLreGCrLR4t5EXAZfMmbid6+QybYCV 6E0a9JVq3AVomiWuGcj3q5Dz1F3vzeIcNBcAF0b0qOZDlmtF9+RWivZijRDQNarVcmsowE2mq ibf/e4dcgndgWEuV2KMjQ9XTkfeL6+QnxiZ3yLDstTJZTw2XwzEjyzcgLZSjP0vdhrEokfvxX W+yhaj/SZFpQ2oFuMw37tX6bG7VYrAys8lFBl6D/Q3ynccY1HjWFQrmsQrwLznUfHFNbJy7HR Q8cxDpUHgtOczitfoaKMIfZ8jSju/QOpcwrg2BEBHs3QjZdBhtSD1hF291g01m8YC0vFQifDR foJhj0tVT5LyEpgrSv6dJl18zEBvWjwPx/s60ytXICjRNTc5a2y/T4OBBnge0vAINz+Qkao0g nN3je8EnSdNzRgDHJCK4YeWPIJJcHVNsfbO4mdy+g9bkNb+tkKJyWeo1EIPRUy8yfUW2ULbKc cx0bp5Q
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/-3it2AdYacBCihmZHAQVyXP0Rjg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 07:01:58 -0000

On 2017-06-28 03:16, Benjamin Kaduk wrote:
> On Tue, Jun 27, 2017 at 09:17:15AM +0100, Gmail wrote:
>>
>>
>> Sent from my iPad
>>
>>> On 27 Jun 2017, at 04:29, Benjamin Kaduk <kaduk@mit.edu> wrote:
>>>
>>> And perhaps Stewart should look at the Errata for RFC 2119, if he has not already.
>>
>> It has been my long standing concern that for all practical purposes no one look at errata! Indeed I doubt that many will until the RFC Editor appends the verified errata to RFCs, or takes some similar approach with them.
> 
> Part of why I always use the https://tools.ietf.org/html/rfcNNNN URLs is that
> they do indicate when errata exist.
> ...

If the RFC Editor provided the errata in a machine readable format, we 
could optionally inline them in the future RFC HTML format.

P.o.c.: <https://www.greenbytes.de/tech/webdav/rfc7230.html#http.uri>

Best regards, Julian


From nobody Wed Jun 28 01:12:56 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 7096012EB78 for <ietf@ietfa.amsl.com>; Wed, 28 Jun 2017 01:12:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, 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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kaSxC6bZF8MG for <ietf@ietfa.amsl.com>; Wed, 28 Jun 2017 01:12:53 -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 9E048128C83 for <ietf@ietf.org>; Wed, 28 Jun 2017 01:12:52 -0700 (PDT)
Received: from [192.168.1.34] ([217.91.35.233]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0LfTC1-1e5mRt3QQT-00p0nW; Wed, 28 Jun 2017 10:12:48 +0200
Subject: Re: Which is the right "RFC2119" Boilerplate?
To: Barry Leiba <barryleiba@computer.org>, Stewart Bryant <stewart.bryant@gmail.com>
Cc: IETF Discussion <ietf@ietf.org>
References: <a69ab951-ec0a-0c29-57aa-013f969db7be@gmail.com> <CAC4RtVB73xfvw_dn-Sg3agd0DwVrboj-E2kqfPRwpSe6no0VOw@mail.gmail.com>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <20be5cb1-bead-0698-3b7f-393f425a3631@gmx.de>
Date: Wed, 28 Jun 2017 10:12:47 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CAC4RtVB73xfvw_dn-Sg3agd0DwVrboj-E2kqfPRwpSe6no0VOw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:87IN2hYmDa6I9jSMFUsDi/LBsZqW8H3EJ+3xNaBPDpEEoSewL0n lBIexboUwy8EIrRDdcRGEttcgSNbu+EnRW75noLQeb8n4+696q7dJs+THv1LXvlL8isBh9Q WgpOoabHZKX/En4pP62nwVlPAan+a1SW6p1BaR0/a5cs+WxRTj9Ex63ZEh4v90KVrTf1Yyo G6AsgczebA17ylOzXdlgA==
X-UI-Out-Filterresults: notjunk:1;V01:K0:Bvz2AiCiGGY=:CZ7HL8KdWqSe8ejyxkICdM Qgw7fWTrNZxu9ze02lMPAkFJFIf6EzBDFMGqR2qZOCdXMUC96TdWUfKEIecrOssThNLYLaymf DVDj4y1UVCERkX+ivRxiTMYb/S1blAW29cAQmE6ttSD0kER5qW7xzAEb3cOG7kGdEsVknidMZ lfag2MAfPnOYnNOHuvMe3CeB0PWshc33gB7yjrbsAmfXwmcI9mxMz78/ttQROTfqADlJh4CrY iNPh83JSLuKQ+GxBzZYw3u9PGZXA3umjG6s0Sm7s25I33YFxBfX1rZzR5ZkZGHQdQbnywmud1 SBG+hxMkPlDXXVAwY/21djP1Pz13pf+yY0O73+EVLi4rpgZlFVB+gyp/vmQjohsDOoZA+oQn2 s6Z8J+FTC0qDFZMxAF5MopTOmZmzoL+PBSgqXBFi+b80gof4vpTKp0hpXkdbLJgWbWMHZAk91 94TeZw1PWLETX9nG1GQhh1EvCaY0SvDOQzYi7AOg1u8P+XrfuaZBSuzqDt9+Dt2tDZaNjpVws zfAvF49liMRq9miL8Ew/H+b5d2J2qFW6DvtEEwfG8onlK7MjNNY9K3BiMJ8LYHqywKO0+V4Z1 wVWl200/TQaGcTT8R4eCyxTsGXgttU8oZ7HAu/n1bU65EnT6ap3PbDDIhK4UMnOZfXfkait9s p1NnWk1/gPTe6CfSsZJICVGOZ6hFqoyMW9C5tN15FoBxVfKQU+ZVxmeVl7QMfY7FvKJo2qGFX Rxlo9YfwXJYJwZJDZ0z8vEaYXc51krhweBOk7yBhYfaRrKlU/aVpi+qT3DKdpWNkny+mX2VFi h3L0vug
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/BE3iSA6aVPiKm7uLwRF8n6S_U0s>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 08:12:54 -0000

On 2017-06-27 10:45, Barry Leiba wrote:
> Henrik is aware that idnits needs to be updated, and is working on
> that.  He's been in contact with me about it.  (I actually thought
> he'd already put the fix up, but I guess not.)
> 
> Barry

Is accepting non-ASCII characters on the TODO list as well?

Best regards, Julian


From nobody Wed Jun 28 05:53:01 2017
Return-Path: <erosen@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 597F9129ABE; Wed, 28 Jun 2017 05:52:51 -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 fn_6gWoT3_dE; Wed, 28 Jun 2017 05:52:49 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0132.outbound.protection.outlook.com [104.47.34.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CA52120454; Wed, 28 Jun 2017 05:52:45 -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=YRnfFcrC5K5WUOa1pz8fD2kwFitT/bNm7tVP3Ud8VEk=; b=PwdCeN15s7QUi4LWxk2wmmVVIKjAFxrZ5ZGXP9J64AIbGtR70CjgsPVAtTX5Qeqr/c5Yhy82lFo+Md6Gih7g7Yxa6UwB7C6EOFYLeAlX561yaUS0lxuer5AY4XwzC4gEc7OevGYtSkmdFBi1NLqRsjMPU7gE3/dOGlhpuJsqgdI=
Authentication-Results: juniper.net; dkim=none (message not signed) header.d=none;juniper.net; dmarc=none action=none header.from=juniper.net;
Received: from [172.29.39.106] (66.129.241.11) by BY2PR05MB2184.namprd05.prod.outlook.com (10.166.112.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1220.5; Wed, 28 Jun 2017 12:52:43 +0000
Subject: Re: Rtgdir last call review of draft-ietf-mpls-rfc3107bis-02
To: Stewart Bryant <stewart@g3ysx.org.uk>, rtg-dir@ietf.org
Cc: mpls@ietf.org, draft-ietf-mpls-rfc3107bis.all@ietf.org, ietf@ietf.org
References: <149859539754.31085.2059230421371020521@ietfa.amsl.com>
From: Eric C Rosen <erosen@juniper.net>
Message-ID: <3c405108-c18f-8f1b-b9e7-25d08157e1ee@juniper.net>
Date: Wed, 28 Jun 2017 08:52:31 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <149859539754.31085.2059230421371020521@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-Originating-IP: [66.129.241.11]
X-ClientProxiedBy: BN6PR11CA0041.namprd11.prod.outlook.com (10.173.25.27) To BY2PR05MB2184.namprd05.prod.outlook.com (10.166.112.12)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 28868ac0-2de5-4e94-3ace-08d4be249262
X-MS-Office365-Filtering-HT: Tenant
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(48565401081)(201703131423075)(201703031133081)(300000504095)(300135200095)(300000505095)(300135600095)(300000506094)(300135500095); SRVR:BY2PR05MB2184; 
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2184; 3:XYpjH7oJhLvzlkqzixeXyzVnYO1AnTRstwENco8PMBj3NgV2g5TdbJMMdVwdc6avh11KD0nGCsgVxX409IpD6gNM1/rh2PowujYqCKGrOSlR4G9a1AjphuofQT9xWskq/y37prlVMsolfqCFmIOdtC2spVKtpe3DTCsu3V2+B9O0BEqO5rLAiwhVsnc6uSUaAzNyk+qdqh+0U2x7p8kT2W4I2QBHmQjPAAx5KY7ElMYE1Qyjq8BbfK4ZnNOUPF8IfPYt/IOkos0jz0Pe4/EMzKvxQt9dDbWDZRXIoKz0fgIeqEAYZ1uBubfMABWPanqmjgPIKgudIWYifJDeTfm9BXZuxj0O0ehv0rBkAtjG3fUTJ6f0qrPyiAGZzHZz0Gzph04xRpunujrxlWL1sSUqQgKqZ/PcpGVqJqyePhd/NPTvOxthwHe/wKHFBwGyOYmoyXBr3QLrEwD2Bd3dLB5+b0AMpCut2yMpTMaMaDKvgcUWFNMOmnU7zdkpmjR01Z5N94os8H0nr8AiCaqnt8HV1NMtnvODgdMFWpxsMpRtpHiaxAGaBCrgoOHMxx/JXMeGHCjWbjCnLvNrdF4DuoZC5WXGCzMV3v81LNEaGxIIKuYLIFQ1A0R5EKu0LWE/AJlkM052wJnDmJiw3iYiNfBGaqPHlb2REU/ZPyVQS0ESgsa/+/YnRv7eVDUms7WRMMlPIpapqR48rHuFtC9VtLccadxbmBBc54cjYdJ3Q5xxffznZxtXL6831w+OrBu05sPz5jQiR5KtbVXyr++tHhe9lg==
X-MS-TrafficTypeDiagnostic: BY2PR05MB2184:
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2184; 25:ZcTAYkt59I+/eqYI2hDcfoCNYkQKl0NsWRQ8rlLbDeHunnrrb/FWPAsB/OrZj5eczjR25sLdU8fVcqCjwhMnQMITeGv2hlENFeZ1ZHoiDhDWYYEw/yf7udfXMSnOCC0+uyTDLCllux77gJfvcmemWz+1ily/JFq9cboJDOaCTWkUCqp0Po/aZT/8otKLI2PYWHoEHI7PRsE0iNYH1bHnAy+IgjtHw1JNK7HRKQvmuCKlAnjn1VWcs2jvXs22aYxgirDvMFuQfJtUIf35KamNWB0OUv/DX9wvmUZIhuONwnCVXVvYNObillUFDRudFLwXVtJ9u0OEaxQ3KhDd892g3MGrDOkXmvcvUEP29qD2xdkOogOF3cSRRSujjch8J4Tb0vcmUv/5OiBxxPAGd7OAAAsxLhtWa91QK7xX8fYJ88NCZXAOdrLNckyGouVq9/BZF2K77rpsYFAyT9C5t6D3mlGg/wyHY6dtykNihbVEVG6aWIaK1xJ6Ad3zqrMrqLXvFtll1VUYQOhL4zr/XlW8n5uXdhBMv5IwCxnIO9kVGnGjpU46QxW8Whrgq+iFJKttY7fEVrsM5xbdJII7irSIMBKdgQ20J6Y2e3uc/WLbefbIaypIyvTcYIn5Z6pCy50hNy4sXKxee3FSlJ36iFo6xmlk0JAsDnCf4itGJT2F4vtp8SAaTxea+hqzeVFjHvwOQc57K0lAFp1HI0BOrnzcxBA8aqfMVhNHVMnQqGlolj2lJ4upaOHrF52cSVduHHIaI7Vl3/cxpBcIRZVtJ6zZzeW2GsajlOiQrvJ/l977MStAyyu7z8floFNGSvVkPg1AYMXPJnPLLx6sngQsTFZ158CCTxeJidRzevHpn8W0/rdqNqfHdvGJPQmNWxO05pjUYOESLSWORkB9Ogiz1iC3UxH7FKDIdsOJ+1ibaZdijl0=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2184; 31:+u0u8UKMkwPn7mPv6hVjXKDtJKk8Z2m1ZjjthDVFfgrgypYODzwoxlH8dlUTTNlHM/QiGIgXvQ3a7Xh4+H5hxn0TnCa/yR4RuVzff2IdKtLidq04iIl9pwwJmJvGccZMF2vXnn+VZ12JEYaV0YgntQQmab94zZ+4JIcN7VZ5+f1e5WvWdKHHF1LE1BISyqaq7nm+vtLfj8GgCmKddqIaNNuZdTpbgofsi1zzeHw56Jpwtn2OhUelBnfDwq8TFgy1cCT/cr9vXHJIyGMvHwb5yCTiSYttIr5baeVaoS8ZcFMrJEY4M+0Xpz7xb9CIy2gNnyIlqivL2D/3ASLVowYaDAIBtGbvmG+GLgb0oZ76UwE5hwxEC6DL3HWwafoocMYKFsVOcKcSSwRKXTiQFlcJefKRrejT/DKIQcE+b1D0gH4Ihj0PSV5K25sASyMczOEV+sxRbOgotQI+0s72wqKu0s1bcAZrqo9rQEzcHSE4IGbtA3xTJANatwVUPeGpVjTfGvW0pvHB+mtE9SdGXaJASyO3S4ZUfdl1ztwc3YRhsaXH8Pnl/QUb5dJ1xEGKHClPU3+JvWGf30y7dDhryMMgrmwhUatyygb+ED3Pd8rCbeTueB1MXoIj4qppvzAGqFdgs0yA9/65zql6B+5dxBv067iLhLKi1LVbVqto+5vx9gc=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2184; 20:BsupNiXUQk+wOUE/hYKN+bAIde/aMvwNQ84plrNSKYKka2q7149pEcEMOPxL43cru01Db6haIISOpfa3iKHQxLiTpTUcqcqjFeMlhFMfEDxmkYvo2FPBmN1ktVrqtxQa9vDdWUSDqIf+aYRNBO/vuI1Q0rmR5wViZq1lkb5S5dWzQ+EEIIiYUNgiSPJeiJJq+wnges15GPTqxIhPaq8M7zFPdQU2AvEoNcV/dAmAnkRAhAM8ZCGuznq+0/o/ZBxB01zgxzwglj8e5ZPI6d9qE6CYzzHLCGk91uE+HBkJ4nKolQHU+uzgpMuhd6wIrhbWzYKj8UfzTPl586LWkfjgG+icnFRDsojkYxNhUdSLRoI1V0uYrNm5PuvjuGAcQQdIOpKYZz/6Xu/8g2iWEuNEUiYjmFOXgEMSvVYcwKtLlOqacy3/ZPE8iWZ7Ocl/33KAf7S3xWzU52B8SVnTHzQAnya0OPR7a+L3WEt58zQme2yq3aYgSHSHNsRU8mxEC42ZKo9V7Gad3H2OMAL4lAZJJ7XpNei25iSstKAjWVeadY8FcgFLfR/7NLgQAT+4FnsrX6iv9Hgo3hYw8gcqmsmIiFeZwARt+rTiayydZvqL7sc=
X-Microsoft-Antispam-PRVS: <BY2PR05MB2184581E7ABB9DCF840AC850D4DD0@BY2PR05MB2184.namprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(278178393323532)(236129657087228);
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(100000703101)(100105400095)(93006095)(93001095)(6055026)(6041248)(20161123560025)(20161123564025)(20161123558100)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123555025)(6072148)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:BY2PR05MB2184; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:BY2PR05MB2184; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA1TUIyMTg0OzQ6Q1VNbTJ2NUxYMjBtL05XVmNTTFZiV0lqKzBN?= =?utf-8?B?Z1lOWEhMWitIL2ttUmE4SW5OZ0JXQ3NoVG8vWDJEZExBM0l6TXJGKzdqQXdP?= =?utf-8?B?ZlFlRG1FQmV3bFFYeEpGNFZEamhwRVZkc0xkd0Y1TTFhbHQrR2JjMFdiaWxL?= =?utf-8?B?eEtneVlUUDZtanVzM29iTWJrcWx5dEhvejIzaUZkOEYxcE0rSnlORlQ4K0I2?= =?utf-8?B?SnVCRy90ZU1OaVM3c1B2NzRnd3NqUHlINGdEY21zYXhwR0wyN0JLTUZibDdm?= =?utf-8?B?NXIxWnNaOEU2YVY5MHZnMDFHR3FLclFVTXZUUmtYZlZ6OHNjMzE2M2NLcXRz?= =?utf-8?B?Y2tmbm9ORE13VndsNmJTbVV6bGtXTkh4a0NmR1Q3NmJWSXdhWHhYTFR4dTBl?= =?utf-8?B?NVRwT2pjcitRU3JjYWhZWkp1NW4xNS9LZDVYcXMvN05WM0xUOGpXZHRwTWht?= =?utf-8?B?YXF1YzZidk1GaVZhME9aSlZHV1hFY0hkdU11Z0NudjhiWnBoVUh0QW54OVFl?= =?utf-8?B?RnRpeTRCUjVGMW1hc2Joa3dSN1VTRkYyL09yRDJKWk1UdHMvSTV5WXJCTEg2?= =?utf-8?B?YkdHdHZaeXE4d1hZME94UEp0ZHFhNUhQQjV3emU2K01jNkVOVGp2UDNVUnkx?= =?utf-8?B?b3pVb01jOGtoUW11bmFXQUpVQnBSTEMxekV4NVhXWklWeFk4S285UnF2OS8z?= =?utf-8?B?SytTRWxheXNUTFcwQVdYYWNUc2s4ZmlOVU10c2xqNUo4d09EcXgrS3JYRk5h?= =?utf-8?B?bFZMQUtSUWpGelZWTDJEVmxLb2RFNkhUL3RCdmVMRnVRWUhpVUlrTlB0c0Fu?= =?utf-8?B?a09SdkdMV2gzY1FUWGVjT3RQODE3cGgvSHJoRFFBeUhWeVV0akY5Rjhwdlhq?= =?utf-8?B?WTlnRHRaajcvVC9rdng4em9SYnNyNTJNek5YSWliTXlqTG4yMzlrcUZ3SW9Q?= =?utf-8?B?M0I5Qmw4NW42bm5GSU5uU1d4UnQxKy84QVUzY1JrbnB1czdFTG9TalBQYWRr?= =?utf-8?B?eU12VDFpeEdjNnBPYi8yK1NaZmxwNGVWeXUxWEpTUXpmYklxYjNHeDVYdG5E?= =?utf-8?B?aGFIY1Q5NzMyZDRwcjF6NWkwZU4veHoycGxDeENsaG9JTnR4bHJhQ3VlZ3dT?= =?utf-8?B?WkhPYjFCVHFyQkMwTWE5Wmw5bzJVNjcyem1zYkhReUFnWTV6MzZ2eDh4RHcw?= =?utf-8?B?YTFpQjJBdmJITjc5NjdDOEtvUVpEZlptSFlyZnJmbGh2M3lvZXJ4UmpSZy9s?= =?utf-8?B?ckU1Y2pZenZhMndTOG9scXN0SUx3VVBVakJXbUtsaDM2emFrdnppVk01V2lQ?= =?utf-8?B?YS9BSnhjK0w4WHN5ODlJZGNneXFTYTNsWmtnYVc5TzE1YmNFNkFndnZGUllX?= =?utf-8?B?SkJ3Yk9vNGd5UUNqN3RHdTVPeTUwSEd1VW1nRWNTSkhwOWNyT0RIWnpHMTJX?= =?utf-8?B?YjJ1bmhqK25zUXMzZVMxTytXS1FocFZNSlFXWjVWRmo1ak03TzVnY1A0MEFE?= =?utf-8?B?ODRxdmdkQnB4d0lQaDlvbXJRMTZjdmJ0bno2OEUzQkdibUxrckRnWWc3T3do?= =?utf-8?B?dzhpVkdBY0pOVk0rbTV5K0ZpWjFNV0FadHgwNUJGNjdwVzFqWUU5R05RbitV?= =?utf-8?B?bkF4UzZRa0t0M2VoV0VybmsrM2RPbC9OUW4vMy9xMUNRR3B6UmVITkpDWUky?= =?utf-8?Q?G6ufrYdcHU4Jd5bi8=3D?=
X-Forefront-PRVS: 03524FBD26
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(979002)(6049001)(6009001)(39860400002)(39840400002)(39400400002)(39850400002)(39410400002)(39450400003)(377454003)(24454002)(230700001)(3846002)(53546010)(23676002)(36756003)(6116002)(7736002)(4326008)(229853002)(305945005)(189998001)(65826007)(6486002)(478600001)(8676002)(230783001)(81156014)(90366009)(4001350100001)(77096006)(81166006)(25786009)(3260700006)(5660300001)(50466002)(33646002)(64126003)(65806001)(31696002)(83506001)(47776003)(65956001)(86362001)(66066001)(2906002)(6246003)(38730400002)(110136004)(31686004)(6666003)(2950100002)(42186005)(54356999)(76176999)(50986999)(53936002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR05MB2184; H:[172.29.39.106]; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA1TUIyMTg0OzIzOnIrNW0yNjNzVnlDajNkWWh3Y2tTMGVZWkVr?= =?utf-8?B?K0U5SmhLRmU5L1JIc3ZNa2xtT1Jza0VjUmFXeSt6enVjWlh2US9jMTIyWXVX?= =?utf-8?B?Uk9ZSXNBVmdjMXdlTGl1Wi9qeFVwanZyOEwwK2JNdFlDQ2dxWXBnb1NNSGV3?= =?utf-8?B?TEd5bVdqbzJjNGRlY0ZhY3RzNVFvQXlTYm1KZU1OWk9PUThGZUVGSmJITlI2?= =?utf-8?B?U01Uc29XK2c0RTg0ZW8xMUZOS1N4eHpacjlrWnN6bjFBZXVyTCs3T1Z3NVQ2?= =?utf-8?B?bnZQYjkyWnlzUEJlN2pWTlc3WDZCdkoyNks5TCs1ZU1KWTF0SWJ0QVcyOTJH?= =?utf-8?B?d1IzVUlvZUsvS3E1RUhicE9oaTB6S010cE1kVnpaMENBR2FOdHRoY1REcFdL?= =?utf-8?B?eXgvc2syMVFFSGF4UUkvT3d5ZDQ3a0hDd3ljbFhwQVU4M0lFbTdNbUROcmlB?= =?utf-8?B?N2djVHBMZDFPN3ZJU2RHbExnNmw5dHdjOXljYi9YSFlxUGVGajR3Vk9XZEpI?= =?utf-8?B?dER1N3hseXRVbitvYXN1amE5a3dXeU1aSFMwTUNlVWhNdU9Md2RjSWtLTUdT?= =?utf-8?B?cUdOSHRsYnF4bGxPTmNUSjJ1ZTdNbHRySytmTm8wZlIwbVEvd0Y5RlhuWGtS?= =?utf-8?B?SkJRckpYWExmNnVVSUxYa3dXL3c1ZVF1WUpkLzc5VUNZLzRVeFNQUEduWks4?= =?utf-8?B?RTVQMDFHRFV2ajNoWGN6V1F4T3plNTN2SDBsdk9lVFF6YXdtL1hCVHFkMitZ?= =?utf-8?B?YVM2ekhQU3VDZE83L0NTY1FvRGwrV0EwU0U1dml6bkYyQkdvcWpCV0tGWFhZ?= =?utf-8?B?UzdmUldQUmYwa0JjdVFxNmtINmN4ZEo3KzdtZW1DSGVhODJtejN1cGpvTlpT?= =?utf-8?B?R01FK2pzeVdzR2lFUkRxbkdIQ1FDM2Fob01yVnZBS0JCRjE0NzAzOHQ5Z29a?= =?utf-8?B?QWE5L2kvRHdzVW5XUVV4clpvZHFLSHJlQnRGRHRxcVp6UTdZcG0wK0tOSWYv?= =?utf-8?B?M3l3RGJEa0Qvak12UWZvUzA1bVZHNWtxSlFodmdLSE1oaWppSENVa3NiaFJ0?= =?utf-8?B?WC9meGZEU0MrcTJyZlRTak1OeDJ3L3BiR1EwSHE3aGV2ZnBMOVBjM2kvRTBy?= =?utf-8?B?bnl0ZEdkYkxFdk5NYUxkTE12MksvbjJCbGFGc3hBOGdYa1c4UC84anhEazY1?= =?utf-8?B?b2UyWmpCWmZEaEN4VnVmcUtNVTZKdW9XbGZITWJudlpSODhsR2taR2MrVEVq?= =?utf-8?B?SE9vRERBcDJNRFFSOVNDRGh2VGJob29vZ0xmaDFjK01Uakt6RG5wcGVOdWlJ?= =?utf-8?B?Y0NHaEptNmFRazlnT3lVZ0U1bTc1VmYrL0hMbDBsbU5UcnhqQ2JyZFYrOU0x?= =?utf-8?B?UXQ1YzdCUVYvemZ6K01mRzN2RDR1WTFXOEpUV0cyeG0rRGd5TWhIeFRkd1B2?= =?utf-8?B?ckJhTjIxM1dwbmMyRXRIcXNtWitFbzBabllEczBiZ3JwY2F0dXVHQmR1NzZY?= =?utf-8?B?MENPSlhIYVpXL2hrOVhyVEs2SGd5U3dOV2lsU1VLV0gvVHl3UE42SVVnKzR6?= =?utf-8?B?c2doMVpSUlF5UXFiYlVxRVpSTWJ5U3A5QXpYdmRUYzMxdmd1K0JCM2tnNXht?= =?utf-8?B?UHIySE85N2l4NUtuNFZ1VU1STjlWRlI2R3pPOFZ0Tk8zK3BFd1lGT2Ircm1x?= =?utf-8?B?MlNsRlJVQi83cU5qclM1R3NDbDdrekhlWVRucktXVWxVNWNjY0ZmK0YyQnVz?= =?utf-8?B?VUkyWk9HVUhNc0JXNFJLemVKWTl0TGkvOGhnUUtxS3dRK2FwWjVvckNqT2JR?= =?utf-8?B?ZmVKRU94a1J0UDlaYUZtZk1iWE52NWZHMkRrSVNPQ3FwaTFFQ1JGTzZDbWVw?= =?utf-8?B?ZVVFRklteFJReGxobHdtWFZmeGk3d2lORHVzeXZvdm95WWVMcjQ3T1REbjF0?= =?utf-8?B?QWlodGdEVTZVdFBTTklpVnYxVFJQaWI1WGlzQ1RMUngxUWtHSjZLdHpkUmhT?= =?utf-8?B?eis2cjFFU3FPUWhZdi9SLzRuVlROc2lxVzhkdVBkZm9oR05xTnNZZGU2bEZB?= =?utf-8?Q?vMUE=3D?=
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtCWTJQUjA1TUIyMTg0OzY6ZklxYndXRTZYa0xuaTdDb0FyejBaMlBRVGty?= =?utf-8?B?NXNoODRFMUd0YW84VzZLSTF0cGpVWVdPY0VNN3preWRDS3dWTEcvRkh0dlc5?= =?utf-8?B?c2NGeGtRVU1ONm9rNVRQSUZiSWNPVlZiWTFLR1NkL1V6UHVzVWZWNHlxTmlK?= =?utf-8?B?Q2VMcHF5NXpmK05WUlpia1VEQjRvTmwrQno2UXQzakJIT0UyUVhUS0YvMXNF?= =?utf-8?B?MVFWZlNIRHh0MTRIVGRaeFlMTUpMdFRvL0ZkallJOUZnMXBQdytnZzhueXl6?= =?utf-8?B?RE5VZFUreGkzTDVEaGtNVmlLY1Nra2p3WjdGZ2xUSDN5ZmRid0ZrSUlRcUpt?= =?utf-8?B?REZxUkYyZUMrQnVxUC84NVN3S0xlYzI5WmdySUpYTnlkYmZKemh5YUhuVG1J?= =?utf-8?B?aDhtZlF0bERtWVlRdm1laVV6akRkeFpHN3hVRXEyS3dMTDVxbWh1WG9OZ0pj?= =?utf-8?B?VllveWxteXBFZm95MVZBQnh2SGZtWGh6ZmYyTS94cU1CbVNwT3J3eUxaOWR4?= =?utf-8?B?b1ZraFBUTTlyOVE2VHM2eEVOcTNaUnk0b3JZUUV3VlZHb3J6TlR3QUpsY2ht?= =?utf-8?B?VFJxYyttbmJoVmFYdlladmMxTGFTOXpDZDdxam1VRTV3SkoybFJFT29KK0Fv?= =?utf-8?B?M2VZd2lNWGkxS2tUbEozUGt6VVlRWURZWXpJbWU0RVRqbEczSGNMRTliUG9P?= =?utf-8?B?dEtWRzNhVFFtMjJLSGYyajdQczUzZ0pacENoTk1tdjVVTHNoNGN3NmY0ekNl?= =?utf-8?B?a2hqUzUvSTVYOFBKYVpYaWtHb2tERFltQTAwdUZtYzZaa0p4c3NZenpVdzFu?= =?utf-8?B?UmFEVExvcGh1cHQrb05RdmE3MGZRT0hDSnd2RFkzQ2xWdlltVy9jY0NIQ1RL?= =?utf-8?B?T3pOZktTdEM5M04rOVNnSTFqT294RStKakdXWlJiS214L2tMbEo5R09SdlJF?= =?utf-8?B?eFA2UHFsUy8vZzFqY0daV1RqdmVTSjhPbjVZY0RNMWVVeVZHQTl5dFUrQTNo?= =?utf-8?B?Qk9KZXJFc2RQRVZxSG4xTGtWS3QxVDg5d0dHaTBFZjJUTzhKUnNwU1doMlhV?= =?utf-8?B?RGVINnQzOVFER2xqQmVVcDRFd1BraExVbHQwMWFvTjE1REVNREthMkZucWFn?= =?utf-8?B?d0RFVWZJeUo0TzQxQkNLbW5ONEFIcUF5Rk1vNk5sNzlpUkZ1TmNOVFNjZEVC?= =?utf-8?B?Z2NWckpiUDJxYzE2aGJUTmNqMnBtbFR0ek1LazlIOWk5eDVZTnJOaXplekhl?= =?utf-8?B?TFZ2NmpSMjBaQlJPeUtTTkZlNytFS0M0TFNFR25tZmlXUUdnR2FCRGk3VWt6?= =?utf-8?B?bVBsN2c1eksrT1RnNnNlaWlQc3I2ZEhrOHdZVzFoNWRDbTJJdVg2T2lkcWUz?= =?utf-8?Q?zJzCClg?=
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2184; 5:HAIp9YZYH6VyWRqa/14az15XJ5/VCUMLZEf5OUqVF8uRSZx0dZELIA8ZwinuGpbrIOGhTH7GgdBVqPd+N0G4FnG/XRZxt1h7LhAoiDAzyERGwsAnzE17ICByfANXDeRJwpo4S92Q7UBHKAxFoH1ZDt4pQ0HFxkOwYubZVqBGpxfpet5taEEBXEbpJN3zXDbHur+C2iyROg6FplMXsekwA5+ffPyUx7RcUaJD8QvR+YbNpV11d+oxNhXBtwcf2T6Jhc1qGmQGk1izkGZbcJ4/3fSjQD3bLrpTPW5W0YYmKJV9YDfbhjAZX0T5ZYObabimpK69io71RryQofrWqF7RaZOCDzQKoc0A1V7iwMW04mhV2ovVmEPK0M9p1Irm3+achP1KQht10Yie/eFQcoMMBWLRhEgpwQOfPLZwMnXYXG9Wcksj+W6YgLkbW+a43QyKehmQdN7rKbNdzYrxVivjTw0xU1DA4Kh3mwnTk9Hxt3ncnu/0/L/NnYgem1zo19dC; 24:JXBTL9/mGvsGDBw2i3B2kzKr+CGlP870c9Qk67P7m6ZWMl4b//5xdH/Y9pkebjagc1YpWRoph4olXu6TzSGjQfW7Egl6BurdZT8NgVau2mQ=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; BY2PR05MB2184; 7:LfCd4mu8WoAxTqMmmD4VLfZXINJ/UIqQf8CdMijHJtHmdRZbg7a8ppUpx1ZEwunzd0Bw/v3uO+M4Tb0N5i8k2PF2XTv/D4UFVXE2IRWZV6I34wYjb2NJj7hMnHeyy4KbthrUTtQp3DlQAhaQNsJbGUipq8A+0x60nH2TVbYOdnn2xUM/33Fxa1Ta8zh2w4WlvJeJ4ICdzJoaEaItpwH/tha1AEICfTnMwCKP9oqmAtl1QV2x0i7/5GL30OKvLq3pWTmCx1r4Cvf3HZSwXY6g2ulaE7pD02qydgrJ5k4gvVxMFUjEr8xVGvxks6Lag+0Wb/2Gu35fkV6L3RJmt7fzLZVZXt3xuH0q8itOHPZCaHO8UFq2bc8QQmFJTRYnoyjDFqW1JZaP89vZFArJhhdAHuRWDvlr0lFgahX+YVoq5bHqIUTOvT2hMmmz/SGtN6hXjgjNGrehtyi/552ntgROdfpDO8uT6QHjaFzwL9RFWN0w0saKn4QCTdRKsIGXpZBlWIKyitO7DYQUfQmtMJIIMZYIKutWbYxke5+JbFy4W7GvoKeTCt/+JH0Z0PgLt8bmZiFfCUKyc5slnQDP3D0cIl8woZfsp+ZJ8ANUVj0ss1j5D17T4d2hcKpmmAupJToB0Ig1ABNY38CTLMT/Q8Eg4XkkJi5NzcdM/tllPDy2sNkUN1oyQ9myirzd1nbAmrn3EL2qSKn9Hl528GI4kLkqFRM4SNHFq/A5SZuvUg002zxcE/H/6e8mv5XeUZMAZ4nIoUq4Pev8JZak2/j+j8HqHRbLjWi7EB6k765W/t+/ftk=
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 28 Jun 2017 12:52:43.8374 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR05MB2184
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PHz64X4IIqVgfdHylRahVaVSiNU>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 12:52:51 -0000

On 6/27/2017 4:29 PM, Stewart Bryant wrote:
> In the introduction it says: "In [RFC3107], this feature was controlled by a
> BGP Capability Code that has never been implemented, and is now essentially
> obsolete." which left me wondering whether there was the intention to formally
> deprecate the feature through the RFC system.

The IANA consideration section of this document requests that the 
"multiple routes to a destination" capability code be marked as 
deprecated, with a reference to this document.  Isn't that sufficient?


From nobody Wed Jun 28 06:25:21 2017
Return-Path: <stewart@g3ysx.org.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 EACAA12EC40 for <ietf@ietfa.amsl.com>; Wed, 28 Jun 2017 06:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=g3ysx-org-uk.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 cbRb13JmwXAV for <ietf@ietfa.amsl.com>; Wed, 28 Jun 2017 06:25:06 -0700 (PDT)
Received: from mail-wm0-x230.google.com (mail-wm0-x230.google.com [IPv6:2a00:1450:400c:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5511F12EC47 for <ietf@ietf.org>; Wed, 28 Jun 2017 06:25:04 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id i127so58832468wma.0 for <ietf@ietf.org>; Wed, 28 Jun 2017 06:25:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=g3ysx-org-uk.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=GaOHiSZhI0FSejZtco/TyhzU7VbkOGNvIq7u5i6axtc=; b=L7h+joh1D+o1UI8tiaiyZjLjy/Ak80aoeyd6W8UhkdBN909fIo/qK0nRf+DuuiBPxD l/Mz1Xx3FroSKgchBnqvWExv7hJl5zZquet6ZCY/qRkbLWyCBDCV4XrPPWDo4z3LV81+ yAGPx3xeRzERFPk4i5vUSlWwjVezo31BKCNf5w5l6M8ZQmKd8P1KejpRtmVuwS0+2jcR zY41vrgkY3GjmuZfcoklXdUQjB+wf3wtzC7AjGeDSdNOyL6DWDZfZBrQs492YXsq4Cfe nWKsF+eRfnpIUk8KnX7sVZj5lCqbMEA1eSsnkMmbyr0I+aGXY+VERG/Rq9fSDblUBG0L HNww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=GaOHiSZhI0FSejZtco/TyhzU7VbkOGNvIq7u5i6axtc=; b=G6T2aU3e0w2GFgiSQ7BDpxzzYaniayQFx2soU0FfH7qtq3mtJGRJYMyHAiFyIyRZI7 vBhrO3UOXH3cilFT8wSMhs6bdLRDGG92UpzgNQTNI4xAZoYr0nXjMhD2RBaGImOLku0g 8XOHbCLXQ/4Q2z40R3S8aKDnb3CG3MNcW/zgPYHDzjFlvUIp5HIk/Hfxd6nWarMmXE6W ti3Ttjlbho5/Xu1n8GCfUnge9XvfQL5B+t2dHxrnTIZnsgKwMDiG/j4VoKcPg6drVJaX P39bFnxu1sc7q4xBf9jNFKmqeHLQvc7ADFIC/IgBj8RoAt9iSLYgO+giJPEdMNvzMUCW +DNw==
X-Gm-Message-State: AKS2vOwBwFYVI5ct8ZIKLUUDA6vsB6u0IEeSsI6R56+g/pQ6nMIUyaKg xa94lu27Z+ASRmQGa/8ZeA==
X-Received: by 10.28.46.3 with SMTP id u3mr7199296wmu.68.1498656302138; Wed, 28 Jun 2017 06:25:02 -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 k75sm8423662wmh.10.2017.06.28.06.25.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jun 2017 06:25:01 -0700 (PDT)
Subject: Re: Rtgdir last call review of draft-ietf-mpls-rfc3107bis-02
To: Eric C Rosen <erosen@juniper.net>, rtg-dir@ietf.org
Cc: mpls@ietf.org, draft-ietf-mpls-rfc3107bis.all@ietf.org, ietf@ietf.org
References: <149859539754.31085.2059230421371020521@ietfa.amsl.com> <3c405108-c18f-8f1b-b9e7-25d08157e1ee@juniper.net>
From: Stewart Bryant <stewart@g3ysx.org.uk>
Message-ID: <4f25a6b2-a912-ce02-819c-73c3b4ba9ced@g3ysx.org.uk>
Date: Wed, 28 Jun 2017 14:24:59 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <3c405108-c18f-8f1b-b9e7-25d08157e1ee@juniper.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xJUab6Xw5J45y2rn5jMNFqjDUL8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 13:25:08 -0000

On 28/06/2017 13:52, Eric C Rosen wrote:
> On 6/27/2017 4:29 PM, Stewart Bryant wrote:
>> In the introduction it says: "In [RFC3107], this feature was 
>> controlled by a
>> BGP Capability Code that has never been implemented, and is now 
>> essentially
>> obsolete." which left me wondering whether there was the intention to 
>> formally
>> deprecate the feature through the RFC system.
>
> The IANA consideration section of this document requests that the 
> "multiple routes to a destination" capability code be marked as 
> deprecated, with a reference to this document.  Isn't that sufficient?
>

Hi Eric,

Sorry I missed that.

I am not sure if the same protocol applies to IANA codepoints as RFCs, 
but if you were obsoleting an RFC it would need to be noted in the 
abstract and the introduction.

If you do a respin it might be better to note the deprecation near the 
text on obsolescence, since people tend to read the main text and not 
the IANA section. However at the end of the day it is up to the AD how 
they want to handle this.

- Stewart


From nobody Wed Jun 28 08:06:29 2017
Return-Path: <sean@sn3rd.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 B6504126CF6; Wed, 28 Jun 2017 08:06:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Sean Turner <sean@sn3rd.com>
To: <secdir@ietf.org>
Cc: manet@ietf.org, ietf@ietf.org, draft-ietf-manet-rfc5444-usage.all@ietf.org
Subject: Secdir last call review of draft-ietf-manet-rfc5444-usage-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149866238770.7570.2060858148344768585@ietfa.amsl.com>
Date: Wed, 28 Jun 2017 08:06:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ttu68FsRGOct_yGvkuHE4oCKEm8>
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, 28 Jun 2017 15:06:28 -0000

Reviewer: Sean Turner
Review result: Ready

This draft is well written and in fact provides a wonderful overview of MANET. 
The draft updates RFC5444 based on some operational experience (and thanks for
that); though it does not specify a protocol it is constraining RFC 5444
implementations hence the “updates” header.

>From a security perspective this draft seems fine; there is one
security-related update and it is explained in the security considerations.

>From a non-MANET expert perspective, I have to admit that I found it hard to
figure out exactly what is being “updated”.  It’s a style thing that I’m not
hard over on, but an informative section explaining what got changed would have
really helped this reader.  I will note that there are a couple of places where
the draft is clear that is updates 5444, e.g., s4.4.1, s.4.6,  so I have to
wonder are those the only update?  Or, is it that all the 2119 requirements for
the processing rules update 5444 and you’d only look in 5444 for the packet
formats?


From nobody Wed Jun 28 08:13:46 2017
Return-Path: <chris.dearlove@baesystems.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EAF7E1274D0; Wed, 28 Jun 2017 08:13:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.127
X-Spam-Level: 
X-Spam-Status: No, score=-6.127 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] 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 cZ0AcJqHkmvg; Wed, 28 Jun 2017 08:13:27 -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 56D7E126CF6; Wed, 28 Jun 2017 08:13:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.40,276,1496098800";  d="scan'208";a="9262605"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta1.baesystems.com with ESMTP; 28 Jun 2017 16:13:24 +0100
X-IronPort-AV: E=Sophos;i="5.40,276,1496098800";  d="scan'208";a="7891417"
Received: from glkxh0002v.greenlnk.net ([10.109.2.33]) by baemasmds016.greenlnk.net with ESMTP; 28 Jun 2017 16:13:24 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.201]) by GLKXH0002V.GREENLNK.net ([10.109.2.33]) with mapi id 14.03.0248.002; Wed, 28 Jun 2017 16:13:24 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Sean Turner <sean@sn3rd.com>, "secdir@ietf.org" <secdir@ietf.org>
CC: "manet@ietf.org" <manet@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-manet-rfc5444-usage.all@ietf.org" <draft-ietf-manet-rfc5444-usage.all@ietf.org>
Subject: RE: Secdir last call review of draft-ietf-manet-rfc5444-usage-06
Thread-Topic: Secdir last call review of draft-ietf-manet-rfc5444-usage-06
Thread-Index: AQHS8CAwegFevquESE68dg0fGkiXz6I6YOfw
Date: Wed, 28 Jun 2017 15:13:23 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636E6D3@GLKXM0003v.GREENLNK.net>
References: <149866238770.7570.2060858148344768585@ietfa.amsl.com>
In-Reply-To: <149866238770.7570.2060858148344768585@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="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8LRFW7x3PvO88KbsrNfI9-RzCw0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 15:13:29 -0000

U2Vhbg0KDQpUaGFua3MgZm9yIHRoYXQgcmV2aWV3LiBBbnN3ZXJpbmcgeW91ciBxdWVzdGlvbiBh
Ym91dCBleGFjdGx5IHdoYXQgaXMgdXBkYXRlZCB3aWxsIHRha2UgYSBsaXR0bGUgd29yayAtIG5v
dCB0b28gbXVjaCwgYnV0IGVub3VnaCAoaW5jbHVkaW5nIGNvbnN1bHRpbmcgd2l0aCBjby1hdXRo
b3JzKSB0aGF0IEkgd29uJ3QgdHJ5IHRvIGFuc3dlciBub3csIGJ1dCB3ZSB3aWxsIHByb3ZpZGUg
YW4gYW5zd2VyIC0gYW5kIGRlcGVuZGluZyBvbiB0aGF0IGFuc3dlciBkZXRlcm1pbmUgaWYgYW55
IGFwcHJvcHJpYXRlIGNvbW1lbnQocykgc2hvdWxkIGJlIGFkZGVkLg0KDQpDaHJpc3RvcGhlcg0K
DQotLSANCkNocmlzdG9waGVyIERlYXJsb3ZlDQpTZW5pb3IgUHJpbmNpcGFsIEVuZ2luZWVyDQpC
QUUgU3lzdGVtcyBBcHBsaWVkIEludGVsbGlnZW5jZSBMYWJvcmF0b3JpZXMNCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQoNClQ6IMKgKzQ0IDMzMDAgNDY3NTAwIMKgfCDCoEU6IGNocmlzLmRlYXJsb3ZlQGJh
ZXN5c3RlbXMuY29tDQoNCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlLCBDaGVsbXNm
b3JkIFRlY2hub2xvZ3kgUGFyaywgR3JlYXQgQmFkZG93LCBDaGVsbXNmb3JkLCBFc3NleCBDTTIg
OEhOLg0Kd3d3LmJhZXN5c3RlbXMuY29tL2FpDQpCQUUgU3lzdGVtcyBBcHBsaWVkIEludGVsbGln
ZW5jZSBMaW1pdGVkDQpSZWdpc3RlcmVkIGluIEVuZ2xhbmQgJiBXYWxlcyBObzogMDEzMzc0NTEN
ClJlZ2lzdGVyZWQgT2ZmaWNlOiBTdXJyZXkgUmVzZWFyY2ggUGFyaywgR3VpbGRmb3JkLCBTdXJy
ZXksIEdVMiA3WVANCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogU2VhbiBU
dXJuZXIgW21haWx0bzpzZWFuQHNuM3JkLmNvbV0gDQpTZW50OiAyOCBKdW5lIDIwMTcgMTY6MDYN
ClRvOiBzZWNkaXJAaWV0Zi5vcmcNCkNjOiBtYW5ldEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsg
ZHJhZnQtaWV0Zi1tYW5ldC1yZmM1NDQ0LXVzYWdlLmFsbEBpZXRmLm9yZw0KU3ViamVjdDogU2Vj
ZGlyIGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1tYW5ldC1yZmM1NDQ0LXVzYWdlLTA2
DQoNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0hIFdBUk5JTkcgISAtLS0tLS0tLS0tLS0tLS0tLS0t
LS0tIFRoaXMgbWVzc2FnZSBvcmlnaW5hdGVzIGZyb20gb3V0c2lkZSBvdXIgb3JnYW5pc2F0aW9u
LCBlaXRoZXIgZnJvbSBhbiBleHRlcm5hbCBwYXJ0bmVyIG9yIGZyb20gdGhlIGludGVybmV0Lg0K
Q29uc2lkZXIgY2FyZWZ1bGx5IHdoZXRoZXIgeW91IHNob3VsZCBjbGljayBvbiBhbnkgbGlua3Ms
IG9wZW4gYW55IGF0dGFjaG1lbnRzIG9yIHJlcGx5Lg0KRm9sbG93IHRoZSAnUmVwb3J0IFN1c3Bp
Y2lvdXMgRW1haWxzJyBsaW5rIG9uIElUIG1hdHRlcnMgZm9yIGluc3RydWN0aW9ucyBvbiByZXBv
cnRpbmcgc3VzcGljaW91cyBlbWFpbCBtZXNzYWdlcy4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNClJldmlld2VyOiBTZWFuIFR1cm5l
cg0KUmV2aWV3IHJlc3VsdDogUmVhZHkNCg0KVGhpcyBkcmFmdCBpcyB3ZWxsIHdyaXR0ZW4gYW5k
IGluIGZhY3QgcHJvdmlkZXMgYSB3b25kZXJmdWwgb3ZlcnZpZXcgb2YgTUFORVQuIA0KVGhlIGRy
YWZ0IHVwZGF0ZXMgUkZDNTQ0NCBiYXNlZCBvbiBzb21lIG9wZXJhdGlvbmFsIGV4cGVyaWVuY2Ug
KGFuZCB0aGFua3MgZm9yIHRoYXQpOyB0aG91Z2ggaXQgZG9lcyBub3Qgc3BlY2lmeSBhIHByb3Rv
Y29sIGl0IGlzIGNvbnN0cmFpbmluZyBSRkMgNTQ0NCBpbXBsZW1lbnRhdGlvbnMgaGVuY2UgdGhl
IOKAnHVwZGF0ZXPigJ0gaGVhZGVyLg0KDQo+RnJvbSBhIHNlY3VyaXR5IHBlcnNwZWN0aXZlIHRo
aXMgZHJhZnQgc2VlbXMgZmluZTsgdGhlcmUgaXMgb25lDQpzZWN1cml0eS1yZWxhdGVkIHVwZGF0
ZSBhbmQgaXQgaXMgZXhwbGFpbmVkIGluIHRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9ucy4NCg0K
PkZyb20gYSBub24tTUFORVQgZXhwZXJ0IHBlcnNwZWN0aXZlLCBJIGhhdmUgdG8gYWRtaXQgdGhh
dCBJIGZvdW5kIGl0IA0KPmhhcmQgdG8NCmZpZ3VyZSBvdXQgZXhhY3RseSB3aGF0IGlzIGJlaW5n
IOKAnHVwZGF0ZWTigJ0uICBJdOKAmXMgYSBzdHlsZSB0aGluZyB0aGF0IEnigJltIG5vdCBoYXJk
IG92ZXIgb24sIGJ1dCBhbiBpbmZvcm1hdGl2ZSBzZWN0aW9uIGV4cGxhaW5pbmcgd2hhdCBnb3Qg
Y2hhbmdlZCB3b3VsZCBoYXZlIHJlYWxseSBoZWxwZWQgdGhpcyByZWFkZXIuICBJIHdpbGwgbm90
ZSB0aGF0IHRoZXJlIGFyZSBhIGNvdXBsZSBvZiBwbGFjZXMgd2hlcmUgdGhlIGRyYWZ0IGlzIGNs
ZWFyIHRoYXQgaXMgdXBkYXRlcyA1NDQ0LCBlLmcuLCBzNC40LjEsIHMuNC42LCAgc28gSSBoYXZl
IHRvIHdvbmRlciBhcmUgdGhvc2UgdGhlIG9ubHkgdXBkYXRlPyAgT3IsIGlzIGl0IHRoYXQgYWxs
IHRoZSAyMTE5IHJlcXVpcmVtZW50cyBmb3IgdGhlIHByb2Nlc3NpbmcgcnVsZXMgdXBkYXRlIDU0
NDQgYW5kIHlvdeKAmWQgb25seSBsb29rIGluIDU0NDQgZm9yIHRoZSBwYWNrZXQgZm9ybWF0cz8N
Cg0KKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioKVGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRl
bnRpYWwgdG8gdGhlIGludGVuZGVkCnJlY2lwaWVudCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdl
ZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkCnJlY2lwaWVudCBwbGVhc2UgZGVsZXRlIGl0
IGZyb20geW91ciBzeXN0ZW0gYW5kIG5vdGlmeSB0aGUgc2VuZGVyLgpZb3Ugc2hvdWxkIG5vdCBj
b3B5IGl0IG9yIHVzZSBpdCBmb3IgYW55IHB1cnBvc2Ugbm9yIGRpc2Nsb3NlIG9yCmRpc3RyaWJ1
dGUgaXRzIGNvbnRlbnRzIHRvIGFueSBvdGhlciBwZXJzb24uCioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqCg==


From nobody Wed Jun 28 11:06: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 93946129AF3; Wed, 28 Jun 2017 11:06:17 -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-ietf-trill-rbridge-multilevel.all@ietf.org, ietf@ietf.org, trill@ietf.org
Subject: Genart last call review of draft-ietf-trill-rbridge-multilevel-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149867317753.7558.8752757743866337364@ietfa.amsl.com>
Date: Wed, 28 Jun 2017 11:06:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PscBXF13hcOCW03ML4bl5Sp8Bws>
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, 28 Jun 2017 18:06:17 -0000

Reviewer: Stewart Bryant
Review result: Ready

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

For more information, please see the FAQ at

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

Document: draft-ietf-trill-rbridge-multilevel-??
Reviewer: Stewart Bryant
Review Date: 2017-06-28
IETF LC End Date: 2017-06-28
IESG Telechat date: 2017-07-06

Summary:

This is a well written document. I do however have a concern with the scaling
text in section 1.2.x, as I think this could be more accessible and ought to
include discussion of MAC Address scaling. More information below.

Major issues: None

Minor issues: The key justification for multi-area is scaling. The scene is set
in Section 1.2.x. However there are no references, the design size parameters
are not articulated for each case, and the equations are not derived. I think
that it would be helpful if the draft either provided some more explanation of
the scaling equations and the associated input assumptions, or provided the
assumptions and  directed the reader to an accessible text to understand the
equations. Although there is some discussion on it later there is no discussion
of the number of addresses to be learned in the single and multi-area cases and
the impact this has on the LSDB. The number of addresses to be learned will
impact the ingress RBridge FIB and the FIB update time so this is just as
significant in understanding the benefit of multi-level as understanding the
link-state convergence time is.

Nits/editorial comments: None



From nobody Wed Jun 28 11:31:33 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 6A75712EC75; Wed, 28 Jun 2017 11:31:24 -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: spring@ietf.org, ietf@ietf.org, draft-ietf-spring-oam-usecase.all@ietf.org
Subject: Genart last call review of draft-ietf-spring-oam-usecase-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149867468440.7527.6305996146978005032@ietfa.amsl.com>
Date: Wed, 28 Jun 2017 11:31:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gI23-MlYgcKQtXLvWWdhGuml4d0>
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, 28 Jun 2017 18:31:25 -0000

Reviewer: Pete Resnick
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-oam-usecase-06
Reviewer: Pete Resnick
Review Date: 2017-06-28
IETF LC End Date: 2017-06-30
IESG Telechat date: Not scheduled for a telechat

Summary: Not Ready for publication as Informational, but might be Ready for
publication as Proposed Standard

Major issues:

This is an admittedly unusual review. I have read through the entire document,
and the technical work seems fine, but is well beyond my technical expertise,
so I can't really comment on the technical correctness. However, it is
absolutely clear to me that this is *not* a "use case" document at all and I
don't think it's appropriate as an Informational document. This is clearly a
*specification* of a path monitoring system. It gives guidances as to required,
recommended, and optional parameters, and specifies how to use different
protocol pieces. It is at the very least what RFC 2026 refers to as an
"Applicability Statement (AS)" (see RFC 2026, sec. 3.2). It *might* be a BCP,
but it is not strictly giving "common guidelines for policies and operations"
(2026, sec. 5), so I don't really think that's right, and instead this should
be offered for Proposed Standard. Either way, I think Informational is not
correct. Importantly, I think there is a good likelihood that this document has
not received the appropriate amount of review; people tend to ignore
Informational "use case" documents, and there have been no Last Call comments
beyond Joel's RTG Area Review. Even in IESG review, an Informational document
only takes the sponsoring AD to approve; every other AD can summarily ignore
the document, or even ballot ABSTAIN, and the document will still be published
(though that does not normally happen). This document should have much more
than that level of review. I strongly recommend to the WG and AD that this
document be withdrawn as an Informational document and resubmitted for Proposed
Standard and have that level of review and scrutiny applied to it.

Minor issues:

None.

Nits/editorial comments:

This document refers to RFC 4379, which has been obsoleted by RFC 8029. It
seems like the references should be updated.



From nobody Wed Jun 28 12:07:21 2017
Return-Path: <tinatsou6@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 359F0128768; Wed, 28 Jun 2017 12:07:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CO__ZxjJlgV8; Wed, 28 Jun 2017 12:07:17 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::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 9ACDF127137; Wed, 28 Jun 2017 12:07:17 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id c73so37987498pfk.2; Wed, 28 Jun 2017 12:07:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=PScfJdq7x3ShU5J3P0x5jikoOdQs8uQ0DfPdpyCHoQg=; b=ZBZZ8Z99UMcnLKiFxJJVjE0PsY43/ceCveIotmnl3rXhDOjynqO9hXNFrw5PdZPKH6 SB5O/PvjTVwT4D2mZlEBI5Bpn1ZvcetAYc5Ttw0Z7MQhkUp6ULxBS8QsS2szRo0KWGHl al/iVqrq74oJsjnG4HgfXcp/JzBj/y95G2Rn5VEXY5V3ypGnEpKr7kEqdJF5u5HhZxec Y3R39ddNGu99T/QuevXdn+hD1u/8s5GKmUqsDCXPt3Unltc+z+IMss469ckNm6esIikg +CyV/r8w7vSRdNN9D39Jn4pLDzjzpkLf5E6puNnThZzrdT6WMyg0lghXg4rwCR/444VP /R9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=PScfJdq7x3ShU5J3P0x5jikoOdQs8uQ0DfPdpyCHoQg=; b=bCRZgbNmbkiNEQxfG/diEx78E16URqRrzHUIoaPC4fp/TJ5zHT2sSZlcxbasjGxmKx HTDul/1pwXnk2AW83GU5WCwf1FynaVFZwT8O7KrVP/cSk+oeu9WnOGUw7W1f26Uz0KGb UrDlBb4jEnN6fjNcKT0Cghfe3YJcs5+9CtxDL+g2CLeqIGM5yjPXOtAD6R34iLSMwVQp EwRLQ417J+tDfD+VhIe1WcleKyOIQBsR/X3QTT3VX4eMT0B/X9sItIB/VHktsGFhQlZZ oLJTwtp3X3ypdQtSQvPeAsuiht8AY0kT1hkhyAtcvgXvqMImT/JZ8RnzfPFb8JeMt97+ E8qw==
X-Gm-Message-State: AKS2vOx2xdQfwsiMSho09VEzWzpXU8cY1+A5oIuC0ya0QkBBJsrLUmEX lhjQb4uycKNSjB1ZlOA+kXtwegs3wg==
X-Received: by 10.84.169.36 with SMTP id g33mr13309446plb.52.1498676836968; Wed, 28 Jun 2017 12:07:16 -0700 (PDT)
MIME-Version: 1.0
From: Tina Tsou <tinatsou6@gmail.com>
Date: Wed, 28 Jun 2017 19:07:06 +0000
Message-ID: <CAMS-Z8Ahi5MqMLUeFauU4BsgHjQRO8r=ojRJ5gcDwaq0cETwnQ@mail.gmail.com>
Subject: OPSDir last call review of draft-ietf-precis-7613bis-08
To: "ops-dir@ietf.org" <ops-dir@ietf.org>
Cc: "draft-irtf-precis-7613bis.all@ietf.org" <draft-irtf-precis-7613bis.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "tina.tsou@arm.com" <tina.tsou@arm.com>
Content-Type: multipart/alternative; boundary="94eb2c13e262802ded055309e4a0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0mwpz04rmJOebu8YPkPghgDLgPw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 19:07:19 -0000

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

Reviewer: Tina Tsou
Review result: Ready

This is a clear document that updates the methods for handling Unicode
strings representing usernames and passwords. It's more sustainable to
handle internationalized usernames and passwords.

>From an operational and manageability point of view this document is Ready.
I do not see any such issues in the updated methods that the document
defines.

No nit was found.
-- 
Thank you, Tina

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

<div><div><span style=3D"color:rgb(49,49,49);word-spacing:1px;background-co=
lor:rgb(255,255,255)"><div dir=3D"auto">Reviewer: Tina Tsou</div></span><sp=
an style=3D"color:rgb(49,49,49);word-spacing:1px;background-color:rgb(255,2=
55,255)">Review result: Ready</span><br style=3D"color:rgb(49,49,49);word-s=
pacing:1px"><br style=3D"color:rgb(49,49,49);word-spacing:1px"><span style=
=3D"color:rgb(49,49,49);word-spacing:1px;background-color:rgb(255,255,255)"=
><div dir=3D"auto">This is a clear document that updates the methods for ha=
ndling Unicode strings representing usernames and passwords. It&#39;s more =
sustainable to handle internationalized usernames and passwords.</div></spa=
n><br style=3D"color:rgb(49,49,49);word-spacing:1px"><span style=3D"color:r=
gb(49,49,49);word-spacing:1px;background-color:rgb(255,255,255)"><div dir=
=3D"auto">From an operational and manageability point of view this document=
 is Ready. I do not see any such issues in the updated methods that the doc=
ument defines.</div></span><br style=3D"color:rgb(49,49,49);word-spacing:1p=
x"><span style=3D"color:rgb(49,49,49);word-spacing:1px;background-color:rgb=
(255,255,255)"><div dir=3D"auto">No nit was found.</div></span></div></div>=
<div dir=3D"ltr">-- <br></div><div data-smartmail=3D"gmail_signature">

Thank you,
Tina</div>

--94eb2c13e262802ded055309e4a0--


From nobody Wed Jun 28 13:19:17 2017
Return-Path: <d3e3e3@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 CBC9212EB00; Wed, 28 Jun 2017 13:19:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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 MSMSNhDNlL2Q; Wed, 28 Jun 2017 13:19:07 -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 A2E8C12EB05; Wed, 28 Jun 2017 13:19:05 -0700 (PDT)
Received: by mail-it0-x232.google.com with SMTP id v202so35569875itb.0; Wed, 28 Jun 2017 13:19:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xAUGIIhww8QT0s6y90rqIPdu3xXAMovnCzTIixHqShU=; b=WqpyuUXOeGDkXoY6II/66v6y+m+G/j1rNPxWN6BLH4VLErWPy3WYiD9UCnv/ldWjrl SR4TysPO6O74N6u6gEreIqM3r+eEWans51sCl7N9HQSdBnXwMXPl5Ka3IA4IyJKVlEKO TAf0L0AYzj12aMZnqmDylEy9EsuWdVvQpo5Lcuks1zUO2YE6QbRJr1nXkGNlsOLijI/I Om+2G0/D4tkWqfN69FlQil5WnQ3i2trRlBfZZYMdtEVEMe69zh17Gcgqu2aWq8CXnEcC cGpGKvRjPejjy2Eu0UHtDwwjFuEm4kuuMJDiCUmGhdMGH/6iouM8/panVLcVYqNqsw7c azvQ==
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=xAUGIIhww8QT0s6y90rqIPdu3xXAMovnCzTIixHqShU=; b=gFTerYevfzo8Xc1gz0ehQ9Wz/xT1dKvRecnI18B5/oeacfwQuvYyCOiBPVv2FDhFkm FhXlrDw4dmPuw2dYOOdqoJlK7G564fC3G6X7EFOhgHDEFP7V5qrelybnzdwvkIkdHQ4A vVlf6yqTPlkbTm0nSO1eb+bmzE8eW5mJYQvnBYBG6x4kxHWjhqYV5ij/1P0yUnZfYv2J 3GGpTy/Zw9C8No9Tj/jCOmbsQu34Y5aoJjFPcR0T3vCxje2t5euP4/9BifXm89vOQjQY iuOctLye8mWw9sqBfvUoyHe8bXZB0KIxQbChViL6VvOOVeY0aOMm/ZkmyOb/MYz9rPA3 GcwQ==
X-Gm-Message-State: AKS2vOyyIpakUjOMR1DWykScecMPhLcN0HSsJhUyqYpFXpLR4xpaLGKV LEwZFTINuTwUAG0WU8z1PNkhm8sv+g==
X-Received: by 10.36.3.11 with SMTP id e11mr8808369ite.79.1498681144981; Wed, 28 Jun 2017 13:19:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.17.221 with HTTP; Wed, 28 Jun 2017 13:18:49 -0700 (PDT)
In-Reply-To: <149867317753.7558.8752757743866337364@ietfa.amsl.com>
References: <149867317753.7558.8752757743866337364@ietfa.amsl.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 28 Jun 2017 16:18:49 -0400
Message-ID: <CAF4+nEFkM+T_CkO_4UgYMoNYJ3xjOLZWfg1k11sv15dP+HJ-zA@mail.gmail.com>
Subject: Re: Genart last call review of draft-ietf-trill-rbridge-multilevel-06
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: "gen-art@ietf.org Review Team" <gen-art@ietf.org>, draft-ietf-trill-rbridge-multilevel.all@ietf.org,  IETF Discussion <ietf@ietf.org>, "trill@ietf.org" <trill@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/Gkk_KCKh_bBu41sW9MejZe6KcsM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 20:19:10 -0000

Hi Stewart,

Thanks for the comments. See below.

On Wed, Jun 28, 2017 at 2:06 PM, 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 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-trill-rbridge-multilevel-??
> Reviewer: Stewart Bryant
> Review Date: 2017-06-28
> IETF LC End Date: 2017-06-28
> IESG Telechat date: 2017-07-06
>
> Summary:
>
> This is a well written document. I do however have a concern with the scaling
> text in section 1.2.x, as I think this could be more accessible and ought to
> include discussion of MAC Address scaling. More information below.
>
> Major issues: None
>
> Minor issues: The key justification for multi-area is scaling. The scene is set
> in Section 1.2.x. However there are no references, the design size parameters
> are not articulated for each case, and the equations are not derived. I think
> that it would be helpful if the draft either provided some more explanation of
> the scaling equations and the associated input assumptions, or provided the
> assumptions and  directed the reader to an accessible text to understand the
> equations.

A reference and some further exposition of the assumptions made with
the way the equations were arrived at could be added.

>                     Although there is some discussion on it later there is no discussion
> of the number of addresses to be learned in the single and multi-area cases and
> the impact this has on the LSDB. The number of addresses to be learned will
> impact the ingress RBridge FIB and the FIB update time so this is just as
> significant in understanding the benefit of multi-level as understanding the
> link-state convergence time is.

The number of MAC (actually MAC/VLAN or MAC/FGL) addresses to be
learned by an edge TRILL switch is not affected by whether the TRILL
campus uses single or multilevel IS-IS. This number of MAC address
learned is the seventh scaling problem listed in Section 1.1 which
states that multilevel TRILL IS-IS helps only with the other six
problems. This point, that multilevel doesn't help here, could be
emphasized more but I don't think I see much point in this document in
going into details such as the scaling considerations of data plane
MAC address learning (which is the default in TRILL) or control plan
MAC address learning (which does not use the core LSDB but rather Data
Label scoped ESADI link stat databases).

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Nits/editorial comments: None
>
>


From nobody Wed Jun 28 13:23:44 2017
Return-Path: <tinatsou6@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 F2E3212EAF2; Wed, 28 Jun 2017 13:23:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VzRpJyFUB6Na; Wed, 28 Jun 2017 13:23:41 -0700 (PDT)
Received: from mail-pf0-x233.google.com (mail-pf0-x233.google.com [IPv6:2607:f8b0:400e:c00::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 14E151270AC; Wed, 28 Jun 2017 13:23:41 -0700 (PDT)
Received: by mail-pf0-x233.google.com with SMTP id q86so38786906pfl.3; Wed, 28 Jun 2017 13:23:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ziFEEGzg42xReVPga2IZDOJueNy0nkyMIrzCqfHUbPI=; b=DZXl4FFjBJzmGYWoOl9xPLoz/+jdk0ANpZLoyW0kaHxMfpO8GhcOoYqAssQat0bF/j 2w4UHVOXcjGhumuOE8Hu45H7kjHm6BqOMKJpQ/T6gh9x3OUyyHPIIMNERAvaeiOPZK3P PFGWtqWAiq96p8ow1G0p1/c/3/osZDA0vqCW+72g2UEzxK2RDFYjHMLtFXGeyLNpPL6z aAayHIbOah/8L9OZ3p0cCRDBgZbUvK8EtEfUlZGq3bT7m/eCgEe+RFMZO+VjqLsb06kw fp3w9omcxoJxObPEOkUad6mmHgAOA2xRlXV9bVrJnEDT0+4wTwVkyZ8BR/zl1r6g4cdn fXlw==
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=ziFEEGzg42xReVPga2IZDOJueNy0nkyMIrzCqfHUbPI=; b=aW5325ZF+Ncq+FhpLmwANJiaLc5GYhjPmXM8Z7gfaCxo/Iq8iuiUOv2+WfAoO3CJcE ICrukx4CD1lzsCdUHpJ6g4nbJIEshZG2aXlNueZZTq5C5ctdRz/ETEz7//7IBynJs8mG i4B232XrOMctJ7DKxHGmbAsJhkcZJHuxaYZaa0qPi4Vj4SfdtbmzFUi83T5aG0w6ECIs t0MH60UV1BgI3+jOVihtdNDYHsGMx8dNAKjRW13GfN1HFNhcG54XiztQbxv4QwbyHtWN T6+8DHAHvW0emWFF2jf/dklQkfrAfe2Zo6a/phpQ7nzDF3ZwtedF0MjIY/c3PH9rAvyp UdqA==
X-Gm-Message-State: AKS2vOwi1p5eAUTvja6wuB+9NW7b4o2FaKpZuiZ3+RDr5L4fBm+zpvwP pnUyJowTzh6ogs11SiuMRNSaSzl4iQ==
X-Received: by 10.84.210.40 with SMTP id z37mr13638829plh.265.1498681420425; Wed, 28 Jun 2017 13:23:40 -0700 (PDT)
MIME-Version: 1.0
References: <CAMS-Z8Ahi5MqMLUeFauU4BsgHjQRO8r=ojRJ5gcDwaq0cETwnQ@mail.gmail.com>
In-Reply-To: <CAMS-Z8Ahi5MqMLUeFauU4BsgHjQRO8r=ojRJ5gcDwaq0cETwnQ@mail.gmail.com>
From: Tina Tsou <tinatsou6@gmail.com>
Date: Wed, 28 Jun 2017 20:23:29 +0000
Message-ID: <CAMS-Z8AsLtYZXuiRkN-9xfg6ko_3mKfSGqw9y1LRVY2=BweU0w@mail.gmail.com>
Subject: Re: OPSDir last call review of draft-ietf-precis-7613bis-08
To: "ops-dir@ietf.org" <ops-dir@ietf.org>
Cc: "draft-ietf-precis-7613bis.all@ietf.org" <draft-ietf-precis-7613bis.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>,  "tina.tsou@arm.com" <tina.tsou@arm.com>
Content-Type: multipart/alternative; boundary="94eb2c142410b2303b05530af593"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/eon_ArDNOavHDKpK5Cqi3wDnBWw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 20:23:42 -0000

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

Correct the author email...


On Wed, Jun 28, 2017 at 12:07 PM Tina Tsou <tinatsou6@gmail.com> wrote:

> Reviewer: Tina Tsou
> Review result: Ready
>
> This is a clear document that updates the methods for handling Unicode
> strings representing usernames and passwords. It's more sustainable to
> handle internationalized usernames and passwords.
>
> From an operational and manageability point of view this document is
> Ready. I do not see any such issues in the updated methods that the
> document defines.
>
> No nit was found.
> --
> Thank you, Tina
>
-- 
Thank you, Tina

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

<div><div dir=3D"auto">Correct the author email...</div><div dir=3D"auto"><=
br></div><br><div class=3D"gmail_quote"><div>On Wed, Jun 28, 2017 at 12:07 =
PM Tina Tsou &lt;<a href=3D"mailto:tinatsou6@gmail.com">tinatsou6@gmail.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"><div><div><span sty=
le=3D"color:rgb(49,49,49);word-spacing:1px;background-color:rgb(255,255,255=
)"><div dir=3D"auto">Reviewer: Tina Tsou</div></span><span style=3D"color:r=
gb(49,49,49);word-spacing:1px;background-color:rgb(255,255,255)">Review res=
ult: Ready</span><br style=3D"color:rgb(49,49,49);word-spacing:1px"><br sty=
le=3D"color:rgb(49,49,49);word-spacing:1px"><span style=3D"color:rgb(49,49,=
49);word-spacing:1px;background-color:rgb(255,255,255)"><div dir=3D"auto">T=
his is a clear document that updates the methods for handling Unicode strin=
gs representing usernames and passwords. It&#39;s more sustainable to handl=
e internationalized usernames and passwords.</div></span><br style=3D"color=
:rgb(49,49,49);word-spacing:1px"><span style=3D"color:rgb(49,49,49);word-sp=
acing:1px;background-color:rgb(255,255,255)"><div dir=3D"auto">From an oper=
ational and manageability point of view this document is Ready. I do not se=
e any such issues in the updated methods that the document defines.</div></=
span><br style=3D"color:rgb(49,49,49);word-spacing:1px"><span style=3D"colo=
r:rgb(49,49,49);word-spacing:1px;background-color:rgb(255,255,255)"><div di=
r=3D"auto">No nit was found.</div></span></div></div><div>-- <br></div><div=
 data-smartmail=3D"gmail_signature">

Thank you,
Tina</div></blockquote></div></div><div dir=3D"ltr">-- <br></div><div data-=
smartmail=3D"gmail_signature">

Thank you,
Tina</div>

--94eb2c142410b2303b05530af593--


From nobody Wed Jun 28 14:39:07 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 F2DDC12EC71; Wed, 28 Jun 2017 14:38:45 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <secdir@ietf.org>
Cc: webpush@ietf.org, ietf@ietf.org, draft-ietf-webpush-vapid.all@ietf.org
Subject: Secdir last call review of draft-ietf-webpush-vapid-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149868592596.7659.3988919152591675113@ietfa.amsl.com>
Date: Wed, 28 Jun 2017 14:38:45 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ljja2ObNdLgJ6QwJ0USq_p3Z8As>
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, 28 Jun 2017 21:38:46 -0000

Reviewer: Robert Sparks
Review result: Has Nits

Summary: Ready (with nits)

This document provides a mechanism for an application server to voluntarily
identify itself to a push server using JWT. The draft is easy to follow. The
security properties of this mechanism are clearly and thoroughly discussed.

There are some minor nits:

1) The draft says that expiry claims MUST NOT be more than 24 hours from the
time of the request. Consider adding some discussion of why 24 hours was chosen
(vs some other arbitrary value), especially given the MUST NOT strength of the
requirement.

2) The last paragraph of 4.2 says application servers create subscriptions, but
it means to say that user agents do. Martin already addressed when I brought it
up out-of-band with <https://github.com/webpush-wg/webpush-vapid/pull/39/files>.

3) The last sentence of the abstract is missing a word. Perhaps s/subscription
a/subscription to a/ ?

4) Consider using the RFC8174 update to RFC2119.



From nobody Wed Jun 28 15:56:01 2017
Return-Path: <peter@filament.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 989C212EC7E for <ietf@ietfa.amsl.com>; Wed, 28 Jun 2017 15:55:59 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=filament-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 QJeq4Zj63QBd for <ietf@ietfa.amsl.com>; Wed, 28 Jun 2017 15:55:57 -0700 (PDT)
Received: from mail-it0-x22c.google.com (mail-it0-x22c.google.com [IPv6:2607:f8b0:4001:c0b::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDFCE12EC2A for <ietf@ietf.org>; Wed, 28 Jun 2017 15:55:57 -0700 (PDT)
Received: by mail-it0-x22c.google.com with SMTP id m84so42249137ita.0 for <ietf@ietf.org>; Wed, 28 Jun 2017 15:55:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=filament-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=ostc474rEBpF5e26A9XupXjNyRg2FUqYNmFgKfDNTqo=; b=Up5SQNxVHYcR4G/ElWNwEdnZ6hP6gv0Iyu0GSoAPON2bmXoJiLRqLFj78zPhpxN/mU A50MI+lOSiv3gBEXBJqG+HCDK+vkc/XO16j+6h9JBub/ryxeLxs+R3iyd89XxTiiyVFX UW5W5qtkyIe81tKxs1YbZlc9WifXjesxIYkHF22teCBt5xif7dkfeGwT5nAAffGJSCzT bR77F2VMJ/gyRMxBvWXyaIpV9d58qYzTQ9dl2/Rpw0H/LaZoaBs35+OZvra9Sn9WODR8 sU4k4st3jOlSt61iIu38iND1af6v3h+hLahWjMJKgU+inOKdHwYW7PPCPDsBUrLgKLLJ cJqw==
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=ostc474rEBpF5e26A9XupXjNyRg2FUqYNmFgKfDNTqo=; b=bD8AMRg6zPUv1PBk5/1kHT6nhsSNsxVghdpCiAN5py7b0AwS6PjiVtNJIeJmfODJHY 7S1hhy5/9a5C/cyf3ikepI6F7dg1aTWeKbvvEKnTQ8cAXgdL38Lp6TUF7b/RJhCeQrAm uKiU4sFm8JqpBGRdmUPYZ2xoM63S7z2DBAYQrTe8SpbMk5ZNu41cBVDX8+LGFrgDdBt+ 1hiyQ7vzMFZRQqAuTAlu35XDqz1WOZylVfqZz2Q7mgwznmAnBXyS4035j3NNoPjU+R2W ZRUd8LJ+pa9YSuKPO+DFK9hhRY206XrC77CpThlttFhy08NgcbTFKxuduMwP/D1LG/Eb VmJg==
X-Gm-Message-State: AKS2vOy3ypprqHlQsfFpN6OxvbO8DWj1voLQbU0Jhy6j5amdzJAAvxR0 E0lNxhZAuZ6V7PoV
X-Received: by 10.36.208.83 with SMTP id m80mr10964917itg.25.1498690557082; Wed, 28 Jun 2017 15:55:57 -0700 (PDT)
Received: from aither.local ([2601:282:4202:67d3:90a7:b391:5c11:8827]) by smtp.gmail.com with ESMTPSA id r87sm550261ioe.49.2017.06.28.15.55.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 28 Jun 2017 15:55:56 -0700 (PDT)
Subject: Re: OPSDir last call review of draft-ietf-precis-7613bis-08
To: Tina Tsou <tinatsou6@gmail.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
References: <CAMS-Z8Ahi5MqMLUeFauU4BsgHjQRO8r=ojRJ5gcDwaq0cETwnQ@mail.gmail.com> <CAMS-Z8AsLtYZXuiRkN-9xfg6ko_3mKfSGqw9y1LRVY2=BweU0w@mail.gmail.com>
Cc: "draft-ietf-precis-7613bis.all@ietf.org" <draft-ietf-precis-7613bis.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "tina.tsou@arm.com" <tina.tsou@arm.com>
From: Peter Saint-Andre - Filament <peter@filament.com>
Message-ID: <c3553c40-40b3-4160-3a86-6bbc20a0d5f8@filament.com>
Date: Wed, 28 Jun 2017 16:55:55 -0600
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: <CAMS-Z8AsLtYZXuiRkN-9xfg6ko_3mKfSGqw9y1LRVY2=BweU0w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DC8Upz2TEL3869C6tNwxNozio2M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 22:56:00 -0000

Hi Tina, thanks for your review!

On 6/28/17 2:23 PM, Tina Tsou wrote:
> Correct the author email...
> 
> 
> On Wed, Jun 28, 2017 at 12:07 PM Tina Tsou <tinatsou6@gmail.com
> <mailto:tinatsou6@gmail.com>> wrote:
> 
>     Reviewer: Tina Tsou
>     Review result: Ready
> 
>     This is a clear document that updates the methods for handling
>     Unicode strings representing usernames and passwords. It's more
>     sustainable to handle internationalized usernames and passwords.
> 
>     From an operational and manageability point of view this document is
>     Ready. I do not see any such issues in the updated methods that the
>     document defines.
> 
>     No nit was found.
>     -- 
>     Thank you, Tina
> 
> -- 
> Thank you, Tina



From nobody Wed Jun 28 16:31:14 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 DCA1512EB0B; Wed, 28 Jun 2017 16:30:57 -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 0lhYZe-n-4Ws; Wed, 28 Jun 2017 16:30:56 -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 ABB8212EC2A; Wed, 28 Jun 2017 16:30:55 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id h22so43452089lfk.3; Wed, 28 Jun 2017 16:30:55 -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=u/HhFhLLRZcU5z43GA4cKl/VbYnkux0RTu+AneGlxIY=; b=L5GtFivmyDiLgvG3xB31/bFgJIQQPJnlOYm3i5wZtNr+Rw3qajc5+0vOwW6CkS+g30 SLt9TGHJThbXI4BbN1Y7bIdzW52qqg+FmDNqwpyV92obYdgL7CWSj5K16RarI1Lqnust D1/B57aDa/I9y8cCFSv/TtF8VkViVl7hQXT/JLBmjXJSw9ydDa4nzxehvrPS4Ctk5IWU 12GlPMG0wK4TUSSw2yj1rN+8mJCc09v8xaot8dlTaL98azpqum4SWJyHmbXweYfpehDb Bqou8GyGUoAqJh5ZkCZ4ImcdrbTVvOfvT1ueP7aeggFFnckqunfkztvs+mH1TijPLV7n QDhA==
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=u/HhFhLLRZcU5z43GA4cKl/VbYnkux0RTu+AneGlxIY=; b=rmHBKxcHigmDMesgBehDXiGBMU88F0NHRo3KSEBKOrzdv5yZxJVopLg2AjLigcsJNZ m5ljWbdzM+YWWNoTQOhb0qsdHiuSVTGbVzJT7IP6uCR2YUg9xSq53r74d7lZ16HwV25b Zuo4v5WAzDkcWc+QuVTOpZVLDsombM44ud1J6/lF6nNmFuRKWdbrXNbKtHXLWEFrTuoT ItUHac3ZtrGSMGfss3kCN+3Fky9qSjR657GgXCq7SCjtheEF912szSEb3DEnLddJO+Ak a3QGC4pEUycoiM2w5OGx5w+yw9EE+F/k/KOPZP99xtKuIlOUOXhZQtOm+OVI/1ilRi8k B24Q==
X-Gm-Message-State: AKS2vOyV5urLhAr5YTD0EUiIWN1YSnM7ToxVoceEPnRLMqkzJ6L7Ny+t so9ZZ9S1L339f720DZf9M6xS6wIxrK79KzA=
X-Received: by 10.25.196.205 with SMTP id u196mr3774462lff.19.1498692654005; Wed, 28 Jun 2017 16:30:54 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.78.17 with HTTP; Wed, 28 Jun 2017 16:30:53 -0700 (PDT)
In-Reply-To: <149868592596.7659.3988919152591675113@ietfa.amsl.com>
References: <149868592596.7659.3988919152591675113@ietfa.amsl.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 28 Jun 2017 16:30:53 -0700
Message-ID: <CABkgnnXhshe3q_XgwLVFRhoHeZ9nRm1Gnsmhe9R0WTjZF64xCA@mail.gmail.com>
Subject: Re: Secdir last call review of draft-ietf-webpush-vapid-03
To: Robert Sparks <rjsparks@nostrum.com>
Cc: "secdir@ietf.org" <secdir@ietf.org>, "webpush@ietf.org" <webpush@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-webpush-vapid.all@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/c6-Xh1OAP_B-F2i1jnJL0FVu2Mc>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 28 Jun 2017 23:30:58 -0000

Thanks Robert.

On 28 June 2017 at 14:38, Robert Sparks <rjsparks@nostrum.com> wrote:
> 1) The draft says that expiry claims MUST NOT be more than 24 hours from the
> time of the request. Consider adding some discussion of why 24 hours was chosen
> (vs some other arbitrary value), especially given the MUST NOT strength of the
> requirement.

Frankly, the decision is a little arbitrary, but it's where we landed.
It's a balance between competing concerns of reuse and the exposure to
theft and abuse that comes with reuse.  The overriding reason for a
MUST NOT strength is that it allows the server to reject requests with
bad claims.  I'll add a sentence to the security considerations, which
talk about the need for expiration and the implications of the MUST
NOT.

See https://github.com/webpush-wg/webpush-vapid/pull/40

> 2) The last paragraph of 4.2 says application servers create subscriptions, but
> it means to say that user agents do. Martin already addressed when I brought it
> up out-of-band with <https://github.com/webpush-wg/webpush-vapid/pull/39/files>.
>
> 3) The last sentence of the abstract is missing a word. Perhaps s/subscription
> a/subscription to a/ ?

Fixed, thanks.

> 4) Consider using the RFC8174 update to RFC2119.

Noted.


From nobody Wed Jun 28 19:35:17 2017
Return-Path: <worley@ariadne.com>
X-Original-To: ietf@ietf.org
Delivered-To: ietf@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 02C4B1270A3; Wed, 28 Jun 2017 19:35:17 -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-trill-arp-optimization.all@ietf.org, ietf@ietf.org, trill@ietf.org
Subject: Genart last call review of draft-ietf-trill-arp-optimization-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149870371689.6498.12830215563460223064@ietfa.amsl.com>
Date: Wed, 28 Jun 2017 19:35:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/cbLYX4A3duLTKGDaHFj_ahLwPd8>
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, 29 Jun 2017 02:35:17 -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 treat these comments just
like any other last call comments.

Document:  draft-ietf-trill-arp-optimization-08
Reviewer:  Dale R. Worley
Review Date:  2017-06-28
IETF LC End Date:  2017-06-29
IESG Telechat date:  unknown

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

   Abstract

   This document describes mechanisms to optimize the ARP (Address
   Resolution Protocol) and ND (Neighbor Discovery) traffic in TRILL
   campus.

s/in TRILL campus/in a TRILL campus/

Perhaps summarize what the optimizations are:

   Each edge RBridge maintains a cache of IP/MAC address/Data Label
   bindings that are learned from ARP/ND requests and responses that
   pass through it.  This cache allows it to avoid flooding an ARP/ND
   request by either responding to it directly or by encapsulating it
   and unicasting it to the location where it is in use.

   2 ARP/ND Optimization Requirement and Solution

   (including DHCP or gratuitous ARP_messages).

s/_//

   and should allow an end station to
   detect duplicate IP addresses.

Unless this is a well-known phrase, it would be best if it was clear
whether the end station is detecting that its own IP address is
duplicated, or whether it is detecting that some other station's IP
address is duplicated.

   TRILL already provides an option to disable data-plane learning from
   the source MAC address of end-station frames on a per port basis (see
   Section 5.3 of [RFC6325]).

Given how this section is written, shouldn't this option be considered
an option to *enable* data-plane learning?  And in particular, doesn't
that imply that TRILL already includes a solution to suppress ARP
flooding?

Also, what is the meaning of "learning from the source MAC address"?
It seems like you'd want to specify what the learning is *of*, and
then perhaps what it is learned *from*.

Or is this particular learning of MAC addresses alone, and not of
IP/MAC bindings?  If so, then isn't this feature orthogonal to ARP/ND
optimization?

As a design matter, I'm curious why an RBridge can't learn IP/MAC
bindings by snooping data packets, and only by snooping ARP packets.
I suspect there are good reasons for it, but the naive reader (me) is
left wondering...

   4.1 SEND Considerations

   Secure SEND messages require knowledge of cryptographic keys. Methods
   of communicating such keys to RBridges for use in SEND are beyond the
   scope of this document. Thus, using the optimizations in this
   document, RBridges do not attempt to construct SEND messages and are
   generally transparent to them. RBridges only construct ARP, RARP, or
   insecure ND messages, as appropriate.

This doesn't flow quite correctly.  The second sentence suggests that
there are known mechanisms for distributing keys to RBridges, but that
this document doesn't describe them.  The reader then expects that the
third sentence will say that if RBridges are provisioned with keys in
an environment, they can generate SEND responses.  But instead, the
real meaning of the second sentence seems to be that there are no such
ways of distributing keys to RBridges and therefore they can't
generate SEND responses.  That suggests that the second sentence
should be rephrased:

    There are no methods of communicating such keys to RBridges for
    use in SEND, and thus RBridges cannot construct SEND messages and
    must be generally transparent to them.

Or perhaps "SEND forbids communicating such keys to RBridges, and
thus...".

   4.3 Get Sender's IP/MAC Mapping Information for Non-zero IP 

What is "non-zero IP"?  Is this the case discussed in section 4.4 item
(d)?  (If so, it also includes "a Neighbor Solicitation for DAD
... which has the unspecified source address".)  Perhaps the property
being described is "Get Sender's IP/MAC Mapping Information from
Non-Address Probe ARP/ND Queries".

   4.4 Determine How to Reply to ARP/ND

   It is not essential that all RBridges use the same strategy for which
   option to select for a particular ARP/ND query. It is up to the
   implementation.

It appears that the division between options (a), (b), (c), and (d)
are fixed by the draft, so this statement is rather confusing.  Also,
"It is up to the implementation." is a bit awkward.  Perhaps:

   Within each item, it is an implementation decision which strategies
   to use for any particular ARP/ND query falling under that item.

--

     Because the edge RBridge might not have an IPv6 address, the
     source IP address for such an ND response MUST be that of the
     target end station.

Wouldn't the source IP address for such an ARP response also be that
of the target end station, given that it is a simulated ARP response
from the target end station?  That is, why is this MUST specific to
IPv6?

     b.3. Drop the message if the directory mechanism is used and you
     know there should be no response (query based on an non-existent IP
     address for example).

It would be better to phrase this:

     b.3. Drop the message if the directory server gives authoritative
     information that the IP address is non-existent.

   4.5 Determine How to Handle the ARP/ND Response

   the target's egress RBridge R2 as discussed in subsection 3.2 item a)

Really, it's subsection 3.2 item a.2.

   or to flood the request as per [RFC6325]

Isn't this item a.5?

   When/if the target responds, 

Probably better as "If and when the target responds,".

   5 Handling RARP (Reverse Address Resolution Protocol) Messages

The title of section 5 starts "Handling" whereas the titles of
sections 6 and 7 start "Handling of".  It's probably worth making the
three consistent.

   Its use is similar to

Shouldn't this be "Its processing is similar to"

   Normally, it is used to
   look up a MAC address to find the corresponding IP address.

Doesn't this duplicate the third sentence of this paragraph?

   7 Handling of Duplicate IP Addresses

   Duplicate IP addresses can be detected when an existing active
   IP1/MAC1 mapping gets modified.

Should "IP1/MAC1" be "IP/MAC"?  Neither "IP1" nor "MAC1" is used
elsewhere in the document.

   Also an edge RBridge may send a query
   to the former owner of IP called a DAD-query (Duplicate Address
   Detection query).

This is a bit ambiguous -- is it the query or the former owner that is
called a DAD-query?  Better "may send a query called a DAD-query (...)
to the former owner of the IP".

However the following discussion does not specify how the DAD-query is
addressed to the "former owner", and so doesn't specify if the former
owner is defined by the MAC address previously associated with the IP
address or what.  The protocol logic seems to require that the
destination MAC is the one previously associated with the IP address
and the queried-for IP must be the IP in question.  This should be
spelled out, since the source addressing is specified.

   In the case where the former owner replies, a Duplicate Address has
   been detected. In this case the querying RBridge SHOULD log the
   duplicate so that the network administrator can take appropriate
   action.

What action should the querying RBridge take in regard to its cache?

   9 Security Considerations

s/as provide in/as provided in/ (two instances)

   12.1 Normative References

   [DirMech] Dunbar, L., Eastlake 3rd, D., Perlman, R., I. Gashinsky.
              and Li Y., TRILL: Edge Directory Assist Mechanisms",
              draft-ietf-trill-directory-assist-mechanisms, work in
              progress.

There are unbalanced double-quotes here.



From nobody Thu Jun 29 00:28:47 2017
Return-Path: <prvs=346f6a78b=Ruediger.Geib@telekom.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 E58E6129BA4; Thu, 29 Jun 2017 00:28:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level: 
X-Spam-Status: No, score=-4.32 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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=telekom.de
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1VOJfEHdC53U; Thu, 29 Jun 2017 00:28:29 -0700 (PDT)
Received: from mailout24.telekom.de (MAILOUT24.telekom.de [80.149.113.254]) (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 EDD0C129B29; Thu, 29 Jun 2017 00:28:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1498721308; x=1530257308; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=4P7gBvS/ULtALQo5dW+Kc9cVCyI2w4qAG9HA57Icw4o=; b=ys63nNMIMnlTWp7GxI3Dad7hIr5ESp1Ru28+orCwSKMOFWOlWQ3sf+2C joX966MScTEORvESeHRMt9SgPXIXYxY/tmQjj8D8bqGazYm5cloYE+GR0 2RMBtdnhu4YAlsJG308JktwMw3LQV+xbwuo5kNrxkaRttpewMQVKTRmI3 fK9XBuNyW1wf8RZWB9A7mrqFy5/sUh7Ms3HFCU3wIGsnzMJlCkK79xDYd ybUq37K1kHG3YCJpZEln9WMRPVYspvwbXtcDKOEU8sPvAymTy3hcz4nLE oIOPZhHjbJWfgDyCZ+fEkwhj9K2kAOdDx0XLeOJHJXCfh/+fq0W3ny0WI g==;
Received: from qde8e4.de.t-internal.com ([10.171.255.33]) by MAILOUT21.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2017 09:28:22 +0200
X-IronPort-AV: E=Sophos;i="5.40,279,1496095200"; d="scan'208";a="32032811"
Received: from he101655.emea1.cds.t-internal.com ([10.134.226.17]) by QDE8PP.de.t-internal.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2017 09:28:22 +0200
Received: from HE101653.emea1.cds.t-internal.com (10.134.226.13) by HE101655.emea1.cds.t-internal.com (10.134.226.17) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 29 Jun 2017 09:28:17 +0200
Received: from HE101653.emea1.cds.t-internal.com ([fe80::8954:80af:2020:572c]) by HE101653.emea1.cds.t-internal.com ([fe80::8954:80af:2020:572c%27]) with mapi id 15.00.1263.000; Thu, 29 Jun 2017 09:28:17 +0200
From: <Ruediger.Geib@telekom.de>
To: <presnick@qti.qualcomm.com>
CC: <spring@ietf.org>, <ietf@ietf.org>, <draft-ietf-spring-oam-usecase.all@ietf.org>, <gen-art@ietf.org>
Subject: AW: Genart last call review of draft-ietf-spring-oam-usecase-06
Thread-Topic: Genart last call review of draft-ietf-spring-oam-usecase-06
Thread-Index: AQHS8DzB9r68TQUb2kmPTiE6hAJfUqI7a1RQ
Date: Thu, 29 Jun 2017 07:28:17 +0000
Message-ID: <8d2d8cf3992b4b1fa96d5a755e5756ab@HE101653.emea1.cds.t-internal.com>
References: <149867468440.7527.6305996146978005032@ietfa.amsl.com>
In-Reply-To: <149867468440.7527.6305996146978005032@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.157.169.89]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/8An-XWYD_1CTbgwgbXhSCFlnL1U>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jun 2017 07:28:32 -0000

SGkgUGV0ZSwNCg0KdGhhbmtzIGZvciBwcm9wb3NpbmcgdG8gbWFrZSB0aGlzIGFuIEFwcGxpY2Fi
aWxpdHkgU3RhdGVtZW50LCBCQ1Agb3Igc3RhbmRhcmQuDQoNCkkgZG9uJ3Qgb2JqZWN0LCBidXQg
aWYgdGhlIHN0YXR1cyBvZiB0aGlzIGRyYWZ0IGlzIHN1cHBvc2VkIHRvIGJlIGNoYW5nZWQsIG15
IGNoYWlycyBhbmQgQUQgbmVlZCB0byBzdXBwb3J0IHRoaXMuIEJydW5vIGFuZCBBbHZhcm8sIHdo
YXQncyB5b3VyIHZpZXcgb24gUGV0ZSdzIHByb3Bvc2FsPyBXZSBtYXkgaGF2ZSB0byBpbnZlc3Qg
c29tZSBtb3JlIHRpbWUgYW5kIHRleHQgdGhlbi4gSSBwZXJzb25hbGx5IGRvbid0IG9iamVjdCB0
byAiaW5mb3JtYXRpb25hbCIgYXMgYW4gYWltLCBidXQgaWYgdGhhdCBtZWFucyByZW1vdmluZyBt
YWpvciBwYXJ0cyBvZiB0aGUgY29udGVudCwgSSdkIGJlIHJhdGhlciB1bmhhcHB5Lg0KDQpQZXRl
LCBhbHNvIEFsdmFybyBnYXZlIHVzIGEgcm91dGluZyBBRCByZXZpZXcgb24gRnJpZGF5LCAxNi4g
SnVuZSAoYW5kIGhlIGhhZCBjb21tZW50cykuIEJydW5vJ3Mgc2hlcGhhcmQgcmV2aWV3IGFzIHBh
cnQgb2YgdGhlIFdHIExhc3QgQ2FsbCByZXN1bHRlZCBpbiBiZXR0ZXIgc3RydWN0dXJpbmcgYW5k
IGRlZmluaXRpb25zIGluIHRoZSBkb2N1bWVudC4gU28gZmFyLCBubyBBRCBvciByZXZpZXdlciAi
dGVuZHMgdG8gaWdub3JlIFt0aGlzXSBJbmZvcm1hdGlvbmFsICJ1c2UgY2FzZSIgZG9jdW1lbnQi
LiBZb3XigJlyZSB0aGUgdGhpcmQgQUQgdG8gY29tbWVudCBhbmQgYXNrIGZvciBjaGFuZ2VzIChh
bmQgSSByZWNhbGwgdG8gaGF2ZSBoYWQgc2VyaW91cyBBRCBhbmQgSUVTRyByZXZpZXdzIHdpdGgg
b3RoZXIgaW5mb3JtYXRpb25hbHMpLg0KDQpSZWdhcmRzLA0KDQpSdWVkaWdlcg0KDQoNCi0tLS0t
VXJzcHLDvG5nbGljaGUgTmFjaHJpY2h0LS0tLS0NClZvbjogUGV0ZSBSZXNuaWNrIFttYWlsdG86
cHJlc25pY2tAcXRpLnF1YWxjb21tLmNvbV0gDQpHZXNlbmRldDogTWl0dHdvY2gsIDI4LiBKdW5p
IDIwMTcgMjA6MzENCkFuOiBnZW4tYXJ0QGlldGYub3JnDQpDYzogc3ByaW5nQGlldGYub3JnOyBp
ZXRmQGlldGYub3JnOyBkcmFmdC1pZXRmLXNwcmluZy1vYW0tdXNlY2FzZS5hbGxAaWV0Zi5vcmcN
CkJldHJlZmY6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtc3ByaW5nLW9h
bS11c2VjYXNlLTA2DQoNClJldmlld2VyOiBQZXRlIFJlc25pY2sNClJldmlldyByZXN1bHQ6IE5v
dCBSZWFkeQ0KDQpJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRy
YWZ0LiBUaGUgR2VuZXJhbCBBcmVhIFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJ
RVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENo
YWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZSBhbnkgb3RoZXIgbGFz
dCBjYWxsIGNvbW1lbnRzLg0KDQpGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUg
RkFRIGF0DQoNCjxodHRwczovL3RyYWMuaWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+
Lg0KDQpEb2N1bWVudDogZHJhZnQtaWV0Zi1zcHJpbmctb2FtLXVzZWNhc2UtMDYNClJldmlld2Vy
OiBQZXRlIFJlc25pY2sNClJldmlldyBEYXRlOiAyMDE3LTA2LTI4DQpJRVRGIExDIEVuZCBEYXRl
OiAyMDE3LTA2LTMwDQpJRVNHIFRlbGVjaGF0IGRhdGU6IE5vdCBzY2hlZHVsZWQgZm9yIGEgdGVs
ZWNoYXQNCg0KU3VtbWFyeTogTm90IFJlYWR5IGZvciBwdWJsaWNhdGlvbiBhcyBJbmZvcm1hdGlv
bmFsLCBidXQgbWlnaHQgYmUgUmVhZHkgZm9yIHB1YmxpY2F0aW9uIGFzIFByb3Bvc2VkIFN0YW5k
YXJkDQoNCk1ham9yIGlzc3VlczoNCg0KVGhpcyBpcyBhbiBhZG1pdHRlZGx5IHVudXN1YWwgcmV2
aWV3LiBJIGhhdmUgcmVhZCB0aHJvdWdoIHRoZSBlbnRpcmUgZG9jdW1lbnQsIGFuZCB0aGUgdGVj
aG5pY2FsIHdvcmsgc2VlbXMgZmluZSwgYnV0IGlzIHdlbGwgYmV5b25kIG15IHRlY2huaWNhbCBl
eHBlcnRpc2UsIHNvIEkgY2FuJ3QgcmVhbGx5IGNvbW1lbnQgb24gdGhlIHRlY2huaWNhbCBjb3Jy
ZWN0bmVzcy4gSG93ZXZlciwgaXQgaXMgYWJzb2x1dGVseSBjbGVhciB0byBtZSB0aGF0IHRoaXMg
aXMgKm5vdCogYSAidXNlIGNhc2UiIGRvY3VtZW50IGF0IGFsbCBhbmQgSSBkb24ndCB0aGluayBp
dCdzIGFwcHJvcHJpYXRlIGFzIGFuIEluZm9ybWF0aW9uYWwgZG9jdW1lbnQuIFRoaXMgaXMgY2xl
YXJseSBhDQoqc3BlY2lmaWNhdGlvbiogb2YgYSBwYXRoIG1vbml0b3Jpbmcgc3lzdGVtLiBJdCBn
aXZlcyBndWlkYW5jZXMgYXMgdG8gcmVxdWlyZWQsIHJlY29tbWVuZGVkLCBhbmQgb3B0aW9uYWwg
cGFyYW1ldGVycywgYW5kIHNwZWNpZmllcyBob3cgdG8gdXNlIGRpZmZlcmVudCBwcm90b2NvbCBw
aWVjZXMuIEl0IGlzIGF0IHRoZSB2ZXJ5IGxlYXN0IHdoYXQgUkZDIDIwMjYgcmVmZXJzIHRvIGFz
IGFuICJBcHBsaWNhYmlsaXR5IFN0YXRlbWVudCAoQVMpIiAoc2VlIFJGQyAyMDI2LCBzZWMuIDMu
MikuIEl0ICptaWdodCogYmUgYSBCQ1AsIGJ1dCBpdCBpcyBub3Qgc3RyaWN0bHkgZ2l2aW5nICJj
b21tb24gZ3VpZGVsaW5lcyBmb3IgcG9saWNpZXMgYW5kIG9wZXJhdGlvbnMiDQooMjAyNiwgc2Vj
LiA1KSwgc28gSSBkb24ndCByZWFsbHkgdGhpbmsgdGhhdCdzIHJpZ2h0LCBhbmQgaW5zdGVhZCB0
aGlzIHNob3VsZCBiZSBvZmZlcmVkIGZvciBQcm9wb3NlZCBTdGFuZGFyZC4gRWl0aGVyIHdheSwg
SSB0aGluayBJbmZvcm1hdGlvbmFsIGlzIG5vdCBjb3JyZWN0LiBJbXBvcnRhbnRseSwgSSB0aGlu
ayB0aGVyZSBpcyBhIGdvb2QgbGlrZWxpaG9vZCB0aGF0IHRoaXMgZG9jdW1lbnQgaGFzIG5vdCBy
ZWNlaXZlZCB0aGUgYXBwcm9wcmlhdGUgYW1vdW50IG9mIHJldmlldzsgcGVvcGxlIHRlbmQgdG8g
aWdub3JlIEluZm9ybWF0aW9uYWwgInVzZSBjYXNlIiBkb2N1bWVudHMsIGFuZCB0aGVyZSBoYXZl
IGJlZW4gbm8gTGFzdCBDYWxsIGNvbW1lbnRzIGJleW9uZCBKb2VsJ3MgUlRHIEFyZWEgUmV2aWV3
LiBFdmVuIGluIElFU0cgcmV2aWV3LCBhbiBJbmZvcm1hdGlvbmFsIGRvY3VtZW50IG9ubHkgdGFr
ZXMgdGhlIHNwb25zb3JpbmcgQUQgdG8gYXBwcm92ZTsgZXZlcnkgb3RoZXIgQUQgY2FuIHN1bW1h
cmlseSBpZ25vcmUgdGhlIGRvY3VtZW50LCBvciBldmVuIGJhbGxvdCBBQlNUQUlOLCBhbmQgdGhl
IGRvY3VtZW50IHdpbGwgc3RpbGwgYmUgcHVibGlzaGVkICh0aG91Z2ggdGhhdCBkb2VzIG5vdCBu
b3JtYWxseSBoYXBwZW4pLiBUaGlzIGRvY3VtZW50IHNob3VsZCBoYXZlIG11Y2ggbW9yZSB0aGFu
IHRoYXQgbGV2ZWwgb2YgcmV2aWV3LiBJIHN0cm9uZ2x5IHJlY29tbWVuZCB0byB0aGUgV0cgYW5k
IEFEIHRoYXQgdGhpcyBkb2N1bWVudCBiZSB3aXRoZHJhd24gYXMgYW4gSW5mb3JtYXRpb25hbCBk
b2N1bWVudCBhbmQgcmVzdWJtaXR0ZWQgZm9yIFByb3Bvc2VkIFN0YW5kYXJkIGFuZCBoYXZlIHRo
YXQgbGV2ZWwgb2YgcmV2aWV3IGFuZCBzY3J1dGlueSBhcHBsaWVkIHRvIGl0Lg0KDQpNaW5vciBp
c3N1ZXM6DQoNCk5vbmUuDQoNCk5pdHMvZWRpdG9yaWFsIGNvbW1lbnRzOg0KDQpUaGlzIGRvY3Vt
ZW50IHJlZmVycyB0byBSRkMgNDM3OSwgd2hpY2ggaGFzIGJlZW4gb2Jzb2xldGVkIGJ5IFJGQyA4
MDI5LiBJdCBzZWVtcyBsaWtlIHRoZSByZWZlcmVuY2VzIHNob3VsZCBiZSB1cGRhdGVkLg0KDQoN
Cg==


From nobody Thu Jun 29 00:33:19 2017
Return-Path: <prvs=346f6a78b=Ruediger.Geib@telekom.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 EF7AE128B8E; Thu, 29 Jun 2017 00:33:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.32
X-Spam-Level: 
X-Spam-Status: No, score=-4.32 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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=telekom.de
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A0B0RobvIEmz; Thu, 29 Jun 2017 00:33:15 -0700 (PDT)
Received: from mailout34.telekom.de (MAILOUT34.telekom.de [80.149.113.196]) (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 99D3B12706D; Thu, 29 Jun 2017 00:33:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1498721595; x=1530257595; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=dXgims0Cx5GKMPSx0/t50bXuJJip5yF9y8jCYqHUJbs=; b=tZq8fOkXCVrC5kxDxuqPhVwj8+1I3fTbVqaJx4tMLG7ReTfs5uc/MXJL GfBA5+/6/s+8z4dZaqdJupAEISVXWE5otKzxGaFv+13ogJF1v5O1mn/Hn tKxlgbGpZi86YWGnFkCrf6LAg1mVJBJY8v23tlFac4lgFmdYsGhmSz1U4 7ylxruXAD4swMjfV9+t+xpgeo5tUJgL2bAtYtFoXwx+dq8QwGP348ajfP IpmWW7KcuNLDPng+YeKfKlni8Osh8oOuNnLRI/ZTYXh/8+I2310Pf/Pq6 lsnyvPnhX7Kqh743N/CPqNgbxUpb2ENZSFVSkis+SGjQASjLfvw8nLv+i w==;
Received: from q4de8ssaz61.gppng.telekom.de ([10.206.166.200]) by MAILOUT31.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2017 09:33:07 +0200
X-IronPort-AV: E=Sophos;i="5.40,279,1496095200"; d="scan'208";a="1206321409"
Received: from he101659.emea1.cds.t-internal.com ([10.134.226.19]) by q4de8ssazdv.gppng.telekom.de with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 Jun 2017 09:33:04 +0200
Received: from HE101653.emea1.cds.t-internal.com (10.134.226.13) by HE101659.emea1.cds.t-internal.com (10.134.226.19) with Microsoft SMTP Server (TLS) id 15.0.1263.5; Thu, 29 Jun 2017 09:33:00 +0200
Received: from HE101653.emea1.cds.t-internal.com ([fe80::8954:80af:2020:572c]) by HE101653.emea1.cds.t-internal.com ([fe80::8954:80af:2020:572c%27]) with mapi id 15.00.1263.000; Thu, 29 Jun 2017 09:33:00 +0200
From: <Ruediger.Geib@telekom.de>
To: <jmh@joelhalpern.com>
CC: <spring@ietf.org>, <ietf@ietf.org>, <draft-ietf-spring-oam-usecase.all@ietf.org>, <rtg-dir@ietf.org>
Subject: AW: Rtgdir last call review of draft-ietf-spring-oam-usecase-06
Thread-Topic: Rtgdir last call review of draft-ietf-spring-oam-usecase-06
Thread-Index: AQHS61uWDtZ/bIkU00O8YkTSMd/hKKI7fDQA
Date: Thu, 29 Jun 2017 07:33:00 +0000
Message-ID: <6a3572d6034241099f9a3b73d1b5450f@HE101653.emea1.cds.t-internal.com>
References: <149813817013.30481.17524594111387704082@ietfa.amsl.com>
In-Reply-To: <149813817013.30481.17524594111387704082@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.157.169.89]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/MJH29Ree_RNyT5l5HetJUT9HLOs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jun 2017 07:33:18 -0000

SGkgSm9lbCwNCg0KdGhhbmtzIGZvciB5b3VyIHJldmlldy4gVGhlIGNvbW1lbnRzIG9mIHRoZSBk
cmFmdCBlZGl0b3JzIGFyZSBtYXJrZWQgW0VEXSBpbnNlcnRlZCBpbiB5b3VyIHRleHQgYmVsb3cu
DQoNClJlZ2FyZHMsDQoNClJ1ZWRpZ2VyDQoNCiMjIyMjIw0KDQpNaW5vcjoNCiAgICBbSkhdDQog
ICAgVGhlIGludHJvZHVjdGlvbiB0cmVhdHMgaGF2aW5nIGEgc2luZ2xlIGNlbnRyYWxpemVkIG1v
bml0b3Jpbmcgc3lzdGVtIGFzIGFuDQogICAgdW5hbGxveWVkIHBvc2l0aXZlLiAgVG8gc2V0IGNv
bnRleHQgcHJvcGVybHksIGl0IHdvdWxkIHNlZW0gbW9yZQ0KICAgIGFwcHJvcHJpYXRlIHRvIG5v
dGUgdGhhdCBtYW55IG9wZXJhdG9ycyBmaW5kIHN1Y2ggY2VudHJhbCBzeXN0ZW1zIHVzZWZ1bCwN
CiAgICBhbmQgdGhlIGFwcHJvYWNoIGRlc2NyaWJlZCBoZXJlIGVuYWJsZXMgdGhhdCB3aGVuIGRl
c2lyZWQuDQoNCltFRF0gSXMgdGhlIGZvbGxvd2luZyB0ZXh0IG9mIHRoZSBidWxsZXRlZCBsaXN0
IG9rIChpZiB5b3UgaGF2ZSBhIGJldHRlciB0ZXJtIHRoZW4gDQoibGFyZ2UiLCBwbGVhc2UgbGV0
IHVzIGtub3cpPyAgICAgIA0KICAgICAiLSBUaGUgc3lzdGVtIGRlc2NyaWJlZCBoZXJlIGFsbG93
cyB0byBzZXQgdXAgYW4gU1IgZG9tYWluIHdpZGUgY2VudHJhbGlzZWQgDQogICAgICBjb25uZWN0
aXZpdHkgdmFsaWRhdGlvbiwgd2hpY2ggaXMgdXNlZnVsIGluIGxhcmdlIG5ldHdvcmsgb3BlcmF0
b3IgZG9tYWlucy4iDQoNCiMjIyMjDQogICAgIFtKSF0NCiAgICBUaGUgcmVmZXJlbmNlIGluIHRo
ZSBpbnRyb2R1Y3Rpb24gdG8gSUdQIHRvcG9sb2d5IGRpc2NvdmVyeSBpcyB2ZXJ5DQogICAgY29u
ZnVzaW5nLiAiQWRkaW5nIE1QTFMgdG9wb2xvZ3kgYXdhcmVuZXNzIHRvIGFuIElHUCBzcGVha2lu
ZyBkZXZpY2UgaGVuY2UNCiAgICBlbmFibGVzIGEgc2ltcGxlIGFuZCBzY2FsYWJsZSBkYXRhIHBs
YW5lIGJhc2VkIG1vbml0b3JpbmcgbWVjaGFuaXNtLiIgIEFzDQogICAgbm90ZWQgbGF0ZXIgaW4g
dGhlIGRvY3VtZW50LCBsaW5rLXN0YXRlIElHUHMgcHJvdmlkZSB0b3BvbG9neSBhd2FyZW5lc3Mu
IA0KICAgIFNvIHdoYXQgaXMgdGhpcyBwYXJ0IG9mIHRoZSBpbnRyb2R1Y3Rpb24gdHJ5aW5nIHRv
IHNheT8gIChTaWRlLW5vdGUsIG5vdA0KICAgIGFsbCBJR1BzIGFyZSBsaW5rIHN0YXRlLCBhbHRo
b3VnaCB0aGUgYXBwbGljYWJpbGl0eSBvZiBCYWJlbCBvciBSSVAgdG8gTVBMUw0KICAgIFNlZ21l
bnQgUm91dGluZyBpcyBjbGVhcmx5IG91dHNpZGUgdGhlIHNjb3BlIG9mIHRoaXMgZG9jdW1lbnQu
KQ0KDQpbRURdIFRoYW5rcyBmb3IgcG9pbnRpbmcgb3V0LiBXZSBwcm9wb3NlIHRvIGNoYW5nZSB0
aGUgdGV4dCByZWZlcmVuY2UgYW5kICBsaW1pdCBzY29wZSB0byBsaW5rIHN0YXRlIElHUHM6ICAN
CiJUb3BvbG9neSBhd2FyZW5lc3MgaXMgYW4gaW1wb3J0YW50IGZlYXR1cmUgb2YgbGluayBzdGF0
ZSBJR1BzIGRlcGxveWVkIGJ5IG9wZXJhdG9ycyBvZiBsYXJnZSBuZXR3b3Jrcy4gTVBMUyB0b3Bv
bG9neSBhd2FyZW5lc3MgY29tYmluZWQgd2l0aCBJR1AgdG9wb2xvZ3kgYXdhcmVuZXNzIGVuYWJs
ZXMgYSBzaW1wbGUgYW5kIHNjYWxhYmxlIGRhdGEgcGxhbmUgYmFzZWQgbW9uaXRvcmluZyBtZWNo
YW5pc20uIg0KDQojIyMjIw0KDQogICAgW0pIXQ0KICAgIEluIHNlY3Rpb24gNS4xIGluIGRpc2N1
c3NpbmcgcGF0aCB0cmFjZSB0aGUgcmVmZXJlbmNlIGlzIHRvIFJGQyA0Mzc5IHdoaWNoDQogICAg
aXMgYSBjbGVhciBzb3VyY2UgZm9yIHBhdGggdHJhY2UuICBIb3dldmVyLCB0aGUgdGV4dCByZWZl
cnMgdG8gInRyZWUNCiAgICB0cmFjZSIuICBXaGlsZSB0aGF0IG1heSBoYXZlIGJlY29tZSBhIGNv
bW1vbiBwaHJhc2UgZm9yIHRoZSB1c2FnZSwgaXQgaXMNCiAgICBub3QgdXNlZCBpbiBSRkMgNDM3
OS4gIFRoZSB0ZXJtIHNob3VsZCBlaXRoZXIgYmUgZXhwbGFpbiwgaW5jbHVkZSBhDQogICAgc3Vp
dGFibGUgcmVmZXJlbmNlLCBvciBub3QgYmUgdXNlZC4NCg0KICAgIFtFRF0gV2lsbCByZXBsYWNl
ICJ0cmVlIHRyYWNlIiBieSBwYXRoIHRyYWNlLg0KDQojIyMjIw0KICAgW0pIXQ0KICAgSW4gc2Vj
dGlvbiA1LjMgb24gZmF1bHQgaXNvbGF0aW9uLCB0aGUgdGV4dCBub3RlcyB0aGF0IHRoZSBvbmx5
IGRpZmZlcmVuY2UNCiAgIGJldHdlZW4gdGhlIHRlc3Qgd2hpY2ggc3VjY2VlZHMgYW5kIHRoYXQg
d2hpY2ggZmFpbHMgaXMgdGhlIGRpZmZlcmVuY2UgdGhlDQogICB0aGUgYWRqYWNlbmN5IFNJRC4g
IFRoZSB0ZXh0IHRoZW4gZ29lcyBvbiB0byBzYXkgIkFzc3VtaW5nIHRoZSBzZWNvbmQgcHJvYmUN
CiAgIGhhcyBiZWVuIHJvdXRlZCBjb3JyZWN0bHksIHRoZSBmYXVsdCBtdXN0IGhhdmUgYmVlbiBv
Y2N1cnJpbmcgaW4gUjIgd2hpY2gNCiAgIGRpZG4ndCBmb3J3YXJkIHRoZSBwYWNrZXQgdG8gdGhl
IGludGVyZmFjZSBpZGVudGlmaWVkIGJ5IGl0cyBBZGphY2VuY3kgU0lEDQogICA2NjMuIiAgVGhh
dCBkb2VzIG5vdCBmb2xsb3cuICBJZiB0aGUgbGluayBhcyBmYWlsZWQgaW4gYW4gdW5kZXRlY3Rl
ZCBmYXNoaW9uDQogICAoZWl0aGVyIGluIG9uZSBkaXJlY3Rpb24gb3IgYm90aCksIFIyIHdvdWxk
IGJlIGZ1bmN0aW9uaW5nIGZpbmUgYW5kIHRoZQ0KICAgc3ltcHRvbSB3b3VsZCBiZSB0aGUgc2Ft
ZS4gIFJlbW90ZWx5IGRldGVjdGluZyB0aGUgZGlmZmVyZW5jZSBiZXR3ZWVuIFIyDQogICBmYWls
aW5nIHRvIGZvcndhcmQgYW5kIHRoZSBsaW5rIG5vdCB3b3JraW5nIHNlZW1zIGEgbXVjaCBoYXJk
ZXIgdGFzay4NCg0KW0VEXSBZZXMsIGxpbmsgb3Igcm91dGVyIGNhbiBiZSBmYXVsdHkuIFdoYXQg
YWJvdXQ6DQoiLi4udGhlIGZhdWx0IGlzIHRoYXQgZm9yIHNvbWUgKHBvc3NpYmx5IHVua25vd24p
IHJlYXNvbiBTUiBwYWNrZXRzIHRvIGJlIGZvcndhcmRlZCBmcm9tIFIyIHZpYSB0aGUgaW50ZXJm
YWNlIGlkZW50aWZpZWQgYnkgQWRqYWNlbmN5IFNJRCA2NjMgYXJlIGxvc3QuIg0KDQojIyMjIw0K
ICAgIFtKSF0NCiAgICBUaGUgY2xhaW0gdGhhdCB0aGUgUE1TIGNhbiAvIHNob3VsZCAoaW50ZW50
IGlzIGFtYmlndW91cykgbm90aWZ5IHRoZSByb3V0ZXINCiAgICB3aGVuIGl0IGRldGVjdHMgYSBw
YXRoIGZhaWx1cmUgcmFpc2VzIGEgbnVtYmVyIG9mIGlzc3Vlcy4gICBJdCBpcyBub3QgYXQNCiAg
ICBhbGwgY2xlYXIgd2hhdCB0aGUgcm91dGVyIHdvdWxkIGRvIHdpdGggdGhlIG5vdGlmaWNhdGlv
bi4gIChlLmcuIElmIGl0DQogICAgcmVtb3ZlZCB0aGUgbGluayBmcm9tIHNlcnZpY2UsIHRoZW4g
ZnV0dXJlIG1vbml0b3Jpbmcgd291bGQgbm90IGJlIGFibGUgdG8NCiAgICBkZXRlY3QgdGhhdCB0
aGUgbGluayB3YXMgd29ya2luZy4pICBFaXRoZXIgdGhpcyBuZWVkcyB0byBiZWNvbWUgYQ0KICAg
IHNpZ25pZmljYW50bHkgbGFyZ2VyIHNlY3Rpb24sIG9yIChtb3JlIGxpa2VseSkgdGhlIHRleHQg
bmVlZHMgdG8gYmUgcmVtb3ZlZC4NCg0KW0VEXSBZb3VyIGNvbW1lbnQgaGl0cyB0aGUgcG9pbnQu
IFByaW9yIHRvIHJlbW92aW5nIGl0LCBJJ2QgbGlrZSB0byBvZmZlciBhIGNoYW5nZSAoYnV0IG1h
eSB3b3JkIGl0IG5vdCB3ZWxsIGFuZCBJIHVuZm9ydHVuYXRlbHkgY2FuJ3QgY2hlY2sgdGV4dCB3
aXRoIG15IG9wZXJhdGlvbmFsIGRlcGFydG1lbnQgZm9yIHRoZSBjb21pbmcgd2Vla3MgLSB2YWNh
dGlvbiBzZWFzb24gaGFzIHN0YXJ0ZWQpLg0KDQpbRURdIExldCdzIGNhbGwgdGhlIHN5bXB0b20g
Im5vdCB3b3JraW5nIGZvcndhcmRpbmciLiBXZSBrbm93LCB0aGF0IGl0IG9jY3Vycy4gSWYgdGhl
cmUgaXMgb25lIGNvdW50ZXItbWVhc3VyZSB3aGljaCBvZnRlbiB3b3JrcyBhbmQgaGFzIHByb3Bl
cnRpZXMgYWxsb3dpbmcgYXV0b21hdGVkIGV4ZWN1dGlvbiAoaS5lLiB0aGUgc2l0dWF0aW9uIGNh
bid0IGRldGVyaW9yYXRlLCBpZiBhIHNvbHV0aW9uIGlzIGV4ZWN1dGVkIGF1dG9tYXRpY2FsbHkp
LCAiYXV0b21hdGlvbiIgbWF5IGFsc28gYmUgcHJvcG9zZWQgaGVyZSAoYnV0IG5vIGRpc2N1c3Np
b24gb2Ygc29sdXRpb24gZGV0YWlscywgcmF0aGVyIGEgbGltaXRlZCBudW1iZXIgb2YgZ2VuZXJh
bCByZXF1aXJlbWVudHMpLiBJZiB0aGUgdGV4dCBiZWxvdyBpcyB1c2VmdWwsIHdlIHNob3VsZCBr
ZWVwIGl0LCBidXQgSSB3aWxsIG5vdCBmaWdodCBmb3IgaXQgaW4gdGhlIGRyYWZ0OiANCg0KW0VE
XQ0KIlBhdGggVHJhY2UgYW5kIEZhaWx1cmUgTm90aWZpY2F0aW9uDQoNClNvbWV0aW1lcyBmb3J3
YXJkaW5nIGFsb25nIGEgc2luZ2xlIHBhdGggaW5kZWVkIGRvZXNuJ3Qgd29yaywgd2hpbGUgdGhl
IGNvbnRyb2wgcGxhbmUgaW5mb3JtYXRpb24gaXMgaGVhbHRoeS4gU3VjaCBhIHNpdHVhdGlvbiBt
YXkgb2NjdXIgYWZ0ZXIgbWFpbnRlbmFuY2Ugd29yayB3aXRoaW4gYSBkb21haW4uDQpBbiBvcGVy
YXRvciBtYXkgcGVyZm9ybSBvbiBkZW1hbmQtdGVzdHMsIGJ1dCBleGVjdXRpb24gb2YgYXV0b21h
dGVkIFBNUyBwYXRoIHRyYWNlIGNoZWNrcyBtYXkgYmUgc2V0IHVwIHRvbyAoc2NvcGUgbWF5IGJl
IGxpbWl0ZWQgdG8gYSBzdWJzZXQgb2YgaW1wb3J0YW50IGVuZC10by1lbmQgcGF0aHMgY3Jvc3Np
bmcgdGhlIHJvdXRlciBvciBuZXR3b3JrIHNlY3Rpb24gYWZ0ZXIgY29tcGxldGlvbiBvZiB0aGUg
bWFpbnRlbmFuY2Ugd29yayB0aGVyZSkuIFVwb24gZGV0ZWN0aW9uIG9mIGEgcGF0aCB3aGljaCBj
YW4ndCBiZSB1c2VkLCB0aGUgb3BlcmF0b3IgbmVlZHMgdG8gYmUgbm90aWZpZWQuIEEgY2hlY2sg
ZW5zdXJpbmcgdGhhdCByZS1yb3V0aW5nIGV2ZW50IGlzIGRpZmZlcmVkIGZyb20gYSBwYXRoIGZh
Y2luZyB3aG9zZSBmb3J3YXJkaW5nIGJlaGF2aW9yIGRvZXNuJ3QgY29ycmVzcG9uZCB0byB0aGUg
Y29udHJvbCBwbGFuZSBpbmZvcm1hdGlvbiBpcyBuZWNlc3NhcnkgKGJ1dCBvdXQgb2Ygc2NvcGUg
b2YgdGhpcyBkb2N1bWVudCkuDQoNCkFkZGluZyBhbiBhdXRvbWF0ZWQgcHJvYmxlbSBzb2x1dGlv
biB0byB0aGUgUE1TIGZlYXR1cmVzIG9ubHkgbWFrZXMgc2Vuc2UsIGlmIHRoZSByb290IGNhdXNl
IG9mIHRoZSBzeW1wdG9tIGFwcGVhcnMgb2Z0ZW4sIGNhbiBiZSBhc3N1bWVkIHRvIGJlIG5vbi0g
YW1iaWd1b3VzIGJ5IGl0cyBzeW1wdG9tcywgY2FuIGJlIHNvbHZlZCBieSBhIHByZS1kZXRlcm1p
bmVkIGNoYWluIG9mIGNvbW1hbmRzIGFuZCB0aGUgYXV0b21hdGVkIFBNUyByZWFjdGlvbiBub3Qg
ZG9pbmcgYW55IGNvbGxhdGVyYWwgZGFtYWdlLiBBIGNsb3NlciBhbmFseXNpcyBpcyBvdXQgb2Yg
c2NvcGUgb2YgdGhpcyBkb2N1bWVudC4NCg0KVGhlIFBNUyBpcyBleHBlY3RlZCB0byBjaGVjayBj
b250cm9sIHBsYW5lIGxpdmVsaW5lc3MgYWZ0ZXIgYSBwYXRoIHJlcGFpciBlZmZvcnQgd2FzIGV4
ZWN1dGVkLiBJdCBkb2Vzbid0IG1hdHRlciB3aGV0aGVyIHRoZSBwYXRoIHJlcGFpciB3YXMgdHJp
Z2dlcmVkIG1hbnVhbGx5IG9yIGJ5IGFuIGF1dG9tYXRlZCBzeXN0ZW0uIg0KDQojIyMjIyMjIyMj
IyMNCg0KW0pIXSBFZGl0b3JpYWw6DQogICAgQ2hhcHRlciA3IGlzIHRpdGxlZCBkZWFsaW5nIHdp
dGggbm9uLVNSIGVudmlyb25tZW50cy4gIFdoaWNoIG1ha2VzIHNlbnNlLiANCiAgICBUaGUgdGV4
dCB0aGVuIHN3aXRjaGVzIHRvIHVzaW5nICJwcmUtU1IiIGluc3RlYWQgb2YgIm5vbi1TUiIuICBJ
IHdvdWxkDQogICAgcmVjb21tZW5kIHRoYXQgYWxsIHVzZXMgb2YgInByZS1TUiIgYmUgY2hhbmdl
ZCB0byAibm9uLVNSIi4NCg0KW0VEXSBPSywgd2lsbCBiZSBkb25lIGluIG5leHQgcHVibGlzaGVk
IHZlcnNpb24uDQoNCi0tLS0tVXJzcHLDvG5nbGljaGUgTmFjaHJpY2h0LS0tLS0NClZvbjogSm9l
bCBIYWxwZXJuIFttYWlsdG86am1oQGpvZWxoYWxwZXJuLmNvbV0gDQpHZXNlbmRldDogRG9ubmVy
c3RhZywgMjIuIEp1bmkgMjAxNyAxNTozMA0KQW46IHJ0Zy1kaXJAaWV0Zi5vcmcNCkNjOiBzcHJp
bmdAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtc3ByaW5nLW9hbS11c2VjYXNl
LmFsbEBpZXRmLm9yZw0KQmV0cmVmZjogUnRnZGlyIGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQt
aWV0Zi1zcHJpbmctb2FtLXVzZWNhc2UtMDYNCg0KUmV2aWV3ZXI6IEpvZWwgSGFscGVybg0KUmV2
aWV3IHJlc3VsdDogSGFzIE5pdHMNCg0KVGhpcyBpcyBhIHJ0Zy1kaXIgcmVxdWVzdGVkIHJldmll
dy4NCg0KU3VtbWFyeTogUmVhZHkgZm9yIHB1YmxpY2F0aW9uIGFzIGFuIEluZm9ybWF0aW9uYWwg
UkZDIHdpdGggc29tZSBtaW5vciBpdGVtcyB0aGF0IHNob3VsZCBiZSBjb25zaWRlcmVkLg0KDQpN
YWpvcjogTi9BDQoNCk1pbm9yOg0KICAgIFRoZSBpbnRyb2R1Y3Rpb24gdHJlYXRzIGhhdmluZyBh
IHNpbmdsZSBjZW50cmFsaXplZCBtb25pdG9yaW5nIHN5c3RlbSBhcyBhbg0KICAgIHVuYWxsb3ll
ZCBwb3NpdGl2ZS4gIFRvIHNldCBjb250ZXh0IHByb3Blcmx5LCBpdCB3b3VsZCBzZWVtIG1vcmUN
CiAgICBhcHByb3ByaWF0ZSB0byBub3RlIHRoYXQgbWFueSBvcGVyYXRvcnMgZmluZCBzdWNoIGNl
bnRyYWwgc3lzdGVtcyB1c2VmdWwsDQogICAgYW5kIHRoZSBhcHByb2FjaCBkZXNjcmliZWQgaGVy
ZSBlbmFibGVzIHRoYXQgd2hlbiBkZXNpcmVkLg0KDQogICAgVGhlIHJlZmVyZW5jZSBpbiB0aGUg
aW50cm9kdWN0aW9uIHRvIElHUCB0b3BvbG9neSBkaXNjb3ZlcnkgaXMgdmVyeQ0KICAgIGNvbmZ1
c2luZy4gIkFkZGluZyBNUExTIHRvcG9sb2d5IGF3YXJlbmVzcyB0byBhbiBJR1Agc3BlYWtpbmcg
ZGV2aWNlIGhlbmNlDQogICAgZW5hYmxlcyBhIHNpbXBsZSBhbmQgc2NhbGFibGUgZGF0YSBwbGFu
ZSBiYXNlZCBtb25pdG9yaW5nIG1lY2hhbmlzbS4iICBBcw0KICAgIG5vdGVkIGxhdGVyIGluIHRo
ZSBkb2N1bWVudCwgbGluay1zdGF0ZSBJR1BzIHByb3ZpZGUgdG9wb2xvZ3kgYXdhcmVuZXNzLiAN
CiAgICBTbyB3aGF0IGlzIHRoaXMgcGFydCBvZiB0aGUgaW50cm9kdWN0aW9uIHRyeWluZyB0byBz
YXk/ICAoU2lkZS1ub3RlLCBub3QNCiAgICBhbGwgSUdQcyBhcmUgbGluayBzdGF0ZSwgYWx0aG91
Z2ggdGhlIGFwcGxpY2FiaWxpdHkgb2YgQmFiZWwgb3IgUklQIHRvIE1QTFMNCiAgICBTZWdtZW50
IFJvdXRpbmcgaXMgY2xlYXJseSBvdXRzaWRlIHRoZSBzY29wZSBvZiB0aGlzIGRvY3VtZW50LikN
Cg0KICAgIEluIHNlY3Rpb24gNS4xIGluIGRpc2N1c3NpbmcgcGF0aCB0cmFjZSB0aGUgcmVmZXJl
bmNlIGlzIHRvIFJGQyA0Mzc5IHdoaWNoDQogICAgaXMgYSBjbGVhciBzb3VyY2UgZm9yIHBhdGgg
dHJhY2UuICBIb3dldmVyLCB0aGUgdGV4dCByZWZlcnMgdG8gInRyZWUNCiAgICB0cmFjZSIuICBX
aGlsZSB0aGF0IG1heSBoYXZlIGJlY29tZSBhIGNvbW1vbiBwaHJhc2UgZm9yIHRoZSB1c2FnZSwg
aXQgaXMNCiAgICBub3QgdXNlZCBpbiBSRkMgNDM3OS4gIFRoZSB0ZXJtIHNob3VsZCBlaXRoZXIg
YmUgZXhwbGFpbiwgaW5jbHVkZSBhDQogICAgc3VpdGFibGUgcmVmZXJlbmNlLCBvciBub3QgYmUg
dXNlZC4NCg0KICAgSW4gc2VjdGlvbiA1LjMgb24gZmF1bHQgaXNvbGF0aW9uLCB0aGUgdGV4dCBu
b3RlcyB0aGF0IHRoZSBvbmx5IGRpZmZlcmVuY2UNCiAgIGJldHdlZW4gdGhlIHRlc3Qgd2hpY2gg
c3VjY2VlZHMgYW5kIHRoYXQgd2hpY2ggZmFpbHMgaXMgdGhlIGRpZmZlcmVuY2UgdGhlDQogICB0
aGUgYWRqYWNlbmN5IFNJRC4gIFRoZSB0ZXh0IHRoZW4gZ29lcyBvbiB0byBzYXkgIkFzc3VtaW5n
IHRoZSBzZWNvbmQgcHJvYmUNCiAgIGhhcyBiZWVuIHJvdXRlZCBjb3JyZWN0bHksIHRoZSBmYXVs
dCBtdXN0IGhhdmUgYmVlbiBvY2N1cnJpbmcgaW4gUjIgd2hpY2gNCiAgIGRpZG4ndCBmb3J3YXJk
IHRoZSBwYWNrZXQgdG8gdGhlIGludGVyZmFjZSBpZGVudGlmaWVkIGJ5IGl0cyBBZGphY2VuY3kg
U0lEDQogICA2NjMuIiAgVGhhdCBkb2VzIG5vdCBmb2xsb3cuICBJZiB0aGUgbGluayBhcyBmYWls
ZWQgaW4gYW4gdW5kZXRlY3RlZCBmYXNoaW9uDQogICAoZWl0aGVyIGluIG9uZSBkaXJlY3Rpb24g
b3IgYm90aCksIFIyIHdvdWxkIGJlIGZ1bmN0aW9uaW5nIGZpbmUgYW5kIHRoZQ0KICAgc3ltcHRv
bSB3b3VsZCBiZSB0aGUgc2FtZS4gIFJlbW90ZWx5IGRldGVjdGluZyB0aGUgZGlmZmVyZW5jZSBi
ZXR3ZWVuIFIyDQogICBmYWlsaW5nIHRvIGZvcndhcmQgYW5kIHRoZSBsaW5rIG5vdCB3b3JraW5n
IHNlZW1zIGEgbXVjaCBoYXJkZXIgdGFzay4NCg0KICAgIFRoZSBjbGFpbSB0aGF0IHRoZSBQTVMg
Y2FuIC8gc2hvdWxkIChpbnRlbnQgaXMgYW1iaWd1b3VzKSBub3RpZnkgdGhlIHJvdXRlcg0KICAg
IHdoZW4gaXQgZGV0ZWN0cyBhIHBhdGggZmFpbHVyZSByYWlzZXMgYSBudW1iZXIgb2YgaXNzdWVz
LiAgIEl0IGlzIG5vdCBhdA0KICAgIGFsbCBjbGVhciB3aGF0IHRoZSByb3V0ZXIgd291bGQgZG8g
d2l0aCB0aGUgbm90aWZpY2F0aW9uLiAgKGUuZy4gSWYgaXQNCiAgICByZW1vdmVkIHRoZSBsaW5r
IGZyb20gc2VydmljZSwgdGhlbiBmdXR1cmUgbW9uaXRvcmluZyB3b3VsZCBub3QgYmUgYWJsZSB0
bw0KICAgIGRldGVjdCB0aGF0IHRoZSBsaW5rIHdhcyB3b3JraW5nLikgIEVpdGhlciB0aGlzIG5l
ZWRzIHRvIGJlY29tZSBhDQogICAgc2lnbmlmaWNhbnRseSBsYXJnZXIgc2VjdGlvbiwgb3IgKG1v
cmUgbGlrZWx5KSB0aGUgdGV4dCBuZWVkcyB0byBiZSByZW1vdmVkLg0KDQpFZGl0b3JpYWw6DQog
ICAgQ2hhcHRlciA3IGlzIHRpdGxlZCBkZWFsaW5nIHdpdGggbm9uLVNSIGVudmlyb25tZW50cy4g
IFdoaWNoIG1ha2VzIHNlbnNlLiANCiAgICBUaGUgdGV4dCB0aGVuIHN3aXRjaGVzIHRvIHVzaW5n
ICJwcmUtU1IiIGluc3RlYWQgb2YgIm5vbi1TUiIuICBJIHdvdWxkDQogICAgcmVjb21tZW5kIHRo
YXQgYWxsIHVzZXMgb2YgInByZS1TUiIgYmUgY2hhbmdlZCB0byAibm9uLVNSIi4NCg0K


From nobody Thu Jun 29 01:50:56 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 8F75012ECBA; Thu, 29 Jun 2017 01:50:41 -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 PMMTSUfUni2B; Thu, 29 Jun 2017 01:50:39 -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 780CC12ECB7; Thu, 29 Jun 2017 01:50:39 -0700 (PDT)
Received: by mail-wr0-x242.google.com with SMTP id z45so36295626wrb.2; Thu, 29 Jun 2017 01:50:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=to:cc:from:subject:message-id:date:user-agent:mime-version :content-language; bh=ESk3ySkqEj005jJJy4hBXIOzjgz3B+cnr4Kr5kBvBxo=; b=VSqgzYVcV+A8jnqfwYmYlLFak2zJxkne+xecxZs7SZ3BYX5J41+UBEI3NWba9Pu4A5 IwdgnNYJuZ6OS2Ns1XxYWHhWJMF+MGJVlUo4kedrANKQnMnZ9LLByUtmWfD2ff2pehQT KUyi3UeVNDtL3TA4n3jaU2grG60RB9nuaWWNNXIzYILvLOVAD01xDxH5TTyqKbZVrc9a Xox6xNcy1AFr9RmyIQgQGtIxDTqLyn4UqF7QXqmXNW3yqbd8FPkk1JySxDXUhFLEZ9O3 o/H1Sk7UBQa/XGdqdH4yBZI93u6v3zDL0/bOB0N4iLsOD1kddpQHEAr1BFpV8Lbzvdfc hs1w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:to:cc:from:subject:message-id:date:user-agent :mime-version:content-language; bh=ESk3ySkqEj005jJJy4hBXIOzjgz3B+cnr4Kr5kBvBxo=; b=BeAlE10RtqrA2qTfBxIarx0o8dMnIbmsb7xakbBXdh7yqj77TMzdvWS3N1BLymmfc3 bb8apOJrqWx48TGKk0WofbIH3bzbDvfxycfItq8pBtYm21NTjolQa18kZMhHO+jXN3da h2z6kpDdUKS30gaMtuftn6AuUYjjjxL5wUEykCHDfjw26PCwNHOJYp1OY65zormtpma1 THkglpU9/y10CtE81bXGTuM5CqHtfX+bd/VBoQUOgJuvKw6nmuBFYzciOBz0/jT3cBdc giXPOFmnNkWL7DpD7saVtmh8fgKoxrIzPMd4UAVsGbvd2+LTT1i8OblvgLSKs0Qhmc2b /xEw==
X-Gm-Message-State: AKS2vOzmra33DUCs/5C2Vs7Bq2Lv45CplZqpoAVBJbvuIN0+7k03bHHu CXaPPpRN46w7DjKQ0n0=
X-Received: by 10.223.139.87 with SMTP id v23mr21380889wra.145.1498726237689;  Thu, 29 Jun 2017 01:50:37 -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 i65sm710382wmf.20.2017.06.29.01.50.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Jun 2017 01:50:37 -0700 (PDT)
To: d3e3e3@gmail.com
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-trill-rbridge-multilevel.all@ietf.org, IETF Discussion <ietf@ietf.org>, trill@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Subject: Re: [trill] Genart last call review of draft-ietf-trill-rbridge-multilevel-06
Message-ID: <58bdb2db-3833-feaa-ced0-eeee68ca5581@gmail.com>
Date: Thu, 29 Jun 2017 09:50:34 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------BF40CDDA72214BF8EEC99F56"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tasS6SKhFYYtmEZgOdOja3v5QuM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jun 2017 08:50:42 -0000

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

>                     Although there is some discussion on it later there is no discussion
> of the number of addresses to be learned in the single and multi-area cases and
> the impact this has on the LSDB. The number of addresses to be learned will
> impact the ingress RBridge FIB and the FIB update time so this is just as
> significant in understanding the benefit of multi-level as understanding the
> link-state convergence time is.

The number of MAC (actually MAC/VLAN or MAC/FGL) addresses to be
learned by an edge TRILL switch is not affected by whether the TRILL
campus uses single or multilevel IS-IS. This number of MAC address
learned is the seventh scaling problem listed in Section 1.1 which
states that multilevel TRILL IS-IS helps only with the other six
problems. This point, that multilevel doesn't help here, could be
emphasized more but I don't think I see much point in this document in
going into details such as the scaling considerations of data plane
MAC address learning (which is the default in TRILL) or control plan
MAC address learning (which does not use the core LSDB but rather Data
Label scoped ESADI link stat databases).

SB> I think the important point is either to demonstrate that the
SB> that the control plane problem you address is the dominant factor in convergence
SB> and that the MAC component (including FIB update) is not significant,
SB> or to point to a solution that makes the data plane element comparable
SB> to the improved control plane. Otherwise there is surely no point in
SB> making these significant changes to the control plane.

- Stewart



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

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <pre class="wordwrap" style="box-sizing: border-box; overflow: auto; font-family: Menlo, Monaco, Consolas, &quot;Courier New&quot;, monospace; font-size: 13px; display: block; padding: 0px; margin: 0px 0px 10px; line-height: 1.42857; word-break: normal; word-wrap: normal; color: rgb(51, 51, 51); background-color: white; border: 0px none black; border-radius: 4px; white-space: pre-wrap; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-style: initial; text-decoration-color: initial;">&gt;                     Although there is some discussion on it later there is no discussion
&gt; of the number of addresses to be learned in the single and multi-area cases and
&gt; the impact this has on the LSDB. The number of addresses to be learned will
&gt; impact the ingress RBridge FIB and the FIB update time so this is just as
&gt; significant in understanding the benefit of multi-level as understanding the
&gt; link-state convergence time is.

The number of MAC (actually MAC/VLAN or MAC/FGL) addresses to be
learned by an edge TRILL switch is not affected by whether the TRILL
campus uses single or multilevel IS-IS. This number of MAC address
learned is the seventh scaling problem listed in Section 1.1 which
states that multilevel TRILL IS-IS helps only with the other six
problems. This point, that multilevel doesn't help here, could be
emphasized more but I don't think I see much point in this document in
going into details such as the scaling considerations of data plane
MAC address learning (which is the default in TRILL) or control plan
MAC address learning (which does not use the core LSDB but rather Data
Label scoped ESADI link stat databases).

SB&gt; I think the important point is either to demonstrate that the
SB&gt; that the control plane problem you address is the dominant factor in convergence
SB&gt; and that the MAC component (including FIB update) is not significant,
SB&gt; or to point to a solution that makes the data plane element comparable
SB&gt; to the improved control plane. Otherwise there is surely no point in 
SB&gt; making these significant changes to the control plane.

- Stewart


</pre>
  </body>
</html>

--------------BF40CDDA72214BF8EEC99F56--


From nobody Thu Jun 29 07:54:10 2017
Return-Path: <pierrick.seite@orange.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BA4A131459; Thu, 29 Jun 2017 07:54:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.399
X-Spam-Level: 
X-Spam-Status: No, score=-5.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-2.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, 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 WlkrollBfksC; Thu, 29 Jun 2017 07:54:00 -0700 (PDT)
Received: from relais-inet.orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B779129AB8; Thu, 29 Jun 2017 07:54:00 -0700 (PDT)
Received: from opfedar05.francetelecom.fr (unknown [xx.xx.xx.7]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id E21B116048B; Thu, 29 Jun 2017 16:53:58 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.59]) by opfedar05.francetelecom.fr (ESMTP service) with ESMTP id BEA226006C; Thu, 29 Jun 2017 16:53:58 +0200 (CEST)
Received: from OPEXCLILM22.corporate.adroot.infra.ftgroup ([fe80::8c90:f4e9:be28:2a1]) by OPEXCLILM43.corporate.adroot.infra.ftgroup ([fe80::ec23:902:c31f:731c%19]) with mapi id 14.03.0352.000; Thu, 29 Jun 2017 16:53:58 +0200
From: <pierrick.seite@orange.com>
To: Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "dmm@ietf.org" <dmm@ietf.org>, "draft-ietf-dmm-mag-multihoming.all@ietf.org" <draft-ietf-dmm-mag-multihoming.all@ietf.org>
Subject: RE: Genart last call review of draft-ietf-dmm-mag-multihoming-03
Thread-Topic: Genart last call review of draft-ietf-dmm-mag-multihoming-03
Thread-Index: AQHS5UQUB4/g2YtYp0GhFtYMb97BHKI8AQUw
Date: Thu, 29 Jun 2017 14:53:57 +0000
Message-ID: <9066_1498748038_59551486_9066_325_1_81C77F07008CA24F9783A98CFD706F713AA75926@OPEXCLILM22.corporate.adroot.infra.ftgroup>
References: <149746836602.14035.16572809666065484300@ietfa.amsl.com>
In-Reply-To: <149746836602.14035.16572809666065484300@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.168.234.1]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/i9lKvWmMJVDBqQ0kDKfR-PPcyDo>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jun 2017 14:54:03 -0000

SGVsbG8sDQoNClRoYW5rcyBmb3IgdGhlIHJldmlldzsgcGxlYXNlIGZpbmQgYmVsb3cgY2xhcmlm
aWNhdGlvbnMgYW5kIGFuc3dlcnMuIFdlIHdpbGwgdXBkYXRlIHRoZSBkb2N1bWVudCBhY2NvcmRp
bmdseS4NCg0KUmVnYXJkcywNCg0KPiAtLS0tLU1lc3NhZ2UgZCdvcmlnaW5lLS0tLS0NCj4gRGUg
OiBSb2JlcnQgU3BhcmtzIFttYWlsdG86cmpzcGFya3NAbm9zdHJ1bS5jb21dDQo+IEVudm95w6kg
OiBtZXJjcmVkaSAxNCBqdWluIDIwMTcgMjE6MjYNCj4gw4AgOiBnZW4tYXJ0QGlldGYub3JnDQo+
IENjIDogaWV0ZkBpZXRmLm9yZzsgZG1tQGlldGYub3JnOyBkcmFmdC1pZXRmLWRtbS1tYWctbXVs
dGlob21pbmcuYWxsQGlldGYub3JnDQo+IE9iamV0IDogR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcg
b2YgZHJhZnQtaWV0Zi1kbW0tbWFnLW11bHRpaG9taW5nLTAzDQo+DQo+IFJldmlld2VyOiBSb2Jl
cnQgU3BhcmtzDQo+IFJldmlldyByZXN1bHQ6IE5vdCBSZWFkeQ0KPg0KPiBJIGFtIHRoZSBhc3Np
Z25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhIFJl
dmlldyBUZWFtDQo+IChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBw
cm9jZXNzZWQgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGDQo+IENoYWlyLiAgUGxlYXNlIHRyZWF0
IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLg0K
Pg0KPiBGb3IgbW9yZSBpbmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQo+DQo+IDxo
dHRwczovL3RyYWMuaWV0Zi5vcmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KPg0KPiBEb2N1
bWVudDogZHJhZnQtaWV0Zi1kbW0tbWFnLW11bHRpaG9taW5nLTAzDQo+IFJldmlld2VyOiBSb2Jl
cnQgU3BhcmtzDQo+IFJldmlldyBEYXRlOiAyMDE3LTA2LTE0DQo+IElFVEYgTEMgRW5kIERhdGU6
IDIwMTctMDYtMTYNCj4gSUVTRyBUZWxlY2hhdCBkYXRlOiBOb3Qgc2NoZWR1bGVkIGZvciBhIHRl
bGVjaGF0DQo+DQo+IFN1bW1hcnk6IE5vdCBSZWFkeQ0KPg0KPiBUaGlzIGRvY3VtZW50IGhhcyBz
ZXZlcmFsIGlzc3VlcyB0aGF0IG5lZWQgdG8gYmUgYWRkcmVzc2VkIGJlZm9yZSBwdWJsaWNhdGlv
biBhcw0KPiBhIHByb3Bvc2VkIHN0YW5kYXJkLg0KPg0KPiAxKSBUaGUgZG9jdW1lbnQgZGVmaW5l
cyBzb21lIHdpcmUgc3ludGF4LCBidXQgZG9lcyBub3QgZGVmaW5lIChvciByZWZpbmUpIHRoZQ0K
PiBwcm90b2NvbCBmb3IgdXNpbmcgdGhlc2UgYml0cyBvZiB3aXJlIHN5bnRheC4gRm9yIGluc3Rh
bmNlLCB0aGUgZG9jdW1lbnQgZG9lcyBub3QNCj4gZGlzY3VzcyBpZi93aGVuIHRoZSBNQUcgSWRl
bnRpZmllciBPcHRpb24gaXMgbmVjZXNzYXJ5LiBJdCBkb2VzIG5vdCBkaXNjdXNzIHdoZW4NCj4g
dGhlIG5ldyBlcnJvciBjb2RlIGl0IGRlZmluZXMgc2hvdWxkIGJlIHNlbnQsIG5vciB3aGF0IGEg
cmVjaXBpZW50IHNob3VsZCBkbyBpZiBpdA0KPiByZWNlaXZlcyB0aGF0IGVycm9yIGNvZGUgKEkg
d291bGQgaGF2ZSBleHBlY3RlZCBkaXNjdXNzaW9uIHNpbWlsYXIgdG8gc29tZSBvZiB0aGUNCj4g
cGFyYWdyYXBocyBpbiBzZWN0aW9ucyA1LjQuMS4yIGFuZCA2LjkuMS4yIG9mIFJGQzUyMTMpLg0K
Pg0KDQo+IEZvciBpbnN0YW5jZSwgdGhlIGRvY3VtZW50IGRvZXMgbm90IGRpc2N1c3MgaWYvd2hl
biB0aGUgTUFHIElkZW50aWZpZXIgT3B0aW9uIGlzIG5lY2Vzc2FyeS4NCg0KVGhlIGZvbGxvd2lu
ZyB0ZXh0IGNvdmVycyB0aGF0IGFzcGVjdDoNCg0KIlRoZSBNQUcgTXVsdGlwYXRoLUJpbmRpbmcg
b3B0aW9uIGlzIGEgbmV3IG1vYmlsaXR5IGhlYWRlciBvcHRpb24NCmRlZmluZWQgZm9yIHVzZSB3
aXRoIFByb3h5IEJpbmRpbmcgVXBkYXRlIGFuZCBQcm94eSBCaW5kaW5nDQpBY2tub3dsZWRnZW1l
bnQgbWVzc2FnZXMgZXhjaGFuZ2VkIGJldHdlZW4gdGhlIGxvY2FsIG1vYmlsaXR5IGFuY2hvcg0K
YW5kIHRoZSBtb2JpbGUgYWNjZXNzIGdhdGV3YXkuDQoNClRoaXMgbW9iaWxpdHkgaGVhZGVyIG9w
dGlvbiBpcyB1c2VkIGZvciByZXF1ZXN0aW5nIG11bHRpcGF0aCBzdXBwb3J0Lg0KSXQgaW5kaWNh
dGVzIHRoYXQgdGhlIG1vYmlsZSBhY2Nlc3MgZ2F0ZXdheSBpcyByZXF1ZXN0aW5nIHRoZSBsb2Nh
bA0KbW9iaWxpdHkgYW5jaG9yIHRvIHJlZ2lzdGVyIHRoZSBjdXJyZW50IGNhcmUtb2YgYWRkcmVz
cyBhc3NvY2lhdGVkDQp3aXRoIHRoZSByZXF1ZXN0IGFzIG9uZSBvZiB0aGUgbWFueSBjYXJlLWFk
ZHJlc3NlcyB0aHJvdWdoIHdoaWNoIHRoZQ0KbW9iaWxlIGFjY2VzcyBnYXRld2F5IGNhbiBiZSBy
ZWFjaGVkLiAgSXQgaXMgYWxzbyBmb3IgY2FycnlpbmcgdGhlDQppbmZvcm1hdGlvbiByZWxhdGVk
IHRvIHRoZSBhY2Nlc3MgbmV0d29yayBhc3NvY2lhdGVkIHdpdGggdGhlIGNhcmUtb2YNClRoZSBN
QUcgTXVsdGlwYXRoLUJpbmRpbmcgb3B0aW9uIGhhcyBhbiBhbGlnbm1lbnQgcmVxdWlyZW1lbnQg
b2YNCiA4bisyLiAgSXRzIGZvcm1hdCBpcyBhcyBzaG93biBpbiBGaWd1cmUgMzrigJ0NCg0KPiAg
SXQgZG9lcyBub3QgZGlzY3VzcyB3aGVuIHRoZSBuZXcgZXJyb3IgY29kZSBpdCBkZWZpbmVzIHNo
b3VsZCBiZSBzZW50LCBub3Igd2hhdCBhIHJlY2lwaWVudCBzaG91bGQgZG8gaWYgaXQgcmVjZWl2
ZXMgdGhhdCBlcnJvciBjb2RlIChJIHdvdWxkIGhhdmUgZXhwZWN0ZWQgZGlzY3Vzc2lvbiBzaW1p
bGFyIHRvIHNvbWUgb2YgdGhlIHBhcmFncmFwaHMgaW4gc2VjdGlvbnMgNS40LjEuMiBhbmQgNi45
LjEuMiBvZiBSRkM1MjEzKS4NCg0KUmVhc29ucyBmb3IgdGhlIExNQSB0byBzZW5kIGVycm9yIGNv
ZGUgYXJlIGFzIGZvbGxvd3MNCg0KLSBUaGUgTE1BIGRvZXMgbm90IHN1cHBvcnQgbXVsdGlwbGUg
Y2FyZS1vZi1hZGRyZXNzIHJlZ2lzdHJhdGlvbg0KLSBhIGJpbmRpbmcgZW50cnkgd2l0aCB0aGUg
cmVxdWVzdGVkIENhcmUtb2YtYWRkcmVzcyBhbHJlYWR5IGV4aXN0DQoNCldlIHdpbGwgY2xhcmlm
eSB0aGlzIHBvaW50IGFuZCBleHBlY3RpbmcgTUFHIGJlaGF2aW9yIGFzIHdlbGwuDQoNCg0KDQo+
IDIpIFRoZXJlIGFyZSBzZW50ZW5jZSBmcmFnbWVudHMgdGhhdCBpbmRpY2F0ZSBpbmZvcm1hdGlv
biB3YXMgbG9zdCBhdCBzb21lIHBvaW50IGluDQo+IGVkaXRpbmcuDQo+DQo+ICAgICAtICJJbiB0
aGUgY29udGludWF0aW9uIG9mIGMsIGEgUHJveHkiIDogd2hhdCBzaG91bGQgaGF2ZSBiZWVuIHdo
ZXJlIHRoZSAnYycNCj4gICAgICAgaXM/DQo+DQo+ICAgICAtICJvciBhdCBXaGVuIG9wZXJhdGlu
ZyIgOiBUaGlzIGxvb2tzIGEgY2xhdXNlIChhbmQgdGhlIGVuZCBvZiBhIHNlbnRlbmNlKQ0KPiAg
ICAgICB3YXMgbG9zdCBhZnRlciAnb3IgYXQnLiAnV2hlbiBvcGVyYXRpbmcnIGlzIGNsZWFybHkg
c3RhcnRpbmcgYSBuZXcNCj4gICAgICAgc2VudGVuY2UuDQo+DQo+DQoNCkZyb20gdmVyc2lvbjE6
DQoNCiAgIEluIHRoZSBjb250aW51YXRpb24gb2YgW1JGQzQ5MDhdLCBhIFByb3h5IE1vYmlsZSBJ
UHY2IFtSRkM1MjEzXSBiYXNlZCBtdWx0aSBob21lZCBhY2hpdGVjdHVyZSBjb3VsZCBiZSBkZWZp
bmVkLg0KDQoNCldlIGNhbiBkZWxldGUgdGhpcyBzZW50ZW5jZSBhcyB0aGUgbmV4dCBzZW50ZW5j
ZSBjb3ZlcnMgdGhpcyBwb2ludC4NCg0KPiBOaXRzOg0KPg0KPiAqIEhvdyBhcmUgUHJlZmVyZW5j
ZSBTZXR0aW5ncyBlaXRoZXIgYSBnb2FsIG9yIGEgYmVuZWZpdD8gSXQgc2VlbXMgb3V0IG9mDQo+
ICAgcGxhY2UgaW4gdGhlIGxpc3QuDQo+DQoNCk9uZSBtYXkgcHJlZmVyIG9uZSBhY2Nlc3MgbmV0
d29yayBvdmVyIG90aGVyLiBFeGFtcGxlOiBVc2UgV2ktRmkgd2hlbiBpdHMgYXZhaWxhYmxlIGFu
ZCBkbyBub3QgdXNlIExURS4gT25lIGNhbiBleHRlbmQgdGhpcyBmdXJ0aGVyIGFuZCBwcm92aWRl
IHByZWZlcmVuY2Ugc2V0dGluZ3MgdGhhdCBhbGxvdyBWb2ljZSB0cmFmZmljIHRvIGdvIG9ubHkg
b3ZlciBMVEUuDQoNCj4gKiBhdCAibGV2ZXJhZ2Ugb24gbGF0ZXN0IiBkbyB5b3UgbWVhbiAibGV2
ZXJhZ2UgdGhlIGxhdGVzdCI/DQo+DQoNCk9MRDoNClRoZSBtb3RpdmF0aW9uIHRvIHVwZGF0ZSBb
UkZDNDkwOF0gIHdpdGggcHJveHkgTW9iaWxlIElQdjYgaXMgdG8gbGV2ZXJhZ2Ugb24gbGF0ZXN0
IG1vYmlsaXR5IHdvcmtpbmcgZ3JvdXAgYWNoaWV2ZW1lbnRzLCBuYW1lbHk6DQoNCk5FVzoNClRo
ZSBtb3RpdmF0aW9uIGZvciB0aGlzIHdvcmsgaXMgdG8gZXh0ZW5kIFByb3h5IE1vYmlsZSBJUHY2
IHByb3RvY29sIHdpdGggbXVsdGlob21pbmcgZXh0ZW5zaW9ucyBbUkZDNDkwOF0gYW5kIHJlYWxp
emUgdGhlIGZvbGxvd2luZyBjYXBhYmlsaXRpZXM6DQoNCg0KPiAqIGF0ICJhbGxvd2luZyB0byBt
YWtlIGFwcHJvcHJpYXRlIHRyYWZmaWMgc3RlZXJpbmcgZGVjaXNpb24iLCBfd2hhdF8gYXJlIHlv
dQ0KPiAgIGFsbG93aW5nIHRvIG1ha2UgYSBkZWNpc2lvbiAod2hvIGlzIHRoZSBhY3Rvcik/DQo+
DQo+ICogJ0ZvciBleGFtcGxlLCB0aGUgb3BlcmF0b3IgbWF5IGhhdmUgcG9saWN5IHdoaWNoIGJp
bmRzIHRyYWZmaWMgZm9yDQo+ICAgIEFwcGxpY2F0aW9uICJYIiBuZWVkcyB0byBpbnRlcmZhY2Ug
d2l0aCBMYWJlbCAiWSIuJyBkb2VzIG5vdCBtYWtlIHNlbnNlLg0KPiAgICBJcyB0aGUgd29yZCAi
bmVlZHMiIGV4dHJhbmVvdXM/DQo+DQo+ICogVGhlIGxhc3Qgc2VudGVuY2UgaW4gdGhlIGRlZmlu
aXRpb24gb2YgdGhlIEJpbmRpbmctSWRlbnRpZmllciBhcHBlYXJzIHRvIGJlDQo+ICAgZGVzY3Jp
YmluZyB0aGUgSW50ZXJmYWNlIExhYmVsLg0KPg0KDQpJbnRlcmZhY2UgbGFiZWwgaXMgYSBkZXNj
cmlwdGl2ZSBzdHJpbmcuIEJpbmRpbmcgaWRlbnRpZmllciBpcyBhbiBpZGVudGlmaWVyIGZvciB0
aGUgYmluZGluZy4gRWFjaCBCaW5kaW5nICBpcyB0aWVkIHRvIGFuIGludGVyZmFjZSBvbiB0aGUg
TUFHLg0KDQogICAgICBUaGlzIDgtYml0IGZpZWxkIGlzIHVzZWQgZm9yIGNhcnJ5aW5nIHRoZSBi
aW5kaW5nIGlkZW50aWZpZXIuICBJdA0KICAgICAgdW5pcXVlbHkgaWRlbnRpZmllcyBhIHNwZWNp
ZmljIGJpbmRpbmcgb2YgdGhlIG1vYmlsZSBub2RlLCB0bw0KICAgICAgd2hpY2ggdGhpcyByZXF1
ZXN0IGNhbiBiZSBhc3NvY2lhdGVkLiAgRWFjaCBiaW5kaW5nIGlkZW50aWZpZXIgaXMNCiAgICAg
IHJlcHJlc2VudGVkIGFzIGFuIHVuc2lnbmVkIGludGVnZXIuICBUaGUgcGVybWl0dGVkIHZhbHVl
cyBhcmUgMQ0KICAgICAgdGhyb3VnaCAyNTQuICBUaGUgQklEIHZhbHVlIG9mIDAgYW5kIDI1NSBh
cmUgcmVzZXJ2ZWQuICBUaGUgbW9iaWxlDQogICAgICBhY2Nlc3MgZ2F0ZXdheSBhc3NpZ25zIGEg
dW5pcXVlIHZhbHVlIGZvciBlYWNoIG9mIGl0cyBpbnRlcmZhY2VzDQogICAgICBhbmQgaW5jbHVk
ZXMgdGhlbSBpbiB0aGUgbWVzc2FnZS4NCg0KPiAqIFNvbWV0aGluZyBpcyBtaXNzaW5nIGF0ICJh
bmQgZWl0aGVyIGJhc2VkIG9uIiBpbiB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMNCj4gICBz
ZWN0aW9uLg0KPg0KT0xEOg0KICAgVGhpcyBlc3NlbnRpYWxseSBhbGxvd3MgdGhlIG1vYmlsZSBu
b2RlJ3MgSVAgdHJhZmZpYyB0byBiZQ0KICAgcm91dGVkIHRocm91Z2ggYW55IG9mIHRoZSB0dW5u
ZWwgcGF0aHMgYW5kIGVpdGhlciBiYXNlZCBvbiBhIHN0YXRpYw0KICAgb3IgYSBkeW5hbWljYWxs
eSBuZWdvdGlhdGVkIGZsb3cgcG9saWN5Lg0KDQpORVc6DQoNCiAgIFRoaXMgZXNzZW50aWFsbHkg
YWxsb3dzIHRoZSBtb2JpbGUgbm9kZSdzIElQIHRyYWZmaWMgdG8gYmUNCiAgIHJvdXRlZCB0aHJv
dWdoIGFueSBvZiB0aGUgdHVubmVsIHBhdGhzLCBiYXNlZCBvbiBhIHN0YXRpYw0KICAgb3IgYSBk
eW5hbWljYWxseSBuZWdvdGlhdGVkIGZsb3cgcG9saWN5Lg0KDQo+ICogQ29uc2lkZXIgdXNpbmcg
UkZDODE3NCBpbnN0ZWFkIG9mIFJGQzIxMTkNCj4NCg0KT0sNCg0KCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KCkNlIG1lc3Nh
Z2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQgY29udGVuaXIgZGVzIGluZm9ybWF0aW9u
cyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRvaXZlbnQgZG9uYwpwYXMg
ZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5zIGF1dG9yaXNhdGlvbi4gU2kg
dm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2ZXVpbGxleiBsZSBzaWduYWxl
cgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUgbGVzIHBpZWNlcyBqb2lu
dGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBldGFudCBzdXNjZXB0aWJsZXMgZCdhbHRl
cmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNwb25zYWJpbGl0ZSBzaSBjZSBtZXNzYWdl
IGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVyY2kuCgpUaGlzIG1lc3NhZ2Ug
YW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRpYWwgb3IgcHJpdmlsZWdl
ZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkgbGF3Owp0aGV5IHNob3VsZCBu
b3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhvdXQgYXV0aG9yaXNhdGlvbi4K
SWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciwgcGxlYXNlIG5vdGlmeSB0
aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBpdHMgYXR0YWNobWVudHMuCkFz
IGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFibGUgZm9yIG1lc3NhZ2Vz
IHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNpZmllZC4KVGhhbmsgeW91
LgoK


From nobody Thu Jun 29 08:46:44 2017
Return-Path: <tonysietf@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 DEE0112EC2C; Thu, 29 Jun 2017 08:46:35 -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 u9dfyMR0LKCd; Thu, 29 Jun 2017 08:46:33 -0700 (PDT)
Received: from mail-wm0-x22d.google.com (mail-wm0-x22d.google.com [IPv6:2a00:1450:400c:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0E26129B09; Thu, 29 Jun 2017 08:46:32 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id b184so19208946wme.1; Thu, 29 Jun 2017 08:46:32 -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=EVNOJ64IHfTg6zGmzvF0dr2gspWHTSxQjBK51arzKeM=; b=Qa8NbQg8m3kcUSn8dxyvQzhN14igeO0SQggGu+UNy9Yjuqw/6N0q9IlsoX/Qr8mbvX aovar6Wija5+BvoJL84AdA4VSRKNuOgKfwGiiedySnjKnJJUSDy27+Xlh1Y7iwVWESQz 2Y17xr74tqrRp3hxt+swP89eB3Z+Ecmoomb6aOOavUSp8HB9iKZUHy6N4VcmMFRCXWGA 2U4AfblfTXJNE6+O60x5f1S2Y43vc9ijc0x2jNDVU5FggpnkEIQGx3tk8oMQ4O7A68Nk 7ymSUR7euKwNbg6u704NUjeG2pRWbBn8EEjjZQrG1NJpcUu094KbWAepbL9pV4IOrFi+ dfFQ==
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=EVNOJ64IHfTg6zGmzvF0dr2gspWHTSxQjBK51arzKeM=; b=KlxvadoUhdQgmn3wa7ONm1MGl9y/ONGbDT/1+wNjcqciGtityLbUDv8M8Hwjj9/+Tw LmmE/VzRiZydoH52cUra6D+S9Q1QXjbuUSOQYOw6P9Y19Li1yk6emJXVcP63lcZeYTMD aw01dm9AMc2C77Knu4/Q9ax8YCdl75N5vAD+1C5cAf4wMDN1A0rKN2p5mM8gCJdvdgH1 ncoZ1ZyTBMsGQLgjMoC6J6il782V+47EoS17jEKQswCLoCS0YdbhjZycuwNVpzRwxuln fzpaQ6lRIqmYyKKWSf3M4eZ6lRG3iZGk6qmkGUTO1tewwt8tPCFt1j53u/An/NghjNfl BDrw==
X-Gm-Message-State: AKS2vOwe5qoEPqP4UfE7ZWBT6p/AWWr8skaKyesPEBRXNPpoPC3xnyx/ 4hhanf97vafbCXqcFZ2XtU4XIKDgoQ==
X-Received: by 10.80.178.166 with SMTP id p35mr2241060edd.118.1498751191231; Thu, 29 Jun 2017 08:46:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.183.131 with HTTP; Thu, 29 Jun 2017 08:45:50 -0700 (PDT)
In-Reply-To: <7d872d02-4154-989d-e83d-4d7408cc6073@juniper.net>
References: <149838804788.3251.829139224134758886@ietfa.amsl.com> <7d872d02-4154-989d-e83d-4d7408cc6073@juniper.net>
From: Tony Przygienda <tonysietf@gmail.com>
Date: Thu, 29 Jun 2017 08:45:50 -0700
Message-ID: <CA+wi2hPVp_z3CNaD7M2Bw+ihFZzmyh+x3U+1O1X66jsuyhX6kQ@mail.gmail.com>
Subject: Re: [Bier] Genart last call review of draft-ietf-bier-architecture-07
To: Eric C Rosen <erosen@juniper.net>
Cc: Dan Romascanu <dromasca@gmail.com>, gen-art@ietf.org, "bier@ietf.org" <bier@ietf.org>, ietf@ietf.org,  draft-ietf-bier-architecture.all@ietf.org
Content-Type: multipart/alternative; boundary="f403045c8a025c36ef05531b34ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/hq5c4vOdUUrfkRK0HszaoJYbzc8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jun 2017 15:46:36 -0000

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

I picked up shepherd of this doc. Will reply by end of week to Dan's,
Eric's comments ...

thanks

-- tony

On Tue, Jun 27, 2017 at 7:42 AM, Eric C Rosen <erosen@juniper.net> wrote:

> On 6/25/2017 6:54 AM, Dan Romascanu wrote:
>
> 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> <https://trac.ietf.org/tr=
ac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-bier-architecture-?
> ?
> Reviewer: Dan Romascanu
> Review Date: 2017-06-25
> IETF LC End Date: 2017-06-29
> IESG Telechat date: 2017-07-06
>
> Summary:
>
> This document specifies a new architecture known as "Bit Index Explicit
> Replication" (BIER) for the forwarding of multicast data packets through =
a
> "multicast domain".  It does not require a protocol for explicitly buildi=
ng
> multicast distribution trees, nor does it require intermediate nodes to
> maintain any per-flow state. This architecture is .  While the Abstract a=
nd
> Introduction of the document mentions Architecture as the principal scope=
, this
> document goes well beyond the scope of a typical architectural document.
> including detailed definitions of the procedures, terminology and normati=
ve
> algorithms required for BIER.
>
> The document is clear and detailed. Because of its structure, I am missin=
g some
> information that usually can be found in architecture documents. I includ=
ed
> these in the 'minor issues' list. Although none of these may be a show-st=
opper,
> I believe that addressing these before document approval can improve the
> quality of the document and of the overall BIER work.
>
> Major issues:
>
> Minor issues:
>
> 1. As the document is targeting 'Experimental' it would be useful to ment=
ion
> what is the scope of the experiment.The charter actually says:
>
> ' The scope of the experiment will be
> documented in the output of the Working Group.'
>
> Would not the Architecture document be the right place for this? If not, =
is
> there another document that deals or is planned to define the scope of th=
e
> experiment?
>
>
> I don't really know what is meant by "the experiment" or "scope of the
> experiment", but I'm pretty sure it is not relevant to the architecture (=
or
> to the forwarding rules).
>
> I don't know if there is another document discussing "scope of the
> experiment", or if such a document is actually needed.  That would be a
> question for the WG chairs.
>
> 2. While the Abstract and Introduction of the document mentions Architect=
ure as
> the principal scope, this document is different from a typical architectu=
ral
> document. While it defines well the procedures, terminology and normative
> algorithms required for BIER Intra-domain forwarding, it goes well beyond=
 the
> level of detail that other similar documents go. Specifications of the
> procedures and normative algorithm should be mentioned in Abstract and
> Introduction, they occupy the same or more space than architecture.
>
>
> I can add a few sentences to the abstract and introduction to make it
> clear that the procedures for fowarding BIER packets within a BIER domain
> specified in this document.
>
> 3. On the other hand I am missing the relationship with other work items =
in the
> BIER charter - there is no manageability section for example, there is no
> reference to the performance impact in networks. Maybe these are dealt wi=
th in
> a different document or documents or BIER, if so it would be good at leas=
t to
> mention and reference these here.
>
>
> There is no requirement to include a manageability section.
>
> I believe there is ongoing work having to do with Operations and
> Management of BIER, but as that does not help to understand the
> architecture (or forwarding procedures), I don't think it would be
> appropriate to reference that work.
>
> With regard to the performance impact, if the question is speed of
> forwarding, there is mention of the fact that the number of lookups neede=
d
> to forward a BIER packet is on the order of the number of neighbors.   I
> don't know what else can really be said at this level of detail, as the
> actual forwarding performance will depend a great deal on the
> implementation.  I'm not worried too much about that, because if BIER
> implementations do not perform well, the technology will not catch on.
>
> 4. I also would have expected the architecture document to refer the use =
cases
> document and note which of the use cases are being addressed and how -
> draft-ietf-bier-use-cases is not even included in the references.
>
>
> I don't see any reason why the architecture document should reference the
> "use cases" document.  An explanation of how to apply the architecture to
> each use case is not within the scope of the architecture document.
>
> 5. Sections 3 to 6 mentioned repeatedly provisioning. As there is no Oper=
ations
> and Manageability section as in many other Routing Area documents, it is =
not
> clear how this is expected to happen.
>
>
> How OAM is "expected to happen" would be outside the scope of this
> document.
>
> For example draft-ietf-bier-bier-yang is
> not mentioned or referred. I suggest adding a note (and maybe references)=
 for
> clarity.
>
>
> I don't see any reason to reference that document.
>
> 6. In section 8 I found:
>
> 'Every BFR must be provisioned to know which of its interfaces lead to
>    a BIER domain and which do not.  If two interfaces lead to different
>    BIER domains, the BFR must be provisioned to know that those two
>    interfaces lead to different BIER domains. '
>
> It seems that the two 'must' in these sentences would rather be capitaliz=
ed.
>
>
>
>
> I will make that change.
>
>
> _______________________________________________
> BIER mailing list
> BIER@ietf.org
> https://www.ietf.org/mailman/listinfo/bier
>
>


--=20
*We=E2=80=99ve heard that a million monkeys at a million keyboards could pr=
oduce
the complete works of Shakespeare; now, thanks to the Internet, we know
that is not true.*
=E2=80=94Robert Wilensky

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

<div dir=3D"ltr">I picked up shepherd of this doc. Will reply by end of wee=
k to Dan&#39;s, Eric&#39;s comments ...=C2=A0<div><br></div><div>thanks=C2=
=A0</div><div><br></div><div>-- tony=C2=A0</div></div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">On Tue, Jun 27, 2017 at 7:42 AM, Eric =
C Rosen <span dir=3D"ltr">&lt;<a href=3D"mailto:erosen@juniper.net" target=
=3D"_blank">erosen@juniper.net</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">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF"><div><div class=3D"h5">
    On 6/25/2017 6:54 AM, Dan Romascanu wrote:<br>
    </div></div><blockquote type=3D"cite">
      <pre><div><div class=3D"h5">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

<a class=3D"m_6427245500128914782moz-txt-link-rfc2396E" href=3D"https://tra=
c.ietf.org/trac/gen/wiki/GenArtfaq" target=3D"_blank">&lt;https://trac.ietf=
.org/trac/<wbr>gen/wiki/GenArtfaq&gt;</a>.

Document: draft-ietf-bier-architecture-?<wbr></div></div>?
Reviewer: Dan Romascanu
Review Date: 2017-06-25
IETF LC End Date: 2017-06-29
IESG Telechat date: 2017-07-06

Summary:

This document specifies a new architecture known as &quot;Bit Index Explici=
t
Replication&quot; (BIER) for the forwarding of multicast data packets throu=
gh a
&quot;multicast domain&quot;.  It does not require a protocol for explicitl=
y building
multicast distribution trees, nor does it require intermediate nodes to
maintain any per-flow state. This architecture is .  While the Abstract and
Introduction of the document mentions Architecture as the principal scope, =
this
document goes well beyond the scope of a typical architectural document.
including detailed definitions of the procedures, terminology and normative
algorithms required for BIER.

The document is clear and detailed. Because of its structure, I am missing =
some
information that usually can be found in architecture documents. I included
these in the &#39;minor issues&#39; list. Although none of these may be a s=
how-stopper,
I believe that addressing these before document approval can improve the
quality of the document and of the overall BIER work.

Major issues:

Minor issues:

1. As the document is targeting &#39;Experimental&#39; it would be useful t=
o mention
what is the scope of the experiment.The charter actually says:

&#39; The scope of the experiment will be
documented in the output of the Working Group.&#39;

Would not the Architecture document be the right place for this? If not, is
there another document that deals or is planned to define the scope of the
experiment?</pre>
    </blockquote>
    <br>
    I don&#39;t really know what is meant by &quot;the experiment&quot; or =
&quot;scope of
    the experiment&quot;, but I&#39;m pretty sure it is not relevant to the
    architecture (or to the forwarding rules).<br>
    <br>
    I don&#39;t know if there is another document discussing &quot;scope of=
 the
    experiment&quot;, or if such a document is actually needed.=C2=A0 That =
would
    be a question for the WG chairs.<span class=3D""><br>
    <br>
    <blockquote type=3D"cite">
      <pre>2. While the Abstract and Introduction of the document mentions =
Architecture as
the principal scope, this document is different from a typical architectura=
l
document. While it defines well the procedures, terminology and normative
algorithms required for BIER Intra-domain forwarding, it goes well beyond t=
he
level of detail that other similar documents go. Specifications of the
procedures and normative algorithm should be mentioned in Abstract and
Introduction, they occupy the same or more space than architecture.</pre>
    </blockquote>
    <br></span>
    I can add a few sentences to the abstract and introduction to make
    it clear that the procedures for fowarding BIER packets within a
    BIER domain specified in this document.=C2=A0 <br><span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <pre>3. On the other hand I am missing the relationship with other wo=
rk items in the
BIER charter - there is no manageability section for example, there is no
reference to the performance impact in networks. Maybe these are dealt with=
 in
a different document or documents or BIER, if so it would be good at least =
to
mention and reference these here.</pre>
    </blockquote>
    <br></span>
    There is no requirement to include a manageability section.<br>
    <br>
    I believe there is ongoing work having to do with Operations and
    Management of BIER, but as that does not help to understand the
    architecture (or forwarding procedures), I don&#39;t think it would be
    appropriate to reference that work.<br>
    <br>
    With regard to the performance impact, if the question is speed of
    forwarding, there is mention of the fact that the number of lookups
    needed to forward a BIER packet is on the order of the number of
    neighbors.=C2=A0=C2=A0 I don&#39;t know what else can really be said at=
 this level
    of detail, as the actual forwarding performance will depend a great
    deal on the implementation.=C2=A0 I&#39;m not worried too much about th=
at,
    because if BIER implementations do not perform well, the technology
    will not catch on.<span class=3D""><br>
    <br>
    <blockquote type=3D"cite">
      <pre>4. I also would have expected the architecture document to refer=
 the use cases
document and note which of the use cases are being addressed and how -
draft-ietf-bier-use-cases is not even included in the references.</pre>
    </blockquote>
    <br></span>
    I don&#39;t see any reason why the architecture document should
    reference the &quot;use cases&quot; document.=C2=A0 An explanation of h=
ow to apply
    the architecture to each use case is not within the scope of the
    architecture document.=C2=A0 <br><span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <pre>5. Sections 3 to 6 mentioned repeatedly provisioning. As there i=
s no Operations
and Manageability section as in many other Routing Area documents, it is no=
t
clear how this is expected to happen. </pre>
    </blockquote>
    <br></span>
    How OAM is &quot;expected to happen&quot; would be outside the scope of=
 this
    document. <br><span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <pre>For example draft-ietf-bier-bier-yang is
not mentioned or referred. I suggest adding a note (and maybe references) f=
or
clarity.</pre>
    </blockquote>
    <br></span>
    I don&#39;t see any reason to reference that document.=C2=A0 <br><span =
class=3D"">
    <br>
    <blockquote type=3D"cite">
      <pre>6. In section 8 I found:

&#39;Every BFR must be provisioned to know which of its interfaces lead to
   a BIER domain and which do not.  If two interfaces lead to different
   BIER domains, the BFR must be provisioned to know that those two
   interfaces lead to different BIER domains. &#39;

It seems that the two &#39;must&#39; in these sentences would rather be cap=
italized.


</pre>
    </blockquote>
    <br></span>
    I will make that change.<br>
    <br>
  </div>

<br>______________________________<wbr>_________________<br>
BIER mailing list<br>
<a href=3D"mailto:BIER@ietf.org">BIER@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/bier" rel=3D"noreferrer" t=
arget=3D"_blank">https://www.ietf.org/mailman/<wbr>listinfo/bier</a><br>
<br></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br><div cla=
ss=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">=
<div><span style=3D"font-size:12.8000001907349px"><font face=3D"georgia, se=
rif"><i>We=E2=80=99ve heard that a million monkeys at a million keyboards c=
ould produce the complete works of Shakespeare; now, thanks to the Internet=
, we know that is not true.</i></font></span><i><font face=3D"garamond, ser=
if"><br></font></i></div><div><span style=3D"font-size:12.8000001907349px">=
<font face=3D"times new roman, serif">=E2=80=94Robert Wilensky</font></span=
><br></div></div></div>
</div>

--f403045c8a025c36ef05531b34ad--


From nobody Thu Jun 29 09:22:57 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 4128B131493; Thu, 29 Jun 2017 09:22:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level: 
X-Spam-Status: No, score=-7.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=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 2_OGQiha7WbO; Thu, 29 Jun 2017 09:22:46 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) (using TLSv1.2 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC537129B4B; Thu, 29 Jun 2017 09:22:45 -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=1498753365; x=1530289365; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=pHueH/mzARtFnoyOwXEKPX0jJXXQvfh91jJMW+7BJbE=; b=K38tHC6RkWLD8TIsN5wI4YkPp+LqmaH0l63LlFh7Iua7INcddJ5P/QQJ jfnN6lOi7oacGwuG+PptQgprjZn6wt2YQvfoCNw0rfpwbriVth/W8yefK cPP4LAdlCd0b0uUR00O8iBoYSmBWJq8YZkkLhJDRwJpwOE+kaVs6/6lqc U=;
X-IronPort-AV: E=Sophos;i="5.40,281,1496127600"; d="scan'208";a="110468504"
Received: from unknown (HELO ironmsg02-R.qualcomm.com) ([10.53.140.106]) by sabertooth02.qualcomm.com with ESMTP; 29 Jun 2017 09:22:44 -0700
X-IronPort-AV: E=McAfee;i="5800,7501,8576"; a="989871297"
X-MGA-submission: =?us-ascii?q?MDGO88aiUPR8rPx05tOuLagkMqsK1KW6h0rLZG?= =?us-ascii?q?oT27UKLVZaROfXiR5PFRWav2mH27eaLLh9KF1lxn55IAeV//6QL9UQh2?= =?us-ascii?q?jR8TwZaVrpxfcUtsrpim7Ye0vTbu3W+g2eSZTpIHbohkW72g/XTTP1y3?= =?us-ascii?q?6N?=
Received: from nasanexm01f.na.qualcomm.com ([10.85.0.32]) by ironmsg02-R.qualcomm.com with ESMTP/TLS/RC4-SHA; 29 Jun 2017 09:22:44 -0700
Received: from [10.64.106.27] (10.80.80.8) by NASANEXM01F.na.qualcomm.com (10.85.0.32) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 29 Jun 2017 09:22:39 -0700
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <Ruediger.Geib@telekom.de>
CC: <spring@ietf.org>, <ietf@ietf.org>, <draft-ietf-spring-oam-usecase.all@ietf.org>, <gen-art@ietf.org>
Subject: Re: Genart last call review of draft-ietf-spring-oam-usecase-06
Date: Thu, 29 Jun 2017 10:18:17 -0500
Message-ID: <2C85CD35-0929-4200-8A79-E194DC5E27C7@qti.qualcomm.com>
In-Reply-To: <8d2d8cf3992b4b1fa96d5a755e5756ab@HE101653.emea1.cds.t-internal.com>
References: <149867468440.7527.6305996146978005032@ietfa.amsl.com> <8d2d8cf3992b4b1fa96d5a755e5756ab@HE101653.emea1.cds.t-internal.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
X-Mailer: MailMate (1.9.6r5347)
X-Originating-IP: [10.80.80.8]
X-ClientProxiedBy: NASANEXM01C.na.qualcomm.com (10.85.0.83) To NASANEXM01F.na.qualcomm.com (10.85.0.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/R2-Og5L54KzTP9X2lJOP8AY0exg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jun 2017 16:22:48 -0000

On 29 Jun 2017, at 2:28, Ruediger.Geib@telekom.de wrote:

> Hi Pete,
>
> thanks for proposing to make this an Applicability Statement, BCP or 
> standard.
>
> I don't object, but if the status of this draft is supposed to be 
> changed, my chairs and AD need to support this. Bruno and Alvaro, 
> what's your view on Pete's proposal? We may have to invest some more 
> time and text then. I personally don't object to "informational" as an 
> aim, but if that means removing major parts of the content, I'd be 
> rather unhappy.

Thanks for considering this. IMO, I don't see why doing this as PS would 
require removing anything; lots of PSs have informational content in 
them.

> Pete, also Alvaro gave us a routing AD review on Friday, 16. June (and 
> he had comments). Bruno's shephard review as part of the WG Last Call 
> resulted in better structuring and definitions in the document. So 
> far, no AD or reviewer "tends to ignore [this] Informational "use 
> case" document". You’re the third AD to comment and ask for changes 
> (and I recall to have had serious AD and IESG reviews with other 
> informationals).

Oh, I didn't mean to say that serious reviews of Informational docs 
didn't happen; it quite often does. But the bar is lower, and I know for 
myself (both as a participant and as an AD) that sometimes I would skip 
reading a particular document because I had run out of time and "it was 
only going for Informational", or see something that I didn't like in a 
Informational document and say, "Well, it's only going for 
Informational, so I'm not going to cause too much of a fuss". For a 
document that is actually a consensus specification of an IETF WG, that 
shouldn't be allowed to happen; everybody should be aware that this 
document should get the full scrutiny of a standards-track document.

> Regards,
>
> Ruediger

Cheers,

pr

> -----Ursprüngliche Nachricht-----
> Von: Pete Resnick [mailto:presnick@qti.qualcomm.com]
> Gesendet: Mittwoch, 28. Juni 2017 20:31
> An: gen-art@ietf.org
> Cc: spring@ietf.org; ietf@ietf.org; 
> draft-ietf-spring-oam-usecase.all@ietf.org
> Betreff: Genart last call review of draft-ietf-spring-oam-usecase-06
>
> Reviewer: Pete Resnick
> 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-oam-usecase-06
> Reviewer: Pete Resnick
> Review Date: 2017-06-28
> IETF LC End Date: 2017-06-30
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: Not Ready for publication as Informational, but might be 
> Ready for publication as Proposed Standard
>
> Major issues:
>
> This is an admittedly unusual review. I have read through the entire 
> document, and the technical work seems fine, but is well beyond my 
> technical expertise, so I can't really comment on the technical 
> correctness. However, it is absolutely clear to me that this is *not* 
> a "use case" document at all and I don't think it's appropriate as an 
> Informational document. This is clearly a
> *specification* of a path monitoring system. It gives guidances as to 
> required, recommended, and optional parameters, and specifies how to 
> use different protocol pieces. It is at the very least what RFC 2026 
> refers to as an "Applicability Statement (AS)" (see RFC 2026, sec. 
> 3.2). It *might* be a BCP, but it is not strictly giving "common 
> guidelines for policies and operations"
> (2026, sec. 5), so I don't really think that's right, and instead this 
> should be offered for Proposed Standard. Either way, I think 
> Informational is not correct. Importantly, I think there is a good 
> likelihood that this document has not received the appropriate amount 
> of review; people tend to ignore Informational "use case" documents, 
> and there have been no Last Call comments beyond Joel's RTG Area 
> Review. Even in IESG review, an Informational document only takes the 
> sponsoring AD to approve; every other AD can summarily ignore the 
> document, or even ballot ABSTAIN, and the document will still be 
> published (though that does not normally happen). This document should 
> have much more than that level of review. I strongly recommend to the 
> WG and AD that this document be withdrawn as an Informational document 
> and resubmitted for Proposed Standard and have that level of review 
> and scrutiny applied to it.
>
> Minor issues:
>
> None.
>
> Nits/editorial comments:
>
> This document refers to RFC 4379, which has been obsoleted by RFC 
> 8029. It seems like the references should be updated.


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


From nobody Thu Jun 29 12:43:06 2017
Return-Path: <tonysietf@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 19500129562; Thu, 29 Jun 2017 12:43:04 -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, 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 XAXCVVcas4OG; Thu, 29 Jun 2017 12:43:01 -0700 (PDT)
Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c: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 D3F7E1205D3; Thu, 29 Jun 2017 12:43:00 -0700 (PDT)
Received: by mail-wm0-x229.google.com with SMTP id i127so25474855wma.0; Thu, 29 Jun 2017 12:43:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=45WlP9O6PuqMca0BwQhj7340e6qF/ld1VLc0Qe3A7mY=; b=M+OCf0Oi3QBtDRJlYunkMJTRO+4wfw2+Bl5oXySTRHGzsSUl7C7wsmTjKTZ3wWWR1y IFaEq6SHV8D2YhNyuSTfYHAdbccdAeiQEGOEEQRQ8+cAiwcTc+fQ1bEqflcQsazA1+dm LQ/y8Js15PSbat9aNmGcuEvuwWZVMPVG2SNo7yrvjB2GWG8xp81PveI8B1YkOgDXrT56 kcy1JHzWsELfz/iqOc36W+phnMXkykqp8cjeqfZqFo0DqLNcph4nXM99VfBfwYZwz8x9 cmm9crz7MZvNwXVRAlVVYA0F+k3eQUviSbJHYqmyS4XPuc8Dr+hOnQu1lVzpHmlwlKAU GC4w==
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=45WlP9O6PuqMca0BwQhj7340e6qF/ld1VLc0Qe3A7mY=; b=XbMCZTYUTGk5hRn8Jag6TiXbFw8/9i86cA+Z7+yZBUf4TkE0WHtQKA7NEmbcWHdcoc 4HjV7Eex/thD/hbNEHscoFNRWFXHiUyNUeojHBY0lWsCkU2jKrTLHHstfc5V5odOLy1K Qdffeg5DJv48n6xmafEhsFHXGD67xR5ZRUkB+Qnit5zSNFtbnKhc8HeHtbJOGa1Pnxlw 3MdV6q1e+UgStri8w2BZb6x0UC9wYzB9YRL54NDU48e3lXmGzTzVcVz1TsCyuCCko4o4 3MbHjE3TyI/Ni87t7TpEO2Uc8wAjeEHPSzH3YfYfAWe1+fuq69K4m/UByKYkDozQtDce YJPw==
X-Gm-Message-State: AKS2vOxGGDRo4pTFSU9gTj9S+UlXbfBLzlbfdNmaQlZIdAERABAb53Nt RORTCquK/Ul2XuduaA3NQ5q3IAo7hw==
X-Received: by 10.80.184.24 with SMTP id j24mr2797663ede.176.1498765379439; Thu, 29 Jun 2017 12:42:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.80.183.131 with HTTP; Thu, 29 Jun 2017 12:42:18 -0700 (PDT)
In-Reply-To: <7d872d02-4154-989d-e83d-4d7408cc6073@juniper.net>
References: <149838804788.3251.829139224134758886@ietfa.amsl.com> <7d872d02-4154-989d-e83d-4d7408cc6073@juniper.net>
From: Tony Przygienda <tonysietf@gmail.com>
Date: Thu, 29 Jun 2017 12:42:18 -0700
Message-ID: <CA+wi2hMEjB1myWVBp0efQi_m8kFGa03o-pNg03CzBChk6Tt1OA@mail.gmail.com>
Subject: Re: [Bier] Genart last call review of draft-ietf-bier-architecture-07
To: Eric C Rosen <erosen@juniper.net>
Cc: Dan Romascanu <dromasca@gmail.com>, gen-art@ietf.org, "bier@ietf.org" <bier@ietf.org>, ietf@ietf.org,  draft-ietf-bier-architecture.all@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c193dbe0b136b05531e8294"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/qB1gJoj4TTxN9UZlk0voEd1mpfE>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jun 2017 19:43:04 -0000

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

Dan, thanks for your comment. My comments inline and I encourage the
working group to provide comments.


On Tue, Jun 27, 2017 at 7:42 AM, Eric C Rosen <erosen@juniper.net> wrote:

> On 6/25/2017 6:54 AM, Dan Romascanu wrote:
>
> 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> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>
> Document: draft-ietf-bier-architecture-?
> ?
> Reviewer: Dan Romascanu
> Review Date: 2017-06-25
> IETF LC End Date: 2017-06-29
> IESG Telechat date: 2017-07-06
>
> Summary:
>
> This document specifies a new architecture known as "Bit Index Explicit
> Replication" (BIER) for the forwarding of multicast data packets through a
> "multicast domain".  It does not require a protocol for explicitly building
> multicast distribution trees, nor does it require intermediate nodes to
> maintain any per-flow state. This architecture is .  While the Abstract and
> Introduction of the document mentions Architecture as the principal scope, this
> document goes well beyond the scope of a typical architectural document.
> including detailed definitions of the procedures, terminology and normative
> algorithms required for BIER.
>
> The document is clear and detailed. Because of its structure, I am missing some
> information that usually can be found in architecture documents. I included
> these in the 'minor issues' list. Although none of these may be a show-stopper,
> I believe that addressing these before document approval can improve the
> quality of the document and of the overall BIER work.
>
> Major issues:
>
> Minor issues:
>
> 1. As the document is targeting 'Experimental' it would be useful to mention
> what is the scope of the experiment.The charter actually says:
>
> ' The scope of the experiment will be
> documented in the output of the Working Group.'
>
> Would not the Architecture document be the right place for this? If not, is
> there another document that deals or is planned to define the scope of the
> experiment?
>
>
> I don't really know what is meant by "the experiment" or "scope of the
> experiment", but I'm pretty sure it is not relevant to the architecture (or
> to the forwarding rules).
>
> I don't know if there is another document discussing "scope of the
> experiment", or if such a document is actually needed.  That would be a
> question for the WG chairs.
>
>
 Applicability statements we have in the charter as #4 and it is probably a
more natural place to document the scope but I consider it unrelated to the
architecture draft.


> 2. While the Abstract and Introduction of the document mentions Architecture as
> the principal scope, this document is different from a typical architectural
> document. While it defines well the procedures, terminology and normative
> algorithms required for BIER Intra-domain forwarding, it goes well beyond the
> level of detail that other similar documents go. Specifications of the
> procedures and normative algorithm should be mentioned in Abstract and
> Introduction, they occupy the same or more space than architecture.
>
>
> I can add a few sentences to the abstract and introduction to make it
> clear that the procedures for fowarding BIER packets within a BIER domain
> specified in this document.
>

The abstract is already pretty fat, let's keep the additions trim.
Introduction of course can benefit from adding quick overview of introduced
procedures and algorithms.


>
> 3. On the other hand I am missing the relationship with other work items in the
> BIER charter - there is no manageability section for example, there is no
> reference to the performance impact in networks. Maybe these are dealt with in
> a different document or documents or BIER, if so it would be good at least to
> mention and reference these here.
>
>
> There is no requirement to include a manageability section.
>
> I believe there is ongoing work having to do with Operations and
> Management of BIER, but as that does not help to understand the
> architecture (or forwarding procedures), I don't think it would be
> appropriate to reference that work.
>

Yes, OAM is in charter & document for it exists. I see nothing wrong with
referencing it but I don't think it needs a manageability section.


>
> With regard to the performance impact, if the question is speed of
> forwarding, there is mention of the fact that the number of lookups needed
> to forward a BIER packet is on the order of the number of neighbors.   I
> don't know what else can really be said at this level of detail, as the
> actual forwarding performance will depend a great deal on the
> implementation.  I'm not worried too much about that, because if BIER
> implementations do not perform well, the technology will not catch on.
>

agreed. I would suggest actually to point out that the algorithm in the
architecture is not normative. The architecture leaves a lot of leeway in
terms how efficient the algorithm can be in terms of reducing replication
vs. speed vs. e.g. ECMP sophistication. This is intended.

As Eric says, if the turbine will be underpowered, this suidae will not
leave the ground ;-)


>
>
> 4. I also would have expected the architecture document to refer the use cases
> document and note which of the use cases are being addressed and how -
> draft-ietf-bier-use-cases is not even included in the references.
>
>
> I don't see any reason why the architecture document should reference the
> "use cases" document.  An explanation of how to apply the architecture to
> each use case is not within the scope of the architecture document.
>

I see no harm in referencing use cases but not much use for it either
except showing that the architecture is flexible enough to meet wide range
of applications.


>
> 5. Sections 3 to 6 mentioned repeatedly provisioning. As there is no Operations
> and Manageability section as in many other Routing Area documents, it is not
> clear how this is expected to happen.
>
>
> How OAM is "expected to happen" would be outside the scope of this
> document.
>

The "provisioning" language is unfortunate. We could (and maybe should)
replace it simply with "MUST support" rather than "be able to be
provisioned" and be done. Whether it's a controller, IGP signalling or
anything else is irrelevant to BIER architecture.


>
> For example draft-ietf-bier-bier-yang is
> not mentioned or referred. I suggest adding a note (and maybe references) for
> clarity.
>
>
> I don't see any reason to reference that document.
>

I agree, I don't think Yang is needed/helpful in an architecture document.

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

<div dir=3D"ltr">Dan, thanks for your comment. My comments inline and I enc=
ourage the working group to provide comments.=C2=A0<div><br></div><div><div=
 class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, Jun 27, 2017 =
at 7:42 AM, Eric C Rosen <span dir=3D"ltr">&lt;<a href=3D"mailto:erosen@jun=
iper.net" target=3D"_blank">erosen@juniper.net</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">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF"><div><div class=3D"h5">
    On 6/25/2017 6:54 AM, Dan Romascanu wrote:<br>
    </div></div><blockquote type=3D"cite">
      <pre><div><div class=3D"h5">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

<a class=3D"m_-844990701592598009moz-txt-link-rfc2396E" href=3D"https://tra=
c.ietf.org/trac/gen/wiki/GenArtfaq" target=3D"_blank">&lt;https://trac.ietf=
.org/trac/<wbr>gen/wiki/GenArtfaq&gt;</a>.

Document: draft-ietf-bier-architecture-?<wbr></div></div>?
Reviewer: Dan Romascanu
Review Date: 2017-06-25
IETF LC End Date: 2017-06-29
IESG Telechat date: 2017-07-06

Summary:

This document specifies a new architecture known as &quot;Bit Index Explici=
t
Replication&quot; (BIER) for the forwarding of multicast data packets throu=
gh a
&quot;multicast domain&quot;.  It does not require a protocol for explicitl=
y building
multicast distribution trees, nor does it require intermediate nodes to
maintain any per-flow state. This architecture is .  While the Abstract and
Introduction of the document mentions Architecture as the principal scope, =
this
document goes well beyond the scope of a typical architectural document.
including detailed definitions of the procedures, terminology and normative
algorithms required for BIER.

The document is clear and detailed. Because of its structure, I am missing =
some
information that usually can be found in architecture documents. I included
these in the &#39;minor issues&#39; list. Although none of these may be a s=
how-stopper,
I believe that addressing these before document approval can improve the
quality of the document and of the overall BIER work.

Major issues:

Minor issues:

1. As the document is targeting &#39;Experimental&#39; it would be useful t=
o mention
what is the scope of the experiment.The charter actually says:

&#39; The scope of the experiment will be
documented in the output of the Working Group.&#39;

Would not the Architecture document be the right place for this? If not, is
there another document that deals or is planned to define the scope of the
experiment?</pre>
    </blockquote>
    <br>
    I don&#39;t really know what is meant by &quot;the experiment&quot; or =
&quot;scope of
    the experiment&quot;, but I&#39;m pretty sure it is not relevant to the
    architecture (or to the forwarding rules).<br>
    <br>
    I don&#39;t know if there is another document discussing &quot;scope of=
 the
    experiment&quot;, or if such a document is actually needed.=C2=A0 That =
would
    be a question for the WG chairs.<span class=3D""><br>
    <br></span></div></blockquote><div><br></div><div>=C2=A0Applicability s=
tatements we have in the charter as #4 and it is probably a more natural pl=
ace to document the scope but I consider it unrelated to the architecture d=
raft.=C2=A0</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 tex=
t=3D"#000000" bgcolor=3D"#FFFFFF"><span class=3D"">
    <blockquote type=3D"cite">
      <pre>2. While the Abstract and Introduction of the document mentions =
Architecture as
the principal scope, this document is different from a typical architectura=
l
document. While it defines well the procedures, terminology and normative
algorithms required for BIER Intra-domain forwarding, it goes well beyond t=
he
level of detail that other similar documents go. Specifications of the
procedures and normative algorithm should be mentioned in Abstract and
Introduction, they occupy the same or more space than architecture.</pre>
    </blockquote>
    <br></span>
    I can add a few sentences to the abstract and introduction to make
    it clear that the procedures for fowarding BIER packets within a
    BIER domain specified in this document.=C2=A0 <br></div></blockquote><d=
iv><br></div><div>The abstract is already pretty fat, let&#39;s keep the ad=
ditions trim. Introduction of course can benefit from adding quick overview=
 of introduced procedures and algorithms.=C2=A0</div><div>=C2=A0</div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF"><span c=
lass=3D"">
    <br>
    <blockquote type=3D"cite">
      <pre>3. On the other hand I am missing the relationship with other wo=
rk items in the
BIER charter - there is no manageability section for example, there is no
reference to the performance impact in networks. Maybe these are dealt with=
 in
a different document or documents or BIER, if so it would be good at least =
to
mention and reference these here.</pre>
    </blockquote>
    <br></span>
    There is no requirement to include a manageability section.<br>
    <br>
    I believe there is ongoing work having to do with Operations and
    Management of BIER, but as that does not help to understand the
    architecture (or forwarding procedures), I don&#39;t think it would be
    appropriate to reference that work.</div></blockquote><div><br></div><d=
iv>Yes, OAM is in charter &amp; document for it exists. I see nothing wrong=
 with referencing it but I don&#39;t think it needs a manageability section=
. =C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div text=3D"=
#000000" bgcolor=3D"#FFFFFF">
    <br>
    With regard to the performance impact, if the question is speed of
    forwarding, there is mention of the fact that the number of lookups
    needed to forward a BIER packet is on the order of the number of
    neighbors.=C2=A0=C2=A0 I don&#39;t know what else can really be said at=
 this level
    of detail, as the actual forwarding performance will depend a great
    deal on the implementation.=C2=A0 I&#39;m not worried too much about th=
at,
    because if BIER implementations do not perform well, the technology
    will not catch on.</div></blockquote><div><br></div><div>agreed. I woul=
d suggest actually to point out that the algorithm in the architecture is n=
ot normative. The architecture leaves a lot of leeway in terms how efficien=
t the algorithm can be in terms of reducing replication vs. speed vs. e.g. =
ECMP sophistication. This is intended.=C2=A0</div><div><br></div><div>As Er=
ic says, if the turbine will be underpowered, this suidae will not leave th=
e ground ;-)</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 tex=
t=3D"#000000" bgcolor=3D"#FFFFFF"><span class=3D""><br>
    <br>
    <blockquote type=3D"cite">
      <pre>4. I also would have expected the architecture document to refer=
 the use cases
document and note which of the use cases are being addressed and how -
draft-ietf-bier-use-cases is not even included in the references.</pre>
    </blockquote>
    <br></span>
    I don&#39;t see any reason why the architecture document should
    reference the &quot;use cases&quot; document.=C2=A0 An explanation of h=
ow to apply
    the architecture to each use case is not within the scope of the
    architecture document.=C2=A0 <br></div></blockquote><div><br></div><div=
>I see no harm in referencing use cases but not much use for it either exce=
pt showing that the architecture is flexible enough to meet wide range of a=
pplications.</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 tex=
t=3D"#000000" bgcolor=3D"#FFFFFF"><span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <pre>5. Sections 3 to 6 mentioned repeatedly provisioning. As there i=
s no Operations
and Manageability section as in many other Routing Area documents, it is no=
t
clear how this is expected to happen. </pre>
    </blockquote>
    <br></span>
    How OAM is &quot;expected to happen&quot; would be outside the scope of=
 this
    document. <br></div></blockquote><div><br></div><div>The &quot;provisio=
ning&quot; language is unfortunate. We could (and maybe should) replace it =
simply with &quot;MUST support&quot; rather than &quot;be able to be provis=
ioned&quot; and be done. Whether it&#39;s a controller, IGP signalling or a=
nything else is irrelevant to BIER architecture.=C2=A0</div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><div text=3D"#000000" bgcolor=3D"#FFFFFF">=
<span class=3D"">
    <br>
    <blockquote type=3D"cite">
      <pre>For example draft-ietf-bier-bier-yang is
not mentioned or referred. I suggest adding a note (and maybe references) f=
or
clarity.</pre>
    </blockquote>
    <br></span>
    I don&#39;t see any reason to reference that document.=C2=A0 <br></div>=
</blockquote><div><br></div><div>I agree, I don&#39;t think Yang is needed/=
helpful in an architecture document.=C2=A0</div><div>=C2=A0</div></div>
</div></div></div>

--94eb2c193dbe0b136b05531e8294--


From nobody Thu Jun 29 12:49:05 2017
Return-Path: <borje.ohlman@abc.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 4243A129B55; Thu, 29 Jun 2017 12:49:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 zS3Ju4kfYLiw; Thu, 29 Jun 2017 12:48:58 -0700 (PDT)
Received: from hekla.abc.se (hekla.abc.se [62.80.200.187]) (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 77083127137; Thu, 29 Jun 2017 12:48:57 -0700 (PDT)
Received: from esekigala257.mynet (h83-209-48-34.cust.se.alltele.net [83.209.48.34]) by hekla.abc.se (OpenSMTPD) with ESMTPSA id 5a64910a (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256:NO);  Thu, 29 Jun 2017 21:48:53 +0200 (CEST)
From: =?utf-8?Q?B=C3=B6rje_Ohlman?= <borje.ohlman@abc.se>
Message-Id: <1743F4BA-1D2E-470E-9D84-6F7CCCDF9861@abc.se>
Content-Type: multipart/alternative; boundary="Apple-Mail=_30EF9F7B-6FA2-4B45-A1A1-0F80279493E9"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Subject: Re: Call for Participation, Workshop on Internet naming systems
Date: Thu, 29 Jun 2017 21:48:56 +0200
In-Reply-To: <9afa1487-e1f7-8758-7ead-ab8114b822ed@iab.org>
Cc: iab@iab.org, ietf-announce@ietf.org, Dirk Kutscher <ietf@dkutscher.net>, David R Oran <daveoran@orandom.net>
To: ietf@ietf.org
References: <9afa1487-e1f7-8758-7ead-ab8114b822ed@iab.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3SQtswp_XWsJogZQmDNNCBGq3Xk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jun 2017 19:49:01 -0000

--Apple-Mail=_30EF9F7B-6FA2-4B45-A1A1-0F80279493E9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Dear All,

The topic of this IAB workshop is very closely related to the research =
area Information-centric Networking (ICN) which is addresses by the IRTF =
ICNRG. We therefore think it is very unfortunate that the proposed dates =
coincide with the major conference in the ICN field, ACM ICN-2017 which =
takes place in Berlin, Germany September 26-28, 2017, =
http://conferences2.sigcomm.org/acm-icn/2017/
We are also planning an ICNRG interim meeting in Berlin September 29, =
2017, as a followup to the conference, =
https://trac.ietf.org/trac/irtf/wiki/icnrg
We would therefore ask you to consider some alternative dates for this =
IAB workshop.

Best regards,
			Dirk, Dave & B=C3=B6rje (IRTF ICNRG co-chairs)

> On 22 Jun 2017, at 22:53, IAB Chair <iab-chair@iab.org> wrote:
>=20
> Call for Participation
> IAB workshop on Explicit Internet Naming Systems
> Internet namespaces rely on Internet connected systems sharing a =
common set of assumptions on the scope, method of resolution, and =
uniqueness of the names.    That set of         assumption allowed the =
creation of URIs and other systems which presumed that you could =
authoritatively identify a service using an Internet name, a service =
port, and a set of locally-significant path elements. =20
> There are now multiple challenges to maintaining that commonality of =
understanding. =20
> Some naming systems wish to use URIs to identify both a service and =
the method of resolution used to map the name to a serving node.  =
Because there is no common facility for varying the resolution method in =
the URI structure, those naming systems must either mint new URI schemes =
for each resolution service or infer the resolution method from a =
reserved name or pattern.  Both methods are currently difficult and =
costly, and the effort thus scales poorly.
> Users=E2=80=99 intentions to refer to specific names are now often =
expressed in voice input, gestures, and other methods which must be =
interpreted before being put into practice.  The systems which carry on =
that interpretation often infer which intent a user is expressing, and =
thus what name is meant, by contextual elements.  Those systems are =
linked to existing systems who have no access to that context and which =
may thus return results or create security expectations for an =
unintended name.
> Unicode allows for both combining characters and composed characters =
when local language communities have different practices.  When these do =
not have a single normalization, context is required to determine which =
to produce or assume in resolution.  How can this context be maintained =
in Internet systems?
> While any of these challenges could easily be the topic of a =
stand-alone effort, this workshop seeks to explore whether there is a =
common set of root problems in the explicitness of the resolution =
context, heuristic derivation of intent, or language matching.   If so, =
it seeks to identify promising areas for the development of new, more =
explicit naming systems for the Internet.
> We invite position papers on this topic to be submitted by July 28, =
2017 to ename@iab.org <mailto:ename@iab.org>.    Decisions on accepted =
submissions will be made by August 11, 2017.
> Proposed dates for the workshop are September 28th and 29th, 2017 and =
the proposed location is in the Pacific North West of North America.  =
Finalized logistics will be announced prior to the deadline for =
submissions.
> Ted Hardie
> for the IAB
>=20


--Apple-Mail=_30EF9F7B-6FA2-4B45-A1A1-0F80279493E9
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"">Dear All,<div class=3D""><br class=3D""></div><div =
class=3D"">The topic of this IAB workshop is very closely related to the =
research area Information-centric Networking (ICN) which is addresses by =
the IRTF ICNRG. We therefore think it is very unfortunate that the =
proposed dates coincide with the major conference in the ICN field, ACM =
ICN-2017 which takes place in Berlin, Germany&nbsp;September 26-28, =
2017,&nbsp;<a href=3D"http://conferences2.sigcomm.org/acm-icn/2017/" =
class=3D"">http://conferences2.sigcomm.org/acm-icn/2017/</a></div><div =
class=3D"">We are also planning an ICNRG interim meeting in =
Berlin&nbsp;September 29, 2017, as a followup to the conference,&nbsp;<a =
href=3D"https://trac.ietf.org/trac/irtf/wiki/icnrg" =
class=3D"">https://trac.ietf.org/trac/irtf/wiki/icnrg</a></div><div =
class=3D"">We would therefore ask you to consider some alternative dates =
for this IAB workshop.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Best regards,</div><div class=3D""><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">			=
</span>Dirk, Dave &amp; B=C3=B6rje (IRTF ICNRG co-chairs)</div><div =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 22 Jun 2017, at 22:53, IAB Chair &lt;<a =
href=3D"mailto:iab-chair@iab.org" class=3D"">iab-chair@iab.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D"">
 =20

    <meta http-equiv=3D"content-type" content=3D"text/html; =
charset=3Dutf-8" class=3D"">
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF" class=3D""><div =
style=3D"margin: 0px; font-size: 11pt; font-family: Arial; padding-top: =
0pt; padding-bottom: 0pt; line-height: 1.15; orphans: 2; widows: 2; =
text-align: left; font-style: normal; font-variant-ligatures: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
class=3D"c0" style=3D"font-weight: 400; text-decoration: none; =
vertical-align: baseline; font-size: 11pt; font-family: Arial; =
font-style: normal;">Call for
        Participation</span></div><div style=3D"margin: 0px; font-size: =
11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt; =
line-height: 1.15; orphans: 2; widows: 2; text-align: left; font-style: =
normal; font-variant-ligatures: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span class=3D"">IAB
        workshop on Explicit Internet Naming Systems</span></div><p =
class=3D"c1 c2" style=3D"margin: 0px; font-size: 11pt; font-family: =
Arial; padding-top: 0pt; padding-bottom: 0pt; line-height: 1.15; =
orphans: 2; widows: 2; text-align: left; height: 11pt; font-style: =
normal; font-variant-ligatures: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><span class=3D"c0" style=3D"font-weight: =
400; text-decoration: none; vertical-align: baseline; font-size: 11pt; =
font-family: Arial; font-style: normal;"></span></p><div style=3D"margin: =
0px; font-size: 11pt; font-family: Arial; padding-top: 0pt; =
padding-bottom: 0pt; line-height: 1.15; orphans: 2; widows: 2; =
text-align: left; font-style: normal; font-variant-ligatures: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
class=3D"">Internet
        namespaces rely<span class=3D"">&nbsp;</span></span><span =
class=3D"c0" style=3D"font-weight: 400; text-decoration: none; =
vertical-align: baseline; font-size: 11pt; font-family: Arial; =
font-style: normal;">on Internet connected systems
        sharing a common set of assumptions on the scope, method of
        resolution, and uniqueness of the names. &nbsp; &nbsp;That set =
of
        assumption allowed the creation of URIs and other systems which
        presumed that you could authoritatively identify a service using
        an Internet name, a service port, and a set of
        locally-significant path elements. &nbsp;</span></div><p =
class=3D"c1 c2" style=3D"margin: 0px; font-size: 11pt; font-family: =
Arial; padding-top: 0pt; padding-bottom: 0pt; line-height: 1.15; =
orphans: 2; widows: 2; text-align: left; height: 11pt; font-style: =
normal; font-variant-ligatures: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><span class=3D"c0" style=3D"font-weight: =
400; text-decoration: none; vertical-align: baseline; font-size: 11pt; =
font-family: Arial; font-style: normal;"></span></p><div style=3D"margin: =
0px; font-size: 11pt; font-family: Arial; padding-top: 0pt; =
padding-bottom: 0pt; line-height: 1.15; orphans: 2; widows: 2; =
text-align: left; font-style: normal; font-variant-ligatures: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
class=3D"c0" style=3D"font-weight: 400; text-decoration: none; =
vertical-align: baseline; font-size: 11pt; font-family: Arial; =
font-style: normal;">There are now
        multiple challenges to maintaining that commonality of
        understanding. &nbsp;</span></div><p class=3D"c1 c2" =
style=3D"margin: 0px; font-size: 11pt; font-family: Arial; padding-top: =
0pt; padding-bottom: 0pt; line-height: 1.15; orphans: 2; widows: 2; =
text-align: left; height: 11pt; font-style: normal; =
font-variant-ligatures: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;"><span class=3D"c0" style=3D"font-weight: 400; text-decoration: =
none; vertical-align: baseline; font-size: 11pt; font-family: Arial; =
font-style: normal;"></span></p>
    <ul class=3D"start c3 lst-kix_vlchuldijmo2-0" style=3D"padding: 0px; =
margin: 0px; list-style-type: none; font-family: 'Times New Roman'; =
font-size: inherit; font-style: normal; font-variant-ligatures: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: 2; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;">
      <li class=3D"c4" style=3D"font-size: 11pt; font-family: Arial; =
margin-left: 36pt; padding-top: 0pt; padding-left: 0pt; padding-bottom: =
10pt; line-height: 1.15; orphans: 2; widows: 2; text-align: left;"><span =
class=3D"c0" style=3D"font-weight: 400; text-decoration: none; =
vertical-align: baseline; font-size: 11pt; font-family: Arial; =
font-style: normal;">Some naming systems wish to use
          URIs to identify both a service and the method of resolution
          used to map the name to a serving node. &nbsp;Because there is =
no
          common facility for varying the resolution method in the URI
          structure, those naming systems must either mint new URI
          schemes for each resolution service or infer the resolution
          method from a reserved name or pattern. &nbsp;Both methods are
          currently difficult and costly, and the effort thus scales
          poorly.</span></li>
      <li class=3D"c4" style=3D"font-size: 11pt; font-family: Arial; =
margin-left: 36pt; padding-top: 0pt; padding-left: 0pt; padding-bottom: =
10pt; line-height: 1.15; orphans: 2; widows: 2; text-align: left;"><span =
class=3D"c0" style=3D"font-weight: 400; text-decoration: none; =
vertical-align: baseline; font-size: 11pt; font-family: Arial; =
font-style: normal;">Users=E2=80=99 intentions to refer to
          specific names are now often expressed in voice input,
          gestures, and other methods which must be interpreted before
          being put into practice. &nbsp;The systems which carry on that
          interpretation often infer which intent a user is expressing,
          and thus what name is meant, by contextual elements. =
&nbsp;Those
          systems are linked to existing systems who have no access to
          that context and which may thus return results or create
          security expectations for an unintended name.</span></li>
    </ul>
    <ul class=3D"start c3 lst-kix_ykgz29z81s2h-0" style=3D"padding: 0px; =
margin: 0px; list-style-type: none; font-family: 'Times New Roman'; =
font-size: inherit; font-style: normal; font-variant-ligatures: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
orphans: 2; text-align: start; text-indent: 0px; text-transform: none; =
white-space: normal; widows: 2; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;">
      <li class=3D"c4" style=3D"font-size: 11pt; font-family: Arial; =
margin-left: 36pt; padding-top: 0pt; padding-left: 0pt; padding-bottom: =
10pt; line-height: 1.15; orphans: 2; widows: 2; text-align: left;"><span =
class=3D"c0" style=3D"font-weight: 400; text-decoration: none; =
vertical-align: baseline; font-size: 11pt; font-family: Arial; =
font-style: normal;">Unicode allows for both combining
          characters and composed characters when local language
          communities have different practices. &nbsp;When these do not =
have
          a single normalization, context is required to determine which
          to produce or assume in resolution. &nbsp;How can this context =
be
          maintained in Internet systems?</span></li>
    </ul><p class=3D"c1 c2" style=3D"margin: 0px; font-size: 11pt; =
font-family: Arial; padding-top: 0pt; padding-bottom: 0pt; line-height: =
1.15; orphans: 2; widows: 2; text-align: left; height: 11pt; font-style: =
normal; font-variant-ligatures: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;"><span class=3D"c0" style=3D"font-weight: =
400; text-decoration: none; vertical-align: baseline; font-size: 11pt; =
font-family: Arial; font-style: normal;"></span></p><div style=3D"margin: =
0px; font-size: 11pt; font-family: Arial; padding-top: 0pt; =
padding-bottom: 0pt; line-height: 1.15; orphans: 2; widows: 2; =
text-align: left; font-style: normal; font-variant-ligatures: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=3D""><span =
class=3D"c0" style=3D"font-weight: 400; text-decoration: none; =
vertical-align: baseline; font-size: 11pt; font-family: Arial; =
font-style: normal;">While any of
        these challenges could easily be the topic of a stand-alone
        effort, this workshop seeks to explore whether there is a common
        set of root problems in the explicitness of the resolution
        context, heuristic derivation of intent, or language matching. =
&nbsp;
        If so, it seeks to identify promising areas for the development
        of new, more explicit naming systems for the =
Internet.</span></div><p class=3D"c1 c2" style=3D"margin: 0px; =
font-size: 11pt; font-family: Arial; padding-top: 0pt; padding-bottom: =
0pt; line-height: 1.15; orphans: 2; widows: 2; text-align: left; height: =
11pt; font-style: normal; font-variant-ligatures: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span class=3D"c0" =
style=3D"font-weight: 400; text-decoration: none; vertical-align: =
baseline; font-size: 11pt; font-family: Arial; font-style: =
normal;"></span></p><div style=3D"margin: 0px; font-size: 11pt; =
font-family: Arial; padding-top: 0pt; padding-bottom: 0pt; line-height: =
1.15; orphans: 2; widows: 2; text-align: left; font-style: normal; =
font-variant-ligatures: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span class=3D"">We
        invite position papers on this topic to be submitted by July 28,
        2017 to<span class=3D"">&nbsp;</span></span><span class=3D"c8" =
style=3D"color:
        rgb(17, 85, 204); text-decoration: underline;"><a class=3D"c6" =
href=3D"mailto:ename@iab.org" style=3D"color: inherit;
          text-decoration: inherit;">ename@iab.org</a></span><span =
class=3D"c0" style=3D"font-weight: 400; text-decoration: none; =
vertical-align: baseline; font-size: 11pt; font-family: Arial; =
font-style: normal;">. &nbsp; &nbsp;Decisions on
        accepted submissions will be made by August 11, =
2017.</span></div><p class=3D"c1 c2" style=3D"margin: 0px; font-size: =
11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt; =
line-height: 1.15; orphans: 2; widows: 2; text-align: left; height: =
11pt; font-style: normal; font-variant-ligatures: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px;"><span class=3D"c0" =
style=3D"font-weight: 400; text-decoration: none; vertical-align: =
baseline; font-size: 11pt; font-family: Arial; font-style: =
normal;"></span></p><div style=3D"margin: 0px; font-size: 11pt; =
font-family: Arial; padding-top: 0pt; padding-bottom: 0pt; line-height: =
1.15; orphans: 2; widows: 2; text-align: left; font-style: normal; =
font-variant-ligatures: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span class=3D"c0" style=3D"font-weight: 400; =
text-decoration: none; vertical-align: baseline; font-size: 11pt; =
font-family: Arial; font-style: normal;">Proposed dates
        for the workshop are September 28th and 29th, 2017 and the
        proposed location is in the Pacific North West of North America.
        &nbsp;Finalized logistics will be announced prior to the =
deadline for
        submissions.</span></div><p class=3D"c1 c2" style=3D"margin: =
0px; font-size: 11pt; font-family: Arial; padding-top: 0pt; =
padding-bottom: 0pt; line-height: 1.15; orphans: 2; widows: 2; =
text-align: left; height: 11pt; font-style: normal; =
font-variant-ligatures: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: =
0px;"><span class=3D"c0" style=3D"font-weight: 400; text-decoration: =
none; vertical-align: baseline; font-size: 11pt; font-family: Arial; =
font-style: normal;"></span></p><div style=3D"margin: 0px; font-size: =
11pt; font-family: Arial; padding-top: 0pt; padding-bottom: 0pt; =
line-height: 1.15; orphans: 2; widows: 2; text-align: left; font-style: =
normal; font-variant-ligatures: normal; font-variant-caps: normal; =
font-weight: normal; letter-spacing: normal; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px;" class=3D""><span class=3D"c0" =
style=3D"font-weight: 400; text-decoration: none; vertical-align: =
baseline; font-size: 11pt; font-family: Arial; font-style: normal;">Ted =
Hardie</span></div><div style=3D"margin: 0px; font-size: 11pt; =
font-family: Arial; padding-top: 0pt; padding-bottom: 0pt; line-height: =
1.15; orphans: 2; widows: 2; text-align: left; font-style: normal; =
font-variant-ligatures: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span class=3D"c0" style=3D"font-weight: 400; =
text-decoration: none; vertical-align: baseline; font-size: 11pt; =
font-family: Arial; font-style: normal;">for the IAB</span></div><div =
style=3D"margin: 0px; font-size: 11pt; font-family: Arial; padding-top: =
0pt; padding-bottom: 0pt; line-height: 1.15; orphans: 2; widows: 2; =
text-align: left; height: 11pt; font-style: normal; =
font-variant-ligatures: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-indent: 0px; text-transform: none; =
white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px;" =
class=3D""><span class=3D"c0" style=3D"font-weight: 400; =
text-decoration: none; vertical-align: baseline; font-size: 11pt; =
font-family: Arial; font-style: normal;"><br class=3D"">
      </span></div>
  </div>

</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_30EF9F7B-6FA2-4B45-A1A1-0F80279493E9--


From nobody Thu Jun 29 12:55:54 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 4327712EAB4; Thu, 29 Jun 2017 12:55:44 -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 telechat review of draft-ietf-precis-7700bis-08
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149876614410.27838.18091001653680250992@ietfa.amsl.com>
Date: Thu, 29 Jun 2017 12:55:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_eiyFsytnRT7kAW1rGpc8V2dEVg>
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, 29 Jun 2017 19:55:44 -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-08
Reviewer: Russ Housley
Review Date: 2017-06-29
IETF LC End Date: 2017-06-13
IESG Telechat date: 2017-07-06

Summary: Ready

Major Concerns: None

Minor Concerns: None

Nits: None

Thanks for addressing the concern that was raised in my earlier review.



From nobody Thu Jun 29 13:20:23 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 345CA12EADB; Thu, 29 Jun 2017 13:20:14 -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 2H93k0i6eEEs; Thu, 29 Jun 2017 13:20:12 -0700 (PDT)
Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d: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 293DA12EABC; Thu, 29 Jun 2017 13:20:12 -0700 (PDT)
Received: by mail-qk0-x234.google.com with SMTP id d78so85670635qkb.1; Thu, 29 Jun 2017 13:20:12 -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=4Oloac48cW6i1uDJyqbHCpfx/i2UJSanArNDY6a40fk=; b=UjIi4GJ+VsZjYlmWFS7wOtHWxVpR1fe4uXRnsNK2nWrf5Q3LCPYWPeL4rtjRXBCjeb 1GE99UHNtMk12pxCkrTw5x/q5RbalV2pTrxq+R3wqVf0ck6Doj5jSI9TJsDSP8kfqEAe KQhaBmzmY+4n5titd3HD9kKHly1NPtb858KZSKThOHcU5vkDjO7RBEmzghFNhMrQFSw4 NaoIS9a02tedIsZWNKykxqxnxyi62GQlQw1BzM8dCfzy5A+W17YTniEoNvl/c54t0r7a slcbdVyrQ1suFpcrdd0A0msGMUgN9aEiCaXQVCcshdORe2/bZOJIe+7cezmVe1zUeV8t tAqQ==
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=4Oloac48cW6i1uDJyqbHCpfx/i2UJSanArNDY6a40fk=; b=s40xZ5nL4+GvQvLBSNtU8AhJypChaKQq4BkeMjA8AJAGN8AnZ1+nDl1D/xXHDrhnJz emiuQs9ZISmtN0a+2889BXEgoGIdBgGl+QFTiWfh1GI6W56R8Bp+toxRYHbIwfHoXQdK 6v6csHmkSrHRUogae/hDUvXGXuvSIWipAmQDgEwWSQ0i1VsT3zZ32WP/eewoyNSN5rr7 RmXlekKvYxD+EhimhbvkJ8e4DKtX904kOpgv3C9Jdg+THX0/7HpJjTw6gMGMqM4quU2R brRGKV48PhBZ6mIfdf3Xfu9RTtWAu1Tn4GEf6KjuqH6ZucQMsEdSl8Lj8apMWBPxskxE 9Ugw==
X-Gm-Message-State: AKS2vOwv1G07A4MsrherTk+YwE8ogaIsrlnl+FF9ScS+HqvyQ7KSzrzZ g7CWzPoDQBiKzOICnqHgWAJyXVE+Ow==
X-Received: by 10.55.75.71 with SMTP id y68mr21733324qka.247.1498767611153; Thu, 29 Jun 2017 13:20:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.108.67 with HTTP; Thu, 29 Jun 2017 13:20:10 -0700 (PDT)
In-Reply-To: <CA+wi2hMEjB1myWVBp0efQi_m8kFGa03o-pNg03CzBChk6Tt1OA@mail.gmail.com>
References: <149838804788.3251.829139224134758886@ietfa.amsl.com> <7d872d02-4154-989d-e83d-4d7408cc6073@juniper.net> <CA+wi2hMEjB1myWVBp0efQi_m8kFGa03o-pNg03CzBChk6Tt1OA@mail.gmail.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Thu, 29 Jun 2017 23:20:10 +0300
Message-ID: <CAFgnS4VgHFnFH-BomtRVLuOYpCTjt5NoY09NLoZPZXjp6j-ogQ@mail.gmail.com>
Subject: Re: [Bier] Genart last call review of draft-ietf-bier-architecture-07
To: Tony Przygienda <tonysietf@gmail.com>
Cc: Eric C Rosen <erosen@juniper.net>, gen-art <gen-art@ietf.org>,  "bier@ietf.org" <bier@ietf.org>, ietf <ietf@ietf.org>, draft-ietf-bier-architecture.all@ietf.org
Content-Type: multipart/alternative; boundary="001a114a9c7410544e05531f079e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/wCf9BwcsPLyQIqTWrVFTAZ7hkfs>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jun 2017 20:20:14 -0000

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

Just a short clarification on one point (or two).

See in text.

Regards,

Dan



> 3. On the other hand I am missing the relationship with other work items in the
>> BIER charter - there is no manageability section for example, there is no
>> reference to the performance impact in networks. Maybe these are dealt with in
>> a different document or documents or BIER, if so it would be good at least to
>> mention and reference these here.
>>
>>
>> There is no requirement to include a manageability section.
>>
>> I believe there is ongoing work having to do with Operations and
>> Management of BIER, but as that does not help to understand the
>> architecture (or forwarding procedures), I don't think it would be
>> appropriate to reference that work.
>>
>
> Yes, OAM is in charter & document for it exists. I see nothing wrong with
> referencing it but I don't think it needs a manageability section.
>
>
>>
>> 5. Sections 3 to 6 mentioned repeatedly provisioning. As there is no Operations
>> and Manageability section as in many other Routing Area documents, it is not
>> clear how this is expected to happen.
>>
>>
>> How OAM is "expected to happen" would be outside the scope of this
>> document.
>>
>
> The "provisioning" language is unfortunate. We could (and maybe should)
> replace it simply with "MUST support" rather than "be able to be
> provisioned" and be done. Whether it's a controller, IGP signalling or
> anything else is irrelevant to BIER architecture.
>
>

Please make a distinction between Operations and Management, and OAM
(Operations, Administration, Maintenance) as per RFC 6291. OAM is just one
of the aspects of Operations and Management.

While a dedicated section on Operations and Manageability considerations is
not mandatory, it is part of many documents in the Routing Area. I hold the
opinion that from operators perspective operational and manageability
aspects are core and should be dealt with in architecture and protocol
documents. Of course, as Gen-ART comments are written for the benefit of
the IESG and especially for the IETF chair, it's up to them to consider or
discard these comments. Note also that I marked them as 'minor' so they are
not show-stoppers IMO.

Regards,

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

<div dir=3D"ltr"><div><div><div>Just a short clarification on one point (or=
 two). <br><br></div>See in text. <br><br></div>Regards,<br><br></div>Dan<b=
r><br><div class=3D"gmail_extra"><span></span><br><span>
    </span><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div d=
ir=3D"ltr"><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><=
span class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div text=3D"#000000" bgcolo=
r=3D"#FFFFFF"><span><blockquote type=3D"cite">
      <pre>3. On the other hand I am missing the relationship with other wo=
rk items in the
BIER charter - there is no manageability section for example, there is no
reference to the performance impact in networks. Maybe these are dealt with=
 in
a different document or documents or BIER, if so it would be good at least =
to
mention and reference these here.</pre>
    </blockquote>
    <br></span>
    There is no requirement to include a manageability section.<br>
    <br>
    I believe there is ongoing work having to do with Operations and
    Management of BIER, but as that does not help to understand the
    architecture (or forwarding procedures), I don&#39;t think it would be
    appropriate to reference that work.</div></blockquote><div><br></div></=
span><div>Yes, OAM is in charter &amp; document for it exists. I see nothin=
g wrong with referencing it but I don&#39;t think it needs a manageability =
section. =C2=A0</div><span class=3D""><div>=C2=A0</div></span><span class=
=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l=
eft:1px #ccc solid;padding-left:1ex"><div text=3D"#000000" bgcolor=3D"#FFFF=
FF"><span>
    <br>
    <blockquote type=3D"cite">
      <pre>5. Sections 3 to 6 mentioned repeatedly provisioning. As there i=
s no Operations
and Manageability section as in many other Routing Area documents, it is no=
t
clear how this is expected to happen. </pre>
    </blockquote>
    <br></span>
    How OAM is &quot;expected to happen&quot; would be outside the scope of=
 this
    document. <br></div></blockquote><div><br></div></span><div>The &quot;p=
rovisioning&quot; language is unfortunate. We could (and maybe should) repl=
ace it simply with &quot;MUST support&quot; rather than &quot;be able to be=
 provisioned&quot; and be done. Whether it&#39;s a controller, IGP signalli=
ng or anything else is irrelevant to BIER architecture.=C2=A0</div><span cl=
ass=3D""><div>=C2=A0</div></span></div></div></div></div></blockquote><div>=
<br></div><div>Please make a distinction between Operations and Management,=
 and OAM (Operations, Administration, Maintenance) as per RFC 6291. OAM is =
just one of the aspects of Operations and Management. <br><br></div><div>Wh=
ile a dedicated section on Operations and Manageability considerations is n=
ot mandatory, it is part of many documents in the Routing Area. I hold the =
opinion that from operators perspective operational and manageability aspec=
ts are core and should be dealt with in architecture and protocol documents=
. Of course, as Gen-ART comments are written for the benefit of the IESG an=
d especially for the IETF chair, it&#39;s up to them to consider or discard=
 these comments. Note also that I marked them as &#39;minor&#39; so they ar=
e not show-stoppers IMO. <br><br></div><div>Regards,<br><br><br></div><div>=
<br>=C2=A0<br></div></div></div></div>

--001a114a9c7410544e05531f079e--


From nobody Thu Jun 29 13:42:52 2017
Return-Path: <aaron.falk@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 912D41270A7; Thu, 29 Jun 2017 13:42:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rhZYoD01--cI; Thu, 29 Jun 2017 13:42:43 -0700 (PDT)
Received: from mail-qk0-x243.google.com (mail-qk0-x243.google.com [IPv6:2607:f8b0:400d: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 3DE281200FC; Thu, 29 Jun 2017 13:42:43 -0700 (PDT)
Received: by mail-qk0-x243.google.com with SMTP id v143so331960qkb.3; Thu, 29 Jun 2017 13:42:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:date:message-id:in-reply-to:references:mime-version;  bh=MGk1xUkFxg8pzlYVCfulHBc8X5nMy0PF4CJiEs1MVhw=; b=Cs76QSnfEL1yC5d5y31kIHyp/kQTtZ1xm1d/fVKtWIgvjwM5LQMxIyxGhd89n7rFA9 3eSBf10Z64qkKwNgG+VutS5pDjpLKyK1CO4jq30eMZMnT99kJ0AmUVWvrihTRjpv2nor 18udTn6LHB9SBP4pUk4QHjho5FSG78IXewPJtj/w8fBITa0YS1LLQgr1U8RPWhuDv5Q6 RJIk+P8jFApY85bpGWT26UQpiy8qEvjb4ALiCSMr7+OFeNb2+YmxCvg3UKejuKqdpCbW TU0DrONBkwCSm1QTmKE6Ezmg47ZmrlSczElGYK9vZgN+UNazqhcfnhU3UH7icEwjDJ+F iMnQ==
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:in-reply-to :references:mime-version; bh=MGk1xUkFxg8pzlYVCfulHBc8X5nMy0PF4CJiEs1MVhw=; b=Mz9MDN63ihDc4kEmEJOIzmbyirmmcS9juoD6LhekOCwxzYyy79T1kX0R4O7e/PRis3 vG1yu66FgT7XZlUrxyOyfRhZXPHkudYVzWqTPEwdvwfSHvj+UfSctNFK2za2QNoPx1mP y7XSwlZwPq8WMfeGMpFFsRSrdMc+haQz+LnNDymG9dwA1P0t7dRk3HBP1v07Hk/1X6ZY sH3qaI9YcnrVog692EuMRypvQleRvi2hEXuZ1ZBY93U4zmkrHEnoVljSSdtIlpSljufD SH41Bg77BJZsZJZBAdLeRKxBRyhOZxRcBunVYYXSzsJB5+6CE+uY4jQ4ZId6Xrmd+syI M5Ig==
X-Gm-Message-State: AKS2vOzjGDkePKqgjBrKcuPzud5Sxpw9bR/qP2FGKpZLinJ4t2wwRfk8 0/O8538XjroR4zxNIcc=
X-Received: by 10.55.169.206 with SMTP id s197mr20106294qke.115.1498768962017;  Thu, 29 Jun 2017 13:42:42 -0700 (PDT)
Received: from [169.254.70.135] ([72.246.0.14]) by smtp.gmail.com with ESMTPSA id r1sm4795434qkh.43.2017.06.29.13.42.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 29 Jun 2017 13:42:41 -0700 (PDT)
From: "Aaron Falk" <aaron.falk@gmail.com>
To: ietf@ietf.org, "99attendees@ietf.org" <99attendees@ietf.org>
Subject: Re: PechaKucha presenters for Prague?
Date: Thu, 29 Jun 2017 16:42:40 -0400
Message-ID: <DDE016E1-C9B5-4980-9A5D-36D05DBB9736@gmail.com>
In-Reply-To: <D53C2422-8C47-4E42-B5AF-9A263FB89730@gmail.com>
References: <D53C2422-8C47-4E42-B5AF-9A263FB89730@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=_MailMate_74347F5E-9349-43D3-9871-4118BEFBC3C8_="
X-Mailer: MailMate (1.9.6r5356)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FR8Vzqruo0RSOsyRPKNWub9p3oA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 29 Jun 2017 20:42:45 -0000

--=_MailMate_74347F5E-9349-43D3-9871-4118BEFBC3C8_=
Content-Type: text/plain; charset=utf-8; format=flowed; markup=markdown
Content-Transfer-Encoding: quoted-printable

I=E2=80=99ve heard from three people, which isn=E2=80=99t sufficient.  Un=
less a few =

more people show interest, I=E2=80=99m canceling for Prague.

=E2=80=94aaron

On 21 Jun 2017, at 18:09, Aaron Falk wrote:

> This is a poll for folks who are interested in presenting at a =

> PechaKucha in Prague.  The number of folks presenting has declined =

> slightly and I=E2=80=99m contemplating whether holding a session at eve=
ry =

> IETF meeting is too frequent.  If I don=E2=80=99t hear from enough folk=
s =

> we=E2=80=99ll wait until Singapore to do the next one.  In other words,=
 if =

> you want to give a talk, please send me a note ASAP.
>
> Standard invitation and background info below.
>
> Thanks!
>
> =E2=80=94aaron
>
> ____
>
> A Pecha Kucha is a lightning-talk presentation format, originating in =

> Japan, where a speaker presents 20 image-only slides that are each on =

> the screen for 20 seconds and advance automatically.  With each talk =

> lasting for 6:40, it has the feature of forcing presentations -- good =

> or bad -- to be focused and brief.  This is an unofficial event. =

> Topics are encouraged to be a IETF-related and satirical or =

> controversial in some way, although not mean-spirited.  Anyone can =

> participate in this social event.  Video from the Berlin, Seoul, and =

> Chicago PKs can be found [here](http://snaggletooth.akam.ai).
>
> Format Details:
>
> * Presentation slots are open to all, assigned first come, first =

> served.
> * To reserve a presentation slot, send a name and title to =

> aaron.falk@gmail.com and receive confirmation.
> * Presenters must agree to adhere to the Pecha Kucha format (20 =

> slides, primarily image-only, automatically advancing every 20 =

> seconds).
> * There are lots of online tutorials and suggestions for how to make a =

> good Pecha Kucha.  Here are a few: [[1](http://www.pechakucha.org/)], =

> [[2](http://blog.indezine.com/2012/05/10-tips-to-create-and-present-pec=
ha.html)], =

> [[3](https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha/)].

--=_MailMate_74347F5E-9349-43D3-9871-4118BEFBC3C8_=
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">I=E2=80=99ve heard from three people, which isn=E2=80=99t=
 sufficient.  Unless a few more people show interest, I=E2=80=99m canceli=
ng for Prague.</p>

<p dir=3D"auto">=E2=80=94aaron</p>

<p dir=3D"auto">On 21 Jun 2017, at 18:09, Aaron Falk wrote:</p>

<blockquote style=3D"border-left:2px solid #777; color:#777; margin:0 0 5=
px; padding-left:5px">
<p dir=3D"auto">This is a poll for folks who are interested in presenting=
 at a PechaKucha in Prague.  The number of folks presenting has declined =
slightly and I=E2=80=99m contemplating whether holding a session at every=
 IETF meeting is too frequent.  If I don=E2=80=99t hear from enough folks=
 we=E2=80=99ll wait until Singapore to do the next one.  In other words, =
if you want to give a talk, please send me a note ASAP.</p>

<p dir=3D"auto">Standard invitation and background info below.</p>

<p dir=3D"auto">Thanks!</p>

<p dir=3D"auto">=E2=80=94aaron</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">A Pecha Kucha is a lightning-talk presentation format, or=
iginating in Japan, where a speaker presents 20 image-only slides that ar=
e each on the screen for 20 seconds and advance automatically.  With each=
 talk lasting for 6:40, it has the feature of forcing presentations -- go=
od or bad -- to be focused and brief.  This is an unofficial event. Topic=
s are encouraged to be a IETF-related and satirical or controversial in s=
ome way, although not mean-spirited.  Anyone can participate in this soci=
al event.  Video from the Berlin, Seoul, and Chicago PKs can be found <a =
href=3D"http://snaggletooth.akam.ai" style=3D"color:#777">here</a>.</p>

<p dir=3D"auto">Format Details:</p>

<ul>
<li>Presentation slots are open to all, assigned first come, first served=
=2E</li>
<li>To reserve a presentation slot, send a name and title to <a href=3D"m=
ailto:aaron.falk@gmail.com" style=3D"color:#777">aaron.falk@gmail.com</a>=
 and receive confirmation.</li>
<li>Presenters must agree to adhere to the Pecha Kucha format (20 slides,=
 primarily image-only, automatically advancing every 20 seconds).</li>
<li>There are lots of online tutorials and suggestions for how to make a =
good Pecha Kucha.  Here are a few: [<a href=3D"http://www.pechakucha.org/=
" style=3D"color:#777">1</a>], [<a href=3D"http://blog.indezine.com/2012/=
05/10-tips-to-create-and-present-pecha.html" style=3D"color:#777">2</a>],=
 [<a href=3D"https://catherinecronin.wordpress.com/2012/06/13/pecha-kucha=
/" style=3D"color:#777">3</a>].</li>
</ul>
</blockquote>
</div>
</div>
</body>
</html>

--=_MailMate_74347F5E-9349-43D3-9871-4118BEFBC3C8_=--


From nobody Thu Jun 29 17:40:09 2017
Return-Path: <tinatsou6@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 49E3B126D45; Thu, 29 Jun 2017 17:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level: 
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ljuSnI8OUP36; Thu, 29 Jun 2017 17:40:07 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E29631200F3; Thu, 29 Jun 2017 17:40:03 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id j186so55403402pge.2; Thu, 29 Jun 2017 17:40:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=5mlqVYUXnDA2eQzvGifZVlfWaiKE8Ofjafaj0vi7GmU=; b=HyoJ6e3SUET9VDP5AdMkcXQOjXMfe+/Ww7t6rpAthBWDqdrP4fD9//vnEPmxPdtmAM qZQZQ1m2gNlHWNIPP4YzGpwtQK1OXRAXBJ7T9NTE2shgRkYPsnnZFgGEpQ0L0Bj/LCtc qPYjNvdZddceE5O/lnDhouwTsqqfe+gnaxGPZ4JXhRa8aqFoAci129L3HhxHSRvgD04z VuBt42vJtRwo5QlLF+m61J4Der97Yejz8vlI1HbTyVRqlYUyWuagivOuKeSZjTx9BFNy FQOLJgEv/UqMO1RZ5tKoxv1vlA4gzaBwSlz24dMVejnUGWqeGmXcDhqfim3ShZrLGxCE t6NQ==
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=5mlqVYUXnDA2eQzvGifZVlfWaiKE8Ofjafaj0vi7GmU=; b=nZqAvZK2OwTmZXY/CGrag18bSET8H/E3HwNL1oLlULQWqOT3FGJlIEhhKkhVLkwCjl EXVZ53y3QoeH91bN3Cj3jCXfJgDzgE4xLmAFLmmCdHeD/DsD/ZS77slfUTjLpZLhpcty qV7nfmLK6sOLjItbNxLq+jkild3yR3utsTyUYQeaz9ymUKTvbhPxP1W0Ylmx9ixqR1rk CqeJUq8J//ThbJZeL0g+j/SoNwYSP5bL+0ItOD2c7jRVplxhyoygEWFJm+tWoOtmMRW2 77zzHIVlikT9bodvxiUpVdrScMx1BuKbm1iMjSEsgSkItZfrtBb0a9Rc6YdchHIO2tF/ OnWg==
X-Gm-Message-State: AKS2vOz0IrjMsoUBiZN9f3OqT4WUnUx+L7PlqICHHmDHperEcRPFc7Mr C6wxXj9KHimJ2D30w/BkYzZ9D8P+Cg==
X-Received: by 10.99.123.18 with SMTP id w18mr18485395pgc.122.1498783203340; Thu, 29 Jun 2017 17:40:03 -0700 (PDT)
MIME-Version: 1.0
From: Tina Tsou <tinatsou6@gmail.com>
Date: Fri, 30 Jun 2017 00:39:52 +0000
Message-ID: <CAMS-Z8DXo7MVQF2NVwBYpiRd661PxPfAH+ZxW22YUpcyK+-3-g@mail.gmail.com>
Subject: SECDir review of draft-IETF-trill-arp-optimization-08
To: "draft-IETF-trill-arp-optimization.all@ietf.org" <draft-IETF-trill-arp-optimization.all@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>, "tina.tsou@arm.com" <tina.tsou@arm.com>
Content-Type: multipart/alternative; boundary="f403045c64ba6e3501055322a818"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/DAgDJEQkY6dP3kYmoGJyEgmP6q8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 00:40:08 -0000

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

Reviewer: Tina Tsou
Review result: Ready

This is a document that specifies optimized ARP/ND response for RBridge,
when the target's location is known, to avoid ARP/ND query and answer
flooding.

>From security point of view this document is Ready. If it can describe how
to store and transfer the key, it is more complete.

In addition, a flow chart may help the readers to clearly understand the
handling of messages in section 4.

No nit was found.
-- 
Thank you, Tina

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

<span style=3D"color:rgb(49,49,49);word-spacing:1px;background-color:rgb(25=
5,255,255)"><div dir=3D"auto">Reviewer: Tina Tsou</div></span><span style=
=3D"color:rgb(49,49,49);word-spacing:1px;background-color:rgb(255,255,255)"=
>Review result: Ready</span><br style=3D"color:rgb(49,49,49);word-spacing:1=
px"><br style=3D"color:rgb(49,49,49);word-spacing:1px"><span style=3D"color=
:rgb(49,49,49);word-spacing:1px;background-color:rgb(255,255,255)"><div dir=
=3D"auto">This is a document that specifies optimized ARP/ND response for R=
Bridge, when the target&#39;s location is known, to avoid ARP/ND query and =
answer flooding.</div></span><br style=3D"color:rgb(49,49,49);word-spacing:=
1px"><span style=3D"color:rgb(49,49,49);word-spacing:1px;background-color:r=
gb(255,255,255)"><div dir=3D"auto">From security point of view this documen=
t is Ready. If it can describe how to store and transfer the key, it is mor=
e complete.</div><div dir=3D"auto"><br></div><div dir=3D"auto">In addition,=
 a flow chart may help the readers to clearly understand the handling of me=
ssages in section 4.</div></span><br style=3D"color:rgb(49,49,49);word-spac=
ing:1px"><span style=3D"color:rgb(49,49,49);word-spacing:1px;background-col=
or:rgb(255,255,255)"><div dir=3D"auto">No nit was found.</div></span><div d=
ir=3D"ltr">-- <br></div><div data-smartmail=3D"gmail_signature">

Thank you,
Tina</div>

--f403045c64ba6e3501055322a818--


From nobody Thu Jun 29 19:17:40 2017
Return-Path: <d3e3e3@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 9686C129B74; Thu, 29 Jun 2017 19:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 B6RkVZ3UiUKa; Thu, 29 Jun 2017 19:17:28 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001: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 192E4129A9C; Thu, 29 Jun 2017 19:17:28 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id h64so17142728iod.0; Thu, 29 Jun 2017 19:17:28 -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=9HzTNkMcvS4yzHxXwMLFDr5N1hX/InMnh6UtABvknZQ=; b=cU9RcUu81fqYMMvQm2x3a351VexCv6V57sGeWcEoRYJBaOkVcNQkJ4/vzCtswoSpAm KnsLeunRxq35kOVy94kCTSxU8vCdGlhzr1LR03jh9SNVZUmvxHp/IPoBNp1sxIG7S2zJ dIqv+c9yivSThgBpsmlwuCu99U6ZwychrTq8uHVies20ZqQU6LvALSoQmgUkeX/c0ESp 9n/nNsJ/CLrsOKfbP/uUkPNFsAQ4wLx+LiANlP8HDpMfSMj3p4I886WWm052DIjUNm32 ndyl3K+hV4N08cDo+z46mC31xHdgd4szz7mEI397TeHo7gsxGu+b30nGcF2jRvRBcHA2 aYgg==
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=9HzTNkMcvS4yzHxXwMLFDr5N1hX/InMnh6UtABvknZQ=; b=YH3tOH0M7TYV6QYYuCKlIhOaRIFjFVoYbhSTU3eB5HphECY9VRCJoDUWVvFRDJlu25 nOLgROR81AELoyXAwTnG0mmAk/XHF2sr+JhidtVmQtC6gHmutId+FUk0l+PEljUTFDrd Pk0N/w7NOxADwbvCZV/PkvYz1IKB7nY0QS7+0/EmoNP+uItjyOQfAhThXAao/bJQLInP kxAscNA3jHDY5tiAUuOid6+i0HYvsMVVXTmbbd9yz+JJhpgvbN3NLtbR120qvsA4TvJ2 /qMKw7BFM77lFimQkKf6cy+PnpjNulRdDo/M2Zwqkqngg1dFhGgyJHIhmJ2kyC+/a6+S fsfA==
X-Gm-Message-State: AKS2vOzXjnKvZYeCUqn1jE1EHkMjQClbddNVhIqncF0v0b3a0rhw1F64 v07e1vpZARpuNqJ5AR2WKM2FgVIKiQ==
X-Received: by 10.107.156.83 with SMTP id f80mr20165783ioe.9.1498789047319; Thu, 29 Jun 2017 19:17:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.17.221 with HTTP; Thu, 29 Jun 2017 19:17:11 -0700 (PDT)
In-Reply-To: <52E4A8FC978E0241AE652516E24CAF0029AC2251@ESESSMB103.ericsson.se>
References: <149754795560.13109.17521244075940607817@ietfa.amsl.com> <CAF4+nEG-28weDot9R9Z4-05PX1tzBoKZSOHu8BJY2GiRzOv0nA@mail.gmail.com> <52E4A8FC978E0241AE652516E24CAF0029AC2251@ESESSMB103.ericsson.se>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 29 Jun 2017 22:17:11 -0400
Message-ID: <CAF4+nEEhaY+gtyjhVN1uzwgJ8m5oy1VU3urdH_hh-2KYV+NXLQ@mail.gmail.com>
Subject: Re: Tsvart early review of draft-ietf-trill-over-ip-10
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: "tsv-art@ietf.org" <tsv-art@ietf.org>, "trill@ietf.org" <trill@ietf.org>,  IETF Discussion <ietf@ietf.org>, "draft-ietf-trill-over-ip.all@ietf.org" <draft-ietf-trill-over-ip.all@ietf.org>
Content-Type: multipart/alternative; boundary="001a1141bcbec246930553240434"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LT0lB1R5sOTGCUmsmmhT9NR6W2Y>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 02:17:32 -0000

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

HI Magnus,

On Tue, Jun 27, 2017 at 1:13 PM, Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> Hi Donald,
>
> After having read your response I think there is an important question
> about the applicability of this document that affects several of the issues
> below and what solution you need. That is the question of what type of
> paths one expect to get Trill over IP working over. Because if the target
> is general Internet and also through middleboxes such as NATs and Firewall
> (Not intending to block) then there are a lot more work to ensure this. If
> you for example changes the applicability to require any on path
> middleboxes to fulfill certain requirements things can be more easily
> addressed.
>

The use cases in the document support communication over the general
Internet in the brach office case but that does not necessarily imply
NATs/Firewalls.

Den 2017-06-26 kl. 02:07, skrev Donald Eastlake:
>
> Hi Magnus,
>
> Thanks for the extensive review. See my responses below.
>
> On Thu, Jun 15, 2017 at 1:32 PM, Magnus Westerlund<magnus.westerlund@ericsson.com> <magnus.westerlund@ericsson.com> wrote:
>
>
> Diffserv usage
> --------------
>
> Section 4.3:
>
>    TRILL over IP implementations MUST support setting the DSCP value in
>    the outer IP Header of TRILL packets they send by mapping the TRILL
>    priority and DEI to the DSCP. They MAY support, for a TRILL Data
>    packet where the native frame payload is an IP packet, mapping the
>    DSCP in this inner IP packet to the outer IP Header with the default
>    for that mapping being to copy the DSCP without change.
>
> I think it is fine to require that implementations are capable  of setting
> DSCP values on the outer IP header. However, I fail to see any discussion of
> the potential issues with actually setting the DSCP values. It is one thing to
> do this in an IP back bone use case where one can know and have control over
> the PHB that the DSCP values maps to. But otherwise, over general internet the
> behavior is not that predictable. One can easily be subject to policers or
> remapping. Also as the actual DSCP code point usage is domain specific this is
> difficult. Priority reversal is likely the least of the problems that this can
> run into over general Internet.
>
> It sounds like appropriate discussion and warnings about these issues
> would resolve the above comment.
>
> I would note that the choice of encapsulation here do becomes important.
> Your's and Joe Touch's observation that for TCP, you can only have a single
> DSCP marking per TCP connection for example. For others, see the discussion
> in Section 5.1 of https://datatracker.ietf.org/doc/rfc7657/ on this
> issue.
>

Well, if a TRILL over IP implementation using TCP transport wants to have
more than one priority category for traffic where there might be one or
more intervening IP routers, which would be the normal case, it would just
need a TCP connection per priority category. Mapping the 8 priority levels
into a smaller number of categories is a routine thing to do. Note that the
base TRILL protocol specification (RFC 6325) says:

   RBridges are not required to implement any
   particular number of distinct priority levels but may treat one or

   more adjacent priority levels in the same fashion.


> David Black also raised an important question if one should treat this as
> a tunnel with a single predictable behavior or let the inner networks
> marking show through. Establishing a tunnel with a single PHB has less risk
> of running into issues than multiple different markings.
>

It is an implementation choice whether to have a single PHB or eight, one
per priority level, or something in between.

> Section 4.3:
>
>    The default TRILL priority and DEI to DSCP mapping, which may be
>    configured per TRILL over IP port, is an follows. Note that the DEI
>    value does not affect the default mapping and, to provide a
>    potentially lower priority service than the default priority 0,
>    priority 1 is considered lower priority than 0. So the priority
>    sequence from lower to higher priority is 1, 0, 2, 3, 4, 5, 6, 7.
>
>       TRILL Priority  DEI  DSCP Field (Binary/decimal)
>       --------------  ---  -----------------------------
>                   0   0/1  001000 / 8
>                   1   0/1  000000 / 0
>                   2   0/1  010000 / 16
>                   3   0/1  011000 / 24
>                   4   0/1  100000 / 32
>                   5   0/1  101000 / 40
>                   6   0/1  110000 / 48
>                   7   0/1  111000 / 56
>
> This appear to be an problematic mapping. At least for prio 0 and 1. As
> priority 1 appears to be intended to be higher than priority 0, it is
> interesting that it is mapped to CS1, which to quotehttps://datatracker.ietf.org/doc/rfc7657/:
>
> CS1 ('001000') was subsequently designated as the recommended
>       codepoint for the Lower Effort (LE) PHB [RFC3662].
>
> So what is proposed can in a network using default mapping, result in that you
> get priority 0 to be lower priority than 1. Plus that in some networks this can
> also results in strange remapping that results in a different PHB for CS1 than.
>
> The intent in the draft is to reflect the default relative priority of
> the different priority code points in IEEE Std 802.1Q where priority 1
> is lower than priority 0. At a quick look, it appears to me that RFC
> 2474 requires that 0x001000 be handled as being of a priority not
> lower than the priority with which 0x000000 is handled. Yet RFC 3662,
> which you point to, seems to suggest using 0x001000 as a lower
> priority code point than 0x000000. Given that 3662 not only does not
> update 2474 but is only Informational while 2474 is Standards Track, I
> would say that 2474 dominates and that this draft makes the best
> assumptions it can about default behavior...
>
>
> David Black provide a good answer on this.
>

I'll reply to him.

> MTU and Fragmentation
> ---------------------
>
> I think there are two main issue here. The first one is MTUD discovery
> of the actual IP path MTU between the ports. That will be needed to prevent
> a lot of traffic going into MTU black holes. Especially as TRILL requries
> 1470 byte support which is likey above a lot of paths.
>
> Seems like it would depend on the environments where TRILL was used.
> For example, I do not think 1470 would be a problem in most Data
> Center or Internet Exchange point uses, for example. Data Centers
> sometimes support 9K jumbo frames and the like.
>
> In fact, it is probably bad to focus too much on 1470 -- that is a
> required minimum to be sure that reasonable size link state PDUs can
> be successfully flooded through the TRILL campus so that routing will
> work. However, it would commonly be the case that, for the TRILL
> campus to be useful in a particular case, links need to be able to
> carry the expected size TRILL Data packets. For example, if there were
> two parts of a TRILL campus connected by one or a few TRILL over IP
> links and the end stations in each part were assuming they could use
> 1500 byte Ethernet packets, then the TRILL over IP links would need to
> support an MTU based on 1500 + TRILL Header + IP and TRILL over IP
> encapsulation. And more if security was being used or there were any
> other reasons for additional headers/encapsulation...
>
>
> Yes, and over general Internet you should be happy if you get 1500 bytes
> of IP MTU, it may easily be lower with a couple of additional tunnel
> headers. Thus, what you say is the goal is not feasible without a solution
> that supports fragmentation and reassembly, enabling one TRILL packet to be
> sent in multiple IP packets. The re-assembly do requires buffering and not
> something to easily perform on a router fast path. And attempting to use IP
> fragmentation is likely doomed if you have any type of NAT or Firewall in
> the way.
>
> This points to a dedicated solution or using a transport protocol that
> supports carrying arbitrary data sizes, like TCP or SCTP. And you need to
> use the byte-stream API of TCP to achieve this.
>

OK.

> Section 8.4:
>
>    Path MTU discovery [RFC4821] should be useful
>    in determining the IP MTU between a pair of RBridge ports with IP
>    connectivity.
>
> The issue with RFC4821 is that it has requirements on the packetization layer.
> Trill appears to have several components that are useful. However, it will
> require a specification of the procedure to result in a useful tool.
>
> See below.
>
>
> Section 8.4:
>
>    TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
>    [RFC7177], can be used to obtain added assurance of the MTU of a
>    link.
>
> Yes, that can confirm working MTUs that are at 1470 or above, but appears
> prevented from working below 1470?
>
> While there is a minimum size for TRILL IS-IS MTU PDUs, determined by
> header size, it is well below 1470, probably (depending on whether
> secuirty is in use, etc.) below 150 bytes.
>
>
> Okay, if you say so, it was not obvious from the spec that is was allowed
> to probe for paths with lesser MTUs than 1470.
>
> Thus, it appears that there is a lack of mechanism here to actually get a valid
> and functional MTU from TRILL in the cases where the Path MTU is below 1470. If
> I am wrong good, but I think this is an important piece for how to handle the
> next main issue.
>
> How about referencing Section 3 ofhttps://tools.ietf.org/html/draft-ietf-trill-mtu-negotiation-05
> which is currently in IETF Last Call? (The wording of that section is
> probably going to be improved based on an OPS review by Brian
> Carpenter.)
>
> I looked at this, and it appears to have the same issue, that it can't
> probe for MTU values below 1470.
>

I think the thing was that, before TRILL over IP, it would not have been
useful to determine an MTU below 1470. But there is no particular problem
in constructing a smaller MTU-probe PDUs and an RBridge receiving such a
PDU is generally required to respond with an equal length MTU-ack.

>    2) RB1 tries to send an MTU-probe padded to the size 1470.
>
>       a) If RB1 fails to receive an MTU-ack from RB2 after k tries, RB1
>          sets the "failed minimum MTU test" flag for RB2 in RB1's Hello
>          and stop.
>
>
> But, the algorithm clearly performs a binary search for the MTU. If
> one look at RFC 4821 one will notice that there are some additional considerations
> there how to make the probing better and robuster. But, cleary Trill has some other
> criterias for what is a success. Verification that Sz works appears sufficient,
> and there are no need to probe further upwards.
>
> UDP encapsulation and IP fragments.
>
>   ----------------------------------
>
> I see it as a big issue that UDP encapsulation is the native one, and that
> relies on IP fragmentation despite the need for reliable fragmentation. With
> the setup of having to support 1470 MTU on TRILL level some packets will be
> fragmented in many environments. That will lead to a lot of losses, and as
> discussed below a very big problem with middleboxes. The main problem here is
> that if one tries to rely on IP fragments one will have issues with packets
> ending up in black holes. And different problems depending on IPv4 or IPv6.
> IPv6 is lilkely the lesser problem assuming that one have working PMTUD.
>
> There are several ways out of this.
>
> 1. Detect issues and use TCP encapsulation with correctly set MSS to not get IP
> fragements 2. Determine MTU and implement an fragmentation mechanism on top of
> UDP.
>
> So, I don't see that much problem with UDP being the general default
> consistent with the TRILL philosophy of defaulting to need zero or
> minimal configuration. The default should be to use multicast Hellos
> for discovery of neighbors which sure points at UDP to me. Having to
> traverse a NAT should be a rare case. Since, in the NAT case, you have
> to configure things related to the static binding and the IP
> address(es) of peer(s) anyway you can also configure to use a
> different encapsulation than UDP, such as TCP, at the same time. I
> don't see it as much of a problem if, by default, TRILL won't operate
> through a NAT. If you are using UDP and it fragments and fragments are
> dropped at a NAT, probably you can't exchange Hellos so you will not
> form an adjacency and anything on the other side of the NAT will not
> be visible.
>
>
> Yes, but this is the issue of applicability and documenting that
> applicability. I don't know what goals and requirements that exist for
> Trill. If the WG are fine with some restrictions, then document them and
> focus on solving the issues that must be solved.
>
> You can clearly choose to require TCP for cases where the IP MTU is
> insufficient for carrying the Sz sized trill packets between the RBs using
> UDP.
>

OK.

> Zero Checksum:
> --------------
>
> Section 5.4:
>
> UDP Checksum - as specified in [RFC0768]
>
> Considering the fast path encapsulation desire, I am surprised to not see any
> mentioning of use of zero checksum here. Raising the zero checksum and forward
> reference would be good I think.
>
> And then Section 8.5:
>
>    The requirements for the usage of the zero UDP Checksum in a UDP
>    tunnel protocol are detailed in [RFC6936]. These requirements apply
>    to the UDP based TRILL over IP encapsulations specified herein
>    (native and VXLAN), which are applications of UDP tunnel.
>
> If you actually intended to allow zero checksum, then you actually should
> document that Trill fulfills the requirements that the applicability statement
> raises. I have not analyzed how well it meets these requirements.
>
> Please review Section 6.2 of RFC 8086 for example how that can be done.
>
> OK. We'll look into it.
>
>
> TCP Encapsulation issue
> -----------------------
>
> Section 5.6:
>
> The TCP encapsulation appear to be missing an delimiter format allowing each
> individual TRILL packet/payload to be read out of the TCP's byte stream. In
> other words, a normal implementation has no way of ensuring that the TCP
> payload starts with the start of a new TRILL payload. Multiple small TRILL
> payloads may be included in the same TCP payload, and also only parts as TCP is
> one way of dealing with TRILL packets that are larger than the IP+Encapsulation
> MTU that actually will work.
>
> This comment is based on that there appear to be no length fields included in
> the TRILL header. The most straight forward delimiter is a 2-byte length field
> for the TRILL payload to be encapsulated.
>
> Right. It might also be useful to include some sort of check field, as
> is done in BGP, to detect if you are out of sync in parsing the TCP
> stream.
>
> As you need to actually perform re-assembly, the solution is to use the
> byte stream semantics the TCP API provides and have a framing for each
> packet.
>

Of course.

My point was that the framing might usefully have some sort of flag field,
like the BGP framing has, so that there was a good chance of detecting if
the parsing of the byte stream into frames has gotten out of synch.

> Another point is that, while with UDP it seems fine to send packets
> with assorted QoS, you don't want to encourage re-ordering of TCP
> packets in a stream. So if TCP encapsulation is being used, you want
> to use the same DSCP value for the packets in a particular TCP stream.
> So, generally, you need to have a TCP connection per priority handling
> category. Mapping the 8 priority levels into a smaller number of
> handling categories is a normal thing to do so you certainly don't
> necessarily need 8 TCP connections. Adding material on this should not
> be too hard.
>
>
> Yes, agreed it is a possibility and points into possible considerations
> that David raised.
>
> Section 5.6:
>
> TCP endpoint requirements. I do wonder if an application like TRILL actual
> would need to discuss performance impacting implementation choices or
> limitations. For example use of NAGLE, the requirements on buffer sizes in
> relation to Bandwidth delay products, as buffer memory in a RBridge will impact
> performance.
>
> Well, I'm not sure how deeply this document should get into such
> performance issues. What about just saying something about
> consideration being given to tuning TCP for performance and pointing
> to one or a few other RFCs that talk about this?
>
>
> As Joe said, these are important considerations. If your intention is to
> enable this to run at substantial fractions of line rates of the
> interfaces. Then this do require considerations.
>

I see.

> Congestion Control
> ------------------
> First thanks for the effort here.
>
> You're welcome.
>
>
> 8.1.2 In Other Environments
>
>    Where UDP based encapsulation headers are used in TRILL over IP in
>    environments other than those discussed in Section 8.1.1, specific
>    congestion control mechanisms are commonly needed.  However, if the
>    traffic being carried by the TRILL over IP link is already congestion
>    controlled and the size and volatility of the TRILL IS-IS link state
>    database is limited, then specific congestion control may not be
>    needed. See [RFC8085] Section 3.1.11 for further guidance.
>
> This is correct, however my question is if the RBridges have any way of knowing
> which traffic is actually congestion controlled, considering that TRILL provides
> an layer 2 abstraction. I wonder if there should be any type of white list of
> the types of layer 2 payloads that can be assumed to be congestion controlled,
> and thus okay to forward over IP paths? I am worried that without any
> recommendation to prevent traffic that is not controlled to be forwarded, can
> lead to congestion issues.
>
> The other issue I think may exist is the issue serial unicast emulation of
> broadcast/multicast creates. As this amplifies the outgoing packet rate with
> a factor of how many addresses are configured for serial unicast this can
> be significant traffic expansion. Thus, I think additional considerations are
> needed here, and maybe rate limiting of the amount of traffic to be multicasted.
>
> OK. We can think about those issues.
>
>
> Flow and ECMP
> -------------
>
> Section 8.3:
>
> For example, for TRILL
>    Data, this entropy field could be based on some hash of the
>    Inner.MacDA, Inner.MacSA, and Inner.VLAN or Inner.FGL.
>
> I would appreciate clearer references to what these fields are.
>
> In a TRILL Data packet, the payload after the TRILL Header looks like
> an Ethernet frame except that there is always either a VLAN tag or,
> alternatively, where the VLAN tag would be, a Fine Grained Label
> [RFC7172]. (The preceding is the view in the TRILL RFCs, but there is
> an equivalent and equally valid view in which all the fields through
> and including the VLAN or FGL tag are part of the TRILL Header.) The
> TRILL base protocol specification focuses on Ethernet as a link
> technology between TRILL switches, in which case there will be a link
> header including an Outer.MacDA and Outer.MacSA fields and possibly an
> Outer.VLAN, all before the TRILL Header. See Figure 1 and Figure 2 in
> RFC 7172.
>
> Some of the above could be added to the draft for clarity.
>
>
> If I understand this correctly, the idea here is to look into the inner
> layer 2 frames, and use the flow equivalents that exists on that level and
> hash that into value that maps the flows onto the source port range.
>
> Yes.
>
>
> I think this text should include a summary of the principle and ensure to
> note the important requirement that what is considered flows in the inner
> must not result in being striped over multiple source ports as this may lead to
> reordering issues due to packets taking different paths.
>
> Well, we can add some text. But when would the relative ordering
> matter for two TRILL Data packets where the two inner native payloads
> have different values for any one or more of these three fields
> (Inner.MacDA, Inner.MacSA, and inner VLAN/FGL tag) ? If any of those
> fields are different, you are talking about different streams.
>
>
> Okay, then this is very straightforward.
>
> NAT and TRILL over IP:
> Section 8.5:
>
> If one like to use TRILL over IP through a NAT, then there are some very
> important considerations that are missing. First the need for static binding
> configurations or the need for determining ones external address(es) and be
> able to communicate that to the peer RBridges, and in addition ensure that one
> has keep-alives to that the NAT binding never times out.
>
> I think those are good points. There is an additional problem that
> TRILL Hellos detect neighbors with which they have 2-way connectivity
> by indicating, inside the Hellos that are sent, from what neighbors
> Hellos have been received on that port. If a NAT is involved, these
> neighbor addresses inside Hellos need to be mapped.
>
> Yes, and the question is how that can be handled, by the receiver of the
> packet, or if the sender needs to determine what address it uses and
> provide that in the HELLOs. If the first is possible that can simplify a
> lot.
>

I'm not sure. this would require a little detailed design work.

> Next is the issue that there is almost zero chance of getting a IP/UDP
> encapsulation TRILL payload through the NAT if it results in IP fragmentation,
> as NATs don't do defragment and refragmented on the internal side, and an IP
> fragment lacks UDP port and thus can't be matched to binding.
>
> So perhaps the recommendation should be to configure the port to use
> TCP if there will be fragmentation.
>
> Yes, I think that are likely the simplest solution for you.
>

OK

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

Also if you like to run IP/ESP through a NAT, then you most likely need the
> IP/UDP/ESP encapsulation (https://tools.ietf.org/html/rfc3948). Note that this
> will restrict the MTU even further and thus ensure that the 1470 requirement
> cannot be fulfilled even without additional tunnels over an 1500 bytes MTU
> Ethernet infrastructure.
>
> I would note that also firewalls likely have issues with IP fragments for the
> same reason, they require significant amount of state to be verified if they
> should be let through.
>
> In general I think you should create a configuration that has chance to work
> through most middleboxes, but I think you should require static bindings. I
> think that configuration is, and don't laugh now, but IP/UDP/ESP/TCP/TRILL,
> otherwise you will not be able to have both security and reliable fragmentation
> of TRILL packets.
>
> OK. Thanks again for this review. It has pointed out a number of
> problems and in thinking about those, I believe a couple of further
> problems have come to mind that I mentioned above. We'll work on a
> revised draft.
>
>
>
> Cheers
>
> Magnus Westerlund
>
> ----------------------------------------------------------------------
> Media Technologies, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287 <+46%2010%20714%2082%2087>
> Torshamnsgatan 23           | Mobile +46 73 0949079 <+46%2073%20094%2090%2079>
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>

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

<div dir=3D"ltr">HI Magnus,<div><br></div><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote">On Tue, Jun 27, 2017 at 1:13 PM, Magnus Westerlund <sp=
an dir=3D"ltr">&lt;<a href=3D"mailto:magnus.westerlund@ericsson.com" target=
=3D"_blank">magnus.westerlund@ericsson.<wbr>com</a>&gt;</span> wrote:<br><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 bgcolor=3D"#FFFFFF">
<div class=3D"gmail-m_-2274122840677479759gmail-m_-1728329784390160147moz-c=
ite-prefix">Hi Donald,<br>
<br>
After having read your response I think there is an important question abou=
t the applicability of this document that affects several of the issues bel=
ow and what solution you need. That is the question of what type of paths o=
ne expect to get Trill over IP working
 over. Because if the target is general Internet and also through middlebox=
es such as NATs and Firewall (Not intending to block) then there are a lot =
more work to ensure this. If you for example changes the applicability to r=
equire any on path middleboxes to
 fulfill certain requirements things can be more easily addressed. </div></=
div></blockquote><div><br></div><div>The use cases in the document support =
communication over the general Internet in the brach office case but that d=
oes not necessarily imply NATs/Firewalls.</div><div><br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div bgcolor=3D"#FFFFFF"><div class=3D=
"gmail-m_-2274122840677479759gmail-m_-1728329784390160147moz-cite-prefix"><=
span class=3D"gmail-m_-2274122840677479759gmail-">
Den 2017-06-26 kl. 02:07, skrev Donald Eastlake:<br>
</span></div>
<blockquote type=3D"cite"><span class=3D"gmail-m_-2274122840677479759gmail-=
">
<pre>Hi Magnus,

Thanks for the extensive review. See my responses below.

On Thu, Jun 15, 2017 at 1:32 PM, Magnus Westerlund
<a class=3D"gmail-m_-2274122840677479759gmail-m_-1728329784390160147moz-txt=
-link-rfc2396E" href=3D"mailto:magnus.westerlund@ericsson.com" target=3D"_b=
lank">&lt;magnus.westerlund@ericsson.co<wbr>m&gt;</a> wrote:
</pre>
<br>
</span><span class=3D"gmail-m_-2274122840677479759gmail-"><blockquote type=
=3D"cite">
<pre>Diffserv usage
--------------

Section 4.3:

   TRILL over IP implementations MUST support setting the DSCP value in
   the outer IP Header of TRILL packets they send by mapping the TRILL
   priority and DEI to the DSCP. They MAY support, for a TRILL Data
   packet where the native frame payload is an IP packet, mapping the
   DSCP in this inner IP packet to the outer IP Header with the default
   for that mapping being to copy the DSCP without change.

I think it is fine to require that implementations are capable  of setting
DSCP values on the outer IP header. However, I fail to see any discussion o=
f
the potential issues with actually setting the DSCP values. It is one thing=
 to
do this in an IP back bone use case where one can know and have control ove=
r
the PHB that the DSCP values maps to. But otherwise, over general internet =
the
behavior is not that predictable. One can easily be subject to policers or
remapping. Also as the actual DSCP code point usage is domain specific this=
 is
difficult. Priority reversal is likely the least of the problems that this =
can
run into over general Internet.
</pre>
</blockquote>
<pre>It sounds like appropriate discussion and warnings about these issues
would resolve the above comment.</pre></span></blockquote>
I would note that the choice of encapsulation here do becomes important. Yo=
ur&#39;s and Joe Touch&#39;s observation that for TCP, you can only have a =
single DSCP marking per TCP connection for example. For others, see the dis=
cussion in Section 5.1 of
<a class=3D"gmail-m_-2274122840677479759gmail-m_-1728329784390160147moz-txt=
-link-freetext" href=3D"https://datatracker.ietf.org/doc/rfc7657/" target=
=3D"_blank">
https://datatracker.ietf.org/d<wbr>oc/rfc7657/</a> on this issue. <br></div=
></blockquote><div><br></div><div>Well, if a TRILL over IP implementation u=
sing TCP transport wants to have more than one priority category for traffi=
c where there might be one or more intervening IP routers, which would be t=
he normal case, it would just need a TCP connection per priority category. =
Mapping the 8 priority levels into a smaller number of categories is a rout=
ine thing to do. Note that the base TRILL protocol specification (RFC 6325)=
 says:</div><div><br></div><pre class=3D"gmail-m_-2274122840677479759gmail-=
newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;colo=
r:rgb(0,0,0)">   RBridges are not required to implement any
   particular number of distinct priority levels but may treat one or=C2=A0=
</pre><div><span style=3D"color:rgb(0,0,0);font-size:13.3333px"><font face=
=3D"monospace, monospace">=C2=A0 =C2=A0more adjacent priority levels in the=
 same fashion.</font></span></div><div>=C2=A0</div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex"><div bgcolor=3D"#FFFFFF">
David Black also raised an important question if one should treat this as a=
 tunnel with a single predictable behavior or let the inner networks markin=
g show through. Establishing a tunnel with a single PHB has less risk of ru=
nning into issues than multiple
 different markings.=C2=A0</div></blockquote><div><br></div><div>It is an i=
mplementation choice whether to have a single PHB or eight, one per priorit=
y level, or something in between.=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div bgcolor=3D"#FFFFFF"><div><div class=3D"gmail-m_-22=
74122840677479759gmail-h5">
<blockquote type=3D"cite">
<pre></pre>
<blockquote type=3D"cite">
<pre>Section 4.3:

   The default TRILL priority and DEI to DSCP mapping, which may be
   configured per TRILL over IP port, is an follows. Note that the DEI
   value does not affect the default mapping and, to provide a
   potentially lower priority service than the default priority 0,
   priority 1 is considered lower priority than 0. So the priority
   sequence from lower to higher priority is 1, 0, 2, 3, 4, 5, 6, 7.

      TRILL Priority  DEI  DSCP Field (Binary/decimal)
      --------------  ---  -----------------------------
                  0   0/1  001000 / 8
                  1   0/1  000000 / 0
                  2   0/1  010000 / 16
                  3   0/1  011000 / 24
                  4   0/1  100000 / 32
                  5   0/1  101000 / 40
                  6   0/1  110000 / 48
                  7   0/1  111000 / 56

This appear to be an problematic mapping. At least for prio 0 and 1. As
priority 1 appears to be intended to be higher than priority 0, it is
interesting that it is mapped to CS1, which to quote
<a class=3D"gmail-m_-2274122840677479759gmail-m_-1728329784390160147moz-txt=
-link-freetext" href=3D"https://datatracker.ietf.org/doc/rfc7657/" target=
=3D"_blank">https://datatracker.ietf.org/d<wbr>oc/rfc7657/</a>:

CS1 (&#39;001000&#39;) was subsequently designated as the recommended
      codepoint for the Lower Effort (LE) PHB [RFC3662].

So what is proposed can in a network using default mapping, result in that =
you
get priority 0 to be lower priority than 1. Plus that in some networks this=
 can
also results in strange remapping that results in a different PHB for CS1 t=
han.
</pre>
</blockquote>
<pre>The intent in the draft is to reflect the default relative priority of
the different priority code points in IEEE Std 802.1Q where priority 1
is lower than priority 0. At a quick look, it appears to me that RFC
2474 requires that 0x001000 be handled as being of a priority not
lower than the priority with which 0x000000 is handled. Yet RFC 3662,
which you point to, seems to suggest using 0x001000 as a lower
priority code point than 0x000000. Given that 3662 not only does not
update 2474 but is only Informational while 2474 is Standards Track, I
would say that 2474 dominates and that this draft makes the best
assumptions it can about default behavior...</pre>
</blockquote>
<br></div></div>
David Black provide a good answer on this. </div></blockquote><div>=C2=A0</=
div><div>I&#39;ll reply to him.</div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div bgcolor=3D"#FFFFFF"><span class=3D"gmail-m_-22741228406774=
79759gmail-">
<blockquote type=3D"cite">
<pre></pre>
<blockquote type=3D"cite">
<pre>MTU and Fragmentation
---------------------

I think there are two main issue here. The first one is MTUD discovery
of the actual IP path MTU between the ports. That will be needed to prevent
a lot of traffic going into MTU black holes. Especially as TRILL requries
1470 byte support which is likey above a lot of paths.
</pre>
</blockquote>
<pre>Seems like it would depend on the environments where TRILL was used.
For example, I do not think 1470 would be a problem in most Data
Center or Internet Exchange point uses, for example. Data Centers
sometimes support 9K jumbo frames and the like.

In fact, it is probably bad to focus too much on 1470 -- that is a
required minimum to be sure that reasonable size link state PDUs can
be successfully flooded through the TRILL campus so that routing will
work. However, it would commonly be the case that, for the TRILL
campus to be useful in a particular case, links need to be able to
carry the expected size TRILL Data packets. For example, if there were
two parts of a TRILL campus connected by one or a few TRILL over IP
links and the end stations in each part were assuming they could use
1500 byte Ethernet packets, then the TRILL over IP links would need to
support an MTU based on 1500 + TRILL Header + IP and TRILL over IP
encapsulation. And more if security was being used or there were any
other reasons for additional headers/encapsulation...</pre>
</blockquote>
<br></span>
Yes, and over general Internet you should be happy if you get 1500 bytes of=
 IP MTU, it may easily be lower with a couple of additional tunnel headers.=
 Thus, what you say is the goal is not feasible without a solution that sup=
ports fragmentation and reassembly,
 enabling one TRILL packet to be sent in multiple IP packets. The re-assemb=
ly do requires buffering and not something to easily perform on a router fa=
st path. And attempting to use IP fragmentation is likely doomed if you hav=
e any type of NAT or Firewall in
 the way. <br>
<br>
This points to a dedicated solution or using a transport protocol that supp=
orts carrying arbitrary data sizes, like TCP or SCTP. And you need to use t=
he byte-stream API of TCP to achieve this.
</div></blockquote><div>=C2=A0</div><div>OK.</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div bgcolor=3D"#FFFFFF"><span class=3D"gmail-m_-2=
274122840677479759gmail-">
<blockquote type=3D"cite">
<pre></pre>
<blockquote type=3D"cite">
<pre>Section 8.4:

   Path MTU discovery [RFC4821] should be useful
   in determining the IP MTU between a pair of RBridge ports with IP
   connectivity.

The issue with RFC4821 is that it has requirements on the packetization lay=
er.
Trill appears to have several components that are useful. However, it will
require a specification of the procedure to result in a useful tool.
</pre>
</blockquote>
<pre>See below.

</pre>
<blockquote type=3D"cite">
<pre>Section 8.4:

   TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
   [RFC7177], can be used to obtain added assurance of the MTU of a
   link.

Yes, that can confirm working MTUs that are at 1470 or above, but appears
prevented from working below 1470?
</pre>
</blockquote>
<pre>While there is a minimum size for TRILL IS-IS MTU PDUs, determined by
header size, it is well below 1470, probably (depending on whether
secuirty is in use, etc.) below 150 bytes.</pre>
</blockquote>
<br></span>
Okay, if you say so, it was not obvious from the spec that is was allowed t=
o probe for paths with lesser MTUs than 1470.
<span class=3D"gmail-m_-2274122840677479759gmail-"><br>
<blockquote type=3D"cite">
<pre></pre>
<blockquote type=3D"cite">
<pre>Thus, it appears that there is a lack of mechanism here to actually ge=
t a valid
and functional MTU from TRILL in the cases where the Path MTU is below 1470=
. If
I am wrong good, but I think this is an important piece for how to handle t=
he
next main issue.
</pre>
</blockquote>
<pre>How about referencing Section 3 of
<a class=3D"gmail-m_-2274122840677479759gmail-m_-1728329784390160147moz-txt=
-link-freetext" href=3D"https://tools.ietf.org/html/draft-ietf-trill-mtu-ne=
gotiation-05" target=3D"_blank">https://tools.ietf.org/html/dr<wbr>aft-ietf=
-trill-mtu-negotiation<wbr>-05</a>
which is currently in IETF Last Call? (The wording of that section is
probably going to be improved based on an OPS review by Brian
Carpenter.)</pre></blockquote></span>
I looked at this, and it appears to have the same issue, that it can&#39;t =
probe for MTU values below 1470.
<br></div></blockquote><div><br></div><div>I think the thing was that, befo=
re TRILL over IP, it would not have been useful to determine an MTU below 1=
470. But there is no particular problem in constructing a smaller MTU-probe=
 PDUs and an RBridge receiving such a PDU is generally required to respond =
with an equal length MTU-ack.=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 bgcolor=3D"#FFFFFF">
<pre class=3D"gmail-m_-2274122840677479759gmail-m_-1728329784390160147newpa=
ge">   2) RB1 tries to send an MTU-probe padded to the size 1470.

      a) If RB1 fails to receive an MTU-ack from RB2 after k tries, RB1
         sets the &quot;failed minimum MTU test&quot; flag for RB2 in RB1&#=
39;s Hello
         and stop.


But, the algorithm clearly performs a binary search for the MTU. If=20
one look at RFC 4821 one will notice that there are some additional conside=
rations
there how to make the probing better and robuster. But, cleary Trill has so=
me other
criterias for what is a success. Verification that Sz works appears suffici=
ent,=20
and there are no need to probe further upwards. </pre><div><div class=3D"gm=
ail-m_-2274122840677479759gmail-h5">
<blockquote type=3D"cite">
<pre></pre>
<blockquote type=3D"cite">
<pre>UDP encapsulation and IP fragments.
</pre>
</blockquote>
<pre>  ------------------------------<wbr>----
</pre>
<blockquote type=3D"cite">
<pre>I see it as a big issue that UDP encapsulation is the native one, and =
that
relies on IP fragmentation despite the need for reliable fragmentation. Wit=
h
the setup of having to support 1470 MTU on TRILL level some packets will be
fragmented in many environments. That will lead to a lot of losses, and as
discussed below a very big problem with middleboxes. The main problem here =
is
that if one tries to rely on IP fragments one will have issues with packets
ending up in black holes. And different problems depending on IPv4 or IPv6.
IPv6 is lilkely the lesser problem assuming that one have working PMTUD.

There are several ways out of this.

1. Detect issues and use TCP encapsulation with correctly set MSS to not ge=
t IP
fragements 2. Determine MTU and implement an fragmentation mechanism on top=
 of
UDP.
</pre>
</blockquote>
<pre>So, I don&#39;t see that much problem with UDP being the general defau=
lt
consistent with the TRILL philosophy of defaulting to need zero or
minimal configuration. The default should be to use multicast Hellos
for discovery of neighbors which sure points at UDP to me. Having to
traverse a NAT should be a rare case. Since, in the NAT case, you have
to configure things related to the static binding and the IP
address(es) of peer(s) anyway you can also configure to use a
different encapsulation than UDP, such as TCP, at the same time. I
don&#39;t see it as much of a problem if, by default, TRILL won&#39;t opera=
te
through a NAT. If you are using UDP and it fragments and fragments are
dropped at a NAT, probably you can&#39;t exchange Hellos so you will not
form an adjacency and anything on the other side of the NAT will not
be visible.</pre>
</blockquote>
<br></div></div>
Yes, but this is the issue of applicability and documenting that applicabil=
ity. I don&#39;t know what goals and requirements that exist for Trill. If =
the WG are fine with some restrictions, then document them and focus on sol=
ving the issues that must be solved.
<br>
<br>
You can clearly choose to require TCP for cases where the IP MTU is insuffi=
cient for carrying the Sz sized trill packets between the RBs using UDP.=C2=
=A0</div></blockquote><div>=C2=A0</div><div>OK.</div><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 bgcolor=3D"#FFFFFF"><div><div class=3D"gma=
il-m_-2274122840677479759gmail-h5">
<blockquote type=3D"cite">
<pre></pre>
<blockquote type=3D"cite">
<pre>Zero Checksum:
--------------

Section 5.4:

UDP Checksum - as specified in [RFC0768]

Considering the fast path encapsulation desire, I am surprised to not see a=
ny
mentioning of use of zero checksum here. Raising the zero checksum and forw=
ard
reference would be good I think.

And then Section 8.5:

   The requirements for the usage of the zero UDP Checksum in a UDP
   tunnel protocol are detailed in [RFC6936]. These requirements apply
   to the UDP based TRILL over IP encapsulations specified herein
   (native and VXLAN), which are applications of UDP tunnel.

If you actually intended to allow zero checksum, then you actually should
document that Trill fulfills the requirements that the applicability statem=
ent
raises. I have not analyzed how well it meets these requirements.

Please review Section 6.2 of RFC 8086 for example how that can be done.
</pre>
</blockquote>
<pre>OK. We&#39;ll look into it.

</pre>
<blockquote type=3D"cite">
<pre>TCP Encapsulation issue
-----------------------

Section 5.6:

The TCP encapsulation appear to be missing an delimiter format allowing eac=
h
individual TRILL packet/payload to be read out of the TCP&#39;s byte stream=
. In
other words, a normal implementation has no way of ensuring that the TCP
payload starts with the start of a new TRILL payload. Multiple small TRILL
payloads may be included in the same TCP payload, and also only parts as TC=
P is
one way of dealing with TRILL packets that are larger than the IP+Encapsula=
tion
MTU that actually will work.

This comment is based on that there appear to be no length fields included =
in
the TRILL header. The most straight forward delimiter is a 2-byte length fi=
eld
for the TRILL payload to be encapsulated.
</pre>
</blockquote>
<pre>Right. It might also be useful to include some sort of check field, as
is done in BGP, to detect if you are out of sync in parsing the TCP
stream.</pre></blockquote></div></div>
As you need to actually perform re-assembly, the solution is to use the byt=
e stream semantics the TCP API provides and have a framing for each packet.
</div></blockquote><div>=C2=A0</div><div>Of course.</div><div><br></div><di=
v>My point was that the framing might usefully have some sort of flag field=
, like the BGP framing has, so that there was a good chance of detecting if=
 the parsing of the byte stream into frames has gotten out of synch.</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"><div bgcolor=3D"#FFFFFF"><=
span class=3D"gmail-m_-2274122840677479759gmail-">
<blockquote type=3D"cite">
<pre>Another point is that, while with UDP it seems fine to send packets
with assorted QoS, you don&#39;t want to encourage re-ordering of TCP
packets in a stream. So if TCP encapsulation is being used, you want
to use the same DSCP value for the packets in a particular TCP stream.
So, generally, you need to have a TCP connection per priority handling
category. Mapping the 8 priority levels into a smaller number of
handling categories is a normal thing to do so you certainly don&#39;t
necessarily need 8 TCP connections. Adding material on this should not
be too hard.</pre>
</blockquote>
<br></span>
Yes, agreed it is a possibility and points into possible considerations tha=
t David raised.
<br><span class=3D"gmail-m_-2274122840677479759gmail-">
<br>
<blockquote type=3D"cite">
<pre></pre>
<blockquote type=3D"cite">
<pre>Section 5.6:

TCP endpoint requirements. I do wonder if an application like TRILL actual
would need to discuss performance impacting implementation choices or
limitations. For example use of NAGLE, the requirements on buffer sizes in
relation to Bandwidth delay products, as buffer memory in a RBridge will im=
pact
performance.
</pre>
</blockquote>
<pre>Well, I&#39;m not sure how deeply this document should get into such
performance issues. What about just saying something about
consideration being given to tuning TCP for performance and pointing
to one or a few other RFCs that talk about this?</pre>
</blockquote>
<br></span>
As Joe said, these are important considerations. If your intention is to en=
able this to run at substantial fractions of line rates of the interfaces. =
Then this do require considerations.=C2=A0</div></blockquote><div><br></div=
><div>I see.=C2=A0</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"><=
div bgcolor=3D"#FFFFFF"><div><div class=3D"gmail-m_-2274122840677479759gmai=
l-h5">
<blockquote type=3D"cite">
<pre></pre>
<blockquote type=3D"cite">
<pre>Congestion Control
------------------
First thanks for the effort here.
</pre>
</blockquote>
<pre>You&#39;re welcome.

</pre>
<blockquote type=3D"cite">
<pre>8.1.2 In Other Environments

   Where UDP based encapsulation headers are used in TRILL over IP in
   environments other than those discussed in Section 8.1.1, specific
   congestion control mechanisms are commonly needed.  However, if the
   traffic being carried by the TRILL over IP link is already congestion
   controlled and the size and volatility of the TRILL IS-IS link state
   database is limited, then specific congestion control may not be
   needed. See [RFC8085] Section 3.1.11 for further guidance.

This is correct, however my question is if the RBridges have any way of kno=
wing
which traffic is actually congestion controlled, considering that TRILL pro=
vides
an layer 2 abstraction. I wonder if there should be any type of white list =
of
the types of layer 2 payloads that can be assumed to be congestion controll=
ed,
and thus okay to forward over IP paths? I am worried that without any
recommendation to prevent traffic that is not controlled to be forwarded, c=
an
lead to congestion issues.

The other issue I think may exist is the issue serial unicast emulation of
broadcast/multicast creates. As this amplifies the outgoing packet rate wit=
h
a factor of how many addresses are configured for serial unicast this can
be significant traffic expansion. Thus, I think additional considerations a=
re
needed here, and maybe rate limiting of the amount of traffic to be multica=
sted.
</pre>
</blockquote>
<pre>OK. We can think about those issues.

</pre>
<blockquote type=3D"cite">
<pre>Flow and ECMP
-------------

Section 8.3:

For example, for TRILL
   Data, this entropy field could be based on some hash of the
   Inner.MacDA, Inner.MacSA, and Inner.VLAN or Inner.FGL.

I would appreciate clearer references to what these fields are.
</pre>
</blockquote>
<pre>In a TRILL Data packet, the payload after the TRILL Header looks like
an Ethernet frame except that there is always either a VLAN tag or,
alternatively, where the VLAN tag would be, a Fine Grained Label
[RFC7172]. (The preceding is the view in the TRILL RFCs, but there is
an equivalent and equally valid view in which all the fields through
and including the VLAN or FGL tag are part of the TRILL Header.) The
TRILL base protocol specification focuses on Ethernet as a link
technology between TRILL switches, in which case there will be a link
header including an Outer.MacDA and Outer.MacSA fields and possibly an
Outer.VLAN, all before the TRILL Header. See Figure 1 and Figure 2 in
RFC 7172.

Some of the above could be added to the draft for clarity.

</pre>
<blockquote type=3D"cite">
<pre>If I understand this correctly, the idea here is to look into the inne=
r
layer 2 frames, and use the flow equivalents that exists on that level and
hash that into value that maps the flows onto the source port range.
</pre>
</blockquote>
<pre>Yes.

</pre>
<blockquote type=3D"cite">
<pre>I think this text should include a summary of the principle and ensure=
 to
note the important requirement that what is considered flows in the inner
must not result in being striped over multiple source ports as this may lea=
d to
reordering issues due to packets taking different paths.
</pre>
</blockquote>
<pre>Well, we can add some text. But when would the relative ordering
matter for two TRILL Data packets where the two inner native payloads
have different values for any one or more of these three fields
(Inner.MacDA, Inner.MacSA, and inner VLAN/FGL tag) ? If any of those
fields are different, you are talking about different streams.</pre>
</blockquote>
<br></div></div>
Okay, then this is very straightforward. <br><span class=3D"gmail-m_-227412=
2840677479759gmail-">
<br>
<blockquote type=3D"cite">
<pre></pre>
<blockquote type=3D"cite">
<pre>NAT and TRILL over IP:
Section 8.5:

If one like to use TRILL over IP through a NAT, then there are some very
important considerations that are missing. First the need for static bindin=
g
configurations or the need for determining ones external address(es) and be
able to communicate that to the peer RBridges, and in addition ensure that =
one
has keep-alives to that the NAT binding never times out.
</pre>
</blockquote>
<pre>I think those are good points. There is an additional problem that
TRILL Hellos detect neighbors with which they have 2-way connectivity
by indicating, inside the Hellos that are sent, from what neighbors
Hellos have been received on that port. If a NAT is involved, these
neighbor addresses inside Hellos need to be mapped.</pre></blockquote></spa=
n>
Yes, and the question is how that can be handled, by the receiver of the pa=
cket, or if the sender needs to determine what address it uses and provide =
that in the HELLOs. If the first is possible that can simplify a lot.
</div></blockquote><div>=C2=A0</div><div>I&#39;m not sure. this would requi=
re a little detailed design work.</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div bgcolor=3D"#FFFFFF"><span class=3D"gmail-m_-227412284067=
7479759gmail-">
<blockquote type=3D"cite">
<pre></pre>
<blockquote type=3D"cite">
<pre>Next is the issue that there is almost zero chance of getting a IP/UDP
encapsulation TRILL payload through the NAT if it results in IP fragmentati=
on,
as NATs don&#39;t do defragment and refragmented on the internal side, and =
an IP
fragment lacks UDP port and thus can&#39;t be matched to binding.
</pre>
</blockquote>
<pre>So perhaps the recommendation should be to configure the port to use
TCP if there will be fragmentation.</pre></blockquote></span>
Yes, I think that are likely the simplest solution for you. <br></div></blo=
ckquote><div><br></div><div>OK=C2=A0</div><div><br></div><div><div>Thanks,<=
/div><div>Donald</div><div>=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>=C2=A0Donald E. Eastlake =
3rd =C2=A0 +1-508-333-2270 (cell)</div><div>=C2=A0155 Beaver Street, Milfor=
d, MA 01757 USA</div><div>=C2=A0<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@=
gmail.com</a></div></div><div><br></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"><div bgcolor=3D"#FFFFFF"><span class=3D"gmail-m_-22741228406=
77479759gmail-"><blockquote type=3D"cite"><blockquote type=3D"cite"><pre>Al=
so if you like to run IP/ESP through a NAT, then you most likely need the
IP/UDP/ESP encapsulation (<a class=3D"gmail-m_-2274122840677479759gmail-m_-=
1728329784390160147moz-txt-link-freetext" href=3D"https://tools.ietf.org/ht=
ml/rfc3948" target=3D"_blank">https://tools.ietf.org/html/r<wbr>fc3948</a>)=
. Note that this
will restrict the MTU even further and thus ensure that the 1470 requiremen=
t
cannot be fulfilled even without additional tunnels over an 1500 bytes MTU
Ethernet infrastructure.

I would note that also firewalls likely have issues with IP fragments for t=
he
same reason, they require significant amount of state to be verified if the=
y
should be let through.

In general I think you should create a configuration that has chance to wor=
k
through most middleboxes, but I think you should require static bindings. I
think that configuration is, and don&#39;t laugh now, but IP/UDP/ESP/TCP/TR=
ILL,
otherwise you will not be able to have both security and reliable fragmenta=
tion
of TRILL packets.
</pre>
</blockquote>
<pre>OK. Thanks again for this review. It has pointed out a number of
problems and in thinking about those, I believe a couple of further
problems have come to mind that I mentioned above. We&#39;ll work on a
revised draft.


</pre>
</blockquote>
</span><pre class=3D"gmail-m_-2274122840677479759gmail-m_-17283297843901601=
47moz-signature" cols=3D"72">Cheers=20

Magnus Westerlund=20

------------------------------<wbr>------------------------------<wbr>-----=
-----
Media Technologies, Ericsson Research
------------------------------<wbr>------------------------------<wbr>-----=
-----
Ericsson AB                 | Phone  <a href=3D"tel:+46%2010%20714%2082%208=
7" value=3D"+46107148287" target=3D"_blank">+46 10 7148287</a>
Torshamnsgatan 23           | Mobile <a href=3D"tel:+46%2073%20094%2090%207=
9" value=3D"+46730949079" target=3D"_blank">+46 73 0949079</a>
SE-164 80 Stockholm, Sweden | mailto: <a class=3D"gmail-m_-2274122840677479=
759gmail-m_-1728329784390160147moz-txt-link-abbreviated" href=3D"mailto:mag=
nus.westerlund@ericsson.com" target=3D"_blank">magnus.westerlund@ericsson.c=
om</a>
------------------------------<wbr>------------------------------<wbr>-----=
-----</pre>
</div>

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

--001a1141bcbec246930553240434--


From nobody Thu Jun 29 20:12:45 2017
Return-Path: <jagao@outlook.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 528BC127F0E for <ietf@ietfa.amsl.com>; Thu, 29 Jun 2017 20:12:44 -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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outlook.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uelaZQI9xSSy for <ietf@ietfa.amsl.com>; Thu, 29 Jun 2017 20:12:42 -0700 (PDT)
Received: from APC01-HK2-obe.outbound.protection.outlook.com (mail-oln040092255012.outbound.protection.outlook.com [40.92.255.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 277CA126C2F for <ietf@ietf.org>; Thu, 29 Jun 2017 20:12:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=SIqDYqhvwDdpzT8imPhmq7RZI+Gh4vQeQPc0h/dzy7c=; b=U00d05eEGvn9NdeGJ4QIKubMIYofiX4WtWYuivWZFT8MYwKU60+E5yi8m8FD+0ZLa4446IorldDX5Vs8UMj8upNPOe+wMXAbQxXO79Z1roJ0GJx1xzqTFN7mY7AQSKIxCE8SLnOoeuea8LL8EtJpWmBdBHMRLaD+simM3hOWw+AmMekzCpfoFi7218fD9l5gNw5MZSMK9SKzFjB1Uh0LznViPOl6aEMlsxOwNxp0iyo3RXu/Hamdi2TV272GXmPX3M4p/HmT086IxG/5ezGSewdVSthLhScVnUYv29mLmtFQAMVvLHaMcq+iSjmi/tfeGrg792mX0kDxrO2demEujw==
Received: from SG2APC01FT038.eop-APC01.prod.protection.outlook.com (10.152.250.55) by SG2APC01HT202.eop-APC01.prod.protection.outlook.com (10.152.251.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.1.1199.9; Fri, 30 Jun 2017 03:12:40 +0000
Received: from SG2PR03MB1470.apcprd03.prod.outlook.com (10.152.250.59) by SG2APC01FT038.mail.protection.outlook.com (10.152.251.98) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1199.9 via Frontend Transport; Fri, 30 Jun 2017 03:12:39 +0000
Received: from SG2PR03MB1470.apcprd03.prod.outlook.com ([fe80::2c3b:f354:dc7e:5831]) by SG2PR03MB1470.apcprd03.prod.outlook.com ([fe80::2c3b:f354:dc7e:5831%14]) with mapi id 15.01.1240.006; Fri, 30 Jun 2017 03:12:39 +0000
From: ? ?? <jagao@outlook.com>
To: "ietf@ietf.org" <ietf@ietf.org>
Subject: An idea about Flexible Session Protocol
Thread-Topic: An idea about Flexible Session Protocol
Thread-Index: AdLxTdEyd88kgUToQge4NpzjkzoFIw==
Date: Fri, 30 Jun 2017 03:12:39 +0000
Message-ID: <SG2PR03MB1470EB0E0BA239DA1E21B9ADBED30@SG2PR03MB1470.apcprd03.prod.outlook.com>
Accept-Language: zh-CN, 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=outlook.com;
x-incomingtopheadermarker: OriginalChecksum:66BD9E79361887FD9D208A9DD0ADFCBDF03A2BFE0EC2C3F7E3167A45E578E980; UpperCasedChecksum:E5943929B78BE8EE523610B515A2C64CBD292A4261D782991DFD38D62ABD13C1; SizeAsReceived:7038; Count:42
x-tmn: [fWeeSC+MFMqZAmAUGnOc/BfCXWtHckkY]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SG2APC01HT202; 7:kvWzVupnyJP/C8hYKQ1ChOiNUw36nkGhq94etVsrPxf84BT1yHWkkOPN4RCA+0V+3MTSIJgKnyhid4E/hV+QIvof/F9BDZftceCbaD2DImH/KwTv0l83WhNwpqJyPId9CnfBK9MVWXgdQUe0mkF76I9EkzR2lGtb8ar9TUCEauuElkPJoMn6M5s308NIvIwPHw1cPLdiHx3tJvhf3sQh74bCxyTnFHpHBf+766jKpKVYBamSqxQ//780PbcbqDBV7sUL9RFoLFuGssFmi/mc/aFazCD4gxJoKjJEsIkMbGB40ya7DlUz/WqpGuEwfJleCzeWlSN+yep6eFjMsWiNYEFY/yqQoen+yGOPRpQW25DDrQQXNt1jhxz7du0mFq4L1Vdv8yGeD4ZhANt38Tx2CrQErll59qOQilW6DmjyWlSUHMmvDVQ3DvgwIFDfgFHrLQ/9paN7GoWGHxry22QXY3drfov/ZEDj4suD3NosteFDlgXfzaOJkoNVhfel82k1hxMtquaNaZLRsd+W59PjUfjXi2UC/u2OsEAu8QhNURsGjhLQY0nKl2wreiD4FBk4WnAFNp+F5ueBEAEZsHenkiB/XBYzkbCn9evM/1JIvmlBJk9Gh/xsz1zQ9fAaj1F727JCekuHwpXKP81UF/n5VPQhSBOFKoD6ZR038e00qJdzg2yrp6YMO8GvH/y+I2Qrbg/QBv73NPBIkD7ppt3jGDGHNo2jgUvbgyipTYccHeQdXcaiZszmT3lqEgDWHaV+QB5nFdc/PsmeNF39DdvMlw==
x-incomingheadercount: 42
x-eopattributedmessage: 0
x-forefront-antispam-report: EFV:NLI; SFV:NSPM; SFS:(7070007)(98901004); DIR:OUT; SFP:1901; SCL:1; SRVR:SG2APC01HT202; H:SG2PR03MB1470.apcprd03.prod.outlook.com; FPR:; SPF:None; LANG:en; 
x-ms-office365-filtering-correlation-id: 0f191885-b131-464d-8214-08d4bf65ddcd
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(300000503095)(300135400095)(201702061074)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031324274)(2017031323274)(2017031322274)(1601125374)(1603101448)(1701031045)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:SG2APC01HT202; 
x-ms-traffictypediagnostic: SG2APC01HT202:
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(444000031); SRVR:SG2APC01HT202; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:SG2APC01HT202; 
x-forefront-prvs: 0354B4BED2
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jun 2017 03:12:39.6011 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SG2APC01HT202
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uKPqEDoZ2LsgrswIqzMOR8ebHKw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 03:12:44 -0000

Hello,

I have an idea about Flexible Session Protocol, and wrote a preliminary con=
cept implementation available at https://github.com/jaglee/FSP

Abstract:

FSP is a connection-oriented transport layer protocol that provides mobilit=
y, multihoming and multipath support by introducing the concept of 'upper l=
ayer thread ID', which was firstly suggested in [Gao2002] <https://mailarch=
ive.ietf.org/arch/msg/ietf/u-6i-6f-Etuvh80-SUuRbSCDTwg>

Authencity of an FSP packet is usually crytographically protected by some a=
lgorithm that requires a shared secret key. The upper layer thread ID is as=
signed roughly the same semantics as the Security Parameter Index (SPI) in =
MOBIKE [RFC4555] to index the secret key. The secret key is assumed to be i=
nstalled by the upper layer application.

FSP facilitates such secret key installation by introducing the concept of =
'transmit transaction', which makes it flexible for the application layer p=
rotocols to adopt wide range of key establishment algorithm.


I wonder if it could resolve some concerns in research.


Best Regards,

Jason Gao


From nobody Thu Jun 29 22:32:09 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 B27AA12785F for <ietf@ietfa.amsl.com>; Thu, 29 Jun 2017 22:32:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 UAwg-3iMyL97 for <ietf@ietfa.amsl.com>; Thu, 29 Jun 2017 22:32:03 -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 4CB9B1200CF for <ietf@ietf.org>; Thu, 29 Jun 2017 22:32:03 -0700 (PDT)
Received: from waikiki.gih.co.uk (localhost [IPv6:::1]) by waikiki.gih.co.uk (Postfix) with ESMTP id ADB03320529 for <ietf@ietf.org>; Fri, 30 Jun 2017 06:32:00 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=gih.co.uk; h=from:subject :to:message-id:date:mime-version:content-type; s=mahalo1; bh=msV UbqXXuapnTFe3KNgt87/VUnA=; b=XRRGFcZIrmiWod09MtjRLdVW2qNglfOHXZd x9D2UuMYqVDs1DNM/NkotMLqV0d+fBeEI1tPLtdNZ/atErj6WxEiFQfrFuYWzKZ9 gIRfmBmuzhXLmnAjlrGdKWoFmZi3RW8vCRpQFCiixsmvzi4EiSQOp6LqUzF87lcd 1FTeidYQ=
Received: from [10.21.64.12] (unknown [196.208.108.90]) (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 9D015320288 for <ietf@ietf.org>; Fri, 30 Jun 2017 06:31:59 +0100 (BST)
From: =?UTF-8?Q?Olivier_MJ_Cr=c3=a9pin-Leblond?= <ocl@gih.com>
Subject: About ccTLDs and gTLDs
To: IETF <ietf@ietf.org>
Message-ID: <51541b4b-a58a-9430-9426-5486edbc1540@gih.com>
Date: Fri, 30 Jun 2017 07:31:58 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="------------9979A8977BFC6CC5E6A61578"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5yIDwW0Tabh0gFKuqYjjld0D50M>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 05:32:08 -0000

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

Hello all,

I am reading RFC1591 and RFC3071 and have a couple of simple questions:
1. Is a ccTLD defined as restricted to 2-letter country codes (ISO3166
alpha 2), or could that include 3-letter country codes in the ISO3166
list (ISO3166 alpha 3)?
2. RFC1591 appears to point at 2-letter, but many other parts of this
RFC are obsolete - so does this RFC remain valid?
Kindest regards,

Olivier

--=20
Olivier MJ Cr=C3=A9pin-Leblond, PhD
http://www.gih.com/ocl.html


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

<html>
  <head>
    <meta http-equiv=3D"content-type" content=3D"text/html; charset=3Dutf=
-8">
  </head>
  <body text=3D"#000000" bgcolor=3D"#FFFFFF">
    Hello all,<br>
    <br>
    I am reading RFC1591 and RFC3071 and have a couple of simple
    questions: <br>
    1. Is a ccTLD defined as restricted to 2-letter country codes
    (ISO3166 alpha 2), or could that include 3-letter country codes in
    the ISO3166 list (ISO3166 alpha 3)?<br>
    2. RFC1591 appears to point at 2-letter, but many other parts of
    this RFC are obsolete - so does this RFC remain valid?<br>
    Kindest regards,<br>
    <br>
    Olivier<br>
    <pre class=3D"moz-signature" cols=3D"72">--=20
Olivier MJ Cr=C3=A9pin-Leblond, PhD
<a class=3D"moz-txt-link-freetext" href=3D"http://www.gih.com/ocl.html">h=
ttp://www.gih.com/ocl.html</a>
</pre>
  </body>
</html>

--------------9979A8977BFC6CC5E6A61578--


From nobody Thu Jun 29 23:46:37 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 24780128B93; Thu, 29 Jun 2017 23:46:36 -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-rfc5444-usage.all@ietf.org
Subject: Genart last call review of draft-ietf-manet-rfc5444-usage-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149880519611.4622.17798538360710855866@ietfa.amsl.com>
Date: Thu, 29 Jun 2017 23:46:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/3GdYl50HFXhbtWI3Ubx6lcHXOmk>
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, 30 Jun 2017 06:46:36 -0000

Reviewer: Peter Yee
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-manet-rfc5444-usage-06
Reviewer: Peter Yee
Review Date: 2017-06-29
IETF LC End Date: 2017-06-29
IESG Telechat date: 2017-07-06

Summary: Ready with issues.

Major issues:

Minor issues:

Page 12, 2nd bullet item: I disagree that this is an implementation detail. 
Unless there's additional signaling which indicates which implementation
generated the packet, how is the receiving demultiplexer to know whether the
sending multiplexer added a Message TLV or that was done by the protocol?

Nits/editorial comments:

General:

Somebody  needs to strangle the comma fairy.  She was a bit too liberal with
this document. ;-)  I didn't take the time to clean up all of the excess
commas, but many are noted below.

Change "end to end" to "end-to-end" throughout the document.

Specific:

Page 3, Section 1, 2nd paragraph, 1st sentence: delete the comma after "in".

Page 3, Section 1, 3rd paragraph: delete the comma after "[RFC5444]".

Page 4, 1st full bullet item, 2nd sentence: delete the commas after "process"
and "usage".  Change "is" to "are".

Page 5, 1st bullet item, 3rd sentence: delete "of" after "design".

Page 5, last bullet item: append a comma after "count".

Page 6, last paragraph, 2nd sentence: insert "may" before "pass".  Change the
comma after "rules" to a semicolon.

Page 7, Section 1.3: change "makes" to "make" in both place.  Change "impedes"
to "impede".

Page 7, Section 2, 2nd paragraph: append a comma after \"TLV\".

Page 9, Section 4.3, 2nd paragraph, 2nd sentence: append a comma after
"Originator Address".

Page 10, Section 4.4.1, 1st bullet item, 1st sentence: elide the comma after
"protocol".

Page 11, 1st bullet item, 2nd sentence: change "of" to "or".

Page 11, 3rd bullet item, 3rd sentence: remove the comma after "[RFC5444]".

Page 12, 3rd bullet item: change the comma to a semicolon.

Page 13, Section 4.5 title: append a comma after "Addresses".

Page 13, Section 4.5, 3rd bullet item: change "an" to "a".

Page 14, 4th bullet item: delete the comma after "Message".

Page 14, last paragraph: add a comma after "absence" and delete one following
"location".

Page 15, 1st full paragraph: insert "it" before "could".

Page 15, 2nd paragraph, 2nd sentence: change "routers" to "router's" or
"routers'".

Page 15, 4th paragraph, 2nd sentence: change the comma after TLV to a semicolon.

Page 15, 5th paragraph: delete the commas after "Type" and "Value".

Page 17, 1st partial paragraph, 1st full sentence: change "MPR_WILLNG" to
"MPR_WILLING".

Page 17, 1st full bullet item, 1st sentence: Strike the comma after "[RFC7182]".

Page 17, Section 5, 1st paragraph: delete the comma.

Page 17, Section 5, 1st paragraph after the bullet items: change the comma
after "structural" to a period.  Capitalize the follow "they".  Insert "are"
before "field lengths" if that makes sense.

Page 17, last paragraph: append a comma after "Block".

Page 18, 2nd bullet item: add a comma after "Block".  Delete the comma after
"TLV".

Page 18, 2nd paragraph, 1st sentence: elide the comma after "[RFC5444]".

Page 18, 2nd paragraph, 2nd sentence: delete the comma after "accepted".

Page 18, 2nd paragraph, 3rd sentence: remove the comma after "mechanism".

Page 18, 2nd paragraph, 5th sentence: change "4 bit" to "4-bit".

Page 18, Section 6, 1st sentence: delete the commas following "different",
"same", "specification", and "information".

Page 18, Section 6, 2nd sentence: change the comma following "[RFC5444]" to a
period.  Capitalize the following "any".

Page 19, 2nd to last paragraph, 1st sentence: change the comma after "only" to
a semicolon.

Page 19, 2nd to last paragraph, 2nd sentence: change the comma after "6.2)" to
a semicolon.

Page 19, last paragraph, 1st sentence: strike the comma after the 4th
occurrence of "addresses".

Page 19, last paragraph, 2nd sentence: append a comma after "example".

Page 20, Section 6.2, 1st paragraph: delete the comma.

Page 20, 1st bullet item: remove the comma after "straightforward".

Page 20, 2nd bullet item: change the second comma to a period.  Capitalize the
following "see".

Page 21, 2nd paragraph, 2nd sentence: elide the comma after "advice".

Page 21, 2nd paragraph, last sentence: I can't parse this sentence.  Consider
rewriting for clarity.  There seems to be a missing clause.

Page 22, bullet item: delete the comma after "allowed".

Page 24, Appendix A, 1st paragraph, 2nd sentence: delete all of the commas.

Page 24, Appendix A, 1st paragraph after the bullet items, 2nd sentence: delete
both commas.

Page 25, Appendix B, 1st sentence: append a comma after "valuedness".

Page 25, Appendix B, 2nd sentence: remove the comma following "creation".

Page 25, Appendix B, 3rd sentence: change the comma after "independent" to a
period.  Capitalize the following "for".


From nobody Fri Jun 30 02:06:51 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 02BD7129B02; Fri, 30 Jun 2017 02:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.127
X-Spam-Level: 
X-Spam-Status: No, score=-6.127 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] 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 iCHM6Sn0daQk; Fri, 30 Jun 2017 02:06:46 -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 C18E7128990; Fri, 30 Jun 2017 02:06:45 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.40,285,1496098800";  d="scan'208";a="9640413"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta1.baesystems.com with ESMTP; 30 Jun 2017 10:06:43 +0100
X-IronPort-AV: E=Sophos;i="5.40,285,1496098800";  d="scan'208";a="8163060"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds016.greenlnk.net with ESMTP; 30 Jun 2017 10:06:43 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.201]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0248.002; Fri, 30 Jun 2017 10:06:42 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Peter Yee <peter@akayla.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "manet@ietf.org" <manet@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-manet-rfc5444-usage.all@ietf.org" <draft-ietf-manet-rfc5444-usage.all@ietf.org>
Subject: RE: Genart last call review of draft-ietf-manet-rfc5444-usage-06
Thread-Topic: Genart last call review of draft-ietf-manet-rfc5444-usage-06
Thread-Index: AQHS8Wy/LoNZ0dAFTES9Ww970gslEqI9GRlQ
Date: Fri, 30 Jun 2017 09:06:42 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636FB1D@GLKXM0003v.GREENLNK.net>
References: <149880519611.4622.17798538360710855866@ietfa.amsl.com>
In-Reply-To: <149880519611.4622.17798538360710855866@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="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/tClBkaIqjtlBTDHB1Pe-bjr7eNk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 09:06:49 -0000

UGV0ZXINCg0KVGhhbmtzIHlvdSBmb3IgeW91ciBjb21tZW50cy4gSSBzaG91bGQgbm90ZSB0aGF0
IHRoZSBmb2xsb3dpbmcgY29tbWVudHMgYXJlIG1pbmUsIG5vdCB5ZXQgY29uc3VsdGVkIHdpdGgg
bXkgY28tYXV0aG9ycy4NCg0KSSdtIGdvaW5nIHRvIG1vc3RseSBkaXNhZ3JlZSB3aXRoIHlvdXIg
ZGlzYWdyZWVtZW50IGFib3V0IHRoZSBpbmRpY2F0ZWQgcG9pbnQgYmVpbmcgYW4gaW1wbGVtZW50
YXRpb24gaXNzdWUuIFdoYXQgbWF0dGVycyBpcyBjb25zaXN0ZW5jeSBhdCBhIHJvdXRlci4gQmV0
d2VlbiByb3V0ZXJzIGRvZXNuJ3QgbWF0dGVyLiBJZiByb3V0ZXIgQSBhZGRzIHRoZSBUTFYgaW4g
dGhlIG11bHRpcGxleGVyIG9yIHRoZSBwcm90b2NvbCwgdGhlIG9uLWFpciBtZXNzYWdlIGlzIGlk
ZW50aWNhbC4gQW5kIGl0IGRvZXNuJ3QgbWF0dGVyIGlmIHJvdXRlciBCIHJlY2VpdmluZyBhIHBh
Y2tldCBtYWtlcyB0aGUgb3Bwb3NpdGUgZGVjaXNpb24sIGFzIGxvbmcgYXMgcm91dGVyIEIncyBt
dWx0aXBsZXhlciBhbmQgcHJvdG9jb2wgYXJlIGNvbnNpc3RlbnQuIEkgYmVsaWV2ZSBvbmUgcmVh
c29uIGZvciB0aGlzIGNvbW1lbnQgaXMgdGhhdCBkaWZmZXJlbnQgaW1wbGVtZW50ZXJzIGhhdmUg
bWFkZSBkaWZmZXJlbnQgZGVjaXNpb25zLiBCZWNhdXNlIHRoZXJlIGlzIGNvbnNpc3RlbmN5IG5l
ZWRlZCBvbiBhIHJvdXRlciBpcyB3aHkgaXQgc2F5cyBpdCBpcyAiaW4gcGFydCIuDQoNCkhvd2V2
ZXIsIEkgd291bGQgYWdyZWUsIHJlLXJlYWRpbmcgaXQgYWdhaW4sIHRoYXQgYXMgd29yZGVkLCBp
dCBkb2Vzbid0IGNvbWUgb3ZlciBhcyBjbGVhcmx5IGFzIGl0IHNob3VsZCwgc28gd2Ugd2lsbCBs
b29rIGF0IHJlLXdvcmRpbmcgaXQuDQoNCkkgZG9uJ3QgYWdyZWUgd2l0aCBhbGwgb2YgeW91ciBj
b21tZW50cyBhYm91dCBjb21tYXMuIEp1c3QgdG8gdGFrZSB0aGUgZmlyc3QsIHNpbXBseSByZW1v
dmluZyB0aGUgY29tbWEgaXMgbm90IGNvcnJlY3QgYmVjYXVzZSAiYnV0IGRpZCBub3QgcXVpdGUg
c3VjY2VlZCBpbiIgaXMgYSBwYXJlbnRoZXNpcy4gSG93ZXZlciwgZmFpbHMgdG8gYmUgY29ycmVj
dCBiZWNhdXNlIGF0dGVtcHRlZCBhbmQgc3VjY2VlZCB0YWtlIGRpZmZlcmVudCBwcmVwb3NpdGlv
bnMuIEJ1dCB0aGVuICJhdHRlbXB0ZWQgdG8gcHJvdmlkaW5nIiBpcyBvZiBjb3Vyc2UgaW5jb3Jy
ZWN0LiBTbyB0aGF0IHNlbnRlbmNlIG5lZWRzIHdvcmssIGJ1dCBub3Qgc2ltcGx5IHJlbW92YWwg
b2YgYSBjb21tYS4gSSB3aWxsIHRha2UgYSBsb29rIGF0IGVhY2ggY2FzZSAod2hpY2ggSSBoYXZl
bid0IHlldCBkb25lKSwgYnV0IHVsdGltYXRlbHkgb2YgY291cnNlIHRoZSBSRkMgRWRpdG9yIHdp
bGwgYWN0IGFzIHRoZSBhcmJpdGVyIG9mIHN1Y2ggbWF0dGVycy4NCg0KQ2hyaXN0b3BoZXINCg0K
LS0gDQpDaHJpc3RvcGhlciBEZWFybG92ZQ0KU2VuaW9yIFByaW5jaXBhbCBFbmdpbmVlcg0KQkFF
IFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2VuY2UgTGFib3JhdG9yaWVzDQpfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fXw0KDQpUOiDCoCs0NCAzMzAwIDQ2NzUwMCDCoHwgwqBFOiBjaHJpcy5kZWFybG92ZUBiYWVz
eXN0ZW1zLmNvbQ0KDQpCQUUgU3lzdGVtcyBBcHBsaWVkIEludGVsbGlnZW5jZSwgQ2hlbG1zZm9y
ZCBUZWNobm9sb2d5IFBhcmssIEdyZWF0IEJhZGRvdywgQ2hlbG1zZm9yZCwgRXNzZXggQ00yIDhI
Ti4NCnd3dy5iYWVzeXN0ZW1zLmNvbS9haQ0KQkFFIFN5c3RlbXMgQXBwbGllZCBJbnRlbGxpZ2Vu
Y2UgTGltaXRlZA0KUmVnaXN0ZXJlZCBpbiBFbmdsYW5kICYgV2FsZXMgTm86IDAxMzM3NDUxDQpS
ZWdpc3RlcmVkIE9mZmljZTogU3VycmV5IFJlc2VhcmNoIFBhcmssIEd1aWxkZm9yZCwgU3VycmV5
LCBHVTIgN1lQDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBQZXRlciBZZWUg
W21haWx0bzpwZXRlckBha2F5bGEuY29tXSANClNlbnQ6IDMwIEp1bmUgMjAxNyAwNzo0Nw0KVG86
IGdlbi1hcnRAaWV0Zi5vcmcNCkNjOiBtYW5ldEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsgZHJh
ZnQtaWV0Zi1tYW5ldC1yZmM1NDQ0LXVzYWdlLmFsbEBpZXRmLm9yZw0KU3ViamVjdDogR2VuYXJ0
IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1tYW5ldC1yZmM1NDQ0LXVzYWdlLTA2DQoN
Ci0tLS0tLS0tLS0tLS0tLS0tLS0tLS0hIFdBUk5JTkcgISAtLS0tLS0tLS0tLS0tLS0tLS0tLS0t
IFRoaXMgbWVzc2FnZSBvcmlnaW5hdGVzIGZyb20gb3V0c2lkZSBvdXIgb3JnYW5pc2F0aW9uLCBl
aXRoZXIgZnJvbSBhbiBleHRlcm5hbCBwYXJ0bmVyIG9yIGZyb20gdGhlIGludGVybmV0Lg0KQ29u
c2lkZXIgY2FyZWZ1bGx5IHdoZXRoZXIgeW91IHNob3VsZCBjbGljayBvbiBhbnkgbGlua3MsIG9w
ZW4gYW55IGF0dGFjaG1lbnRzIG9yIHJlcGx5Lg0KRm9sbG93IHRoZSAnUmVwb3J0IFN1c3BpY2lv
dXMgRW1haWxzJyBsaW5rIG9uIElUIG1hdHRlcnMgZm9yIGluc3RydWN0aW9ucyBvbiByZXBvcnRp
bmcgc3VzcGljaW91cyBlbWFpbCBtZXNzYWdlcy4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNClJldmlld2VyOiBQZXRlciBZZWUNClJl
dmlldyByZXN1bHQ6IFJlYWR5IHdpdGggSXNzdWVzDQoNCkkgYW0gdGhlIGFzc2lnbmVkIEdlbi1B
UlQgcmV2aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWEgUmV2aWV3IFRlYW0g
KEdlbi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZCBieSB0
aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMg
anVzdCBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQoNCkZvciBtb3JlIGluZm9y
bWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCg0KPGh0dHBzOi8vdHJhYy5pZXRmLm9yZy90
cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQoNCkRvY3VtZW50OiBkcmFmdC1pZXRmLW1hbmV0LXJm
YzU0NDQtdXNhZ2UtMDYNClJldmlld2VyOiBQZXRlciBZZWUNClJldmlldyBEYXRlOiAyMDE3LTA2
LTI5DQpJRVRGIExDIEVuZCBEYXRlOiAyMDE3LTA2LTI5DQpJRVNHIFRlbGVjaGF0IGRhdGU6IDIw
MTctMDctMDYNCg0KU3VtbWFyeTogUmVhZHkgd2l0aCBpc3N1ZXMuDQoNCk1ham9yIGlzc3VlczoN
Cg0KTWlub3IgaXNzdWVzOg0KDQpQYWdlIDEyLCAybmQgYnVsbGV0IGl0ZW06IEkgZGlzYWdyZWUg
dGhhdCB0aGlzIGlzIGFuIGltcGxlbWVudGF0aW9uIGRldGFpbC4gDQpVbmxlc3MgdGhlcmUncyBh
ZGRpdGlvbmFsIHNpZ25hbGluZyB3aGljaCBpbmRpY2F0ZXMgd2hpY2ggaW1wbGVtZW50YXRpb24g
Z2VuZXJhdGVkIHRoZSBwYWNrZXQsIGhvdyBpcyB0aGUgcmVjZWl2aW5nIGRlbXVsdGlwbGV4ZXIg
dG8ga25vdyB3aGV0aGVyIHRoZSBzZW5kaW5nIG11bHRpcGxleGVyIGFkZGVkIGEgTWVzc2FnZSBU
TFYgb3IgdGhhdCB3YXMgZG9uZSBieSB0aGUgcHJvdG9jb2w/DQoNCk5pdHMvZWRpdG9yaWFsIGNv
bW1lbnRzOg0KDQpHZW5lcmFsOg0KDQpTb21lYm9keSAgbmVlZHMgdG8gc3RyYW5nbGUgdGhlIGNv
bW1hIGZhaXJ5LiAgU2hlIHdhcyBhIGJpdCB0b28gbGliZXJhbCB3aXRoIHRoaXMgZG9jdW1lbnQu
IDstKSAgSSBkaWRuJ3QgdGFrZSB0aGUgdGltZSB0byBjbGVhbiB1cCBhbGwgb2YgdGhlIGV4Y2Vz
cyBjb21tYXMsIGJ1dCBtYW55IGFyZSBub3RlZCBiZWxvdy4NCg0KQ2hhbmdlICJlbmQgdG8gZW5k
IiB0byAiZW5kLXRvLWVuZCIgdGhyb3VnaG91dCB0aGUgZG9jdW1lbnQuDQoNClNwZWNpZmljOg0K
DQpQYWdlIDMsIFNlY3Rpb24gMSwgMm5kIHBhcmFncmFwaCwgMXN0IHNlbnRlbmNlOiBkZWxldGUg
dGhlIGNvbW1hIGFmdGVyICJpbiIuDQoNClBhZ2UgMywgU2VjdGlvbiAxLCAzcmQgcGFyYWdyYXBo
OiBkZWxldGUgdGhlIGNvbW1hIGFmdGVyICJbUkZDNTQ0NF0iLg0KDQpQYWdlIDQsIDFzdCBmdWxs
IGJ1bGxldCBpdGVtLCAybmQgc2VudGVuY2U6IGRlbGV0ZSB0aGUgY29tbWFzIGFmdGVyICJwcm9j
ZXNzIg0KYW5kICJ1c2FnZSIuICBDaGFuZ2UgImlzIiB0byAiYXJlIi4NCg0KUGFnZSA1LCAxc3Qg
YnVsbGV0IGl0ZW0sIDNyZCBzZW50ZW5jZTogZGVsZXRlICJvZiIgYWZ0ZXIgImRlc2lnbiIuDQoN
ClBhZ2UgNSwgbGFzdCBidWxsZXQgaXRlbTogYXBwZW5kIGEgY29tbWEgYWZ0ZXIgImNvdW50Ii4N
Cg0KUGFnZSA2LCBsYXN0IHBhcmFncmFwaCwgMm5kIHNlbnRlbmNlOiBpbnNlcnQgIm1heSIgYmVm
b3JlICJwYXNzIi4gIENoYW5nZSB0aGUgY29tbWEgYWZ0ZXIgInJ1bGVzIiB0byBhIHNlbWljb2xv
bi4NCg0KUGFnZSA3LCBTZWN0aW9uIDEuMzogY2hhbmdlICJtYWtlcyIgdG8gIm1ha2UiIGluIGJv
dGggcGxhY2UuICBDaGFuZ2UgImltcGVkZXMiDQp0byAiaW1wZWRlIi4NCg0KUGFnZSA3LCBTZWN0
aW9uIDIsIDJuZCBwYXJhZ3JhcGg6IGFwcGVuZCBhIGNvbW1hIGFmdGVyIFwiVExWXCIuDQoNClBh
Z2UgOSwgU2VjdGlvbiA0LjMsIDJuZCBwYXJhZ3JhcGgsIDJuZCBzZW50ZW5jZTogYXBwZW5kIGEg
Y29tbWEgYWZ0ZXIgIk9yaWdpbmF0b3IgQWRkcmVzcyIuDQoNClBhZ2UgMTAsIFNlY3Rpb24gNC40
LjEsIDFzdCBidWxsZXQgaXRlbSwgMXN0IHNlbnRlbmNlOiBlbGlkZSB0aGUgY29tbWEgYWZ0ZXIg
InByb3RvY29sIi4NCg0KUGFnZSAxMSwgMXN0IGJ1bGxldCBpdGVtLCAybmQgc2VudGVuY2U6IGNo
YW5nZSAib2YiIHRvICJvciIuDQoNClBhZ2UgMTEsIDNyZCBidWxsZXQgaXRlbSwgM3JkIHNlbnRl
bmNlOiByZW1vdmUgdGhlIGNvbW1hIGFmdGVyICJbUkZDNTQ0NF0iLg0KDQpQYWdlIDEyLCAzcmQg
YnVsbGV0IGl0ZW06IGNoYW5nZSB0aGUgY29tbWEgdG8gYSBzZW1pY29sb24uDQoNClBhZ2UgMTMs
IFNlY3Rpb24gNC41IHRpdGxlOiBhcHBlbmQgYSBjb21tYSBhZnRlciAiQWRkcmVzc2VzIi4NCg0K
UGFnZSAxMywgU2VjdGlvbiA0LjUsIDNyZCBidWxsZXQgaXRlbTogY2hhbmdlICJhbiIgdG8gImEi
Lg0KDQpQYWdlIDE0LCA0dGggYnVsbGV0IGl0ZW06IGRlbGV0ZSB0aGUgY29tbWEgYWZ0ZXIgIk1l
c3NhZ2UiLg0KDQpQYWdlIDE0LCBsYXN0IHBhcmFncmFwaDogYWRkIGEgY29tbWEgYWZ0ZXIgImFi
c2VuY2UiIGFuZCBkZWxldGUgb25lIGZvbGxvd2luZyAibG9jYXRpb24iLg0KDQpQYWdlIDE1LCAx
c3QgZnVsbCBwYXJhZ3JhcGg6IGluc2VydCAiaXQiIGJlZm9yZSAiY291bGQiLg0KDQpQYWdlIDE1
LCAybmQgcGFyYWdyYXBoLCAybmQgc2VudGVuY2U6IGNoYW5nZSAicm91dGVycyIgdG8gInJvdXRl
cidzIiBvciAicm91dGVycyciLg0KDQpQYWdlIDE1LCA0dGggcGFyYWdyYXBoLCAybmQgc2VudGVu
Y2U6IGNoYW5nZSB0aGUgY29tbWEgYWZ0ZXIgVExWIHRvIGEgc2VtaWNvbG9uLg0KDQpQYWdlIDE1
LCA1dGggcGFyYWdyYXBoOiBkZWxldGUgdGhlIGNvbW1hcyBhZnRlciAiVHlwZSIgYW5kICJWYWx1
ZSIuDQoNClBhZ2UgMTcsIDFzdCBwYXJ0aWFsIHBhcmFncmFwaCwgMXN0IGZ1bGwgc2VudGVuY2U6
IGNoYW5nZSAiTVBSX1dJTExORyIgdG8gIk1QUl9XSUxMSU5HIi4NCg0KUGFnZSAxNywgMXN0IGZ1
bGwgYnVsbGV0IGl0ZW0sIDFzdCBzZW50ZW5jZTogU3RyaWtlIHRoZSBjb21tYSBhZnRlciAiW1JG
QzcxODJdIi4NCg0KUGFnZSAxNywgU2VjdGlvbiA1LCAxc3QgcGFyYWdyYXBoOiBkZWxldGUgdGhl
IGNvbW1hLg0KDQpQYWdlIDE3LCBTZWN0aW9uIDUsIDFzdCBwYXJhZ3JhcGggYWZ0ZXIgdGhlIGJ1
bGxldCBpdGVtczogY2hhbmdlIHRoZSBjb21tYSBhZnRlciAic3RydWN0dXJhbCIgdG8gYSBwZXJp
b2QuICBDYXBpdGFsaXplIHRoZSBmb2xsb3cgInRoZXkiLiAgSW5zZXJ0ICJhcmUiDQpiZWZvcmUg
ImZpZWxkIGxlbmd0aHMiIGlmIHRoYXQgbWFrZXMgc2Vuc2UuDQoNClBhZ2UgMTcsIGxhc3QgcGFy
YWdyYXBoOiBhcHBlbmQgYSBjb21tYSBhZnRlciAiQmxvY2siLg0KDQpQYWdlIDE4LCAybmQgYnVs
bGV0IGl0ZW06IGFkZCBhIGNvbW1hIGFmdGVyICJCbG9jayIuICBEZWxldGUgdGhlIGNvbW1hIGFm
dGVyICJUTFYiLg0KDQpQYWdlIDE4LCAybmQgcGFyYWdyYXBoLCAxc3Qgc2VudGVuY2U6IGVsaWRl
IHRoZSBjb21tYSBhZnRlciAiW1JGQzU0NDRdIi4NCg0KUGFnZSAxOCwgMm5kIHBhcmFncmFwaCwg
Mm5kIHNlbnRlbmNlOiBkZWxldGUgdGhlIGNvbW1hIGFmdGVyICJhY2NlcHRlZCIuDQoNClBhZ2Ug
MTgsIDJuZCBwYXJhZ3JhcGgsIDNyZCBzZW50ZW5jZTogcmVtb3ZlIHRoZSBjb21tYSBhZnRlciAi
bWVjaGFuaXNtIi4NCg0KUGFnZSAxOCwgMm5kIHBhcmFncmFwaCwgNXRoIHNlbnRlbmNlOiBjaGFu
Z2UgIjQgYml0IiB0byAiNC1iaXQiLg0KDQpQYWdlIDE4LCBTZWN0aW9uIDYsIDFzdCBzZW50ZW5j
ZTogZGVsZXRlIHRoZSBjb21tYXMgZm9sbG93aW5nICJkaWZmZXJlbnQiLCAic2FtZSIsICJzcGVj
aWZpY2F0aW9uIiwgYW5kICJpbmZvcm1hdGlvbiIuDQoNClBhZ2UgMTgsIFNlY3Rpb24gNiwgMm5k
IHNlbnRlbmNlOiBjaGFuZ2UgdGhlIGNvbW1hIGZvbGxvd2luZyAiW1JGQzU0NDRdIiB0byBhIHBl
cmlvZC4gIENhcGl0YWxpemUgdGhlIGZvbGxvd2luZyAiYW55Ii4NCg0KUGFnZSAxOSwgMm5kIHRv
IGxhc3QgcGFyYWdyYXBoLCAxc3Qgc2VudGVuY2U6IGNoYW5nZSB0aGUgY29tbWEgYWZ0ZXIgIm9u
bHkiIHRvIGEgc2VtaWNvbG9uLg0KDQpQYWdlIDE5LCAybmQgdG8gbGFzdCBwYXJhZ3JhcGgsIDJu
ZCBzZW50ZW5jZTogY2hhbmdlIHRoZSBjb21tYSBhZnRlciAiNi4yKSIgdG8gYSBzZW1pY29sb24u
DQoNClBhZ2UgMTksIGxhc3QgcGFyYWdyYXBoLCAxc3Qgc2VudGVuY2U6IHN0cmlrZSB0aGUgY29t
bWEgYWZ0ZXIgdGhlIDR0aCBvY2N1cnJlbmNlIG9mICJhZGRyZXNzZXMiLg0KDQpQYWdlIDE5LCBs
YXN0IHBhcmFncmFwaCwgMm5kIHNlbnRlbmNlOiBhcHBlbmQgYSBjb21tYSBhZnRlciAiZXhhbXBs
ZSIuDQoNClBhZ2UgMjAsIFNlY3Rpb24gNi4yLCAxc3QgcGFyYWdyYXBoOiBkZWxldGUgdGhlIGNv
bW1hLg0KDQpQYWdlIDIwLCAxc3QgYnVsbGV0IGl0ZW06IHJlbW92ZSB0aGUgY29tbWEgYWZ0ZXIg
InN0cmFpZ2h0Zm9yd2FyZCIuDQoNClBhZ2UgMjAsIDJuZCBidWxsZXQgaXRlbTogY2hhbmdlIHRo
ZSBzZWNvbmQgY29tbWEgdG8gYSBwZXJpb2QuICBDYXBpdGFsaXplIHRoZSBmb2xsb3dpbmcgInNl
ZSIuDQoNClBhZ2UgMjEsIDJuZCBwYXJhZ3JhcGgsIDJuZCBzZW50ZW5jZTogZWxpZGUgdGhlIGNv
bW1hIGFmdGVyICJhZHZpY2UiLg0KDQpQYWdlIDIxLCAybmQgcGFyYWdyYXBoLCBsYXN0IHNlbnRl
bmNlOiBJIGNhbid0IHBhcnNlIHRoaXMgc2VudGVuY2UuICBDb25zaWRlciByZXdyaXRpbmcgZm9y
IGNsYXJpdHkuICBUaGVyZSBzZWVtcyB0byBiZSBhIG1pc3NpbmcgY2xhdXNlLg0KDQpQYWdlIDIy
LCBidWxsZXQgaXRlbTogZGVsZXRlIHRoZSBjb21tYSBhZnRlciAiYWxsb3dlZCIuDQoNClBhZ2Ug
MjQsIEFwcGVuZGl4IEEsIDFzdCBwYXJhZ3JhcGgsIDJuZCBzZW50ZW5jZTogZGVsZXRlIGFsbCBv
ZiB0aGUgY29tbWFzLg0KDQpQYWdlIDI0LCBBcHBlbmRpeCBBLCAxc3QgcGFyYWdyYXBoIGFmdGVy
IHRoZSBidWxsZXQgaXRlbXMsIDJuZCBzZW50ZW5jZTogZGVsZXRlIGJvdGggY29tbWFzLg0KDQpQ
YWdlIDI1LCBBcHBlbmRpeCBCLCAxc3Qgc2VudGVuY2U6IGFwcGVuZCBhIGNvbW1hIGFmdGVyICJ2
YWx1ZWRuZXNzIi4NCg0KUGFnZSAyNSwgQXBwZW5kaXggQiwgMm5kIHNlbnRlbmNlOiByZW1vdmUg
dGhlIGNvbW1hIGZvbGxvd2luZyAiY3JlYXRpb24iLg0KDQpQYWdlIDI1LCBBcHBlbmRpeCBCLCAz
cmQgc2VudGVuY2U6IGNoYW5nZSB0aGUgY29tbWEgYWZ0ZXIgImluZGVwZW5kZW50IiB0byBhIHBl
cmlvZC4gIENhcGl0YWxpemUgdGhlIGZvbGxvd2luZyAiZm9yIi4NCg0KKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioKVGhp
cyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgdG8gdGhlIGludGVu
ZGVkCnJlY2lwaWVudCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdlZC4gSWYgeW91IGFyZSBub3Qg
dGhlIGludGVuZGVkCnJlY2lwaWVudCBwbGVhc2UgZGVsZXRlIGl0IGZyb20geW91ciBzeXN0ZW0g
YW5kIG5vdGlmeSB0aGUgc2VuZGVyLgpZb3Ugc2hvdWxkIG5vdCBjb3B5IGl0IG9yIHVzZSBpdCBm
b3IgYW55IHB1cnBvc2Ugbm9yIGRpc2Nsb3NlIG9yCmRpc3RyaWJ1dGUgaXRzIGNvbnRlbnRzIHRv
IGFueSBvdGhlciBwZXJzb24uCioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqCg==


From nobody Fri Jun 30 03:44: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 AC64C12EAF7; Fri, 30 Jun 2017 03:44:29 -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 qZ4HWwtAumnT; Fri, 30 Jun 2017 03:44:27 -0700 (PDT)
Received: from ukmta2.baesystems.com (ukmta2.baesystems.com [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 79C9012969E; Fri, 30 Jun 2017 03:44:26 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.40,286,1496098800";  d="scan'208";a="8740161"
Received: from unknown (HELO baemasmds016.greenlnk.net) ([10.15.207.101]) by ukmta2.baesystems.com with ESMTP; 30 Jun 2017 11:44:24 +0100
X-IronPort-AV: E=Sophos;i="5.40,286,1496098800";  d="scan'208";a="8184978"
Received: from glkxh0005v.greenlnk.net ([10.109.2.36]) by baemasmds016.greenlnk.net with ESMTP; 30 Jun 2017 11:44:24 +0100
Received: from GLKXM0003V.GREENLNK.net ([169.254.4.201]) by GLKXH0005V.GREENLNK.net ([10.109.2.36]) with mapi id 14.03.0248.002; Fri, 30 Jun 2017 11:44:24 +0100
From: "Dearlove, Christopher (UK)" <chris.dearlove@baesystems.com>
To: Peter Yee <peter@akayla.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "manet@ietf.org" <manet@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-manet-rfc5444-usage.all@ietf.org" <draft-ietf-manet-rfc5444-usage.all@ietf.org>
Subject: RE: Genart last call review of draft-ietf-manet-rfc5444-usage-06
Thread-Topic: Genart last call review of draft-ietf-manet-rfc5444-usage-06
Thread-Index: AQHS8Wy/LoNZ0dAFTES9Ww970gslEqI9N7cQ
Date: Fri, 30 Jun 2017 10:44:24 +0000
Message-ID: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636FB6D@GLKXM0003v.GREENLNK.net>
References: <149880519611.4622.17798538360710855866@ietfa.amsl.com>
In-Reply-To: <149880519611.4622.17798538360710855866@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="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/0ZbiH0mxv7P-SpFQCkEuFZC6xaI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 10:44:30 -0000

UGV0ZXINCg0KSGF2aW5nIG5vdyB3b3JrZWQgdGhyb3VnaCBhbGwgb2YgdGhvc2UsIGZpcnN0IHBh
cnRpY3VsYXIgdGhhbmtzIGZvciB0aGUgc2V2ZXJhbCBvdXQtYW5kLW91dCBlcnJvcnMgY2F1Z2h0
LiBTZWNvbmQsIG15IGRyYWZ0IGZvciByZXZpZXcgYnkgbXkgY28tYXV0aG9ycyBoYXMgYSBtaXh0
dXJlIG9mIGFjY2VwdGVkIGNoYW5nZSAodGhlIGxhcmdlc3QgZ3JvdXApLCBub3QgY2hhbmdlZCwg
YW5kIHJldmlzZWQgdG8gYSB0aGlyZCBmb3JtICh0aGUgc2Vjb25kIGxhcmdlc3QgZ3JvdXApLiBJ
biBwYXJ0aWN1bGFyLCB0aGUgZmlyc3QgY29tbWEgY2FzZSBJIHJlc29sdmVkIGJ5IHJlc3RydWN0
dXJpbmcgdGhlIHNlbnRlbmNlLg0KDQpBcyBpbmRpY2F0ZWQsIEkgbmVlZCB0byBnZXQgYnV5LWlu
IChvciBmdXJ0aGVyIHJldmlzaW9ucykgZnJvbSBteSBjby1hdXRob3JzLCBidXQgSSBob3BlIGEg
LTA3IHdpbGwgYmUgcmVsYXRpdmVseSBxdWlja2x5IHByb2R1Y2VkLg0KDQpDaHJpc3RvcGhlcg0K
DQotLSANCkNocmlzdG9waGVyIERlYXJsb3ZlDQpTZW5pb3IgUHJpbmNpcGFsIEVuZ2luZWVyDQpC
QUUgU3lzdGVtcyBBcHBsaWVkIEludGVsbGlnZW5jZSBMYWJvcmF0b3JpZXMNCl9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fDQoNClQ6IMKgKzQ0IDMzMDAgNDY3NTAwIMKgfCDCoEU6IGNocmlzLmRlYXJsb3ZlQGJh
ZXN5c3RlbXMuY29tDQoNCkJBRSBTeXN0ZW1zIEFwcGxpZWQgSW50ZWxsaWdlbmNlLCBDaGVsbXNm
b3JkIFRlY2hub2xvZ3kgUGFyaywgR3JlYXQgQmFkZG93LCBDaGVsbXNmb3JkLCBFc3NleCBDTTIg
OEhOLg0Kd3d3LmJhZXN5c3RlbXMuY29tL2FpDQpCQUUgU3lzdGVtcyBBcHBsaWVkIEludGVsbGln
ZW5jZSBMaW1pdGVkDQpSZWdpc3RlcmVkIGluIEVuZ2xhbmQgJiBXYWxlcyBObzogMDEzMzc0NTEN
ClJlZ2lzdGVyZWQgT2ZmaWNlOiBTdXJyZXkgUmVzZWFyY2ggUGFyaywgR3VpbGRmb3JkLCBTdXJy
ZXksIEdVMiA3WVANCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogUGV0ZXIg
WWVlIFttYWlsdG86cGV0ZXJAYWtheWxhLmNvbV0gDQpTZW50OiAzMCBKdW5lIDIwMTcgMDc6NDcN
ClRvOiBnZW4tYXJ0QGlldGYub3JnDQpDYzogbWFuZXRAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7
IGRyYWZ0LWlldGYtbWFuZXQtcmZjNTQ0NC11c2FnZS5hbGxAaWV0Zi5vcmcNClN1YmplY3Q6IEdl
bmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtbWFuZXQtcmZjNTQ0NC11c2FnZS0w
Ng0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tISBXQVJOSU5HICEgLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLSBUaGlzIG1lc3NhZ2Ugb3JpZ2luYXRlcyBmcm9tIG91dHNpZGUgb3VyIG9yZ2FuaXNhdGlv
biwgZWl0aGVyIGZyb20gYW4gZXh0ZXJuYWwgcGFydG5lciBvciBmcm9tIHRoZSBpbnRlcm5ldC4N
CkNvbnNpZGVyIGNhcmVmdWxseSB3aGV0aGVyIHlvdSBzaG91bGQgY2xpY2sgb24gYW55IGxpbmtz
LCBvcGVuIGFueSBhdHRhY2htZW50cyBvciByZXBseS4NCkZvbGxvdyB0aGUgJ1JlcG9ydCBTdXNw
aWNpb3VzIEVtYWlscycgbGluayBvbiBJVCBtYXR0ZXJzIGZvciBpbnN0cnVjdGlvbnMgb24gcmVw
b3J0aW5nIHN1c3BpY2lvdXMgZW1haWwgbWVzc2FnZXMuDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQpSZXZpZXdlcjogUGV0ZXIgWWVl
DQpSZXZpZXcgcmVzdWx0OiBSZWFkeSB3aXRoIElzc3Vlcw0KDQpJIGFtIHRoZSBhc3NpZ25lZCBH
ZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhIFJldmlldyBU
ZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQg
YnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1l
bnRzIGp1c3QgbGlrZSBhbnkgb3RoZXIgbGFzdCBjYWxsIGNvbW1lbnRzLg0KDQpGb3IgbW9yZSBp
bmZvcm1hdGlvbiwgcGxlYXNlIHNlZSB0aGUgRkFRIGF0DQoNCjxodHRwczovL3RyYWMuaWV0Zi5v
cmcvdHJhYy9nZW4vd2lraS9HZW5BcnRmYXE+Lg0KDQpEb2N1bWVudDogZHJhZnQtaWV0Zi1tYW5l
dC1yZmM1NDQ0LXVzYWdlLTA2DQpSZXZpZXdlcjogUGV0ZXIgWWVlDQpSZXZpZXcgRGF0ZTogMjAx
Ny0wNi0yOQ0KSUVURiBMQyBFbmQgRGF0ZTogMjAxNy0wNi0yOQ0KSUVTRyBUZWxlY2hhdCBkYXRl
OiAyMDE3LTA3LTA2DQoNClN1bW1hcnk6IFJlYWR5IHdpdGggaXNzdWVzLg0KDQpNYWpvciBpc3N1
ZXM6DQoNCk1pbm9yIGlzc3VlczoNCg0KUGFnZSAxMiwgMm5kIGJ1bGxldCBpdGVtOiBJIGRpc2Fn
cmVlIHRoYXQgdGhpcyBpcyBhbiBpbXBsZW1lbnRhdGlvbiBkZXRhaWwuIA0KVW5sZXNzIHRoZXJl
J3MgYWRkaXRpb25hbCBzaWduYWxpbmcgd2hpY2ggaW5kaWNhdGVzIHdoaWNoIGltcGxlbWVudGF0
aW9uIGdlbmVyYXRlZCB0aGUgcGFja2V0LCBob3cgaXMgdGhlIHJlY2VpdmluZyBkZW11bHRpcGxl
eGVyIHRvIGtub3cgd2hldGhlciB0aGUgc2VuZGluZyBtdWx0aXBsZXhlciBhZGRlZCBhIE1lc3Nh
Z2UgVExWIG9yIHRoYXQgd2FzIGRvbmUgYnkgdGhlIHByb3RvY29sPw0KDQpOaXRzL2VkaXRvcmlh
bCBjb21tZW50czoNCg0KR2VuZXJhbDoNCg0KU29tZWJvZHkgIG5lZWRzIHRvIHN0cmFuZ2xlIHRo
ZSBjb21tYSBmYWlyeS4gIFNoZSB3YXMgYSBiaXQgdG9vIGxpYmVyYWwgd2l0aCB0aGlzIGRvY3Vt
ZW50LiA7LSkgIEkgZGlkbid0IHRha2UgdGhlIHRpbWUgdG8gY2xlYW4gdXAgYWxsIG9mIHRoZSBl
eGNlc3MgY29tbWFzLCBidXQgbWFueSBhcmUgbm90ZWQgYmVsb3cuDQoNCkNoYW5nZSAiZW5kIHRv
IGVuZCIgdG8gImVuZC10by1lbmQiIHRocm91Z2hvdXQgdGhlIGRvY3VtZW50Lg0KDQpTcGVjaWZp
YzoNCg0KUGFnZSAzLCBTZWN0aW9uIDEsIDJuZCBwYXJhZ3JhcGgsIDFzdCBzZW50ZW5jZTogZGVs
ZXRlIHRoZSBjb21tYSBhZnRlciAiaW4iLg0KDQpQYWdlIDMsIFNlY3Rpb24gMSwgM3JkIHBhcmFn
cmFwaDogZGVsZXRlIHRoZSBjb21tYSBhZnRlciAiW1JGQzU0NDRdIi4NCg0KUGFnZSA0LCAxc3Qg
ZnVsbCBidWxsZXQgaXRlbSwgMm5kIHNlbnRlbmNlOiBkZWxldGUgdGhlIGNvbW1hcyBhZnRlciAi
cHJvY2VzcyINCmFuZCAidXNhZ2UiLiAgQ2hhbmdlICJpcyIgdG8gImFyZSIuDQoNClBhZ2UgNSwg
MXN0IGJ1bGxldCBpdGVtLCAzcmQgc2VudGVuY2U6IGRlbGV0ZSAib2YiIGFmdGVyICJkZXNpZ24i
Lg0KDQpQYWdlIDUsIGxhc3QgYnVsbGV0IGl0ZW06IGFwcGVuZCBhIGNvbW1hIGFmdGVyICJjb3Vu
dCIuDQoNClBhZ2UgNiwgbGFzdCBwYXJhZ3JhcGgsIDJuZCBzZW50ZW5jZTogaW5zZXJ0ICJtYXki
IGJlZm9yZSAicGFzcyIuICBDaGFuZ2UgdGhlIGNvbW1hIGFmdGVyICJydWxlcyIgdG8gYSBzZW1p
Y29sb24uDQoNClBhZ2UgNywgU2VjdGlvbiAxLjM6IGNoYW5nZSAibWFrZXMiIHRvICJtYWtlIiBp
biBib3RoIHBsYWNlLiAgQ2hhbmdlICJpbXBlZGVzIg0KdG8gImltcGVkZSIuDQoNClBhZ2UgNywg
U2VjdGlvbiAyLCAybmQgcGFyYWdyYXBoOiBhcHBlbmQgYSBjb21tYSBhZnRlciBcIlRMVlwiLg0K
DQpQYWdlIDksIFNlY3Rpb24gNC4zLCAybmQgcGFyYWdyYXBoLCAybmQgc2VudGVuY2U6IGFwcGVu
ZCBhIGNvbW1hIGFmdGVyICJPcmlnaW5hdG9yIEFkZHJlc3MiLg0KDQpQYWdlIDEwLCBTZWN0aW9u
IDQuNC4xLCAxc3QgYnVsbGV0IGl0ZW0sIDFzdCBzZW50ZW5jZTogZWxpZGUgdGhlIGNvbW1hIGFm
dGVyICJwcm90b2NvbCIuDQoNClBhZ2UgMTEsIDFzdCBidWxsZXQgaXRlbSwgMm5kIHNlbnRlbmNl
OiBjaGFuZ2UgIm9mIiB0byAib3IiLg0KDQpQYWdlIDExLCAzcmQgYnVsbGV0IGl0ZW0sIDNyZCBz
ZW50ZW5jZTogcmVtb3ZlIHRoZSBjb21tYSBhZnRlciAiW1JGQzU0NDRdIi4NCg0KUGFnZSAxMiwg
M3JkIGJ1bGxldCBpdGVtOiBjaGFuZ2UgdGhlIGNvbW1hIHRvIGEgc2VtaWNvbG9uLg0KDQpQYWdl
IDEzLCBTZWN0aW9uIDQuNSB0aXRsZTogYXBwZW5kIGEgY29tbWEgYWZ0ZXIgIkFkZHJlc3NlcyIu
DQoNClBhZ2UgMTMsIFNlY3Rpb24gNC41LCAzcmQgYnVsbGV0IGl0ZW06IGNoYW5nZSAiYW4iIHRv
ICJhIi4NCg0KUGFnZSAxNCwgNHRoIGJ1bGxldCBpdGVtOiBkZWxldGUgdGhlIGNvbW1hIGFmdGVy
ICJNZXNzYWdlIi4NCg0KUGFnZSAxNCwgbGFzdCBwYXJhZ3JhcGg6IGFkZCBhIGNvbW1hIGFmdGVy
ICJhYnNlbmNlIiBhbmQgZGVsZXRlIG9uZSBmb2xsb3dpbmcgImxvY2F0aW9uIi4NCg0KUGFnZSAx
NSwgMXN0IGZ1bGwgcGFyYWdyYXBoOiBpbnNlcnQgIml0IiBiZWZvcmUgImNvdWxkIi4NCg0KUGFn
ZSAxNSwgMm5kIHBhcmFncmFwaCwgMm5kIHNlbnRlbmNlOiBjaGFuZ2UgInJvdXRlcnMiIHRvICJy
b3V0ZXIncyIgb3IgInJvdXRlcnMnIi4NCg0KUGFnZSAxNSwgNHRoIHBhcmFncmFwaCwgMm5kIHNl
bnRlbmNlOiBjaGFuZ2UgdGhlIGNvbW1hIGFmdGVyIFRMViB0byBhIHNlbWljb2xvbi4NCg0KUGFn
ZSAxNSwgNXRoIHBhcmFncmFwaDogZGVsZXRlIHRoZSBjb21tYXMgYWZ0ZXIgIlR5cGUiIGFuZCAi
VmFsdWUiLg0KDQpQYWdlIDE3LCAxc3QgcGFydGlhbCBwYXJhZ3JhcGgsIDFzdCBmdWxsIHNlbnRl
bmNlOiBjaGFuZ2UgIk1QUl9XSUxMTkciIHRvICJNUFJfV0lMTElORyIuDQoNClBhZ2UgMTcsIDFz
dCBmdWxsIGJ1bGxldCBpdGVtLCAxc3Qgc2VudGVuY2U6IFN0cmlrZSB0aGUgY29tbWEgYWZ0ZXIg
IltSRkM3MTgyXSIuDQoNClBhZ2UgMTcsIFNlY3Rpb24gNSwgMXN0IHBhcmFncmFwaDogZGVsZXRl
IHRoZSBjb21tYS4NCg0KUGFnZSAxNywgU2VjdGlvbiA1LCAxc3QgcGFyYWdyYXBoIGFmdGVyIHRo
ZSBidWxsZXQgaXRlbXM6IGNoYW5nZSB0aGUgY29tbWEgYWZ0ZXIgInN0cnVjdHVyYWwiIHRvIGEg
cGVyaW9kLiAgQ2FwaXRhbGl6ZSB0aGUgZm9sbG93ICJ0aGV5Ii4gIEluc2VydCAiYXJlIg0KYmVm
b3JlICJmaWVsZCBsZW5ndGhzIiBpZiB0aGF0IG1ha2VzIHNlbnNlLg0KDQpQYWdlIDE3LCBsYXN0
IHBhcmFncmFwaDogYXBwZW5kIGEgY29tbWEgYWZ0ZXIgIkJsb2NrIi4NCg0KUGFnZSAxOCwgMm5k
IGJ1bGxldCBpdGVtOiBhZGQgYSBjb21tYSBhZnRlciAiQmxvY2siLiAgRGVsZXRlIHRoZSBjb21t
YSBhZnRlciAiVExWIi4NCg0KUGFnZSAxOCwgMm5kIHBhcmFncmFwaCwgMXN0IHNlbnRlbmNlOiBl
bGlkZSB0aGUgY29tbWEgYWZ0ZXIgIltSRkM1NDQ0XSIuDQoNClBhZ2UgMTgsIDJuZCBwYXJhZ3Jh
cGgsIDJuZCBzZW50ZW5jZTogZGVsZXRlIHRoZSBjb21tYSBhZnRlciAiYWNjZXB0ZWQiLg0KDQpQ
YWdlIDE4LCAybmQgcGFyYWdyYXBoLCAzcmQgc2VudGVuY2U6IHJlbW92ZSB0aGUgY29tbWEgYWZ0
ZXIgIm1lY2hhbmlzbSIuDQoNClBhZ2UgMTgsIDJuZCBwYXJhZ3JhcGgsIDV0aCBzZW50ZW5jZTog
Y2hhbmdlICI0IGJpdCIgdG8gIjQtYml0Ii4NCg0KUGFnZSAxOCwgU2VjdGlvbiA2LCAxc3Qgc2Vu
dGVuY2U6IGRlbGV0ZSB0aGUgY29tbWFzIGZvbGxvd2luZyAiZGlmZmVyZW50IiwgInNhbWUiLCAi
c3BlY2lmaWNhdGlvbiIsIGFuZCAiaW5mb3JtYXRpb24iLg0KDQpQYWdlIDE4LCBTZWN0aW9uIDYs
IDJuZCBzZW50ZW5jZTogY2hhbmdlIHRoZSBjb21tYSBmb2xsb3dpbmcgIltSRkM1NDQ0XSIgdG8g
YSBwZXJpb2QuICBDYXBpdGFsaXplIHRoZSBmb2xsb3dpbmcgImFueSIuDQoNClBhZ2UgMTksIDJu
ZCB0byBsYXN0IHBhcmFncmFwaCwgMXN0IHNlbnRlbmNlOiBjaGFuZ2UgdGhlIGNvbW1hIGFmdGVy
ICJvbmx5IiB0byBhIHNlbWljb2xvbi4NCg0KUGFnZSAxOSwgMm5kIHRvIGxhc3QgcGFyYWdyYXBo
LCAybmQgc2VudGVuY2U6IGNoYW5nZSB0aGUgY29tbWEgYWZ0ZXIgIjYuMikiIHRvIGEgc2VtaWNv
bG9uLg0KDQpQYWdlIDE5LCBsYXN0IHBhcmFncmFwaCwgMXN0IHNlbnRlbmNlOiBzdHJpa2UgdGhl
IGNvbW1hIGFmdGVyIHRoZSA0dGggb2NjdXJyZW5jZSBvZiAiYWRkcmVzc2VzIi4NCg0KUGFnZSAx
OSwgbGFzdCBwYXJhZ3JhcGgsIDJuZCBzZW50ZW5jZTogYXBwZW5kIGEgY29tbWEgYWZ0ZXIgImV4
YW1wbGUiLg0KDQpQYWdlIDIwLCBTZWN0aW9uIDYuMiwgMXN0IHBhcmFncmFwaDogZGVsZXRlIHRo
ZSBjb21tYS4NCg0KUGFnZSAyMCwgMXN0IGJ1bGxldCBpdGVtOiByZW1vdmUgdGhlIGNvbW1hIGFm
dGVyICJzdHJhaWdodGZvcndhcmQiLg0KDQpQYWdlIDIwLCAybmQgYnVsbGV0IGl0ZW06IGNoYW5n
ZSB0aGUgc2Vjb25kIGNvbW1hIHRvIGEgcGVyaW9kLiAgQ2FwaXRhbGl6ZSB0aGUgZm9sbG93aW5n
ICJzZWUiLg0KDQpQYWdlIDIxLCAybmQgcGFyYWdyYXBoLCAybmQgc2VudGVuY2U6IGVsaWRlIHRo
ZSBjb21tYSBhZnRlciAiYWR2aWNlIi4NCg0KUGFnZSAyMSwgMm5kIHBhcmFncmFwaCwgbGFzdCBz
ZW50ZW5jZTogSSBjYW4ndCBwYXJzZSB0aGlzIHNlbnRlbmNlLiAgQ29uc2lkZXIgcmV3cml0aW5n
IGZvciBjbGFyaXR5LiAgVGhlcmUgc2VlbXMgdG8gYmUgYSBtaXNzaW5nIGNsYXVzZS4NCg0KUGFn
ZSAyMiwgYnVsbGV0IGl0ZW06IGRlbGV0ZSB0aGUgY29tbWEgYWZ0ZXIgImFsbG93ZWQiLg0KDQpQ
YWdlIDI0LCBBcHBlbmRpeCBBLCAxc3QgcGFyYWdyYXBoLCAybmQgc2VudGVuY2U6IGRlbGV0ZSBh
bGwgb2YgdGhlIGNvbW1hcy4NCg0KUGFnZSAyNCwgQXBwZW5kaXggQSwgMXN0IHBhcmFncmFwaCBh
ZnRlciB0aGUgYnVsbGV0IGl0ZW1zLCAybmQgc2VudGVuY2U6IGRlbGV0ZSBib3RoIGNvbW1hcy4N
Cg0KUGFnZSAyNSwgQXBwZW5kaXggQiwgMXN0IHNlbnRlbmNlOiBhcHBlbmQgYSBjb21tYSBhZnRl
ciAidmFsdWVkbmVzcyIuDQoNClBhZ2UgMjUsIEFwcGVuZGl4IEIsIDJuZCBzZW50ZW5jZTogcmVt
b3ZlIHRoZSBjb21tYSBmb2xsb3dpbmcgImNyZWF0aW9uIi4NCg0KUGFnZSAyNSwgQXBwZW5kaXgg
QiwgM3JkIHNlbnRlbmNlOiBjaGFuZ2UgdGhlIGNvbW1hIGFmdGVyICJpbmRlcGVuZGVudCIgdG8g
YSBwZXJpb2QuICBDYXBpdGFsaXplIHRoZSBmb2xsb3dpbmcgImZvciIuDQoNCioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
ClRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBhcmUgY29uZmlkZW50aWFsIHRvIHRoZSBp
bnRlbmRlZApyZWNpcGllbnQgYW5kIG1heSBhbHNvIGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUg
bm90IHRoZSBpbnRlbmRlZApyZWNpcGllbnQgcGxlYXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lz
dGVtIGFuZCBub3RpZnkgdGhlIHNlbmRlci4KWW91IHNob3VsZCBub3QgY29weSBpdCBvciB1c2Ug
aXQgZm9yIGFueSBwdXJwb3NlIG5vciBkaXNjbG9zZSBvcgpkaXN0cmlidXRlIGl0cyBjb250ZW50
cyB0byBhbnkgb3RoZXIgcGVyc29uLgoqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioq
KioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKioqKgo=


From nobody Fri Jun 30 04:54: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 078FE12EC00 for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 04:54:38 -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 N48je7VcQj02 for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 04:54:35 -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 DD411129468 for <ietf@ietf.org>; Fri, 30 Jun 2017 04:54:34 -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 v5UBOQbh131037 for <ietf@ietf.org>; Fri, 30 Jun 2017 07:25:12 -0400
Received: from e13.ny.us.ibm.com (e13.ny.us.ibm.com [129.33.205.203]) by mx0b-001b2d01.pphosted.com with ESMTP id 2bdms5t8tt-1 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NOT) for <ietf@ietf.org>; Fri, 30 Jun 2017 07:25:12 -0400
Received: from localhost by e13.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, 30 Jun 2017 07:25:11 -0400
Received: from b01cxnp23032.gho.pok.ibm.com (9.57.198.27) by e13.ny.us.ibm.com (146.89.104.200) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted;  Fri, 30 Jun 2017 07:25:09 -0400
Received: from b01ledav004.gho.pok.ibm.com (b01ledav004.gho.pok.ibm.com [9.57.199.109]) by b01cxnp23032.gho.pok.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id v5UBP8Fa23920760 for <ietf@ietf.org>; Fri, 30 Jun 2017 11:25:08 GMT
Received: from b01ledav004.gho.pok.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 49B51112034 for <ietf@ietf.org>; Fri, 30 Jun 2017 07:25:10 -0400 (EDT)
Received: from rotala.raleigh.ibm.com (unknown [9.27.195.37]) by b01ledav004.gho.pok.ibm.com (Postfix) with ESMTPS id 3692211204B for <ietf@ietf.org>; Fri, 30 Jun 2017 07:25:10 -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 v5UBP6Uw007559 for <ietf@ietf.org>; Fri, 30 Jun 2017 07:25:07 -0400
Received: (from narten@localhost) by rotala.raleigh.ibm.com (8.15.2/8.15.2/Submit) id v5UBP6rq007524 for ietf@ietf.org; Fri, 30 Jun 2017 07:25:06 -0400
From: narten@us.ibm.com
Date: Fri, 30 Jun 2017 07:25: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: 17063011-0008-0000-0000-000002526148
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00007297; HX=3.00000241; KW=3.00000007; PH=3.00000004; SC=3.00000214; SDB=6.00880832; UDB=6.00439147; IPR=6.00660986;  BA=6.00005448; NDR=6.00000001; ZLA=6.00000005; ZF=6.00000009; ZB=6.00000000; ZP=6.00000000; ZH=6.00000000; ZU=6.00000002; MB=3.00016021; XFM=3.00000015; UTC=2017-06-30 11:25:09
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 17063011-0009-0000-0000-000035DCAEEB
Message-Id: <201706301125.v5UBP6rq007524@rotala.raleigh.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-06-30_09:, , 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-1706300182
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/KV0y6PlVnCq17G1HXBqXSRKGagM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 11:54:38 -0000

Total of 99 messages in the last 7 days.
 
script run at: Fri Jun 30 07:25:01 EDT 2017
 
    Messages   |      Bytes        | Who
--------+------+--------+----------+------------------------
  9.09% |    9 |  6.27% |    81027 | julian.reschke@gmx.de
  4.04% |    4 |  8.22% |   106165 | d3e3e3@gmail.com
  5.05% |    5 |  3.50% |    45250 | touch@isi.edu
  4.04% |    4 |  3.03% |    39121 | chris.dearlove@baesystems.com
  4.04% |    4 |  2.94% |    37959 | stewart.bryant@gmail.com
  4.04% |    4 |  2.37% |    30560 | w@1wt.eu
  2.02% |    2 |  4.14% |    53489 | erosen@juniper.net
  2.02% |    2 |  3.62% |    46826 | tonysietf@gmail.com
  1.01% |    1 |  4.34% |    56128 | magnus.westerlund@ericsson.com
  3.03% |    3 |  2.32% |    29964 | peter@filament.com
  2.02% |    2 |  3.29% |    42456 | christer.holmberg@ericsson.com
  3.03% |    3 |  2.19% |    28340 | tinatsou6@gmail.com
  3.03% |    3 |  2.11% |    27260 | dromasca@gmail.com
  2.02% |    2 |  2.15% |    27754 | ruediger.geib@telekom.de
  1.01% |    1 |  2.97% |    38321 | michael.bishop@microsoft.com
  2.02% |    2 |  1.88% |    24335 | kazuhooku@gmail.com
  2.02% |    2 |  1.76% |    22795 | linda.dunbar@huawei.com
  1.01% |    1 |  2.62% |    33811 | bclaise@cisco.com
  2.02% |    2 |  1.58% |    20386 | mnot@mnot.net
  2.02% |    2 |  1.51% |    19543 | presnick@qti.qualcomm.com
  1.01% |    1 |  2.43% |    31374 | david.black@dell.com
  2.02% |    2 |  1.30% |    16807 | kaduk@mit.edu
  2.02% |    2 |  1.13% |    14614 | stewart@g3ysx.org.uk
  1.01% |    1 |  2.10% |    27145 | borje.ohlman@abc.se
  1.01% |    1 |  1.99% |    25652 | michelle.cotton@iana.org
  1.01% |    1 |  1.70% |    21994 | daedulus@btconnect.com
  1.01% |    1 |  1.52% |    19600 | elwynd@dial.pipex.com
  1.01% |    1 |  1.51% |    19541 | lorenzo@google.com
  1.01% |    1 |  1.16% |    15045 | gunter.van_de_velde@nokia.com
  1.01% |    1 |  1.06% |    13636 | pierrick.seite@orange.com
  1.01% |    1 |  1.01% |    13084 | brian.e.carpenter@gmail.com
  1.01% |    1 |  0.99% |    12742 | aaron.falk@gmail.com
  1.01% |    1 |  0.99% |    12729 | ted.ietf@gmail.com
  1.01% |    1 |  0.98% |    12656 | stpeter@stpeter.im
  1.01% |    1 |  0.98% |    12623 | worley@ariadne.com
  1.01% |    1 |  0.97% |    12573 | rousskov@measurement-factory.com
  1.01% |    1 |  0.97% |    12471 | alexandre.petrescu@gmail.com
  1.01% |    1 |  0.93% |    12057 | gabrielkwaye@gmail.com
  1.01% |    1 |  0.87% |    11270 | jagao@outlook.com
  1.01% |    1 |  0.86% |    11088 | narten@us.ibm.com
  1.01% |    1 |  0.85% |    10976 | john-ietf@jck.com
  1.01% |    1 |  0.83% |    10744 | eburger@standardstrack.com
  1.01% |    1 |  0.81% |    10468 | phill@hallambaker.com
  1.01% |    1 |  0.80% |    10330 | tobias.gondrom@gondrom.org
  1.01% |    1 |  0.72% |     9272 | j.schoenwaelder@jacobs-university.de
  1.01% |    1 |  0.71% |     9134 | ncamwing@cisco.com
  1.01% |    1 |  0.70% |     9004 | barryleiba@computer.org
  1.01% |    1 |  0.67% |     8626 | martin.thomson@gmail.com
  1.01% |    1 |  0.66% |     8579 | email1@jevan.com.au
  1.01% |    1 |  0.65% |     8362 | alissa@cooperw.in
  1.01% |    1 |  0.61% |     7835 | fluffy@iii.ca
  1.01% |    1 |  0.60% |     7712 | jeff.hodges@kingsmountain.com
  1.01% |    1 |  0.48% |     6148 | ron.even.tlv@gmail.com
  1.01% |    1 |  0.47% |     6128 | agenda@ietf.org
  1.01% |    1 |  0.47% |     6037 | ietf-secretariat@ietf.org
  1.01% |    1 |  0.45% |     5763 | sean@sn3rd.com
  1.01% |    1 |  0.44% |     5716 | rjsparks@nostrum.com
  1.01% |    1 |  0.44% |     5696 | liushucheng@huawei.com
  1.01% |    1 |  0.42% |     5448 | housley@vigilsec.com
--------+------+--------+----------+------------------------
100.00% |   99 |100.00% |  1292169 | Total


From nobody Fri Jun 30 06:33:40 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 6F10412EC0D; Fri, 30 Jun 2017 06:33:38 -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-httpbis-early-hints.all@ietf.org, ietf@ietf.org, ietf-http-wg@w3.org
Subject: Opsdir last call review of draft-ietf-httpbis-early-hints-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149882961840.4584.5598980043749268047@ietfa.amsl.com>
Date: Fri, 30 Jun 2017 06:33:38 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/6b072tcq_nauP08vIRRrlcB5BDA>
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, 30 Jun 2017 13:33:38 -0000

Reviewer: Bert Wijnen
Review result: Ready

This document is clear (at least to me) and is ready for publication.
I dod not see any special operational or network management related issues/concerns.

Bert


From nobody Fri Jun 30 06:48:22 2017
Return-Path: <email1@jevan.com.au>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A7FD12EC13 for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 06:48:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.738
X-Spam-Level: 
X-Spam-Status: No, score=-0.738 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_NEUTRAL=0.779, T_REMOTE_IMAGE=0.01] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id blYCnUwBDQdT for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 06:48:19 -0700 (PDT)
Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (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 8BB5B129B2B for <ietf@ietf.org>; Fri, 30 Jun 2017 06:48:17 -0700 (PDT)
Received: from [10.9.9.211] (helo=mailfront11.runbox.com) by mailtransmit02.runbox with esmtp (Exim 4.86_2) (envelope-from <email1@jevan.com.au>) id 1dQwHO-0005YM-G5 for ietf@ietf.org; Fri, 30 Jun 2017 15:48:14 +0200
Received: from [121.127.214.84] (helo=desktop-797rgpq) by mailfront11.runbox.com with esmtpsa (uid:796123 ) (TLS1.0:DHE_RSA_3DES_EDE_CBC_SHA1:192) (Exim 4.82) id 1dQwGu-0005Ed-DA for ietf@ietf.org; Fri, 30 Jun 2017 15:47:45 +0200
To: ietf@ietf.org
From: Jevan Pipitone <email1@jevan.com.au>
Subject: copy paste OL element in browser
Message-ID: <d4c13c5e-66d2-7fff-abe0-f61bff90bc89@jevan.com.au>
Date: Fri, 30 Jun 2017 23:47:37 +1000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
Content-Language: en-US
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----MTometvbaqimdskhwyojreumesocxluzyx"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PtSCFu8vMmnb3Bw8YzDckVGMj10>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 13:48:21 -0000

------MTometvbaqimdskhwyojreumesocxluzyx
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

When I copy text that has been displayed from an "ol" ordered list 
element on a web page in firefox, and paste it into notepad, the text is 
copied but the numbers are not. To me this seems like a problem, what do 
you think?

If you don't believe me try it at

https://www.w3schools.com/html/tryit.asp?filename=tryhtml_lists_ordered

The code is:

<!DOCTYPE html>
<html>
<body>
<h2>An ordered HTML list</h2>
<ol>
   <li>Coffee</li>
   <li>Tea</li>
   <li>Milk</li>
</ol>
</body>
</html>

What it comes out when copied from the web page displayed (not from the 
source) and pasted into notepad is

     Coffee
     Tea
     Milk

not

1. Coffee
2. Tea
3. Milk

The latter would be better I think

Jevan.



------MTometvbaqimdskhwyojreumesocxluzyx
Content-Type: text/html

<html>
<head>
</head>
<body>
When I copy text that has been displayed from an &#34;ol&#34; ordered list <br />
element on a web page in firefox, and paste it into notepad, the text is <br />
copied but the numbers are not. To me this seems like a problem, what do <br />
you think?<br />
<br />
If you don't believe me try it at<br />
<br />
<a href="https://www.w3schools.com/html/tryit.asp?filename=tryhtml_lists_ordered">https://www.w3schools.com/html/tryit.asp?filename=tryhtml_lists_ordered</a><br />
<br />
The code is:<br />
<br />
&lt;!DOCTYPE html&gt;<br />
&lt;html&gt;<br />
&lt;body&gt;<br />
&lt;h2&gt;An ordered HTML list&lt;/h2&gt;<br />
&lt;ol&gt;<br />
&nbsp;&nbsp;&nbsp;&lt;li&gt;Coffee&lt;/li&gt;<br />
&nbsp;&nbsp;&nbsp;&lt;li&gt;Tea&lt;/li&gt;<br />
&nbsp;&nbsp;&nbsp;&lt;li&gt;Milk&lt;/li&gt;<br />
&lt;/ol&gt;<br />
&lt;/body&gt;<br />
&lt;/html&gt;<br />
<br />
What it comes out when copied from the web page displayed (not from the <br />
source) and pasted into notepad is<br />
<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Coffee<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Tea<br />
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Milk<br />
<br />
not<br />
<br />
1. Coffee<br />
2. Tea<br />
3. Milk<br />
<br />
The latter would be better I think<br />
<br />
Jevan.<br />
<br />
<br />

<img src="http://ts.msgtag.net/bfmfgxBx/Fno/Dn/zexDp/pzj/azsinprqA/ww.gif" alt=" " border="0" id="MSGTAGImage"/></body>
</html>

------MTometvbaqimdskhwyojreumesocxluzyx--


From nobody Fri Jun 30 06:59:57 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 0177D124B0A for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 06:59:55 -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, 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=dE1UciUx; dkim=pass (1024-bit key) header.d=yitter.info header.b=gBW2Th7n
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5cyP5_z0aaXz for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 06:59:52 -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 75EAB1201F8 for <ietf@ietf.org>; Fri, 30 Jun 2017 06:59:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mx4.yitter.info (Postfix) with ESMTP id C55B7C0355 for <ietf@ietf.org>; Fri, 30 Jun 2017 13:59:51 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1498831191; bh=T3i1k3QF+IgjnOCK7AUyHGPMV6yA5EoytS6ucwNPLus=; h=Date:From:To:Subject:References:In-Reply-To:From; b=dE1UciUxBMQ7GAqTdAyVZzT89qeGnUBnIs5UiXXECydV+vBySCHqxxTitbdZtiziu t0+bCLM+9OKFtDRabR0xJ7wIQfITwU3kWwFunRJLp5e38iSPEp9vjarAY4ZfZuAJ9m uVudug1D2EEXRYQKRSBrbw6ccJ4r3WOD+GME6La0=
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 3bEWvceWNpVf for <ietf@ietf.org>; Fri, 30 Jun 2017 13:59:50 +0000 (UTC)
Date: Fri, 30 Jun 2017 09:59:49 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yitter.info; s=default; t=1498831190; bh=T3i1k3QF+IgjnOCK7AUyHGPMV6yA5EoytS6ucwNPLus=; h=Date:From:To:Subject:References:In-Reply-To:From; b=gBW2Th7nghgS2aC83jDZDEkIwP6mZnZuU8kIlEJJGYeTJk+KtpShq19PfZIj+J0CW 4lZ8fuC1dfAh9C8eyFu2hAnYP9pLtbsJZyBqEdr6Je8zjlTgwayAnzMVuZEK0eAPY6 /QC59Of03IP44RJozEYlCn318U1SLr0VuK1IBqfc=
From: Andrew Sullivan <ajs@anvilwalrusden.com>
To: ietf@ietf.org
Subject: Re: About ccTLDs and gTLDs
Message-ID: <20170630135949.q7fr2ja7erhbjus5@mx4.yitter.info>
References: <51541b4b-a58a-9430-9426-5486edbc1540@gih.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <51541b4b-a58a-9430-9426-5486edbc1540@gih.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/E3Hc2s7t2Egi5IIp--AJsQ3o2HA>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 13:59:55 -0000

On Fri, Jun 30, 2017 at 07:31:58AM +0200, Olivier MJ Crépin-Leblond wrote:
> Hello all,
> 
> I am reading RFC1591 and RFC3071 and have a couple of simple questions:
> 1. Is a ccTLD defined as restricted to 2-letter country codes (ISO3166
> alpha 2), or could that include 3-letter country codes in the ISO3166
> list (ISO3166 alpha 3)?

RFC 1591 says, "the two letter country codes from ISO-3166," so I
don't see why the 3-letter codes would be included.  I can think of a
good reason _not_ to include 3 letter codes, and that is the potential
for collision with other 3-letter TLDs.  (I believe that the
traditional resistance to adding _any_ 2-letter TLD, even if it's not
on the 3166 list, comes from the possibility that a new country will
happen that could collide with such a 2-letter TLD.  The ISO list
isn't static, and simply reserving everything in the space seems
prudent.  I will not comment on the wisdom of adding "country codes"
that are not on the 3166 2-letter list, except to note the text in
1591, "The IANA is not in the business of deciding what is and what is
not a country.")

> 2. RFC1591 appears to point at 2-letter, but many other parts of this
> RFC are obsolete - so does this RFC remain valid?

I am not sure what you mean by "parts of this RFC are obsolete".
There does not appear to be any RFC that obsletes or even updates RFC
1591.

What of course is true is that there is a community that has taken
over the policy role for the root zone, and it might be that that
community regards some of the text as obsolete.  As I pointed out
repeatedly to colleagues around ICANN during the preparation for the
IANA transition, 1591 is not holy writ.  People could update or
obsolete it at any time by using the normal processes for obsoleting
or updating an RFC.  There is the small problem of who has change
control over RFC 1591, since it is not obviously a product of the IETF
and looks like it might have been a product of IANA.  More likely,
since ICANN is in the business of making policies for the root zone
anyway, ICANN could simply issue a new document that it says it will
follow, and publish a statement that for its policy purposes RFC 1591
has been superseded by $document(s).

I got the impression, however, during those conversations, that
several people prefer the current ambiguity because it allows for
divergent opinions, with each opinion holder able to cite some
document.  Whether this is because there is an unresolved difference
of opinion that is hidden behind such appeals, or whether some people
just like to have something to argue about so they can go to meetings,
I cannot say.

Best regards,

A

-- 
Andrew Sullivan
ajs@anvilwalrusden.com


From nobody Fri Jun 30 07:13:35 2017
Return-Path: <joelja@bogus.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 E837312EC23; Fri, 30 Jun 2017 07:13:33 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Jaeggli <joelja@bogus.com>
To: <ops-dir@ietf.org>
Cc: spring@ietf.org, ietf@ietf.org, draft-ietf-spring-oam-usecase.all@ietf.org
Subject: Opsdir last call review of draft-ietf-spring-oam-usecase-06
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149883201392.4666.499169365560986574@ietfa.amsl.com>
Date: Fri, 30 Jun 2017 07:13:33 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/heqYN1OiQgSsZ-heyGju2mbkveE>
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, 30 Jun 2017 14:13:34 -0000

Reviewer: Joel Jaeggli
Review result: Has Nits

I have reviewed

draft-ietf-spring-oam-usecase-06 as par of the OPS directorate review cycle
forIETF last call.

In general I think this document is ready to go however I have a couple of
concerns that should probably at least be discussed prior to IESG review.

>From my vantage point the document is not so much a description of a use case
or requirements as it is the architectural wrapper around
draft-ietf-mpls-spring-lsp-ping. It's most helpful in my opinion to review this
one as though the other one was the companion document, from this vantage point
I think the later document is effectively normatively referenced. Similarly the
readiness of the later document (which is a bit earlier in it's lifecycle)
raises the question of whether this one is ready to go.

in the security considerations section the document notes:

   As mentioned in the introduction, a PMS monitoring packet should
   never leave the domain where it originated.  It therefore should
   never use stale MPLS or IGP routing information.

I think is is more accurate to say:

Use of stale MPLS or IGP routing information could cause a PMS monitoring
packet to leave the domain where it originated. PMS monitoring packets should
not be sent using stale MPLS or IGP routing information.

As it is necessary to know that the information is stale is order to follow the
instruction, as is the case with for example convergence events that may be
ongoing at the time of diagnostic measurement.



From nobody Fri Jun 30 08:43:51 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 D8A88129B16; Fri, 30 Jun 2017 08:43:35 -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-teas-gmpls-scsi.all@ietf.org, ietf@ietf.org, teas@ietf.org
Subject: Genart last call review of draft-ietf-teas-gmpls-scsi-03
X-Test-IDTracker: no
X-IETF-IDTracker: 6.55.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149883741586.4634.17173245619136808055@ietfa.amsl.com>
Date: Fri, 30 Jun 2017 08:43:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/mhGJqkfUEU0Ijy1C6rpLT4TJZ58>
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, 30 Jun 2017 15:43:36 -0000

Reviewer: Robert Sparks
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-teas-gmpls-scsi-03
Reviewer: Robert Sparks
Review Date: 2017-06-30
IETF LC End Date: 2017-07-13
IESG Telechat date: 2017-08-03

Summary: Ready with nits

I think this document wins the humorous autocorrect-generated (I hope) typo of
the week. See the last sentence of the second paragraph of the IANA
considerations. I suspect you want a different final word.

I also expect IANA will send the decision for which of the options for placing
the registry you suggest back to the group. You would save time by just making
the decision now. Ask IANA now if you want their opinion on how the choice
should go.



From nobody Fri Jun 30 08:50:47 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 2F648129B21 for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 08:50:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 qdDujcqrdRZT for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 08:50:44 -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 1DD35129B0E for <ietf@ietf.org>; Fri, 30 Jun 2017 08:50:44 -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 1dQyBu-000Fyn-9z; Fri, 30 Jun 2017 11:50:42 -0400
Date: Fri, 30 Jun 2017 11:50:36 -0400
From: John C Klensin <john-ietf@jck.com>
To: =?UTF-8?Q?Olivier_MJ_Cr=C3=A9pin-Leblond?= <ocl@gih.com>, IETF <ietf@ietf.org>
Subject: Re: About ccTLDs and gTLDs
Message-ID: <CA3EDEF73364C49363D0CD89@PSB>
In-Reply-To: <51541b4b-a58a-9430-9426-5486edbc1540@gih.com>
References: <51541b4b-a58a-9430-9426-5486edbc1540@gih.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/C1DJgDPZeOV-WwY__2sNKMn1gLw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 15:50:46 -0000

--On Friday, June 30, 2017 07:31 +0200 Olivier MJ
Cr=C3=A9pin-Leblond <ocl@gih.com> wrote:

> Hello all,
>=20
> I am reading RFC1591 and RFC3071 and have a couple of simple
> questions: 1. Is a ccTLD defined as restricted to 2-letter
> country codes (ISO3166 alpha 2), or could that include
> 3-letter country codes in the ISO3166 list (ISO3166 alpha 3)?
> 2. RFC1591 appears to point at 2-letter, but many other parts
> of this RFC are obsolete - so does this RFC remain valid?

Olivier,

First, it is important to understand that RFC 1591 was never an
IETF document.  It was an IANA policy document, dating from a
time that IANA operated largely independent of the IETF (the
IETF could _request_ registration actions or registry creation,
but not _order_ them and so could others) and, while it
(deliberately, IIR) didn't strongly call that out, reflecting
policies and norms that had been in effect, although evolving
somewhat, long before the time it was published.

It may also be useful to recall that the practical authority of
IANA in the DNS space at that time was derived from two things.
The first is what is known (especially next week) on this side
of the pond as the "consent of the governed": just about
everyone understood that a central registration and allocation
authority was important and, with one important exception [1],
no one had something they believed was a better idea that they
were anxious to propose.  Yes, in theory the US Government could
have stepped in, but they didn't and their behavior was such as
to lead everyone to believe that they wouldn't.   The second was
that there was a general belief that, if the rules, especially
those involving principles of responsible behavior that 1591
invokes with the "trustee for the ... community" language, were
violated IANA had both the authority and the will to, e.g., make
changes in delegations to parties who would be more responsible.

There were also a number of things -- both "rules" and
explanations -- that didn't go into 1591, either because we
didn't think of them (or think they were necessary) or because
Jon saw them simply as things he wasn't going to allow.   The
now-famous "will be alphabetic" phrasing in RFC 1123 about TLD
labels was typical: Jon knew he simply was not going to allow
TLD names containing anything other than ASCII letters.

Whether the principles underlying 1591 are "obsolete" or not
depends on some complicated questions involving one's view of
the Internet and the role of the DNS (see
draft-klensin-dns-function-considerations as well as several
RFCs that followed 1591.  Certainly, when 1591 was written, we
didn't anticipate either ICANN or the rise of the domain name
business (and, arguably, its dominance in decision-making).

Now, with that background, let me try to answer your question.
First, the ccTLD naming model was strictly limited to allocated
codes in what is now called ISO 3166-1 alpha-2 [1].
Specifically, no use of the reserved list (not sure that existed
at the time either), no private-use codes, no codes allocated by
IANA rather than a body fully responsible to ISO TC 46, and,
while there are a couple of famous mistakes (history and
explanation on request if relevant) no allocations on
speculation.

One of those rules was, AFAKK, never formally published although
at least part of it was widely understood.  That was that TLD
labels came in categories that could be determined by length,
such that filters and algorithms could be based on those
categories.  The rule was 2-3.4+, i.e.,

 * All two-letter labels were country codes derived from
	3166 alpha-2.
 * All three letter labels were generic TLDs (not all of
	which were managed under IANA supervision).
 * All labels of four characters or more were either the
	specific string "ARPA" (which was originally intended to
	be temporary and transitional) or what is now known as a
	"special use name", i.e., one that is not part of the
	global DNS or that was expected to be processed using
	some non-DNS mechanism.

ICANN staff were warned about that rule in the 1999 period but
decided to allow TLD applications for gTLDs with labels longer
than three characters and to not identify the issue to
applicants.   Many of the issues that are now seen as "universal
acceptance" problems are the result of that decision.  Whether
one assumed at the time, or concludes now, that it was a
rational, consensus, decision to favor applicant choice and
consequent competition in the TLD marketplace over that
historical rule or, even the controversies about special names,
a screwup and/or show of arrogance is very much in the mind of
the beholder.

Similarly, ICANN clearly broke the 1591 rules in allocating "EU"
as a TLD label.  It is not an ISO 3166-1 alpha-2 registered
country code and it violates some territorial overlap rules that
are intrinsic to bother 3166-1 and the assumptions underlying
1591.  At a different end of the problem, IANA's rules (pointed
to but maybe not explicit enough) is that, if a country
convinced 3166/MA to change its code, there needed to be a plan
in place to remove the older TLD within a reasonably short
period before the new code would be delegated (on a "one
territory, one code" principle)).  IIR, there was such an
agreement about "SU" before "RU" was delegated, but ICANN has
never succeeded in getting rid of "SU", violating that =
principle.

All of this is further complicated by IDN TLDs, where new ones
associated with countries are not limited to two characters
(even in their original scripts); non-country political entities
are allowed (if one counts GOV. MIL, and maybe INT, they have
always been allowed, but those are probably a bit different(;
and the relationships between 3166 alpha-2 ccTLDs and their IDN
relatives have never really been spelled out (despite the length
of the ccTLD Fast Track Procedure.

Whether that makes 3166 partially or completely obsolete is a
matter of personal judgment.   Because it was an IANA document,
the IETF Protocol Police would never have arrested anyone for
violating it.  Unlike the IETF and its relationship to the
Protocol Police, IANA did have the ability to enforce its
provisions (and did).  ICANN has clearly demonstrated a
willingness to violate some of its provisions (explicit or
implied) and it appears that, both prior and subsequent to the
recent "IANA transition", there is no one to tell them that they
cannot do so.  My personal opinion that the Internet would be
much better off if the principles of 1591, especially the
requirement that registries be required to act in the best
interests of the global Internet community, were followed and
enforced (see draft-klensin-idna-rfc5891bis for the specific
IDNA case) are probably worth a cup of fancy coffee after a few
Euros (or equivalent) are thrown in.

best,
    john


[1] The dissenters were largely arguing for abandoning the DNS
in favor of X.500.  At least in public, that position was
justified on the basis of developing and future technology, with
the side effect of putting the top-level entities under the
control of the ISO and ITU registration processes.
Interestingly, with regard to your question, X.500 uses ISO
3166-1 alpha-2 country codes as well.

[2]  I don't think there was more than one part of ISO 3166 at
the time Jon discovered or was pointed to the Standard and can't
remember if it contained the alpha-3 codes in addition to the
alpha-2 and numeric ones.  I do know that we never considered
anything other than the alpha-2 codes for ccTLD names, if only
because Jon wanted that system to be as deterministic as
possible with no possibility about arguments about what code
should be assigned that IANA needed to referee.   =20



From nobody Fri Jun 30 09:01:40 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 64E8412F17A for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 09:01:37 -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=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 dwN0TMvySXOy for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 09:01:34 -0700 (PDT)
Received: from p3plsmtpa07-06.prod.phx3.secureserver.net (p3plsmtpa07-06.prod.phx3.secureserver.net [173.201.192.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 D7305128961 for <ietf@ietf.org>; Fri, 30 Jun 2017 09:01:33 -0700 (PDT)
Received: from spectre ([173.8.184.78]) by :SMTPAUTH: with SMTP id QyLtdTtTpSSXYQyLtdpIrE; Fri, 30 Jun 2017 09:01:02 -0700
From: "Peter Yee" <peter@akayla.com>
To: "'Dearlove, Christopher \(UK\)'" <chris.dearlove@baesystems.com>, <gen-art@ietf.org>
Cc: <manet@ietf.org>, <ietf@ietf.org>, <draft-ietf-manet-rfc5444-usage.all@ietf.org>
References: <149880519611.4622.17798538360710855866@ietfa.amsl.com> <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636FB1D@GLKXM0003v.GREENLNK.net>
In-Reply-To: <B31EEDDDB8ED7E4A93FDF12A4EECD30DE636FB1D@GLKXM0003v.GREENLNK.net>
Subject: RE: Genart last call review of draft-ietf-manet-rfc5444-usage-06
Date: Fri, 30 Jun 2017 09:01:09 -0700
Message-ID: <02dc01d2f1ba$172111e0$456335a0$@akayla.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-us
Thread-Index: AQCr02KVCrHuUUtTB2jHVPMoKtTFcAJ14pcJpHgY+6A=
X-CMAE-Envelope: MS4wfFFNdpLC2U4iBWKItez/+Xfaw6RSq2m8F/tPywpa5b+D1Wrrn027PR9J4qV8WqyLXUPjL69p3td8Mx0G/eLYgN3z1bOllrpnV6P64yRpAHU0jK4ER3iK DQLArN4QqsRItGA6F5dflmh+bPfuPUxbdrAZWvC8sQTvB07P46OkS8dHHP2kiFGPvn5nJ+YCD2TOCJpNnjUix9PSBN4aceX6D4DGPHd2lJFmphZzN2k270nH 91KEmtTruY0B5KNB3wXE4OUluMRpfETX4C7mrYFVYBx9Pz0QEZxOu070wD7E4HBD/TlovK+WGureHx/1GhX7jw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/5BZQiu0EwNaJpI3nKCl6c7p4hRM>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 16:01:37 -0000

Christopher,

	Thanks for clarifying what the implementation paragraph is supposed to =
convey.  It wasn't clear to me that this applied only within the router =
or that it would be over-the-wire identical.

	As for the commas, there were a lot of them.  I didn't even start =
trying to clean them up until part way through the review.  As you note, =
some of them are tricky.  That was part of the problem I had in reading =
the draft - dense sentences that strung together lengthy clauses =
requiring the reader to refer to earlier bits in the sentence in order =
to make sure the meaning was understood.  To be clear, I'm not saying =
anything stated in the draft appeared to be incorrect.  It just made for =
more difficult reading and parsing.

	I appreciate the quick response and look forward to reading the revised =
document.

		-Peter

-----Original Message-----
From: Dearlove, Christopher (UK) [mailto:chris.dearlove@baesystems.com]=20
Sent: Friday, June 30, 2017 2:07 AM
To: Peter Yee; gen-art@ietf.org
Cc: manet@ietf.org; ietf@ietf.org; =
draft-ietf-manet-rfc5444-usage.all@ietf.org
Subject: RE: Genart last call review of =
draft-ietf-manet-rfc5444-usage-06

Peter

Thanks you for your comments. I should note that the following comments =
are mine, not yet consulted with my co-authors.

I'm going to mostly disagree with your disagreement about the indicated =
point being an implementation issue. What matters is consistency at a =
router. Between routers doesn't matter. If router A adds the TLV in the =
multiplexer or the protocol, the on-air message is identical. And it =
doesn't matter if router B receiving a packet makes the opposite =
decision, as long as router B's multiplexer and protocol are consistent. =
I believe one reason for this comment is that different implementers =
have made different decisions. Because there is consistency needed on a =
router is why it says it is "in part".

However, I would agree, re-reading it again, that as worded, it doesn't =
come over as clearly as it should, so we will look at re-wording it.

I don't agree with all of your comments about commas. Just to take the =
first, simply removing the comma is not correct because "but did not =
quite succeed in" is a parenthesis. However, fails to be correct because =
attempted and succeed take different prepositions. But then "attempted =
to providing" is of course incorrect. So that sentence needs work, but =
not simply removal of a comma. I will take a look at each case (which I =
haven't yet done), but ultimately of course the RFC Editor will act as =
the arbiter of such matters.

Christopher

--
Christopher Dearlove
Senior Principal Engineer
BAE Systems Applied Intelligence Laboratories =
_________________________________________________________________________=
_

T:  +44 3300 467500  |  E: 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: Peter Yee [mailto:peter@akayla.com]
Sent: 30 June 2017 07:47
To: gen-art@ietf.org
Cc: manet@ietf.org; ietf@ietf.org; =
draft-ietf-manet-rfc5444-usage.all@ietf.org
Subject: Genart last call review of draft-ietf-manet-rfc5444-usage-06

----------------------! 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.
--------------------------------------------------------

Reviewer: Peter Yee
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-manet-rfc5444-usage-06
Reviewer: Peter Yee
Review Date: 2017-06-29
IETF LC End Date: 2017-06-29
IESG Telechat date: 2017-07-06

Summary: Ready with issues.

Major issues:

Minor issues:

Page 12, 2nd bullet item: I disagree that this is an implementation =
detail.=20
Unless there's additional signaling which indicates which implementation =
generated the packet, how is the receiving demultiplexer to know whether =
the sending multiplexer added a Message TLV or that was done by the =
protocol?

Nits/editorial comments:

General:

Somebody  needs to strangle the comma fairy.  She was a bit too liberal =
with this document. ;-)  I didn't take the time to clean up all of the =
excess commas, but many are noted below.

Change "end to end" to "end-to-end" throughout the document.

Specific:

Page 3, Section 1, 2nd paragraph, 1st sentence: delete the comma after =
"in".

Page 3, Section 1, 3rd paragraph: delete the comma after "[RFC5444]".

Page 4, 1st full bullet item, 2nd sentence: delete the commas after =
"process"
and "usage".  Change "is" to "are".

Page 5, 1st bullet item, 3rd sentence: delete "of" after "design".

Page 5, last bullet item: append a comma after "count".

Page 6, last paragraph, 2nd sentence: insert "may" before "pass".  =
Change the comma after "rules" to a semicolon.

Page 7, Section 1.3: change "makes" to "make" in both place.  Change =
"impedes"
to "impede".

Page 7, Section 2, 2nd paragraph: append a comma after \"TLV\".

Page 9, Section 4.3, 2nd paragraph, 2nd sentence: append a comma after =
"Originator Address".

Page 10, Section 4.4.1, 1st bullet item, 1st sentence: elide the comma =
after "protocol".

Page 11, 1st bullet item, 2nd sentence: change "of" to "or".

Page 11, 3rd bullet item, 3rd sentence: remove the comma after =
"[RFC5444]".

Page 12, 3rd bullet item: change the comma to a semicolon.

Page 13, Section 4.5 title: append a comma after "Addresses".

Page 13, Section 4.5, 3rd bullet item: change "an" to "a".

Page 14, 4th bullet item: delete the comma after "Message".

Page 14, last paragraph: add a comma after "absence" and delete one =
following "location".

Page 15, 1st full paragraph: insert "it" before "could".

Page 15, 2nd paragraph, 2nd sentence: change "routers" to "router's" or =
"routers'".

Page 15, 4th paragraph, 2nd sentence: change the comma after TLV to a =
semicolon.

Page 15, 5th paragraph: delete the commas after "Type" and "Value".

Page 17, 1st partial paragraph, 1st full sentence: change "MPR_WILLNG" =
to "MPR_WILLING".

Page 17, 1st full bullet item, 1st sentence: Strike the comma after =
"[RFC7182]".

Page 17, Section 5, 1st paragraph: delete the comma.

Page 17, Section 5, 1st paragraph after the bullet items: change the =
comma after "structural" to a period.  Capitalize the follow "they".  =
Insert "are"
before "field lengths" if that makes sense.

Page 17, last paragraph: append a comma after "Block".

Page 18, 2nd bullet item: add a comma after "Block".  Delete the comma =
after "TLV".

Page 18, 2nd paragraph, 1st sentence: elide the comma after "[RFC5444]".

Page 18, 2nd paragraph, 2nd sentence: delete the comma after "accepted".

Page 18, 2nd paragraph, 3rd sentence: remove the comma after =
"mechanism".

Page 18, 2nd paragraph, 5th sentence: change "4 bit" to "4-bit".

Page 18, Section 6, 1st sentence: delete the commas following =
"different", "same", "specification", and "information".

Page 18, Section 6, 2nd sentence: change the comma following "[RFC5444]" =
to a period.  Capitalize the following "any".

Page 19, 2nd to last paragraph, 1st sentence: change the comma after =
"only" to a semicolon.

Page 19, 2nd to last paragraph, 2nd sentence: change the comma after =
"6.2)" to a semicolon.

Page 19, last paragraph, 1st sentence: strike the comma after the 4th =
occurrence of "addresses".

Page 19, last paragraph, 2nd sentence: append a comma after "example".

Page 20, Section 6.2, 1st paragraph: delete the comma.

Page 20, 1st bullet item: remove the comma after "straightforward".

Page 20, 2nd bullet item: change the second comma to a period.  =
Capitalize the following "see".

Page 21, 2nd paragraph, 2nd sentence: elide the comma after "advice".

Page 21, 2nd paragraph, last sentence: I can't parse this sentence.  =
Consider rewriting for clarity.  There seems to be a missing clause.

Page 22, bullet item: delete the comma after "allowed".

Page 24, Appendix A, 1st paragraph, 2nd sentence: delete all of the =
commas.

Page 24, Appendix A, 1st paragraph after the bullet items, 2nd sentence: =
delete both commas.

Page 25, Appendix B, 1st sentence: append a comma after "valuedness".

Page 25, Appendix B, 2nd sentence: remove the comma following =
"creation".

Page 25, Appendix B, 3rd sentence: change the comma after "independent" =
to a period.  Capitalize the following "for".

********************************************************************
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 Fri Jun 30 09:51:33 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 5072E130140 for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 09:51:28 -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] 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 jvDmndyIqISQ for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 09:51:26 -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 5602912F3D5 for <ietf@ietf.org>; Fri, 30 Jun 2017 09:51:26 -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 1dQz8e-000G4R-Ph; Fri, 30 Jun 2017 12:51:24 -0400
Date: Fri, 30 Jun 2017 12:51:18 -0400
From: John C Klensin <john-ietf@jck.com>
To: Andrew Sullivan <ajs@anvilwalrusden.com>, ietf@ietf.org
Subject: Re: About ccTLDs and gTLDs
Message-ID: <FC98C91ACD76B48AA6BCF576@PSB>
In-Reply-To: <20170630135949.q7fr2ja7erhbjus5@mx4.yitter.info>
References: <51541b4b-a58a-9430-9426-5486edbc1540@gih.com> <20170630135949.q7fr2ja7erhbjus5@mx4.yitter.info>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
X-SA-Exim-Connect-IP: 198.252.137.10
X-SA-Exim-Mail-From: john-ietf@jck.com
X-SA-Exim-Scanned: No (on bsa2.jck.com); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/ZryBqx-aoWht612EnLKqRW8ew9o>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 16:51:28 -0000

--On Friday, June 30, 2017 09:59 -0400 Andrew Sullivan
<ajs@anvilwalrusden.com> wrote:

> On Fri, Jun 30, 2017 at 07:31:58AM +0200, Olivier MJ
> Cr=C3=A9pin-Leblond wrote:
>> Hello all,
>>=20
>> I am reading RFC1591 and RFC3071 and have a couple of simple
>> questions: 1. Is a ccTLD defined as restricted to 2-letter
>> country codes (ISO3166 alpha 2), or could that include
>> 3-letter country codes in the ISO3166 list (ISO3166 alpha 3)?

>...(I believe that the traditional resistance to adding
> _any_ 2-letter TLD, even if it's not on the 3166 list, comes
> from the possibility that a new country will happen that could
> collide with such a 2-letter TLD.  The ISO list isn't static,
> and simply reserving everything in the space seems prudent.

Exactly.  Even using codes that 3166-1 designates as "private
use" is dangerous because there is not reason why some future
version to the standard might not press those codes into use if
the available code space becomes limited (more likely since the
p9licy as to how long 3166/MA needed to wait before reallocating
a code that was no longer used was expanded from five years to
some really long period).

It is worth being explicit about something Andrew implies.  If
XX were to be delegated to some non-country entity and then a
country comes along and is assigned that code by 3166/MA, there
is an immediate and nasty crisis because there is no model for
allocating any other code to the country and whatever entity had
been delegated XX would certainly object to having it taken away
and presumably having all of its registrations cancelled.   Many
pre-ICANN IANA policies were designed around avoiding, rather
than encouraging, such problems.

> will not comment on the wisdom of adding "country codes" that
> are not on the 3166 2-letter list, except to note the text in
> 1591, "The IANA is not in the business of deciding what is and
> what is not a country."

While there was another reason for that statement, yes.  3166
was chosen both because it provided an explicit list of entities
that could request/ register ccTLDs and because it avoid
arguments about what the country code/ label should be, with
neither decision requiring IANA involvement.  I've mentioned
several times in various discussions that IANA resisted sending
even an observer to 3166/MA until well after the transition to
ICANN because Jon didn't want anyone to be able to try to demand
that he propose adding a country-entity and code to 3166 in
other that a TDL could then be registered.

>> 2. RFC1591 appears to point at 2-letter, but many other parts
>> of this RFC are obsolete - so does this RFC remain valid?
>=20
> I am not sure what you mean by "parts of this RFC are
> obsolete". There does not appear to be any RFC that obsletes
> or even updates RFC 1591.
>=20
> What of course is true is that there is a community that has
> taken over the policy role for the root zone, and it might be
> that that community regards some of the text as obsolete.  As
> I pointed out repeatedly to colleagues around ICANN during the
> preparation for the IANA transition, 1591 is not holy writ.
> People could update or obsolete it at any time by using the
> normal processes for obsoleting or updating an RFC.  There is
> the small problem of who has change control over RFC 1591,
> since it is not obviously a product of the IETF and looks like
> it might have been a product of IANA.

yes.  If definitely was.  I assume the IAB could have objected
had they wanted to, but that not only would have set of some
sort of constitutional crisis but, at least based on what I was
told at the time (much earlier than 1591), part of the reason
for establishing IANA as an entity was to keep IAB members
insulated from allocation decisions in order to avoid all sorts
of potential conflict of interest and antitrust problems.

>   More likely, since
> ICANN is in the business of making policies for the root zone
> anyway, ICANN could simply issue a new document that it says
> it will follow, and publish a statement that for its policy
> purposes RFC 1591 has been superseded by $document(s).

Of course, ICANN did issue a document that more or less
explicitly updates 1591 in the form of the May 1999 ICP-1.  Of
course, rather than obsoleting 1591, it references it and
essentially reaffirms it.  It even includes the "trustee for the
domain" and "obligation to serve the community" language.=20

> I got the impression, however, during those conversations, =
that
> several people prefer the current ambiguity because it allows
> for divergent opinions, with each opinion holder able to cite
> some document.  Whether this is because there is an unresolved
> difference of opinion that is hidden behind such appeals, or
> whether some people just like to have something to argue about
> so they can go to meetings, I cannot say.

No comment.

best,
   john

p.s. In case it is relevant, I was very actively involved in the
development and text of 1591 and some other IANA policies during
that period.





From nobody Fri Jun 30 09:53:35 2017
Return-Path: <dfk@ripe.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 1E35E12ECF5 for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 09:53:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ir2_sbq9jxHo for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 09:53:30 -0700 (PDT)
Received: from mahimahi.ripe.net (mahimahi.ripe.net [IPv6:2001:67c:2e8:11::c100:1372]) (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 94D0C12F4B2 for <ietf@ietf.org>; Fri, 30 Jun 2017 09:53:30 -0700 (PDT)
Received: from nene.ripe.net ([193.0.23.10]) by mahimahi.ripe.net with esmtps (TLSv1.2:DHE-RSA-AES256-GCM-SHA384:256) (Exim 4.84_2) (envelope-from <dfk@ripe.net>) id 1dQzAe-0002YJ-AP for ietf@ietf.org; Fri, 30 Jun 2017 18:53:29 +0200
Received: from sslvpn.ripe.net ([193.0.20.230] helo=reif.karrenberg.net) by nene.ripe.net with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84_2) (envelope-from <dfk@ripe.net>) id 1dQzAe-00052n-3K for ietf@ietf.org; Fri, 30 Jun 2017 18:53:28 +0200
Subject: Re:
To: ietf@ietf.org
References: <51541b4b-a58a-9430-9426-5486edbc1540@gih.com> <CA3EDEF73364C49363D0CD89@PSB>
From: Daniel Karrenberg <dfk@ripe.net>
Message-ID: <bd508ec0-a532-cd65-2b51-4dbd8f36de1c@ripe.net>
Date: Fri, 30 Jun 2017 18:53:27 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
In-Reply-To: <CA3EDEF73364C49363D0CD89@PSB>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-ACL-Warn: Delaying message
X-RIPE-Spam-Level: -------
X-RIPE-Spam-Report: Spam Total Points:   -7.5 points pts rule name              description ---- ---------------------- ------------------------------------ -7.5 ALL_TRUSTED            Passed through trusted hosts only via SMTP
X-RIPE-Signature: 87740cc88a4b7a0bf9ddec397c72be837e4d59d1bfc7b7d1cdf8519b0bcfd7a2
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/QTC9W3kYSeCb7hxJXFy0YjdxKR8>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 16:53:33 -0000

john,

your eloquently told story agrees with personal memory and my particular
version of reality ;-).

I know for a fact that ISO3166 at the time contained at least two letter
alphabetic, three letter alphabetic and numeric codes for each country
or territory recognized by the United Nations.

I also distinctly remember a number of conversations with Jon about DNS
"going international". Jon wisely saw that IANA needed an external
authority to decide what was a country. After considering several such
authorities, the United nations appeared the most widely agreed one.
>From there it was but a short step to ISO3166. The choice for two letter
alphabetic codes was also straightforward: there were no two letter TLDs
at the time and that guaranteed that there would be no clashes with
exiting TLDs. [1]

So I would argue that ASCII ccTLDs are indeed meant to be exactly two
letters. If only to avoid clashes with future changes to ISO3166 I would
consider it to be a Bad Idea to allocate two letter ASCII strings for
any other purpose. This is why I have spoken up against ".EU" until the
ISO3166 maintenance agency published it as a "reserved" code.

Conversely it would be problematic now to have three letter ASCII ccTLDs
unless there is a clear agreement with ISO that they will never allocate
a three letter code that already exists as a gTLD. Afaik there are no
clashes right now, but past results are not a guarantee for the future.
It is never a good idea to have two 'authorities' over one part of a
name space.

dfk

[1] UK appeared at different times in at least two realities that have
been recounted to me. ;-) But there was no clash in ISO3166 at the time.




On 1.01.70 1:00 ,  wrote:
> 
> 
> --On Friday, June 30, 2017 07:31 +0200 Olivier MJ
> Crépin-Leblond <ocl@gih.com> wrote:
> 
>> Hello all,
>>
>> I am reading RFC1591 and RFC3071 and have a couple of simple
>> questions: 1. Is a ccTLD defined as restricted to 2-letter
>> country codes (ISO3166 alpha 2), or could that include
>> 3-letter country codes in the ISO3166 list (ISO3166 alpha 3)?
>> 2. RFC1591 appears to point at 2-letter, but many other parts
>> of this RFC are obsolete - so does this RFC remain valid?
> 
> Olivier,
> 
> First, it is important to understand that RFC 1591 was never an
> IETF document.  It was an IANA policy document, dating from a
> time that IANA operated largely independent of the IETF (the
> IETF could _request_ registration actions or registry creation,
> but not _order_ them and so could others) and, while it
> (deliberately, IIR) didn't strongly call that out, reflecting
> policies and norms that had been in effect, although evolving
> somewhat, long before the time it was published.
> 
> It may also be useful to recall that the practical authority of
> IANA in the DNS space at that time was derived from two things.
> The first is what is known (especially next week) on this side
> of the pond as the "consent of the governed": just about
> everyone understood that a central registration and allocation
> authority was important and, with one important exception [1],
> no one had something they believed was a better idea that they
> were anxious to propose.  Yes, in theory the US Government could
> have stepped in, but they didn't and their behavior was such as
> to lead everyone to believe that they wouldn't.   The second was
> that there was a general belief that, if the rules, especially
> those involving principles of responsible behavior that 1591
> invokes with the "trustee for the ... community" language, were
> violated IANA had both the authority and the will to, e.g., make
> changes in delegations to parties who would be more responsible.
> 
> There were also a number of things -- both "rules" and
> explanations -- that didn't go into 1591, either because we
> didn't think of them (or think they were necessary) or because
> Jon saw them simply as things he wasn't going to allow.   The
> now-famous "will be alphabetic" phrasing in RFC 1123 about TLD
> labels was typical: Jon knew he simply was not going to allow
> TLD names containing anything other than ASCII letters.
> 
> Whether the principles underlying 1591 are "obsolete" or not
> depends on some complicated questions involving one's view of
> the Internet and the role of the DNS (see
> draft-klensin-dns-function-considerations as well as several
> RFCs that followed 1591.  Certainly, when 1591 was written, we
> didn't anticipate either ICANN or the rise of the domain name
> business (and, arguably, its dominance in decision-making).
> 
> Now, with that background, let me try to answer your question.
> First, the ccTLD naming model was strictly limited to allocated
> codes in what is now called ISO 3166-1 alpha-2 [1].
> Specifically, no use of the reserved list (not sure that existed
> at the time either), no private-use codes, no codes allocated by
> IANA rather than a body fully responsible to ISO TC 46, and,
> while there are a couple of famous mistakes (history and
> explanation on request if relevant) no allocations on
> speculation.
> 
> One of those rules was, AFAKK, never formally published although
> at least part of it was widely understood.  That was that TLD
> labels came in categories that could be determined by length,
> such that filters and algorithms could be based on those
> categories.  The rule was 2-3.4+, i.e.,
> 
>  * All two-letter labels were country codes derived from
> 	3166 alpha-2.
>  * All three letter labels were generic TLDs (not all of
> 	which were managed under IANA supervision).
>  * All labels of four characters or more were either the
> 	specific string "ARPA" (which was originally intended to
> 	be temporary and transitional) or what is now known as a
> 	"special use name", i.e., one that is not part of the
> 	global DNS or that was expected to be processed using
> 	some non-DNS mechanism.
> 
> ICANN staff were warned about that rule in the 1999 period but
> decided to allow TLD applications for gTLDs with labels longer
> than three characters and to not identify the issue to
> applicants.   Many of the issues that are now seen as "universal
> acceptance" problems are the result of that decision.  Whether
> one assumed at the time, or concludes now, that it was a
> rational, consensus, decision to favor applicant choice and
> consequent competition in the TLD marketplace over that
> historical rule or, even the controversies about special names,
> a screwup and/or show of arrogance is very much in the mind of
> the beholder.
> 
> Similarly, ICANN clearly broke the 1591 rules in allocating "EU"
> as a TLD label.  It is not an ISO 3166-1 alpha-2 registered
> country code and it violates some territorial overlap rules that
> are intrinsic to bother 3166-1 and the assumptions underlying
> 1591.  At a different end of the problem, IANA's rules (pointed
> to but maybe not explicit enough) is that, if a country
> convinced 3166/MA to change its code, there needed to be a plan
> in place to remove the older TLD within a reasonably short
> period before the new code would be delegated (on a "one
> territory, one code" principle)).  IIR, there was such an
> agreement about "SU" before "RU" was delegated, but ICANN has
> never succeeded in getting rid of "SU", violating that principle.
> 
> All of this is further complicated by IDN TLDs, where new ones
> associated with countries are not limited to two characters
> (even in their original scripts); non-country political entities
> are allowed (if one counts GOV. MIL, and maybe INT, they have
> always been allowed, but those are probably a bit different(;
> and the relationships between 3166 alpha-2 ccTLDs and their IDN
> relatives have never really been spelled out (despite the length
> of the ccTLD Fast Track Procedure.
> 
> Whether that makes 3166 partially or completely obsolete is a
> matter of personal judgment.   Because it was an IANA document,
> the IETF Protocol Police would never have arrested anyone for
> violating it.  Unlike the IETF and its relationship to the
> Protocol Police, IANA did have the ability to enforce its
> provisions (and did).  ICANN has clearly demonstrated a
> willingness to violate some of its provisions (explicit or
> implied) and it appears that, both prior and subsequent to the
> recent "IANA transition", there is no one to tell them that they
> cannot do so.  My personal opinion that the Internet would be
> much better off if the principles of 1591, especially the
> requirement that registries be required to act in the best
> interests of the global Internet community, were followed and
> enforced (see draft-klensin-idna-rfc5891bis for the specific
> IDNA case) are probably worth a cup of fancy coffee after a few
> Euros (or equivalent) are thrown in.
> 
> best,
>     john
> 
> 
> [1] The dissenters were largely arguing for abandoning the DNS
> in favor of X.500.  At least in public, that position was
> justified on the basis of developing and future technology, with
> the side effect of putting the top-level entities under the
> control of the ISO and ITU registration processes.
> Interestingly, with regard to your question, X.500 uses ISO
> 3166-1 alpha-2 country codes as well.
> 
> [2]  I don't think there was more than one part of ISO 3166 at
> the time Jon discovered or was pointed to the Standard and can't
> remember if it contained the alpha-3 codes in addition to the
> alpha-2 and numeric ones.  I do know that we never considered
> anything other than the alpha-2 codes for ccTLD names, if only
> because Jon wanted that system to be as deterministic as
> possible with no possibility about arguments about what code
> should be assigned that IANA needed to referee.    
> 
> 
> 


From nobody Fri Jun 30 10:21:50 2017
Return-Path: <d3e3e3@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 23FBB13144D for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 10:21:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Level: 
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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 r7hfowzD37Ok for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 10:21:47 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87CB3131448 for <ietf@ietf.org>; Fri, 30 Jun 2017 10:21:47 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id h64so27676851iod.0 for <ietf@ietf.org>; Fri, 30 Jun 2017 10:21:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XLk9hHUxxGdvKvtynMGFaX5Q/kle8hFo5AHMe8ilDw0=; b=iSer6OkxQgCcVS342cP+Tc/6QwQ1HkAjbDuN1MvCLQ6nxiRFh4qhFvPiISG+7caQ+H KQuV309fSrSFKuEQcjSJIs6uazmqSXvh8Unstq1x2E9JczIZI0yO94OJ8mwvmwV6Hem3 71DMB55wMISEbHGX5h5pH3Jt70jAo2zsP382rV2cX3giZPzqhEVsRo/tpRRoLKUqnkaq /l63EJKDfahWovTT5ekEXrDfsjjPbhzjU2BB3VFhP5mvTr0gohq2MjOakjzUltGnwKwC VkMIQTsA69bxzJFiof8emJcE4wpt+O2TCkEWnLq8dt7mVKHMjwUfpzMLn9mv5ApkQRFO EenA==
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=XLk9hHUxxGdvKvtynMGFaX5Q/kle8hFo5AHMe8ilDw0=; b=eIUX/pTcN1wYQfDnFF3PUwsAq0EV2DRcATuz55aKhP0iUD9RS+iMXrSp1H17Vb/ucn QV1mHtxma/sJ0VmbM0ovy0Fgqt6sqHLNwN16ZLjNc+O/T4Ah1Q6TTsy0JgPfZOueBsmx bGY/FnqX4VQgz6s7/ACTbsivRAb2TigKrICSJbS+QevvCed0VyeU/bJDKKgIlwbSYJ+M VeOh84ZNK7Y084mpNX1f1F+r1Cd5EpoCxF6ksOmS3IlmSA39pvRYsw3pOS2J/K2mmkzB gS3AnqyiyOnTwwp+9rKa/LY3HtWbruO/II3UaW7Lrs+qVt3CCKLIdPY44gen2gda+6Fv yPYA==
X-Gm-Message-State: AKS2vOyGqJJ5TvJU+qzhHTdopHXbBxwoogchcjEVCKKAIkBRLvm5WRih Mrf+fzf3fEpfD7vhZd03dpxvR5haOQ==
X-Received: by 10.107.4.19 with SMTP id 19mr22521114ioe.95.1498843306922; Fri, 30 Jun 2017 10:21:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.17.221 with HTTP; Fri, 30 Jun 2017 10:21:31 -0700 (PDT)
In-Reply-To: <bd508ec0-a532-cd65-2b51-4dbd8f36de1c@ripe.net>
References: <51541b4b-a58a-9430-9426-5486edbc1540@gih.com> <CA3EDEF73364C49363D0CD89@PSB> <bd508ec0-a532-cd65-2b51-4dbd8f36de1c@ripe.net>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 30 Jun 2017 13:21:31 -0400
Message-ID: <CAF4+nEE5+nF_biteqsbEThU8tSeN7SwuCZLun3MHuJYVGvn0rQ@mail.gmail.com>
Subject: Re:
To: Daniel Karrenberg <dfk@ripe.net>
Cc: IETF Discussion <ietf@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/IpbZF8dKT4BzuZkVlrFIA7tF1uw>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 17:21:49 -0000

On Fri, Jun 30, 2017 at 12:53 PM, Daniel Karrenberg <dfk@ripe.net> wrote:
> john,
>
> ...
>
> Conversely it would be problematic now to have three letter ASCII ccTLDs
> unless there is a clear agreement with ISO that they will never allocate
> a three letter code that already exists as a gTLD. Afaik there are no
> clashes right now, but past results are not a guarantee for the future.

COM is the three letter code for the Comoros Islands. I believe it is
also used by a few entities as their TLD :-)

> It is never a good idea to have two 'authorities' over one part of a
> name space.
>
> dfk

Thanks,
Donald


From nobody Fri Jun 30 12:21:01 2017
Return-Path: <ericding.ny@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 ECF79127867 for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 12:20:59 -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, MIME_QP_LONG_LINE=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 L6Ys_R-KaFU5 for <ietf@ietfa.amsl.com>; Fri, 30 Jun 2017 12:20:55 -0700 (PDT)
Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d: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 36B33126B7E for <ietf@ietf.org>; Fri, 30 Jun 2017 12:20:55 -0700 (PDT)
Received: by mail-qk0-x231.google.com with SMTP id v143so24537874qkb.0 for <ietf@ietf.org>; Fri, 30 Jun 2017 12:20:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:content-transfer-encoding:mime-version:date:subject:message-id :to; bh=gOlWZ+w8HJRU0SOyRhhB+lUG7aea7+5gQ2i81CH4u94=; b=OeDfBeniFPuGAhCojfCLRMsbxWqfcIC7PQMuWid6b6Tj3hUI8BcN5+4nioVQg0HSlE 7CtAeCENnl8dFfX/gUpnrzW/Lx4aNo3cTvRGoTixmiaabwQfC5KDmvc+q9YnIPrKAHA7 GHxZY+ha8hNel5Nvw9gACPczks4gVOBhujmgFkZoTu1juAUIngmDkbkjnnNrvLa39WgZ zIbc2Edl+FBQ0oF+1Www7tT3f8YIG6csDXtBwZhzYSzGUHHXz7jXYCNVoO0ZyjzDMC1o alZnyHZ6HSCLTx4kJ3rhKh4IUacF2PkvWiXkJrbxi+gqQSS3xA6f7wHoo8JTulXvAop/ gVqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version:date :subject:message-id:to; bh=gOlWZ+w8HJRU0SOyRhhB+lUG7aea7+5gQ2i81CH4u94=; b=UQ0+RZazWiN73MXmJteihRPe0eEr+an+Gg2UwYvnHVRQXxKPs0b+cn12+pOqC6rSLp /5nyV0793ZqZv09g591TFUm+OV73Pb4PsXzu5xXVU1YQLfHfWbHq1UZPuQ30nMyKv92E 5Xw9enKhnU3Xl90a3AqzhJZ3nEchQJfHDBaa23y2uQDipS77O10vxrTAe6wP3AmMiD+G QDjzmf4gSQkR3f5saOqq9cGPskdLg/xfdSOFo6B5C6Idp7tEo0PI4cJnVorruRUaZ4cg M1EKTzSHiOzNbh1FVrq/UgDnAOA6njOi1TP/et1iGAO96rIGQIcooJLKlwG2IRHSfTcT +WQg==
X-Gm-Message-State: AKS2vOwfzTkbM3pPRwV8sv1GPVvEhQFgvQ+mqF+9GGT3iQ6qpHEqc3M6 LmVmGo3cwXROArJKDu4=
X-Received: by 10.55.165.200 with SMTP id o191mr28225218qke.47.1498850454162;  Fri, 30 Jun 2017 12:20:54 -0700 (PDT)
Received: from [10.94.121.127] (mobile-166-171-185-82.mycingular.net. [166.171.185.82]) by smtp.gmail.com with ESMTPSA id i85sm6410556qke.66.2017.06.30.12.20.53 for <ietf@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 30 Jun 2017 12:20:53 -0700 (PDT)
From: Eric Ding <ericding.ny@gmail.com>
Content-Type: multipart/alternative; boundary=Apple-Mail-37EADE25-A591-4C22-A11E-44F726F1B2D6
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
Date: Fri, 30 Jun 2017 15:20:52 -0400
Subject: Unsubscribe
Message-Id: <766BC512-D078-4706-AF9F-2AA9296CDECE@gmail.com>
To: ietf@ietf.org
X-Mailer: iPhone Mail (14F89)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/JiG0xwZXgFiQwYTumbli-8n_RlI>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Jun 2017 19:21:00 -0000

--Apple-Mail-37EADE25-A591-4C22-A11E-44F726F1B2D6
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: 7bit

Unsubscribe

> On Jun 30, 2017, at 3:00 PM, ietf-request@ietf.org wrote:
> 
> Send ietf mailing list submissions to
>    ietf@ietf.org
> 
> To subscribe or unsubscribe via the World Wide Web, visit
>    https://www.ietf.org/mailman/listinfo/ietf
> or, via email, send a message with subject or body 'help' to
>    ietf-request@ietf.org
> 
> You can reach the person managing the list at
>    ietf-owner@ietf.org
> 
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of ietf digest..."
> 
> 
> Today's Topics:
> 
>   1. Re: (Daniel Karrenberg)
>   2. Re: (Donald Eastlake)
> 
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 30 Jun 2017 18:53:27 +0200
> From: Daniel Karrenberg <dfk@ripe.net>
> To: ietf@ietf.org
> Subject: Re:
> Message-ID: <bd508ec0-a532-cd65-2b51-4dbd8f36de1c@ripe.net>
> Content-Type: text/plain; charset=utf-8
> 
> john,
> 
> your eloquently told story agrees with personal memory and my particular
> version of reality ;-).
> 
> I know for a fact that ISO3166 at the time contained at least two letter
> alphabetic, three letter alphabetic and numeric codes for each country
> or territory recognized by the United Nations.
> 
> I also distinctly remember a number of conversations with Jon about DNS
> "going international". Jon wisely saw that IANA needed an external
> authority to decide what was a country. After considering several such
> authorities, the United nations appeared the most widely agreed one.
>> From there it was but a short step to ISO3166. The choice for two letter
> alphabetic codes was also straightforward: there were no two letter TLDs
> at the time and that guaranteed that there would be no clashes with
> exiting TLDs. [1]
> 
> So I would argue that ASCII ccTLDs are indeed meant to be exactly two
> letters. If only to avoid clashes with future changes to ISO3166 I would
> consider it to be a Bad Idea to allocate two letter ASCII strings for
> any other purpose. This is why I have spoken up against ".EU" until the
> ISO3166 maintenance agency published it as a "reserved" code.
> 
> Conversely it would be problematic now to have three letter ASCII ccTLDs
> unless there is a clear agreement with ISO that they will never allocate
> a three letter code that already exists as a gTLD. Afaik there are no
> clashes right now, but past results are not a guarantee for the future.
> It is never a good idea to have two 'authorities' over one part of a
> name space.
> 
> dfk
> 
> [1] UK appeared at different times in at least two realities that have
> been recounted to me. ;-) But there was no clash in ISO3166 at the time.
> 
> 
> 
> 
>> On 1.01.70 1:00 ,  wrote:
>> 
>> 
>> --On Friday, June 30, 2017 07:31 +0200 Olivier MJ
>> Cr?pin-Leblond <ocl@gih.com> wrote:
>> 
>>> Hello all,
>>> 
>>> I am reading RFC1591 and RFC3071 and have a couple of simple
>>> questions: 1. Is a ccTLD defined as restricted to 2-letter
>>> country codes (ISO3166 alpha 2), or could that include
>>> 3-letter country codes in the ISO3166 list (ISO3166 alpha 3)?
>>> 2. RFC1591 appears to point at 2-letter, but many other parts
>>> of this RFC are obsolete - so does this RFC remain valid?
>> 
>> Olivier,
>> 
>> First, it is important to understand that RFC 1591 was never an
>> IETF document.  It was an IANA policy document, dating from a
>> time that IANA operated largely independent of the IETF (the
>> IETF could _request_ registration actions or registry creation,
>> but not _order_ them and so could others) and, while it
>> (deliberately, IIR) didn't strongly call that out, reflecting
>> policies and norms that had been in effect, although evolving
>> somewhat, long before the time it was published.
>> 
>> It may also be useful to recall that the practical authority of
>> IANA in the DNS space at that time was derived from two things.
>> The first is what is known (especially next week) on this side
>> of the pond as the "consent of the governed": just about
>> everyone understood that a central registration and allocation
>> authority was important and, with one important exception [1],
>> no one had something they believed was a better idea that they
>> were anxious to propose.  Yes, in theory the US Government could
>> have stepped in, but they didn't and their behavior was such as
>> to lead everyone to believe that they wouldn't.   The second was
>> that there was a general belief that, if the rules, especially
>> those involving principles of responsible behavior that 1591
>> invokes with the "trustee for the ... community" language, were
>> violated IANA had both the authority and the will to, e.g., make
>> changes in delegations to parties who would be more responsible.
>> 
>> There were also a number of things -- both "rules" and
>> explanations -- that didn't go into 1591, either because we
>> didn't think of them (or think they were necessary) or because
>> Jon saw them simply as things he wasn't going to allow.   The
>> now-famous "will be alphabetic" phrasing in RFC 1123 about TLD
>> labels was typical: Jon knew he simply was not going to allow
>> TLD names containing anything other than ASCII letters.
>> 
>> Whether the principles underlying 1591 are "obsolete" or not
>> depends on some complicated questions involving one's view of
>> the Internet and the role of the DNS (see
>> draft-klensin-dns-function-considerations as well as several
>> RFCs that followed 1591.  Certainly, when 1591 was written, we
>> didn't anticipate either ICANN or the rise of the domain name
>> business (and, arguably, its dominance in decision-making).
>> 
>> Now, with that background, let me try to answer your question.
>> First, the ccTLD naming model was strictly limited to allocated
>> codes in what is now called ISO 3166-1 alpha-2 [1].
>> Specifically, no use of the reserved list (not sure that existed
>> at the time either), no private-use codes, no codes allocated by
>> IANA rather than a body fully responsible to ISO TC 46, and,
>> while there are a couple of famous mistakes (history and
>> explanation on request if relevant) no allocations on
>> speculation.
>> 
>> One of those rules was, AFAKK, never formally published although
>> at least part of it was widely understood.  That was that TLD
>> labels came in categories that could be determined by length,
>> such that filters and algorithms could be based on those
>> categories.  The rule was 2-3.4+, i.e.,
>> 
>> * All two-letter labels were country codes derived from
>>    3166 alpha-2.
>> * All three letter labels were generic TLDs (not all of
>>    which were managed under IANA supervision).
>> * All labels of four characters or more were either the
>>    specific string "ARPA" (which was originally intended to
>>    be temporary and transitional) or what is now known as a
>>    "special use name", i.e., one that is not part of the
>>    global DNS or that was expected to be processed using
>>    some non-DNS mechanism.
>> 
>> ICANN staff were warned about that rule in the 1999 period but
>> decided to allow TLD applications for gTLDs with labels longer
>> than three characters and to not identify the issue to
>> applicants.   Many of the issues that are now seen as "universal
>> acceptance" problems are the result of that decision.  Whether
>> one assumed at the time, or concludes now, that it was a
>> rational, consensus, decision to favor applicant choice and
>> consequent competition in the TLD marketplace over that
>> historical rule or, even the controversies about special names,
>> a screwup and/or show of arrogance is very much in the mind of
>> the beholder.
>> 
>> Similarly, ICANN clearly broke the 1591 rules in allocating "EU"
>> as a TLD label.  It is not an ISO 3166-1 alpha-2 registered
>> country code and it violates some territorial overlap rules that
>> are intrinsic to bother 3166-1 and the assumptions underlying
>> 1591.  At a different end of the problem, IANA's rules (pointed
>> to but maybe not explicit enough) is that, if a country
>> convinced 3166/MA to change its code, there needed to be a plan
>> in place to remove the older TLD within a reasonably short
>> period before the new code would be delegated (on a "one
>> territory, one code" principle)).  IIR, there was such an
>> agreement about "SU" before "RU" was delegated, but ICANN has
>> never succeeded in getting rid of "SU", violating that principle.
>> 
>> All of this is further complicated by IDN TLDs, where new ones
>> associated with countries are not limited to two characters
>> (even in their original scripts); non-country political entities
>> are allowed (if one counts GOV. MIL, and maybe INT, they have
>> always been allowed, but those are probably a bit different(;
>> and the relationships between 3166 alpha-2 ccTLDs and their IDN
>> relatives have never really been spelled out (despite the length
>> of the ccTLD Fast Track Procedure.
>> 
>> Whether that makes 3166 partially or completely obsolete is a
>> matter of personal judgment.   Because it was an IANA document,
>> the IETF Protocol Police would never have arrested anyone for
>> violating it.  Unlike the IETF and its relationship to the
>> Protocol Police, IANA did have the ability to enforce its
>> provisions (and did).  ICANN has clearly demonstrated a
>> willingness to violate some of its provisions (explicit or
>> implied) and it appears that, both prior and subsequent to the
>> recent "IANA transition", there is no one to tell them that they
>> cannot do so.  My personal opinion that the Internet would be
>> much better off if the principles of 1591, especially the
>> requirement that registries be required to act in the best
>> interests of the global Internet community, were followed and
>> enforced (see draft-klensin-idna-rfc5891bis for the specific
>> IDNA case) are probably worth a cup of fancy coffee after a few
>> Euros (or equivalent) are thrown in.
>> 
>> best,
>>    john
>> 
>> 
>> [1] The dissenters were largely arguing for abandoning the DNS
>> in favor of X.500.  At least in public, that position was
>> justified on the basis of developing and future technology, with
>> the side effect of putting the top-level entities under the
>> control of the ISO and ITU registration processes.
>> Interestingly, with regard to your question, X.500 uses ISO
>> 3166-1 alpha-2 country codes as well.
>> 
>> [2]  I don't think there was more than one part of ISO 3166 at
>> the time Jon discovered or was pointed to the Standard and can't
>> remember if it contained the alpha-3 codes in addition to the
>> alpha-2 and numeric ones.  I do know that we never considered
>> anything other than the alpha-2 codes for ccTLD names, if only
>> because Jon wanted that system to be as deterministic as
>> possible with no possibility about arguments about what code
>> should be assigned that IANA needed to referee.    
>> 
>> 
>> 
> 
> 
> 
> ------------------------------
> 
> Message: 2
> Date: Fri, 30 Jun 2017 13:21:31 -0400
> From: Donald Eastlake <d3e3e3@gmail.com>
> To: Daniel Karrenberg <dfk@ripe.net>
> Cc: IETF Discussion <ietf@ietf.org>
> Subject: Re:
> Message-ID:
>    <CAF4+nEE5+nF_biteqsbEThU8tSeN7SwuCZLun3MHuJYVGvn0rQ@mail.gmail.com>
> Content-Type: text/plain; charset="UTF-8"
> 
>> On Fri, Jun 30, 2017 at 12:53 PM, Daniel Karrenberg <dfk@ripe.net> wrote:
>> john,
>> 
>> ...
>> 
>> Conversely it would be problematic now to have three letter ASCII ccTLDs
>> unless there is a clear agreement with ISO that they will never allocate
>> a three letter code that already exists as a gTLD. Afaik there are no
>> clashes right now, but past results are not a guarantee for the future.
> 
> COM is the three letter code for the Comoros Islands. I believe it is
> also used by a few entities as their TLD :-)
> 
>> It is never a good idea to have two 'authorities' over one part of a
>> name space.
>> 
>> dfk
> 
> Thanks,
> Donald
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> ietf mailing list
> ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
> 
> 
> ------------------------------
> 
> End of ietf Digest, Vol 109, Issue 92
> *************************************

--Apple-Mail-37EADE25-A591-4C22-A11E-44F726F1B2D6
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><p style=3D"margin: 0px; font-size: 12=
px; line-height: normal; font-family: Helvetica;"><span style=3D"font-size: 1=
2pt;">Unsubscribe</span></p></div><div><br>On Jun 30, 2017, at 3:00 PM, <a h=
ref=3D"mailto:ietf-request@ietf.org">ietf-request@ietf.org</a> wrote:<br><br=
></div><blockquote type=3D"cite"><div><span>Send ietf mailing list submissio=
ns to</span><br><span> &nbsp; &nbsp;<a href=3D"mailto:ietf@ietf.org">ietf@ie=
tf.org</a></span><br><span></span><br><span>To subscribe or unsubscribe via t=
he World Wide Web, visit</span><br><span> &nbsp; &nbsp;<a href=3D"https://ww=
w.ietf.org/mailman/listinfo/ietf">https://www.ietf.org/mailman/listinfo/ietf=
</a></span><br><span>or, via email, send a message with subject or body 'hel=
p' to</span><br><span> &nbsp; &nbsp;<a href=3D"mailto:ietf-request@ietf.org"=
>ietf-request@ietf.org</a></span><br><span></span><br><span>You can reach th=
e person managing the list at</span><br><span> &nbsp; &nbsp;<a href=3D"mailt=
o:ietf-owner@ietf.org">ietf-owner@ietf.org</a></span><br><span></span><br><s=
pan>When replying, please edit your Subject line so it is more specific</spa=
n><br><span>than "Re: Contents of ietf digest..."</span><br><span></span><br=
><span></span><br><span>Today's Topics:</span><br><span></span><br><span> &n=
bsp;&nbsp;1. Re: (Daniel Karrenberg)</span><br><span> &nbsp;&nbsp;2. Re: (Do=
nald Eastlake)</span><br><span></span><br><span></span><br><span>-----------=
-----------------------------------------------------------</span><br><span>=
</span><br><span>Message: 1</span><br><span>Date: Fri, 30 Jun 2017 18:53:27 +=
0200</span><br><span>From: Daniel Karrenberg &lt;<a href=3D"mailto:dfk@ripe.=
net">dfk@ripe.net</a>&gt;</span><br><span>To: <a href=3D"mailto:ietf@ietf.or=
g">ietf@ietf.org</a></span><br><span>Subject: Re:</span><br><span>Message-ID=
: &lt;<a href=3D"mailto:bd508ec0-a532-cd65-2b51-4dbd8f36de1c@ripe.net">bd508=
ec0-a532-cd65-2b51-4dbd8f36de1c@ripe.net</a>&gt;</span><br><span>Content-Typ=
e: text/plain; charset=3Dutf-8</span><br><span></span><br><span>john,</span>=
<br><span></span><br><span>your eloquently told story agrees with personal m=
emory and my particular</span><br><span>version of reality ;-).</span><br><s=
pan></span><br><span>I know for a fact that ISO3166 at the time contained at=
 least two letter</span><br><span>alphabetic, three letter alphabetic and nu=
meric codes for each country</span><br><span>or territory recognized by the U=
nited Nations.</span><br><span></span><br><span>I also distinctly remember a=
 number of conversations with Jon about DNS</span><br><span>"going internati=
onal". Jon wisely saw that IANA needed an external</span><br><span>authority=
 to decide what was a country. After considering several such</span><br><spa=
n>authorities, the United nations appeared the most widely agreed one.</span=
><br><blockquote type=3D"cite"><span>=46rom there it was but a short step to=
 ISO3166. The choice for two letter</span><br></blockquote><span>alphabetic c=
odes was also straightforward: there were no two letter TLDs</span><br><span=
>at the time and that guaranteed that there would be no clashes with</span><=
br><span>exiting TLDs. [1]</span><br><span></span><br><span>So I would argue=
 that ASCII ccTLDs are indeed meant to be exactly two</span><br><span>letter=
s. If only to avoid clashes with future changes to ISO3166 I would</span><br=
><span>consider it to be a Bad Idea to allocate two letter ASCII strings for=
</span><br><span>any other purpose. This is why I have spoken up against ".E=
U" until the</span><br><span>ISO3166 maintenance agency published it as a "r=
eserved" code.</span><br><span></span><br><span>Conversely it would be probl=
ematic now to have three letter ASCII ccTLDs</span><br><span>unless there is=
 a clear agreement with ISO that they will never allocate</span><br><span>a t=
hree letter code that already exists as a gTLD. Afaik there are no</span><br=
><span>clashes right now, but past results are not a guarantee for the futur=
e.</span><br><span>It is never a good idea to have two 'authorities' over on=
e part of a</span><br><span>name space.</span><br><span></span><br><span>dfk=
</span><br><span></span><br><span>[1] UK appeared at different times in at l=
east two realities that have</span><br><span>been recounted to me. ;-) But t=
here was no clash in ISO3166 at the time.</span><br><span></span><br><span><=
/span><br><span></span><br><span></span><br><span>On 1.01.70 1:00 , &nbsp;wr=
ote:</span><br><blockquote type=3D"cite"><span></span><br></blockquote><bloc=
kquote type=3D"cite"><span></span><br></blockquote><blockquote type=3D"cite"=
><span>--On Friday, June 30, 2017 07:31 +0200 Olivier MJ</span><br></blockqu=
ote><blockquote type=3D"cite"><span>Cr?pin-Leblond &lt;<a href=3D"mailto:ocl=
@gih.com">ocl@gih.com</a>&gt; wrote:</span><br></blockquote><blockquote type=
=3D"cite"><span></span><br></blockquote><blockquote type=3D"cite"><blockquot=
e type=3D"cite"><span>Hello all,</span><br></blockquote></blockquote><blockq=
uote type=3D"cite"><blockquote type=3D"cite"><span></span><br></blockquote><=
/blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>I am r=
eading RFC1591 and RFC3071 and have a couple of simple</span><br></blockquot=
e></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>que=
stions: 1. Is a ccTLD defined as restricted to 2-letter</span><br></blockquo=
te></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>co=
untry codes (ISO3166 alpha 2), or could that include</span><br></blockquote>=
</blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>3-let=
ter country codes in the ISO3166 list (ISO3166 alpha 3)?</span><br></blockqu=
ote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><span>2=
. RFC1591 appears to point at 2-letter, but many other parts</span><br></blo=
ckquote></blockquote><blockquote type=3D"cite"><blockquote type=3D"cite"><sp=
an>of this RFC are obsolete - so does this RFC remain valid?</span><br></blo=
ckquote></blockquote><blockquote type=3D"cite"><span></span><br></blockquote=
><blockquote type=3D"cite"><span>Olivier,</span><br></blockquote><blockquote=
 type=3D"cite"><span></span><br></blockquote><blockquote type=3D"cite"><span=
>First, it is important to understand that RFC 1591 was never an</span><br><=
/blockquote><blockquote type=3D"cite"><span>IETF document. &nbsp;It was an I=
ANA policy document, dating from a</span><br></blockquote><blockquote type=3D=
"cite"><span>time that IANA operated largely independent of the IETF (the</s=
pan><br></blockquote><blockquote type=3D"cite"><span>IETF could _request_ re=
gistration actions or registry creation,</span><br></blockquote><blockquote t=
ype=3D"cite"><span>but not _order_ them and so could others) and, while it</=
span><br></blockquote><blockquote type=3D"cite"><span>(deliberately, IIR) di=
dn't strongly call that out, reflecting</span><br></blockquote><blockquote t=
ype=3D"cite"><span>policies and norms that had been in effect, although evol=
ving</span><br></blockquote><blockquote type=3D"cite"><span>somewhat, long b=
efore the time it was published.</span><br></blockquote><blockquote type=3D"=
cite"><span></span><br></blockquote><blockquote type=3D"cite"><span>It may a=
lso be useful to recall that the practical authority of</span><br></blockquo=
te><blockquote type=3D"cite"><span>IANA in the DNS space at that time was de=
rived from two things.</span><br></blockquote><blockquote type=3D"cite"><spa=
n>The first is what is known (especially next week) on this side</span><br><=
/blockquote><blockquote type=3D"cite"><span>of the pond as the "consent of t=
he governed": just about</span><br></blockquote><blockquote type=3D"cite"><s=
pan>everyone understood that a central registration and allocation</span><br=
></blockquote><blockquote type=3D"cite"><span>authority was important and, w=
ith one important exception [1],</span><br></blockquote><blockquote type=3D"=
cite"><span>no one had something they believed was a better idea that they</=
span><br></blockquote><blockquote type=3D"cite"><span>were anxious to propos=
e. &nbsp;Yes, in theory the US Government could</span><br></blockquote><bloc=
kquote type=3D"cite"><span>have stepped in, but they didn't and their behavi=
or was such as</span><br></blockquote><blockquote type=3D"cite"><span>to lea=
d everyone to believe that they wouldn't. &nbsp;&nbsp;The second was</span><=
br></blockquote><blockquote type=3D"cite"><span>that there was a general bel=
ief that, if the rules, especially</span><br></blockquote><blockquote type=3D=
"cite"><span>those involving principles of responsible behavior that 1591</s=
pan><br></blockquote><blockquote type=3D"cite"><span>invokes with the "trust=
ee for the ... community" language, were</span><br></blockquote><blockquote t=
ype=3D"cite"><span>violated IANA had both the authority and the will to, e.g=
., make</span><br></blockquote><blockquote type=3D"cite"><span>changes in de=
legations to parties who would be more responsible.</span><br></blockquote><=
blockquote type=3D"cite"><span></span><br></blockquote><blockquote type=3D"c=
ite"><span>There were also a number of things -- both "rules" and</span><br>=
</blockquote><blockquote type=3D"cite"><span>explanations -- that didn't go i=
nto 1591, either because we</span><br></blockquote><blockquote type=3D"cite"=
><span>didn't think of them (or think they were necessary) or because</span>=
<br></blockquote><blockquote type=3D"cite"><span>Jon saw them simply as thin=
gs he wasn't going to allow. &nbsp;&nbsp;The</span><br></blockquote><blockqu=
ote type=3D"cite"><span>now-famous "will be alphabetic" phrasing in RFC 1123=
 about TLD</span><br></blockquote><blockquote type=3D"cite"><span>labels was=
 typical: Jon knew he simply was not going to allow</span><br></blockquote><=
blockquote type=3D"cite"><span>TLD names containing anything other than ASCI=
I letters.</span><br></blockquote><blockquote type=3D"cite"><span></span><br=
></blockquote><blockquote type=3D"cite"><span>Whether the principles underly=
ing 1591 are "obsolete" or not</span><br></blockquote><blockquote type=3D"ci=
te"><span>depends on some complicated questions involving one's view of</spa=
n><br></blockquote><blockquote type=3D"cite"><span>the Internet and the role=
 of the DNS (see</span><br></blockquote><blockquote type=3D"cite"><span>draf=
t-klensin-dns-function-considerations as well as several</span><br></blockqu=
ote><blockquote type=3D"cite"><span>RFCs that followed 1591. &nbsp;Certainly=
, when 1591 was written, we</span><br></blockquote><blockquote type=3D"cite"=
><span>didn't anticipate either ICANN or the rise of the domain name</span><=
br></blockquote><blockquote type=3D"cite"><span>business (and, arguably, its=
 dominance in decision-making).</span><br></blockquote><blockquote type=3D"c=
ite"><span></span><br></blockquote><blockquote type=3D"cite"><span>Now, with=
 that background, let me try to answer your question.</span><br></blockquote=
><blockquote type=3D"cite"><span>First, the ccTLD naming model was strictly l=
imited to allocated</span><br></blockquote><blockquote type=3D"cite"><span>c=
odes in what is now called ISO 3166-1 alpha-2 [1].</span><br></blockquote><b=
lockquote type=3D"cite"><span>Specifically, no use of the reserved list (not=
 sure that existed</span><br></blockquote><blockquote type=3D"cite"><span>at=
 the time either), no private-use codes, no codes allocated by</span><br></b=
lockquote><blockquote type=3D"cite"><span>IANA rather than a body fully resp=
onsible to ISO TC 46, and,</span><br></blockquote><blockquote type=3D"cite">=
<span>while there are a couple of famous mistakes (history and</span><br></b=
lockquote><blockquote type=3D"cite"><span>explanation on request if relevant=
) no allocations on</span><br></blockquote><blockquote type=3D"cite"><span>s=
peculation.</span><br></blockquote><blockquote type=3D"cite"><span></span><b=
r></blockquote><blockquote type=3D"cite"><span>One of those rules was, AFAKK=
, never formally published although</span><br></blockquote><blockquote type=3D=
"cite"><span>at least part of it was widely understood. &nbsp;That was that T=
LD</span><br></blockquote><blockquote type=3D"cite"><span>labels came in cat=
egories that could be determined by length,</span><br></blockquote><blockquo=
te type=3D"cite"><span>such that filters and algorithms could be based on th=
ose</span><br></blockquote><blockquote type=3D"cite"><span>categories. &nbsp=
;The rule was 2-3.4+, i.e.,</span><br></blockquote><blockquote type=3D"cite"=
><span></span><br></blockquote><blockquote type=3D"cite"><span> * All two-le=
tter labels were country codes derived from</span><br></blockquote><blockquo=
te type=3D"cite"><span> &nbsp; &nbsp;3166 alpha-2.</span><br></blockquote><b=
lockquote type=3D"cite"><span> * All three letter labels were generic TLDs (=
not all of</span><br></blockquote><blockquote type=3D"cite"><span> &nbsp; &n=
bsp;which were managed under IANA supervision).</span><br></blockquote><bloc=
kquote type=3D"cite"><span> * All labels of four characters or more were eit=
her the</span><br></blockquote><blockquote type=3D"cite"><span> &nbsp; &nbsp=
;specific string "ARPA" (which was originally intended to</span><br></blockq=
uote><blockquote type=3D"cite"><span> &nbsp; &nbsp;be temporary and transiti=
onal) or what is now known as a</span><br></blockquote><blockquote type=3D"c=
ite"><span> &nbsp; &nbsp;"special use name", i.e., one that is not part of t=
he</span><br></blockquote><blockquote type=3D"cite"><span> &nbsp; &nbsp;glob=
al DNS or that was expected to be processed using</span><br></blockquote><bl=
ockquote type=3D"cite"><span> &nbsp; &nbsp;some non-DNS mechanism.</span><br=
></blockquote><blockquote type=3D"cite"><span></span><br></blockquote><block=
quote type=3D"cite"><span>ICANN staff were warned about that rule in the 199=
9 period but</span><br></blockquote><blockquote type=3D"cite"><span>decided t=
o allow TLD applications for gTLDs with labels longer</span><br></blockquote=
><blockquote type=3D"cite"><span>than three characters and to not identify t=
he issue to</span><br></blockquote><blockquote type=3D"cite"><span>applicant=
s. &nbsp;&nbsp;Many of the issues that are now seen as "universal</span><br>=
</blockquote><blockquote type=3D"cite"><span>acceptance" problems are the re=
sult of that decision. &nbsp;Whether</span><br></blockquote><blockquote type=
=3D"cite"><span>one assumed at the time, or concludes now, that it was a</sp=
an><br></blockquote><blockquote type=3D"cite"><span>rational, consensus, dec=
ision to favor applicant choice and</span><br></blockquote><blockquote type=3D=
"cite"><span>consequent competition in the TLD marketplace over that</span><=
br></blockquote><blockquote type=3D"cite"><span>historical rule or, even the=
 controversies about special names,</span><br></blockquote><blockquote type=3D=
"cite"><span>a screwup and/or show of arrogance is very much in the mind of<=
/span><br></blockquote><blockquote type=3D"cite"><span>the beholder.</span><=
br></blockquote><blockquote type=3D"cite"><span></span><br></blockquote><blo=
ckquote type=3D"cite"><span>Similarly, ICANN clearly broke the 1591 rules in=
 allocating "EU"</span><br></blockquote><blockquote type=3D"cite"><span>as a=
 TLD label. &nbsp;It is not an ISO 3166-1 alpha-2 registered</span><br></blo=
ckquote><blockquote type=3D"cite"><span>country code and it violates some te=
rritorial overlap rules that</span><br></blockquote><blockquote type=3D"cite=
"><span>are intrinsic to bother 3166-1 and the assumptions underlying</span>=
<br></blockquote><blockquote type=3D"cite"><span>1591. &nbsp;At a different e=
nd of the problem, IANA's rules (pointed</span><br></blockquote><blockquote t=
ype=3D"cite"><span>to but maybe not explicit enough) is that, if a country</=
span><br></blockquote><blockquote type=3D"cite"><span>convinced 3166/MA to c=
hange its code, there needed to be a plan</span><br></blockquote><blockquote=
 type=3D"cite"><span>in place to remove the older TLD within a reasonably sh=
ort</span><br></blockquote><blockquote type=3D"cite"><span>period before the=
 new code would be delegated (on a "one</span><br></blockquote><blockquote t=
ype=3D"cite"><span>territory, one code" principle)). &nbsp;IIR, there was su=
ch an</span><br></blockquote><blockquote type=3D"cite"><span>agreement about=
 "SU" before "RU" was delegated, but ICANN has</span><br></blockquote><block=
quote type=3D"cite"><span>never succeeded in getting rid of "SU", violating t=
hat principle.</span><br></blockquote><blockquote type=3D"cite"><span></span=
><br></blockquote><blockquote type=3D"cite"><span>All of this is further com=
plicated by IDN TLDs, where new ones</span><br></blockquote><blockquote type=
=3D"cite"><span>associated with countries are not limited to two characters<=
/span><br></blockquote><blockquote type=3D"cite"><span>(even in their origin=
al scripts); non-country political entities</span><br></blockquote><blockquo=
te type=3D"cite"><span>are allowed (if one counts GOV. MIL, and maybe INT, t=
hey have</span><br></blockquote><blockquote type=3D"cite"><span>always been a=
llowed, but those are probably a bit different(;</span><br></blockquote><blo=
ckquote type=3D"cite"><span>and the relationships between 3166 alpha-2 ccTLD=
s and their IDN</span><br></blockquote><blockquote type=3D"cite"><span>relat=
ives have never really been spelled out (despite the length</span><br></bloc=
kquote><blockquote type=3D"cite"><span>of the ccTLD Fast Track Procedure.</s=
pan><br></blockquote><blockquote type=3D"cite"><span></span><br></blockquote=
><blockquote type=3D"cite"><span>Whether that makes 3166 partially or comple=
tely obsolete is a</span><br></blockquote><blockquote type=3D"cite"><span>ma=
tter of personal judgment. &nbsp;&nbsp;Because it was an IANA document,</spa=
n><br></blockquote><blockquote type=3D"cite"><span>the IETF Protocol Police w=
ould never have arrested anyone for</span><br></blockquote><blockquote type=3D=
"cite"><span>violating it. &nbsp;Unlike the IETF and its relationship to the=
</span><br></blockquote><blockquote type=3D"cite"><span>Protocol Police, IAN=
A did have the ability to enforce its</span><br></blockquote><blockquote typ=
e=3D"cite"><span>provisions (and did). &nbsp;ICANN has clearly demonstrated a=
</span><br></blockquote><blockquote type=3D"cite"><span>willingness to viola=
te some of its provisions (explicit or</span><br></blockquote><blockquote ty=
pe=3D"cite"><span>implied) and it appears that, both prior and subsequent to=
 the</span><br></blockquote><blockquote type=3D"cite"><span>recent "IANA tra=
nsition", there is no one to tell them that they</span><br></blockquote><blo=
ckquote type=3D"cite"><span>cannot do so. &nbsp;My personal opinion that the=
 Internet would be</span><br></blockquote><blockquote type=3D"cite"><span>mu=
ch better off if the principles of 1591, especially the</span><br></blockquo=
te><blockquote type=3D"cite"><span>requirement that registries be required t=
o act in the best</span><br></blockquote><blockquote type=3D"cite"><span>int=
erests of the global Internet community, were followed and</span><br></block=
quote><blockquote type=3D"cite"><span>enforced (see draft-klensin-idna-rfc58=
91bis for the specific</span><br></blockquote><blockquote type=3D"cite"><spa=
n>IDNA case) are probably worth a cup of fancy coffee after a few</span><br>=
</blockquote><blockquote type=3D"cite"><span>Euros (or equivalent) are throw=
n in.</span><br></blockquote><blockquote type=3D"cite"><span></span><br></bl=
ockquote><blockquote type=3D"cite"><span>best,</span><br></blockquote><block=
quote type=3D"cite"><span> &nbsp;&nbsp;&nbsp;john</span><br></blockquote><bl=
ockquote type=3D"cite"><span></span><br></blockquote><blockquote type=3D"cit=
e"><span></span><br></blockquote><blockquote type=3D"cite"><span>[1] The dis=
senters were largely arguing for abandoning the DNS</span><br></blockquote><=
blockquote type=3D"cite"><span>in favor of X.500. &nbsp;At least in public, t=
hat position was</span><br></blockquote><blockquote type=3D"cite"><span>just=
ified on the basis of developing and future technology, with</span><br></blo=
ckquote><blockquote type=3D"cite"><span>the side effect of putting the top-l=
evel entities under the</span><br></blockquote><blockquote type=3D"cite"><sp=
an>control of the ISO and ITU registration processes.</span><br></blockquote=
><blockquote type=3D"cite"><span>Interestingly, with regard to your question=
, X.500 uses ISO</span><br></blockquote><blockquote type=3D"cite"><span>3166=
-1 alpha-2 country codes as well.</span><br></blockquote><blockquote type=3D=
"cite"><span></span><br></blockquote><blockquote type=3D"cite"><span>[2] &nb=
sp;I don't think there was more than one part of ISO 3166 at</span><br></blo=
ckquote><blockquote type=3D"cite"><span>the time Jon discovered or was point=
ed to the Standard and can't</span><br></blockquote><blockquote type=3D"cite=
"><span>remember if it contained the alpha-3 codes in addition to the</span>=
<br></blockquote><blockquote type=3D"cite"><span>alpha-2 and numeric ones. &=
nbsp;I do know that we never considered</span><br></blockquote><blockquote t=
ype=3D"cite"><span>anything other than the alpha-2 codes for ccTLD names, if=
 only</span><br></blockquote><blockquote type=3D"cite"><span>because Jon wan=
ted that system to be as deterministic as</span><br></blockquote><blockquote=
 type=3D"cite"><span>possible with no possibility about arguments about what=
 code</span><br></blockquote><blockquote type=3D"cite"><span>should be assig=
ned that IANA needed to referee. &nbsp;&nbsp;&nbsp;</span><br></blockquote><=
blockquote type=3D"cite"><span></span><br></blockquote><blockquote type=3D"c=
ite"><span></span><br></blockquote><blockquote type=3D"cite"><span></span><b=
r></blockquote><span></span><br><span></span><br><span></span><br><span>----=
--------------------------</span><br><span></span><br><span>Message: 2</span=
><br><span>Date: Fri, 30 Jun 2017 13:21:31 -0400</span><br><span>From: Donal=
d Eastlake &lt;<a href=3D"mailto:d3e3e3@gmail.com">d3e3e3@gmail.com</a>&gt;<=
/span><br><span>To: Daniel Karrenberg &lt;<a href=3D"mailto:dfk@ripe.net">df=
k@ripe.net</a>&gt;</span><br><span>Cc: IETF Discussion &lt;<a href=3D"mailto=
:ietf@ietf.org">ietf@ietf.org</a>&gt;</span><br><span>Subject: Re:</span><br=
><span>Message-ID:</span><br><span> &nbsp; &nbsp;&lt;<a href=3D"mailto:CAF4+=
nEE5+nF_biteqsbEThU8tSeN7SwuCZLun3MHuJYVGvn0rQ@mail.gmail.com">CAF4+nEE5+nF_=
biteqsbEThU8tSeN7SwuCZLun3MHuJYVGvn0rQ@mail.gmail.com</a>&gt;</span><br><spa=
n>Content-Type: text/plain; charset=3D"UTF-8"</span><br><span></span><br><sp=
an>On Fri, Jun 30, 2017 at 12:53 PM, Daniel Karrenberg &lt;<a href=3D"mailto=
:dfk@ripe.net">dfk@ripe.net</a>&gt; wrote:</span><br><blockquote type=3D"cit=
e"><span>john,</span><br></blockquote><blockquote type=3D"cite"><span></span=
><br></blockquote><blockquote type=3D"cite"><span>...</span><br></blockquote=
><blockquote type=3D"cite"><span></span><br></blockquote><blockquote type=3D=
"cite"><span>Conversely it would be problematic now to have three letter ASC=
II ccTLDs</span><br></blockquote><blockquote type=3D"cite"><span>unless ther=
e is a clear agreement with ISO that they will never allocate</span><br></bl=
ockquote><blockquote type=3D"cite"><span>a three letter code that already ex=
ists as a gTLD. Afaik there are no</span><br></blockquote><blockquote type=3D=
"cite"><span>clashes right now, but past results are not a guarantee for the=
 future.</span><br></blockquote><span></span><br><span>COM is the three lett=
er code for the Comoros Islands. I believe it is</span><br><span>also used b=
y a few entities as their TLD :-)</span><br><span></span><br><blockquote typ=
e=3D"cite"><span>It is never a good idea to have two 'authorities' over one p=
art of a</span><br></blockquote><blockquote type=3D"cite"><span>name space.<=
/span><br></blockquote><blockquote type=3D"cite"><span></span><br></blockquo=
te><blockquote type=3D"cite"><span>dfk</span><br></blockquote><span></span><=
br><span>Thanks,</span><br><span>Donald</span><br><span></span><br><span></s=
pan><br><span></span><br><span>------------------------------</span><br><spa=
n></span><br><span>Subject: Digest Footer</span><br><span></span><br><span>_=
______________________________________________</span><br><span>ietf mailing l=
ist</span><br><span><a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a></span=
><br><span><a href=3D"https://www.ietf.org/mailman/listinfo/ietf">https://ww=
w.ietf.org/mailman/listinfo/ietf</a></span><br><span></span><br><span></span=
><br><span>------------------------------</span><br><span></span><br><span>E=
nd of ietf Digest, Vol 109, Issue 92</span><br><span>***********************=
**************</span><br></div></blockquote></body></html>=

--Apple-Mail-37EADE25-A591-4C22-A11E-44F726F1B2D6--


From nobody Fri Jun 30 18:43:42 2017
Return-Path: <d3e3e3@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 0ADE012EC5C; Fri, 30 Jun 2017 18:43:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, 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 eTvYNoVfK8wD; Fri, 30 Jun 2017 18:43:31 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001: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 EE95512EABA; Fri, 30 Jun 2017 18:43:30 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id r36so32633421ioi.1; Fri, 30 Jun 2017 18:43:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=QgV41TXIZD7Vk5O6hFiAunE+DHtrdZuP08ULzeYh1Nk=; b=mY/uoT/MQLktf5kK42lyLAPk6UexxqDAuE6kufCOUSfUFrOR2DkqXLVcHgpK5phQDZ ygRDioA3PnCQ5X8TsCQaJqilQ/XJgMOPt4GC0Yaz0m/rp9c5sVeI/N0HNLNYyTBEWbWQ iPhieu5dBFmV1m/NaUcvflcbvtmRW1dJt/bllGT9qy3I0scxamL+L2q89CXXuXntVa/c 2nvm7pm3IpxbCsLJ4VGq569bP3VerCTsssAcIAn7DNYbdHLOyYhf4hrvtqV5EN/yTcGv PGaElgH+sHIzPfkzRQaeTJEWDAZrIzoulU2sKtotkj57iJNuD8pMO6KTi4FfFlsJQlv7 XaYg==
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=QgV41TXIZD7Vk5O6hFiAunE+DHtrdZuP08ULzeYh1Nk=; b=FloA/PSF+3c5n3Ke5DTqpuHKpNVs7SZZ85pREe+9cW+lGr0P3OfvAOwJvJtQflQHlr UsIZZjorojjls9NYm7PlAXET4vhltPu9T7PoDZ5h+5XO4+cqb/4yLtumVPycGTXAnpq1 EqUbWt5JHrdxfqB8+nQ5ITs92gtiY09ZmaNSvWsZUH/QbNXrGcj3JU8MeBG9gyUloAm4 RzQylW0ZWhe6uQ5AOIynOgm4+8UP9zOfktayOPrqBHN437V2YH9N33wLU7x1jqXhwJW0 glKaqbiaFr1PptggNoCcrppnE/DI/5efy0UKDI7A4p2e/kcMcZLWLFhqCtQeWfgnt3M9 bXjQ==
X-Gm-Message-State: AKS2vOy4DKCSO0528qbab4hmP2UqDYpAVx5fVh+2jZz0eZAayWkt8Veg 4XOKErF5v5FpcWwO05uCTHXGZkxtXKo5
X-Received: by 10.107.156.83 with SMTP id f80mr25274248ioe.9.1498873410069; Fri, 30 Jun 2017 18:43:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.17.221 with HTTP; Fri, 30 Jun 2017 18:43:13 -0700 (PDT)
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949362FB4DF88@MX307CL04.corp.emc.com>
References: <CE03DB3D7B45C245BCA0D243277949362FB4DF88@MX307CL04.corp.emc.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 30 Jun 2017 21:43:13 -0400
Message-ID: <CAF4+nEFUmB=eMO6rvK6-YiL+3Adp_t1QVqgMDBHZFn73_JxEfw@mail.gmail.com>
Subject: Re: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-10 - ECN & DSCP considerations
To: "Black, David" <David.Black@dell.com>
Cc: Magnus Westerlund <magnus.westerlund@ericsson.com>, "tsv-art@ietf.org" <tsv-art@ietf.org>,  "draft-ietf-trill-over-ip.all@ietf.org" <draft-ietf-trill-over-ip.all@ietf.org>, IETF Discussion <ietf@ietf.org>,  "trill@ietf.org" <trill@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/uaeye_sklqYI68qRZqorWG-wIPg>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Jul 2017 01:43:35 -0000

Hi David,

On Mon, Jun 26, 2017 at 3:04 PM, Black, David <David.Black@dell.com> wrote:
> Adding some comments on ECN and DSCP ...
>
>> > Section 4.3:
>> >
>> >    TRILL over IP implementations MUST support setting the DSCP value in
>> >    the outer IP Header of TRILL packets they send by mapping the TRILL
>> >    priority and DEI to the DSCP. They MAY support, for a TRILL Data
>> >    packet where the native frame payload is an IP packet, mapping the
>> >    DSCP in this inner IP packet to the outer IP Header with the default
>> >    for that mapping being to copy the DSCP without change.
>> >
>> > I think it is fine to require that implementations are capable of setting
>> > DSCP values on the outer IP header. However, I fail to see any discussion of
>> > the potential issues with actually setting the DSCP values. It is one thing to
>> > do this in an IP back bone use case where one can know and have control
>> > over the PHB that the DSCP values maps to. But otherwise, over general
>> > internet the
>> > behavior is not that predictable. One can easily be subject to policers or
>> > remapping. Also as the actual DSCP code point usage is domain specific this is
>> > difficult. Priority reversal is likely the least of the problems that this can
>> > run into over general Internet.
>>
>> It sounds like appropriate discussion and warnings about these issues
>> would resolve the above comment.
>
> For ECN, see RFC 6040 and draft-ietf-tsvwg-rfc6040update-shim.  In particular,
> copying the inner ECN codepoint to the outer IP header encapsulation without
> requiring decapsulation processing as specified in RFC 6040 or the 6040update-shim
> draft can lose congestion indications from the network and hence is wrong
> (it's also wrong wrt RFC 3168, but RFC 6040 and the 6040update-shim drafts are
> better and more current references).

That's a good point.

> For DSCPs, start with RFC 2983 - thinking about the validity (or likely validity)
> of the outer DSCP at the decapsulator may help in choosing whether to
> recommend a uniform model (e.g., copy DSCP out at ingress, copy back in at
> egress) or a pipe model (e.g., do something reasonable for outer DSCP at
> ingress, ignore it on egress) as the implementation default.

I believe the default behavior in the current draft is the best
default. That sets DSCP based on the same TRILL Header indicia that
controls default QoS on non-IP links.

> -- DSCP mapping to/from TRILL/Ethernet priorities
>
>> The intent in the draft is to reflect the default relative priority of
>> the different priority code points in IEEE Std 802.1Q where priority 1
>> is lower than priority 0. At a quick look, it appears to me that RFC
>> 2474 requires that 0x001000 be handled as being of a priority not
>> lower than the priority with which 0x000000 is handled. Yet RFC 3662,
>> which you point to, seems to suggest using 0x001000 as a lower
>> priority code point than 0x000000. Given that 3662 not only does not
>> update 2474 but is only Informational while 2474 is Standards Track, I
>> would say that 2474 dominates and that this draft makes the best
>> assumptions it can about default behavior...
>
> Well ... that's a discussion about text in RFCs that are well over a decade
> old, and in an area (less-than-best-effort service) where the aspirations
> of at least RFC 3662 weren't realized ... but that RFC is not safe to ignore,
> either.
>
> In practice, the specification of CS1 for less-than-best-effort service has
> been promulgated by RFC 4594 rather than RFC 3662, and RFC 4594 has
> had significant "running code" impact on network design and operation.
>
> As Magnus mentioned RFC7657, I strongly suggest starting from the
> RFC 7657 discussion of this topic in order to figure out what to do.  I'm
> not sure what to recommend, but I do think that starting from
> RFC 7657 (rather than RFC 2474 and RFC 3662) is the better approach.

OK.

> FWIW, the TSVWG WG is in the process of figuring out which DSCP
> to recommend for less-than-best-effort-service in place of CS1 - that's
> likely to be an active topic of discussion in Prague.

I'll try to attend that session.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> Thanks, --David
>
>> -----Original Message-----
>> From: Tsv-art [mailto:tsv-art-bounces@ietf.org] On Behalf Of Donald
>> Eastlake
>> Sent: Sunday, June 25, 2017 8:07 PM
>> To: Magnus Westerlund <magnus.westerlund@ericsson.com>
>> Cc: tsv-art@ietf.org; draft-ietf-trill-over-ip.all@ietf.org; IETF Discussion
>> <ietf@ietf.org>; trill@ietf.org
>> Subject: Re: [Tsv-art] Tsvart early review of draft-ietf-trill-over-ip-10
>>
>> Hi Magnus,
>>
>> Thanks for the extensive review. See my responses below.
>>
>> On Thu, Jun 15, 2017 at 1:32 PM, Magnus Westerlund
>> <magnus.westerlund@ericsson.com> wrote:
>> >
>> > Reviewer: Magnus Westerlund
>> > Review result: Not Ready
>> >
>> > Early review of draft-ietf-trill-over-ip-10
>> > Reviewer: Magnus Westerlund
>> > Review result: Not Ready
>> >
>> > TSV-ART review comments:
>> >
>> > I have set this to not ready as there are several issues, some significant that
>> > could affect the protocol realization significantly. Some may be me missing
>> > things in TRILL, I was not that familiar with it before this review and I have
>> > only tried looking up things, not reading the whole earlier specifications. So
>> > don't hesitate to push back and provide pointers to things that can resolve
>> > issues. The authors and the WG clearly have thought about a lot of issues
>> and
>> > dealt with much already.
>>
>> OK. Hopefully we can resolve these one way or the other.
>>
>> > Diffserv usage
>> > --------------
>> >
>> > Section 4.3:
>> >
>> >    TRILL over IP implementations MUST support setting the DSCP value in
>> >    the outer IP Header of TRILL packets they send by mapping the TRILL
>> >    priority and DEI to the DSCP. They MAY support, for a TRILL Data
>> >    packet where the native frame payload is an IP packet, mapping the
>> >    DSCP in this inner IP packet to the outer IP Header with the default
>> >    for that mapping being to copy the DSCP without change.
>> >
>> > I think it is fine to require that implementations are capable  of setting
>> > DSCP values on the outer IP header. However, I fail to see any discussion of
>> > the potential issues with actually setting the DSCP values. It is one thing to
>> > do this in an IP back bone use case where one can know and have control
>> over
>> > the PHB that the DSCP values maps to. But otherwise, over general
>> internet the
>> > behavior is not that predictable. One can easily be subject to policers or
>> > remapping. Also as the actual DSCP code point usage is domain specific this
>> is
>> > difficult. Priority reversal is likely the least of the problems that this can
>> > run into over general Internet.
>>
>> It sounds like appropriate discussion and warnings about these issues
>> would resolve the above comment.
>>
>> > Section 4.3:
>> >
>> >    The default TRILL priority and DEI to DSCP mapping, which may be
>> >    configured per TRILL over IP port, is an follows. Note that the DEI
>> >    value does not affect the default mapping and, to provide a
>> >    potentially lower priority service than the default priority 0,
>> >    priority 1 is considered lower priority than 0. So the priority
>> >    sequence from lower to higher priority is 1, 0, 2, 3, 4, 5, 6, 7.
>> >
>> >       TRILL Priority  DEI  DSCP Field (Binary/decimal)
>> >       --------------  ---  -----------------------------
>> >                   0   0/1  001000 / 8
>> >                   1   0/1  000000 / 0
>> >                   2   0/1  010000 / 16
>> >                   3   0/1  011000 / 24
>> >                   4   0/1  100000 / 32
>> >                   5   0/1  101000 / 40
>> >                   6   0/1  110000 / 48
>> >                   7   0/1  111000 / 56
>> >
>> > This appear to be an problematic mapping. At least for prio 0 and 1. As
>> > priority 1 appears to be intended to be higher than priority 0, it is
>> > interesting that it is mapped to CS1, which to quote
>> > https://datatracker.ietf.org/doc/rfc7657/:
>> >
>> > CS1 ('001000') was subsequently designated as the recommended
>> >       codepoint for the Lower Effort (LE) PHB [RFC3662].
>> >
>> > So what is proposed can in a network using default mapping, result in that
>> you
>> > get priority 0 to be lower priority than 1. Plus that in some networks this can
>> > also results in strange remapping that results in a different PHB for CS1
>> than.
>>
>> The intent in the draft is to reflect the default relative priority of
>> the different priority code points in IEEE Std 802.1Q where priority 1
>> is lower than priority 0. At a quick look, it appears to me that RFC
>> 2474 requires that 0x001000 be handled as being of a priority not
>> lower than the priority with which 0x000000 is handled. Yet RFC 3662,
>> which you point to, seems to suggest using 0x001000 as a lower
>> priority code point than 0x000000. Given that 3662 not only does not
>> update 2474 but is only Informational while 2474 is Standards Track, I
>> would say that 2474 dominates and that this draft makes the best
>> assumptions it can about default behavior...
>>
>> > MTU and Fragmentation
>> > ---------------------
>> >
>> > I think there are two main issue here. The first one is MTUD discovery
>> > of the actual IP path MTU between the ports. That will be needed to
>> prevent
>> > a lot of traffic going into MTU black holes. Especially as TRILL requries
>> > 1470 byte support which is likey above a lot of paths.
>>
>> Seems like it would depend on the environments where TRILL was used.
>> For example, I do not think 1470 would be a problem in most Data
>> Center or Internet Exchange point uses, for example. Data Centers
>> sometimes support 9K jumbo frames and the like.
>>
>> In fact, it is probably bad to focus too much on 1470 -- that is a
>> required minimum to be sure that reasonable size link state PDUs can
>> be successfully flooded through the TRILL campus so that routing will
>> work. However, it would commonly be the case that, for the TRILL
>> campus to be useful in a particular case, links need to be able to
>> carry the expected size TRILL Data packets. For example, if there were
>> two parts of a TRILL campus connected by one or a few TRILL over IP
>> links and the end stations in each part were assuming they could use
>> 1500 byte Ethernet packets, then the TRILL over IP links would need to
>> support an MTU based on 1500 + TRILL Header + IP and TRILL over IP
>> encapsulation. And more if security was being used or there were any
>> other reasons for additional headers/encapsulation...
>>
>> > Section 8.4:
>> >
>> >    Path MTU discovery [RFC4821] should be useful
>> >    in determining the IP MTU between a pair of RBridge ports with IP
>> >    connectivity.
>> >
>> > The issue with RFC4821 is that it has requirements on the packetization
>> layer.
>> > Trill appears to have several components that are useful. However, it will
>> > require a specification of the procedure to result in a useful tool.
>>
>> See below.
>>
>> > Section 8.4:
>> >
>> >    TRILL IS-IS MTU PDUs, as specified in Section 5 of [RFC6325] and in
>> >    [RFC7177], can be used to obtain added assurance of the MTU of a
>> >    link.
>> >
>> > Yes, that can confirm working MTUs that are at 1470 or above, but appears
>> > prevented from working below 1470?
>>
>> While there is a minimum size for TRILL IS-IS MTU PDUs, determined by
>> header size, it is well below 1470, probably (depending on whether
>> secuirty is in use, etc.) below 150 bytes.
>>
>> > Thus, it appears that there is a lack of mechanism here to actually get a valid
>> > and functional MTU from TRILL in the cases where the Path MTU is below
>> 1470. If
>> > I am wrong good, but I think this is an important piece for how to handle
>> the
>> > next main issue.
>>
>> How about referencing Section 3 of
>> https://tools.ietf.org/html/draft-ietf-trill-mtu-negotiation-05
>> which is currently in IETF Last Call? (The wording of that section is
>> probably going to be improved based on an OPS review by Brian
>> Carpenter.)
>>
>> > UDP encapsulation and IP fragments.
>>   ----------------------------------
>> > I see it as a big issue that UDP encapsulation is the native one, and that
>> > relies on IP fragmentation despite the need for reliable fragmentation.
>> With
>> > the setup of having to support 1470 MTU on TRILL level some packets will
>> be
>> > fragmented in many environments. That will lead to a lot of losses, and as
>> > discussed below a very big problem with middleboxes. The main problem
>> here is
>> > that if one tries to rely on IP fragments one will have issues with packets
>> > ending up in black holes. And different problems depending on IPv4 or
>> IPv6.
>> > IPv6 is lilkely the lesser problem assuming that one have working PMTUD.
>> >
>> > There are several ways out of this.
>> >
>> > 1. Detect issues and use TCP encapsulation with correctly set MSS to not
>> get IP
>> > fragements 2. Determine MTU and implement an fragmentation
>> mechanism on top of
>> > UDP.
>>
>> So, I don't see that much problem with UDP being the general default
>> consistent with the TRILL philosophy of defaulting to need zero or
>> minimal configuration. The default should be to use multicast Hellos
>> for discovery of neighbors which sure points at UDP to me. Having to
>> traverse a NAT should be a rare case. Since, in the NAT case, you have
>> to configure things related to the static binding and the IP
>> address(es) of peer(s) anyway you can also configure to use a
>> different encapsulation than UDP, such as TCP, at the same time. I
>> don't see it as much of a problem if, by default, TRILL won't operate
>> through a NAT. If you are using UDP and it fragments and fragments are
>> dropped at a NAT, probably you can't exchange Hellos so you will not
>> form an adjacency and anything on the other side of the NAT will not
>> be visible.
>>
>> > Zero Checksum:
>> > --------------
>> >
>> > Section 5.4:
>> >
>> > UDP Checksum - as specified in [RFC0768]
>> >
>> > Considering the fast path encapsulation desire, I am surprised to not see
>> any
>> > mentioning of use of zero checksum here. Raising the zero checksum and
>> forward
>> > reference would be good I think.
>> >
>> > And then Section 8.5:
>> >
>> >    The requirements for the usage of the zero UDP Checksum in a UDP
>> >    tunnel protocol are detailed in [RFC6936]. These requirements apply
>> >    to the UDP based TRILL over IP encapsulations specified herein
>> >    (native and VXLAN), which are applications of UDP tunnel.
>> >
>> > If you actually intended to allow zero checksum, then you actually should
>> > document that Trill fulfills the requirements that the applicability statement
>> > raises. I have not analyzed how well it meets these requirements.
>> >
>> > Please review Section 6.2 of RFC 8086 for example how that can be done.
>>
>> OK. We'll look into it.
>>
>> > TCP Encapsulation issue
>> > -----------------------
>> >
>> > Section 5.6:
>> >
>> > The TCP encapsulation appear to be missing an delimiter format allowing
>> each
>> > individual TRILL packet/payload to be read out of the TCP's byte stream. In
>> > other words, a normal implementation has no way of ensuring that the TCP
>> > payload starts with the start of a new TRILL payload. Multiple small TRILL
>> > payloads may be included in the same TCP payload, and also only parts as
>> TCP is
>> > one way of dealing with TRILL packets that are larger than the
>> IP+Encapsulation
>> > MTU that actually will work.
>> >
>> > This comment is based on that there appear to be no length fields included
>> in
>> > the TRILL header. The most straight forward delimiter is a 2-byte length
>> field
>> > for the TRILL payload to be encapsulated.
>>
>> Right. It might also be useful to include some sort of check field, as
>> is done in BGP, to detect if you are out of sync in parsing the TCP
>> stream.
>>
>> Another point is that, while with UDP it seems fine to send packets
>> with assorted QoS, you don't want to encourage re-ordering of TCP
>> packets in a stream. So if TCP encapsulation is being used, you want
>> to use the same DSCP value for the packets in a particular TCP stream.
>> So, generally, you need to have a TCP connection per priority handling
>> category. Mapping the 8 priority levels into a smaller number of
>> handling categories is a normal thing to do so you certainly don't
>> necessarily need 8 TCP connections. Adding material on this should not
>> be too hard.
>>
>> > Section 5.6:
>> >
>> > TCP endpoint requirements. I do wonder if an application like TRILL actual
>> > would need to discuss performance impacting implementation choices or
>> > limitations. For example use of NAGLE, the requirements on buffer sizes in
>> > relation to Bandwidth delay products, as buffer memory in a RBridge will
>> impact
>> > performance.
>>
>> Well, I'm not sure how deeply this document should get into such
>> performance issues. What about just saying something about
>> consideration being given to tuning TCP for performance and pointing
>> to one or a few other RFCs that talk about this?
>>
>> > Congestion Control
>> > ------------------
>> > First thanks for the effort here.
>>
>> You're welcome.
>>
>> > 8.1.2 In Other Environments
>> >
>> >    Where UDP based encapsulation headers are used in TRILL over IP in
>> >    environments other than those discussed in Section 8.1.1, specific
>> >    congestion control mechanisms are commonly needed.  However, if the
>> >    traffic being carried by the TRILL over IP link is already congestion
>> >    controlled and the size and volatility of the TRILL IS-IS link state
>> >    database is limited, then specific congestion control may not be
>> >    needed. See [RFC8085] Section 3.1.11 for further guidance.
>> >
>> > This is correct, however my question is if the RBridges have any way of
>> knowing
>> > which traffic is actually congestion controlled, considering that TRILL
>> provides
>> > an layer 2 abstraction. I wonder if there should be any type of white list of
>> > the types of layer 2 payloads that can be assumed to be congestion
>> controlled,
>> > and thus okay to forward over IP paths? I am worried that without any
>> > recommendation to prevent traffic that is not controlled to be forwarded,
>> can
>> > lead to congestion issues.
>> >
>> > The other issue I think may exist is the issue serial unicast emulation of
>> > broadcast/multicast creates. As this amplifies the outgoing packet rate with
>> > a factor of how many addresses are configured for serial unicast this can
>> > be significant traffic expansion. Thus, I think additional considerations are
>> > needed here, and maybe rate limiting of the amount of traffic to be
>> multicasted.
>>
>> OK. We can think about those issues.
>>
>> > Flow and ECMP
>> > -------------
>> >
>> > Section 8.3:
>> >
>> > For example, for TRILL
>> >    Data, this entropy field could be based on some hash of the
>> >    Inner.MacDA, Inner.MacSA, and Inner.VLAN or Inner.FGL.
>> >
>> > I would appreciate clearer references to what these fields are.
>>
>> In a TRILL Data packet, the payload after the TRILL Header looks like
>> an Ethernet frame except that there is always either a VLAN tag or,
>> alternatively, where the VLAN tag would be, a Fine Grained Label
>> [RFC7172]. (The preceding is the view in the TRILL RFCs, but there is
>> an equivalent and equally valid view in which all the fields through
>> and including the VLAN or FGL tag are part of the TRILL Header.) The
>> TRILL base protocol specification focuses on Ethernet as a link
>> technology between TRILL switches, in which case there will be a link
>> header including an Outer.MacDA and Outer.MacSA fields and possibly an
>> Outer.VLAN, all before the TRILL Header. See Figure 1 and Figure 2 in
>> RFC 7172.
>>
>> Some of the above could be added to the draft for clarity.
>>
>> > If I understand this correctly, the idea here is to look into the inner
>> > layer 2 frames, and use the flow equivalents that exists on that level and
>> > hash that into value that maps the flows onto the source port range.
>>
>> Yes.
>>
>> > I think this text should include a summary of the principle and ensure to
>> > note the important requirement that what is considered flows in the inner
>> > must not result in being striped over multiple source ports as this may lead
>> to
>> > reordering issues due to packets taking different paths.
>>
>> Well, we can add some text. But when would the relative ordering
>> matter for two TRILL Data packets where the two inner native payloads
>> have different values for any one or more of these three fields
>> (Inner.MacDA, Inner.MacSA, and inner VLAN/FGL tag) ? If any of those
>> fields are different, you are talking about different streams.
>>
>> > NAT and TRILL over IP:
>> > Section 8.5:
>> >
>> > If one like to use TRILL over IP through a NAT, then there are some very
>> > important considerations that are missing. First the need for static binding
>> > configurations or the need for determining ones external address(es) and
>> be
>> > able to communicate that to the peer RBridges, and in addition ensure that
>> one
>> > has keep-alives to that the NAT binding never times out.
>>
>> I think those are good points. There is an additional problem that
>> TRILL Hellos detect neighbors with which they have 2-way connectivity
>> by indicating, inside the Hellos that are sent, from what neighbors
>> Hellos have been received on that port. If a NAT is involved, these
>> neighbor addresses inside Hellos need to be mapped.
>>
>> > Next is the issue that there is almost zero chance of getting a IP/UDP
>> > encapsulation TRILL payload through the NAT if it results in IP
>> fragmentation,
>> > as NATs don't do defragment and refragmented on the internal side, and
>> an IP
>> > fragment lacks UDP port and thus can't be matched to binding.
>>
>> So perhaps the recommendation should be to configure the port to use
>> TCP if there will be fragmentation.
>>
>> > Also if you like to run IP/ESP through a NAT, then you most likely need the
>> > IP/UDP/ESP encapsulation (https://tools.ietf.org/html/rfc3948). Note that
>> this
>> > will restrict the MTU even further and thus ensure that the 1470
>> requirement
>> > cannot be fulfilled even without additional tunnels over an 1500 bytes MTU
>> > Ethernet infrastructure.
>> >
>> > I would note that also firewalls likely have issues with IP fragments for the
>> > same reason, they require significant amount of state to be verified if they
>> > should be let through.
>> >
>> > In general I think you should create a configuration that has chance to work
>> > through most middleboxes, but I think you should require static bindings. I
>> > think that configuration is, and don't laugh now, but
>> IP/UDP/ESP/TCP/TRILL,
>> > otherwise you will not be able to have both security and reliable
>> fragmentation
>> > of TRILL packets.
>>
>> OK. Thanks again for this review. It has pointed out a number of
>> problems and in thinking about those, I believe a couple of further
>> problems have come to mind that I mentioned above. We'll work on a
>> revised draft.
>>
>> Thanks,
>> Donald
>> ===============================
>>  Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
>>  155 Beaver Street, Milford, MA 01757 USA
>>  d3e3e3@gmail.com
>>
>> > Cheers
>> >
>> > Magnus Westerlund
>>
>> _______________________________________________
>> Tsv-art mailing list
>> Tsv-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/tsv-art


From nobody Fri Jun 30 18:45:20 2017
Return-Path: <d3e3e3@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 02B6212EC5C; Fri, 30 Jun 2017 18:45:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level: 
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 UojO-XNMDysF; Fri, 30 Jun 2017 18:45:16 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A317812EABA; Fri, 30 Jun 2017 18:45:16 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id v202so13237837itb.1; Fri, 30 Jun 2017 18:45:16 -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=rVwAyZ2hf3RtWJu3zXtQsb67LaGH+63xs6W4yKhOJTo=; b=rypx6KhZsxI8uLsL04P/sXqmQD8yCQoSGbvIpFgD8OVixsZ29G0vC/gn2mou35Y8h1 LBuF2ztJZMcgz8jGc0YgvJTv9BfXXkTDVBDhg7PLT5w7Ht+gCDQTRed6S2oCFMxQzQQ/ aIsaXnqJGXo2kotOXMy3lUgKVw6c2EImaSNwht3bt+B+NiCb1h/XU6lAg0Qw6qKhU8yJ 0UwVUWZRNZzlObU1DFqH2JFoJR3a6ZJfy6Hyap3l+J4eWUSe3Q3CVf53iVijjay6kxhK ntd55LY2hin6YSuUx3IHu2zuRgqBzGWCpTQP0yJsG0mf/Re3IzEEVT7blnkqUO2GXpZg OuFg==
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=rVwAyZ2hf3RtWJu3zXtQsb67LaGH+63xs6W4yKhOJTo=; b=tDJhfjRyTC7U56GrEqVy1JjbZH50tXSYtm8QnZFw9soRkeLT6zrpqgsXUz89M27LGK ZQevtcnH6pcdPf8vc9iADlbBgWl7J7SZ+VXRODlmmKSDTvXR+joSaKXK7IDwkzVRaoqS zEQ6l5fbsyHF0+Kqze2KECKhAkj6vungzK1zODgPIfoPffopAR99X6t+1VixV5VwuCqo I4iXySFUoTjQqLDGQkbVz6sCXQyZD8AQzhlPeksO0czKtGCk4sCPTDAbisCW5qw1aWAQ uxk2KyQea2OX4mEZlw6z/URRyu97zLB1I2Bii08sr/24oRdHvu6B1+6urLkxPZib4uiO tF8g==
X-Gm-Message-State: AKS2vOy/hdKCCIS9TpjsLYReE1baFk0GhDfP3bsa12cO0KYEZ7mKefYE xeBIHJNWQ7uDizx4nToCHfxxxOPQ6TxZ
X-Received: by 10.36.53.70 with SMTP id k67mr22173084ita.79.1498873516075; Fri, 30 Jun 2017 18:45:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.17.221 with HTTP; Fri, 30 Jun 2017 18:45:00 -0700 (PDT)
In-Reply-To: <CAMS-Z8DXo7MVQF2NVwBYpiRd661PxPfAH+ZxW22YUpcyK+-3-g@mail.gmail.com>
References: <CAMS-Z8DXo7MVQF2NVwBYpiRd661PxPfAH+ZxW22YUpcyK+-3-g@mail.gmail.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Fri, 30 Jun 2017 21:45:00 -0400
Message-ID: <CAF4+nEFpdq20it8decTM1S8W-X_zN_vMy6xv7_-rc0KDWicu6Q@mail.gmail.com>
Subject: Re: SECDir review of draft-IETF-trill-arp-optimization-08
To: Tina Tsou <tinatsou6@gmail.com>
Cc: "draft-IETF-trill-arp-optimization.all@ietf.org" <draft-IETF-trill-arp-optimization.all@ietf.org>,  "ietf@ietf.org" <ietf@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>, "tina.tsou@arm.com" <tina.tsou@arm.com>
Content-Type: multipart/alternative; boundary="001a114abeec7d2ef9055337afb5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/1LbHiIdjRun53S9TSygSei5Ksm0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@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, 01 Jul 2017 01:45:18 -0000

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

Thanks, for the review.

Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 <(508)%20333-2270> (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

On Thu, Jun 29, 2017 at 8:39 PM, Tina Tsou <tinatsou6@gmail.com> wrote:

> Reviewer: Tina Tsou
> Review result: Ready
>
> This is a document that specifies optimized ARP/ND response for RBridge,
> when the target's location is known, to avoid ARP/ND query and answer
> flooding.
>
> From security point of view this document is Ready. If it can describe how
> to store and transfer the key, it is more complete.
>
> In addition, a flow chart may help the readers to clearly understand the
> handling of messages in section 4.
>
> No nit was found.
> --
> Thank you, Tina
>

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

<div dir=3D"ltr"><div class=3D"gmail_extra"><div><div class=3D"m_-703298238=
9813493694gmail_signature" data-smartmail=3D"gmail_signature">Thanks, for t=
he review.</div><div class=3D"m_-7032982389813493694gmail_signature" data-s=
martmail=3D"gmail_signature"><br>Donald<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<br>=C2=
=A0Donald E. Eastlake 3rd =C2=A0 <a href=3D"tel:(508)%20333-2270" value=3D"=
+15083332270" target=3D"_blank">+1-508-333-2270</a> (cell)<br>=C2=A0155 Bea=
ver Street, Milford, MA 01757 USA<br>=C2=A0<a href=3D"mailto:d3e3e3@gmail.c=
om" target=3D"_blank">d3e3e3@gmail.com</a></div></div>
<br><div class=3D"gmail_quote">On Thu, Jun 29, 2017 at 8:39 PM, Tina Tsou <=
span dir=3D"ltr">&lt;<a href=3D"mailto:tinatsou6@gmail.com" target=3D"_blan=
k">tinatsou6@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><span style=3D"color:rgb(49,49,49);word-spacing:1px;background-color:rg=
b(255,255,255)"><div dir=3D"auto">Reviewer: Tina Tsou</div></span><span sty=
le=3D"color:rgb(49,49,49);word-spacing:1px;background-color:rgb(255,255,255=
)">Review result: Ready</span><br style=3D"color:rgb(49,49,49);word-spacing=
:1px"><br style=3D"color:rgb(49,49,49);word-spacing:1px"><span style=3D"col=
or:rgb(49,49,49);word-spacing:1px;background-color:rgb(255,255,255)"><div d=
ir=3D"auto">This is a document that specifies optimized ARP/ND response for=
 RBridge, when the target&#39;s location is known, to avoid ARP/ND query an=
d answer flooding.</div></span><br style=3D"color:rgb(49,49,49);word-spacin=
g:1px"><span style=3D"color:rgb(49,49,49);word-spacing:1px;background-color=
:rgb(255,255,255)"><div dir=3D"auto">From security point of view this docum=
ent is Ready. If it can describe how to store and transfer the key, it is m=
ore complete.</div><div dir=3D"auto"><br></div><div dir=3D"auto">In additio=
n, a flow chart may help the readers to clearly understand the handling of =
messages in section 4.</div></span><br style=3D"color:rgb(49,49,49);word-sp=
acing:1px"><span style=3D"color:rgb(49,49,49);word-spacing:1px;background-c=
olor:rgb(255,255,255)"><div dir=3D"auto">No nit was found.</div></span><spa=
n class=3D"m_-7032982389813493694HOEnZb"><font color=3D"#888888"><div dir=
=3D"ltr">-- <br></div><div data-smartmail=3D"gmail_signature">

Thank you,
Tina</div>
</font></span></blockquote></div><br></div></div>

--001a114abeec7d2ef9055337afb5--

