
From nobody Wed Apr  5 22:52:54 2017
Return-Path: <presnick@qti.qualcomm.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AC94E12943D; Wed,  5 Apr 2017 22:52:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Pete Resnick <presnick@qti.qualcomm.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-httpbis-encryption-encoding.all@ietf.org, ietf@ietf.org, ietf-http-wg@w3.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
Date: Wed, 05 Apr 2017 22:52:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/sC1NfpC9C9FlmN70BXuzRNE21YQ>
Subject: [Gen-art] Genart last call review of draft-ietf-httpbis-encryption-encoding-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 05:52:49 -0000

Reviewer: Pete Resnick
Review result: Ready

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please 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-httpbis-encryption-encoding-??
Reviewer: Pete Resnick
Review Date: 2017-04-05
IETF LC End Date: 2017-04-06
IESG Telechat date: 2017-04-13

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: Looks fine from a non-security-expert's
perspective. It is my duty to ask about keyid in section 2.1:

      A "keyid" parameter SHOULD be a UTF-8
      [RFC3629] encoded string, particularly where the identifier
might
      need to appear in a textual form.

I presume that simply means "might need to be rendered" and does not
include "might need to be typed in by someone", correct? The former is
easy; the latter probably requires a bit more text.


From nobody Thu Apr  6 12:45:28 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 066F2129407 for <gen-art@ietf.org>; Thu,  6 Apr 2017 12:45:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-to: peter@akayla.com, mahoney@nostrum.com
Message-ID: <149150792195.22040.14734065942275646321.idtracker@ietfa.amsl.com>
Date: Thu, 06 Apr 2017 12:45:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/HcK-Ee5yZ2Vf3KBEqMldB1Bk1lg>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 19:45:22 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-04-13

Reviewer               Type      LC end     Draft
Francis Dupont         Telechat  2017-02-24 draft-ietf-dmm-lma-controlled-mag-params-04 *
Francis Dupont         Telechat  2017-03-13 draft-ietf-dhc-relay-server-security-04 *
Roni Even              Telechat  2017-03-10 draft-ietf-bess-evpn-vpws-11 *
Wassim Haddad          Last Call 2017-03-27 draft-ietf-alto-multi-cost-08
Orit Levin             Last Call 2017-04-07 draft-ietf-isis-mi-bis-02
Matthew Miller         Last Call 2017-04-07 draft-ietf-rtgwg-yang-key-chain-17
Meral Shirazipour      Telechat  2017-03-13 draft-mm-wg-effect-encrypt-09
Robert Sparks          Last Call 2017-04-10 draft-ietf-isis-auto-conf-04
Peter Yee              Telechat  2017-03-01 draft-ietf-6man-rfc2460bis-09 *

Last calls:

Reviewer               Type      LC end     Draft
Meral Shirazipour      Last Call 2017-04-09 draft-ietf-core-coap-tcp-tls-07
Robert Sparks          Last Call 2017-04-13 draft-ietf-dnssd-mdns-dns-interop-04
Dale Worley            Last Call 2017-04-18 draft-ietf-grow-bgp-reject-04

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Robert Sparks
  Dale Worley
  Peter Yee
  Lucy Yong
  Jari Arkko
  Stewart Bryant
  Brian Carpenter
  Elwyn Davies
  Ralph Droms
  Francis Dupont

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Thu Apr  6 13:37:57 2017
Return-Path: <wassim.haddad@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDFB129665; Thu,  6 Apr 2017 13:37:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 p74qa5yOt04t; Thu,  6 Apr 2017 13:37:52 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EF3612965E; Thu,  6 Apr 2017 13:37:52 -0700 (PDT)
X-AuditID: c618062d-767ff700000029b8-83-58e6b90c3ca8
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by  (Symantec Mail Security) with SMTP id C7.ED.10680.C09B6E85; Thu,  6 Apr 2017 23:54:22 +0200 (CEST)
Received: from [155.53.28.109] (147.117.188.8) by smtp-am.internal.ericsson.com (147.117.188.98) with Microsoft SMTP Server id 14.3.339.0; Thu, 6 Apr 2017 16:37:49 -0400
From: Wassim Haddad <wassim.haddad@ericsson.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Message-ID: <CE6FB235-45A1-44C9-9661-AF1325BAE8EF@ericsson.com>
Date: Thu, 6 Apr 2017 13:37:49 -0700
CC: Wassim Haddad <wassim.haddad@ericsson.com>, <draft-ietf-alto-multi-cost.all@ietf.org>
To: <gen-art@ietf.org>
X-Mailer: Apple Mail (2.3273)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFupmluLIzCtJLcpLzFFi42KZXLonQZdv57MIg4NLNSzOLTvAaHH11WcW ByaPJUt+MgUwRnHZpKTmZJalFunbJXBlnLuxgrngKXPFme8z2RoY/zF1MXJySAiYSMz/8Imx i5GLQ0hgA6PEo4vzmSGctYwS/cdmg1WxCRhIfF1+lhXEZhbQkViw+xMbhK0tsWzha2YQm1dA X+LV7p/sILawgJPE/nt/WCHi9hK3N70Cq2cRUJE4snQHC0RvtET/sp1gtoiAmMSVhwegLpKV uDX7EthMIQF1iSm3JrBMYOSbhWT1LCSrZyFZvYCReRUjR2lxQU5uupHBJkZgEB2TYNPdwXh/ uuchRgEORiUe3oQfTyKEWBPLiitzDzFKcDArifCen/osQog3JbGyKrUoP76oNCe1+BCjNAeL kjjvhPMXIoQE0hNLUrNTUwtSi2CyTBycUg2MSRbvCi/9quCZK3e/pHH2009+oZ2rTm1l3Fjj 0Cz4PvyYzer76ScNPyoqngzv6PJYVb1Ut3kN/6rLOq1X3kzju8l/zD5hyTOdvjMVF07dlGYV 7lbxbOLW8N6hafT9zPUWfW/PGY3VL6T1LWujygreea5i13/o48x4MubwBj630x/f+De8ZLim xFKckWioxVxUnAgA79Dukh4CAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/4xTCMVLM7OYJ307r6RjqDgIL5tI>
Subject: [Gen-art]  Gen-ART Review of draft-ietf-alto-multi-cost-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Apr 2017 20:37:54 -0000

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

Document: draft-ietf-alto-multi-cost-08
Reviewer:  Wassim Haddad
Review Date: 06 April 2017
IETF LC End Date: 27 March 2017=20
IETF Telechat Date: 13 April 2017

Summary:  This draft is ready for publication as proposed RFC

- Major Issues: None

- Minor Issues: None


Regards,

Wassim H.





From nobody Thu Apr  6 20:26:50 2017
Return-Path: <oritl@microsoft.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B897127058; Thu,  6 Apr 2017 20:26:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_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 5iMFajAQ5Eqq; Thu,  6 Apr 2017 20:26:46 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0103.outbound.protection.outlook.com [104.47.34.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0341F129446; Thu,  6 Apr 2017 20:26:45 -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=GLFhJr/BFrNmaCDelZ1GM0u4CsbiBwY46ojzAcJXllU=; b=LQHj8c8Q/v7QbXLXxBdYOStPBzkkYYWAry5MWReG/2Dot0eD4cc/JASXi/VtHDBXdEpv/Vmc38rV7haMYbnMksU+M/vw6Tc2Z5vY21rpZO6IFNmYQ7aLYx8v3/YVdLQTLy2IPzxQr6TnPUlufAHdMU1eJm2xCpRvCzf5g/DkV2U=
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) by CY1PR0301MB2121.namprd03.prod.outlook.com (10.164.2.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Fri, 7 Apr 2017 03:26:44 +0000
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) by CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) with mapi id 15.01.1019.019; Fri, 7 Apr 2017 03:26:44 +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-isis-mi-bis.all@tools.ietf.org" <draft-ietf-isis-mi-bis.all@tools.ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJA==
Date: Fri, 7 Apr 2017 03:26:44 +0000
Message-ID: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [73.157.101.212]
x-microsoft-exchange-diagnostics: 1; CY1PR0301MB2121; 7:C1QK1mUv/ryjQAGMCyaaNd1PxAKsnpV/3x7xPYPH9XTcf5jQM5rWPb60DBT/QQ2IxYuQSBPkGMOdIqLppRytbOqbRoHi3/1muyQvt3Pditsl41HmkYKwrMlHWmD67oQGzjSFYQwG9SZpRyfCeUJeANx8ccXK4XqcYa5RIcrZurEINQJ3ukQPvFI2hEaEB4fIy1bkOrO9fq0Fi5lz+V8ni6FmsLbPNOcZRLikD+LlojAjuM94L+Ua/I284kf+TyT/1sMjRamLCEjCPIIjMNZl6jXscM1WEHEawztq9K4PxDVq0D2wMBVU+IFX1u63C7XoNh6ZhTsvt0eVEgAo0jzKwrgVTn2tznsBjqmSp7DKJlE=
x-ms-office365-filtering-correlation-id: 3cf57564-a829-4d97-c9ac-08d47d65ea6a
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:CY1PR0301MB2121; 
x-microsoft-antispam-prvs: <CY1PR0301MB21210C1857228026075CF4F0AD0C0@CY1PR0301MB2121.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705)(788757137089);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123555025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(20161123560025)(6072148); SRVR:CY1PR0301MB2121; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB2121; 
x-forefront-prvs: 0270ED2845
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39840400002)(39400400002)(39860400002)(39850400002)(377424004)(2351001)(66066001)(8990500004)(5660300001)(53936002)(6506006)(38730400002)(110136004)(10090500001)(5005710100001)(77096006)(99286003)(5640700003)(6306002)(9686003)(7736002)(6436002)(2906002)(74316002)(55016002)(305945005)(10290500002)(2501003)(33656002)(230783001)(4326008)(3660700001)(102836003)(6916009)(3846002)(6116002)(7696004)(81166006)(50986999)(2900100001)(8936002)(54356999)(189998001)(8676002)(86362001)(25786009)(3280700002)(122556002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB2121; H:CY1PR0301MB2122.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: 07 Apr 2017 03:26:44.1930 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB2121
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/2FJmXmOB-6vaP53g-gycSaUiIJ4>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 03:26:48 -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-isis-mi-bis-02
Reviewer: Orit Levin
Review Date: 2017-04-06
IETF LC End Date: 2017-04-07
IESG Telechat date: 2017-04-13

Summary: This draft is "ready with issues" for publication.

Major issues: None.

Minor issues:

1. Add text explaining the reason (or reasons) for replacing the original R=
FC 6822 from 2012.=20
Reason: It is a "bis" draft and there is no mention about it in the text.
2. In Abstract, state clearly that this standard introduces the support for=
 instances vs. other already existing concepts also listed in the Abstract =
(i.e., circuits, adjacencies,  topologies, etc.).
Reason: The wording is not clear about what is the new feature vs. what are=
 the new benefits vs. what was the original baseline
3. Throughout the document, use "standard instance" instead of "IID =3D 0" =
or "IID #0".
Reason: Expressions "standard instance", "IID =3D 0" and "IID #0" are used =
interchangeably throughout the document. It seems that they all refer to th=
e same thing - the implementation of the original protocol without the conc=
ept of instances. Please, correct me if I am wrong.
4. In section 2 par 3, change "support" and "operates" to "MUST support" to=
 use requirements language.
5. In section 2 par 2, change "may" to either "can" or "MAY" to clarify the=
 intent.
6. In section 2.1 par 3, clarify whether IID #0 is ever being used on the w=
ire. Explain the concept of the "standard interface" (see previous comment)=
.
Reason: It seems to me that IID #0 MUST never be used on the wire. Please, =
correct me if I am wrong.
7. In section 2.1, rephrase "marks ... by including" to "MUST include" to u=
se requirements language.
8. In section 2.4.1 par 2 second sentence, the sentence starting with "Howe=
ver" needs to be rewritten using standards language to explain its intent.=
=20
9. In section 2.5, replace "exists" with "MUST be performed".
10. In section 2.5.1, replace "only operates" with "MUST only be performed"=
.
11. In section 2.5.2, replace "This requires" with "It is REQUIRED".
12. In section 2.5.2 third sentence, after "inconsistent" insert "due to th=
eir configuration". Please, correct me if I am wrong.
13. In section 7 Security Considerations, discuss possible additional secur=
ity considerations (or the lack of them) related to the introduction of "in=
stances".
Reason: Beyond the normal IETF procedure, this is especially important beca=
use "multiple instances allow isolation of resources..." Can this isolation=
, if observed or interfered, be damaging beyond the previous "standard inte=
rface" situation.

Nits/editorial comments:
1. Compare (Diff) the current draft with the published RFC 6822. You will f=
ind that many of the editorial corrections got lost in the bis version. Omi=
tted corrections throughout the document include "instance-specific", " top=
ology (or topologies)", "Type-Length-Value" and others.
2. In Introduction par 4, either change the two "may" to capitals or replac=
e with "can" to clarify the intent.
3. In Introduction par 5, add references to where in the document the two m=
ethods are described. Also, consider changing "defined" to "described".
4. In Introduction par 7, move the last paragraph before listing the exampl=
es and adjust the text accordingly, for clarity.
5. In section 2.3, replace "normal" with "usual".
6. In section 2.6.1 first sentence, replace "not to cause" to "to avoid".


From nobody Fri Apr  7 01:07:26 2017
Return-Path: <sabine.randriamasy@nokia-bell-labs.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D73E0126C7B; Fri,  7 Apr 2017 01:07:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.697
X-Spam-Level: 
X-Spam-Status: No, score=-4.697 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.796, 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=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 GxcgNaodsjkL; Fri,  7 Apr 2017 01:07:22 -0700 (PDT)
Received: from EUR03-AM5-obe.outbound.protection.outlook.com (mail-eopbgr30116.outbound.protection.outlook.com [40.107.3.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 387CE128C84; Fri,  7 Apr 2017 01:07:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector2-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=lAzGgusNyZJ1CkHl9MB5z3Vcw0lwOxcKIncpzk4ak+o=; b=Lndme/d9TRIPON23eMZqsbICuuakrId7pvPF+NQvH0zDSICKNdYWuJ802DehIzDnW7CKJ/n63aqJa/6tGM9sFTaAKiaVseKoHyWoo1LTdEbreOOweU++HVCx/Xg+YAuGpDxZIv5G0py4awMZqZslL3VnIT5ZvJo7ky4QdrA3+sU=
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) by DB6PR0701MB2454.eurprd07.prod.outlook.com (10.168.75.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.8; Fri, 7 Apr 2017 08:07:20 +0000
Received: from DB6PR0701MB2454.eurprd07.prod.outlook.com ([10.168.75.147]) by DB6PR0701MB2454.eurprd07.prod.outlook.com ([10.168.75.147]) with mapi id 15.01.1019.021; Fri, 7 Apr 2017 08:07:20 +0000
From: "Randriamasy, Sabine (Nokia - FR/Nozay)" <sabine.randriamasy@nokia-bell-labs.com>
To: Wassim Haddad <wassim.haddad@ericsson.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-alto-multi-cost.all@ietf.org" <draft-ietf-alto-multi-cost.all@ietf.org>
Thread-Topic: [Gen-art] Gen-ART Review of draft-ietf-alto-multi-cost-08
Thread-Index: AQHSrxWsHskhs6dD4kS5C6qSUDEdd6G5jZsw
Date: Fri, 7 Apr 2017 08:07:19 +0000
Message-ID: <DB6PR0701MB2454C6908030141376D946AC950C0@DB6PR0701MB2454.eurprd07.prod.outlook.com>
References: <CE6FB235-45A1-44C9-9661-AF1325BAE8EF@ericsson.com>
In-Reply-To: <CE6FB235-45A1-44C9-9661-AF1325BAE8EF@ericsson.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ericsson.com; dkim=none (message not signed) header.d=none;ericsson.com; dmarc=none action=none header.from=nokia-bell-labs.com;
x-originating-ip: [135.245.20.20]
x-microsoft-exchange-diagnostics: 1; DB6PR0701MB2454; 7:+iNslQwp/DCh7fXXvA8XG/Rsevm/JcCYCFD5mmmoYusojY5wo0zrwavTde5YfFALZUciwi21XZh/V3cXLVKg9o0jYZ1u+6uaO90tqlXljokweVRx0rT/ruc9l2kzzku4fvp+vwHluAaOfklJ9m4seZXjC5ApNDSd4F77BQS9j3xaE/ftolUzY/ezfd4nJ7RkXVmargDtmweY+yjL09KNMt4tXS4AwOCwteJ1vH5Q4dw0bIvK0uctDoUAdcrqReNMfLQ3rNSfEgdVqzYYmIFm3DgcjPCnZ4jDZU38aU/khvfB1HZhApAPLK8OyBfXlSat4Dapv8bqEoz1a7FlQ46kng==
x-ms-office365-filtering-correlation-id: c3ab9574-9534-482c-d552-08d47d8d1d44
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:DB6PR0701MB2454; 
x-microsoft-antispam-prvs: <DB6PR0701MB24540CB82950E527EA7C9352950C0@DB6PR0701MB2454.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(37575265505322);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(20161123564025)(20161123560025)(20161123555025)(20161123562025)(6072148); SRVR:DB6PR0701MB2454; BCL:0; PCL:0; RULEID:; SRVR:DB6PR0701MB2454; 
x-forefront-prvs: 0270ED2845
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39860400002)(39400400002)(39450400003)(39840400002)(39410400002)(13464003)(74316002)(9686003)(6506006)(122556002)(6306002)(77096006)(3280700002)(230783001)(53936002)(50986999)(66066001)(2950100002)(54356999)(25786009)(345774005)(99286003)(6436002)(305945005)(55016002)(33656002)(76176999)(86362001)(8676002)(2501003)(38730400002)(189998001)(6246003)(81166006)(6116002)(3846002)(2900100001)(7696004)(8936002)(2906002)(4326008)(3660700001)(102836003)(5660300001)(90052001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB2454; H:DB6PR0701MB2454.eurprd07.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: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Apr 2017 08:07:19.9352 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2454
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/qH4rCqkvILQdbIPcTtgyvUUjoNU>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-alto-multi-cost-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 08:07:25 -0000

Hello Wassim,

Thank you for your feedback,
Best regards,
Sabine


>>-----Original Message-----
>>From: Wassim Haddad [mailto:wassim.haddad@ericsson.com]
>>Sent: 06 April 2017 22:38
>>To: gen-art@ietf.org
>>Cc: Wassim Haddad <wassim.haddad@ericsson.com>; draft-ietf-alto-multi-
>>cost.all@ietf.org
>>Subject: [Gen-art] Gen-ART Review of draft-ietf-alto-multi-cost-08
>>
>>I am the assigned Gen-ART reviewer for this draft. For background on Gen-
>>ART, please see the FAQ at
>><http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>>
>>Document: draft-ietf-alto-multi-cost-08
>>Reviewer:  Wassim Haddad
>>Review Date: 06 April 2017
>>IETF LC End Date: 27 March 2017
>>IETF Telechat Date: 13 April 2017
>>
>>Summary:  This draft is ready for publication as proposed RFC
>>
>>- Major Issues: None
>>
>>- Minor Issues: None
>>
>>
>>Regards,
>>
>>Wassim H.
>>
>>
>>


From nobody Fri Apr  7 10:58:59 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F387129552; Fri,  7 Apr 2017 10:58:52 -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: draft-ietf-rtgwg-yang-key-chain.all@ietf.org, ietf@ietf.org, rtgwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149158793224.11224.1489071223626497682@ietfa.amsl.com>
Date: Fri, 07 Apr 2017 10:58:52 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/RhnISkxtAEoxddVZK7595-cXEfQ>
Subject: [Gen-art] Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 17:58:52 -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-rtgwg-yang-key-chain-17
Reviewer: Matthew A. Miller
Review Date: 2017-04-07
IETF LC End Date: 2017-04-07
IESG Telechat date: 2017-04-13

Summary:

This document is almost ready to be published as a Proposed Standard,
once the issues noted herein are resolved.

Major issues:

NONE

Minor issues:

* Forgive me for my limited knowledge of YANG, but is there a reason
key-strings are only representable as either a YANG string or
hex-string type, and not the YANG binary type?

* This document does not provide much guidance around AES key wrap
other than it can be used and the KEK is provided
out-of-band/-context.
For instance, AES key-wrapped key-strings probably require using
"hexidecimal-string".  Also, assuming I'm reading the model
correctly,
it appears this feature applies to the whole chain, which I think is
worth calling out.

* This document warns against using the "clear-text" algorithm, which
the
reader is lead to understand is for legacy implementation reasons.
However, is there not a similar concern with cryptographically weak
algorithms, such as md5 and (arguably) sha1?

Nits/editorial comments:

* In Section 3.2. "Key Chain Model Features", the word "of" is
missing
between "configuration" and "an" in the phrase "support configuration
an
acceptance tolerance".

Non-nits:

* I note that idnits is calling out some odd spacing issues, but I
think
they are safe to ignore.



From nobody Fri Apr  7 13:47:51 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E2CE8127873; Fri,  7 Apr 2017 13:47:49 -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: dnssd@ietf.org, ietf@ietf.org, draft-ietf-dnssd-mdns-dns-interop.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149159806986.11195.9301095647004982341@ietfa.amsl.com>
Date: Fri, 07 Apr 2017 13:47:49 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ZXeXTlsI09nWGrX1C3RHB7V33j8>
Subject: [Gen-art] Genart last call review of draft-ietf-dnssd-mdns-dns-interop-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 20:47:50 -0000

Reviewer: Robert Sparks
Review result: Ready

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

For more information, please see the FAQ at

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

Document: draft-ietf-dnssd-mdns-dns-interop-04
Reviewer: Robert Sparks
Review Date: 2017-04-07
IETF LC End Date: 2017-04-13
IESG Telechat date: Not scheduled for a telechat

Summary: Ready for publication as an Informational RFC






From nobody Fri Apr  7 13:55:53 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0ED6E120454; Fri,  7 Apr 2017 13:55:45 -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 1T2rFpNogp1X; Fri,  7 Apr 2017 13:55:42 -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 12D2412741D; Fri,  7 Apr 2017 13:55:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3134; q=dns/txt; s=iport; t=1491598540; x=1492808140; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=9ewat/gfRoAbKiVjXknzPWDeArjRqHYiOXxr8iIbC7A=; b=J55A6aXL4JQ8UyHHGpoOcizvbC8+EipTscbfAqcf5ksm9OhA8ygbPopQ JClref6zDPCNlZ92MdGrfu7xiPad7n7TxU/k3E29gLZ/wRZpJWCgm81Xz Kc9n5xWPAob3f2hv9RXXQtNbh0kRKWQD0KkjGTsPg7pRON1IVneCYmreN w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAgDU++dY/5xdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1NhgQsHg1+KE5FElVeCDyqFeAIag0M/GAECAQEBAQEBAWsohRU?= =?us-ascii?q?BAQEBAyMRRQwEAgEIDgMDAQEBAwIUDwMCAgIwFAEICAIEAQ0FCIoHDqp4giaKa?= =?us-ascii?q?gEBAQEBAQEBAQEBAQEBAQEBAQEBARgFgQuFQ4RwhSSCOIJfBZx4AYZ/i0+CB4U?= =?us-ascii?q?uihSTfgEfOIEFWxWFHRyBY3WILIENAQEB?=
X-IronPort-AV: E=Sophos;i="5.37,167,1488844800"; d="scan'208";a="228128711"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2017 20:55:39 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v37Ktc5h008945 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Apr 2017 20:55:39 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 7 Apr 2017 15:55:38 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Fri, 7 Apr 2017 15:55:38 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90H4gcf2S4v0ECj7j9mrpM816G6YX4Q
Date: Fri, 7 Apr 2017 20:55:38 +0000
Message-ID: <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com>
In-Reply-To: <149159669211.11107.3275242226580240988@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.24.94.189]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/MC-tY7bqxF_ZdYlbqkq1mhswRVQ>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 20:55:45 -0000

Um9iZXJ0IC0NCg0KVGhhbnggZm9yIHRoZSByZXZpZXcuDQpSZXBseSBpbmxpbmUuDQoNCj4gLS0t
LS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogUm9iZXJ0IFNwYXJrcyBbbWFpbHRvOnJq
c3BhcmtzQG5vc3RydW0uY29tXQ0KPiBTZW50OiBGcmlkYXksIEFwcmlsIDA3LCAyMDE3IDE6MjUg
UE0NCj4gVG86IGdlbi1hcnRAaWV0Zi5vcmcNCj4gQ2M6IGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNv
bmYuYWxsQGlldGYub3JnOyBpZXRmQGlldGYub3JnOyBpc2lzLXdnQGlldGYub3JnDQo+IFN1Ympl
Y3Q6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYt
MDQNCj4gDQo+IFJldmlld2VyOiBSb2JlcnQgU3BhcmtzDQo+IFJldmlldyByZXN1bHQ6IFJlYWR5
IHdpdGggSXNzdWVzDQo+IA0KPiBJIGFtIHRoZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZv
ciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBBcmVhIFJldmlldw0KPiBUZWFtIChHZW4tQVJUKSBy
ZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWluZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cgZm9y
DQo+IHRoZSBJRVRGIENoYWlyLiAgUGxlYXNlIHRyZWF0IHRoZXNlIGNvbW1lbnRzIGp1c3QgbGlr
ZSBhbnkgb3RoZXIgbGFzdCBjYWxsDQo+IGNvbW1lbnRzLg0KPiANCj4gRm9yIG1vcmUgaW5mb3Jt
YXRpb24sIHBsZWFzZSBzZWUgdGhlIEZBUSBhdA0KPiANCj4gPGh0dHBzOi8vdHJhYy5pZXRmLm9y
Zy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQo+IA0KPiBEb2N1bWVudDogZHJhZnQtaWV0Zi1p
c2lzLWF1dG8tY29uZi0wNA0KPiBSZXZpZXdlcjogUm9iZXJ0IFNwYXJrcw0KPiBSZXZpZXcgRGF0
ZTogMjAxNy0wNC0wNw0KPiBJRVRGIExDIEVuZCBEYXRlOiAyMDE3LTA0LTEwDQo+IElFU0cgVGVs
ZWNoYXQgZGF0ZTogMjAxNy0wNC0xMw0KPiANCj4gU3VtbWFyeTogUmVhZHkgZm9yIHB1YmxpY2F0
aW9uIGFzIFByb3Bvc2VkIFN0YW5kYXJkLCBidXQgd2l0aCBvbmUgcG9zc2libGUNCj4gdGhpbmcg
dG8gYWRkIHRvIHRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9uIHNlY3Rpb24NCj4gDQo+IFRoaXMg
ZG9jdW1lbnQgaXMgY2xlYXIgYW5kIHNlZW1zIHN0cmFpZ2h0Zm9yd2FyZCB0byBpbXBsZW1lbnQu
DQo+IA0KPiBJIHRoaW5rLCBob3dldmVyLCB0aGVyZSBpcyBhbiBhdHRhY2sgcG9zc2liaWxpdHkg
eW91IHNob3VsZCBjYWxsIG91dCBpbiB0aGUNCj4gc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgc2Vj
dGlvbi4gQXMgaG9tZSByb3V0ZXJzIGFyZSB1c2VkIGFzIGV4YW1wbGVzIG9mDQo+IGVsZW1lbnRz
IHRoYXQgbWlnaHQgdXNlIHRoaXMgcHJvdG9jb2wsIGNvbnNpZGVyIHRoZSBjYXNlIG9mIGEgbWFs
aWNpb3VzIHBhcnR5DQo+IHdhbnRpbmcgdG8gZGVueSBzZXJ2aWNlIGluIHRoYXQgaG9tZS4NCj4g
QSBzdWJvcm5lZCBkZXZpY2UgaW4gdGhlIGhvbWUgY291bGQgd2F0Y2ggZm9yIHRoZSBwcm90b2Nv
bCwgYW5kIHByZXNlbnQgYQ0KPiBjcmFmdGVkIHBhY2tldCB0byBmb3JjZSB0aGUgaG9tZSByb3V0
ZXIocykgdG8gcmUtc3RhcnQgdGhlIGF1dG9jb25maWd1cmF0aW9uDQo+IHByb3RvY29sIGNvbnRp
bnVhbGx5IChieSBjbGFpbWluZyB0byBiZSBhIGR1cGxpY2F0ZSBhbmQgYmVpbmcgY2FyZWZ1bCB0
byBtYWtlDQo+IGl0IHRoZSByb3V0ZXJzIGpvYiB0byByZXN0YXJ0KS4NCj4gSGF2aW5nIHRoZSBt
ZDUgcGFzc3dvcmQgY29uZmlndXJlZCB3b3VsZCBtaXRpZ2F0ZSB0aGlzIGF0dGFjay4NCg0KW0xl
czpdIFRoZSBkcmFmdCBzYXlzIHR3byB0aGluZ3Mgd2hpY2ggYXJlIHJlbGV2YW50Og0KDQozLjUu
MS4gIEF1dGhlbnRpY2F0aW9uIFRMVg0KDQogICBJdCBpcyBSRUNPTU1FTkRFRCB0aGF0IElTLUlT
IHJvdXRlcnMgc3VwcG9ydGluZyB0aGlzIHNwZWNpZmljYXRpb24NCiAgIG9mZmVyIGFuIG9wdGlv
biB0byBleHBsaWNpdGx5IGNvbmZpZ3VyZSBhIHNpbmdsZSBwYXNzd29yZCBmb3IgSE1BQy0NCiAg
IE1ENSBhdXRoZW50aWNhdGlvbiBhcyBzcGVjaWZpZWQgaW5bUkZDNTMwNF0uDQoNCjQuICBTZWN1
cml0eSBDb25zaWRlcmF0aW9ucw0KDQogICBJbiBnZW5lcmFsLCB0aGUgdXNlIG9mIGF1dGhlbnRp
Y2F0aW9uIGlzIGluY29tcGF0aWJsZSB3aXRoIGF1dG8tDQogICBjb25maWd1cmF0aW9uIGFzIGl0
IHJlcXVpcmVzIHNvbWUgbWFudWFsIGNvbmZpZ3VyYXRpb24uDQoNCkl0IHNlZW1zIHRvIG1lIHRo
YXQgdGhlc2Ugc2VjdGlvbnMgYWRlcXVhdGVseSBjb3ZlciB5b3VyIHBvaW50Lg0KPz8/DQoNCiAg
ICBMZXMNCg0K


From nobody Fri Apr  7 14:18:57 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AB5B128B91; Fri,  7 Apr 2017 14:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.88
X-Spam-Level: 
X-Spam-Status: No, score=-1.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=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 EOG1fxzy8oYx; Fri,  7 Apr 2017 14:18:23 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B27C1292D0; Fri,  7 Apr 2017 14:18:03 -0700 (PDT)
Received: from unescapeable.local ([47.186.26.91]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v37LHx4q031384 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 7 Apr 2017 16:18:00 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [47.186.26.91] claimed to be unescapeable.local
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com>
Cc: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com>
Date: Fri, 7 Apr 2017 16:17:59 -0500
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: <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Z2cr8lxIuxC1kUuidDfFbo9pCqw>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 21:18:32 -0000

On 4/7/17 3:55 PM, Les Ginsberg (ginsberg) wrote:
> Robert -
>
> Thanx for the review.
> Reply inline.
>
>> -----Original Message-----
>> From: Robert Sparks [mailto:rjsparks@nostrum.com]
>> Sent: Friday, April 07, 2017 1:25 PM
>> To: gen-art@ietf.org
>> Cc: draft-ietf-isis-auto-conf.all@ietf.org; ietf@ietf.org; isis-wg@ietf.org
>> Subject: Genart last call review of draft-ietf-isis-auto-conf-04
>>
>> Reviewer: Robert Sparks
>> 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-isis-auto-conf-04
>> Reviewer: Robert Sparks
>> Review Date: 2017-04-07
>> IETF LC End Date: 2017-04-10
>> IESG Telechat date: 2017-04-13
>>
>> Summary: Ready for publication as Proposed Standard, but with one possible
>> thing to add to the security consideration section
>>
>> This document is clear and seems straightforward to implement.
>>
>> I think, however, there is an attack possibility you should call out in the
>> security considerations section. As home routers are used as examples of
>> elements that might use this protocol, consider the case of a malicious party
>> wanting to deny service in that home.
>> A suborned device in the home could watch for the protocol, and present a
>> crafted packet to force the home router(s) to re-start the autoconfiguration
>> protocol continually (by claiming to be a duplicate and being careful to make
>> it the routers job to restart).
>> Having the md5 password configured would mitigate this attack.
> [Les:] The draft says two things which are relevant:
>
> 3.5.1.  Authentication TLV
>
>     It is RECOMMENDED that IS-IS routers supporting this specification
>     offer an option to explicitly configure a single password for HMAC-
>     MD5 authentication as specified in[RFC5304].
>
> 4.  Security Considerations
>
>     In general, the use of authentication is incompatible with auto-
>     configuration as it requires some manual configuration.
>
> It seems to me that these sections adequately cover your point.
> ???
They provide the mitigation. They do not call out the risk.

The current security considerations section says for wired networks, 
plugging into the wire is protection enough, and you don't need to use 
the authentication tlv.  I don't think that's true given the possibility 
of this attack. I suggest discussing the attack in the security 
considerations section and pointing to using the Authentication TLV with 
it's onerous bit of manual configuration as the mitigation.

>
>      Les
>


From nobody Fri Apr  7 14:30:51 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 377131200C1; Fri,  7 Apr 2017 14:30:34 -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 wsvwksPF2roP; Fri,  7 Apr 2017 14:30:28 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5EA0127871; Fri,  7 Apr 2017 14:30:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5604; q=dns/txt; s=iport; t=1491600616; x=1492810216; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=6TNYProto9lO+SJcnYZiGRBEYaDNB8tFLT112Bereuw=; b=Oc6eXDv1QXb3m/wp6tPE3xYbLUKSqX1U3XM16nZ3V2s1h7KWyxIky+fv fcRBukagGrhiBiG9w655o1mNYfE/HsCA5kt56PIFnMTuJyMUhTLlsZfR8 a/lRn5pEWHIVm15H55NhM8G9urDmS/PyAcjVup2/aZjc0uoXDzjYJ7isv c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAgCNBOhY/5hdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1NhgQsHg1+KE5FElVeCDyqFeAIag0Q/GAECAQEBAQEBAWsohRU?= =?us-ascii?q?BAQEBAyMRRQwEAgEIDgMDAQEBAQICFA8DAgICMBQBCAgCBAENBQiKBw6qZoImi?= =?us-ascii?q?moBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYELhUOEcIUkgjiCXwWJKpNOAYZ/i0+?= =?us-ascii?q?CB4UuihSTfgEfOIEFWxWFHRyBY3WILIENAQEB?=
X-IronPort-AV: E=Sophos;i="5.37,168,1488844800"; d="scan'208";a="233901098"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2017 21:30:15 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v37LUFXN002047 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Apr 2017 21:30:15 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 7 Apr 2017 16:30:14 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Fri, 7 Apr 2017 16:30:14 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90H4gcf2S4v0ECj7j9mrpM816G6YX4QgABbdoD//63TkA==
Date: Fri, 7 Apr 2017 21:30:14 +0000
Message-ID: <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com>
In-Reply-To: <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.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.24.94.189]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/FrYwrVRXOibFoVdd3OjDLQVpvrI>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 21:30:34 -0000

Um9iZXJ0IC0NCg0KPiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBSb2JlcnQg
U3BhcmtzIFttYWlsdG86cmpzcGFya3NAbm9zdHJ1bS5jb21dDQo+IFNlbnQ6IEZyaWRheSwgQXBy
aWwgMDcsIDIwMTcgMjoxOCBQTQ0KPiBUbzogTGVzIEdpbnNiZXJnIChnaW5zYmVyZyk7IGdlbi1h
cnRAaWV0Zi5vcmcNCj4gQ2M6IGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYuYWxsQGlldGYub3Jn
OyBpZXRmQGlldGYub3JnOyBpc2lzLXdnQGlldGYub3JnDQo+IFN1YmplY3Q6IFJlOiBHZW5hcnQg
bGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLTA0DQo+IA0KPiAN
Cj4gDQo+IE9uIDQvNy8xNyAzOjU1IFBNLCBMZXMgR2luc2JlcmcgKGdpbnNiZXJnKSB3cm90ZToN
Cj4gPiBSb2JlcnQgLQ0KPiA+DQo+ID4gVGhhbnggZm9yIHRoZSByZXZpZXcuDQo+ID4gUmVwbHkg
aW5saW5lLg0KPiA+DQo+ID4+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+ID4+IEZyb206
IFJvYmVydCBTcGFya3MgW21haWx0bzpyanNwYXJrc0Bub3N0cnVtLmNvbV0NCj4gPj4gU2VudDog
RnJpZGF5LCBBcHJpbCAwNywgMjAxNyAxOjI1IFBNDQo+ID4+IFRvOiBnZW4tYXJ0QGlldGYub3Jn
DQo+ID4+IENjOiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLmFsbEBpZXRmLm9yZzsgaWV0ZkBp
ZXRmLm9yZzsNCj4gPj4gaXNpcy13Z0BpZXRmLm9yZw0KPiA+PiBTdWJqZWN0OiBHZW5hcnQgbGFz
dCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLTA0DQo+ID4+DQo+ID4+
IFJldmlld2VyOiBSb2JlcnQgU3BhcmtzDQo+ID4+IFJldmlldyByZXN1bHQ6IFJlYWR5IHdpdGgg
SXNzdWVzDQo+ID4+DQo+ID4+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2aWV3ZXIgZm9y
IHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENCj4gPj4gUmV2aWV3IFRlYW0gKEdlbi1BUlQp
IHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZCBieQ0KPiA+PiB0aGUg
SUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMganVz
dCBsaWtlDQo+ID4+IGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+ID4+DQo+ID4+IEZv
ciBtb3JlIGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4gPj4NCj4gPj4gPGh0
dHBzOi8vdHJhYy5pZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQo+ID4+DQo+ID4+
IERvY3VtZW50OiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLTA0DQo+ID4+IFJldmlld2VyOiBS
b2JlcnQgU3BhcmtzDQo+ID4+IFJldmlldyBEYXRlOiAyMDE3LTA0LTA3DQo+ID4+IElFVEYgTEMg
RW5kIERhdGU6IDIwMTctMDQtMTANCj4gPj4gSUVTRyBUZWxlY2hhdCBkYXRlOiAyMDE3LTA0LTEz
DQo+ID4+DQo+ID4+IFN1bW1hcnk6IFJlYWR5IGZvciBwdWJsaWNhdGlvbiBhcyBQcm9wb3NlZCBT
dGFuZGFyZCwgYnV0IHdpdGggb25lDQo+ID4+IHBvc3NpYmxlIHRoaW5nIHRvIGFkZCB0byB0aGUg
c2VjdXJpdHkgY29uc2lkZXJhdGlvbiBzZWN0aW9uDQo+ID4+DQo+ID4+IFRoaXMgZG9jdW1lbnQg
aXMgY2xlYXIgYW5kIHNlZW1zIHN0cmFpZ2h0Zm9yd2FyZCB0byBpbXBsZW1lbnQuDQo+ID4+DQo+
ID4+IEkgdGhpbmssIGhvd2V2ZXIsIHRoZXJlIGlzIGFuIGF0dGFjayBwb3NzaWJpbGl0eSB5b3Ug
c2hvdWxkIGNhbGwgb3V0DQo+ID4+IGluIHRoZSBzZWN1cml0eSBjb25zaWRlcmF0aW9ucyBzZWN0
aW9uLiBBcyBob21lIHJvdXRlcnMgYXJlIHVzZWQgYXMNCj4gPj4gZXhhbXBsZXMgb2YgZWxlbWVu
dHMgdGhhdCBtaWdodCB1c2UgdGhpcyBwcm90b2NvbCwgY29uc2lkZXIgdGhlIGNhc2UNCj4gPj4g
b2YgYSBtYWxpY2lvdXMgcGFydHkgd2FudGluZyB0byBkZW55IHNlcnZpY2UgaW4gdGhhdCBob21l
Lg0KPiA+PiBBIHN1Ym9ybmVkIGRldmljZSBpbiB0aGUgaG9tZSBjb3VsZCB3YXRjaCBmb3IgdGhl
IHByb3RvY29sLCBhbmQNCj4gPj4gcHJlc2VudCBhIGNyYWZ0ZWQgcGFja2V0IHRvIGZvcmNlIHRo
ZSBob21lIHJvdXRlcihzKSB0byByZS1zdGFydCB0aGUNCj4gPj4gYXV0b2NvbmZpZ3VyYXRpb24g
cHJvdG9jb2wgY29udGludWFsbHkgKGJ5IGNsYWltaW5nIHRvIGJlIGEgZHVwbGljYXRlDQo+ID4+
IGFuZCBiZWluZyBjYXJlZnVsIHRvIG1ha2UgaXQgdGhlIHJvdXRlcnMgam9iIHRvIHJlc3RhcnQp
Lg0KPiA+PiBIYXZpbmcgdGhlIG1kNSBwYXNzd29yZCBjb25maWd1cmVkIHdvdWxkIG1pdGlnYXRl
IHRoaXMgYXR0YWNrLg0KPiA+IFtMZXM6XSBUaGUgZHJhZnQgc2F5cyB0d28gdGhpbmdzIHdoaWNo
IGFyZSByZWxldmFudDoNCj4gPg0KPiA+IDMuNS4xLiAgQXV0aGVudGljYXRpb24gVExWDQo+ID4N
Cj4gPiAgICAgSXQgaXMgUkVDT01NRU5ERUQgdGhhdCBJUy1JUyByb3V0ZXJzIHN1cHBvcnRpbmcg
dGhpcyBzcGVjaWZpY2F0aW9uDQo+ID4gICAgIG9mZmVyIGFuIG9wdGlvbiB0byBleHBsaWNpdGx5
IGNvbmZpZ3VyZSBhIHNpbmdsZSBwYXNzd29yZCBmb3IgSE1BQy0NCj4gPiAgICAgTUQ1IGF1dGhl
bnRpY2F0aW9uIGFzIHNwZWNpZmllZCBpbltSRkM1MzA0XS4NCj4gPg0KPiA+IDQuICBTZWN1cml0
eSBDb25zaWRlcmF0aW9ucw0KPiA+DQo+ID4gICAgIEluIGdlbmVyYWwsIHRoZSB1c2Ugb2YgYXV0
aGVudGljYXRpb24gaXMgaW5jb21wYXRpYmxlIHdpdGggYXV0by0NCj4gPiAgICAgY29uZmlndXJh
dGlvbiBhcyBpdCByZXF1aXJlcyBzb21lIG1hbnVhbCBjb25maWd1cmF0aW9uLg0KPiA+DQo+ID4g
SXQgc2VlbXMgdG8gbWUgdGhhdCB0aGVzZSBzZWN0aW9ucyBhZGVxdWF0ZWx5IGNvdmVyIHlvdXIg
cG9pbnQuDQo+ID4gPz8/DQo+IFRoZXkgcHJvdmlkZSB0aGUgbWl0aWdhdGlvbi4gVGhleSBkbyBu
b3QgY2FsbCBvdXQgdGhlIHJpc2suDQo+IA0KPiBUaGUgY3VycmVudCBzZWN1cml0eSBjb25zaWRl
cmF0aW9ucyBzZWN0aW9uIHNheXMgZm9yIHdpcmVkIG5ldHdvcmtzLCBwbHVnZ2luZw0KPiBpbnRv
IHRoZSB3aXJlIGlzIHByb3RlY3Rpb24gZW5vdWdoLCBhbmQgeW91IGRvbid0IG5lZWQgdG8gdXNl
IHRoZQ0KPiBhdXRoZW50aWNhdGlvbiB0bHYuICBJIGRvbid0IHRoaW5rIHRoYXQncyB0cnVlIGdp
dmVuIHRoZSBwb3NzaWJpbGl0eSBvZiB0aGlzIGF0dGFjay4NCj4gSSBzdWdnZXN0IGRpc2N1c3Np
bmcgdGhlIGF0dGFjayBpbiB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgc2VjdGlvbiBhbmQN
Cj4gcG9pbnRpbmcgdG8gdXNpbmcgdGhlIEF1dGhlbnRpY2F0aW9uIFRMViB3aXRoIGl0J3Mgb25l
cm91cyBiaXQgb2YgbWFudWFsDQo+IGNvbmZpZ3VyYXRpb24gYXMgdGhlIG1pdGlnYXRpb24uDQo+
IA0KW0xlczpdIElmIHlvdSBpbnNpc3QgSSBhbSBPSyB3aXRoIHRoaXMgLSBidXQgZnJhbmtseSB5
b3UgYXJlIHR3aXN0aW5nIG15IGFybS4gOi0pDQpTeXN0ZW0taWQgZHVwbGljYXRpb24gaXMgYSBw
cm9ibGVtIGZvciBhbnkgZGVwbG95bWVudCAtIG5vdCBqdXN0IGF1dG9jb25maWcgZGVwbG95bWVu
dHMuIEFuZCBpdCB3aWxsIGJlIGRpc3J1cHRpdmUgaW4gYW55IG5ldHdvcmsgdW50aWwgaXQgaXMg
cmVzb2x2ZWQuDQpUaGUgb25seSB0aGluZyBhdXRvY29uZmlnIGhhcyBhZGRlZCBpcyBhIHdheSB0
byByZXNvbHZlIHRoaXMgdy9vIG1hbnVhbCBpbnRlcnZlbnRpb24uIFRoaXMgaW4gbm8gd2F5IGlu
Y3JlYXNlcyB0aGUgdnVsbmVyYWJpbGl0eSBub3IgdGhlIGRpc3J1cHRpb24gdGhlIGF0dGFja2Vy
IGNhbiBwcm9kdWNlLiAoWWVzIC0gSSBzdGF0ZSB0aGF0IHF1aXRlIGludGVudGlvbmFsbHkpLg0K
U28geW91IGFyZSBhc2tpbmcgdXMgdG8gcmVwZWF0IGEgZGlzY3Vzc2lvbiB3aGljaCBoYXMgYWxy
ZWFkeSBiZWVuIGhlbGQgaW4gdGhlIGNvbnRleHQgb2YgUkZDIDUzMDQgYW5kIFJGQyA1MzEwLg0K
DQpJdCB3b3VsZCBiZSBtb3JlIGFwcHJvcHJpYXRlIHRvIGFkZCB0aGUgbm9ybWFsIHJlZmVyZW5j
ZSB0byBSRkMgNTMwNC81MzEwIGluIHRoZSBTZWN1cml0eSBzZWN0aW9uIHRoYW4gd2hhdCB5b3Ug
cHJvcG9zZS4NCg0KICAgTGVzDQoNCj4gPg0KPiA+ICAgICAgTGVzDQo+ID4NCg0K


From nobody Fri Apr  7 14:45:01 2017
Return-Path: <aretana@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A20B128954; Fri,  7 Apr 2017 14:44:53 -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 9IQu480dmgNU; Fri,  7 Apr 2017 14:44:49 -0700 (PDT)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87669127867; Fri,  7 Apr 2017 14:44:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2054; q=dns/txt; s=iport; t=1491601479; x=1492811079; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ex9eRFrNp5aIHAeA9nV+XTDS3EGQEvumdwkHZtElj0k=; b=LRxgexDVFAFKGd6pT5dpWwcvxbv34BMAZbsHX8aqBd+XlXUwa7xLFjSm BPlJEc/nTc94lfEu1Z39rY2/BDNv/mln7CcDWle8WEh2XObpykD53r7bz OXEV4wYZOqYVHOk9v96kDiWWE8pJir0Gj8j/MMOftc9qvvHR6Humq8VNz A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAgCgB+hY/5JdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1OBbAeDX4oTkUSVV4IPhiICGoNEPxgBAgEBAQEBAQFrKIUWAQQ?= =?us-ascii?q?BIxFFBQsCAQgaAiYCAgIwFRACBAENBYoHCKsJgiaKagEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAR2BC4VDggWCa4RWgwYugjEBBJYfhlkBklcKkTaTfgEfOIEFWxVSAYZ?= =?us-ascii?q?JdYgsgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,168,1488844800"; d="scan'208";a="228460278"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2017 21:44:38 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id v37LicQ9023688 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Apr 2017 21:44:38 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 7 Apr 2017 16:44:38 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Fri, 7 Apr 2017 16:44:37 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90HdNwrO1bKAUiTTjwvgN+2naG6trYAgAAGPoCAAANsAP//wPeA
Date: Fri, 7 Apr 2017 21:44:37 +0000
Message-ID: <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com>
In-Reply-To: <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.6]
Content-Type: text/plain; charset="utf-8"
Content-ID: <70AB0C03D82FC941A35D0037BC501F0B@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/u0w5x6wPHcEneyg4SBjvspfXwUc>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 21:44:53 -0000

T24gNC83LzE3LCA1OjMwIFBNLCAiTGVzIEdpbnNiZXJnIChnaW5zYmVyZykiIDxnaW5zYmVyZ0Bj
aXNjby5jb20+IHdyb3RlOg0KDQpMZXM6DQoNCkhpIQ0KDQo+IFN5c3RlbS1pZCBkdXBsaWNhdGlv
biBpcyBhIHByb2JsZW0gZm9yIGFueSBkZXBsb3ltZW50IC0gbm90IGp1c3QgYXV0b2NvbmZpZyAN
Cj4gZGVwbG95bWVudHMuIEFuZCBpdCB3aWxsIGJlIGRpc3J1cHRpdmUgaW4gYW55IG5ldHdvcmsg
dW50aWwgaXQgaXMgcmVzb2x2ZWQuDQo+DQo+IFRoZSBvbmx5IHRoaW5nIGF1dG9jb25maWcgaGFz
IGFkZGVkIGlzIGEgd2F5IHRvIHJlc29sdmUgdGhpcyB3L28gbWFudWFsIA0KPiBpbnRlcnZlbnRp
b24uIFRoaXMgaW4gbm8gd2F5IGluY3JlYXNlcyB0aGUgdnVsbmVyYWJpbGl0eSBub3IgdGhlIGRp
c3J1cHRpb24gdGhlIA0KPiBhdHRhY2tlciBjYW4gcHJvZHVjZS4gKFllcyAtIEkgc3RhdGUgdGhh
dCBxdWl0ZSBpbnRlbnRpb25hbGx5KS4NCg0KSSBkb27igJl0IGtub3cgYWJvdXQgUm9iZXJ0LCBi
dXQgdGhhdCBpcyBwYXJ0IG9mIHRoZSBkaXNjdXNzaW9uIEkgd291bGQgbGlrZSB0byBzZWUuDQoN
ClllcywgZHVwbGljYXRlIHN5c3RlbS1pZHMgaGF2ZSBhbHdheXMgYmVlbiBhIHBvdGVudGlhbCBw
cm9ibGVtLCBidXQgdGhpcyBkb2N1bWVudCBpbnRyb2R1Y2VzIGEgbmV3IGRlLWR1cGxpY2F0aW9u
IG1lY2hhbmlzbSB0aGF0IHJlc3VsdHMgbm90IGp1c3QgaW4gdW5zeW5j4oCZZCBkYXRhYmFzZXMs
IGJ1dCBpbiByZXN0YXJ0aW5nIGFkamFjZW5jaWVzIOKAkyBzbyBhdCBsZWFzdCB0aGUgbWFuaWZl
c3RhdGlvbiBvZiB0aGUgcHJvYmxlbSBpcyBkaWZmZXJlbnQuDQoNCj4gU28geW91IGFyZSBhc2tp
bmcgdXMgdG8gcmVwZWF0IGEgZGlzY3Vzc2lvbiB3aGljaCBoYXMgYWxyZWFkeSBiZWVuIGhlbGQg
aW4gdGhlIGNvbnRleHQgb2YgDQo+IFJGQyA1MzA0IGFuZCBSRkMgNTMxMC4NCj4NCj4gSXQgd291
bGQgYmUgbW9yZSBhcHByb3ByaWF0ZSB0byBhZGQgdGhlIG5vcm1hbCByZWZlcmVuY2UgdG8gUkZD
IDUzMDQvNTMxMCBpbiB0aGUgDQo+IFNlY3VyaXR5IHNlY3Rpb24gdGhhbiB3aGF0IHlvdSBwcm9w
b3NlLg0KDQpJIGRvbuKAmXQgdGhpbmsgaXQgaHVydHMgdG8gYWRkIGEgcmVmZXJlbmNlIHRvIHRo
b3NlIFJGQ3MsIGJ1dCB0aGV5IGFyZSBib3RoIGFib3V0IGFkZGluZyBhdXRoZW50aWNhdGlvbiDi
gJMgdGhlIHByb2JsZW0gaW4gdGhpcyBkb2N1bWVudCBpcyBleGFjZXJiYXRlZCBieSB0aGUgZmFj
dCB0aGF0IHRoZXJl4oCZcyBubyBhdXRoZW50aWNhdGlvbiBieSBkZWZhdWx0Lg0KDQpUaGUgbG93
ZXIgbGF5ZXIgYXV0aGVudGljYXRpb24gbWVjaGFuaXNtcyBhcmUgcXVpdGUgd2Vhaywgc3BlY2lh
bGx5IGtub3dpbmcgdGhhdCwgaWYgaW4gYSBob21lIGVudmlyb25tZW50LCBmb3IgZXhhbXBsZSwg
aXQgbWF5IGJlIHJlbGF0aXZlbHkgZWFzeSB0byBjb25uZWN0IHRvIHRoZSBXaUZpIG5ldHdvcmsu
DQoNCkFsdmFyby4NCg0KDQo=


From nobody Fri Apr  7 15:44:53 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCE3112714F; Fri,  7 Apr 2017 15:44:38 -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 D5bekc4kL0BF; Fri,  7 Apr 2017 15:44:32 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57780128B8E; Fri,  7 Apr 2017 15:44:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4000; q=dns/txt; s=iport; t=1491605067; x=1492814667; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=nHmSyAnRov0e8Q1BW7uMEdM0PAE08g0b0qFKipF0eik=; b=USNIDVuGyYmUm15unI9XvYbEK4IsdDjlFxVnSmTlszzkZ1ekapr9iO8x Cg6AIdoDeNCl0gu861bVSHIwLnlT9+gVxfJP9gsZCzG0L9W8gWOob/EYo zplLMMOHIPoyGq4XpLhujPqL/qsoa6LuxCKsZpxuZ4DIWgnce/r4l2aAW 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AFAgACFehY/5pdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgygrgWwHg1+KE5FElVeCD4YiAhqDRD8YAQIBAQEBAQEBayiFFQE?= =?us-ascii?q?BAQECASMRRQwEAgEIEQQBAQECAiYCAgIwFQgIAgQBDQUIiX8IqlyCJopqAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBHYELhUOEcIdcgl8FnHgBkk6RSZN+AR84gQVbFYc?= =?us-ascii?q?cdYgsgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,168,1488844800"; d="scan'208";a="230307470"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2017 22:44:26 +0000
Received: from XCH-ALN-002.cisco.com (xch-aln-002.cisco.com [173.36.7.12]) by rcdn-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v37MiQsA022101 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Apr 2017 22:44:26 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-002.cisco.com (173.36.7.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 7 Apr 2017 17:44:25 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Fri, 7 Apr 2017 17:44:25 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90H4gcf2S4v0ECj7j9mrpM816G6YX4QgABbdoD//63TkIAAWZ6A//+58rA=
Date: Fri, 7 Apr 2017 22:44:25 +0000
Message-ID: <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com>
In-Reply-To: <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.94.189]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/FNonu_1H8I81Y55aGSBVqVSsAg4>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Apr 2017 22:44:39 -0000

QWx2YXJvIC0NCg0KTm90IHN1cmUgaG93IGxvbmcgd2Ugc2hvdWxkIGRlYmF0ZSB0aGlzIGFzIHRo
ZSB0ZXh0IHlvdSBhcmUgYXNraW5nIGZvciBpcyBtb2Rlc3QgLSBidXQgb25lIG1vcmUgYXR0ZW1w
dCBvbiBteSBwYXJ0IC0gbm90IHNvIG11Y2ggdG8gZGViYXRlIHdoZXRoZXIgdG8gYWRkIHRleHQg
b3Igbm90IC0gYnV0IHRvIGNvbWUgdG8gYSBjb21tb24gdW5kZXJzdGFuZGluZy4NCg0KPiAtLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBBbHZhcm8gUmV0YW5hIChhcmV0YW5hKQ0K
PiBTZW50OiBGcmlkYXksIEFwcmlsIDA3LCAyMDE3IDI6NDUgUE0NCj4gVG86IExlcyBHaW5zYmVy
ZyAoZ2luc2JlcmcpOyBSb2JlcnQgU3BhcmtzOyBnZW4tYXJ0QGlldGYub3JnDQo+IENjOiBkcmFm
dC1pZXRmLWlzaXMtYXV0by1jb25mLmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsgaXNpcy13
Z0BpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogR2VuYXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJh
ZnQtaWV0Zi1pc2lzLWF1dG8tY29uZi0wNA0KPiANCj4gT24gNC83LzE3LCA1OjMwIFBNLCAiTGVz
IEdpbnNiZXJnIChnaW5zYmVyZykiIDxnaW5zYmVyZ0BjaXNjby5jb20+IHdyb3RlOg0KPiANCj4g
TGVzOg0KPiANCj4gSGkhDQo+IA0KPiA+IFN5c3RlbS1pZCBkdXBsaWNhdGlvbiBpcyBhIHByb2Js
ZW0gZm9yIGFueSBkZXBsb3ltZW50IC0gbm90IGp1c3QNCj4gPiBhdXRvY29uZmlnIGRlcGxveW1l
bnRzLiBBbmQgaXQgd2lsbCBiZSBkaXNydXB0aXZlIGluIGFueSBuZXR3b3JrIHVudGlsIGl0IGlz
DQo+IHJlc29sdmVkLg0KPiA+DQo+ID4gVGhlIG9ubHkgdGhpbmcgYXV0b2NvbmZpZyBoYXMgYWRk
ZWQgaXMgYSB3YXkgdG8gcmVzb2x2ZSB0aGlzIHcvbw0KPiA+IG1hbnVhbCBpbnRlcnZlbnRpb24u
IFRoaXMgaW4gbm8gd2F5IGluY3JlYXNlcyB0aGUgdnVsbmVyYWJpbGl0eSBub3INCj4gPiB0aGUg
ZGlzcnVwdGlvbiB0aGUgYXR0YWNrZXIgY2FuIHByb2R1Y2UuIChZZXMgLSBJIHN0YXRlIHRoYXQg
cXVpdGUNCj4gaW50ZW50aW9uYWxseSkuDQo+IA0KPiBJIGRvbuKAmXQga25vdyBhYm91dCBSb2Jl
cnQsIGJ1dCB0aGF0IGlzIHBhcnQgb2YgdGhlIGRpc2N1c3Npb24gSSB3b3VsZCBsaWtlIHRvDQo+
IHNlZS4NCj4gDQo+IFllcywgZHVwbGljYXRlIHN5c3RlbS1pZHMgaGF2ZSBhbHdheXMgYmVlbiBh
IHBvdGVudGlhbCBwcm9ibGVtLCBidXQgdGhpcw0KPiBkb2N1bWVudCBpbnRyb2R1Y2VzIGEgbmV3
IGRlLWR1cGxpY2F0aW9uIG1lY2hhbmlzbSB0aGF0IHJlc3VsdHMgbm90IGp1c3QNCj4gaW4gdW5z
eW5j4oCZZCBkYXRhYmFzZXMsIGJ1dCBpbiByZXN0YXJ0aW5nIGFkamFjZW5jaWVzIOKAkyBzbyBh
dCBsZWFzdCB0aGUNCj4gbWFuaWZlc3RhdGlvbiBvZiB0aGUgcHJvYmxlbSBpcyBkaWZmZXJlbnQu
DQo+IA0KW0xlczpdIFRoZSAicHJvYmxlbSIgZXhpc3RzIGFzIGxvbmcgYXMgdGhlIGR1cGxpY2F0
ZSBzeXN0ZW0taWRzIGV4aXN0LiBUaGUgcmVjb3ZlcnkgbWVjaGFuaXNtIGRvZXMgbm90IGludHJv
ZHVjZSBuZXcgcHJvYmxlbXMgLSBpdCBhY3R1YWxseSBhY3RzIHRvIG1pbmltaXplIHRoZSBkdXJh
dGlvbiBvZiB0aGUgcHJvYmxlbS4gT25lIGNvdWxkIGFyZ3VlIChhbmQgSSBhbSBOT1QgZG9pbmcg
c28pIHRoYXQgYXV0b21hdGVkIHJlc29sdXRpb24gY291bGQgYmUgYSBiZW5lZml0IGluIGFsbCBk
ZXBsb3ltZW50cy4gSSB0aGluayB0aGUgaXNzdWUgaW4gbm9uLWF1dG9jb25maWcgZGVwbG95bWVu
dHMgaXMgdGhhdCBzaW5jZSBzeXN0ZW1zIGhhdmUgYmVlbiBtYW51YWxseSBwcm92aXNpb25lZCB3
ZSBjYW5ub3QgYXNzdW1lIHRoYXQgbmV0d29yayBvcGVyYXRvcnMgd2FudCB1cyB0byBhdXRvbWF0
aWNhbGx5IGNoYW5nZSB0aGUgY29uZmlnIG9uIG9uZSBvZiB0aGVpciBib3hlcy4gVGhvdWdoLCB3
aG8ga25vd3MgLSBtYXliZSB3ZSB3aWxsIGdldCBhc2tlZCB0byB1c2UgdGhpcyBleHRlbnNpb24g
b3V0c2lkZSBvZiBhdXRvY29uZmlnIGRlcGxveW1lbnRzLiANCg0KSXQgaXMgbmVjZXNzYXJ5IHRv
IGhhdmUgc3VjaCBhIG1lY2hhbmlzbSBpbiBhdXRvY29uZmlnIGRlcGxveW1lbnRzIHNpbmNlIHRo
ZXJlIGlzIC0gYnkgZGVmYXVsdCAtIG5vIG1hbnVhbCBpbnRlcnZlbnRpb24uIEJ1dCB0byBjaGFy
YWN0ZXJpemUgdGhpcyBhcyBhZGRpbmcgcmlzayBpcyBpbmNvcnJlY3QgSU1PLg0KDQogIExlcw0K
DQoNCj4gPiBTbyB5b3UgYXJlIGFza2luZyB1cyB0byByZXBlYXQgYSBkaXNjdXNzaW9uIHdoaWNo
IGhhcyBhbHJlYWR5IGJlZW4NCj4gPiBoZWxkIGluIHRoZSBjb250ZXh0IG9mIFJGQyA1MzA0IGFu
ZCBSRkMgNTMxMC4NCj4gPg0KPiA+IEl0IHdvdWxkIGJlIG1vcmUgYXBwcm9wcmlhdGUgdG8gYWRk
IHRoZSBub3JtYWwgcmVmZXJlbmNlIHRvIFJGQw0KPiA+IDUzMDQvNTMxMCBpbiB0aGUgU2VjdXJp
dHkgc2VjdGlvbiB0aGFuIHdoYXQgeW91IHByb3Bvc2UuDQo+IA0KPiBJIGRvbuKAmXQgdGhpbmsg
aXQgaHVydHMgdG8gYWRkIGEgcmVmZXJlbmNlIHRvIHRob3NlIFJGQ3MsIGJ1dCB0aGV5IGFyZSBi
b3RoDQo+IGFib3V0IGFkZGluZyBhdXRoZW50aWNhdGlvbiDigJMgdGhlIHByb2JsZW0gaW4gdGhp
cyBkb2N1bWVudCBpcyBleGFjZXJiYXRlZA0KPiBieSB0aGUgZmFjdCB0aGF0IHRoZXJl4oCZcyBu
byBhdXRoZW50aWNhdGlvbiBieSBkZWZhdWx0Lg0KPiANCj4gVGhlIGxvd2VyIGxheWVyIGF1dGhl
bnRpY2F0aW9uIG1lY2hhbmlzbXMgYXJlIHF1aXRlIHdlYWssIHNwZWNpYWxseQ0KPiBrbm93aW5n
IHRoYXQsIGlmIGluIGEgaG9tZSBlbnZpcm9ubWVudCwgZm9yIGV4YW1wbGUsIGl0IG1heSBiZSBy
ZWxhdGl2ZWx5DQo+IGVhc3kgdG8gY29ubmVjdCB0byB0aGUgV2lGaSBuZXR3b3JrLg0KPiANCj4g
QWx2YXJvLg0KPiANCg0K


From nobody Sat Apr  8 15:55:45 2017
Return-Path: <acee@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5A912714F; Sat,  8 Apr 2017 15:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.623
X-Spam-Level: 
X-Spam-Status: No, score=-12.623 tagged_above=-999 required=5 tests=[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 cXtyUZw2JLQz; Sat,  8 Apr 2017 15:55:40 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98F6F1250B8; Sat,  8 Apr 2017 15:55:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2806; q=dns/txt; s=iport; t=1491692140; x=1492901740; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=zkVtu0DpB2Azi2hOQXUF+XPu8DkbyNAYSk2OO6g01JI=; b=e2S1wqGEecRZhBbvHwIf0oWaumhFFzA91H4dQs4rGQwESOPZ62Qms7w4 c8iZlU5/GiTXxY+XfEDVjHWbGmPQpeksgIvleBU6UDnlfFkqt+I7bp6HA SzJXzf8Q8SHffB0mJwXUsNXHxscCPPs+QETtu7qWpyCwbR5+cPf+9+Mz3 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AUAQCfaelY/4ENJK1CGhkBAQEBAQEBA?= =?us-ascii?q?QEBAQcBAQEBAYNTYYELB41ykUCVV4IPLIV4AoNePxgBAgEBAQEBAQFrKIUWAQQ?= =?us-ascii?q?BeQULAgEIFDIyJQIEAQ0FCYl+CA4xqW+KXAEBAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?R2LQIJwgUIkhWUFkCuFdYZbAYZ/i1mBf4UuihSKNYlKAR84gQVbFYUdG4FjdQG?= =?us-ascii?q?Gb4EwgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,174,1488844800"; d="scan'208";a="409393167"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Apr 2017 22:55:39 +0000
Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v38MtdX4015015 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 8 Apr 2017 22:55:39 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 8 Apr 2017 18:55:35 -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; Sat, 8 Apr 2017 18:55:36 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-rtgwg-yang-key-chain.all@ietf.org" <draft-ietf-rtgwg-yang-key-chain.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
Thread-Index: AQHSr8ihxBldHKjCb0K6BYj9/alinKG8FuQA
Date: Sat, 8 Apr 2017 22:55:35 +0000
Message-ID: <D50ED999.A7F47%acee@cisco.com>
References: <149158793224.11224.1489071223626497682@ietfa.amsl.com>
In-Reply-To: <149158793224.11224.1489071223626497682@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.197]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <F3C8E32FD63BFD4A9794F21646ED72BA@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/SH_UNhLqPMKHJlti4PgxdpG8qI0>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Apr 2017 22:55:43 -0000

Hi Matt,

Thanks for the review.

On 4/7/17, 1:58 PM, "Matthew Miller" <linuxwolf+ietf@outer-planes.net>
wrote:

>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-rtgwg-yang-key-chain-17
>Reviewer: Matthew A. Miller
>Review Date: 2017-04-07
>IETF LC End Date: 2017-04-07
>IESG Telechat date: 2017-04-13
>
>Summary:
>
>This document is almost ready to be published as a Proposed Standard,
>once the issues noted herein are resolved.
>
>Major issues:
>
>NONE
>
>Minor issues:
>
>* Forgive me for my limited knowledge of YANG, but is there a reason
>key-strings are only representable as either a YANG string or
>hex-string type, and not the YANG binary type?

Let me ask why I=B9d want to use this type? I can get all the entropy I wan=
t
with a hex string and implementations are familiar with this
representation. I=B9m not really fond of the obscure base64 representation
used by the YANG type and if one consults Benoit=B9s search tool, the type
is not widely used. http://www.yangcatalog.org/yang-search/yang-search.php

>
>* This document does not provide much guidance around AES key wrap
>other than it can be used and the KEK is provided
>out-of-band/-context.
>For instance, AES key-wrapped key-strings probably require using
>"hexidecimal-string".

Yes - I=B9ll add that.

>  Also, assuming I'm reading the model
>correctly,
>it appears this feature applies to the whole chain, which I think is
>worth calling out.

In YANG, if you support a feature, it is for the entire model.
The per-chain boolean indicates whether or not it is applies to all the
keys in that particular key-chain. I will clarify this.
>
>* This document warns against using the "clear-text" algorithm, which
>the
>reader is lead to understand is for legacy implementation reasons.
>However, is there not a similar concern with cryptographically weak
>algorithms, such as md5 and (arguably) sha1?

I can add something for MD5.
>
>Nits/editorial comments:
>
>* In Section 3.2. "Key Chain Model Features", the word "of" is
>missing
>between "configuration" and "an" in the phrase "support configuration
>an
>acceptance tolerance".

Good catch. I will fix.
>
>Non-nits:
>
>* I note that idnits is calling out some odd spacing issues, but I
>think
>they are safe to ignore.

Though the line numbers don=B9t match the draft, I was able to fix these.

Thanks,
Acee=20
>


From nobody Sat Apr  8 16:23:08 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF787127A90; Sat,  8 Apr 2017 16:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.623
X-Spam-Level: 
X-Spam-Status: No, score=-12.623 tagged_above=-999 required=5 tests=[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 4UVmHQAUUMVV; Sat,  8 Apr 2017 16:23:06 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7DDC12420B; Sat,  8 Apr 2017 16:23:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5408; q=dns/txt; s=iport; t=1491693785; x=1492903385; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=8FK1GC9Lg27AK7zkXUbx56DPCoNvG7sqneG5+zvCszM=; b=BXdUYocZTmRG5YcrPkQ8Iu2kl5Pai5GeOvnIN1Enl/bAgMtlPmd4Id7W 2x0bw81tBSd8FnH9nCi+dkY0blQ17rOZuv64UZe4Y1ulCZMaerx/JkOo6 u2lYTqrs6dszRxcwPKb/u5Ob2mmoGUfLmwc76GqLKSn67jUuAcdeDBtrf 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AVAQBxcOlY/4ENJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1NhgQsHjXKRQJVXgg8shXgCg14/GAECAQEBAQEBAWsohRUBAQE?= =?us-ascii?q?BAgE6PwUHBAIBCBEDAQEBHwkHMhQJCAEBBAENBQiJfwgOqgWKXAEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAR2GUIRwhB2GHgEEiSqMdoZbAYZ/gyuIJYIIVYRZihSIY4s?= =?us-ascii?q?cAR84gQVbFUGEWxyBY3UBiB+BDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.37,175,1488844800"; d="scan'208";a="407745201"
Received: from alln-core-9.cisco.com ([173.36.13.129]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Apr 2017 23:23:04 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by alln-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v38NN4va029812 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 8 Apr 2017 23:23:04 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 8 Apr 2017 18:23:04 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Sat, 8 Apr 2017 18:23:03 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Orit Levin <oritl@microsoft.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-isis-mi-bis.all@tools.ietf.org" <draft-ietf-isis-mi-bis.all@tools.ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJABiHiqg
Date: Sat, 8 Apr 2017 23:23:03 +0000
Message-ID: <dc04ef63da5242d6a57386cb9d07b005@XCH-ALN-001.cisco.com>
References: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com>
In-Reply-To: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.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.24.67.234]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/O8qt9VUORvEl3bjHllSzhoxDP1c>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Apr 2017 23:23:08 -0000

Orit -

Thanx for the review.
Responses inline.

> -----Original Message-----
> From: Orit Levin [mailto:oritl@microsoft.com]
> Sent: Thursday, April 06, 2017 8:27 PM
> To: gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area Revie=
w
> Team (Gen-ART) reviews all IETF documents being processed by the IESG for
> the IETF Chair.  Please treat these comments just like any other last cal=
l
> comments.
>=20
> For more information, please see the FAQ at
>=20
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-isis-mi-bis-02
> Reviewer: Orit Levin
> Review Date: 2017-04-06
> IETF LC End Date: 2017-04-07
> IESG Telechat date: 2017-04-13
>=20
> Summary: This draft is "ready with issues" for publication.
>=20
> Major issues: None.
>=20
> Minor issues:
>=20
> 1. Add text explaining the reason (or reasons) for replacing the original=
 RFC
> 6822 from 2012.
> Reason: It is a "bis" draft and there is no mention about it in the text.

[Les:] Note that the latest revision of the draft correctly identifies the =
draft as obsoleting RFC 6822. Previous versions had incorrectly identified =
this as an update to RFC 6822.
This is then the new Standard for the IS-IS MI support.

There are two classes of future readers of this document:

a)Readers who are unfamiliar with RFC 6822. For them what changed between R=
FC 6822 and this document is irrelevant.=20

b)Readers who are familiar with RFC 6822. For them it is useful to know wha=
t changed - which is described in Appendix A.

In order not to distract readers of type "a" - as well as to provide an "un=
interrupted" description of the normative behavior I believe placement of t=
he change description in an Appendix improves the readability of the docume=
nt.

Does this make sense to you?

> 2. In Abstract, state clearly that this standard introduces the support f=
or
> instances vs. other already existing concepts also listed in the Abstract=
 (i.e.,
> circuits, adjacencies,  topologies, etc.).

[Les:] The Abstract currently says:

"This draft describes a mechanism that allows a single router to share
   one or more circuits among multiple Intermediate System To
   Intermediate System (IS-IS) routing protocol instances."

Previous to this extension, a router could have multiple instances of the I=
S-IS protocol, but multiple instance could not be run over the same interfa=
ce.=20
So we are not introducing "instances", but we are introducing the ability t=
o enable multiple instances on the same interface.

> Reason: The wording is not clear about what is the new feature vs. what a=
re
> the new benefits vs. what was the original baseline=20

>3. Throughout the
> document, use "standard instance" instead of "IID =3D 0" or "IID #0".
> Reason: Expressions "standard instance", "IID =3D 0" and "IID #0" are use=
d
> interchangeably throughout the document. It seems that they all refer to =
the
> same thing - the implementation of the original protocol without the conc=
ept
> of instances. Please, correct me if I am wrong.

[Les:]  I don't think this is possible without seriously compromising the d=
ocument. For example:

Section 2.1

" IID #0 is reserved for the standard instance supported by legacy
   systems. "

Changing this to  " Standard instance is reserved for the standard instance=
 ..."

Is clearly nonsensical.

Later in Section 2.1

"When the IID =3D 0, the list of supported ITIDs MUST NOT be present."

What is being discussed here is what is the correct behavior when an MI-cap=
able router sends a PDU associated IID #0 and includes the new IID TLV.=20
Replacing this with "When the standard instance..." loses the important poi=
nt that the value of the IID in the IID TLV in this case is "0".

Hope this helps clarify things.

> 4. In section 2 par 3, change "support" and "operates" to "MUST support" =
to
> use requirements language.

[Les:] I am on the fence as regards this change. Section 2 is an introducti=
on to the following sub-sections - which define the normative behavior. But=
 the introduction itself is not defining normative behavior - it is providi=
ng a context in which the protocol extensions defined in the following sub-=
sections can be understood.=20

I am more inclined to change the "MAY" used later in the same paragraph you=
 mention to "may" so it is consistent with the rest of this section.

???


> 5. In section 2 par 2, change "may" to either "can" or "MAY" to clarify t=
he
> intent.

[Les:] Did you mean Section 2.1 para 2?
If so I agree to the change.

> 6. In section 2.1 par 3, clarify whether IID #0 is ever being used on the=
 wire.

[Les:] There are numerous places in the document where the legal use of IID=
  #0 is discussed. I do not understand how a reader would conclude that IID=
 #0 is never sent on the wire.

> Explain the concept of the "standard interface" (see previous comment)

[Les:] There is no mention of "standard interface" - did you mean "standard=
 instance"?

If so, Section 1 paragraph 4 states:

"Legacy routers support the standard
   or zero instance of the protocol."

   Les


From nobody Sat Apr  8 22:57:05 2017
Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCB5129417; Sat,  8 Apr 2017 22:57:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Roni Even <ron.even.tlv@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-bess-evpn-vpws.all@ietf.org, ietf@ietf.org, bess@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149171742319.3063.4555090995663652452@ietfa.amsl.com>
Date: Sat, 08 Apr 2017 22:57:03 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/8inrwYfUOHs-0m605Z3iAKBj2OI>
Subject: [Gen-art] Genart telechat review of draft-ietf-bess-evpn-vpws-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 09 Apr 2017 05:57:03 -0000

Reviewer: Roni Even
Review result: Ready

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

For more information, please see the FAQ at

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

Document: draft-ietf-bess-evpn-vpws-??
Reviewer: Roni Even
Review Date: 2017-04-08
IETF LC End Date: 2017-03-10
IESG Telechat date: 2017-04-13

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

In section 1 second paragraph "[RFC7432] provides the ability " looks
like the reference is not a link to RFC7432.




From nobody Sun Apr  9 23:45:46 2017
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D74712786A for <gen-art@ietfa.amsl.com>; Sun,  9 Apr 2017 23:45:44 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Joi6jmO9q4E1 for <gen-art@ietfa.amsl.com>; Sun,  9 Apr 2017 23:45:43 -0700 (PDT)
Received: from usplmg21.ericsson.net (usplmg21.ericsson.net [198.24.6.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20A141272E1 for <gen-art@ietf.org>; Sun,  9 Apr 2017 23:45:42 -0700 (PDT)
X-AuditID: c6180641-417ff700000058cf-e1-58eae3b9425f
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by  (Symantec Mail Security) with SMTP id C9.53.22735.9B3EAE85; Mon, 10 Apr 2017 03:45:31 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0339.000; Mon, 10 Apr 2017 02:45:38 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-ietf-core-coap-tcp-tls.all@tools.ietf.org" <draft-ietf-core-coap-tcp-tls.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-core-coap-tcp-tls-07
Thread-Index: AdKxxgRKbG1uB6t+RkGgQFfE5vWQ3w==
Date: Mon, 10 Apr 2017 06:45:37 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A4F471630@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A4F471630eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyuXRPgu7ux68iDN5+sbJonfCZ1eLqq88s DkweS5b8ZPL4cvkzWwBTFJdNSmpOZllqkb5dAlfG/t//mQtWa1VMODmbtYHxv0oXIyeHhICJ xIvWpyxdjFwcQgIbGCW2Ht3FCuEsZ5S4cGUKI0gVm4CFxPbfz8ESIgKTGCVOP1nJBJIQFnCR uHrpHjuILSLgKbHmZhsThK0ncfTnQ1YQm0VAVWLL1r1gNbwCvhInlu9lA7EZBcQkvp9aA1bP LCAucevJfCaIkwQkluw5zwxhi0q8fPyPFcJWkvj4ez47RH2+xOYr71kgZgpKnJz5hGUCo+As JKNmISmbhaQMIq4jsWD3JzYIW1ti2cLXzDD2mQOPmZDFFzCyr2LkKC0uyMlNNzLcxAgM/GMS bI47GPf2eh5iFOBgVOLhTbB7FSHEmlhWXJl7iFGCg1lJhPeG9OsIId6UxMqq1KL8+KLSnNTi Q4zSHCxK4rzvyi9ECAmkJ5akZqemFqQWwWSZODilGhjn1E0zqBDYNoM5e8nFP4eq+S5wnM7Z kW254633Pvew1n1/xVTabsu6rjE9KDSJZ8rUbFufmfsWSK8wemi549PMD+vKffj690tE62gE TxbeGF3Opimn5//ygWfw12Bmu4nC0563KTyZaZRo0L662s3U8uXl5nXr/l0t9Zy8sGXDj+mc wk+7lNWVWIozEg21mIuKEwGOhRECeAIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/_Sf2TmiROGYL7pEFjE_h8Soh7IY>
Subject: [Gen-art] Gen-ART Last Call review of draft-ietf-core-coap-tcp-tls-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 06:45:44 -0000

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

I am the assigned Gen-ART reviewer for this draft. The General Area Review =
Team (Gen-ART) reviews all IETF documents being processed by the IESG for t=
he IETF Chair.  Please treat these comments just like any other last call c=
omments. For more information, please see the FAQ at <https://trac.ietf.org=
/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-core-coap-tcp-tls-07
Reviewer: Meral Shirazipour
Review Date: 2017-04-09
IETF LC End Date: 2017-04-09
IESG Telechat date: NA


Summary: This draft is ready to be published as Standards Track RFC but I s=
aw some issues.
Major issues:

Minor issues:
-I am not a CoAP expert, but list comments from Mark Nottingham are of conc=
ern (to [core] Mon, 10 April 2017 04:07 UTC).


Nits/editorial comments:
-Please spell out acronyms at first use.
-Not sure if other documents address this, but does this document assume fi=
xed CoAP devices as end point (not moving and connectivity is assumed 'the =
same' during the TCP session?)



Best Regards,
Meral
---
Meral Shirazipour
Ericsson
Research
www.ericsson.com

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I am the assigned Gen-ART reviewer for this draft. T=
he General Area Review Team (Gen-ART) reviews all IETF documents being proc=
essed by the IESG for the IETF Chair.&nbsp; Please treat these comments jus=
t like any other last call comments. For
 more information, please see the FAQ at &lt;https://trac.ietf.org/trac/gen=
/wiki/GenArtfaq&gt;.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Document: draft-ietf-core-coap-tcp-tls-07<o:p></o:p>=
</p>
<p class=3D"MsoNormal">Reviewer: Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Review Date: 2017-04-09<o:p></o:p></p>
<p class=3D"MsoNormal">IETF LC End Date: 2017-04-09<o:p></o:p></p>
<p class=3D"MsoNormal">IESG Telechat date: NA<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Summary: This draft is ready to be published as Stan=
dards Track RFC but I saw some issues.<o:p></o:p></p>
<p class=3D"MsoNormal">Major issues:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Minor issues:<o:p></o:p></p>
<p class=3D"MsoNormal">-I am not a CoAP expert, but list comments from Mark=
 Nottingham are of concern (to [core] Mon, 10 April 2017 04:07 UTC).<o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Nits/editorial comments: <o:p></o:p></p>
<p class=3D"MsoNormal">-Please spell out acronyms at first use.<o:p></o:p><=
/p>
<p class=3D"MsoNormal">-Not sure if other documents address this, but does =
this document assume fixed CoAP devices as end point (not moving and connec=
tivity is assumed 'the same' during the TCP session?)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best Regards,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal">---<o:p></o:p></p>
<p class=3D"MsoNormal">Meral Shirazipour<o:p></o:p></p>
<p class=3D"MsoNormal">Ericsson<o:p></o:p></p>
<p class=3D"MsoNormal">Research<o:p></o:p></p>
<p class=3D"MsoNormal">www.ericsson.com<o:p></o:p></p>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4F471630eusaamb107erics_--


From nobody Mon Apr 10 03:07:41 2017
Return-Path: <leo.liubing@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 94378129468; Mon, 10 Apr 2017 03:07:32 -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 96M4Ogqjai1J; Mon, 10 Apr 2017 03:07:29 -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 A3E5E129477; Mon, 10 Apr 2017 03:07:26 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml701-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DEL10452; Mon, 10 Apr 2017 10:07:22 +0000 (GMT)
Received: from NKGEML412-HUB.china.huawei.com (10.98.56.73) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 10 Apr 2017 11:07:21 +0100
Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.121]) by nkgeml412-hub.china.huawei.com ([10.98.56.73]) with mapi id 14.03.0235.001; Mon, 10 Apr 2017 18:07:11 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90I1Qr5MFU/1kyZBIn9T3xh16G53MgAgAAGPoCAAANtAIAABASAgAAQtoCABGROEA==
Date: Mon, 10 Apr 2017 10:07:10 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com>
In-Reply-To: <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.191.175]
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.0A090206.58EB595B.0077, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.121, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 9ea5c2356683d7cef74a5744d7b6aa9a
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/k7bUhGIEDVbV1l3iK3U-_9ODp5k>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 10:07:33 -0000

SGkgUm9iZXIsIEFsdmFybywgYW5kIExlcywNCg0KSW4gZ2VuZXJhbCwgdGhlIHVzZSBvZiBhdXRo
ZW50aWNhdGlvbiBpcyBpbmNvbXBhdGlibGUgd2l0aCBhdXRvLQ0KICAgY29uZmlndXJhdGlvbiBh
cyBpdCByZXF1aXJlcyBzb21lIG1hbnVhbCBjb25maWd1cmF0aW9uLg0KDQo+IC0tLS0tT3JpZ2lu
YWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IExlcyBHaW5zYmVyZyAoZ2luc2JlcmcpIFttYWlsdG86
Z2luc2JlcmdAY2lzY28uY29tXQ0KPiBTZW50OiBTYXR1cmRheSwgQXByaWwgMDgsIDIwMTcgNjo0
NCBBTQ0KPiBUbzogQWx2YXJvIFJldGFuYSAoYXJldGFuYSk7IFJvYmVydCBTcGFya3M7IGdlbi1h
cnRAaWV0Zi5vcmcNCj4gQ2M6IGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYuYWxsQGlldGYub3Jn
OyBpZXRmQGlldGYub3JnOyBpc2lzLXdnQGlldGYub3JnDQo+IFN1YmplY3Q6IFJFOiBHZW5hcnQg
bGFzdCBjYWxsIHJldmlldyBvZiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLTA0DQo+IA0KPiBB
bHZhcm8gLQ0KPiANCj4gTm90IHN1cmUgaG93IGxvbmcgd2Ugc2hvdWxkIGRlYmF0ZSB0aGlzIGFz
IHRoZSB0ZXh0IHlvdSBhcmUgYXNraW5nIGZvciBpcw0KPiBtb2Rlc3QgLSBidXQgb25lIG1vcmUg
YXR0ZW1wdCBvbiBteSBwYXJ0IC0gbm90IHNvIG11Y2ggdG8gZGViYXRlIHdoZXRoZXINCj4gdG8g
YWRkIHRleHQgb3Igbm90IC0gYnV0IHRvIGNvbWUgdG8gYSBjb21tb24gdW5kZXJzdGFuZGluZy4N
Cj4gDQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBBbHZhcm8gUmV0
YW5hIChhcmV0YW5hKQ0KPiA+IFNlbnQ6IEZyaWRheSwgQXByaWwgMDcsIDIwMTcgMjo0NSBQTQ0K
PiA+IFRvOiBMZXMgR2luc2JlcmcgKGdpbnNiZXJnKTsgUm9iZXJ0IFNwYXJrczsgZ2VuLWFydEBp
ZXRmLm9yZw0KPiA+IENjOiBkcmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLmFsbEBpZXRmLm9yZzsg
aWV0ZkBpZXRmLm9yZzsNCj4gPiBpc2lzLXdnQGlldGYub3JnDQo+ID4gU3ViamVjdDogUmU6IEdl
bmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYtMDQNCj4g
Pg0KPiA+IE9uIDQvNy8xNywgNTozMCBQTSwgIkxlcyBHaW5zYmVyZyAoZ2luc2JlcmcpIiA8Z2lu
c2JlcmdAY2lzY28uY29tPg0KPiB3cm90ZToNCj4gPg0KPiA+IExlczoNCj4gPg0KPiA+IEhpIQ0K
PiA+DQo+ID4gPiBTeXN0ZW0taWQgZHVwbGljYXRpb24gaXMgYSBwcm9ibGVtIGZvciBhbnkgZGVw
bG95bWVudCAtIG5vdCBqdXN0DQo+ID4gPiBhdXRvY29uZmlnIGRlcGxveW1lbnRzLiBBbmQgaXQg
d2lsbCBiZSBkaXNydXB0aXZlIGluIGFueSBuZXR3b3JrDQo+ID4gPiB1bnRpbCBpdCBpcw0KPiA+
IHJlc29sdmVkLg0KPiA+ID4NCj4gPiA+IFRoZSBvbmx5IHRoaW5nIGF1dG9jb25maWcgaGFzIGFk
ZGVkIGlzIGEgd2F5IHRvIHJlc29sdmUgdGhpcyB3L28NCj4gPiA+IG1hbnVhbCBpbnRlcnZlbnRp
b24uIFRoaXMgaW4gbm8gd2F5IGluY3JlYXNlcyB0aGUgdnVsbmVyYWJpbGl0eSBub3INCj4gPiA+
IHRoZSBkaXNydXB0aW9uIHRoZSBhdHRhY2tlciBjYW4gcHJvZHVjZS4gKFllcyAtIEkgc3RhdGUg
dGhhdCBxdWl0ZQ0KPiA+IGludGVudGlvbmFsbHkpLg0KPiA+DQo+ID4gSSBkb27igJl0IGtub3cg
YWJvdXQgUm9iZXJ0LCBidXQgdGhhdCBpcyBwYXJ0IG9mIHRoZSBkaXNjdXNzaW9uIEkgd291bGQN
Cj4gPiBsaWtlIHRvIHNlZS4NCj4gPg0KPiA+IFllcywgZHVwbGljYXRlIHN5c3RlbS1pZHMgaGF2
ZSBhbHdheXMgYmVlbiBhIHBvdGVudGlhbCBwcm9ibGVtLCBidXQNCj4gPiB0aGlzIGRvY3VtZW50
IGludHJvZHVjZXMgYSBuZXcgZGUtZHVwbGljYXRpb24gbWVjaGFuaXNtIHRoYXQgcmVzdWx0cw0K
PiA+IG5vdCBqdXN0IGluIHVuc3luY+KAmWQgZGF0YWJhc2VzLCBidXQgaW4gcmVzdGFydGluZyBh
ZGphY2VuY2llcyDigJMgc28gYXQNCj4gPiBsZWFzdCB0aGUgbWFuaWZlc3RhdGlvbiBvZiB0aGUg
cHJvYmxlbSBpcyBkaWZmZXJlbnQuDQo+ID4NCj4gW0xlczpdIFRoZSAicHJvYmxlbSIgZXhpc3Rz
IGFzIGxvbmcgYXMgdGhlIGR1cGxpY2F0ZSBzeXN0ZW0taWRzIGV4aXN0LiBUaGUNCj4gcmVjb3Zl
cnkgbWVjaGFuaXNtIGRvZXMgbm90IGludHJvZHVjZSBuZXcgcHJvYmxlbXMgLSBpdCBhY3R1YWxs
eSBhY3RzIHRvDQo+IG1pbmltaXplIHRoZSBkdXJhdGlvbiBvZiB0aGUgcHJvYmxlbS4gT25lIGNv
dWxkIGFyZ3VlIChhbmQgSSBhbSBOT1QgZG9pbmcNCj4gc28pIHRoYXQgYXV0b21hdGVkIHJlc29s
dXRpb24gY291bGQgYmUgYSBiZW5lZml0IGluIGFsbCBkZXBsb3ltZW50cy4gSSB0aGluaw0KPiB0
aGUgaXNzdWUgaW4gbm9uLWF1dG9jb25maWcgZGVwbG95bWVudHMgaXMgdGhhdCBzaW5jZSBzeXN0
ZW1zIGhhdmUgYmVlbg0KPiBtYW51YWxseSBwcm92aXNpb25lZCB3ZSBjYW5ub3QgYXNzdW1lIHRo
YXQgbmV0d29yayBvcGVyYXRvcnMgd2FudCB1cyB0bw0KPiBhdXRvbWF0aWNhbGx5IGNoYW5nZSB0
aGUgY29uZmlnIG9uIG9uZSBvZiB0aGVpciBib3hlcy4gVGhvdWdoLCB3aG8ga25vd3MgLQ0KPiBt
YXliZSB3ZSB3aWxsIGdldCBhc2tlZCB0byB1c2UgdGhpcyBleHRlbnNpb24gb3V0c2lkZSBvZiBh
dXRvY29uZmlnDQo+IGRlcGxveW1lbnRzLg0KPiANCj4gSXQgaXMgbmVjZXNzYXJ5IHRvIGhhdmUg
c3VjaCBhIG1lY2hhbmlzbSBpbiBhdXRvY29uZmlnIGRlcGxveW1lbnRzIHNpbmNlDQo+IHRoZXJl
IGlzIC0gYnkgZGVmYXVsdCAtIG5vIG1hbnVhbCBpbnRlcnZlbnRpb24uIEJ1dCB0byBjaGFyYWN0
ZXJpemUgdGhpcyBhcw0KPiBhZGRpbmcgcmlzayBpcyBpbmNvcnJlY3QgSU1PLg0KDQpbQmluZ10g
SSBhZ3JlZSB3aXRoIExlcyB0aGF0IHN5cy1pZCBkdXBsaWNhdGlvbiBhdHRhY2sgaXMgbm90IGFu
ICJhZGRpbmciIHJpc2suIA0KQnV0IG1heWJlIHdlIGNvdWxkIGFkZCBhIGJpdCBtb3JlIHRleHQg
dG8gZXhwbGFpbiB3aHkgdGhpcyBkb2N1bWVudCBSRUNPTU1ORUQgdG8gaW1wbGVtZW50IEF1dGgg
VExWLg0KDQpQcm9wb3NlZCBhZGRlZCB0ZXh0IGluIDMuNS4xIChBdXRoZW50aWNhdGlvbiBUTFYp
IGFzIGJlbG93Og0KIlRoZSB1c2Ugb2YgYXV0aGVudGljYXRpb24gaXMgaW5jb21wYXRpYmxlIHdp
dGggYXV0by1jb25maWd1cmF0aW9uIGFzIGl0IHJlcXVpcmVzIHNvbWUgbWFudWFsIGNvbmZpZ3Vy
YXRpb24uIEhvd2V2ZXIsIHRoZXJlIG1pZ2h0IGJlIHNvbWUgdXNlcnMgd291bGQgbGlrZSB0byBw
YXkgdGhlIGVmZm9ydCBvZiBtYW51YWwgY29uZmlndXJhdGlvbiB0byBtaXRpZ2F0ZSBzb21lIHNl
Y3VyaXR5IGF0dGFjayAoZS5nLiBhIG1hbGljaW91cyBub2RlIGNyYWZ0cyBwYWNrZXQgdG8gaW50
ZW50aW9uYWxseSBjYXVzZSB0aGUgU3lzLUlEIGR1cGxpY2F0aW9uIHByb2NlZHVyZSBjb250aW51
b3VzbHkpLiANClRodXMsIGl0IGlzIFJFQ09NTUVORUQgdGhhdCBJUy1JUy4uLiAodGhlIHNhbWUg
YXMgZXhpc3RpbmcgdGV4dCkuDQoNCkRvIHlvdSB0aGluayBpdCdzIE9LPw0KDQpCZXN0IHJlZ2Fy
ZHMsDQpCaW5nDQoNCg0KPiAgIExlcw0KPiANCj4gDQo+ID4gPiBTbyB5b3UgYXJlIGFza2luZyB1
cyB0byByZXBlYXQgYSBkaXNjdXNzaW9uIHdoaWNoIGhhcyBhbHJlYWR5IGJlZW4NCj4gPiA+IGhl
bGQgaW4gdGhlIGNvbnRleHQgb2YgUkZDIDUzMDQgYW5kIFJGQyA1MzEwLg0KPiA+ID4NCj4gPiA+
IEl0IHdvdWxkIGJlIG1vcmUgYXBwcm9wcmlhdGUgdG8gYWRkIHRoZSBub3JtYWwgcmVmZXJlbmNl
IHRvIFJGQw0KPiA+ID4gNTMwNC81MzEwIGluIHRoZSBTZWN1cml0eSBzZWN0aW9uIHRoYW4gd2hh
dCB5b3UgcHJvcG9zZS4NCj4gPg0KPiA+IEkgZG9u4oCZdCB0aGluayBpdCBodXJ0cyB0byBhZGQg
YSByZWZlcmVuY2UgdG8gdGhvc2UgUkZDcywgYnV0IHRoZXkgYXJlDQo+ID4gYm90aCBhYm91dCBh
ZGRpbmcgYXV0aGVudGljYXRpb24g4oCTIHRoZSBwcm9ibGVtIGluIHRoaXMgZG9jdW1lbnQgaXMN
Cj4gPiBleGFjZXJiYXRlZCBieSB0aGUgZmFjdCB0aGF0IHRoZXJl4oCZcyBubyBhdXRoZW50aWNh
dGlvbiBieSBkZWZhdWx0Lg0KPiA+DQo+ID4gVGhlIGxvd2VyIGxheWVyIGF1dGhlbnRpY2F0aW9u
IG1lY2hhbmlzbXMgYXJlIHF1aXRlIHdlYWssIHNwZWNpYWxseQ0KPiA+IGtub3dpbmcgdGhhdCwg
aWYgaW4gYSBob21lIGVudmlyb25tZW50LCBmb3IgZXhhbXBsZSwgaXQgbWF5IGJlDQo+ID4gcmVs
YXRpdmVseSBlYXN5IHRvIGNvbm5lY3QgdG8gdGhlIFdpRmkgbmV0d29yay4NCj4gPg0KPiA+IEFs
dmFyby4NCj4gPg0KDQo=


From nobody Mon Apr 10 07:16:28 2017
Return-Path: <aretana@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5EF53129490; Mon, 10 Apr 2017 07:16:20 -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 tMM-UZAi4tUL; Mon, 10 Apr 2017 07:16:19 -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 F10A4120046; Mon, 10 Apr 2017 07:16:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4570; q=dns/txt; s=iport; t=1491833779; x=1493043379; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=EGQwcp4QM1rFNIujrx+RuG12lA7XCiJQMGZR87lV+Nw=; b=lUfmynmkorf05IpOLxFePHga4fht6zG+AUYkiK5DhyeW8WovkUoJsedT xZG12Ht0Gx8KDLhrp1/Nd5Bg9ErulKjZ0Fd2reHNRjJo6VU2ORGf77ehz YcsZHj2mrzOYV+UTajJ+IX6+cCElcLMfQHQm32ZDf4IHjG5tcGnJr9xCv Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DGAQC+kutY/5xdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgygrgWwHg1+KE5FGlVeCD4YkAhqDQj8YAQIBAQEBAQEBayiFFQE?= =?us-ascii?q?BAQECASMRRQwEAgEIEQQBAQECAiYCAgIwFQgIAgQBDQWKBwipEoImimMBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEdgQuFRYIFgmuEVoMGLoIxAQSWIIZbAZJYkUGTfwE?= =?us-ascii?q?fOIEFWxVSAYZIdYhSgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,182,1488844800"; d="scan'208";a="228984776"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Apr 2017 14:16:18 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v3AEGHUM014097 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 10 Apr 2017 14:16:18 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 10 Apr 2017 09:16:17 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Mon, 10 Apr 2017 09:16:17 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90HdNwrO1bKAUiTTjwvgN+2naG6trYAgAAGPoCAAANsAP//wPeAgABTw4CAA+X3AA==
Date: Mon, 10 Apr 2017 14:16:17 +0000
Message-ID: <624A5B5B-6BCA-4FA0-A344-42AAE3A57F15@cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com>
In-Reply-To: <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.6]
Content-Type: text/plain; charset="utf-8"
Content-ID: <71EA5EFDB308D34ABDDCECFD2184C4F9@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/PBqaBo1Z2ZSrizH6ayZxjnb-5jw>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 14:16:20 -0000

TGVzOg0KDQpIaSENCg0KVGhlIHJpc2sgaXMgbm90IGluIHRoZSBtZWNoYW5pc20gaXRzZWxmLCBh
c3N1bWluZyB0d28gcm91dGVycyB3aXRoIHRoZSBjb3JyZWN0IGltcGxlbWVudGF0aW9uLg0KDQpU
aGUgcmlzayBpcyBpbiB0aGUgZmFjdCB0aGF0IGEgY29tcHJvbWlzZWQgcm91dGVyIGNhbiBjcmFm
dCBhIHBhY2tldCB0byBmb3JjZSB0aGUgYXV0by1jb25maWcgcm91dGVycyB0byBjb250aW51b3Vz
bHkgcmVzdGFydC4gICBBbGwgd2XigJlyZSBhc2tpbmcgZm9yIGlzIGEgcmVjb2duaXRpb24gdGhh
dCB0aGUgcmlzayBleGlzdHMuDQoNClRoYW5rcyENCg0KQWx2YXJvLg0KDQoNCg0KDQpPbiA0Lzcv
MTcsIDY6NDQgUE0sICJMZXMgR2luc2JlcmcgKGdpbnNiZXJnKSIgPGdpbnNiZXJnQGNpc2NvLmNv
bT4gd3JvdGU6DQoNCkFsdmFybyAtDQoNCk5vdCBzdXJlIGhvdyBsb25nIHdlIHNob3VsZCBkZWJh
dGUgdGhpcyBhcyB0aGUgdGV4dCB5b3UgYXJlIGFza2luZyBmb3IgaXMgbW9kZXN0IC0gYnV0IG9u
ZSBtb3JlIGF0dGVtcHQgb24gbXkgcGFydCAtIG5vdCBzbyBtdWNoIHRvIGRlYmF0ZSB3aGV0aGVy
IHRvIGFkZCB0ZXh0IG9yIG5vdCAtIGJ1dCB0byBjb21lIHRvIGEgY29tbW9uIHVuZGVyc3RhbmRp
bmcuDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogQWx2YXJvIFJldGFu
YSAoYXJldGFuYSkNCj4gU2VudDogRnJpZGF5LCBBcHJpbCAwNywgMjAxNyAyOjQ1IFBNDQo+IFRv
OiBMZXMgR2luc2JlcmcgKGdpbnNiZXJnKTsgUm9iZXJ0IFNwYXJrczsgZ2VuLWFydEBpZXRmLm9y
Zw0KPiBDYzogZHJhZnQtaWV0Zi1pc2lzLWF1dG8tY29uZi5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0
Zi5vcmc7IGlzaXMtd2dAaWV0Zi5vcmcNCj4gU3ViamVjdDogUmU6IEdlbmFydCBsYXN0IGNhbGwg
cmV2aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYtMDQNCj4gDQo+IE9uIDQvNy8xNywg
NTozMCBQTSwgIkxlcyBHaW5zYmVyZyAoZ2luc2JlcmcpIiA8Z2luc2JlcmdAY2lzY28uY29tPiB3
cm90ZToNCj4gDQo+IExlczoNCj4gDQo+IEhpIQ0KPiANCj4gPiBTeXN0ZW0taWQgZHVwbGljYXRp
b24gaXMgYSBwcm9ibGVtIGZvciBhbnkgZGVwbG95bWVudCAtIG5vdCBqdXN0DQo+ID4gYXV0b2Nv
bmZpZyBkZXBsb3ltZW50cy4gQW5kIGl0IHdpbGwgYmUgZGlzcnVwdGl2ZSBpbiBhbnkgbmV0d29y
ayB1bnRpbCBpdCBpcw0KPiByZXNvbHZlZC4NCj4gPg0KPiA+IFRoZSBvbmx5IHRoaW5nIGF1dG9j
b25maWcgaGFzIGFkZGVkIGlzIGEgd2F5IHRvIHJlc29sdmUgdGhpcyB3L28NCj4gPiBtYW51YWwg
aW50ZXJ2ZW50aW9uLiBUaGlzIGluIG5vIHdheSBpbmNyZWFzZXMgdGhlIHZ1bG5lcmFiaWxpdHkg
bm9yDQo+ID4gdGhlIGRpc3J1cHRpb24gdGhlIGF0dGFja2VyIGNhbiBwcm9kdWNlLiAoWWVzIC0g
SSBzdGF0ZSB0aGF0IHF1aXRlDQo+IGludGVudGlvbmFsbHkpLg0KPiANCj4gSSBkb27igJl0IGtu
b3cgYWJvdXQgUm9iZXJ0LCBidXQgdGhhdCBpcyBwYXJ0IG9mIHRoZSBkaXNjdXNzaW9uIEkgd291
bGQgbGlrZSB0bw0KPiBzZWUuDQo+IA0KPiBZZXMsIGR1cGxpY2F0ZSBzeXN0ZW0taWRzIGhhdmUg
YWx3YXlzIGJlZW4gYSBwb3RlbnRpYWwgcHJvYmxlbSwgYnV0IHRoaXMNCj4gZG9jdW1lbnQgaW50
cm9kdWNlcyBhIG5ldyBkZS1kdXBsaWNhdGlvbiBtZWNoYW5pc20gdGhhdCByZXN1bHRzIG5vdCBq
dXN0DQo+IGluIHVuc3luY+KAmWQgZGF0YWJhc2VzLCBidXQgaW4gcmVzdGFydGluZyBhZGphY2Vu
Y2llcyDigJMgc28gYXQgbGVhc3QgdGhlDQo+IG1hbmlmZXN0YXRpb24gb2YgdGhlIHByb2JsZW0g
aXMgZGlmZmVyZW50Lg0KPiANCltMZXM6XSBUaGUgInByb2JsZW0iIGV4aXN0cyBhcyBsb25nIGFz
IHRoZSBkdXBsaWNhdGUgc3lzdGVtLWlkcyBleGlzdC4gVGhlIHJlY292ZXJ5IG1lY2hhbmlzbSBk
b2VzIG5vdCBpbnRyb2R1Y2UgbmV3IHByb2JsZW1zIC0gaXQgYWN0dWFsbHkgYWN0cyB0byBtaW5p
bWl6ZSB0aGUgZHVyYXRpb24gb2YgdGhlIHByb2JsZW0uIE9uZSBjb3VsZCBhcmd1ZSAoYW5kIEkg
YW0gTk9UIGRvaW5nIHNvKSB0aGF0IGF1dG9tYXRlZCByZXNvbHV0aW9uIGNvdWxkIGJlIGEgYmVu
ZWZpdCBpbiBhbGwgZGVwbG95bWVudHMuIEkgdGhpbmsgdGhlIGlzc3VlIGluIG5vbi1hdXRvY29u
ZmlnIGRlcGxveW1lbnRzIGlzIHRoYXQgc2luY2Ugc3lzdGVtcyBoYXZlIGJlZW4gbWFudWFsbHkg
cHJvdmlzaW9uZWQgd2UgY2Fubm90IGFzc3VtZSB0aGF0IG5ldHdvcmsgb3BlcmF0b3JzIHdhbnQg
dXMgdG8gYXV0b21hdGljYWxseSBjaGFuZ2UgdGhlIGNvbmZpZyBvbiBvbmUgb2YgdGhlaXIgYm94
ZXMuIFRob3VnaCwgd2hvIGtub3dzIC0gbWF5YmUgd2Ugd2lsbCBnZXQgYXNrZWQgdG8gdXNlIHRo
aXMgZXh0ZW5zaW9uIG91dHNpZGUgb2YgYXV0b2NvbmZpZyBkZXBsb3ltZW50cy4gDQoNCkl0IGlz
IG5lY2Vzc2FyeSB0byBoYXZlIHN1Y2ggYSBtZWNoYW5pc20gaW4gYXV0b2NvbmZpZyBkZXBsb3lt
ZW50cyBzaW5jZSB0aGVyZSBpcyAtIGJ5IGRlZmF1bHQgLSBubyBtYW51YWwgaW50ZXJ2ZW50aW9u
LiBCdXQgdG8gY2hhcmFjdGVyaXplIHRoaXMgYXMgYWRkaW5nIHJpc2sgaXMgaW5jb3JyZWN0IElN
Ty4NCg0KICBMZXMNCg0KDQo+ID4gU28geW91IGFyZSBhc2tpbmcgdXMgdG8gcmVwZWF0IGEgZGlz
Y3Vzc2lvbiB3aGljaCBoYXMgYWxyZWFkeSBiZWVuDQo+ID4gaGVsZCBpbiB0aGUgY29udGV4dCBv
ZiBSRkMgNTMwNCBhbmQgUkZDIDUzMTAuDQo+ID4NCj4gPiBJdCB3b3VsZCBiZSBtb3JlIGFwcHJv
cHJpYXRlIHRvIGFkZCB0aGUgbm9ybWFsIHJlZmVyZW5jZSB0byBSRkMNCj4gPiA1MzA0LzUzMTAg
aW4gdGhlIFNlY3VyaXR5IHNlY3Rpb24gdGhhbiB3aGF0IHlvdSBwcm9wb3NlLg0KPiANCj4gSSBk
b27igJl0IHRoaW5rIGl0IGh1cnRzIHRvIGFkZCBhIHJlZmVyZW5jZSB0byB0aG9zZSBSRkNzLCBi
dXQgdGhleSBhcmUgYm90aA0KPiBhYm91dCBhZGRpbmcgYXV0aGVudGljYXRpb24g4oCTIHRoZSBw
cm9ibGVtIGluIHRoaXMgZG9jdW1lbnQgaXMgZXhhY2VyYmF0ZWQNCj4gYnkgdGhlIGZhY3QgdGhh
dCB0aGVyZeKAmXMgbm8gYXV0aGVudGljYXRpb24gYnkgZGVmYXVsdC4NCj4gDQo+IFRoZSBsb3dl
ciBsYXllciBhdXRoZW50aWNhdGlvbiBtZWNoYW5pc21zIGFyZSBxdWl0ZSB3ZWFrLCBzcGVjaWFs
bHkNCj4ga25vd2luZyB0aGF0LCBpZiBpbiBhIGhvbWUgZW52aXJvbm1lbnQsIGZvciBleGFtcGxl
LCBpdCBtYXkgYmUgcmVsYXRpdmVseQ0KPiBlYXN5IHRvIGNvbm5lY3QgdG8gdGhlIFdpRmkgbmV0
d29yay4NCj4gDQo+IEFsdmFyby4NCj4gDQoNCg0KDQo=


From nobody Mon Apr 10 07:34:26 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783B4129517; Mon, 10 Apr 2017 07:34:24 -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 W5WtRQmjywyn; Mon, 10 Apr 2017 07:34:23 -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 7B5EE1294FF; Mon, 10 Apr 2017 07:34:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8618; q=dns/txt; s=iport; t=1491834862; x=1493044462; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=vstBV/U16TJ6DMdvjG3CEx/IpzoXE6F+oszkcq3mfXY=; b=D0Q2ZqZEQvqKqEaIJ7c139GyHW0T4w0iWmKZsDvwr7/CqG0HbEMMiah5 QTZejN0IC6WJk8L5csblhgOtzMYDF+UerYWPVVrMUGmowij3h+X60cD/y d4+/6fhgA3W38PFVJRCZhGmkgNeSY6kbhErrLaCUm+MJtrBAcOXAK2kWc c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DGAQDClutY/4cNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1OBbAeDX4oTkUaVV4IPhiQCGoNFPxgBAgEBAQEBAQFrKIUVAQE?= =?us-ascii?q?BAQIBIxFFBQcEAgEIEQQBAQECAiMDAgICMBQBCAgCBAENBQiJfwipEIImimMBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBAQEdgQuFRYRwh1yCXwWcewGST5FKk38BHzhKO1s?= =?us-ascii?q?Vhxt1iFKBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.37,182,1488844800"; d="scan'208";a="13171601"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 10 Apr 2017 14:34:21 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v3AEYLcJ001665 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 10 Apr 2017 14:34:21 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 10 Apr 2017 09:34:20 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Mon, 10 Apr 2017 09:34:20 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Liubing (Leo)" <leo.liubing@huawei.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90H4gcf2S4v0ECj7j9mrpM816G6YX4QgABbdoD//63TkIAAWZ6A//+58rCABDovAP//9BHw
Date: Mon, 10 Apr 2017 14:34:20 +0000
Message-ID: <c3a3a16110cb44c182413d993377de6d@XCH-ALN-001.cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com>
In-Reply-To: <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.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.24.67.234]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/m5egoVWGjgDS4LAJZSO9pBtwZvU>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 14:34:24 -0000

QmluZy9Sb2JlcnQvQWx2YXJvIC0NCg0KSGVyZSBpcyB0aGUgZXhpc3RpbmcgdGV4dCBvZiB0aGUg
U2VjdXJpdHkgU2VjdGlvbjoNCg0KICAiSW4gZ2VuZXJhbCwgdGhlIHVzZSBvZiBhdXRoZW50aWNh
dGlvbiBpcyBpbmNvbXBhdGlibGUgd2l0aCBhdXRvLQ0KICAgY29uZmlndXJhdGlvbiBhcyBpdCBy
ZXF1aXJlcyBzb21lIG1hbnVhbCBjb25maWd1cmF0aW9uLg0KDQogICBGb3Igd2lyZWQgZGVwbG95
bWVudCwgdGhlIHdpcmVkIGNvbm5lY3Rpb24gaXRzZWxmIGNvdWxkIGJlIGNvbnNpZGVyZWQNCiAg
IGFzIGFuIGltcGxpY2l0IGF1dGhlbnRpY2F0aW9uIGluIHRoYXQgdW53YW50ZWQgcm91dGVycyBh
cmUgdXN1YWxseQ0KICAgbm90IGFibGUgdG8gY29ubmVjdCAoaS5lLiB0aGVyZSBpcyBzb21lIGtp
bmQgb2YgcGh5c2ljYWwgc2VjdXJpdHkgaW4NCiAgIHBsYWNlIHByZXZlbnRpbmcgdGhlIGNvbm5l
Y3Rpb24gb2Ygcm9ndWUgZGV2aWNlcyk7IGZvciB3aXJlbGVzcw0KICAgZGVwbG95bWVudCwgdGhl
IGF1dGhlbnRpY2F0aW9uIGNvdWxkIGJlIGFjaGlldmVkIGF0IHRoZSBsb3dlcg0KICAgd2lyZWxl
c3MgbGluayBsYXllci4iDQoNCg0KUHJvcG9zZWQgcmV2aXNpb246DQoNCiJJbiB0aGUgYWJzZW5j
ZSBvZiBjcnlwdG9ncmFwaGljIGF1dGhlbnRpY2F0aW9uIGl0IGlzIHBvc3NpYmxlIGZvciBhbiBh
dHRhY2tlciB0byBpbmplY3QgIGEgUERVIGZhbHNlbHkgaW5kaWNhdGluZw0KIHRoZXJlIGlzIGEg
ZHVwbGljYXRlIHN5c3RlbS1pZC4gVGhpcyBtYXkgdHJpZ2dlciBhdXRvbWF0aWMgcmVzdGFydCBv
ZiB0aGUgcHJvdG9jb2wgdXNpbmcgdGhlIGR1cGxpY2F0ZS1pZA0KcmVzb2x1dGlvbiBwcm9jZWR1
cmVzIGRlZmluZWQgaW4gdGhpcyBkb2N1bWVudC4gDQoNCk5vdGUgdGhhdCB0aGUgdXNlIG9mIGF1
dGhlbnRpY2F0aW9uIGlzIGluY29tcGF0aWJsZSB3aXRoIGF1dG8tDQpjb25maWd1cmF0aW9uIGFz
IGl0IHJlcXVpcmVzIHNvbWUgbWFudWFsIGNvbmZpZ3VyYXRpb24uDQoNCiAgIEZvciB3aXJlZCBk
ZXBsb3ltZW50LCB0aGUgd2lyZWQgY29ubmVjdGlvbiBpdHNlbGYgY291bGQgYmUgY29uc2lkZXJl
ZA0KICAgYXMgYW4gaW1wbGljaXQgYXV0aGVudGljYXRpb24gaW4gdGhhdCB1bndhbnRlZCByb3V0
ZXJzIGFyZSB1c3VhbGx5DQogICBub3QgYWJsZSB0byBjb25uZWN0IChpLmUuIHRoZXJlIGlzIHNv
bWUga2luZCBvZiBwaHlzaWNhbCBzZWN1cml0eSBpbg0KICAgcGxhY2UgcHJldmVudGluZyB0aGUg
Y29ubmVjdGlvbiBvZiByb2d1ZSBkZXZpY2VzKTsgZm9yIHdpcmVsZXNzDQogICBkZXBsb3ltZW50
LCB0aGUgYXV0aGVudGljYXRpb24gY291bGQgYmUgYWNoaWV2ZWQgYXQgdGhlIGxvd2VyDQogICB3
aXJlbGVzcyBsaW5rIGxheWVyLiINCg0KPz8/DQoNCiAgIExlcw0KDQoNCj4gLS0tLS1PcmlnaW5h
bCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogTGl1YmluZyAoTGVvKSBbbWFpbHRvOmxlby5saXViaW5n
QGh1YXdlaS5jb21dDQo+IFNlbnQ6IE1vbmRheSwgQXByaWwgMTAsIDIwMTcgMzowNyBBTQ0KPiBU
bzogTGVzIEdpbnNiZXJnIChnaW5zYmVyZyk7IEFsdmFybyBSZXRhbmEgKGFyZXRhbmEpOyBSb2Jl
cnQgU3BhcmtzOyBnZW4tDQo+IGFydEBpZXRmLm9yZw0KPiBDYzogZHJhZnQtaWV0Zi1pc2lzLWF1
dG8tY29uZi5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7IGlzaXMtd2dAaWV0Zi5vcmcNCj4g
U3ViamVjdDogUkU6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1h
dXRvLWNvbmYtMDQNCj4gDQo+IEhpIFJvYmVyLCBBbHZhcm8sIGFuZCBMZXMsDQo+IA0KPiBJbiBn
ZW5lcmFsLCB0aGUgdXNlIG9mIGF1dGhlbnRpY2F0aW9uIGlzIGluY29tcGF0aWJsZSB3aXRoIGF1
dG8tDQo+ICAgIGNvbmZpZ3VyYXRpb24gYXMgaXQgcmVxdWlyZXMgc29tZSBtYW51YWwgY29uZmln
dXJhdGlvbi4NCj4gDQo+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiBGcm9tOiBM
ZXMgR2luc2JlcmcgKGdpbnNiZXJnKSBbbWFpbHRvOmdpbnNiZXJnQGNpc2NvLmNvbV0NCj4gPiBT
ZW50OiBTYXR1cmRheSwgQXByaWwgMDgsIDIwMTcgNjo0NCBBTQ0KPiA+IFRvOiBBbHZhcm8gUmV0
YW5hIChhcmV0YW5hKTsgUm9iZXJ0IFNwYXJrczsgZ2VuLWFydEBpZXRmLm9yZw0KPiA+IENjOiBk
cmFmdC1pZXRmLWlzaXMtYXV0by1jb25mLmFsbEBpZXRmLm9yZzsgaWV0ZkBpZXRmLm9yZzsNCj4g
PiBpc2lzLXdnQGlldGYub3JnDQo+ID4gU3ViamVjdDogUkU6IEdlbmFydCBsYXN0IGNhbGwgcmV2
aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYtMDQNCj4gPg0KPiA+IEFsdmFybyAtDQo+
ID4NCj4gPiBOb3Qgc3VyZSBob3cgbG9uZyB3ZSBzaG91bGQgZGViYXRlIHRoaXMgYXMgdGhlIHRl
eHQgeW91IGFyZSBhc2tpbmcgZm9yDQo+ID4gaXMgbW9kZXN0IC0gYnV0IG9uZSBtb3JlIGF0dGVt
cHQgb24gbXkgcGFydCAtIG5vdCBzbyBtdWNoIHRvIGRlYmF0ZQ0KPiA+IHdoZXRoZXIgdG8gYWRk
IHRleHQgb3Igbm90IC0gYnV0IHRvIGNvbWUgdG8gYSBjb21tb24gdW5kZXJzdGFuZGluZy4NCj4g
Pg0KPiA+ID4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gPiA+IEZyb206IEFsdmFybyBS
ZXRhbmEgKGFyZXRhbmEpDQo+ID4gPiBTZW50OiBGcmlkYXksIEFwcmlsIDA3LCAyMDE3IDI6NDUg
UE0NCj4gPiA+IFRvOiBMZXMgR2luc2JlcmcgKGdpbnNiZXJnKTsgUm9iZXJ0IFNwYXJrczsgZ2Vu
LWFydEBpZXRmLm9yZw0KPiA+ID4gQ2M6IGRyYWZ0LWlldGYtaXNpcy1hdXRvLWNvbmYuYWxsQGll
dGYub3JnOyBpZXRmQGlldGYub3JnOw0KPiA+ID4gaXNpcy13Z0BpZXRmLm9yZw0KPiA+ID4gU3Vi
amVjdDogUmU6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYtaXNpcy1hdXRv
LWNvbmYtMDQNCj4gPiA+DQo+ID4gPiBPbiA0LzcvMTcsIDU6MzAgUE0sICJMZXMgR2luc2Jlcmcg
KGdpbnNiZXJnKSIgPGdpbnNiZXJnQGNpc2NvLmNvbT4NCj4gPiB3cm90ZToNCj4gPiA+DQo+ID4g
PiBMZXM6DQo+ID4gPg0KPiA+ID4gSGkhDQo+ID4gPg0KPiA+ID4gPiBTeXN0ZW0taWQgZHVwbGlj
YXRpb24gaXMgYSBwcm9ibGVtIGZvciBhbnkgZGVwbG95bWVudCAtIG5vdCBqdXN0DQo+ID4gPiA+
IGF1dG9jb25maWcgZGVwbG95bWVudHMuIEFuZCBpdCB3aWxsIGJlIGRpc3J1cHRpdmUgaW4gYW55
IG5ldHdvcmsNCj4gPiA+ID4gdW50aWwgaXQgaXMNCj4gPiA+IHJlc29sdmVkLg0KPiA+ID4gPg0K
PiA+ID4gPiBUaGUgb25seSB0aGluZyBhdXRvY29uZmlnIGhhcyBhZGRlZCBpcyBhIHdheSB0byBy
ZXNvbHZlIHRoaXMgdy9vDQo+ID4gPiA+IG1hbnVhbCBpbnRlcnZlbnRpb24uIFRoaXMgaW4gbm8g
d2F5IGluY3JlYXNlcyB0aGUgdnVsbmVyYWJpbGl0eQ0KPiA+ID4gPiBub3IgdGhlIGRpc3J1cHRp
b24gdGhlIGF0dGFja2VyIGNhbiBwcm9kdWNlLiAoWWVzIC0gSSBzdGF0ZSB0aGF0DQo+ID4gPiA+
IHF1aXRlDQo+ID4gPiBpbnRlbnRpb25hbGx5KS4NCj4gPiA+DQo+ID4gPiBJIGRvbuKAmXQga25v
dyBhYm91dCBSb2JlcnQsIGJ1dCB0aGF0IGlzIHBhcnQgb2YgdGhlIGRpc2N1c3Npb24gSQ0KPiA+
ID4gd291bGQgbGlrZSB0byBzZWUuDQo+ID4gPg0KPiA+ID4gWWVzLCBkdXBsaWNhdGUgc3lzdGVt
LWlkcyBoYXZlIGFsd2F5cyBiZWVuIGEgcG90ZW50aWFsIHByb2JsZW0sIGJ1dA0KPiA+ID4gdGhp
cyBkb2N1bWVudCBpbnRyb2R1Y2VzIGEgbmV3IGRlLWR1cGxpY2F0aW9uIG1lY2hhbmlzbSB0aGF0
IHJlc3VsdHMNCj4gPiA+IG5vdCBqdXN0IGluIHVuc3luY+KAmWQgZGF0YWJhc2VzLCBidXQgaW4g
cmVzdGFydGluZyBhZGphY2VuY2llcyDigJMgc28NCj4gPiA+IGF0IGxlYXN0IHRoZSBtYW5pZmVz
dGF0aW9uIG9mIHRoZSBwcm9ibGVtIGlzIGRpZmZlcmVudC4NCj4gPiA+DQo+ID4gW0xlczpdIFRo
ZSAicHJvYmxlbSIgZXhpc3RzIGFzIGxvbmcgYXMgdGhlIGR1cGxpY2F0ZSBzeXN0ZW0taWRzIGV4
aXN0Lg0KPiA+IFRoZSByZWNvdmVyeSBtZWNoYW5pc20gZG9lcyBub3QgaW50cm9kdWNlIG5ldyBw
cm9ibGVtcyAtIGl0IGFjdHVhbGx5DQo+ID4gYWN0cyB0byBtaW5pbWl6ZSB0aGUgZHVyYXRpb24g
b2YgdGhlIHByb2JsZW0uIE9uZSBjb3VsZCBhcmd1ZSAoYW5kIEkNCj4gPiBhbSBOT1QgZG9pbmcN
Cj4gPiBzbykgdGhhdCBhdXRvbWF0ZWQgcmVzb2x1dGlvbiBjb3VsZCBiZSBhIGJlbmVmaXQgaW4g
YWxsIGRlcGxveW1lbnRzLiBJDQo+ID4gdGhpbmsgdGhlIGlzc3VlIGluIG5vbi1hdXRvY29uZmln
IGRlcGxveW1lbnRzIGlzIHRoYXQgc2luY2Ugc3lzdGVtcw0KPiA+IGhhdmUgYmVlbiBtYW51YWxs
eSBwcm92aXNpb25lZCB3ZSBjYW5ub3QgYXNzdW1lIHRoYXQgbmV0d29yaw0KPiBvcGVyYXRvcnMN
Cj4gPiB3YW50IHVzIHRvIGF1dG9tYXRpY2FsbHkgY2hhbmdlIHRoZSBjb25maWcgb24gb25lIG9m
IHRoZWlyIGJveGVzLg0KPiA+IFRob3VnaCwgd2hvIGtub3dzIC0gbWF5YmUgd2Ugd2lsbCBnZXQg
YXNrZWQgdG8gdXNlIHRoaXMgZXh0ZW5zaW9uDQo+ID4gb3V0c2lkZSBvZiBhdXRvY29uZmlnIGRl
cGxveW1lbnRzLg0KPiA+DQo+ID4gSXQgaXMgbmVjZXNzYXJ5IHRvIGhhdmUgc3VjaCBhIG1lY2hh
bmlzbSBpbiBhdXRvY29uZmlnIGRlcGxveW1lbnRzDQo+ID4gc2luY2UgdGhlcmUgaXMgLSBieSBk
ZWZhdWx0IC0gbm8gbWFudWFsIGludGVydmVudGlvbi4gQnV0IHRvDQo+ID4gY2hhcmFjdGVyaXpl
IHRoaXMgYXMgYWRkaW5nIHJpc2sgaXMgaW5jb3JyZWN0IElNTy4NCj4gDQo+IFtCaW5nXSBJIGFn
cmVlIHdpdGggTGVzIHRoYXQgc3lzLWlkIGR1cGxpY2F0aW9uIGF0dGFjayBpcyBub3QgYW4gImFk
ZGluZyIgcmlzay4NCj4gQnV0IG1heWJlIHdlIGNvdWxkIGFkZCBhIGJpdCBtb3JlIHRleHQgdG8g
ZXhwbGFpbiB3aHkgdGhpcyBkb2N1bWVudA0KPiBSRUNPTU1ORUQgdG8gaW1wbGVtZW50IEF1dGgg
VExWLg0KPiANCj4gUHJvcG9zZWQgYWRkZWQgdGV4dCBpbiAzLjUuMSAoQXV0aGVudGljYXRpb24g
VExWKSBhcyBiZWxvdzoNCj4gIlRoZSB1c2Ugb2YgYXV0aGVudGljYXRpb24gaXMgaW5jb21wYXRp
YmxlIHdpdGggYXV0by1jb25maWd1cmF0aW9uIGFzIGl0DQo+IHJlcXVpcmVzIHNvbWUgbWFudWFs
IGNvbmZpZ3VyYXRpb24uIEhvd2V2ZXIsIHRoZXJlIG1pZ2h0IGJlIHNvbWUgdXNlcnMNCj4gd291
bGQgbGlrZSB0byBwYXkgdGhlIGVmZm9ydCBvZiBtYW51YWwgY29uZmlndXJhdGlvbiB0byBtaXRp
Z2F0ZSBzb21lDQo+IHNlY3VyaXR5IGF0dGFjayAoZS5nLiBhIG1hbGljaW91cyBub2RlIGNyYWZ0
cyBwYWNrZXQgdG8gaW50ZW50aW9uYWxseSBjYXVzZSB0aGUNCj4gU3lzLUlEIGR1cGxpY2F0aW9u
IHByb2NlZHVyZSBjb250aW51b3VzbHkpLg0KPiBUaHVzLCBpdCBpcyBSRUNPTU1FTkVEIHRoYXQg
SVMtSVMuLi4gKHRoZSBzYW1lIGFzIGV4aXN0aW5nIHRleHQpLg0KPiANCj4gRG8geW91IHRoaW5r
IGl0J3MgT0s/DQo+IA0KPiBCZXN0IHJlZ2FyZHMsDQo+IEJpbmcNCj4gDQo+IA0KPiA+ICAgTGVz
DQo+ID4NCj4gPg0KPiA+ID4gPiBTbyB5b3UgYXJlIGFza2luZyB1cyB0byByZXBlYXQgYSBkaXNj
dXNzaW9uIHdoaWNoIGhhcyBhbHJlYWR5IGJlZW4NCj4gPiA+ID4gaGVsZCBpbiB0aGUgY29udGV4
dCBvZiBSRkMgNTMwNCBhbmQgUkZDIDUzMTAuDQo+ID4gPiA+DQo+ID4gPiA+IEl0IHdvdWxkIGJl
IG1vcmUgYXBwcm9wcmlhdGUgdG8gYWRkIHRoZSBub3JtYWwgcmVmZXJlbmNlIHRvIFJGQw0KPiA+
ID4gPiA1MzA0LzUzMTAgaW4gdGhlIFNlY3VyaXR5IHNlY3Rpb24gdGhhbiB3aGF0IHlvdSBwcm9w
b3NlLg0KPiA+ID4NCj4gPiA+IEkgZG9u4oCZdCB0aGluayBpdCBodXJ0cyB0byBhZGQgYSByZWZl
cmVuY2UgdG8gdGhvc2UgUkZDcywgYnV0IHRoZXkNCj4gPiA+IGFyZSBib3RoIGFib3V0IGFkZGlu
ZyBhdXRoZW50aWNhdGlvbiDigJMgdGhlIHByb2JsZW0gaW4gdGhpcyBkb2N1bWVudA0KPiA+ID4g
aXMgZXhhY2VyYmF0ZWQgYnkgdGhlIGZhY3QgdGhhdCB0aGVyZeKAmXMgbm8gYXV0aGVudGljYXRp
b24gYnkgZGVmYXVsdC4NCj4gPiA+DQo+ID4gPiBUaGUgbG93ZXIgbGF5ZXIgYXV0aGVudGljYXRp
b24gbWVjaGFuaXNtcyBhcmUgcXVpdGUgd2Vhaywgc3BlY2lhbGx5DQo+ID4gPiBrbm93aW5nIHRo
YXQsIGlmIGluIGEgaG9tZSBlbnZpcm9ubWVudCwgZm9yIGV4YW1wbGUsIGl0IG1heSBiZQ0KPiA+
ID4gcmVsYXRpdmVseSBlYXN5IHRvIGNvbm5lY3QgdG8gdGhlIFdpRmkgbmV0d29yay4NCj4gPiA+
DQo+ID4gPiBBbHZhcm8uDQo+ID4gPg0KDQo=


From nobody Mon Apr 10 08:13:28 2017
Return-Path: <shares@ndzh.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 105B1129537; Mon, 10 Apr 2017 08:13:20 -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 eQLBoLUiGrgH; Mon, 10 Apr 2017 08:13:16 -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 7189E1294F6; Mon, 10 Apr 2017 08:13:13 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=70.194.20.181; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Dale Worley'" <worley@ariadne.com>, <gen-art@ietf.org>
Cc: <i2nsf@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org>
References: <148952979419.24295.8210647087024239014@ietfa.amsl.com>
In-Reply-To: <148952979419.24295.8210647087024239014@ietfa.amsl.com>
Date: Mon, 10 Apr 2017 11:08:04 -0400
Message-ID: <00fb01d2b20c$4182ab80$c4880280$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGutpg0SXJzXob6/wPiGXgr+oPIOqHd3kAA
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/BdOnfWZaRQ5ROOJtDt92wB5ML1g>
Subject: Re: [Gen-art] [I2nsf] Review of draft-ietf-i2nsf-problem-and-use-cases-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 15:13:20 -0000

Dale: 

Thank you for the review.  Please see my comments below. 

Sue 

-----Original Message-----
From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Dale Worley
Sent: Tuesday, March 14, 2017 6:17 PM
To: gen-art@ietf.org
Cc: i2nsf@ietf.org; ietf@ietf.org;
draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Subject: [I2nsf] Review of draft-ietf-i2nsf-problem-and-use-cases-11

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-i2nsf-problem-and-use-cases-11
Reviewer:  Dale R. Worley
Review Date:  2017-03-14
IETF LC End Date:  2017-03-22
IESG Telechat date:  [unknown]

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

All of these nits are editorial.

>1.  Introduction
>
> This document describes the problem statement for Interface to
> Network Security Functions (I2NSF) as well as some I2NSF use cases.
> A summary of the state of the art in the industry and IETF which is
> relevant to I2NSF work is documented in
>  [I-D.hares-i2nsf-gap-analysis].

>The content of these sentences is very good, but the construction seems to
be peculiar.  The document doesn't *describe* the problem statement, the
document *is* a statement.  Similarly, hares-i2nsf-gap-analysis *is* a
summary of the state of the art.  >So I would use
>
> This document is the problem statement for Interface to Network
> Security Functions (I2NSF) as well as some I2NSF use cases.  A
> summary of the state of the art in the industry and IETF which is
> relevant to I2NSF work is [I-D.hares-i2nsf-gap-analysis].

Dale 

>But maybe you'll prefer to ask the RFC Editor.
>
> This document also briefly describes the
> following use cases summarized by
> [I-D.pastor-i2nsf-merged-use-cases]:
>
>This sentence should start a new paragraph, as it's not connected to the
sentences before it.

Thank you for finding these errors.  I also needed to change
I-D.hares-i2nsf-gap-analysis to draft-ietf-i2nsf-gap-analysis. 


>3.  Problem Space
>
> The following sub-section describes ...
>s/sub-section describes/sub-sections describe/

Thank you - sorry to have missed it. 

>3.1.1.  Diverse Types of Security Functions
>
> NSFs by different vendors can have
>  different features and have different interfaces.
>
>It might be worth mentioning somewhere what seems to be a convention:
>the document (or at least, section 3.1) is largely oriented toward "service
providers" who sell comprehensive network services (including security
functions) to "customers", but who in turn buy security functions from
"vendors".  Perhaps this could be ?>entered as terminology in section 2.
>
>The reason I mention this is that my background is as an end-user (which is
common in the IETF), so the term "service provider"
>Triggers in my mind the idea "someone I buy something from".  And the term
"vendor" triggers the *same* idea.  But in this draft, the default reader is
a "service provider" and "vendor" is *not* the same thing.

I've added this text: Security Service Provider:  A provider of security
services to the customers (end-users or enterprises) using NSF equipment
purchased from vendors or created by the service provider. 

>This point started to confuse me at the beginning of section 3.1.6.
>
>  Security Functions in a Demilitarized Zone (DMZ):   Examples of this
>   function are firewall/ACLs, IDS/IPS, one or all of AAA services
>    NAT, forwarding proxies, and application filtering.
> The phrase "one or all of AAA services NAT" seems to be incorrect.  I
suspect there's supposed to be a comma before NAT.

Good catch.  I will fix. 

>   Security gateways and VPN concentrators:    Examples of these
>     functions are; IPsec gateways, Secure VPN concentrators that
>    handle bridging secure VPNs, and Secure VPN controllers for data
>    flows.

> Unless "Secure VPN" is a name in itself, "secure" shouldn't be
capitalized.

Good point.  I will fix. 

> 3.1.2.  Diverse Interfaces to Control and Monitor NSFs
>
>   A challenge for monitoring is that an NSF cannot monitor what it
>   cannot view.  Therefore, enabling a security function (e.g., firewall
>   [I-D.ietf-opsawg-firewalls]) does not mean that a network is
>   protected.  As such, it is necessary to have a mechanism to monitor
>  and provide execution status of NSFs to security and compliance
>   management tools.  There exist various network security monitoring
>   vendor-specific interfaces for forensics and troubleshooting.

> This paragraph seems awkward.  Each sentence is reasonable, but the
connection between them is not clear to me. 
>  Perhaps the third sentence has the meaning "... it is necesary to have a
mechanism ...to verify that the NSF is seeing the traffic that is intended".
>The last sentence contains "network security monitoring vendor-specific
interfaces" which is awkward.  Perhaps
>
> There exist various vendor-specific interfaces for network security
> monitoring, forensics, and troubleshooting.

New paragraph is below.   Is it better

New/
A challenge for monitoring prior to mitigation of a security intrusion
is that an NSF cannot monitor what it cannot view. Therefore, enabling a 
 security function to mitigate an intrusion 
 (e.g., firewall <xref target="I-D.ietf-opsawg-firewalls"></xref>) 
 does not mean that a network is protected if there is no monitoring
feedback.  
  As such, it is necessary to have a mechanism
  to monitor and provide execution status of NSFs to security and
  compliance management tools. There exist various network security
  monitoring vendor-specific interfaces for forensics and
  troubleshooting, but an industry standard interface could 
  provide monitoring across avariety of NSFs.
/

 

3.1.4.  More Demand to Control NSFs Dynamically

>   The Security Service Providers ...

>The capitalization of "security service providers" is inconsistent.
> Some times all three words are capitalized, and some times they're not.
Thanks for catching this - I will fix it. 

3.1.5.  Demand for Multi-Tenancy to Control and Monitor NSFs

>   Service providers may need several operational units to control and
 >  monitor the NSFs, especially when NSFs become distributed and
 >  virtualized.
>
> You may want to explain what an "operational unit" is.  As far as I can
tell, neither "unit" nor "operational" (in this sense) is used elsewhere in
this draft.

Thanks for catching this vagueness. 
The point the service provides may have to deploy multiple controllers. 

How about: 

Service providers may need to deploy several NSF controllers to control and
monitor the NSFs, especially when NSFs become distributed and
virtualized.

>3.1.7.  Lack of Mechanism for NSFs to Utilize External Profiles
>  Many security functions depend on signature files or profiles to
>   perform (e.g., IPS/IDS signatures, DDos Open Threat Signaling
> (DOTS) filters).  
>I think the words "to perform" should be removed.  The sentence makes more
sense to me without those.  Or, if there is a meaning that needs to be
specified, "to perform" probably >isn't the right choice.  "to work" makes
sense in this place, but is an informal usage.  Perhaps "to function".

[removed "to perform") 

>   Today, the construction and use of black list databases
>  can be a win-win strategy for all parties involved.
>"win-win strategy" is a hackneyed phrase.  This is better

 > Today, the construction and use of black list databases
  > can be beneficial for all parties involved.

>However, it's not clear to me what additional information is carried by
"for all parties involved".  And for that matter, is "today"
>important here?
>I suspect that you mean something like this:
>
 > Today, black list databases can be beneficial, and in the future
 > there might be open source signatures/profiles ...

> 
>   (e.g., by Snort, Suricata, Bro and Kisnet)
>
>s/Kisnet/Kismet/
>"Snort, Suricata, Bro and Kisnet" reads like a reference -- I had to look
them up to discover that they are IDS software!
>
>But there needs to be some connection between a list of IDS software
systems and "open source signatures/profiles".  Perhaps:
>
> Today, black list databases can be beneficial, and in the future
>   there might be open source signatures/profiles distributed as part
>  of IDS systems (e.g. Snort, Suricata, Bro and Kisnet).

All good comments, but my recollection was the WG wanted to underscore the
strategy was good for all parties. 
Therefore, here's the new paragraph


New/
Today, black list databases can be a beneficial 
 strategy for all parties involved, but in the future there might be 
 open Source-provided signature/profiles distributed as part of IDS systems
(e.g., by Snort, Suricata, Bro and Kismet).
/
--
>There is a need to have a standard envelope (i.e., the format) to
 > allow NSFs to use external profiles.
>This is awkward.  Perhaps
 > There is a need to have a standard format to allow NSFs to use
 > external profiles.

This part hit many discussions.  How about

New/ There is a need to have a standard envelope (i.e., a message format) to

allow NSFs to use external profiles./ 

>3.1.8.  Lack of Mechanisms to Accept External Alerts to Trigger ...
>
> I2NSF controller(s) would manage the changing to the affected
>  policies ...
> This could be simplified to "I2NSF controller(s) would change the affected
policies ...".

New/  I2NSF  controller(s) would control any changes to affected policies
          (e.g., forwarding and routing, filtering, etc.)./

>The I2NSF controls the change (whether others change the policies or not). 
>  By monitoring the network alerts from DDoS ...
>Probably s/DDoS/DOTS/.
>
>   ... I2NSF
> can feed an alerts analytics engine that could recognize attacks so
> the I2NSF can enforce the appropriate policies.
>  Here, "I2NSF" is being used as a noun, whereas the previous usage is that
it is an adjective, and "I2NSF controller(s)" would be used.

New/
By monitoring the network alerts regarding DDoS attacks (e.g. from DOTS
servers or clients), 
the I2NSF controller(s) can feed an alerts analytics engine
that could recognize attacks so the I2NSF can enforce the
appropriate policies. 
/


>   ... provide information to the client ...
>
>I think this is clearer if s/the client/its clients/.  "client" is used
with two meanings, one is "customer" (e.g., in the definition of "Bespoke"),
and more commonly as "software client".  > If you say "[the controller's]
clients", it is clear that you're using the second meaning.

New/ DDoS mitigation is enhanced if the provider's network security
          controller can monitor, analyze, and investigate the abnormal
events
          and provide information to the customer or change the network
          configuration automatically
/

>3.1.9.  Lack of Mechanism for Dynamic Key Distribution to NSFs
>
> There is a need for a controller to distribute various keys to
> distributed NSFs.  To distribute various keys, the keys must be
>  created and managed.

>Perhaps combine these as
>
>   There is a need for a controller to create, manage, and distribute
>  various keys to distributed NSFs.

I've made this change. 


>   In addition, keys may be used to secure
>  the protocol and messages in the core routing infrastructure (see
>  [RFC4948])

>Probably s/protocol/protocols/.
>
I've made this change. 

>   If a device had an abstract key table
>  maintained by security services, a device could use these keys for
>  routing and seurity devices.
>
>s/seurity/security/
>
>Typical English usage in this situation is "it could use ..."; because "it"
is the subject of the second clause, it is presupposed to be the same as the
subject of the first clause.

New sentences: 
/ If a device had an abstract  key table maintained by security services, it
could use these 
keys for routing and security devices.  /

>   Conceptually, there must be an interface defined for routing/
>  signaling protocols to make requests for automated key management
>  when it is being used, and to notify the protocols when keys become
 >  available in the key table.  One potential use of such an interface
>   is to manage IPsec security associations on SDN networks.
>I think you need to add a subject in "... and for XXX to notify the
protocols ..." for clarity, the omitted noun could be "interface" or
"protocols".

Grammatically - I disagree .  The clauses "to make request...." and "to
notify" are infinitive clauses which modify the direct object (an interface)
which are linked together in a list.  
However, rather than debate this syntax with others - I've changed the
syntax to a cl

New/ 
Conceptually, there must be an interface defined for routing/signaling
protocols 
  that can:  a) make requests for automated key management when it is being
used. and 
   b) notify the protocols when keys become available in the key table. 
/


>The last sentence seems redundant, as security associations have been
discussed at the beginning of 3.1.9.  Is there a particular reason to point
out IPsec at this point (since many >secured protocols need keys)?

The WG felt it needed an example here.   If it is OK, I'm going to leave
this in for another round of editing. 

> If protocols share
>     common mechanisms for authentication (e.g., TCP Authentication
>     Option [RFC5925]), then the same mapping may be reused.

>This sentence starts with "protocols [that] share common mechanisms"
>but then mentions only one protocol.  Do you mean

  >     If several protocols share a
  >    common mechanism for authentication (e.g., TCP Authentication
  >   Option [RFC5925]), then the same mapping may be used for all
  >   usages of that mechanism.


Thank you.  I've changed to this sentence. 


>   3.  Automated Key management needs to support both symmetric keys and
>     group keys via the abstract key service provided by items 1 and
 >     2.
>s/Key/key/

--Thank you. 

>I think "via the abstract key service provided by items 1 and 2" is
redundant here.

It may be redundant, but as I recall it was important to some of the
authors. 
--------------

3.2.  Challenges Facing Customers

>   o  Which critical communications are to be preserved during critical
>     events and which hosts are continue service,
>
>"are continue service" seems to be incorrect in some way.

New/Which critical communications are to be preserved during
            critical events and which hosts will continue services over the
network,/


>   o  What signaling information is passed to a controller that during a
>     Distributed Denial of Service in order to ask for mitigation
>     services (within the scope DOTS working group),
> "that" should be removed, I think.

Removed. 

>3.2.2.  Today's Control Requests are Vendor Specific
>
> Without a standard technical
> standard interface that provides a clear technical characterization,
>  the service provider faces many challenges:

>Should "standard technical standard interface" be "standard interface"
>or "standardized interface"?

>Standardized interface. 
> No standard technical characterization, APIs, or Interface
>I think you want a colon after this phrase to parallel the other items in
the list.

Thank you. 

>   Managing by scripts de-jour:    The current practices rely upon the
>      use of scripts that generate other scripts which automatically run
>  to upload or download configuration changes, log information and
>    other things.  These scripts have to be adjusted each time an
>    implementation from a different vendor technology is enabled on a
>    provider side.
> The phrase "on a provider side" doesn't read well.  Perhaps "by a service
provider"?

3.3.  Lack of Standard Interface to Inject Feedback to NSF

>   The following sub-section describes the problems and challenges
>  facing customers and security service providers when some or all of
> the security functions are no longer physically hosted by the
> customer's adminstrative domain.
>s/adminstrative/administrative/

Note: Sentence was removed. 

>   As more sophisticated threats arise, enterprises, vendors, and
>   service providers have to rely on each other to achieve optimal
> protection.  Cyber Threat Alliance (CTA,
> http://cyberthreatalliance.org/) is one of those initiatives that aim
> at combining efforts conducted by multiple organizations.

>This paragraph doesn't fit well in the flow of the text.  The second
sentence seems like it's basically a reference, and the link should be put
down in the references.  But I think the >point resembles the discussion in
3.1.7, that you want to enable organizations to pass among themselves new
profiles, which the customers or service providers can insert into NSFs > in
a simple way.  Perhaps

>   As more sophisticated threats arise, protection will depend
> on enterprises, vendors, and service providers being able to
>  cooperate to develop optimal profiles, e.g., through initiatives
>   like [CTA].  

>and then combine with the paragraph which follows:
>
 > The standard interface to provide security profiles to the NSF should
 > interwork with the formats which exchange security profiles between
>  organizations.

3.5.  Difficulty to Validate Policies across Multiple Domains

  >As discussed in the previous four sections, both service providers ...

>Probably s/sections/sub-sections/.
>   ... and customers have needs to express policies and profiles ...
>
>s/needs/need/
>
 > This section and the next section (section 3.6) xamine what ...
>s/xamine/examine/

> (Have you spell-checked this draft?) 

Not this one.  I'm afraid I rushed the -11 out in response to query.  I
lived to regret this fact. 
>
>
>   ... happens in two specific network scnearios: ...

s/scnearios/scenarios/

> a) multi-domain control of
 >  security devices hosted on virtual and non-virtual ...
>There is a noun missing after "virtual and non-virtual".

Noun is NSFs 

>   Hosted security service may instantiate NSFs in Virtual Machines
>
>
>You probably don't want to capitalize "virtual machines" here.

Changed. 


>   To set-up this cross-domain service, the security controller must be
>  able to communicate with NSFs and/or controllers within its domain
>  and across domains to negatiate for the services needed.

> s/set-up/set up/  ("set up" is a verb (more or less), "set-up" is the
action of setting up or the thing which is set up.)

The text should be "to set up" an infinitive verb setting up an infinitive
clause, or it can be considered a prepositional phrase "to set up ..." 
Anyway, thank you for the editing. 

s/negatiate/negotiate/

3.6.  Software-Defined Networks

>   Software-Defined Networks have changed the landscape of data center
>   designs by introducing overlay networks deployed over ToR switches
>  that connect to a hypervisor.

>You probably should spell out "ToR switch"; "top of rack switch" is not yet
listed in Wikipedia as a meaning of "ToR".


Start here
-----------------
4.1.  Basic Framework

> Integrity of the NSF:   by ensuring that the NSF is not
> compromised;

>  Isolation:   by ensuring the execution of the NSF is self-contained
 >   for privacy requirements in multi-tenancy scenarios.
>   Provenance of NSF:    Customers may need to be provided with strict
>      guarantees about the origin of the NSF, its status (e.g.,
>    available, idle, down, and others), and feedback mechanisms so
>    that a customer may be able to check that a given NSF or set of
>    NSFs properly conform to the the customer's requirements and
>    subsequent configuration tasks.
>The punctuation and capitalization is inconsistent between the list items
here.  I suggest changing the first two to (more or less)\
>sentences:
>
> Integrity of the NSF:   Ensuring that the NSF is not compromised.
>
> Isolation:   Ensuring the execution of the NSF is self-contained
>    for privacy requirements in multi-tenancy scenarios.
>
>?Probably s/Provenance of NSF/Provenance of the NSF/.
>
> In order to achieve this, the security controller may collect
> security measurements and share them with an independent and trusted
> third party (via Interface 1) in order to allow for attestation of
> NSF functions using the third party added information.
>
>Would this really be via Interface 1?  It looks like Interface 1 only goes
to the customer's client, not a 3rd party service, and it is used for
passing security requests.  This is made clearer in the next paragraph, but
it would probably be better to only say that there needs to be an interface
to 3rd parties for services like this, and it may be a variant of Interface
1 or it may be a distinct interface.

Dale: While this make be clearer, it was the WGs final comments.   I'll see
what the IESG says. 


>4.2.  Access Networks

>   Figure 3 shows how these virtual
>  access nodes for different types of customers connect connect through
>  virtual access nodes an NSF.
> s/connect connect/connect/
>The grammar of the sentence needs fixing also somewhere near "nodes an
NSF".

Sue: Fixed 

 > These use cases define the interaction between the operator and the
> vNSFs through automated interfaces, typically by means of
> Business- to-Business (B2B) communications.
>Dale: Is "Business-to-Business (B2B) communications" a technical term?  
> It doesn't seem to me to convey any additional information, since most of
the usages envision that NSFs may be provided by outside vendors, so pretty
much any communication with an NSF may be business-to-business
communication.

New/These use cases define the interaction between the operator and the
        vNSFs through automated interfaces which support the business
communications
        between customer and provider or between two business entities./

> Service Provider:   Service requests for policies that protect ...
>
>There isn't a "Service Provider" illustrated in the figure.  
>I assume that the Service Provider looks much like the other three cases, 
>since those look very much like each other, but some sort of
> illustration should be provided.  Especially if the Service Provider 
> has further customers (presumably further to the left in the figure), that
would be a more complex architecture.

Sue: Service Provider added to the network 

 >  ... may want to get
  > their dedicated NSFs (most likely vNSFs) for direct control purposes.
>This is rather informal usage.  Perhaps better:

>   ... may want to contract separately for dedicated NSFs ...

Sue: Thank you - changed. 

>  In this case, here are the steps to associate vNSFs to specific
> customers:
>There are two cases discussed in the paragraph before this sentence, 
>and it's not obvious which one this sentence is connected to via "In this
case".  
>Or does it apply to both?  If it applies to the second case only, 
>I suggest splitting the last two sentences off as a separate paragraph. 
 >If this sentence applies to all cases in this subsection, I suggest
removing "In this case".

Done - split off the second 2 sentences. 

>4.3.  Cloud Data Center Scenario
>
> The on-demand, dynamic nature of security service delivery
> essentially encourages that the network security "devices" be in
> software or virtual form factors, rather than in a physical appliance
>  form.

>I think you want to s/form factors/forms/.  (The phrase "form factor"
>seems to be abused to mean many things.)

Done - corrected to "forms" 

 >  Another example is that IPS/
 > IDS services for investment banking and non-banking traffic may be
 > separated for regulatory reasons.

> Is "investment banking" specific here, or does this statement also apply
to "banking" generally?  Or is "non-banking traffic" really
"non-investment-banking traffic" (in which case calling it "other traffic"
is probably better)?

Sue: Good point.  
New /
Another  example is that IPS/IDS services which splits traffic into
investment banking traffic and other data traffic to comply with 
regulatory restrictions for transfer of investment banking information/

>4.3.2.  Firewall Policy Deployment Automation
>
> Even though most vendors support similar firewall features, the
> actual rule configuration keywords are different from vendors to
> vendors, making it difficult for automation.
>
>Probably s/actual rule/specific rule/ or even just "specific".

Sue: 
New/
Even though most vendors support similar firewall features, the
          specific rule configuration keywords are different from vendors to
          vendors, making it difficult for automation.
/

4.3.3.  Client-Specific Security Policy in Cloud VPNs

/   Clients of service provider-operated cloud data centers not only need
/ to secure Virtual Private Networks (VPNs), but also [X] virtual security
/ functions that apply the clients' security policies.  
/There's an understood verb at the location marked [X].  I think it's
supposed to be "to secure", and if so, the usage is correct.  But it's hard
to read, so I think it would be better to not omit the verb.

Sue: You are right. The negation in the sentence makes this difficult. 

New /Clients of service provider-operated cloud data centers 
          need to secure Virtual Private Networks (VPNs) and virtual
          security functions that apply the clients' security policies./

Now the direct objection into a list (VPNs + virtual security functions).


4.4.  Preventing Distributed DoS, Malware and Botnet attacks

>   Many networks such as Internet of
>  Things (IoT) networks, Information-Centric Networks (ICN), Content
> Delivery Networks (CDN), Voice over IP packet networks (VoIP), and
> Voice over LTE (VoLTE) are also exposed to such attacks.
>
>This seems to be just a specialization of the preceding sentences.
>Does it add more information?  
>(E.g., perhaps there are special considerations for each of these types of
networks, in which case it might be useful to state that.)

Changed to:/
 Many networks
which carry groups of information (such as Internet of Things (IoT)
networks, 
Information-Centric Networks (ICN),  Content Delivery Networks (CDN), 
Voice over IP packet networks (VoIP), and Voice over LTE (VoLTE))
are also exposed to such remote attacks.  There are many examples of 
remote attacks on these networks, but the following examples will illustrate
the 
issues. A malware attack on an IoT network which carries sensor readings and
instructions may attempt to 
alter the sensor instructions in order to disable a key sensor. 
A malware attack VoIP or VoLTE  networks is software that attempts to place
unauthorized 
 long-distance calls. Botnets may overwhelm nodes in ICN and CDN networks so
that 
the networks cannot pass critical data.  
/

4.5.  Regulatory and Compliance Security Policies

  >Organizations are not only supposed to protect their networks against
   >attacks, but they should also adhere to various industry 
   >regulations:
>It's probably better to s/should also/must also/!

Thanks for noticing. 

7.  Security Considerations

>Having a secure access to control and monitor NSFs is crucial for
> hosted security services.
>Probably s/a secure/secure/.

>   Therefore, proper secure communication
> channels have to be carefully specified for carrying controlling and
> monitoring traffic between the NSFs and their management entity (or
> entities).

>I think you can condense this to "management entity(ies)", but you probably
should talk to the RFC Editor about it.

I will ask the RFC Editor about this point. 


>>   In addition, the Flow security policies specified by customers can
>> conflict with providers' internal security policies which may allow
>>   unauthorized traffic or unauthorized changes to flow polices (e.g.
>> customers changing flow policies that do not belong to them).
>I don't think you want to capitalize "flow" here.

Agreed, 

>It's not clear to me what "which may allow unauthorized ..." applies to.
It seems like there's an important issue in just
>   In addition, the Flow security policies specified by customers can
>  conflict with providers' internal security policies
>
>It seems that solving I2NSF requires a clear understanding of how the
customer's policies and the provider's policies interact.  (I would think
something is allowed only if both policies allow it, but the reality may be
more complex.)

>The rest of the sentence seems redundant given the discussion in the rest
of document.
>
> Therefore, it is crucial to have proper AAA [RFC2904] to authorize
> access to the network and access to the I2NSF management stream.
>
>It seems to me that this is a rather generalized need for I2NSF, and not
connected to the previous sentences.  So I would omit "Therefore"
>and put it as a separate paragraph.

Good catch. 


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


From nobody Mon Apr 10 09:05:26 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC5CA129534 for <gen-art@ietfa.amsl.com>; Mon, 10 Apr 2017 09:05:13 -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=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=outer-planes-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 7dXT5tgpGRGO for <gen-art@ietfa.amsl.com>; Mon, 10 Apr 2017 09:05:07 -0700 (PDT)
Received: from mail-oi0-x244.google.com (mail-oi0-x244.google.com [IPv6:2607:f8b0:4003:c06::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EFA7129544 for <gen-art@ietf.org>; Mon, 10 Apr 2017 09:05:07 -0700 (PDT)
Received: by mail-oi0-x244.google.com with SMTP id o83so371511oik.1 for <gen-art@ietf.org>; Mon, 10 Apr 2017 09:05:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outer-planes-net.20150623.gappssmtp.com; s=20150623; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to; bh=UPM72sq92ZDu4opqFNzUO6qFYswQGFh9okmQcjhj6qA=; b=JYO9gr/R36dtSc3aBjtpSL1iQgWymi8w5R95X11Xr+9rZaduwz1qw6VMFoiscJZo+T oPFRGTFSenS39Oer5CfRZQzj8CxqucSRY9lFMzy4zlK5idSUP5lWPYvAzW5zAfd73JV5 Rf4oIk7yWf8hzl0GwiiWf3B4TFONrCt0dkUkyEY9unu0stuxFj9CydYSweAKUqLn974Z kDOWwY1iosHGDfmsQW+GtnjvN3i6+9J6mJ60n/Hep5S35pFRUC/12ndpu2lZxHgd1nyN lI6KUjgAuy+yOEOVKEsnx1QNeHwQSasIt/E5og3ksXcUD1Selkp1PpwQimfe0eVMZCA8 Ny2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to; bh=UPM72sq92ZDu4opqFNzUO6qFYswQGFh9okmQcjhj6qA=; b=mTEIMCw1RtWL4hWHstMoOIpg0hCZncpRTZok4eqWYCUnCgVG1dLUeTzkjvE95IbLnP i8LK34gVTMfuXHrf3WtvlOyCSA6CZubs4aYefI471qYl52V5kXo2e6C4t1ht7Jdhv726 KiIXEu1wxyVwIuEzNPFafi/J/WWSPNbYOvelo/uKwMOuOSFmUlwbWe9B9gjFVeLmbBDM 0IXV3xhSgFLP9N3v5JoCiIMPnIJ6dYXfy9fKfFavhUJlgD2MOvkWkfaeVNBYBvnz/tVZ cytvvHs6oWkff6gfgwstsjRLCpquqnPpvJgS2hPvHfBwHWa1NfIfSEUj65rBA2ci3Cs+ FbRA==
X-Gm-Message-State: AN3rC/6kiN6otB62zdatSJOhQAA6QHArbVp3n6vlLirtfm1MI0a8TpNSQDX2WmhCg8lpQw==
X-Received: by 10.202.96.132 with SMTP id u126mr1797762oib.183.1491840306789;  Mon, 10 Apr 2017 09:05:06 -0700 (PDT)
Received: from [10.6.23.170] ([128.177.113.102]) by smtp.gmail.com with ESMTPSA id y198sm6407011oie.8.2017.04.10.09.05.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Apr 2017 09:05:05 -0700 (PDT)
Sender: Matthew Miller <linuxwolf@outer-planes.net>
To: "Acee Lindem (acee)" <acee@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
Cc: "draft-ietf-rtgwg-yang-key-chain.all@ietf.org" <draft-ietf-rtgwg-yang-key-chain.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
References: <149158793224.11224.1489071223626497682@ietfa.amsl.com> <D50ED999.A7F47%acee@cisco.com>
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
Message-ID: <6f34a4cc-6492-a354-f257-412b0f5e84a1@outer-planes.net>
Date: Mon, 10 Apr 2017 10:05:09 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <D50ED999.A7F47%acee@cisco.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="QkgNiHQAfBscnI68RtA2QqVf0dI9QJ52c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/KVeJfX1SsuzZq4QzVWdszYXKj_I>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 16:05:14 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--QkgNiHQAfBscnI68RtA2QqVf0dI9QJ52c
Content-Type: multipart/mixed; boundary="L4swmtKLJ5mrwTLR8UO1A3aCKF4QSjA3w";
 protected-headers="v1"
From: "Matthew A. Miller" <linuxwolf+ietf@outer-planes.net>
To: "Acee Lindem (acee)" <acee@cisco.com>, "gen-art@ietf.org"
 <gen-art@ietf.org>
Cc: "draft-ietf-rtgwg-yang-key-chain.all@ietf.org"
 <draft-ietf-rtgwg-yang-key-chain.all@ietf.org>, "ietf@ietf.org"
 <ietf@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
Message-ID: <6f34a4cc-6492-a354-f257-412b0f5e84a1@outer-planes.net>
Subject: Re: Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
References: <149158793224.11224.1489071223626497682@ietfa.amsl.com>
 <D50ED999.A7F47%acee@cisco.com>
In-Reply-To: <D50ED999.A7F47%acee@cisco.com>

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

Thanks for responding Acee, I look forward to the next revision.

Responses inline ...


- m&m

Matthew A. Miller

On 17/04/08 16:55, Acee Lindem (acee) wrote:
> Hi Matt,
>=20
> Thanks for the review.
>=20
> On 4/7/17, 1:58 PM, "Matthew Miller" <linuxwolf+ietf@outer-planes.net>
> wrote:
>=20
>> 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-rtgwg-yang-key-chain-17
>> Reviewer: Matthew A. Miller
>> Review Date: 2017-04-07
>> IETF LC End Date: 2017-04-07
>> IESG Telechat date: 2017-04-13
>>
>> Summary:
>>
>> This document is almost ready to be published as a Proposed Standard,
>> once the issues noted herein are resolved.
>>
>> Major issues:
>>
>> NONE
>>
>> Minor issues:
>>
>> * Forgive me for my limited knowledge of YANG, but is there a reason
>> key-strings are only representable as either a YANG string or
>> hex-string type, and not the YANG binary type?
>=20
> Let me ask why I=C2=B9d want to use this type? I can get all the entrop=
y I want
> with a hex string and implementations are familiar with this
> representation. I=C2=B9m not really fond of the obscure base64 represen=
tation
> used by the YANG type and if one consults Benoit=C2=B9s search tool, th=
e type
> is not widely used. http://www.yangcatalog.org/yang-search/yang-search.=
php
>=20

Thanks for explaining.  I asked because (more) efficient transfer of
binary data has come up for other textual formats (read: JSON), and the
rough consensus was for base64.  That said, if the community is already
fine with hex, then I consider this a non-issue.

>>
>> * This document does not provide much guidance around AES key wrap
>> other than it can be used and the KEK is provided
>> out-of-band/-context.
>> For instance, AES key-wrapped key-strings probably require using
>> "hexidecimal-string".
>=20
> Yes - I=C2=B9ll add that.
>=20

Thanks.

>>  Also, assuming I'm reading the model
>> correctly,
>> it appears this feature applies to the whole chain, which I think is
>> worth calling out.
>=20
> In YANG, if you support a feature, it is for the entire model.
> The per-chain boolean indicates whether or not it is applies to all the=

> keys in that particular key-chain. I will clarify this.
>>
>> * This document warns against using the "clear-text" algorithm, which
>> the
>> reader is lead to understand is for legacy implementation reasons.
>> However, is there not a similar concern with cryptographically weak
>> algorithms, such as md5 and (arguably) sha1?
>=20
> I can add something for MD5.

Thanks.  I know I said arguably sha1, but at the apps layer it is
considered weak with in-the-wild tools able to produce collisions, which
leads to the minimum being sha256.

I would consider including a note about sha1 and md5, but I understand
that maybe operational realities are such that sha256 is not widely
deployed for these devices, or its not otherwise seen as a problem yet.

>>
>> Nits/editorial comments:
>>
>> * In Section 3.2. "Key Chain Model Features", the word "of" is
>> missing
>> between "configuration" and "an" in the phrase "support configuration
>> an
>> acceptance tolerance".
>=20
> Good catch. I will fix.
>>
>> Non-nits:
>>
>> * I note that idnits is calling out some odd spacing issues, but I
>> think
>> they are safe to ignore.
>=20
> Though the line numbers don=C2=B9t match the draft, I was able to fix t=
hese.
>=20
> Thanks,
> Acee=20
>>
>=20


--L4swmtKLJ5mrwTLR8UO1A3aCKF4QSjA3w--

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

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

iQEcBAEBCgAGBQJY6602AAoJEOz0ck4QngW72r0H/1bMTPltgvYGOnyVUPmK95U/
dIj0sFlmyQpfaiiSnNgdBOw5mzkKsbyaaYdfBcCn+nI2HVc8o6rF+oLSREXYUywM
ZQ5AIU8lCmfVSQRald7QTk+AyWFrtsjNclwNaqy3yzYmq2I4XF3meP69w6T9TSce
bajwM47C6DebrWSvyBf94uc8pMcVIqXtcSeOLywJkvX4oU0NoIY/ejU7WMQZKwM5
sbrb/2YjXCtHaXwlKxJi+SRyeTaNY+wyLgN5PELNXNG5jtbwAF+PWiJFLWCC8Bos
dfq1bGQs18D1jJ0bCrd4iLHV1jcTO+tuwZMraKAXiXVdTJZTydGBOSeZwJ5piOY=
=JxPb
-----END PGP SIGNATURE-----

--QkgNiHQAfBscnI68RtA2QqVf0dI9QJ52c--


From nobody Mon Apr 10 10:32:35 2017
Return-Path: <aretana@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B06FC1294EC; Mon, 10 Apr 2017 10:32:33 -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 Ndt6fal-EbCI; Mon, 10 Apr 2017 10:32:32 -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 A4ED012947E; Mon, 10 Apr 2017 10:32:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2094; q=dns/txt; s=iport; t=1491845549; x=1493055149; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ilKWlMmlgb0EuOMIUmF06s8jkmHQOgPCZo0Kx+dFWHw=; b=SXFt2KXtQrOv5pNVuc1/OssVYEsI9BT1wHprifpRpVxkb5ErG+ZVVtzF SKPNbj62jpge/AZrMjgWI1x6Izc//Z7lPSGKOA1qf2SaKk93XA/J/3kkX xigCLaClhA6jBqqvSDruGYo1yEYw+CH9klCmXGr1OZze8kLuiDs2d2+UU A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DEAQBiwOtY/49dJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1OBbAeDX4oTpx+CD4YkAhqDTT8YAQIBAQEBAQEBayiFFgYjEUU?= =?us-ascii?q?QAgEIGgImAgICMBUQAgQBDQWKD6kMgiaKfQEBAQEBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?R2BC4VFggWCa4dcLoIxAQSWIIZbAZJYkUGTfwEfOEo7WxVSAYZIdYhSgQ0BAQE?=
X-IronPort-AV: E=Sophos;i="5.37,182,1488844800"; d="scan'208";a="229072990"
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; 10 Apr 2017 17:32:28 +0000
Received: from XCH-RCD-004.cisco.com (xch-rcd-004.cisco.com [173.37.102.14]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v3AHWSsC029910 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 10 Apr 2017 17:32:28 GMT
Received: from xch-aln-002.cisco.com (173.36.7.12) by XCH-RCD-004.cisco.com (173.37.102.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 10 Apr 2017 12:32:28 -0500
Received: from xch-aln-002.cisco.com ([173.36.7.12]) by XCH-ALN-002.cisco.com ([173.36.7.12]) with mapi id 15.00.1210.000; Mon, 10 Apr 2017 12:32:28 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Liubing (Leo)" <leo.liubing@huawei.com>, Robert Sparks <rjsparks@nostrum.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90HdNwrO1bKAUiTTjwvgN+2naG6trYAgAAGPoCAAANsAP//wPeAgABTw4CAA+NsAIAASqUA///utoA=
Date: Mon, 10 Apr 2017 17:32:27 +0000
Message-ID: <DC9299D1-F989-471C-A7AC-1A5E9C9288AB@cisco.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com> <c3a3a16110cb44c182413d993377de6d@XCH-ALN-001.cisco.com>
In-Reply-To: <c3a3a16110cb44c182413d993377de6d@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.1f.0.170216
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.117.15.6]
Content-Type: text/plain; charset="utf-8"
Content-ID: <BCEC487E835CFC4387DBE1CB06065FF2@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/fngpY9t5FsacasljI6NQOrbQjEY>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 17:32:34 -0000

V29ya3MgZm9yIG1lIQ0KDQpUaGFua3MhDQoNCkFsdmFyby4NCg0KDQoNCg0KDQpPbiA0LzEwLzE3
LCAxMDozNCBBTSwgIkxlcyBHaW5zYmVyZyAoZ2luc2JlcmcpIiA8Z2luc2JlcmdAY2lzY28uY29t
PiB3cm90ZToNCg0KQmluZy9Sb2JlcnQvQWx2YXJvIC0NCg0KSGVyZSBpcyB0aGUgZXhpc3Rpbmcg
dGV4dCBvZiB0aGUgU2VjdXJpdHkgU2VjdGlvbjoNCg0KICAiSW4gZ2VuZXJhbCwgdGhlIHVzZSBv
ZiBhdXRoZW50aWNhdGlvbiBpcyBpbmNvbXBhdGlibGUgd2l0aCBhdXRvLQ0KICAgY29uZmlndXJh
dGlvbiBhcyBpdCByZXF1aXJlcyBzb21lIG1hbnVhbCBjb25maWd1cmF0aW9uLg0KDQogICBGb3Ig
d2lyZWQgZGVwbG95bWVudCwgdGhlIHdpcmVkIGNvbm5lY3Rpb24gaXRzZWxmIGNvdWxkIGJlIGNv
bnNpZGVyZWQNCiAgIGFzIGFuIGltcGxpY2l0IGF1dGhlbnRpY2F0aW9uIGluIHRoYXQgdW53YW50
ZWQgcm91dGVycyBhcmUgdXN1YWxseQ0KICAgbm90IGFibGUgdG8gY29ubmVjdCAoaS5lLiB0aGVy
ZSBpcyBzb21lIGtpbmQgb2YgcGh5c2ljYWwgc2VjdXJpdHkgaW4NCiAgIHBsYWNlIHByZXZlbnRp
bmcgdGhlIGNvbm5lY3Rpb24gb2Ygcm9ndWUgZGV2aWNlcyk7IGZvciB3aXJlbGVzcw0KICAgZGVw
bG95bWVudCwgdGhlIGF1dGhlbnRpY2F0aW9uIGNvdWxkIGJlIGFjaGlldmVkIGF0IHRoZSBsb3dl
cg0KICAgd2lyZWxlc3MgbGluayBsYXllci4iDQoNCg0KUHJvcG9zZWQgcmV2aXNpb246DQoNCiJJ
biB0aGUgYWJzZW5jZSBvZiBjcnlwdG9ncmFwaGljIGF1dGhlbnRpY2F0aW9uIGl0IGlzIHBvc3Np
YmxlIGZvciBhbiBhdHRhY2tlciB0byBpbmplY3QgIGEgUERVIGZhbHNlbHkgaW5kaWNhdGluZw0K
dGhlcmUgaXMgYSBkdXBsaWNhdGUgc3lzdGVtLWlkLiBUaGlzIG1heSB0cmlnZ2VyIGF1dG9tYXRp
YyByZXN0YXJ0IG9mIHRoZSBwcm90b2NvbCB1c2luZyB0aGUgZHVwbGljYXRlLWlkDQpyZXNvbHV0
aW9uIHByb2NlZHVyZXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50LiANCg0KTm90ZSB0aGF0IHRo
ZSB1c2Ugb2YgYXV0aGVudGljYXRpb24gaXMgaW5jb21wYXRpYmxlIHdpdGggYXV0by0NCmNvbmZp
Z3VyYXRpb24gYXMgaXQgcmVxdWlyZXMgc29tZSBtYW51YWwgY29uZmlndXJhdGlvbi4NCg0KICAg
Rm9yIHdpcmVkIGRlcGxveW1lbnQsIHRoZSB3aXJlZCBjb25uZWN0aW9uIGl0c2VsZiBjb3VsZCBi
ZSBjb25zaWRlcmVkDQogICBhcyBhbiBpbXBsaWNpdCBhdXRoZW50aWNhdGlvbiBpbiB0aGF0IHVu
d2FudGVkIHJvdXRlcnMgYXJlIHVzdWFsbHkNCiAgIG5vdCBhYmxlIHRvIGNvbm5lY3QgKGkuZS4g
dGhlcmUgaXMgc29tZSBraW5kIG9mIHBoeXNpY2FsIHNlY3VyaXR5IGluDQogICBwbGFjZSBwcmV2
ZW50aW5nIHRoZSBjb25uZWN0aW9uIG9mIHJvZ3VlIGRldmljZXMpOyBmb3Igd2lyZWxlc3MNCiAg
IGRlcGxveW1lbnQsIHRoZSBhdXRoZW50aWNhdGlvbiBjb3VsZCBiZSBhY2hpZXZlZCBhdCB0aGUg
bG93ZXINCiAgIHdpcmVsZXNzIGxpbmsgbGF5ZXIuIg0KDQo/Pz8NCg0KDQoNCg0K


From nobody Mon Apr 10 10:36:05 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE319129A96; Mon, 10 Apr 2017 10:35:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zk1vo9YZg61H; Mon, 10 Apr 2017 10:35:57 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8A16E1294EC; Mon, 10 Apr 2017 10:35:52 -0700 (PDT)
Received: from unescapeable.local ([148.87.66.203]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v3AHZgY8051381 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 10 Apr 2017 12:35:42 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [148.87.66.203] claimed to be unescapeable.local
To: "Alvaro Retana (aretana)" <aretana@cisco.com>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "Liubing (Leo)" <leo.liubing@huawei.com>, "gen-art@ietf.org" <gen-art@ietf.org>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com> <c3a3a16110cb44c182413d993377de6d@XCH-ALN-001.cisco.com> <DC9299D1-F989-471C-A7AC-1A5E9C9288AB@cisco.com>
Cc: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
Message-ID: <adbc350e-f516-75da-ae9c-458cae1b91da@nostrum.com>
Date: Mon, 10 Apr 2017 13:35:39 -0400
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: <DC9299D1-F989-471C-A7AC-1A5E9C9288AB@cisco.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/_oM8TENdefegh_Sn8IyrORUUDy8>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Apr 2017 17:35:58 -0000

+1


On 4/10/17 1:32 PM, Alvaro Retana (aretana) wrote:
> Works for me!
>
> Thanks!
>
> Alvaro.
>
>
>
>
>
> On 4/10/17, 10:34 AM, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com> wrote:
>
> Bing/Robert/Alvaro -
>
> Here is the existing text of the Security Section:
>
>    "In general, the use of authentication is incompatible with auto-
>     configuration as it requires some manual configuration.
>
>     For wired deployment, the wired connection itself could be considered
>     as an implicit authentication in that unwanted routers are usually
>     not able to connect (i.e. there is some kind of physical security in
>     place preventing the connection of rogue devices); for wireless
>     deployment, the authentication could be achieved at the lower
>     wireless link layer."
>
>
> Proposed revision:
>
> "In the absence of cryptographic authentication it is possible for an attacker to inject  a PDU falsely indicating
> there is a duplicate system-id. This may trigger automatic restart of the protocol using the duplicate-id
> resolution procedures defined in this document.
>
> Note that the use of authentication is incompatible with auto-
> configuration as it requires some manual configuration.
>
>     For wired deployment, the wired connection itself could be considered
>     as an implicit authentication in that unwanted routers are usually
>     not able to connect (i.e. there is some kind of physical security in
>     place preventing the connection of rogue devices); for wireless
>     deployment, the authentication could be achieved at the lower
>     wireless link layer."
>
> ???
>
>
>
>


From nobody Mon Apr 10 18:26:24 2017
Return-Path: <worley@ariadne.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CF23129417; Mon, 10 Apr 2017 18:26:16 -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
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149187397615.15779.7399941790518824590@ietfa.amsl.com>
Date: Mon, 10 Apr 2017 18:26:16 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/HFWwslKG23ZBKBrF_1QE3JGNPdk>
Subject: [Gen-art] Genart last call review of draft-ietf-grow-bgp-reject-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 01:26:16 -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.

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

Document:  draft-ietf-grow-bgp-reject-04
Reviewer:  Dale R. Worley
Review Date:  2017-04-10
IETF LC End Date:  2017-04-18
IESG Telechat date:  not scheduled

Summary:  This draft is basically ready for publication, but has nits
that should be fixed before publication.

This is the shortest draft I've ever reviewed.  There are only 41
lines of text that contain technical content.

My knowledge of BGP is quite limited, so I cannot review the
desirability of this solution.  I assume that the routing and
operations community has fully considered that question.

I find the wording of section 2 to be poor:

   2.  Solution Requirements

   The following requirements apply to the solution described in this
   document:

   o  Software MUST consider any routes ineligible for route
selection
      (section 9.1.1 [RFC4271]), if no import policy was configured
for
      the EBGP peer.

   o  Software MUST NOT advertise any routes to an EBGP peer, if no
      export policy was configured.

   o  Software SHOULD fall back to an "import nothing" and "export
      nothing" mode following failure of internal components, such as
a
      policy engine.

   o  Software MUST operate in this mode by default.

   o  Software MAY provide a configuration option to disable this
      security capability.

First, section 2 isn't the requirements for the solution, but the
requirements *on BGP speakers* constitute the solution itself.
Second, "software" seems to be a misnomer for "BGP speaker". 
(Compare
with RFC 4271.)  Third, the interaction of the final item with the
2119 words in the preceding items is awkward.  Fourth, it seems that
"routes" in the first item should be qualified by "advertised by an
EBGP peer".  In all cases, what is intended is clear, but the words
don't seem to say it well.

Revising the phrasing, I get:

   2.  Solution

   The following requirements apply to all BGP speakers:

   o A BGP speaker MUST consider any routes advertised by an EBGP
peer
      ineligible for route selection (section 9.1.1 [RFC4271]), if no
      import policy was configured for the peer.

   o  A BGP speaker MUST NOT advertise any routes to an EBGP peer, if
no
      export policy was configured.

   o  A BGP speaker SHOULD fall back to an "import nothing" and
"export
      nothing" mode following failure of internal components, such as
a
      policy engine.

   o  A BGP speaker MAY provide a configuration option to disable the
      preceding behaviors, but it MUST implement them by default.



From nobody Mon Apr 10 18:44:54 2017
Return-Path: <leo.liubing@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF5C11293F2; Mon, 10 Apr 2017 18:44:52 -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 5rDaruX32T6A; Mon, 10 Apr 2017 18:44:50 -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 A749D128BB7; Mon, 10 Apr 2017 18:44:48 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML714-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DEM15405; Tue, 11 Apr 2017 01:44:45 +0000 (GMT)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by LHREML714-CAH.china.huawei.com (10.201.108.37) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 11 Apr 2017 02:44:44 +0100
Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.121]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0235.001; Tue, 11 Apr 2017 09:44:40 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: Robert Sparks <rjsparks@nostrum.com>, "Alvaro Retana (aretana)" <aretana@cisco.com>, "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "draft-ietf-isis-auto-conf.all@ietf.org" <draft-ietf-isis-auto-conf.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "isis-wg@ietf.org" <isis-wg@ietf.org>
Thread-Topic: Genart last call review of draft-ietf-isis-auto-conf-04
Thread-Index: AQHSr90I1Qr5MFU/1kyZBIn9T3xh16G53MgAgAAGPoCAAANtAIAABASAgAAQtoCABGROEP//ycMAgAAxw4CAAADlgIABDlAA
Date: Tue, 11 Apr 2017 01:44:40 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED881A@nkgeml514-mbs.china.huawei.com>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com> <814d03ced1c64f18b20d23c65e7cdf04@XCH-ALN-001.cisco.com> <8469f915-7e13-dead-7a4e-ab36506948da@nostrum.com> <1fd1507c9d5442d0a944e35da9b38b1d@XCH-ALN-001.cisco.com> <EDD33B73-CDF2-42AB-AE8A-96073F449997@cisco.com> <db59f122a2d84c28851944a50f1564a2@XCH-ALN-001.cisco.com> <8AE0F17B87264D4CAC7DE0AA6C406F45C2ED8506@nkgeml514-mbs.china.huawei.com> <c3a3a16110cb44c182413d993377de6d@XCH-ALN-001.cisco.com> <DC9299D1-F989-471C-A7AC-1A5E9C9288AB@cisco.com> <adbc350e-f516-75da-ae9c-458cae1b91da@nostrum.com>
In-Reply-To: <adbc350e-f516-75da-ae9c-458cae1b91da@nostrum.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.191.175]
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.0A0B0205.58EC350E.0015, ss=1, re=0.000, recu=0.000, reip=0.000,  cl=1, cld=1, fgs=0, ip=169.254.3.121, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 9ea5c2356683d7cef74a5744d7b6aa9a
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/KXPLnhp5kyqjAE5FYHxIw9Cq6ZU>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 01:44:53 -0000

SGkgTGVzLCBSb2JlcnQgYW5kIEFsdmFybywNCg0KVGhhbmtzIGZvciBMZXMnIHByb3Bvc2VkIHRl
eHQuIEknbGwgdXBkYXRlIGl0IGFjY29yZGluZ2x5Lg0KDQpCLlIuDQpCaW5nDQoNCg0KPiAtLS0t
LU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBSb2JlcnQgU3BhcmtzIFttYWlsdG86cmpz
cGFya3NAbm9zdHJ1bS5jb21dDQo+IFNlbnQ6IFR1ZXNkYXksIEFwcmlsIDExLCAyMDE3IDE6MzYg
QU0NCj4gVG86IEFsdmFybyBSZXRhbmEgKGFyZXRhbmEpOyBMZXMgR2luc2JlcmcgKGdpbnNiZXJn
KTsgTGl1YmluZyAoTGVvKTsNCj4gZ2VuLWFydEBpZXRmLm9yZw0KPiBDYzogZHJhZnQtaWV0Zi1p
c2lzLWF1dG8tY29uZi5hbGxAaWV0Zi5vcmc7IGlldGZAaWV0Zi5vcmc7IGlzaXMtd2dAaWV0Zi5v
cmcNCj4gU3ViamVjdDogUmU6IEdlbmFydCBsYXN0IGNhbGwgcmV2aWV3IG9mIGRyYWZ0LWlldGYt
aXNpcy1hdXRvLWNvbmYtMDQNCj4gDQo+ICsxDQo+IA0KPiANCj4gT24gNC8xMC8xNyAxOjMyIFBN
LCBBbHZhcm8gUmV0YW5hIChhcmV0YW5hKSB3cm90ZToNCj4gPiBXb3JrcyBmb3IgbWUhDQo+ID4N
Cj4gPiBUaGFua3MhDQo+ID4NCj4gPiBBbHZhcm8uDQo+ID4NCj4gPg0KPiA+DQo+ID4NCj4gPg0K
PiA+IE9uIDQvMTAvMTcsIDEwOjM0IEFNLCAiTGVzIEdpbnNiZXJnIChnaW5zYmVyZykiIDxnaW5z
YmVyZ0BjaXNjby5jb20+DQo+IHdyb3RlOg0KPiA+DQo+ID4gQmluZy9Sb2JlcnQvQWx2YXJvIC0N
Cj4gPg0KPiA+IEhlcmUgaXMgdGhlIGV4aXN0aW5nIHRleHQgb2YgdGhlIFNlY3VyaXR5IFNlY3Rp
b246DQo+ID4NCj4gPiAgICAiSW4gZ2VuZXJhbCwgdGhlIHVzZSBvZiBhdXRoZW50aWNhdGlvbiBp
cyBpbmNvbXBhdGlibGUgd2l0aCBhdXRvLQ0KPiA+ICAgICBjb25maWd1cmF0aW9uIGFzIGl0IHJl
cXVpcmVzIHNvbWUgbWFudWFsIGNvbmZpZ3VyYXRpb24uDQo+ID4NCj4gPiAgICAgRm9yIHdpcmVk
IGRlcGxveW1lbnQsIHRoZSB3aXJlZCBjb25uZWN0aW9uIGl0c2VsZiBjb3VsZCBiZQ0KPiBjb25z
aWRlcmVkDQo+ID4gICAgIGFzIGFuIGltcGxpY2l0IGF1dGhlbnRpY2F0aW9uIGluIHRoYXQgdW53
YW50ZWQgcm91dGVycyBhcmUgdXN1YWxseQ0KPiA+ICAgICBub3QgYWJsZSB0byBjb25uZWN0IChp
LmUuIHRoZXJlIGlzIHNvbWUga2luZCBvZiBwaHlzaWNhbCBzZWN1cml0eSBpbg0KPiA+ICAgICBw
bGFjZSBwcmV2ZW50aW5nIHRoZSBjb25uZWN0aW9uIG9mIHJvZ3VlIGRldmljZXMpOyBmb3Igd2ly
ZWxlc3MNCj4gPiAgICAgZGVwbG95bWVudCwgdGhlIGF1dGhlbnRpY2F0aW9uIGNvdWxkIGJlIGFj
aGlldmVkIGF0IHRoZSBsb3dlcg0KPiA+ICAgICB3aXJlbGVzcyBsaW5rIGxheWVyLiINCj4gPg0K
PiA+DQo+ID4gUHJvcG9zZWQgcmV2aXNpb246DQo+ID4NCj4gPiAiSW4gdGhlIGFic2VuY2Ugb2Yg
Y3J5cHRvZ3JhcGhpYyBhdXRoZW50aWNhdGlvbiBpdCBpcyBwb3NzaWJsZSBmb3IgYW4NCj4gPiBh
dHRhY2tlciB0byBpbmplY3QgIGEgUERVIGZhbHNlbHkgaW5kaWNhdGluZyB0aGVyZSBpcyBhIGR1
cGxpY2F0ZQ0KPiA+IHN5c3RlbS1pZC4gVGhpcyBtYXkgdHJpZ2dlciBhdXRvbWF0aWMgcmVzdGFy
dCBvZiB0aGUgcHJvdG9jb2wgdXNpbmcgdGhlDQo+IGR1cGxpY2F0ZS1pZCByZXNvbHV0aW9uIHBy
b2NlZHVyZXMgZGVmaW5lZCBpbiB0aGlzIGRvY3VtZW50Lg0KPiA+DQo+ID4gTm90ZSB0aGF0IHRo
ZSB1c2Ugb2YgYXV0aGVudGljYXRpb24gaXMgaW5jb21wYXRpYmxlIHdpdGggYXV0by0NCj4gPiBj
b25maWd1cmF0aW9uIGFzIGl0IHJlcXVpcmVzIHNvbWUgbWFudWFsIGNvbmZpZ3VyYXRpb24uDQo+
ID4NCj4gPiAgICAgRm9yIHdpcmVkIGRlcGxveW1lbnQsIHRoZSB3aXJlZCBjb25uZWN0aW9uIGl0
c2VsZiBjb3VsZCBiZQ0KPiBjb25zaWRlcmVkDQo+ID4gICAgIGFzIGFuIGltcGxpY2l0IGF1dGhl
bnRpY2F0aW9uIGluIHRoYXQgdW53YW50ZWQgcm91dGVycyBhcmUgdXN1YWxseQ0KPiA+ICAgICBu
b3QgYWJsZSB0byBjb25uZWN0IChpLmUuIHRoZXJlIGlzIHNvbWUga2luZCBvZiBwaHlzaWNhbCBz
ZWN1cml0eSBpbg0KPiA+ICAgICBwbGFjZSBwcmV2ZW50aW5nIHRoZSBjb25uZWN0aW9uIG9mIHJv
Z3VlIGRldmljZXMpOyBmb3Igd2lyZWxlc3MNCj4gPiAgICAgZGVwbG95bWVudCwgdGhlIGF1dGhl
bnRpY2F0aW9uIGNvdWxkIGJlIGFjaGlldmVkIGF0IHRoZSBsb3dlcg0KPiA+ICAgICB3aXJlbGVz
cyBsaW5rIGxheWVyLiINCj4gPg0KPiA+ID8/Pw0KPiA+DQo+ID4NCj4gPg0KPiA+DQoNCg==


From nobody Mon Apr 10 20:09:04 2017
Return-Path: <job@instituut.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6399D129AD1 for <gen-art@ietfa.amsl.com>; Mon, 10 Apr 2017 20:08:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level: 
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, T_HTML_ATTACH=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4wvr2j0WUV2c for <gen-art@ietfa.amsl.com>; Mon, 10 Apr 2017 20:08:56 -0700 (PDT)
Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 13213129573 for <gen-art@ietf.org>; Mon, 10 Apr 2017 20:08:52 -0700 (PDT)
Received: by mail-wm0-f46.google.com with SMTP id t189so50839562wmt.1 for <gen-art@ietf.org>; Mon, 10 Apr 2017 20:08:52 -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=HugrvemqyWmSo0guDatVZqsttkVxqSDItpXFpYQGOmw=; b=Pz0HN0z14vybaj8rmK260veE0KGslifuPw5LMT1ju1WuX4gs15V9h3Cxc7K7uOIO2J pymMuR4EH49tK5LOuSEH7AYnHsj9F9op/8tPKw3XmUeNNedqYHVKljpnLgwlVXLnEBG9 zZQl7EZe2FmDeLuwiYZNHAlI6CorQJVLOEz9H/pDJmSIze7ZG/RLIW9f4wvInVPSmEk2 9IAfzu3A2v4CdJlXechiNYNrDTi3NMr+62GhDN9cCWEbRIlzvEF42hQN5+RaS7hqMB2Y nM5mFpADurgFbgDCEr8sSiCZAEs9mdk6ynLKATk7VQtt8AfCzGyqOuQxlflONh+g3vGC f5ug==
X-Gm-Message-State: AN3rC/5P8K5VV7Det4MpJqTETPJLI/VGVLBVqe63HSzP86vF8bK0UFkg mtf5ibe7xHfiSlpcLkynMg==
X-Received: by 10.28.66.77 with SMTP id p74mr13233357wma.107.1491880131345; Mon, 10 Apr 2017 20:08:51 -0700 (PDT)
Received: from localhost ([89.248.135.158]) by smtp.gmail.com with ESMTPSA id r5sm19672249wra.50.2017.04.10.20.08.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Apr 2017 20:08:49 -0700 (PDT)
Date: Tue, 11 Apr 2017 05:08:47 +0200
From: Job Snijders <job@ntt.net>
To: Dale Worley <worley@ariadne.com>
Cc: gen-art@ietf.org, draft-ietf-grow-bgp-reject.all@ietf.org, grow@ietf.org, ietf@ietf.org
Message-ID: <20170411030847.vxjgzavkwkj2ge2j@Vurt.local>
References: <149187397615.15779.7399941790518824590@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="zhmrpzekvruzsstz"
Content-Disposition: inline
In-Reply-To: <149187397615.15779.7399941790518824590@ietfa.amsl.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/4W5xe9_61GMTrxmIJWFX4T75eIs>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-bgp-reject-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 03:08:59 -0000

--zhmrpzekvruzsstz
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Dear Dale, 

I'd be happy to incorporate these changes. I appreciate that you
clarified the text.

Attached is an easy-to-read html rfcdiff which contains Dale Worley's
proposed changes verbatim. Unless someone speaks up against this
proposal, I'll upload this as a new -05 revision somewhere in the next
few days.

Kind regards,

Job

On Mon, Apr 10, 2017 at 06:26:16PM -0700, Dale Worley wrote:
> 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.
> 
> For more information, please see the FAQ at
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> 
> Document:  draft-ietf-grow-bgp-reject-04
> Reviewer:  Dale R. Worley
> Review Date:  2017-04-10
> IETF LC End Date:  2017-04-18
> IESG Telechat date:  not scheduled
> 
> Summary:  This draft is basically ready for publication, but has nits
> that should be fixed before publication.
> 
> This is the shortest draft I've ever reviewed.  There are only 41
> lines of text that contain technical content.
> 
> My knowledge of BGP is quite limited, so I cannot review the
> desirability of this solution.  I assume that the routing and
> operations community has fully considered that question.
> 
> I find the wording of section 2 to be poor:
> 
>    2.  Solution Requirements
> 
>    The following requirements apply to the solution described in this
>    document:
> 
>    o  Software MUST consider any routes ineligible for route selection
>       (section 9.1.1 [RFC4271]), if no import policy was configured
>       for the EBGP peer.
> 
>    o  Software MUST NOT advertise any routes to an EBGP peer, if no
>       export policy was configured.
> 
>    o  Software SHOULD fall back to an "import nothing" and "export
>       nothing" mode following failure of internal components, such as
>       a policy engine.
> 
>    o  Software MUST operate in this mode by default.
> 
>    o  Software MAY provide a configuration option to disable this
>       security capability.
> 
> First, section 2 isn't the requirements for the solution, but the
> requirements *on BGP speakers* constitute the solution itself.
> Second, "software" seems to be a misnomer for "BGP speaker".  (Compare
> with RFC 4271.)  Third, the interaction of the final item with the
> 2119 words in the preceding items is awkward.  Fourth, it seems that
> "routes" in the first item should be qualified by "advertised by an
> EBGP peer".  In all cases, what is intended is clear, but the words
> don't seem to say it well.
> 
> Revising the phrasing, I get:
> 
>    2.  Solution
> 
>    The following requirements apply to all BGP speakers:
> 
>    o A BGP speaker MUST consider any routes advertised by an EBGP peer
>      ineligible for route selection (section 9.1.1 [RFC4271]), if no
>      import policy was configured for the peer.
> 
>    o  A BGP speaker MUST NOT advertise any routes to an EBGP peer, if
>       no export policy was configured.
> 
>    o  A BGP speaker SHOULD fall back to an "import nothing" and
>       "export nothing" mode following failure of internal components,
>       such as a policy engine.
> 
>    o  A BGP speaker MAY provide a configuration option to disable the
>       preceding behaviors, but it MUST implement them by default.

--zhmrpzekvruzsstz
Content-Type: text/html; charset=us-ascii
Content-Disposition: attachment; filename="draft-ietf-grow-bgp-reject-05-from-4.diff.html"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<!-- Generated by rfcdiff 1.41: rfcdiff  --> 
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
<!-- System: Darwin Vurt.local 16.5.0 Darwin Kernel Version 16.5.0: Fri Mar  3 16:45:33 PST 2017; root:xnu-3789.51.2~1/RELEASE_X86_64 x86_64 --> 
<!-- Using awk: /usr/local/bin/gawk: GNU Awk 4.1.4, API: 1.1 (GNU MPFR 3.1.5, GNU MP 6.1.2) --> 
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 2.8.1 --> 
<!-- Using wdiff: /usr/local/bin/wdiff: wdiff (GNU wdiff) 1.2.2 --> 
<html> 
<head> 
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
  <meta http-equiv="Content-Style-Type" content="text/css" /> 
  <title>Diff: draft-ietf-grow-bgp-reject-04.txt - draft-ietf-grow-bgp-reject-05.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body > 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tr bgcolor="orange"><th></th><th>&nbsp;draft-ietf-grow-bgp-reject-04.txt&nbsp;</th><th> </th><th>&nbsp;draft-ietf-grow-bgp-reject-05.txt&nbsp;</th><th></th></tr> 
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Global Routing Operations                                       J. Mauch</td><td> </td><td class="right">Global Routing Operations                                       J. Mauch</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Internet-Draft                                                    Akamai</td><td> </td><td class="right">Internet-Draft                                                    Akamai</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Intended status: Standards Track                             J. Snijders</td><td> </td><td class="right">Intended status: Standards Track                             J. Snijders</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">Expires: <span class="delete">September 28, 2017</span>                                          NTT</td><td> </td><td class="rblock">Expires: <span class="insert">October 13, 2017  </span>                                          NTT</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                                                              G. Hankins</td><td> </td><td class="right">                                                              G. Hankins</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">                                                                   Nokia</td><td> </td><td class="right">                                                                   Nokia</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                          <span class="delete">March 27</span>, 2017</td><td> </td><td class="rblock">                                                          <span class="insert">April 11</span>, 2017</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">        Default EBGP Route Propagation Behavior Without Policies</td><td> </td><td class="right">        Default EBGP Route Propagation Behavior Without Policies</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                     draft-ietf-grow-bgp-reject-0<span class="delete">4</span></td><td> </td><td class="rblock">                     draft-ietf-grow-bgp-reject-0<span class="insert">5</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Abstract</td><td> </td><td class="right">Abstract</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document defines the default behavior of a BGP speaker when</td><td> </td><td class="right">   This document defines the default behavior of a BGP speaker when</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   there is no import or export policy associated with an External BGP</td><td> </td><td class="right">   there is no import or export policy associated with an External BGP</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   session.</td><td> </td><td class="right">   session.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Requirements Language</td><td> </td><td class="right">Requirements Language</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td> </td><td class="right">   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l2" /><small>skipping to change at</small><em> page 1, line 41</em></th><th> </th><th><a name="part-r2" /><small>skipping to change at</small><em> page 1, line 41</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are working documents of the Internet Engineering</td><td> </td><td class="right">   Internet-Drafts are working documents of the Internet Engineering</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Task Force (IETF).  Note that other groups may also distribute</td><td> </td><td class="right">   Task Force (IETF).  Note that other groups may also distribute</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   working documents as Internet-Drafts.  The list of current Internet-</td><td> </td><td class="right">   working documents as Internet-Drafts.  The list of current Internet-</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td> </td><td class="right">   Drafts is at http://datatracker.ietf.org/drafts/current/.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Internet-Drafts are draft documents valid for a maximum of six months</td><td> </td><td class="right">   Internet-Drafts are draft documents valid for a maximum of six months</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   and may be updated, replaced, or obsoleted by other documents at any</td><td> </td><td class="right">   and may be updated, replaced, or obsoleted by other documents at any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   time.  It is inappropriate to use Internet-Drafts as reference</td><td> </td><td class="right">   time.  It is inappropriate to use Internet-Drafts as reference</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   material or to cite them other than as "work in progress."</td><td> </td><td class="right">   material or to cite them other than as "work in progress."</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   This Internet-Draft will expire on <span class="delete">September 28</span>, 2017.</td><td> </td><td class="rblock">   This Internet-Draft will expire on <span class="insert">October 13</span>, 2017.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Copyright Notice</td><td> </td><td class="right">Copyright Notice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Copyright (c) 2017 IETF Trust and the persons identified as the</td><td> </td><td class="right">   Copyright (c) 2017 IETF Trust and the persons identified as the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   document authors.  All rights reserved.</td><td> </td><td class="right">   document authors.  All rights reserved.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td> </td><td class="right">   This document is subject to BCP 78 and the IETF Trust's Legal</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Provisions Relating to IETF Documents</td><td> </td><td class="right">   Provisions Relating to IETF Documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td> </td><td class="right">   (http://trustee.ietf.org/license-info) in effect on the date of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   publication of this document.  Please review these documents</td><td> </td><td class="right">   publication of this document.  Please review these documents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   carefully, as they describe your rights and restrictions with respect</td><td> </td><td class="right">   carefully, as they describe your rights and restrictions with respect</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   to this document.  Code Components extracted from this document must</td><td> </td><td class="right">   to this document.  Code Components extracted from this document must</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   include Simplified BSD License text as described in Section 4.e of</td><td> </td><td class="right">   include Simplified BSD License text as described in Section 4.e of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   the Trust Legal Provisions and are provided without warranty as</td><td> </td><td class="right">   the Trust Legal Provisions and are provided without warranty as</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   described in the Simplified BSD License.</td><td> </td><td class="right">   described in the Simplified BSD License.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Table of Contents</td><td> </td><td class="right">Table of Contents</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2</td><td> </td><td class="right">   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   2.  Solution <span class="delete">Requirements</span> . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="rblock">   2.  Solution <span class="insert"> . . . . . .</span> . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   3.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   3.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   3</td><td> </td><td class="right">   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   3</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">     7.2.  Informative References  . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4</td><td> </td><td class="right">   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   4</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">1.  Introduction</td><td> </td><td class="right">1.  Introduction</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l3" /><small>skipping to change at</small><em> page 3, line 5</em></th><th> </th><th><a name="part-r3" /><small>skipping to change at</small><em> page 3, line 5</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   interconnected, the risk of a misbehaving BGP speaker poses</td><td> </td><td class="right">   interconnected, the risk of a misbehaving BGP speaker poses</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   significant risks to Internet routing.</td><td> </td><td class="right">   significant risks to Internet routing.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This specification intends to improve this situation by requiring the</td><td> </td><td class="right">   This specification intends to improve this situation by requiring the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   explicit configuration of a BGP import and export policy for any</td><td> </td><td class="right">   explicit configuration of a BGP import and export policy for any</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   External BGP (EBGP) session such as customers, peers, or</td><td> </td><td class="right">   External BGP (EBGP) session such as customers, peers, or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   confederation boundaries for all enabled address families.  When this</td><td> </td><td class="right">   confederation boundaries for all enabled address families.  When this</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   solution is implemented, BGP speakers do not accept or send routes</td><td> </td><td class="right">   solution is implemented, BGP speakers do not accept or send routes</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   without policies configured on EBGP sessions.</td><td> </td><td class="right">   without policies configured on EBGP sessions.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">2.  Solution<span class="delete"> Requirements</span></td><td> </td><td class="rblock">2.  Solution</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0007" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   The following requirements apply to <span class="delete">the solution described in this</span></td><td> </td><td class="rblock">   The following requirements apply to <span class="insert">all BGP speakers:</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   document:</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0008" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  <span class="delete">Software MUST consider any routes ineligible for route selection</span></td><td> </td><td class="rblock">   o  <span class="insert">A BGP speaker MUST consider any routes advertised by an EBGP peer</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      (section 9.1.1 [RFC4271]), if no import policy was configured for</td><td> </td><td class="right">      (section 9.1.1 [RFC4271]), if no import policy was configured for</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0009" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">      the <span class="delete">EBGP </span>peer.</td><td> </td><td class="rblock">      the peer.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0010" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  <span class="delete">Software</span> MUST NOT advertise any routes to an EBGP peer, if no</td><td> </td><td class="rblock">   o  <span class="insert">A BGP speaker</span> MUST NOT advertise any routes to an EBGP peer, if no</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      export policy was configured.</td><td> </td><td class="right">      export policy was configured.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0011" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  <span class="delete">Software</span> SHOULD fall back to an "import nothing" and "export</td><td> </td><td class="rblock">   o  <span class="insert">A BGP speaker</span> SHOULD fall back to an "import nothing" and "export</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      nothing" mode following failure of internal components, such as a</td><td> </td><td class="right">      nothing" mode following failure of internal components, such as a</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">      policy engine.</td><td> </td><td class="right">      policy engine.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0012" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   o  <span class="delete">Software MUST operate in this mode by default.</span></td><td> </td><td class="rblock">   o  <span class="insert">A BGP speaker</span> MAY provide a configuration option to disable <span class="insert">the</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete"></span></td><td> </td><td class="rblock"><span class="insert">      preceding behaviors, but it MUST implement them by default.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">   o  Software</span> MAY provide a configuration option to disable <span class="delete">this</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">      security capability.</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">3.  Acknowledgments</td><td> </td><td class="right">3.  Acknowledgments</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   The authors would like to thank the following people for their</td><td> </td><td class="right">   The authors would like to thank the following people for their</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   comments, support and review: Shane Amante, Christopher Morrow,</td><td> </td><td class="right">   comments, support and review: Shane Amante, Christopher Morrow,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   Robert Raszuk, Greg Skinner, Adam Chappell, Sriram Kotikalapudi,</td><td> </td><td class="right">   Robert Raszuk, Greg Skinner, Adam Chappell, Sriram Kotikalapudi,</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0013" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   Brian Dickson, Jeffrey Haas, John Heasley, Ignas <span class="delete">Bagdonas and</span> Donald</td><td> </td><td class="rblock">   Brian Dickson, Jeffrey Haas, John Heasley, Ignas <span class="insert">Bagdonas,</span> Donald</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">   <span class="delete">Smith.</span></td><td> </td><td class="rblock">   <span class="insert">Smith, and Dale Worley.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">4.  Security Considerations</td><td> </td><td class="right">4.  Security Considerations</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   This document addresses a basic routing security issue caused by</td><td> </td><td class="right">   This document addresses a basic routing security issue caused by</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   permissive default routing policy configurations.  Operators need</td><td> </td><td class="right">   permissive default routing policy configurations.  Operators need</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   implementers to address this problem with more secure defaults to</td><td> </td><td class="right">   implementers to address this problem with more secure defaults to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   mitigate collateral damage on Internet routing.  Inadvertent or</td><td> </td><td class="right">   mitigate collateral damage on Internet routing.  Inadvertent or</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   adversarial advertisements cause business impact that can be</td><td> </td><td class="right">   adversarial advertisements cause business impact that can be</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">   mitigated by a secure default behavior.</td><td> </td><td class="right">   mitigated by a secure default behavior.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 13 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>18 lines changed or deleted</i></th><th><i> </i></th><th><i>15 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.41. The latest version is available from <a href="http://www.tools.ietf.org/tools/rfcdiff/" >http://tools.ietf.org/tools/rfcdiff/</a> </td></tr>
   </table>
   </body>
   </html>

--zhmrpzekvruzsstz--


From nobody Tue Apr 11 02:55:25 2017
Return-Path: <Jonathan.Hardwick@metaswitch.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3DA4127071; Tue, 11 Apr 2017 02:55:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_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=metaswitch.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7BvvnbrPFPXB; Tue, 11 Apr 2017 02:55:21 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0094.outbound.protection.outlook.com [104.47.38.94]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68C36129329; Tue, 11 Apr 2017 02:55:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=metaswitch.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=b9HETZbL8j2CzLb+MsfxZDwMCVL8Zj5oXcgY7WjUSBg=; b=mLpJtzmhimVYec0Yt8UKwjjGIb6RM6v4uTyACslRrFs3uO+5NuqWcwwzGHv5Dt5vLJsz26SIQyTpufPyIFhwyAtF+MSkfpXIfi50v6IVcYg1tAiZWHX1kUTXyIsXMsBiK6dBBs0SSDmKoTAAB/5vlgHM02V0s6XfnnPmRJbHQHA=
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com (10.163.75.152) by BY2PR0201MB1910.namprd02.prod.outlook.com (10.163.75.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1019.17; Tue, 11 Apr 2017 09:55:18 +0000
Received: from BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) by BY2PR0201MB1910.namprd02.prod.outlook.com ([10.163.75.152]) with mapi id 15.01.1019.025; Tue, 11 Apr 2017 09:55:18 +0000
From: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>
To: Joel Halpern <jmh@joelhalpern.com>
CC: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Review of draft-ietf-pce-stateful-pce-18
Thread-Index: AQHSiM898qSTLMFhq0+xLX5nlZUWFKG/9CxQ
Date: Tue, 11 Apr 2017 09:55:17 +0000
Message-ID: <BY2PR0201MB191095098C1B48E5661CED6384000@BY2PR0201MB1910.namprd02.prod.outlook.com>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
In-Reply-To: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: joelhalpern.com; dkim=none (message not signed) header.d=none;joelhalpern.com; dmarc=none action=none header.from=metaswitch.com;
x-originating-ip: [86.132.76.121]
x-microsoft-exchange-diagnostics: 1; BY2PR0201MB1910; 7:0KiugvFB4MZ2dcC02gs2lCwTptPiz2jonC9SPkwJtsETaNkPehF/npjBNqjXJWQ6PXEp5DoVXQ8SWLQBRq0f3Y71QrqjFChqFMKCSwgheCp08lerPqlhKsnd2f2YUkXKBq+EfNQsTIcfqRIPM8AVZab3wyIxA0s8beJxU0lpY6cVcnsqPeJEepFcIKy9HD7AE9BKk6E+P+tWqXxuxgLeCyvfLTN4L0OL4UBPqwluLzWHSlhgkXTZ7My5IuE4OMOxBWy8x79LzSxrn844ZFzd/jZCMbSl1PqwTqXoEJF9t53wJJWQoFkfRpPpY8IghlK48bjUawtjcnnOMq6SuOhOGw==
x-ms-office365-filtering-correlation-id: aa5b51c7-e4b9-48b7-7e47-08d480c0dc1e
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:BY2PR0201MB1910; 
x-microsoft-antispam-prvs: <BY2PR0201MB1910CD25773FDB0DA09950F384000@BY2PR0201MB1910.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(20558992708506);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(6041248)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(20161123564025)(20161123562025)(20161123560025)(6072148); SRVR:BY2PR0201MB1910; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0201MB1910; 
x-forefront-prvs: 0274272F87
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39400400002)(39450400003)(39840400002)(66654002)(51914003)(13464003)(37854004)(86362001)(81166006)(8676002)(3280700002)(3660700001)(110136004)(33656002)(8936002)(189998001)(25786009)(5660300001)(4326008)(2906002)(53546009)(6436002)(230783001)(102836003)(2900100001)(6116002)(122556002)(38730400002)(3846002)(229853002)(2950100002)(54356999)(76176999)(6916009)(305945005)(50986999)(66066001)(7696004)(6506006)(77096006)(54906002)(99286003)(55016002)(53936002)(74316002)(6246003)(7736002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0201MB1910; H:BY2PR0201MB1910.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: metaswitch.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Apr 2017 09:55:17.7351 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9d9e56eb-f613-4ddb-b27b-bfcdf14b2cdb
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB1910
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/XAZEeQfqAk1RE1ugWyrKHo3s64c>
Subject: Re: [Gen-art] Review of draft-ietf-pce-stateful-pce-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 09:55:24 -0000

SGkgSm9lbA0KDQpNYW55IHRoYW5rcyBmb3IgdGhlc2UgY29tbWVudHMuICBJJ20gcGlja2luZyB1
cCB0aGlzIHRocmVhZCBhbmQgcmVwbHlpbmcgYXMgUENFIHdvcmtpbmcgZ3JvdXAgY2hhaXIsIGFz
IHRoZSBhdXRob3JzIGFyZSB1bmF2YWlsYWJsZS4gIEkgYXBvbG9naXNlIGZvciB0aGUgZGVsYXku
DQoNClBsZWFzZSBzZWUgbXkgcHJvcG9zZWQgcmVzb2x1dGlvbnMgaW5saW5lIGJlbG93LCBtYXJr
ZWQgd2l0aCAiSm9uPiINCg0KQmVzdCByZWdhcmRzDQpKb24NCg0KDQotLS0tLU9yaWdpbmFsIE1l
c3NhZ2UtLS0tLQ0KRnJvbTogSm9lbCBIYWxwZXJuIFttYWlsdG86am1oQGpvZWxoYWxwZXJuLmNv
bV0gDQpTZW50OiAxNyBGZWJydWFyeSAyMDE3IDAzOjM4DQpUbzogZ2VuLWFydEBpZXRmLm9yZw0K
Q2M6IGRyYWZ0LWlldGYtcGNlLXN0YXRlZnVsLXBjZS5hbGxAaWV0Zi5vcmc7IHBjZUBpZXRmLm9y
ZzsgaWV0ZkBpZXRmLm9yZw0KU3ViamVjdDogUmV2aWV3IG9mIGRyYWZ0LWlldGYtcGNlLXN0YXRl
ZnVsLXBjZS0xOA0KDQpSZXZpZXdlcjogSm9lbCBIYWxwZXJuDQpSZXZpZXcgcmVzdWx0OiBSZWFk
eSB3aXRoIElzc3Vlcw0KDQo8c25pcD4NCg0KPT09PQ0KDQpNaW5vciBpc3N1ZXM6DQogICBBdCB0
aGUgZW5kIG9mIHNlY3Rpb24gNS40LCB0aGUgdGV4dCB0YWxrcyBhYm91dCBhIFBDRSBhY2NlcHRp
bmcgc3RhdHVzIHVwZGF0ZXMgZXZlbiBpZiB0aGUgIHN0YXRlZnVsIGNhcGFiaWxpdHkgaGFzIG5v
dCBiZWVuIG5lZ290aWF0ZWQuICBXaGljaCBpcyBmaW5lLiAgQnV0IGFzIHdyaXR0ZW4sIHRoZSB0
ZXh0IHNlZW1zIHRvIHNheSB0aGF0IGRvaW5nIHNvIG1lYW5zIHRoYXQgdGhlIFBDRSB3aWxsIGJl
IGFibGUgdG8gImJ1aWxkIGFuZCBtYWludGFpbiBhbiB1cCB0byBkYXRlIHZpZXcgb2YgdGhlIHN0
YXRlIG9mIHRoZSBQQ0MncyBMU1BzIi4gIEhvd2V2ZXIsIGlmIHRoZSBjYXBhYmlsaXR5IGhhcyBu
b3QgYmVlbiBuZWdvdGlhdGVkLCBJIGRvIG5vdCBzZWUgaG93IHRoZSBQQ0UgY2FuIGNvdW50IG9u
IGdldHRpbmcgZnVsbCBhbmQgdGltZWx5IHN0YXRlIHJlcG9ydHMuICBUcnlpbmcgdG8gaW5mZXIg
d2h5IGEgUENDIGlzIHNlbmRpbmcgc3VjaCBhIHJlcG9ydCBpbiB0aGUgYWJzZW5jZSBvZiB0aGUg
YWdyZWVtZW50IHNlZW1zIHByb2JsZW1hdGljLg0KDQpKb24+IEkgYWdyZWUuICBJIHByb3Bvc2Ug
dGhhdCB3ZSBkZWxldGUgdGhpcyBzZW50ZW5jZToNCiIgTm90ZSB0aGF0IGV2ZW4gaWYgdGhlIHVw
ZGF0ZQ0KICAgY2FwYWJpbGl0eSBoYXMgbm90IGJlZW4gYWR2ZXJ0aXNlZCwgYSBQQ0UgY2FuIHN0
aWxsIGFjY2VwdCBMU1AgU3RhdHVzDQogICBSZXBvcnRzIGZyb20gYSBQQ0MgYW5kIGJ1aWxkIGFu
ZCBtYWludGFpbiBhbiB1cCB0byBkYXRlIHZpZXcgb2YgdGhlDQogICBzdGF0ZSBvZiB0aGUgUEND
J3MgTFNQcy4gIg0KDQo9PT09DQoNCiAgICBUaGlzIGNvbW1lbnQgbWF5IGJlIGEgbWlzdW5kZXJz
dGFuZGluZyBvciBtaXMtZXhwZWN0YXRpb24gb24gbXkgcGFydC4gIEkgd291bGQgaGF2ZSBleHBl
Y3RlZCBvbmUgb2YgdGhlIHdheXMgbyB1c2luZyBhbiBhY3RpdmUgUENFIGlzIHRvIGhhdmUgdGhl
IFBDRSBkZWNpZGUgKHVuZGVyIHN1aXRhYmxlIGNpcmN1bXN0YW5jZXMpIHRoYXQgYW4gTFNQIGlz
IG5lZWRlZCBiZXR3ZWVuIHR3byBQQ0NzLiAgQXMgZmFyIGFzIEkgY2FuIHRlbGwsIHRoZSB0ZXh0
IGluIHNlY3Rpb24NCjUuOC4yIGFuZCA1LjguMyBwcm9oaWJpdHMgdGhhdC4gIEEgUENFIGlzIG9u
bHkgYWxsb3dlZCB0byBzZW5kIGFuIExTUCBVcGRhdGUgUmVxdWVzdCAoaW4gYSBQQ1VwZCBtZXNz
YWdlKSBmb3IgYW4gTFNQIHRoYXQgaGFzIGJlZW4gZGVsZWdhdGVkIHRvIGl0LiAgQXQgdGhhdCBw
b2ludCBJIHRob3VnaHQgdGhhdCBhIFBDQyBjb3VsZCBkZWxlZ2F0ZSBhIGJsb2NrIG9mIHVuc2V0
dXAgTFNQcyB0byB0aGUgUENFLiAgQnV0IHRoZW4gbG9va2luZyBhdCA1LjguMiwgdGhlIHRleHQg
c3RhdGVzIHRoYXQgZm9yIGVhY2ggZGVsZWdhdGlvbiwgdGhlIFBDQyBtdXN0IHJlcXVlc3QgYW4g
aW5pdGlhbCBwYXRoLiAgVGhhdCBzZWVtcyB0byBwcm9oaWJpdCBkZWxlZ2F0aW5nIGEgYmxvY2sg
b2YgTFNQcyBmb3IgZnV0dXJlIHVwZGF0ZXMuICBJcyB0aGUgaW50ZW50aW9uIHRvIHByb2hpYml0
IHRoZSBkcml2aW5nIG9mIExTUCBjcmVhdGlvbiBmcm9tIHRoZSBQQ0U/DQoNCkpvbj4gWWVzLCB0
aGUgaW50ZW50aW9uIGlzIHRoYXQgdGhlIFBDRSBkb2VzIG5vdCBkcml2ZSBjcmVhdGlvbiBvZiB0
aGUgTFNQcy4gIFRoYXQgYmVoYXZpb3VyIGlzIGFsbG93ZWQgYnV0IGlzIGRlc2NyaWJlZCBieSBh
IHNlcGFyYXRlIGRyYWZ0IChkcmFmdC1pZXRmLXBjZS1wY2UtaW5pdGlhdGVkLWxzcCkuICBJIHBy
b3Bvc2UgdG8gY2xhcmlmeSB0aGlzIGluIHRoZSBpbnRyb2R1Y3Rpb24gdG8gdGhlIGRyYWZ0LCBz
byB0aGF0IGZ1dHVyZSByZWFkZXJzIGRvbid0IGdldCBjYXVnaHQgYnkgdGhlIHNhbWUgbWlzLWV4
cGVjdGF0aW9uLiAgV2UnbGwgYWRkIHRoZSBmb2xsb3dpbmcgdGV4dCB0byBzZWN0aW9uIDEsIGFu
ZCBhZGQgYW4gaW5mb3JtYXRpdmUgcmVmZXJlbmNlIHRvIGRyYWZ0LWlldGYtcGNlLXBjZS1pbml0
aWF0ZWQtbHNwLiAgT0s/DQoNCk5FVw0KICAgVGhlIGV4dGVuc2lvbnMgdGhhdCB0aGlzIGRvY3Vt
ZW50IGRlc2NyaWJlcyBkbyBub3QgcGVybWl0IHRoZQ0KICAgUENFIHRvIGRyaXZlIGNyZWF0aW9u
IG9mIGFuIExTUC4gIFRoZSBjb21wYW5pb24gZG9jdW1lbnQNCiAgIFtJLUQuIGlldGYtcGNlLXBj
ZS1pbml0aWF0ZWQtbHNwXSBzcGVjaWZpZXMgUENFLWluaXRpYXRlZCBMU1AgY3JlYXRpb24uDQoN
Cj09PT0NCg0KICAgIEkgaGF2ZSBsb29rZWQgYnV0IEkgY2FuIG5vdCBmaW5kIHRoZSB0ZXh0IGV4
cGxhaW5pbmcgdGhlIHNpZ25pZmljYW5jZSBhbmQgdXNlIG9mIHRoZSBTeW1ib2xpYyBwYXRoIG5h
bWUuICBJdCBpcyBtYW5kYXRlZCBieSB0aGUgZHJhZnQuICBUaGVyZSBzZWVtcyB0byBiZSBhbiBp
bXBsaWNpdCBhc3N1bXB0aW9uIHRhaHQgaXQgaXMgbmVlZGVkIGJ5IHRoZSBQQ0UuICBJZiB0aGUg
ZXhwbGFuYXRpb24gb2YgaG93IG9yIHdoeSBpdCBpcyBuZWVkZWQgaXMgbm90IHByZXNlbnQsIGl0
IHNob3VsZCBiZS4NCg0KSm9uPiBBZ3JlZWQuICBTZXZlcmFsIG9mIG91ciByZXZpZXdlcnMgaGF2
ZSBwaWNrZWQgdXAgb24gdGhpcy4gIEkgdGhpbmsgd2Ugc2hvdWxkIGNsYXJpZnkgdGhpcyBpbiBz
ZWN0aW9uIDcuMy4yICJTeW1ib2xpYyBQYXRoIE5hbWUgVExWIi4NCg0KT0xEDQogICBFYWNoIExT
UCAocGF0aCkgTVVTVCBoYXZlIGEgc3ltYm9saWMgbmFtZSB0aGF0IGlzIHVuaXF1ZSBpbiB0aGUg
UENDLg0KICAgVGhpcyBzeW1ib2xpYyBwYXRoIG5hbWUgTVVTVCByZW1haW4gY29uc3RhbnQgdGhy
b3VnaG91dCBhbiBMU1Ancw0KICAgbGlmZXRpbWUsIHdoaWNoIG1heSBzcGFuIGFjcm9zcyBtdWx0
aXBsZSBjb25zZWN1dGl2ZSBQQ0VQIHNlc3Npb25zDQogICBhbmQvb3IgUENDIHJlc3RhcnRzLiAg
VGhlIHN5bWJvbGljIHBhdGggbmFtZSBNQVkgYmUgc3BlY2lmaWVkIGJ5IGFuDQogICBvcGVyYXRv
ciBpbiBhIFBDQydzIGNvbmZpZ3VyYXRpb24uICBJZiB0aGUgb3BlcmF0b3IgZG9lcyBub3Qgc3Bl
Y2lmeQ0KICAgYSB1bmlxdWUgc3ltYm9saWMgbmFtZSBmb3IgYSBwYXRoLCB0aGUgUENDIE1VU1Qg
YXV0by1nZW5lcmF0ZSBvbmUuDQoNCiAgIFRoZSBTWU1CT0xJQy1QQVRILU5BTUUgVExWIE1VU1Qg
YmUgaW5jbHVkZWQgaW4gdGhlIExTUCBvYmplY3QgaW4gdGhlDQogICBMU1AgU3RhdGUgUmVwb3J0
IChQQ1JwdCkgbWVzc2FnZSB3aGVuIGR1cmluZyBhIGdpdmVuIFBDRVAgc2Vzc2lvbiBhbg0KICAg
TFNQIGlzIGZpcnN0IHJlcG9ydGVkIHRvIGEgUENFLiAgQSBQQ0Mgc2VuZHMgdG8gYSBQQ0UgdGhl
IGZpcnN0IExTUA0KICAgU3RhdGUgUmVwb3J0IGVpdGhlciBkdXJpbmcgU3RhdGUgU3luY2hyb25p
emF0aW9uLCBvciB3aGVuIGEgbmV3IExTUA0KICAgaXMgY29uZmlndXJlZCBhdCB0aGUgUENDLiAg
VGhlIHN5bWJvbGljIHBhdGggbmFtZSBNQVkgYmUgaW5jbHVkZWQgaW4NCiAgIHRoZSBMU1Agb2Jq
ZWN0IGluIHN1YnNlcXVlbnQgTFNQIFN0YXRlIFJlcG9ydHMgZm9yIHRoZSBMU1AuDQoNCiAgIDxz
bmlwPg0KDQogICBTeW1ib2xpYyBQYXRoIE5hbWUgKHZhcmlhYmxlKTogc3ltYm9saWMgbmFtZSBm
b3IgdGhlIExTUCwgdW5pcXVlIGluDQogICB0aGUgUENDLg0KDQpORVcNCiAgIEVhY2ggTFNQIE1V
U1QgaGF2ZSBhIHN5bWJvbGljIHBhdGggbmFtZSB0aGF0IGlzIHVuaXF1ZSBpbiB0aGUgUENDLg0K
ICAgVGhlIHN5bWJvbGljIHBhdGggbmFtZSBpcyBhIGh1bWFuLXJlYWRhYmxlIHN0cmluZyB0aGF0
IGlkZW50aWZpZXMgYW4NCiAgIExTUCBpbiB0aGUgbmV0d29yay4gIFRoZSBzeW1ib2xpYyBwYXRo
IG5hbWUgTVVTVCByZW1haW4gY29uc3RhbnQNCiAgIHRocm91Z2hvdXQgYW4gTFNQJ3MgbGlmZXRp
bWUsIHdoaWNoIG1heSBzcGFuIGFjcm9zcyBtdWx0aXBsZQ0KICAgY29uc2VjdXRpdmUgUENFUCBz
ZXNzaW9ucyBhbmQvb3IgUENDIHJlc3RhcnRzLiAgVGhlIHN5bWJvbGljIHBhdGgNCiAgIG5hbWUg
TUFZIGJlIHNwZWNpZmllZCBieSBhbiBvcGVyYXRvciBpbiBhIFBDQydzIGNvbmZpZ3VyYXRpb24u
ICBJZiB0aGUNCiAgIG9wZXJhdG9yIGRvZXMgbm90IHNwZWNpZnkgYSB1bmlxdWUgc3ltYm9saWMg
bmFtZSBmb3IgYW4gTFNQLCB0aGVuIHRoZQ0KICAgUENDIE1VU1QgYXV0by1nZW5lcmF0ZSBvbmUu
ICAgDQoNCiAgIFRoZSBQQ0UgdXNlcyB0aGUgc3ltYm9saWMgcGF0aCBuYW1lIGFzIGEgc3RhYmxl
IGlkZW50aWZpZXIgZm9yIHRoZSBMU1AuDQogICBJZiB0aGUgUENFUCBzZXNzaW9uIHJlc3RhcnRz
LCBvciB0aGUgUENDIHJlc3RhcnRzLCBvciB0aGUgUENDIHJlLWRlbGVnYXRlcw0KICAgdGhlIExT
UCB0byBhIGRpZmZlcmVudCBQQ0UsIHRoZSBzeW1ib2xpYyBwYXRoIG5hbWUgZm9yIHRoZSBMU1Ag
cmVtYWlucw0KICAgY29uc3RhbnQgYW5kIGNhbiBiZSB1c2VkIHRvIGNvcnJlbGF0ZSBhY3Jvc3Mg
dGhlIFBDRVAgc2Vzc2lvbiBpbnN0YW5jZXMuDQoNCiAgIFRoZSBvdGhlciBwcm90b2NvbCBpZGVu
dGlmaWVycyBmb3IgdGhlIExTUCBjYW5ub3QgcmVsaWFibHkgYmUgdXNlZCB0bw0KICAgaWRlbnRp
ZnkgdGhlIExTUCBhY3Jvc3MgbXVsdGlwbGUgUENFUCBzZXNzaW9ucywgZm9yIHRoZSBmb2xsb3dp
bmcgcmVhc29ucy4NCiAgIC0gIFRoZSBQTFNQLUlEIGlzIHVuaXF1ZSBvbmx5IHdpdGhpbiB0aGUg
c2NvcGUgb2YgYSBzaW5nbGUgUENFUCBzZXNzaW9uLg0KICAgLSAgVGhlIExTUC1JREVOVElGSUVS
UyBUTFYgaXMgb25seSBndWFyYW50ZWVkIHRvIGJlIHByZXNlbnQgZm9yIExTUHMgDQogICAgICB0
aGF0IGFyZSBzaWduYWxsZWQgd2l0aCBSU1ZQLVRFLg0KDQogICBUaGUgU1lNQk9MSUMtUEFUSC1O
QU1FIFRMViBNVVNUIGJlIGluY2x1ZGVkIGluIHRoZSBMU1Agb2JqZWN0IGluIHRoZQ0KICAgTFNQ
IFN0YXRlIFJlcG9ydCAoUENScHQpIG1lc3NhZ2Ugd2hlbiBkdXJpbmcgYSBnaXZlbiBQQ0VQIHNl
c3Npb24gYW4NCiAgIExTUCBpcyBmaXJzdCByZXBvcnRlZCB0byBhIFBDRS4gIEEgUENDIHNlbmRz
IHRvIGEgUENFIHRoZSBmaXJzdCBMU1ANCiAgIFN0YXRlIFJlcG9ydCBlaXRoZXIgZHVyaW5nIFN0
YXRlIFN5bmNocm9uaXphdGlvbiwgb3Igd2hlbiBhIG5ldyBMU1ANCiAgIGlzIGNvbmZpZ3VyZWQg
YXQgdGhlIFBDQy4NCg0KICAgVGhlIGluaXRpYWwgUENScHQgY3JlYXRlcyBhIGJpbmRpbmcgYmV0
d2VlbiB0aGUgc3ltYm9saWMgcGF0aCBuYW1lIGFuZA0KICAgdGhlIFBMU1AtSUQgZm9yIHRoZSBM
U1Agd2hpY2ggbGFzdHMgZm9yIHRoZSBkdXJhdGlvbiBvZiB0aGUgUENFUCBzZXNzaW9uLg0KICAg
VGhlIFBDQyBNQVkgb21pdCB0aGUgc3ltYm9saWMgcGF0aCBuYW1lIGZyb20gc3Vic2VxdWVudCBM
U1AgU3RhdGUNCiAgIFJlcG9ydHMgZm9yIHRoYXQgTFNQIG9uIHRoYXQgUENFUCBzZXNzaW9uLCBh
bmQganVzdCBnaXZlIHRoZSBQTFNQLUlELg0KDQogICA8c25pcD4NCg0KICAgU3ltYm9saWMgUGF0
aCBOYW1lICh2YXJpYWJsZSk6IHN5bWJvbGljIG5hbWUgZm9yIHRoZSBMU1AsIHVuaXF1ZSBpbg0K
ICAgdGhlIFBDQy4gIEl0IFNIT1VMRCBiZSBhIHN0cmluZyBvZiBwcmludGFibGUgQVNDSUkgY2hh
cmFjdGVycyBhbmQgU0hPVUxEDQogICBiZSBOVUxMLXRlcm1pbmF0ZWQuICBUaGUgU3ltYm9saWMg
UGF0aCBOYW1lIChpbmNsdWRpbmcgaXRzIE5VTEwNCiAgIHRlcm1pbmF0b3IpIE1VU1QgYmUgcGFk
ZGVkIHRvIDQtYnl0ZXMgYWxpZ25tZW50OyB0aGUgcGFkZGluZyBpdHNlbGYNCiAgIE1VU1QgTk9U
IGJlIGluY2x1ZGVkIGluIHRoZSBMZW5ndGggZmllbGQuDQoNCkVORCBORVcNCg0KPT09PQ0KDQpO
aXRzL2VkaXRvcmlhbCBjb21tZW50czogDQogICAgU2hvdWxkIHRoZSB0ZXh0IG9uIHRoZSBTIGJp
dCBpbiBzZWN0aW9uIDcuMyAodGhlIExTUCBPYmplY3QNCmRlZmluaXRpb24pIG5vdGUgdGhhdCBp
dCBzaG91bGQgYmUgc2V0IHRvIDAgb24gYWxsIG1lc3NhZ2VzIHNlbnQgYnkgdGhlIFBDRT8gIFNo
b3VsZCB0aGF0IGFsc28gYmUgc3RhdGVkIGZvciB0aGUgUiBiaXQ/ICBBbmQgdGhlIE8gYml0cz8N
Cg0KSm9uPiBZZXMuICBXZSB3aWxsIGFkZCBhIG5vdGUgdG8gdGhlIGRlc2NyaXB0aW9uIG9mIHRo
ZXNlIGZpZWxkcy4NCg0KPT09PQ0KDQogIFNlY3Rpb24gOS4yIHNlZW1zIHZlcnkgb2RkLiAgSXQg
c3RhdGVzIHRoYXQgdGhlIElFVEYgIlNIT1VMRCIgZG8gc29tZSBhZGRpdGlvbmFsIHdvcmsuICBJ
IHVuZGVyc3RhbmQgd2h5IHRlaCB3b3JrIGlzIG5lZWRlZC4gIEJ1dCB0aGlzIGRvZXMgbm90IHNl
ZW0gdG8gbWF0Y2ggdGhlIFJGQyAyMTE5IG1lYW5pbmcgb2YgU0hPVUxEIGFzIGl0IGRvZXMgbm90
IGFwcGx5IHRvIGVpdGVociB0aGUgaW1wbGVtZW50b3Igb3IgdGhlIGltcGxlbWVudGF0aW9uLg0K
DQpKb24+IEkgYWdyZWUgLSB0aGlzIGlzIGluY29ycmVjdCB1c2Ugb2YgU0hPVUxELiAgSXQgYWxz
byByZWZlcmVuY2VzIHRoZSBNSUIgd2l0aG91dCBldmVuIG1lbnRpb25pbmcgdGhlIFlBTkcsIHdo
aWNoIGlzIGEgc3ltcHRvbSBvZiB0aGlzIGRvY3VtZW50J3MgYWR2YW5jZWQgYWdlLiAgV2UnbGwg
Y2hhbmdlIHRoaXMgYXMgZm9sbG93cyAoYW5kIGFkZCB0d28gaW5mb3JtYXRpdmUgcmVmZXJlbmNl
cykuDQoNCk5FVw0KICAgVGhlIFBDRVAgWUFORyBtb2R1bGUgW0ktRC5pZXRmLXBjZS1wY2VwLXlh
bmddIHNob3VsZCBpbmNsdWRlDQogICAtICBhZHZlcnRpc2VkIHN0YXRlZnVsIGNhcGFiaWxpdGll
cyBhbmQgc3luY2hyb25pemF0aW9uIHN0YXR1cyBwZXIgUENFUCBzZXNzaW9uDQogICAtICB0aGUg
ZGVsZWdhdGlvbiBzdGF0dXMgb2YgZWFjaCBjb25maWd1cmVkIExTUC4NCg0KICAgVGhlIFBDRVAg
TUlCIFtSRkM3NDIwXSBjb3VsZCBhbHNvIGJlIHVwZGF0ZWQgdG8gaW5jbHVkZSB0aGlzIGluZm9y
bWF0aW9uLg0KDQo9PT09DQoNCg==


From nobody Tue Apr 11 06:46:47 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B30BB129BDB; Tue, 11 Apr 2017 06:46:45 -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_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=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 jXdOEFNL8p86; Tue, 11 Apr 2017 06:46:44 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A976128959; Tue, 11 Apr 2017 06:46:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 4FF6F660F4E; Tue, 11 Apr 2017 06:46:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1491918376; bh=g+awUG1ihLZdm/bQrQ+bYZcmiRU4/2424sOMGePZAFo=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=Wf5z3wteOmmJ/Xqt6AL8fA02HaMZS0cWKcqeHmekaOOi3ByU/v1BdlcWSYIsIP4Ix rNOSSJDK/5E3QKbXyES/OiaSW6nqJ++/yEOZFhs5FFASpfe4vbe9AUQkIot24sRFI+ foon+aGB7rkrdjaaUtzlrYF7mYmzVeAn68AcvkQ0=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailb2.tigertech.net (Postfix) with ESMTPSA id 802DD660F54; Tue, 11 Apr 2017 06:46:15 -0700 (PDT)
To: Jonathan Hardwick <Jonathan.Hardwick@metaswitch.com>
References: <148730267819.21972.5284047079762312692.idtracker@ietfa.amsl.com> <BY2PR0201MB191095098C1B48E5661CED6384000@BY2PR0201MB1910.namprd02.prod.outlook.com>
Cc: "draft-ietf-pce-stateful-pce.all@ietf.org" <draft-ietf-pce-stateful-pce.all@ietf.org>, "pce@ietf.org" <pce@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <2598a1a7-a5b1-fb4d-4ea5-8ecb33e58321@joelhalpern.com>
Date: Tue, 11 Apr 2017 09:46:14 -0400
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: <BY2PR0201MB191095098C1B48E5661CED6384000@BY2PR0201MB1910.namprd02.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/iVAv6mwYgVbGyK2M8N1dOfWsbOE>
Subject: Re: [Gen-art] Review of draft-ietf-pce-stateful-pce-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 13:46:45 -0000

Thank you Jonathan.  Those changes sufficiently address my concerns.
Yours,
Joel

On 4/11/17 5:55 AM, Jonathan Hardwick wrote:
> Hi Joel
>
> Many thanks for these comments.  I'm picking up this thread and replying as PCE working group chair, as the authors are unavailable.  I apologise for the delay.
>
> Please see my proposed resolutions inline below, marked with "Jon>"
>
> Best regards
> Jon
>
>
> -----Original Message-----
> From: Joel Halpern [mailto:jmh@joelhalpern.com]
> Sent: 17 February 2017 03:38
> To: gen-art@ietf.org
> Cc: draft-ietf-pce-stateful-pce.all@ietf.org; pce@ietf.org; ietf@ietf.org
> Subject: Review of draft-ietf-pce-stateful-pce-18
>
> Reviewer: Joel Halpern
> Review result: Ready with Issues
>
> <snip>
>
> ====
>
> Minor issues:
>    At the end of section 5.4, the text talks about a PCE accepting status updates even if the  stateful capability has not been negotiated.  Which is fine.  But as written, the text seems to say that doing so means that the PCE will be able to "build and maintain an up to date view of the state of the PCC's LSPs".  However, if the capability has not been negotiated, I do not see how the PCE can count on getting full and timely state reports.  Trying to infer why a PCC is sending such a report in the absence of the agreement seems problematic.
>
> Jon> I agree.  I propose that we delete this sentence:
> " Note that even if the update
>    capability has not been advertised, a PCE can still accept LSP Status
>    Reports from a PCC and build and maintain an up to date view of the
>    state of the PCC's LSPs. "
>
> ====
>
>     This comment may be a misunderstanding or mis-expectation on my part.  I would have expected one of the ways o using an active PCE is to have the PCE decide (under suitable circumstances) that an LSP is needed between two PCCs.  As far as I can tell, the text in section
> 5.8.2 and 5.8.3 prohibits that.  A PCE is only allowed to send an LSP Update Request (in a PCUpd message) for an LSP that has been delegated to it.  At that point I thought that a PCC could delegate a block of unsetup LSPs to the PCE.  But then looking at 5.8.2, the text states that for each delegation, the PCC must request an initial path.  That seems to prohibit delegating a block of LSPs for future updates.  Is the intention to prohibit the driving of LSP creation from the PCE?
>
> Jon> Yes, the intention is that the PCE does not drive creation of the LSPs.  That behaviour is allowed but is described by a separate draft (draft-ietf-pce-pce-initiated-lsp).  I propose to clarify this in the introduction to the draft, so that future readers don't get caught by the same mis-expectation.  We'll add the following text to section 1, and add an informative reference to draft-ietf-pce-pce-initiated-lsp.  OK?
>
> NEW
>    The extensions that this document describes do not permit the
>    PCE to drive creation of an LSP.  The companion document
>    [I-D. ietf-pce-pce-initiated-lsp] specifies PCE-initiated LSP creation.
>
> ====
>
>     I have looked but I can not find the text explaining the significance and use of the Symbolic path name.  It is mandated by the draft.  There seems to be an implicit assumption taht it is needed by the PCE.  If the explanation of how or why it is needed is not present, it should be.
>
> Jon> Agreed.  Several of our reviewers have picked up on this.  I think we should clarify this in section 7.3.2 "Symbolic Path Name TLV".
>
> OLD
>    Each LSP (path) MUST have a symbolic name that is unique in the PCC.
>    This symbolic path name MUST remain constant throughout an LSP's
>    lifetime, which may span across multiple consecutive PCEP sessions
>    and/or PCC restarts.  The symbolic path name MAY be specified by an
>    operator in a PCC's configuration.  If the operator does not specify
>    a unique symbolic name for a path, the PCC MUST auto-generate one.
>
>    The SYMBOLIC-PATH-NAME TLV MUST be included in the LSP object in the
>    LSP State Report (PCRpt) message when during a given PCEP session an
>    LSP is first reported to a PCE.  A PCC sends to a PCE the first LSP
>    State Report either during State Synchronization, or when a new LSP
>    is configured at the PCC.  The symbolic path name MAY be included in
>    the LSP object in subsequent LSP State Reports for the LSP.
>
>    <snip>
>
>    Symbolic Path Name (variable): symbolic name for the LSP, unique in
>    the PCC.
>
> NEW
>    Each LSP MUST have a symbolic path name that is unique in the PCC.
>    The symbolic path name is a human-readable string that identifies an
>    LSP in the network.  The symbolic path name MUST remain constant
>    throughout an LSP's lifetime, which may span across multiple
>    consecutive PCEP sessions and/or PCC restarts.  The symbolic path
>    name MAY be specified by an operator in a PCC's configuration.  If the
>    operator does not specify a unique symbolic name for an LSP, then the
>    PCC MUST auto-generate one.
>
>    The PCE uses the symbolic path name as a stable identifier for the LSP.
>    If the PCEP session restarts, or the PCC restarts, or the PCC re-delegates
>    the LSP to a different PCE, the symbolic path name for the LSP remains
>    constant and can be used to correlate across the PCEP session instances.
>
>    The other protocol identifiers for the LSP cannot reliably be used to
>    identify the LSP across multiple PCEP sessions, for the following reasons.
>    -  The PLSP-ID is unique only within the scope of a single PCEP session.
>    -  The LSP-IDENTIFIERS TLV is only guaranteed to be present for LSPs
>       that are signalled with RSVP-TE.
>
>    The SYMBOLIC-PATH-NAME TLV MUST be included in the LSP object in the
>    LSP State Report (PCRpt) message when during a given PCEP session an
>    LSP is first reported to a PCE.  A PCC sends to a PCE the first LSP
>    State Report either during State Synchronization, or when a new LSP
>    is configured at the PCC.
>
>    The initial PCRpt creates a binding between the symbolic path name and
>    the PLSP-ID for the LSP which lasts for the duration of the PCEP session.
>    The PCC MAY omit the symbolic path name from subsequent LSP State
>    Reports for that LSP on that PCEP session, and just give the PLSP-ID.
>
>    <snip>
>
>    Symbolic Path Name (variable): symbolic name for the LSP, unique in
>    the PCC.  It SHOULD be a string of printable ASCII characters and SHOULD
>    be NULL-terminated.  The Symbolic Path Name (including its NULL
>    terminator) MUST be padded to 4-bytes alignment; the padding itself
>    MUST NOT be included in the Length field.
>
> END NEW
>
> ====
>
> Nits/editorial comments:
>     Should the text on the S bit in section 7.3 (the LSP Object
> definition) note that it should be set to 0 on all messages sent by the PCE?  Should that also be stated for the R bit?  And the O bits?
>
> Jon> Yes.  We will add a note to the description of these fields.
>
> ====
>
>   Section 9.2 seems very odd.  It states that the IETF "SHOULD" do some additional work.  I understand why teh work is needed.  But this does not seem to match the RFC 2119 meaning of SHOULD as it does not apply to eitehr the implementor or the implementation.
>
> Jon> I agree - this is incorrect use of SHOULD.  It also references the MIB without even mentioning the YANG, which is a symptom of this document's advanced age.  We'll change this as follows (and add two informative references).
>
> NEW
>    The PCEP YANG module [I-D.ietf-pce-pcep-yang] should include
>    -  advertised stateful capabilities and synchronization status per PCEP session
>    -  the delegation status of each configured LSP.
>
>    The PCEP MIB [RFC7420] could also be updated to include this information.
>
> ====
>


From nobody Tue Apr 11 11:55:17 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 719F312EC51; Tue, 11 Apr 2017 11:55:15 -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=cooperw.in header.b=Mozk4rfR; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PH9RQ28x
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WXgQH3F5x4PF; Tue, 11 Apr 2017 11:55:14 -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 DD06212EC52; Tue, 11 Apr 2017 11:55:13 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 483FD20FD6; Tue, 11 Apr 2017 14:55:13 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 11 Apr 2017 14:55:13 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=WOUw2pDNrHWnIrdHPz YTbrXe92MqhF271NxP93zlmL8=; b=Mozk4rfRAj01N5u1zNVweYBfc0m24Akpr0 L9jpTenWxGsO+mjGZpoXowM4c0zT3pENf3IR0iR6d6f/doQ5nly456o8aGRPxjKD RTPT0wXkD2IzWwujOZcppC1yFVnih3tzMeoihSwME04VVGF/afmrUkR/rMzpXpRs QWqkQ6gJFdD0wHdkz3sag3QpZHJPGdEhN6Povci5NfXpjXUMLnwvy5aIs9KqnSVM BO3kyKCBl1YYVYQ0CytYEhs4Pa5vkUo1UshBI2Ty8tm3L/ozXw5C49zpDEELhcBS tCq7RfSkFNVBI3cJE+EUeQXMdzv/jZ2n1uDJfu7U8S/IB8Fc63ig==
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=WOUw2pDNrHWnIrdHPzYTbrXe92MqhF271NxP93zlmL8=; b=PH9RQ28x eYyJ3Q0XLFuRHLMX8kUXOXOA3IPPF1xAcoLsPpyCiNmaGxYW2sqFPRlOLntfkvey mKLp7zw0N+B1eoVzf/IAdJTpkmA+wA01HIlY4VunnySlpQpQmWyqCU96AcJJq0KF s0fEYp9CBRnJnR8Z1D7bcPpUwdte74yXGYRi0Fpr++Cw6ymZQwkboRJk2PQBa4Ri NtU4xgOEiSLBpL9tUMw49ZCH61QyF/ggCxrLCTjbzer5mgEY7+giQVHwlL6ftoEd srV7y4tP+h+Jng8LrWdt7g877j18KdiHri7MJYNr9tLW9BGsWtz2FCbEco1bsnwZ Qmp2v/uJkd9ZMQ==
X-ME-Sender: <xms:kSbtWNq9W22tlf_UhRwU5hg_h-PE4RYMo02_JQ2P7zywEqsNUOP17w>
X-Sasl-enc: 64SbdDNBq6KT1CNb06k0PRe8z1crdTISZW2y3xgNhSaX 1491936912
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.178]) by mail.messagingengine.com (Postfix) with ESMTPA id 5F85A240AE; Tue, 11 Apr 2017 14:55:12 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <149097476468.4284.16899240629504751438@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 14:55:11 -0400
Cc: gen-art@ietf.org, draft-ietf-pals-status-reduction.all@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <83DF8D05-26E0-4883-AABE-210A7586BCF1@cooperw.in>
References: <149097476468.4284.16899240629504751438@ietfa.amsl.com>
To: Dan Romascanu <dromasca@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/smfP0ub_7Ixz5U7QSqCOYt11J5E>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-pals-status-reduction-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 18:55:15 -0000

Dan, thank you for your review!
Alissa

> On Mar 31, 2017, at 11:39 AM, Dan Romascanu <dromasca@gmail.com> wrote:
> 
> Reviewer: Dan Romascanu
> 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-pals-status-reduction-??
> Reviewer: Dan Romascanu
> Review Date: 2017-03-31
> IETF LC End Date: 2017-03-31
> IESG Telechat date: 2017-04-13
> 
> Summary:
> 
> This document describes a very useful optimization for MPLS LSP PWs
> operations by defining a method for generating an aggregated PW 
> status message transmitted on a MPLS LSP to indicate the status of the
> PWs carried on the LSP. The document is clear, detailed and provides
> all needed information for implementers to write code and for
> operators to deploy. 
> 
> Major issues:
> 
> Minor issues:
> 
> Nits/editorial comments: 
> 
> 1. In section 8, first paragraph: s/rages/ranges/
> 2. In sections 8.3, 8.4 the construct "IETF Review" is worded in three
> different ways (IETF review, IETF Review, "IETF Review") - better
> align
> 
> 
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Apr 11 11:58:00 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B97C412EC76; Tue, 11 Apr 2017 11:57:57 -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=cooperw.in header.b=Syo8ig+0; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=SEejeLKz
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WRpf8WZM7grR; Tue, 11 Apr 2017 11:57:56 -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 E099312EC89; Tue, 11 Apr 2017 11:56:55 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5237920A74; Tue, 11 Apr 2017 14:56:55 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 11 Apr 2017 14:56:55 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=1jSIRc4qVs7SL7qB67 opOoSALCD6LAonRJZrXz7vm8c=; b=Syo8ig+06Hzv68aQ7loiG1Zbia0Zct9xCZ FTkZFy1zp4Os4nRP3MhChDFZ8OT5ffL6HbguTvqb0uaXKLnPLnYyZI62vKZnZz+4 h7lNb3Sob6LAg7xb8UPq26Ma+Tmj9L89wud5Of+VqAgEFztGhYskOYPhISTprD8Y Wk7bGU5Bzi4rihzW2gXxpJDQsUBAkMA4v7Ix5dGo4qSNogDmBjTyqtZ/UO9Me9Ik jkWFCuE81xIxF1ku4n/01U7TCIQdxQnrxk3Pr3UKUkwWLoZg6T4UOV6tdgQXB/6+ yaVsUB4yzngDtO4e11xduFpo1Xi4SqzwjcXwbOFfFp3RFRWxipiA==
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=1jSIRc4qVs7SL7qB67opOoSALCD6LAonRJZrXz7vm8c=; b=SEejeLKz MVVCcqlybNtndFDfU4iDJFDt0zqfloiMc1jIq2Zb0nvyms7YhrDPM/q5iYCVIshQ OCurCrf7/FpTweqkTa72XvquCOQnTscU/7I+eLQncDru/wlZyPX9z2RwclbXFfl6 spuUK4cAZgrU6TGhc8bVpy7+IRPC424xVdQ8KB6wjYPNwQkWGQ7VtlKi3c7+5Xvr XSDBuDjdGeW6lAUzsDCyeurdjtgpFCMngQxO3Hgz9F4GonvtJSih0Wdj9ebwnMAe ov1TR6wGlkgefXVFkKQ/ZDFyNdmNVcoXOdOEvcPg9eUeK9od7p1uIY5bfyx4RMl/ RXUeYY4rKaey6g==
X-ME-Sender: <xms:9ybtWBdm90MToKOj6vJK7ZFI_YLlKSx0JyMKAyT2_ksOYVuJoyBonA>
X-Sasl-enc: IeQuR5J7l6+fDoYwyFNLfsLEY5dUdsujDn1SukhHFgPM 1491937014
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.178]) by mail.messagingengine.com (Postfix) with ESMTPA id 7902F240AE; Tue, 11 Apr 2017 14:56:54 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <149171742319.3063.4555090995663652452@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 14:56:52 -0400
Cc: gen-art@ietf.org, draft-ietf-bess-evpn-vpws.all@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <2AA8DBB4-EBA6-45B1-85B7-E8C7176C35A6@cooperw.in>
References: <149171742319.3063.4555090995663652452@ietfa.amsl.com>
To: Roni Even <ron.even.tlv@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/gpO5q1b3ntKQ56nk-AdKQIzhqes>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-bess-evpn-vpws-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 18:57:58 -0000

Roni, thank you for your review.
Alissa

> On Apr 9, 2017, at 1:57 AM, Roni Even <ron.even.tlv@gmail.com> wrote:
> 
> Reviewer: Roni Even
> Review result: Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair. Please wait for direction from your
> document shepherd or AD before posting a new version of the draft.
> 
> For more information, please see the FAQ at
> 
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
> 
> Document: draft-ietf-bess-evpn-vpws-??
> Reviewer: Roni Even
> Review Date: 2017-04-08
> IETF LC End Date: 2017-03-10
> IESG Telechat date: 2017-04-13
> 
> Summary:
> 
> Major issues:
> 
> Minor issues:
> 
> Nits/editorial comments: 
> 
> In section 1 second paragraph "[RFC7432] provides the ability " looks
> like the reference is not a link to RFC7432.
> 
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Apr 11 12:03:17 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C833012944F; Tue, 11 Apr 2017 12:03:15 -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=cooperw.in header.b=ND4GaheG; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=VFmw2bJN
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHjfC0xnKiN5; Tue, 11 Apr 2017 12:03:14 -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 4983712EC34; Tue, 11 Apr 2017 12:03:01 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id AE57B20BBF; Tue, 11 Apr 2017 15:03:00 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 11 Apr 2017 15:03:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=/D1I1lpLbnX+oqwW0C HiYrQMXPPsqmb7esTbJp66gh4=; b=ND4GaheGv40zKyHar/lGnKf6NoIPrF8Kx5 309hBRgobr8BLc1oQ1QNMT53rnyK0E2OBv082un9K8A5nYPKxzSye+RXjgfsIC5L NHyBMnbAR4J674WyBtOV41qjyTQFUidR4UkwrRogxr7DTJuH3xc0zCDr+dCy/j1P qxpgO7E4h2LeVUeF9T9H14mlxZ2mHvSt2Tm12sOzaWoffMVBl4C75D4s/B9iVqX+ CeDu8jel8kB/DxQ08ytyLrsDvJqrb38BO4hQIoRa36QNTzM6RJnHQ4WoTvU6NFXo IpgKua4QfjTw15BMsVKNWVwGRoLtAd7bgGqZ0/hkXt16mM1mCpMw==
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=/D1I1lpLbnX+oqwW0CHiYrQMXPPsqmb7esTbJp66gh4=; b=VFmw2bJN qxZQdYFNwL2I5d017tRKec0qdmNVi/7kBKx9iQmRuwE0pL489GQfrnNX7Ce9n7Zu VuEjWM2Q7iBS3iFgeSQuljOoGGsFAiBEBCqhbsm72ROHnEgX9v+PugELWSbRoBaV 51v7++a6CDu5uA/+1LqgCaAGHfcsEpoPiKXJR95n8B8c69SkzfWRVP/OKIO8gpUO p0AK1IdPjXc5kFEhpirUFYl39nFRbkR2bAOibx3i1/XeRAtA1tnQOPoCF5hsUWzG UtkH0ieSPJJyWulHB+P/MmdM86XfSGeUdGJqbempkQCSxh+0Iw8ui3vceg8XNHSd H4r6+pfne70DUQ==
X-ME-Sender: <xms:ZCjtWP1subfTUkjMMKDW3K2d9IEorZjgJUEY1C-IduaMWx6hK9FZMQ>
X-Sasl-enc: WlaXk4WkN9Ec/37jRA/K9fySdPqgE3VHisBrScGPzU+b 1491937380
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.178]) by mail.messagingengine.com (Postfix) with ESMTPA id D1FD62470C; Tue, 11 Apr 2017 15:02:59 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <148916605590.6778.14181761811890656682@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 15:02:58 -0400
Cc: gen-art@ietf.org, draft-ietf-ippm-twamp-time-format.all@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <FCC0BC25-BB0F-45B5-9007-609F85E9DD6B@cooperw.in>
References: <148916605590.6778.14181761811890656682@ietfa.amsl.com>
To: Joel Halpern <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/1sVz7pryNlT480D2qnMf7EYFbws>
Subject: Re: [Gen-art] Review of draft-ietf-ippm-twamp-time-format-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 19:03:16 -0000

Joel, thank you for your review.
Alissa

> On Mar 10, 2017, at 12:14 PM, Joel Halpern <jmh@joelhalpern.com> wrote:
> 
> 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-ippm-twamp-time-format-??
> Reviewer: Joel Halpern
> Review Date: 2017-03-10
> IETF LC End Date: 2017-03-15
> IESG Telechat date: Not scheduled for a telechat
> 
> Summary: This revision fully resolves my concerns from -03
> 
> Major issues: N/A
> 
> Minor issues: N/A
> 
> Nits/editorial comments: N/A
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Apr 11 12:05:23 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AB22D12778E; Tue, 11 Apr 2017 12:05:22 -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=cooperw.in header.b=CmV7Tk7t; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=kRWca5Vd
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FRxWHA7eBvlQ; Tue, 11 Apr 2017 12:05:21 -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 5768312EC85; Tue, 11 Apr 2017 12:05:17 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id B47C420A7F; Tue, 11 Apr 2017 15:05:16 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 11 Apr 2017 15:05:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=ZPcEndJuKwpRf/L/N8 qdF8pybRSxFVASDUzKKZit4hM=; b=CmV7Tk7t2zO+MSFBXxu+dCbno+ypPq9F+f 9rBMw95LCqlHkcVsIa1BF2PMJIAqiD9nFqHUimB75l1lfVORmo/rC+N166TrtxSC WXnwc6lD2FqnfMFnd/HllzqGDVWeoReDptj1FcESoLmaEY7qpHb2kAI4iOBNHsz0 sMzc6VtkWU4YnL6OaGu5L//hDse7eCEjchvnVvnvmlmrbxM0sPmOfEF9F0C/wlQW ufqz13UStCeBvEiilXdn6b5XHynp3TOVVsgSP+RE2OzXI0Oh4CVK0T2rdotodfzw cv3goEwAo6KoYchdU1ZsWToDTZ+2aLu7qMbSllzQna6n8iw/ER5A==
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=ZPcEndJuKwpRf/L/N8qdF8pybRSxFVASDUzKKZit4hM=; b=kRWca5Vd 1dFI4QCHAztc1ModftuqnUFYG8jgZq8Xw+oT4oc3AnFUp8dpiwiNrpWlua3V3q4T beNYxrbgndhBocc7NhuB2t1u9qsExw8WSG0x11fmuTu60amUivRe9mArSFA+P4V4 1jxt/IF01ceK/T+FdWxUf1TUlVd3fnwHrnHeKWPWvTtJIRWBWEw9zxsP8jfTQ4a/ b6mfNJJs66rd/RquRxfvR3ul1ur6F1LnfwfU76crwMyKm6aPjofubm5hEE0ZMEHC 2TUDN/Du4VYESSnLaEOwLxnaZCE1kBVuQokO3CWwPlxJjIRgJn3je+5ZBQgSRpxr ze1a8fgC6mOt0Q==
X-ME-Sender: <xms:7CjtWFrf0bZMQKEaCLpL5PNIRlL_ouxiE0B-0Xt2UhJuLXJyP0qiXA>
X-Sasl-enc: n57Pb6Q03fsnVugVsmwmfDy5S1nZBh44YWpEeptjAV2j 1491937516
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.178]) by mail.messagingengine.com (Postfix) with ESMTPA id D97D52470C; Tue, 11 Apr 2017 15:05:15 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 15:05:14 -0400
Cc: gen-art@ietf.org, draft-ietf-httpbis-encryption-encoding.all@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <6052B209-AAD3-4B77-8D54-E7FC6B7CF69A@cooperw.in>
References: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/KwjGgwYYEWDmIsrzmBpikeAZUFw>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-httpbis-encryption-encoding-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 19:05:22 -0000

Pete, thank you for your review.
Alissa

> On Apr 6, 2017, at 1:52 AM, Pete Resnick <presnick@qti.qualcomm.com> wrote:
> 
> Reviewer: Pete Resnick
> Review result: Ready
> 
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please 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-httpbis-encryption-encoding-??
> Reviewer: Pete Resnick
> Review Date: 2017-04-05
> IETF LC End Date: 2017-04-06
> IESG Telechat date: 2017-04-13
> 
> Summary: Ready
> 
> Major issues: None
> 
> Minor issues: None
> 
> Nits/editorial comments: Looks fine from a non-security-expert's
> perspective. It is my duty to ask about keyid in section 2.1:
> 
>      A "keyid" parameter SHOULD be a UTF-8
>      [RFC3629] encoded string, particularly where the identifier
> might
>      need to appear in a textual form.
> 
> I presume that simply means "might need to be rendered" and does not
> include "might need to be typed in by someone", correct? The former is
> easy; the latter probably requires a bit more text.
> 
> 


From nobody Tue Apr 11 12:11:05 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E197C12EC8B; Tue, 11 Apr 2017 12:11:03 -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=cooperw.in header.b=PZAAwwCv; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=hmwjfeH0
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dLb5DDAvYb_r; Tue, 11 Apr 2017 12:11:02 -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 510BB12EB7C; Tue, 11 Apr 2017 12:11:02 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id AB925208CD; Tue, 11 Apr 2017 15:11:01 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 11 Apr 2017 15:11:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=DxSCmZmT/qXYpOw4Lj ErRWfLhht/OVvBcWetudtzxdc=; b=PZAAwwCvzalCzLyBME0iYQBhMFaiVwvMo3 ohsLWCuAk85sHpi6VPvC2GHr1yNUa1Em8uZmDrH3mg8JbjdXyCw9WecQ6mc5saRq 34JzTFPCU5rab30pG35Z3IHFHP2+1eDb+AM4i4IRsaJ5bL7ob2PPvUVuVUegNz5i P4aEx50i2b8lmrNY8bAVqjB8qPkl2xN39DofsrQG5SNIseRFKOp5sKr4LjbqE/ON CZAuzoGZscTHAAHr0XrkvJAjWgjipc/nqv7UEh7FRTFn07GiJkjv1A/tMZeBIRaR QOz8+jka471SewsK4KLNBG56+Zb0G/Oro4IBg2e8dHf/+xezxj9A==
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=DxSCmZmT/qXYpOw4LjErRWfLhht/OVvBcWetudtzxdc=; b=hmwjfeH0 lMWtqraw5RkLx/4zmySdrEUaSOQrzuazU57grILbTRbjLTg7EyqooZKkdeg/f2+d pHSCmVYLqTW+IAXY+GIBZ4I6YWLKRlL1/rt0o7jhc19aRcfSvcZSKSSa0R6bipu2 IOyQaWhqm9IJwWCe67Qfs8kcEmu1j5d+he2mTQkjPAIMHExCar+UpQDmFJM0KSN8 qa2auEYWN9u1NmGt7jGQSc1qcCePWE+fmk8NwSpez7ycGHJDS3CGfWMs7Vjxc8qg iEoOb4VPBXKXBxbUKaJNAgaXN4R4KgUtaIz4EOgmKqVZ8ppQ6BXRBMJCntVIyahd 0yU/atTHTDfo1A==
X-ME-Sender: <xms:RSrtWJV1ptOnKiITtUzpT5zn5gdS_1rV8z9f5j4mVv7T7n35ybGXvA>
X-Sasl-enc: GVUeZoGzaCqxK2Px3USb7YMSfN5m9qNces0VZU0pHFmR 1491937861
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.178]) by mail.messagingengine.com (Postfix) with ESMTPA id CD5E4246E4; Tue, 11 Apr 2017 15:11:00 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <149159669211.11107.3275242226580240988@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 15:10:59 -0400
Cc: gen-art@ietf.org, draft-ietf-isis-auto-conf.all@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <2B612937-C6D5-4538-A8C4-C0F320B76E52@cooperw.in>
References: <149159669211.11107.3275242226580240988@ietfa.amsl.com>
To: Robert Sparks <rjsparks@nostrum.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/6zge22QHS-n4LOr9ABkBZJA5hTg>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-isis-auto-conf-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 19:11:04 -0000

Robert, thank you for your review.

And thanks all for your engagement to resolve the issue raised by Robert.

Alissa

> On Apr 7, 2017, at 4:24 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
> 
> Reviewer: Robert Sparks
> 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-isis-auto-conf-04
> Reviewer: Robert Sparks
> Review Date: 2017-04-07
> IETF LC End Date: 2017-04-10
> IESG Telechat date: 2017-04-13
> 
> Summary: Ready for publication as Proposed Standard, but with 
> one possible thing to add to the security consideration section
> 
> This document is clear and seems straightforward to implement. 
> 
> I think, however, there is an attack possibility you should call out 
> in the security considerations section. As home routers are used 
> as examples of elements that might use this protocol, consider 
> the case of a malicious party wanting to deny service in that home.
> A suborned device in the home could watch for the protocol, and
> present a crafted packet to force the home router(s) to re-start
> the autoconfiguration protocol continually (by claiming to be a
> duplicate and being careful to make it the routers job to restart).
> Having the md5 password configured would mitigate this attack.
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Apr 11 12:36:13 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2F4512EBCA; Tue, 11 Apr 2017 12:36:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=ZL9C24YL; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=df91o2Kf
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PT7vH-8f8Gt5; Tue, 11 Apr 2017 12:36:10 -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 D6A9A12EC9C; Tue, 11 Apr 2017 12:36:09 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 51626209F7; Tue, 11 Apr 2017 15:36:09 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 11 Apr 2017 15:36:09 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=c+9A1/5kCSeNQVpPt4 45e42nb5ogewT5IVEZkGKpD2g=; b=ZL9C24YLV35njbdTM6cJ6mgzqtVs0d4S9P 4M3mtYp4U/Q8ecBAvm1ZtyD178l1/f75itJz9j2OrBTk64thZqtly6atCfjvQ8uL LFS8r5vRsaivzchnXvHLpKqQTEZx8ZgkEXPmPfXiiYZ3S1oswtgdijJ+e1Zegl/Q M+YCcvAORsj7Tp4h/1F7AwKOiY0iPWNJTNdW/XPSefwRhPuPptVJ8gDK8g2OzTnY YRBOwxT/+ll7YY0wGZwQRrhs+7caey01+I4MkEn6PoJa/ZuBt1likG9LfAECy9mN uuHQL2eT2NmUuPsfss1U6osmqVxGlWDLOvhXmQJ7BjmPzPicvuSw==
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=c+9A1/5kCSeNQVpPt445e42nb5ogewT5IVEZkGKpD2g=; b=df91o2Kf hvPzm3Lmrig5mUJ/ZU90X02UynNYAXouGhE+p05+qWuXAQJyO42ah8EytUrOkllK /T2swGjoDDVfKA9d/fLIMX49LRxGx2eUGyD2DehwtZ9XX9RuaZxrOEPsgZUT1GZE 1uFtO6O8yWN+6hobVlI30ScYNq28ftmjGJAoQrGciOph40j1gtMoHV7uTQGYyUfP F16J5Q5zsLdZX+0kKC+lqNJkNVFZCdQSjp8NnFt+fxNOetEYGof88Hs5yZI5F17U UmuHSGg3A1jPmoLyDR7dHKJb32mVyEzhAXwKcPL+UsMO8z7z/qm3VjzqWeIkoX1i +MMUjMsCJeF+fA==
X-ME-Sender: <xms:KTDtWB-pnxyY5bj5inJ1wGmZllLMZn0suaxGyzZEsJpoZvtnjpIIQg>
X-Sasl-enc: xFnKCn1b5YHytEQW9ozbT8jVwKtWu3CvWr4Vo7fnuTw1 1491939368
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.178]) by mail.messagingengine.com (Postfix) with ESMTPA id 53F7324526; Tue, 11 Apr 2017 15:36:08 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <149049732959.11830.18161576308900341179@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 15:36:06 -0400
Cc: gen-art@ietf.org, draft-ietf-aqm-codel.all@ietf.org, aqm@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <6708251A-546F-49F7-B8DE-86B2C704A63E@cooperw.in>
References: <149049732959.11830.18161576308900341179@ietfa.amsl.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/g2ty0SZre9ys4hUG9ZjuRZ9n3AE>
Subject: Re: [Gen-art] Review of draft-ietf-aqm-codel-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 19:36:13 -0000

Fernando, thanks for your review. Will leave it the authors/WG to =
consider your comments. On your major point, personally I don=E2=80=99t =
find it problematic for the diagrams to be archived elsewhere, given our =
current limitations of ASCII art and the clear presentation in the =
referenced doc/session in TSVAREA.

Alissa

> On Mar 25, 2017, at 11:02 PM, Fernando Gont <fgont@si6networks.com> =
wrote:
>=20
> Reviewer: Fernando Gont
> 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-aqm-codel-07
> Reviewer: Fernando Gont
> Review Date: 2017-03-25
> IETF LC End Date: 2017-03-27
> IESG Telechat date: 2017-04-13
>=20
> Summary:
> The document is well written. However, there seem to be too many
> details that are left out in other associated documents. Whereas such
> details (including figures) are needed to understand this document,
> they should be included here. Either provide full explanations or
> summarize the outcome without details (there's text that somehow
> relies on the reading finding such figures elsewhere).
>=20
>=20
> Major issues:
> * Section 5.1, page 16:
>>   A more detailed explanation with many pictures can be found in
>>   http://www.ietf.org/proceedings/84/slides/slides-84-tsvarea-4.pdf
> .
>=20
> Unless I'm missing something, if this document is specifying CoDel,
> then all such details should be here.
>=20
>=20
> Minor issues:
> * General:
> The document would benefit from a terminology section. For example,
> only well into the I-D one finds definitions of terms such as "sojourn
> times" or "target setpoint". Not sure if those terms are supposed to
> be trivial/obvious to most people reading this document, but their
> non-definition left me trying to figure out what the terms were about
> before I was ale to better understand what you were describing.
>=20
>=20
>=20
> Page 3, Section 1:
>>   o  simple and efficient implementation (can easily span the
> spectrum
>>      from low-end, linux-based access points and home routers up
> to
>>      high-end commercial router silicon)
>=20
> There seems to be an unnecesary implicit "judgement" here, associating
> linux-based with low-end, and commercial with high end. I suggest you
> modify the text.
>=20
>=20
> Page 10:
>>           count_ =3D (delta > 1 && now - drop_next_ < 16*interval_)?
>=20
> For clarity, I'd use additional parenthesis here.
>=20
>=20
> Nits/editorial comments:=20
> * Page 17:
>> The power vs. f curve for any AIMD TCP is monotone decreasing.=20
>=20
> Please expand the acronym.
>=20
>=20
> * Page 17:
>>   simulation that this result holds for Reno, Cubic, and
>>   Westwood[TSV84].
>=20
> Missing space.
>=20
> Thanks!
> Fernando
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Apr 11 12:45:47 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 062B912FC15; Tue, 11 Apr 2017 12:45:45 -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=cooperw.in header.b=gffhU4SK; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=lfIIS8Qt
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5D2VmiEQxvjw; Tue, 11 Apr 2017 12:45:41 -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 A9EE412EB22; Tue, 11 Apr 2017 12:45:41 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 1A56520F26; Tue, 11 Apr 2017 15:45:41 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Tue, 11 Apr 2017 15:45:41 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=DBStrk6+Zzp+rWv7Jw GgP/EKuYSFcKd//dyOO1FSzIo=; b=gffhU4SKdL0XjLeW0KuaRk0Jd3lQSHsNkZ pL49c7UmSVv9GTr9eQ5UCVYGmtbEoDtF8PmcpcxKoZxJ8g1eS1RC9fwG4yeWWYc/ pnRHZtyOptUkGqTWFigjl9/r6Q+fZyV9qafvyWUxhukPJQCNW0LKWWONkw6HdGt+ wqI5V9FiF0Fc8rRBTxijvI0WALnrdm5SzM/ysftc2PcyfAAi0wsw/Pe47x4vQ/iE FAw8GlAJ4FhFDNhb+rU0wjwpo51aUsADX/d7mLMP8iQXhStbCGJN3Jce9QvkwUPx ZQYchSWwenCvUbP9Jij4ToNxqAPSQonTlA+L5aE9FhGu21iyMUVA==
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=DBStrk6+Zzp+rWv7JwGgP/EKuYSFcKd//dyOO1FSzIo=; b=lfIIS8Qt jX6L0OywiGzvOxyjSsogPLWicM71jWW7v0VSvrafxd0Qn/2lmWJsWO9RJ4VZ9RuR ssEKkZEsRgxEmLadlwx29vudElSX9MVvxIPruwQUl5MBKn0RHJfkpVIWnMqT0obY AlaJtoIJvk3zznPNGYkeYeQNxScgihPXWrelKlSCG/PnMSZnrc5XI3/87rC7gyqg SZ3YXqyx9u3M8DZCiZTS/cW4dtluhQMQvOzIN//ueX0Xn0ftKUPyHK3WNSSS2UfW gEDAaS9xCcn4TsTrh5iEuikykfaW3mm8DijovFJwh0dkShqvm2/Gxes71z2IUhqL ZZZvMc5NBT+3hA==
X-ME-Sender: <xms:ZTLtWCDsf1N9--WTFyvOHhiPTa3mhmZJSmqbfhemmLYjgPXCicwAbQ>
X-Sasl-enc: ro2phRiSDoX9v+xP8q7+48NfzePPcKoFB+k0gShP1NUv 1491939940
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.178]) by mail.messagingengine.com (Postfix) with ESMTPA id D54A624526; Tue, 11 Apr 2017 15:45:39 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <148952979419.24295.8210647087024239014@ietfa.amsl.com>
Date: Tue, 11 Apr 2017 15:45:38 -0400
Cc: gen-art@ietf.org, draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E82868B3-8270-4502-9C98-867C07CC6BFF@cooperw.in>
References: <148952979419.24295.8210647087024239014@ietfa.amsl.com>
To: Dale Worley <worley@ariadne.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/g8GLZC4AmRkDg0GT7x4iLEyGV-Y>
Subject: Re: [Gen-art] Review of draft-ietf-i2nsf-problem-and-use-cases-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 19:45:45 -0000

Dale, thank you for your review. Sue, thanks for your engagement with =
Dale=E2=80=99s review.

I will be ballotting ABSTAIN as I agree with the assessment from Alvaro =
and Mirja.

Alissa

> On Mar 14, 2017, at 6:16 PM, Dale Worley <worley@ariadne.com> wrote:
>=20
> Reviewer: Dale Worley
> Review result: Ready with Nits
>=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
> Document:  draft-ietf-i2nsf-problem-and-use-cases-11
> Reviewer:  Dale R. Worley
> Review Date:  2017-03-14
> IETF LC End Date:  2017-03-22
> IESG Telechat date:  [unknown]
>=20
> Summary:
>=20
>       This draft is basically ready for publication, but has nits
>       that should be fixed before publication.
>=20
> All of these nits are editorial.
>=20
> 1.  Introduction
>=20
>   This document describes the problem statement for Interface to
>   Network Security Functions (I2NSF) as well as some I2NSF use
> cases.
>   A summary of the state of the art in the industry and IETF which
> is
>   relevant to I2NSF work is documented in
>   [I-D.hares-i2nsf-gap-analysis].
>=20
> The content of these sentences is very good, but the construction
> seems to be peculiar.  The document doesn't *describe* the problem
> statement, the document *is* a statement.  Similarly,
> hares-i2nsf-gap-analysis *is* a summary of the state of the art.  So
> I
> would use
>=20
>   This document is the problem statement for Interface to Network
>   Security Functions (I2NSF) as well as some I2NSF use cases.  A
>   summary of the state of the art in the industry and IETF which is
>   relevant to I2NSF work is [I-D.hares-i2nsf-gap-analysis].
>=20
> But maybe you'll prefer to ask the RFC Editor.
>=20
>   This document also briefly describes the
>   following use cases summarized by
>   [I-D.pastor-i2nsf-merged-use-cases]:
>=20
> This sentence should start a new paragraph, as it's not connected to
> the sentences before it.
>=20
> 3.  Problem Space
>=20
>   The following sub-section describes ...
>=20
> s/sub-section describes/sub-sections describe/
>=20
> 3.1.1.  Diverse Types of Security Functions
>=20
>   NSFs by different vendors can have
>   different features and have different interfaces.
>=20
> It might be worth mentioning somewhere what seems to be a convention:
> the document (or at least, section 3.1) is largely oriented toward
> "service providers" who sell comprehensive network services
> (including
> security functions) to "customers", but who in turn buy security
> functions from "vendors".  Perhaps this could be entered as
> terminology in section 2.
>=20
> The reason I mention this is that my background is as an end-user
> (which is common in the IETF), so the term "service provider"
> triggers
> in my mind the idea "someone I buy something from".  And the term
> "vendor" triggers the *same* idea.  But in this draft, the default
> reader is a "service provider" and "vendor" is *not* the same thing.
>=20
> This point started to confuse me at the beginning of section 3.1.6.
>=20
>   Security Functions in a Demilitarized Zone (DMZ):   Examples of
> this
>      function are firewall/ACLs, IDS/IPS, one or all of AAA services
>      NAT, forwarding proxies, and application filtering.
>=20
> The phrase "one or all of AAA services NAT" seems to be incorrect.  I
> suspect there's supposed to be a comma before NAT.
>=20
>   Security gateways and VPN concentrators:    Examples of these
>      functions are; IPsec gateways, Secure VPN concentrators that
>      handle bridging secure VPNs, and Secure VPN controllers for
> data
>      flows.
>=20
> Unless "Secure VPN" is a name in itself, "secure" shouldn't be
> capitalized.
>=20
> 3.1.2.  Diverse Interfaces to Control and Monitor NSFs
>=20
>   A challenge for monitoring is that an NSF cannot monitor what it
>   cannot view.  Therefore, enabling a security function (e.g.,
> firewall
>   [I-D.ietf-opsawg-firewalls]) does not mean that a network is
>   protected.  As such, it is necessary to have a mechanism to
> monitor
>   and provide execution status of NSFs to security and compliance
>   management tools.  There exist various network security monitoring
>   vendor-specific interfaces for forensics and troubleshooting.
>=20
> This paragraph seems awkward.  Each sentence is reasonable, but the
> connection between them is not clear to me.  Perhaps the third
> sentence has the meaning "... it is necesary to have a mechanism
> ...to
> verify that the NSF is seeing the traffic that is intended".
>=20
> The last sentence contains "network security monitoring
> vendor-specific interfaces" which is awkward.  Perhaps
>=20
>   There exist various vendor-specific interfaces for network
> security
>   monitoring, forensics, and troubleshooting.
>=20
> 3.1.4.  More Demand to Control NSFs Dynamically
>=20
>   The Security Service Providers ...
>=20
> The capitalization of "security service providers" is inconsistent.
> Some times all three words are capitalized, and some times they're
> not.
>=20
> 3.1.5.  Demand for Multi-Tenancy to Control and Monitor NSFs
>=20
>   Service providers may need several operational units to control
> and
>   monitor the NSFs, especially when NSFs become distributed and
>   virtualized.
>=20
> You may want to explain what an "operational unit" is.  As far as I
> can tell, neither "unit" nor "operational" (in this sense) is used
> elsewhere in this draft.
>=20
> 3.1.7.  Lack of Mechanism for NSFs to Utilize External Profiles
>=20
>   Many security functions depend on signature files or profiles to
>   perform (e.g., IPS/IDS signatures, DDos Open Threat Signaling
> (DOTS)
>   filters). =20
>=20
> I think the words "to perform" should be removed.  The sentence makes
> more sense to me without those.  Or, if there is a meaning that needs
> to be specified, "to perform" probably isn't the right choice.  "to
> work" makes sense in this place, but is an informal usage.  Perhaps
> "to function".
>=20
>   Today, the construction and use of black list databases
>   can be a win-win strategy for all parties involved.
>=20
> "win-win strategy" is a hackneyed phrase.  This is better
>=20
>   Today, the construction and use of black list databases
>   can be beneficial for all parties involved.
>=20
> However, it's not clear to me what additional information is carried
> by "for all parties involved".  And for that matter, is "today"
> important here?
>=20
> I suspect that you mean something like this:
>=20
>   Today, black list databases can be beneficial, and in the future
>   there might be open source signatures/profiles ...
>=20
> --
>=20
>   (e.g., by Snort, Suricata, Bro and Kisnet)
>=20
> s/Kisnet/Kismet/
>=20
> "Snort, Suricata, Bro and Kisnet" reads like a reference -- I had to
> look them up to discover that they are IDS software!
>=20
> But there needs to be some connection between a list of IDS software
> systems and "open source signatures/profiles".  Perhaps:
>=20
>   Today, black list databases can be beneficial, and in the future
>   there might be open source signatures/profiles distributed as part
>   of IDS systems (e.g. Snort, Suricata, Bro and Kisnet).
>=20
> --
>=20
>   There is a need to have a standard envelope (i.e., the format) to
>   allow NSFs to use external profiles.
>=20
> This is awkward.  Perhaps
>=20
>   There is a need to have a standard format to allow NSFs to use
>   external profiles.
>=20
> 3.1.8.  Lack of Mechanisms to Accept External Alerts to Trigger ...
>=20
>   I2NSF controller(s) would manage the changing to the affected
>   policies ...
>=20
> This could be simplified to "I2NSF controller(s) would change the
> affected policies ...".
>=20
>   By monitoring the network alerts from DDoS ...
>=20
> Probably s/DDoS/DOTS/.
>=20
>   ... I2NSF
>   can feed an alerts analytics engine that could recognize attacks
> so
>   the I2NSF can enforce the appropriate policies.
>=20
> Here, "I2NSF" is being used as a noun, whereas the previous usage is
> that it is an adjective, and "I2NSF controller(s)" would be used.
>=20
>   ... provide information to the client ...
>=20
> I think this is clearer if s/the client/its clients/.  "client" is
> used with two meanings, one is "customer" (e.g., in the definition of
> "Bespoke"), and more commonly as "software client".  If you say "[the
> controller's] clients", it is clear that you're using the second
> meaning.
>=20
> 3.1.9.  Lack of Mechanism for Dynamic Key Distribution to NSFs
>=20
>   There is a need for a controller to distribute various keys to
>   distributed NSFs.  To distribute various keys, the keys must be
>   created and managed.
>=20
> Perhaps combine these as
>=20
>   There is a need for a controller to create, manage, and distribute
>   various keys to distributed NSFs.
>=20
> --
>=20
>   In addition, keys may be used to secure
>   the protocol and messages in the core routing infrastructure (see
>   [RFC4948])
>=20
> Probably s/protocol/protocols/.
>=20
>   If a device had an abstract key table
>   maintained by security services, a device could use these keys for
>   routing and seurity devices.
>=20
> s/seurity/security/
>=20
> Typical English usage in this situation is "it could use ...";
> because
> "it" is the subject of the second clause, it is presupposed to be the
> same as the subject of the first clause.
>=20
>   Conceptually, there must be an interface defined for routing/
>   signaling protocols to make requests for automated key management
>   when it is being used, and to notify the protocols when keys
> become
>   available in the key table.  One potential use of such an
> interface
>   is to manage IPsec security associations on SDN networks.
>=20
> I think you need to add a subject in "... and for XXX to notify the
> protocols ..." for clarity, the omitted noun could be "interface" or
> "protocols".
>=20
> The last sentence seems redundant, as security associations have been
> discussed at the beginning of 3.1.9.  Is there a particular reason to
> point out IPsec at this point (since many secured protocols need
> keys)?
>=20
>       If protocols share
>       common mechanisms for authentication (e.g., TCP Authentication
>       Option [RFC5925]), then the same mapping may be reused.
>=20
> This sentence starts with "protocols [that] share common mechanisms"
> but then mentions only one protocol.  Do you mean
>=20
>       If several protocols share a
>       common mechanism for authentication (e.g., TCP Authentication
>       Option [RFC5925]), then the same mapping may be used for all
>       usages of that mechanism.
>=20
> --
>=20
>   3.  Automated Key management needs to support both symmetric keys
> and
>       group keys via the abstract key service provided by items 1
> and
>       2.
>=20
> s/Key/key/
>=20
> I think "via the abstract key service provided by items 1 and 2" is
> redundant here.
>=20
> 3.2.  Challenges Facing Customers
>=20
>   o  Which critical communications are to be preserved during
> critical
>      events and which hosts are continue service,
>=20
> "are continue service" seems to be incorrect in some way.
>=20
>   o  What signaling information is passed to a controller that during
> a
>      Distributed Denial of Service in order to ask for mitigation
>      services (within the scope DOTS working group),
>=20
> "that" should be removed, I think.
>=20
> 3.2.2.  Today's Control Requests are Vendor Specific
>=20
>   Without a standard technical
>   standard interface that provides a clear technical
> characterization,
>   the service provider faces many challenges:
>=20
> Should "standard technical standard interface" be "standard
> interface"
> or "standardized interface"?
>=20
>   No standard technical characterization, APIs, or Interface
>=20
> I think you want a colon after this phrase to parallel the other
> items
> in the list.
>=20
>   Managing by scripts de-jour:    The current practices rely upon
> the
>      use of scripts that generate other scripts which automatically
> run
>      to upload or download configuration changes, log information
> and
>      other things.  These scripts have to be adjusted each time an
>      implementation from a different vendor technology is enabled on
> a
>      provider side.
>=20
> The phrase "on a provider side" doesn't read well.  Perhaps "by a
> service provider"?
>=20
> 3.3.  Lack of Standard Interface to Inject Feedback to NSF
>=20
>   The following sub-section describes the problems and challenges
>   facing customers and security service providers when some or all
> of
>   the security functions are no longer physically hosted by the
>   customer's adminstrative domain.
>=20
> s/adminstrative/administrative/
>=20
>   As more sophisticated threats arise, enterprises, vendors, and
>   service providers have to rely on each other to achieve optimal
>   protection.  Cyber Threat Alliance (CTA,
>   http://cyberthreatalliance.org/) is one of those initiatives that
> aim
>   at combining efforts conducted by multiple organizations.
>=20
> This paragraph doesn't fit well in the flow of the text.  The second
> sentence seems like it's basically a reference, and the link should
> be
> put down in the references.  But I think the point resembles the
> discussion in 3.1.7, that you want to enable organizations to pass
> among themselves new profiles, which the customers or service
> providers can insert into NSFs in a simple way.  Perhaps
>=20
>   As more sophisticated threats arise, protection will depend
>   on enterprises, vendors, and service providers being able to
>   cooperate to develop optimal profiles, e.g., through initiatives
>   like [CTA]. =20
>=20
> and then combine with the paragraph which follows:
>=20
>   The standard interface to provide security profiles to the NSF
> should
>   interwork with the formats which exchange security profiles
> between
>   organizations.
>=20
> 3.5.  Difficulty to Validate Policies across Multiple Domains
>=20
>   As discussed in the previous four sections, both service providers
> ...
>=20
> Probably s/sections/sub-sections/.
>=20
>   ... and customers have needs to express policies and profiles ...
>=20
> s/needs/need/
>=20
>   This section and the next section (section 3.6) xamine what ...
>=20
> s/xamine/examine/
>=20
> (Have you spell-checked this draft?)
>=20
>   ... happens in two specific network scnearios: ...
>=20
> s/scnearios/scenarios/
>=20
>   a) multi-domain control of
>   security devices hosted on virtual and non-virtual ...
>=20
> There is a noun missing after "virtual and non-virtual".
>=20
>   Hosted security service may instantiate NSFs in Virtual Machines
>   ...
>=20
> You probably don't want to capitalize "virtual machines" here.
>=20
>   To
>   set-up this cross-domain service, the security controller must be
>   able to communicate with NSFs and/or controllers within its domain
>   and across domains to negatiate for the services needed.
>=20
> s/set-up/set up/  ("set up" is a verb (more or less), "set-up" is the
> action of setting up or the thing which is set up.)
>=20
> s/negatiate/negotiate/
>=20
> 3.6.  Software-Defined Networks
>=20
>   Software-Defined Networks have changed the landscape of data
> center
>   designs by introducing overlay networks deployed over ToR switches
>   that connect to a hypervisor.
>=20
> You probably should spell out "ToR switch"; "top of rack switch" is
> not yet listed in Wikipedia as a meaning of "ToR".
>=20
> 4.1.  Basic Framework
>=20
>   Integrity of the NSF:   by ensuring that the NSF is not
> compromised;
>=20
>   Isolation:   by ensuring the execution of the NSF is
> self-contained
>      for privacy requirements in multi-tenancy scenarios.
>=20
>   Provenance of NSF:    Customers may need to be provided with
> strict
>      guarantees about the origin of the NSF, its status (e.g.,
>      available, idle, down, and others), and feedback mechanisms so
>      that a customer may be able to check that a given NSF or set of
>      NSFs properly conform to the the customer's requirements and
>      subsequent configuration tasks.
>=20
> The punctuation and capitalization is inconsistent between the list
> items here.  I suggest changing the first two to (more or less)
> sentences:
>=20
>   Integrity of the NSF:   Ensuring that the NSF is not compromised.
>=20
>   Isolation:   Ensuring the execution of the NSF is self-contained
>      for privacy requirements in multi-tenancy scenarios.
>=20
> Probably s/Provenance of NSF/Provenance of the NSF/.
>=20
>   In order to achieve this, the security controller may collect
>   security measurements and share them with an independent and
> trusted
>   third party (via Interface 1) in order to allow for attestation of
>   NSF functions using the third party added information.
>=20
> Would this really be via Interface 1?  It looks like Interface 1 only
> goes to the customer's client, not a 3rd party service, and it is
> used
> for passing security requests.  This is made clearer in the next
> paragraph, but it would probably be better to only say that there
> needs to be an interface to 3rd parties for services like this, and
> it
> may be a variant of Interface 1 or it may be a distinct interface.
>=20
> 4.2.  Access Networks
>=20
>   Figure 3 shows how these virtual
>   access nodes for different types of customers connect connect
> through
>   virtual access nodes an NSF.
>=20
> s/connect connect/connect/
>=20
> The grammar of the sentence needs fixing also somewhere near "nodes
> an
> NSF".
>=20
>   These use cases define the interaction between the operator and
> the
>   vNSFs through automated interfaces, typically by means of
> Business-
>   to-Business (B2B) communications.
>=20
> Is "Business-to-Business (B2B) communications" a technical term?  It
> doesn't seem to me to convey any additional information, since most
> of
> the usages envision that NSFs may be provided by outside vendors, so
> pretty much any communication with an NSF may be business-to-business
> communication.
>=20
>   Service Provider:   Service requests for policies that protect ...
>=20
> There isn't a "Service Provider" illustrated in the figure.  I assume
> that the Service Provider looks much like the other three cases,
> since
> those look very much like each other, but some sort of illustration
> should be provided.  Especially if the Service Provider has further
> customers (presumably further to the left in the figure), that would
> be a more complex architecture.
>=20
>   ... may want to get
>   their dedicated NSFs (most likely vNSFs) for direct control
> purposes.
>=20
> This is rather informal usage.  Perhaps better:
>=20
>   ... may want to contract separately for dedicated NSFs ...
>=20
> --
>=20
>   In this case, here are the steps to associate vNSFs to specific
>   customers:
>=20
> There are two cases discussed in the paragraph before this sentence,
> and it's not obvious which one this sentence is connected to via "In
> this case".  Or does it apply to both?  If it applies to the second
> case only, I suggest splitting the last two sentences off as a
> separate paragraph.  If this sentence applies to all cases in this
> subsection, I suggest removing "In this case".
>=20
> 4.3.  Cloud Data Center Scenario
>=20
>   The on-demand, dynamic nature of security service delivery
>   essentially encourages that the network security "devices" be in
>   software or virtual form factors, rather than in a physical
> appliance
>   form.
>=20
> I think you want to s/form factors/forms/.  (The phrase "form factor"
> seems to be abused to mean many things.)
>=20
>   Another example is that IPS/
>   IDS services for investment banking and non-banking traffic may be
>   separated for regulatory reasons.
>=20
> Is "investment banking" specific here, or does this statement also
> apply to "banking" generally?  Or is "non-banking traffic" really
> "non-investment-banking traffic" (in which case calling it "other
> traffic" is probably better)?
>=20
> 4.3.2.  Firewall Policy Deployment Automation
>=20
>   Even though most vendors support similar firewall features, the
>   actual rule configuration keywords are different from vendors to
>   vendors, making it difficult for automation.
>=20
> Probably s/actual rule/specific rule/ or even just "specific".
>=20
> 4.3.3.  Client-Specific Security Policy in Cloud VPNs
>=20
>   Clients of service provider-operated cloud data centers not only
> need
>   to secure Virtual Private Networks (VPNs), but also [X] virtual
> security
>   functions that apply the clients' security policies. =20
>=20
> There's an understood verb at the location marked [X].  I think it's
> supposed to be "to secure", and if so, the usage is correct.  But
> it's
> hard to read, so I think it would be better to not omit the verb.
>=20
> 4.4.  Preventing Distributed DoS, Malware and Botnet attacks
>=20
>   Many networks such as Internet of
>   Things (IoT) networks, Information-Centric Networks (ICN), Content
>   Delivery Networks (CDN), Voice over IP packet networks (VoIP), and
>   Voice over LTE (VoLTE) are also exposed to such attacks.
>=20
> This seems to be just a specialization of the preceding sentences.
> Does it add more information?  (E.g., perhaps there are special
> considerations for each of these types of networks, in which case it
> might be useful to state that.)
>=20
> 4.5.  Regulatory and Compliance Security Policies
>=20
>   Organizations are not only supposed to protect their networks
> against
>   attacks, but they should also adhere to various industry
> regulations:
>=20
> It's probably better to s/should also/must also/!
>=20
> 7.  Security Considerations
>=20
>   Having a secure access to control and monitor NSFs is crucial for
>   hosted security services.
>=20
> Probably s/a secure/secure/.
>=20
>   Therefore, proper secure communication
>   channels have to be carefully specified for carrying controlling
> and
>   monitoring traffic between the NSFs and their management entity
> (or
>   entities).
>=20
> I think you can condense this to "management entity(ies)", but you
> probably should talk to the RFC Editor about it.
>=20
>   In addition, the Flow security policies specified by customers can
>   conflict with providers' internal security policies which may
> allow
>   unauthorized traffic or unauthorized changes to flow polices (e.g.
>   customers changing flow policies that do not belong to them).
>=20
> I don't think you want to capitalize "flow" here.
>=20
> It's not clear to me what "which may allow unauthorized ..." applies
> to.  It seems like there's an important issue in just
>=20
>   In addition, the Flow security policies specified by customers can
>   conflict with providers' internal security policies
>=20
> It seems that solving I2NSF requires a clear understanding of how the
> customer's policies and the provider's policies interact.  (I would
> think something is allowed only if both policies allow it, but the
> reality may be more complex.)
>=20
> The rest of the sentence seems redundant given the discussion in the
> rest of document.
>=20
>   Therefore, it is crucial to have proper AAA [RFC2904] to authorize
>   access to the network and access to the I2NSF management stream.
>=20
> It seems to me that this is a rather generalized need for I2NSF, and
> not connected to the previous sentences.  So I would omit "Therefore"
> and put it as a separate paragraph.
>=20
> [END]
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Tue Apr 11 13:11:19 2017
Return-Path: <martin.vigoureux@nokia.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B04141294B2; Tue, 11 Apr 2017 13:11:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.811
X-Spam-Level: 
X-Spam-Status: No, score=-1.811 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=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, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (body has been altered)" 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 v-jEnwVTzShF; Tue, 11 Apr 2017 13:11:15 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on0134.outbound.protection.outlook.com [104.47.1.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02F47130F27; Tue, 11 Apr 2017 13:11:13 -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=/7RV0h0RauCO+TljaUch5qMUCheQJfng9Ja5156VxR0=; b=OmWfRf3H8RaUB0slfoDiOIOG3FlSYu/lqGiugpcuv7WRL5KPJn0CmwF79om5M9rKQDo9ui3MGeFrqEV7pSDRHhPcphw/qwZUVNIwJn1IslsLsJMQzl0CZcXMw5ykBGZLE95vi0YUA6pxXH7zdpUBntY6Ock/NQ5ukxWCa/Uk7TU=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=nokia.com;
Received: from [192.168.0.22] (88.182.48.47) by DB6PR0701MB2470.eurprd07.prod.outlook.com (10.168.75.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.5; Tue, 11 Apr 2017 20:11:10 +0000
To: Roni Even <ron.even.tlv@gmail.com>
References: <149171742319.3063.4555090995663652452@ietfa.amsl.com> <2AA8DBB4-EBA6-45B1-85B7-E8C7176C35A6@cooperw.in>
CC: Alissa Cooper <alissa@cooperw.in>, <gen-art@ietf.org>, <draft-ietf-bess-evpn-vpws.all@ietf.org>
From: Martin Vigoureux <martin.vigoureux@nokia.com>
Message-ID: <d9044626-126d-4271-32a9-c3fe6fe299d2@nokia.com>
Date: Tue, 11 Apr 2017 22:11:08 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <2AA8DBB4-EBA6-45B1-85B7-E8C7176C35A6@cooperw.in>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
X-Originating-IP: [88.182.48.47]
X-ClientProxiedBy: VI1PR0901CA0105.eurprd09.prod.outlook.com (10.173.68.31) To DB6PR0701MB2470.eurprd07.prod.outlook.com (10.168.75.151)
X-MS-Office365-Filtering-Correlation-Id: 30af89a2-f9e2-4cff-fa71-08d48116e60a
X-MS-Office365-Filtering-HT: Tenant
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(48565401081)(201703131423075)(201703031133081); SRVR:DB6PR0701MB2470; 
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2470; 3:eohdNU5PyPnfYsw4MWnYV0q7oU20GhgdHLpqx12xGS91eodpFTQRxWOJe6VwIZaPuOszENsb97AocUwmmv668HZb3ik2rOBHw3+8MUK5XeZ1PQAQOqExw56RCME6YBrCldZGBFh2/D0R9/8hj4NFQwcOcMe2FBYe3xuJ57WJI6ey5FEtSPqN72dI+s+QM7rH4KUGzukK7fM/6ad3/5cZ12ZG9VraNW5jcWq1GMn2O4yCuLUu2Sgs3U27ImPpGsCq+2zHRMgeE/R1GTeNmXMFEfYC75ZlZW3X6mmNzzEVB3MJE4rFfId63NjbQLObcgnogZHx+CATxd6/VgKpm+kjMXnWoJIuelopCisW08SdNjc=; 25:IjMjlgzRzb8z9QSMXTSJ6PHbHOKbQcOl+w+1kOcyh9zdfaLQ60c5o2QiEIm+a3XSTWZ1r/aHasWLiPb2pJ6KVy8bOtWSge8ox4huwMpUnPMs4o2FzN3sN7/8HX460Mdjh5JtW5J6JddG8HNU/OxbeN2IRNfMd8WPk9seF/YMFIHEYKh+GQW5NIDG8lY5S2Ca6bzI8N/vBKyzae9kaHFqcZUfm5cke9aPdEOCOEwn64OrH36flGgvxH5WhKbeNSgo4il2BnNCvrqy0oqV81G3yuCxHYlA/qvjPWxQ4rLM+V2BSNi+h+OomW5IvroOXvubmyP0KLjcl6zasJKV2phP7JJgrfpP4IMIA4CeYdfdiPAAkNJP94h1Rx4uqGf00wxVZpYkQ12IfAmCbmFrDrfdJfmAnXxI1TgS4dyufop1U9nhOjyeeEqrKAd5sYMrMcUIatPOt2fbYsyRAsWWZ9XRRclsFKh6gPgM0S+uMPLkDis=
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2470; 31:FCHV4siJ9k+avLqbEznvA3LmrvTFLDzoKl/GEqoB+ghJ18VTTv3T/jt5f1taMFegeX7UIfbBNANg91HqcVRy7auJ0jImUqxJfbvst9WUZnJdjGc2no4koMAcIfggmf7HkkbeinJbh4sMbJf7Le6PrdqG4RI5SAWLlZVDbx+lZMtvUPCiXLbnyb8qrnnimbt1DRgtkdQqn5F8PkUPC/8t3e1QfJ0NdvK5UevlebWhBiHCg5aPy+K9rMjCxJs1kOhRRtsI9aXVuEa9GWh68kDDF2bYOMtYSh8LnWkfRHzm7iM=; 20:yM+qcuko/NpMtpqp23/7aNAqhx/UBFWKB4+ywZxGDNZ1TC208ckqioAkFB/CFgF9GZBvybFPTflodXu5VrvU84hRDxK7aG8QB26kMrt5jET4ie9fdZVZMCg57Urym9PR/W0lOT2nIL0xwFSt4HHvHRHsMwEpjFd6Py9NHfjGEtC4BzfhoLK54KuI2GZLRb2Y2F/EUYdUpRUloUIzYSx9jdx3FdEX1U9m6wiLAszWIFDLbJ7M0mGpasJSSov/6MU56CL7vA6REoN/wXc+HjK+utrMmbmoFZ2TvpAjhax2NzcH5e7HyRl/QGmsmslf9qjzasrWSd0xcwAQ3eHvvRYsNNAzHxB2AeEbyp93ylJHN7P219haxmY1kyt3ko54CYiw9O91BGa/STZmalW1Wc2Svoufrx3ZLlwl6lza3CfsinlQaDplh0QVZKvMQoQ/Yb3tHrJGk347X6NH/dlPJO8xe05K172Mje8mPMCwZFwu87UXlNJsyEA6vJcAya7tFMpk
X-Microsoft-Antispam-PRVS: <DB6PR0701MB24708F0DAC515879861051718C000@DB6PR0701MB2470.eurprd07.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(20161123564025)(20161123560025)(20161123555025)(20161123562025)(6072148); SRVR:DB6PR0701MB2470; BCL:0; PCL:0; RULEID:; SRVR:DB6PR0701MB2470; 
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2470; 4:ZDuypv6JjI56Jr8FG3oU162C4ys782ojBxM8uH3NhdgqGbeeF3l21HVjBfAolyR6F0Oeok/onCOPcEcXWqQdtYm8dFSxxHKf4zhhiK3A9qCIO8bGOXooET/etjQBjMHNTPGqcmNAbqO/X0FwFeURFiZZ7iEHC95dQb0FuboaZo6Cf9PGLAtyfbOVXLpjHoPPG3x1AOp2SSp65db8iw2hZrLn04PzgC7vSRJc0eOadhIL1tCJ8Ec/rySIjdi3bfXcaV+B/EI/d8xKpGIx7WqenGU5W97aH1LEGsGry1aizqKYYCinw59hOr/zLdu+Sz8ztVEYlv6mIMFt4yY8uorKNtkvmQCIo+e3ut8BNuQJRnhrd7aWJIBehkZ0P3fq9kvn8O6DhdCgjSqZ4pCyqfAOYJU42YW69birfm2ssUda5IuZ6SdKp3kyPqMDX1PBmSoPB6652FEYbxYOPO+PRIa0q0f89qkisCxE+F6IeJ+MjafRj7m6HFDXwSOs6c1FT0obeP/5yZGFEIt4A0n/AOcrRJeusdo33eItS+0ftJN5BRMeHZt2JEH/acD+PUNaoWzfE09MXqgb2ZJ4/xprJsBzHIZg34kOC+drFTdKycIodD/Dr+3Mklome2jJewGeNhuQNB1p/tyEVkOpeQqEs+23CokA8At7vuwmUYEAyM3uFxV0IBj+kNdVnA/yOV/3ddfcFtFPSFsM4TR0Wo2ekXQL0890n7e5v4laOeac9+Ew9mk=
X-Forefront-PRVS: 0274272F87
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(4630300001)(6049001)(6009001)(39400400002)(39860400002)(39850400002)(39840400002)(39450400003)(39410400002)(24454002)(377424004)(377454003)(50986999)(76176999)(77096006)(38730400002)(345774005)(54356999)(23746002)(110136004)(4001350100001)(50466002)(7736002)(2950100002)(6916009)(305945005)(189998001)(5660300001)(4326008)(2870700001)(6486002)(6116002)(53936002)(83506001)(65826007)(3846002)(90366009)(6246003)(25786009)(8676002)(81166006)(66066001)(230783001)(117156002)(65956001)(2906002)(47776003)(6306002)(33646002)(36756003)(54906002)(86362001)(31696002)(42186005)(31686004)(229853002); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0701MB2470; H:[192.168.0.22]; FPR:; SPF:None; MLV:sfv; LANG:en; 
X-Microsoft-Exchange-Diagnostics: =?Windows-1252?Q?1; DB6PR0701MB2470; 23:q3DxlTVeir01cCjQToo2zTEzQrXzz0KoUcE?= =?Windows-1252?Q?rRr8UiOnchGaczPetZsm3cGtrrnUHRUlplgk4mICSTjeiOCCaQrbVVzM?= =?Windows-1252?Q?3U/9l5JP8dzj8OvTNMDPdpnEh+W9tpaEPaOHRz5JXNqqGli8q8VCTRdn?= =?Windows-1252?Q?SVt7/ruqa4puzG6BpWX11IBvAFz5rtkUjwe31NBbDkSIBFcgT8beChdH?= =?Windows-1252?Q?VroJbFwNuX0wxHxP+Kx0E4+vgKG18E1jNzbTV/uoC+bfNSPBgAy2Z5jv?= =?Windows-1252?Q?kc8m3ZY5k19Dgkc0+VqY1kHA2iws+956Y/i1gqo7PBPjU+jcgTXJVMso?= =?Windows-1252?Q?yKIhvceBrp0UKmAb49jWuAxP/8L+2JeToA6VW+V9sOhWbeQjQRD78Vca?= =?Windows-1252?Q?Tdos/hd7lgnCxPfrFbLnsDzZQs5tv3uRTMcRoxavu3Owm5HUKUkxOo5A?= =?Windows-1252?Q?9UgLE4Y+02yuwspe0IUr5bx50cmDcqkcNMGCCT0mOjRmVA7RqSZMumsr?= =?Windows-1252?Q?aMOg9YRonvY6CJwt8nk/i4Vh0o+YjR068WIkGnrtHfN/awtJhK+mS5fr?= =?Windows-1252?Q?zu3LwagE7s79lVc5d9+g7VJoHLvpXtMSNhUtd+OjkJbJ2Qcspqu84bu0?= =?Windows-1252?Q?iErP5nTBYeGjPJ7S++jYcdvoNg9NKs86A7vowtEZmLaoxydLdKi5Snv5?= =?Windows-1252?Q?dvRFhJD6JBZbmuDwAV6B9Kt3F/wLtIh38cWFyiVNFFCeJXJJ9j2+/SU1?= =?Windows-1252?Q?crNTPJw62w1HEbSI/SHBOIQcqKplRrtFzeP8JG7WOI8W3X13mTtXxQ0m?= =?Windows-1252?Q?0wyCB1qj7w25ceEViD+lN9nLMnbi61I6/E8vvTDYJ6wZBFs8pCMZJrWW?= =?Windows-1252?Q?bspTY9hMX5BP6Fc7CSyBiZXRKKtAL209v9E4FNnjVyh0OA6OVg1RsTcC?= =?Windows-1252?Q?xWB9SQpDAGQGKSxYZc17fSVk9roex1hLOZVDmsTdLPl1LW0mROhyV7hq?= =?Windows-1252?Q?Ohaa2LvGKS8bLZfRdBWManJTP6XJ6Y/P1sC8zHk4E/DB39ALm8MsvCPj?= =?Windows-1252?Q?bAFy2vBrE287EJ5U+GRbC8eYMKx7CkdMQTMHbYI8X2rIFQLCpvOXrH/q?= =?Windows-1252?Q?MGeqj4Ax6dhGUuZtmlATcYGKNvd5WGGvNYGkT9eRT7fbNnPyB3Z5mhJY?= =?Windows-1252?Q?bJAoa8HegD4BB4XbDceTx6xc7egYxkqmIIXTWmhFOWXvOySm4Zkobyug?= =?Windows-1252?Q?Zf7Ac5LVJqDtjS4BBOJQEYUlAto4eV94aHeK/8rRdc2Tzn17LthmuayZ?= =?Windows-1252?Q?YSxDpF6aJ85IrDf0itxSPz3NCZcP43wucQTEb4n/pz5xpydJ+sMQMzRU?= =?Windows-1252?Q?K/lNoksQa2DCqnlHMSIpXExVfwqXMLvzsqwp/J5cjmk72uQTgnlXr/Zv?= =?Windows-1252?Q?azBOnHkZTPZ2sQyN4DGFFd+eqJXCEl9bwpQ39iOnxNt5dX7EtsGIHMtC?= =?Windows-1252?Q?MR4VlE0c=3D?=
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2470; 6:R9zp8xeUwchH5EdpnshH6/JElTp1lbB8TBuqVZm2RPPVR83Xn/HmK1HtdlLUfB7m4Q3G97DaT+H+c/SQcwtn7J2XmDv6McJYfL7nea+tIqcIF5F21xB3hdrYMMwWCvc0F9Bx8suG8QLnzIyWBgVZj1x2USbiAyuawMPB7aBVxX84WU/fZ+/Tq59bPjxljuIx23OoFpWrFnjC129sY4+1111hTgE0wI+DE/K+UbIuBpo3G40foy2vGOQGE/FD064+SptFOgt2EKHuiO/BfIau1r3EcGL4GBCNXncJPRA87NrEPRSjp6YSoyfZfRWcHHJQHvHmj0xiZsjN8fDJt6eU2MnoPi2vMm2yM/nRBA6npNWpJOa8yESX/c7QIEwvTBRlSbiIhAmmTo8iEQEs/pa1aPxTWLqLkjtcYnzx2P6HeYwzvPGuCSvX6/rj5IRkSFzJldLMmq/dBJK/IbLk9ProI7YKrlzrnAY5YBwD/N7bL7Q=; 5:qwUN4yJHaaTgHMgf13AN7E3R4VDfaCWra2XmWq3MswIYTSZE5tbgqK2ChccskoZyp59R7p78EHBIvhRsIqOuhAml9dNY7V6wXq5T5hiaU241j6ZvTsphHWlPH2hCPLcw4pVS+cUaJ54R3bIb0jOAEQ==; 24:Fbr3K1DWxOj7/HWjKIQri8h/NDe3ftzIDx6c51ng+XDRMufXCPc/CO23GW6aFqyt6/rAaSQ0dzJaXgnVirbONYFKx9b50927uDGR5KbnEO8=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB6PR0701MB2470; 7:T2ohm9rgd3hs2EnLie6cCKvAdvcsxLImNYdzX3+iDaJfZaXZqu583fanPC9V4xORTT283C2UpPYZDpS6G6ebWBNYc341L651Zn7qsSZ1yrwd/6nXhP0IWHPnap8i4cR9LX86ekqjHIuxP63J75ikccP76EHXKwJSrDJhAWYNuE0vK86jAmHZ9HnIcsdKetJulMwGNMe/CdLPzGRjOxq0CISkLr1YyGJmkeiQ/ptR8nC3T2A8A0r8xnyoMunK9+94QmxaIYeT0VOwXUjOcfXsFvzjVPoJA+RkAVDBha6XLlf7SdHGVe/VAj2gqtSlDza4wizlMosClwnGfPW0/T7ttw==
X-OriginatorOrg: nokia.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 11 Apr 2017 20:11:10.8610 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0701MB2470
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/bUmwtB-jSLY72lS8V8M8Df23Xck>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-bess-evpn-vpws-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2017 20:11:18 -0000

Hello Roni,

I believe this is an artefact of the HTMLization of the doc. I think 
this happens to all drafts/rfcs. References as the first "word" of a 
paragraph are not processed as is and so no link is created.

martin

Le 11/04/2017 à 20:56, Alissa Cooper a écrit :
> Roni, thank you for your review.
> Alissa
>
>> On Apr 9, 2017, at 1:57 AM, Roni Even <ron.even.tlv@gmail.com> wrote:
>>
>> Reviewer: Roni Even
>> Review result: Ready
>>
>> I am the assigned Gen-ART reviewer for this draft. The General Area
>> Review Team (Gen-ART) reviews all IETF documents being processed
>> by the IESG for the IETF Chair. Please wait for direction from your
>> document shepherd or AD before posting a new version of the draft.
>>
>> For more information, please see the FAQ at
>>
>> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>>
>> Document: draft-ietf-bess-evpn-vpws-??
>> Reviewer: Roni Even
>> Review Date: 2017-04-08
>> IETF LC End Date: 2017-03-10
>> IESG Telechat date: 2017-04-13
>>
>> Summary:
>>
>> Major issues:
>>
>> Minor issues:
>>
>> Nits/editorial comments:
>>
>> In section 1 second paragraph "[RFC7432] provides the ability " looks
>> like the reference is not a link to RFC7432.
>>
>>
>>
>> _______________________________________________
>> Gen-art mailing list
>> Gen-art@ietf.org
>> https://www.ietf.org/mailman/listinfo/gen-art
>
>


From nobody Wed Apr 12 07:31:37 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18F99129BE0; Wed, 12 Apr 2017 07:31:35 -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=FAFqQNVr; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=JxZx5pAj
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FOjv7n5IDzBW; Wed, 12 Apr 2017 07:31:31 -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 3FA4E129BC1; Wed, 12 Apr 2017 07:31:13 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id A94D420B98; Wed, 12 Apr 2017 10:31:12 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 12 Apr 2017 10:31:12 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=in+Lv+fI2h7OQileYs 015r4xYITacCN3rNEU00Fjh4c=; b=FAFqQNVriSM2a3VgSDG2v0DHTeNqxPiJ8k Qrn3oRHS/0htROXZ6CpW3TRLCFBcy69RfnrZCHSLy3HoGpEA6pW/At3qM0b4KtgN TYxRaecGhL/NqfWSYUbdm7dHR/78jXOujTIUeYomBN0QGD/WRZl+FHBes3EaL5n7 p8zKog/mh2LWEuVZftS18phnMjfYzwrEDr3m29PIotNvNW3XZGJkZHZ723BAA/TS Mkuie1fWhVGYh0ZYASmN1OmVNV6hxz+WWiGCVgyMrZmiLQ98mUhfwklEU+XLJTKp qUlNHp/9JuY2i+rqQ5qqBE84YzeR1xshILTMhh3h/RNRYjszRHNw==
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=in+Lv+fI2h7OQileYs015r4xYITacCN3rNEU00Fjh4c=; b=JxZx5pAj xeMM3zrInMEjStEHjOf4i+EmCcpgJqpkO4MKN2C/ke27IBsDbp359eMUjueAyKdM Wkt+TFQbKjDerqnvOQNAZKjQIf4aBeoeYxugiVCc1T2xPyIzxhuRmHnMQCIRnKIz eQ16xG7h2WYpFVWUu8xX4ZcJD3cjY1aehqyhkSlACuQYuNgo68vNy54a1zsFogqR mEoD/Mn/6bkeorQYHFlGktXqtwe/RlaNIf9x5DjPbVC+2CQp8fKstQim/8oXe2GO P8yj2RK2TlGm8tEkDv6ZSK1w37A5fZlWXwlLM8La7W/TrGHTBye3DupVzJpS97Dc ZmDT7nsjWnOlng==
X-ME-Sender: <xms:MDruWOqsHOVLfuzw09qF0GHk8lwResLaykZG3nSDGUDa1_LYUpQsDA>
X-Sasl-enc: R37p2lq4R56NwU9YU0d/N0hxJnhmhi8MK3qOenX/ZMhV 1492007472
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.182]) by mail.messagingengine.com (Postfix) with ESMTPA id 1FAEA7E399; Wed, 12 Apr 2017 10:31:10 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <7D0ACEF0-2A1D-4AC9-A88A-F357B936ABF8@cisco.com>
Date: Wed, 12 Apr 2017 10:31:08 -0400
Cc: Francis Dupont <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" <gen-art@ietf.org>, "suresh.krishnan@ericsson.com" <suresh.krishnan@ericsson.com>, "draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org" <draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EB53B674-1DC2-457C-A398-2E0AB77EB8A5@cooperw.in>
References: <201702271130.v1RBUZaY065404@givry.fdupont.fr> <11C3DA1E-287F-40FB-8900-8C74F9D6A51A@cisco.com> <C9D5E5D0-AD13-470D-B0AA-E107FE2B185A@cisco.com> <7D0ACEF0-2A1D-4AC9-A88A-F357B936ABF8@cisco.com>
To: "Dhananjay Patki (dhpatki)" <dhpatki@cisco.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ngTe4TVCfFMyPe9xoW6LkFtKavg>
Subject: Re: [Gen-art] review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 14:31:35 -0000

Thanks to Francis for doing the review and to the authors for =
incorporating his suggestions.
Alissa

> On Mar 11, 2017, at 12:51 PM, Dhananjay Patki (dhpatki) =
<dhpatki@cisco.com> wrote:
>=20
> Hi,
>=20
> I uploaded version 04 of the document.
> --
> Regards,
> Dhananjay
>=20
>=20
> -----Original Message-----
> From: "Dhananjay Patki (dhpatki)" <dhpatki@cisco.com>
> Date: Friday, 3 March 2017 at 10:59 AM
> To: Francis Dupont <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" =
<gen-art@ietf.org>
> Cc: "draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org" =
<draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org>
> Subject: Re: review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
> Resent-From: <alias-bounces@ietf.org>
> Resent-To: <dhpatki@cisco.com>, <sgundave@cisco.com>, =
<jonghyouk@smu.ac.kr>, <fuqiao1@outlook.com>, <lyle.t.bertz@sprint.com>, =
<jouni.nospam@gmail.com>, <maxpassion@gmail.com>, =
<suresh.krishnan@ericsson.com>, <terry.manderson@icann.org>, Dapeng Liu =
<max.ldp@alibaba-inc.com>, <max.ldp@alibaba-inc.com>
> Resent-Date: Friday, 3 March 2017 at 10:59 AM
>=20
> Hi Francis,
>=20
> Please let me know if you are fine with the rework of if you have any =
further comments.
> --
> Thanks,
> Dhananjay
>=20
>=20
> -----Original Message-----
> From: "Dhananjay Patki (dhpatki)" <dhpatki@cisco.com>
> Date: Tuesday, 28 February 2017 at 9:46 AM
> To: Francis Dupont <Francis.Dupont@fdupont.fr>, "gen-art@ietf.org" =
<gen-art@ietf.org>
> Cc: "draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org" =
<draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org>
> Subject: Re: review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
> Resent-From: <alias-bounces@ietf.org>
> Resent-To: <dhpatki@cisco.com>, <sgundave@cisco.com>, =
<jonghyouk@smu.ac.kr>, <fuqiao1@outlook.com>, <lyle.t.bertz@sprint.com>, =
<jouni.nospam@gmail.com>, <maxpassion@gmail.com>, =
<suresh.krishnan@ericsson.com>, <terry.manderson@icann.org>, Dapeng Liu =
<max.ldp@alibaba-inc.com>, <max.ldp@alibaba-inc.com>
> Resent-Date: Tuesday, 28 February 2017 at 9:46 AM
>=20
> Hi Francis,
>=20
> Please see inline responses. Also, please find attached version 04 of =
the draft attached to this email. I will upload the new version once you =
approve the rework. Or would you want the updated draft to be uploaded =
first? Let me know if you have any further comments.
> --
> Thanks,
> Dhananjay
>=20
>=20
> -----Original Message-----
> From: Francis Dupont <Francis.Dupont@fdupont.fr>
> Date: Monday, 27 February 2017 at 5:00 PM
> To: "gen-art@ietf.org" <gen-art@ietf.org>
> Cc: "draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org" =
<draft-ietf-dmm-lma-controlled-mag-params.all@ietf.org>
> Subject: review of draft-ietf-dmm-lma-controlled-mag-params-03.txt
> Resent-From: <alias-bounces@ietf.org>
> Resent-To: <dhpatki@cisco.com>, <sgundave@cisco.com>, =
<jonghyouk@smu.ac.kr>, <fuqiao1@outlook.com>, <lyle.t.bertz@sprint.com>, =
<jouni.nospam@gmail.com>, <maxpassion@gmail.com>, =
<suresh.krishnan@ericsson.com>, <terry.manderson@icann.org>, Dapeng Liu =
<max.ldp@alibaba-inc.com>, <max.ldp@alibaba-inc.com>
> Resent-Date: Monday, 27 February 2017 at 5:11 PM
>=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-dmm-lma-controlled-mag-params-03.txt
> Reviewer: Francis Dupont
> Review Date: 20170217
> IETF LC End Date: 20170224
> IESG Telechat date: unknown
>=20
> Summary: Ready
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:=20
> - ToC page 2 and 9 (title) page 8: Acknowledgements -> Acknowledgments
>=20
> [Dhananjay] Both spellings are valid. I see the former in many RFCs. =
So I left it as it is.
>=20
> - 1 page 2: you must expand the abbrevs at first use in the body of
>  the document: the abstract is not a part of the body.
>=20
> [Dhananjay] Corrected
>=20
> - 1 page 2: singaling -> signaling
>=20
> [Dhananjay] Corrected
>=20
> - 3 page 3: suboptions -> sub-options
>  (because the dash was at all other uses)
>=20
> [Dhananjay] Corrected
>=20
> - 3 page 4: the wording "The sub-options are optional" is ambiguous:
>  it can mean that there is no mandatory sub-options or that the
>  field can be empty. Obviously it is the first according to the
>  section 3 intro "MUST contain one or more".
>=20
> [Dhananjay] Corrected. Reworded as follows.
>=20
>    =E2=80=9CLCMP Sub-options are described in the below sections. The =
sub-options
>     can be present in any order. Inclusion of any specific sub-option =
is
>     optional, but at least one sub-option MUST be present.=E2=80=9D
>=20
> - 3.1 page 4: Binding Refresh Control Sub-Option ->
>  Binding Re-registration Control Sub-Option
>  (it is the official name of the option cf section 6)
>=20
> [Dhananjay] Corrected
>=20
> - authors' addresses page 12: China -> P.R. China or ISO 3166 CN
>  BTW I have a question about the "Kansas": I can understand
>  to put only the state for California or Texas but Kansas? (:-)
>=20
> [Dhananjay] Changed China to P.R. China (though I find many RFCs that =
use just China). Is there anything to be corrected for =E2=80=9CKansas=E2=80=
=9D? :-)
>=20
> Regars
>=20
> Francis.Dupont@fdupont.fr
>=20
>=20
>=20
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 12 09:42:40 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00C501317A6; Wed, 12 Apr 2017 09:42:39 -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=LfFL1l0A; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=apnBY/80
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BfRh-tZiJP1F; Wed, 12 Apr 2017 09:42:36 -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 12E01131798; Wed, 12 Apr 2017 09:42:24 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 701AB210F0; Wed, 12 Apr 2017 12:42:23 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 12 Apr 2017 12:42:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=aZTeyVcsoshVtHAVPn L6hcMu2Wh0hSCILOxNP9IRBNU=; b=LfFL1l0A82/zLfbj+5yQfCWM/jJAlVIQ6B 3B19ggsUhYFDP9a2oz2m0xL5Z6SmTHGpJ6cVJ4SFt9L3MRkTXChhdLdfY9iVop7M yV08GmxeD9TtJ++MIYCh7zhI91YybJFZIMJOmgV9aHr6lBk0OzqRIdLnpH8ac8fl H2BDavVYmkNN36YRPe9F0W9UfWrbCJtIwi/dBUQh9CY+w/qc2gpHHQ0lalx3lL9w P5af5l0xuFpPNQhNMk7sF3HF2G/EApoSITI0ZD1hmkHG+eYYpJ5Cct5ZwWpKjp8+ uc+0FblKjTMdpU/4/VrQOuhwfw6nYQ+Mn56OTIL2dQBFEd1yRB+Q==
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=aZTeyVcsoshVtHAVPnL6hcMu2Wh0hSCILOxNP9IRBNU=; b=apnBY/80 JxDUSJFXwK3w6lgdkO+XCCminSmues4PP+KeJ4OM+mmUYfWRSF7iuysDaxIpVeou TWk3UfwpSrP7pWQ0SO4u2AQttzPUdX6HEHmOiX8ezol0/70myFlKQrJzWQKTL2oZ XWHTzkshfzsS4s1sD9MFSyYXR7iBGoB4RhGEkJL2ZGadM9VVtlpYIhEdKQD90adM 5mIJ1QKmxXM/mN1Wkfuai1gZ2me36EeWtO8TzsZ1BUkRsHpcp+4/o2adgECwy5Eq uS9l1WZZI1+fdqgBkJZ9VO6bEu81csH/KZ2z1o0w6Y1dVcpV+qXx0495UrHGkqSD +KxodJSSLmOBFA==
X-ME-Sender: <xms:71juWGwxfj4KLjli_Z_B1--wvW2hjS91IVPKi0tANiSP7aKF5FpmPw>
X-Sasl-enc: zk7Om1TFcWjNOWNa8FN9WRm1+xZ+NT0T55gbuKMUOvnI 1492015343
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.182]) by mail.messagingengine.com (Postfix) with ESMTPA id 929BD7E669; Wed, 12 Apr 2017 12:42:22 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <CE6FB235-45A1-44C9-9661-AF1325BAE8EF@ericsson.com>
Date: Wed, 12 Apr 2017 12:42:20 -0400
Cc: gen-art@ietf.org, draft-ietf-alto-multi-cost.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <1640F6D0-AB24-4BEE-9BC2-559E65CA25B0@cooperw.in>
References: <CE6FB235-45A1-44C9-9661-AF1325BAE8EF@ericsson.com>
To: Wassim Haddad <wassim.haddad@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/s5HGOOEh0Dekq-VWWgBZmscpYMI>
Subject: Re: [Gen-art] Gen-ART Review of draft-ietf-alto-multi-cost-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 16:42:39 -0000

Wassim, thank you for your review!
Alissa

> On Apr 6, 2017, at 4:37 PM, Wassim Haddad <wassim.haddad@ericsson.com> =
wrote:
>=20
> I am the assigned Gen-ART reviewer for this draft. For background on =
Gen-ART,=20
> please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>
>=20
> Document: draft-ietf-alto-multi-cost-08
> Reviewer:  Wassim Haddad
> Review Date: 06 April 2017
> IETF LC End Date: 27 March 2017=20
> IETF Telechat Date: 13 April 2017
>=20
> Summary:  This draft is ready for publication as proposed RFC
>=20
> - Major Issues: None
>=20
> - Minor Issues: None
>=20
>=20
> Regards,
>=20
> Wassim H.
>=20
>=20
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 12 09:43:01 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4B2012EAE8; Wed, 12 Apr 2017 09:43:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=gCc1KOQg; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=h49m1wM7
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dOpO3ngDk5I7; Wed, 12 Apr 2017 09:42:57 -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 99724129543; Wed, 12 Apr 2017 09:42:47 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 03C6720FA8; Wed, 12 Apr 2017 12:42:47 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 12 Apr 2017 12:42:47 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=6i0iIephPqDgKHcmDS vEz62aMzDXQzwlnKRRLpqv0oM=; b=gCc1KOQgpYiR+ZjjyQSKydeYj/G0ETotPW +IXNOiXcxbwH4Vc1+YLguffG6YfViqETLtVN/i6PRNiBSu3UM9R6rahSbHAnjCm1 4gRAr9QiP//MtdgTGmXCN3zX1O4FBnPuOcVUztufHOPORxtcijDuWxsv8LViJN7r 4appe0M75s+n88sURy+UpAuS2SerUMQ/dCPVGEe44/lNczFLelhrZ899JozUflBR V+yk6nomgxJGt7J85j0CrbkIxHwxEBc4TnGqPsf1Sbuy1GF+/6t/dGV9HVlKd9zh epqoFcE1MR0n7SGOdkLB0oRiHk5TiKvj1E36wR8W/h8TmKb0I5lg==
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=6i0iIephPqDgKHcmDSvEz62aMzDXQzwlnKRRLpqv0oM=; b=h49m1wM7 mMm0SniXkmoB1pPubhAp24C4XLzKCLLnwv9F7oZ2PfgqwM5OJ7Nt4bmcHc2OnQB9 yyRC5D4XKOcVDJWvyn1OBtNWwiNbLg3yeeyBnsx7+RPqCKn9QvwaROQTf1RaQn1g tQxqslB+so/ot8XDS/JRajRITDnKqyzvkfsZMTYmjzgq8rqgrrcDCDED8HMMutyR kGZGSOaA38F/QTaSGondERkRe0GfWeUEw1Z2nZGl26yjEHUoCzvO01F9JO8MtTS1 qjGJVuLb4u2n+3Q2YFJ3QHOjKI8bnuIrqYpihzUj8SpISJlV2oEIpTQSWYXH+Gat QsVHxjsUxeTc8w==
X-ME-Sender: <xms:BlnuWMpkov6gtauFHc_Ors6AWuQufhYVC-TUuwDubBQaAcFL_Qq-pw>
X-Sasl-enc: ELa1/7YtDtw9KnTw/47i6wR2gAWyQrF7aac1t3WcFRsm 1492015366
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.182]) by mail.messagingengine.com (Postfix) with ESMTPA id 30E407E15C; Wed, 12 Apr 2017 12:42:46 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <149096796486.21620.15409836640558971168@ietfa.amsl.com>
Date: Wed, 12 Apr 2017 12:42:45 -0400
Cc: gen-art@ietf.org, draft-ietf-ippm-6man-pdm-option.all@ietf.org
Content-Transfer-Encoding: 7bit
Message-Id: <4019A5F5-4C51-4ED3-B6D5-D0112A55287D@cooperw.in>
References: <149096796486.21620.15409836640558971168@ietfa.amsl.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/qozo8g494RH7yyxa-Zc-lOGVlkU>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-ippm-6man-pdm-option-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 16:43:01 -0000

Jouni, thank you for your review!
Alissa

> On Mar 31, 2017, at 9:46 AM, Jouni Korhonen <jouni.nospam@gmail.com> wrote:
> 
> Reviewer: Jouni Korhonen
> 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-ippm-6man-pdm-option-??
> Reviewer: Jouni Korhonen
> Review Date: 2017-03-31
> IETF LC End Date: 2016-09-28
> IESG Telechat date: 2017-04-13
> 
> Summary: Ready for publication. I did review earlier version of the
> document and the comments I raised back them have now been addressed
> to an adequate level. 
> 
> Major issues: None.
> 
> Minor issues: None.
> 
> Nits/editorial comments:  None.
> 
> 
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 12 12:32:29 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A02912952C; Wed, 12 Apr 2017 12:32:21 -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=l2itjAqw; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Ehgg10RP
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1lmg5fQtfbaD; Wed, 12 Apr 2017 12:32:19 -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 EA97012EB3F; Wed, 12 Apr 2017 12:32:16 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 6080020EB1; Wed, 12 Apr 2017 15:32:16 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Wed, 12 Apr 2017 15:32:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=aSuH1/uTq2A829KkXT 8jfzadRmcL4KmPPNH5iNl07dY=; b=l2itjAqw5LAuQg0oDoXVaQr36PigAETxQk PErdZueIrKiCIAsO/81wRbJnYQ9yQjQeadIpvlWOn0u0oymIYCNs8enwTSZBiwSd zJgrFRnnOEUz3BhiAX0XwWWNZeMPnBkWHvZEUpgHA8vWRvykRY9JLk865JohfOiI frID2TEIGrWjKbMmp2nuxnAqtR6Rp2uiiVX6qiXGQn+pXjWjOyTB0Lm64rOPY9ZF o8HyqhUqT8whraNXZZtg33fatz3PiFVTDpGaV2lBYjBu0JhuiH1IAYTud0dDub5D v3u1YXzW8gqoUjTnmnHWkzmXnaG8hlMbxt3g6kOjNiPj+Thb1R8Q==
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=aSuH1/uTq2A829KkXT8jfzadRmcL4KmPPNH5iNl07dY=; b=Ehgg10RP XWj0rlqMFxtgkFKeLbuhYmsH1KOy5C/VsBHcaLm147Se3Tv8yNwg5iXq1Av4TJkv zO8o8C6PphwaTc/nlkG+5R49YhbHkObTcnuevwbAfCMhEyldjvrQl3vTSWNhwe0n JN5dibKREEisRwg6OCEv5/wj5cWUMZemCZNKcCNTWE4sRehyd3xozj/D3XhYda/4 pEGk/05Y/+E1HOeg7q8QkkZMvKtnq5EHtY9vK4mVNAov3kZ79XeAn9/gSNeaeivF I7jPEqX0rq8OGT4BOUKwlrvKXq5K0FKO+S0d9+xL6zwmEwuUfhoBxQK8JzeQMlD2 tT528K2X1BrWaA==
X-ME-Sender: <xms:wIDuWAlJmdXLUPmps4PWoFw8cqeuCvFFvFKpTwQaLnLu58jSn8RdZw>
X-Sasl-enc: o0u3PNllqODVO8VF5ta9doJwwoWPNJOFeRoFCqqKaJH/ 1492025535
Received: from sjc-alcoop-8817.cisco.com (unknown [128.107.241.182]) by mail.messagingengine.com (Postfix) with ESMTPA id 4F45824722; Wed, 12 Apr 2017 15:32:14 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <148834537055.29494.17692224713818414298.idtracker@ietfa.amsl.com>
Date: Wed, 12 Apr 2017 15:32:12 -0400
Cc: gen-art@ietf.org, draft-ietf-6man-rfc2460bis.all@ietf.org, IPv6 List <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5A651777-8781-47E8-ACAB-FFC72E0BE0D5@cooperw.in>
References: <148834537055.29494.17692224713818414298.idtracker@ietfa.amsl.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/XGw7JqAEWG3pTYHA9b3HyJjtDok>
Subject: Re: [Gen-art] Review of draft-ietf-6man-rfc2460bis-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Apr 2017 19:32:21 -0000

Peter, thank you for your review! I have asked the authors/WG to =
consider your suggestions in my ballot.

Alissa

> On Mar 1, 2017, at 12:16 AM, Peter Yee <peter@akayla.com> wrote:
>=20
> Reviewer: Peter Yee
> Review result: Ready with Nits
>=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-6man-rfc2460bis-08
> Reviewer: Peter Yee
> Review Date: 2017-02-28
> IETF LC End Date: 2017-03-01
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: Ready with nits.  This Internet-Draft is an update to RFC
> 2460, the specification for IPv6.  See the following note.
>=20
> Note that I read this document in the context that it is an update of
> RFC 2460, primarily for the purpose of cleaning up minor items (things
> that to moved to other documents, for example) and addressing errata.=20=

> I did not do a top-to-bottom review of the document as though it were
> a wholly new work.
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:=20
>=20
> General:
>=20
> For RFCs named outside of references (i.e., those that aren't found in
> square brackets), separate "RFC" from the following numbers with a
> space.  This is especially prevalent in Appendix B.
>=20
>> =46rom the mailing list discussion back in 2015, I can't determine if =
an
> actual decision was taken as to whether RFC 2119 recommended/expected
> language ought to be used in this document.  The discussion mentioned
> leaving the topic for IETF LC, but I can't even tell if there was
> consensus to do that.  This document does not use RFC 2119 language
> primarily because it is minor update to RFC 2460, which itself did not
> use RFC 2119 language.  There was a healthy debate on the mailing list
> and I feel it came down mostly on the side of using RFC 2119, but
> again no consensus was obvious, just a preponderance of opinions.  The
> thread starts here:
> https://www.ietf.org/mail-archive/web/ipv6/current/msg23284.html
>=20
> Change all uses of "en-route" to "en route".  Usage is mixed in the
> document, but en-route is never used before a noun and as a borrowed
> word from French would arguably not even be hyphenated had it appeared
> before a noun.  We won't even get into italicizing it. ;-)
>=20
> Change all uses of "behaviour" to "behavior".  Although both British
> and American English are permissible, it seems preferable that only
> form be used in any particular document.  Given so many other
> Americanized spellings in the document, I'm recommending going with
> American English in this case.
>=20
> Specific:
>=20
> Page 20, 5th bullet item, 2nd paragraph, 2nd sentence: delete "an"
> before "overlapping".
>=20
> Page 22, Section 4.8, 1st paragraph, append a comma after "because".
>=20
> Page 23, 1st partial paragraph, 1st full sentence: insert "be" before
> "a".
>=20
> Page 23, 1st full paragraph, 2nd sentence: insert "be" before "a".
>=20
> Page 23, 2nd full paragraph: consider changing "need to" to "must".=20
> (Ignoring any decision taken on RFC 2119 usage.)  I don't believe the
> "need to" at the top of this page needs to(!) change as it describing
> what designers need to do, not placing a restriction on a protocol
> element.
>=20
> Page 23, Header Specific Data definition: change the comma to a
> period.
>=20
> Page 26, 2nd bullet item, 1st sentence: delete the comma after
> "node".
>=20
> Page 26, 3rd bullet item, 2nd sentence: change "use" to "Use" in the
> title of RFC 6936.
>=20
> Page 29, Section 12.1, [I-D.ietf-6man-rfc4291bis] reference: update
> -06 to -07 to reflect the current version of that draft.
>=20
> Page 34, Appendix B title: change to "Changes since RFC 2460".
>=20
> Page 35, 1st 07) item: change "IPSEC" to "IPsec".
>=20
> Page 39, 01) item: delete an extraneous space before "and".
>=20


From nobody Wed Apr 12 22:28:22 2017
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B70B11293E0 for <gen-art@ietfa.amsl.com>; Wed, 12 Apr 2017 22:28:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xzWiLEg3-9yE for <gen-art@ietfa.amsl.com>; Wed, 12 Apr 2017 22:28:19 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06DCE1267BB for <gen-art@ietf.org>; Wed, 12 Apr 2017 22:28:18 -0700 (PDT)
X-AuditID: c618062d-767ff700000029b8-52-58ef1e9d8697
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by  (Symantec Mail Security) with SMTP id 74.62.10680.D9E1FE85; Thu, 13 Apr 2017 08:45:51 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0339.000; Thu, 13 Apr 2017 01:28:15 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: "draft-mm-wg-effect-encrypt.all@tools.ietf.org" <draft-mm-wg-effect-encrypt.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Telechat Call review of draft-mm-wg-effect-encrypt-10
Thread-Index: AQHStBa/di/vr07Fl0Ce2SOChSKPAA==
Date: Thu, 13 Apr 2017 05:28:14 +0000
Message-ID: <7AB1B56E-7786-40C3-9951-455A687787D3@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/f.20.0.170309
x-originating-ip: [147.117.188.12]
Content-Type: multipart/alternative; boundary="_000_7AB1B56E778640C39951455A687787D3ericssoncom_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJLMWRmVeSWpSXmKPExsUyuXRPgu58ufcRBp3L5C2+7EuyuPrqM4sD k8eSJT+ZPL5c/swWwBTFZZOSmpNZllqkb5fAlXHvxy62guaAivYvz9gaGJ/5djFyckgImEhs PXqGGcQWEtjAKLGpLaaLkQvIXs4ocej7byaQBJuAhcT2389ZQRIiAn2MEg37WllAEsICbhLd rbPZuxg5gBLeEhOmSYKERQT0JE7tXQJWwiKgKrHj9xWwBbwC9hL3zn9hBbEZBcQkvp9aAzaf WUBc4taT+UwQBwlILNlznhnCFpV4+fgfWL0o0MyZO/8yQsSVJOa8vsYM0Zss8bxtAivEfEGJ kzOfsExgFJqFZOwsJGWzkJTNArqaWUBTYv0ufYgSRYkp3Q/ZIWwNidY5c6Fsa4kvc5qZkdUs YORYxchRWlyQk5tuZLCJERghxyTYdHcw3p/ueYhRgINRiYf3gdG7CCHWxLLiytxDjBIczEoi vLN/AoV4UxIrq1KL8uOLSnNSiw8xSnOwKInzTjh/IUJIID2xJDU7NbUgtQgmy8TBKdXAmLxO 8JWwQuZlv+lR2XKnb/N7sn79szRu5QOxlLd11bmPO3TNfXfkdIXb5Rra7l4+eeY0ARc5WetX ksv9js3mMDeRiHmok7fkzIXbUX+Xrm83vaR+6GrkxQubJlcmJDHXrtaIn/8pcO3WOMOW62fq vqQcfdEjxdKaGvHSyqhjf8rtLYXMTBUzlViKMxINtZiLihMBlnBj7YwCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/x6P7LXJebpbEs1xODVLTQDX4vJQ>
Subject: [Gen-art] Gen-ART Telechat Call review of draft-mm-wg-effect-encrypt-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 05:28:21 -0000

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

SSBhbSB0aGUgYXNzaWduZWQgR2VuLUFSVCByZXZpZXdlciBmb3IgdGhpcyBkcmFmdC4gVGhlIEdl
bmVyYWwgQXJlYSBSZXZpZXcgVGVhbSAoR2VuLUFSVCkgcmV2aWV3cyBhbGwgSUVURiBkb2N1bWVu
dHMgYmVpbmcgcHJvY2Vzc2VkIGJ5IHRoZSBJRVNHIGZvciB0aGUgSUVURiBDaGFpci4gUGxlYXNl
IHdhaXQgZm9yIGRpcmVjdGlvbiBmcm9tIHlvdXIgZG9jdW1lbnQgc2hlcGhlcmQgb3IgQUQgYmVm
b3JlIHBvc3RpbmcgYSBuZXcgdmVyc2lvbiBvZiB0aGUgZHJhZnQuDQoNCkZvciBtb3JlIGluZm9y
bWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQgPGh0dHA6Ly93aWtpLnRvb2xzLmlldGYub3Jn
L2FyZWEvZ2VuL3RyYWMvd2lraS9HZW5BcnRmYXE+Lg0KDQpEb2N1bWVudDogZHJhZnQtbW0td2ct
ZWZmZWN0LWVuY3J5cHQtMTANClJldmlld2VyOiBNZXJhbCBTaGlyYXppcG91cg0KUmV2aWV3IERh
dGU6IDIwMTctMDQtMTINCklFVEYgTEMgRW5kIERhdGU6IDIwMTctMDMtMTMNCklFU0cgVGVsZWNo
YXQgZGF0ZTogMjAxNy0wNC0xMw0KDQpTdW1tYXJ5OiBUaGlzIGRyYWZ0IGlzIHJlYWR5IHRvIGJl
IHB1Ymxpc2hlZCBhcyBJbmZvcm1hdGlvbmFsIFJGQyBidXQgSSBoYXZlIGNvbWUgY29tbWVudHMu
DQoNCk1ham9yIGlzc3VlczoNCk1pbm9yIGlzc3VlczoNCk5pdHMvZWRpdG9yaWFsIGNvbW1lbnRz
Og0KLVtQYWdlIDVdLCBpdCB3b3VsZCBiZSBnb29kIHRvIGdpdmUgYSByZWZlcmVuY2UgYWZ0ZXIg
4oCcRm9sbG93aW5nIHRoZSBTbm93ZGVuIHJldmVsYXRpb25z4oCdLg0KLVtQYWdlIDZdLCDigJx0
aGUgbmV3IG5ldHdvcms/c+KAneKAlC0+4oCddGhlIG5ldyBuZXR3b3Jr4oCZcyDigJwNCi1bUGFn
ZSA3XSwg4oCcZm9yIHRvZGF5P3PigJ0tLS0+Zm9yIHRvZGF54oCZc+KAnQ0KLVtQYWdlIDldLCDi
gJxwZXJ2YXNzaXZl4oCdLS0tPuKAnXBlcnZlcnNpdmXigJ0NCi1bUGFnZSAxMF0sIOKAnHByb2l2
aWRlcnPigJ0tLS0+4oCccHJvdmlkZXJz4oCdDQotU2VjdGlvbiAyLCBzb21lIHVzZSBjYXNlcyBp
biBzdWJzZWN0aW9ucyBvZiBzZWN0aW9uIDIgcmVmZXIgdG8gbW9iaWxlIG5ldHdvcmsgc2NlbmFy
aW8uIEFyZSB0aGV5IG9ubHkgYXBwbGljYWJsZSBpbiBtb2JpbGUgbmV0d29ya3M/IGUuZy4gSFRU
UCByZWRpcmVjdC4NCi1TZWN0aW9uIDIuNi4yIHNob3VsZCBtYXliZSBiZSByZW5hbWVkIHRvIOKA
nHplcm8gcmF0aW5n4oCdLg0KLVtQYWdlIDE4XSwg4oCcYWNoZWl2ZeKAnS0tLT7igJ1hY2hpZXZl
4oCdDQoNCi1nZW5lcmFsOg0KLT4gdGV4dCB1c2VzIOKAnG1pZGRsZSBib3jigJ0gYW5kIOKAnG1p
ZGRsZWJveOKAnS4gUGxlYXNlIHVzZSBtaWRkbGVib3guDQotPnBsZWFzZSBzcGVsbCBvdXQgYWNy
b255bXMgYXQgZmlyc3QgdXNlDQoNCkJlc3QgUmVnYXJkcywNCk1lcmFsDQotLS0NCk1lcmFsIFNo
aXJhemlwb3VyDQpFcmljc3NvbiBSZXNlYXJjaA0Kd3d3LmVyaWNzc29uLmNvbQ0KDQoNCg==

--_000_7AB1B56E778640C39951455A687787D3ericssoncom_
Content-Type: text/html; charset="utf-8"
Content-ID: <323372DCB152A0449449723649EB1D98@ericsson.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iVGl0bGUiIGNvbnRlbnQ9IiI+DQo8bWV0YSBuYW1lPSJLZXl3b3JkcyIgY29udGVu
dD0iIj4NCjxtZXRhIG5hbWU9IkdlbmVyYXRvciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUg
KGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxlPjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8N
CkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0
IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJ
cGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8N
CnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsN
CgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWls
eTpDYWxpYnJpO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpzcGFu
LkVtYWlsU3R5bGUxNw0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJY29sb3I6d2luZG93dGV4dDt9DQpzcGFuLm1zb0lucw0KCXttc28t
c3R5bGUtdHlwZTpleHBvcnQtb25seTsNCgltc28tc3R5bGUtbmFtZToiIjsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lOw0KCWNvbG9yOnRlYWw7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0
eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6Q2FsaWJyaTt9DQpAcGFnZSBXb3Jk
U2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGlu
IDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9z
dHlsZT4NCjwvaGVhZD4NCjxib2R5IGJnY29sb3I9IndoaXRlIiBsYW5nPSJFTi1VUyIgbGluaz0i
IzA1NjNDMSIgdmxpbms9IiM5NTRGNzIiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5JIGFtIHRo
ZSBhc3NpZ25lZCBHZW4tQVJUIHJldmlld2VyIGZvciB0aGlzIGRyYWZ0LiBUaGUgR2VuZXJhbCBB
cmVhIFJldmlldyBUZWFtIChHZW4tQVJUKSByZXZpZXdzIGFsbCBJRVRGIGRvY3VtZW50cyBiZWlu
ZyBwcm9jZXNzZWQgYnkgdGhlIElFU0cgZm9yIHRoZSBJRVRGIENoYWlyLiBQbGVhc2Ugd2FpdCBm
b3IgZGlyZWN0aW9uIGZyb20geW91ciBkb2N1bWVudA0KIHNoZXBoZXJkIG9yIEFEIGJlZm9yZSBw
b3N0aW5nIGEgbmV3IHZlcnNpb24gb2YgdGhlIGRyYWZ0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdCI+Rm9yIG1vcmUgaW5mb3JtYXRpb24sIHBsZWFzZSBzZWUgdGhl
IEZBUSBhdCAmbHQ7aHR0cDovL3dpa2kudG9vbHMuaWV0Zi5vcmcvYXJlYS9nZW4vdHJhYy93aWtp
L0dlbkFydGZhcSZndDsuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
Ij5Eb2N1bWVudDogZHJhZnQtbW0td2ctZWZmZWN0LWVuY3J5cHQtMTA8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBw
dCI+UmV2aWV3ZXI6IE1lcmFsIFNoaXJhemlwb3VyPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPlJldmlldyBE
YXRlOiAyMDE3LTA0LTEyPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPklFVEYgTEMgRW5kIERhdGU6IDIwMTct
MDMtMTM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdCI+SUVTRyBUZWxlY2hhdCBkYXRlOiAyMDE3LTA0LTEzPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0Ij5TdW1tYXJ5OiBUaGlzIGRy
YWZ0IGlzIHJlYWR5IHRvIGJlIHB1Ymxpc2hlZCBhcyBJbmZvcm1hdGlvbmFsIFJGQyBidXQgSSBo
YXZlIGNvbWUgY29tbWVudHMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0Ij5NYWpvciBpc3N1ZXM6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPk1pbm9yIGlzc3Vlczo8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdCI+Tml0cy9lZGl0b3JpYWwgY29tbWVudHM6PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPi1b
UGFnZSA1XSwgaXQgd291bGQgYmUgZ29vZCB0byBnaXZlIGEgcmVmZXJlbmNlIGFmdGVyIOKAnEZv
bGxvd2luZyB0aGUgU25vd2RlbiByZXZlbGF0aW9uc+KAnS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+LVtQ
YWdlIDZdLCDigJx0aGUgbmV3IG5ldHdvcms/c+KAneKAlC0mZ3Q74oCddGhlIG5ldyBuZXR3b3Jr
4oCZcyDigJw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+LVtQYWdlIDddLCDigJxmb3IgdG9kYXk/c+KAnS0t
LSZndDtmb3IgdG9kYXnigJlz4oCdPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPi1bUGFnZSA5XSwg4oCccGVy
dmFzc2l2ZeKAnS0tLSZndDvigJ1wZXJ2ZXJzaXZl4oCdPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPi1bUGFn
ZSAxMF0sIOKAnHByb2l2aWRlcnPigJ0tLS0mZ3Q74oCccHJvdmlkZXJz4oCdPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQiPi1TZWN0aW9uIDIsIHNvbWUgdXNlIGNhc2VzIGluIHN1YnNlY3Rpb25zIG9mIHNlY3Rp
b24gMiByZWZlciB0byBtb2JpbGUgbmV0d29yayBzY2VuYXJpby4gQXJlIHRoZXkgb25seSBhcHBs
aWNhYmxlIGluIG1vYmlsZSBuZXR3b3Jrcz8gZS5nLiBIVFRQIHJlZGlyZWN0LjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0Ij4tU2VjdGlvbiAyLjYuMiBzaG91bGQgbWF5YmUgYmUgcmVuYW1lZCB0byDigJx6ZXJv
IHJhdGluZ+KAnS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+LVtQYWdlIDE4XSwg4oCcYWNoZWl2ZeKAnS0t
LSZndDvigJ1hY2hpZXZl4oCdPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEu
MHB0Ij4tZ2VuZXJhbDo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+LSZndDsgdGV4dCB1c2VzIOKAnG1pZGRs
ZSBib3jigJ0gYW5kIOKAnG1pZGRsZWJveOKAnS4gUGxlYXNlIHVzZSBtaWRkbGVib3guPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQiPi0mZ3Q7cGxlYXNlIHNwZWxsIG91dCBhY3JvbnltcyBhdCBmaXJzdCB1c2U8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPkJlc3QgUmVnYXJkcyw8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdCI+TWVyYWw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+LS0tPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQiPk1lcmFsIFNoaXJhemlwb3VyPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPkVyaWNzc29uIFJlc2Vh
cmNoPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQiPnd3dy5lcmljc3Nvbi5jb208bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdCI+
PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_7AB1B56E778640C39951455A687787D3ericssoncom_--


From nobody Thu Apr 13 13:11:13 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B79EF129A9B for <gen-art@ietf.org>; Thu, 13 Apr 2017 13:11:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-to: mahoney@nostrum.com
Message-ID: <149211427164.15800.1411481249744713448.idtracker@ietfa.amsl.com>
Date: Thu, 13 Apr 2017 13:11:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/nkGByUvB9uiD1HI_ptw5bsI3DRw>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 20:11:12 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-04-27

Reviewer               Type      LC end     Draft
Lucy Yong              Telechat  None       draft-ietf-isis-l2bundles-04

Last calls:

Reviewer               Type      LC end     Draft
Stewart Bryant         Last Call 2017-04-21 draft-ietf-grow-large-communities-usage-05
Elwyn Davies           Last Call 2017-04-21 draft-ietf-core-links-json-07
Vijay Gurbani          Last Call 2017-04-20 draft-ietf-avtcore-rfc5285-bis-09
Joel Halpern           Last Call 2017-04-28 draft-ietf-v6ops-unique-ipv6-prefix-per-host-02

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Robert Sparks
  Dale Worley
  Peter Yee
  Lucy Yong
  Jari Arkko
  Stewart Bryant
  Brian Carpenter
  Elwyn Davies
  Ralph Droms
  Francis Dupont

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Thu Apr 13 16:02:11 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3135812EAD1; Thu, 13 Apr 2017 16:02:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: v6ops@ietf.org, draft-ietf-v6ops-unique-ipv6-prefix-per-host.all@ietf.org,  ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149212453015.27548.13210718340210615403@ietfa.amsl.com>
Date: Thu, 13 Apr 2017 16:02:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/gPjYlBO7UqAiyMf53LIA8mcOzb0>
Subject: [Gen-art] Genart last call review of draft-ietf-v6ops-unique-ipv6-prefix-per-host-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 23:02:10 -0000

Reviewer: Joel Halpern
Review result: Ready with Issues

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

For more information, please see the FAQ at

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

Document: draft-ietf-v6ops-unique-ipv6-prefix-per-host-??
Reviewer: Joel Halpern
Review Date: 2017-04-13
IETF LC End Date: None
IESG Telechat date: Not scheduled for a telechat

Summary: This document is almsot ready for publication as an RFC.

Major issues: N/A

Minor issues:
    The proposed status seems questionable.  We as a community are not
recommending that operators assign unique prefixes to hosts.  This
document is saying "if you want to do that, here is a way, using
existing tools, to make that work."  The document also recommends
specific setting of other flags (the O flag in the RA, for example)
that are not closely coupled to the particular topic.  This looks like
an ordinary Informational RFC.  I would have no concern with this
being published with that label.

Nits/editorial comments: 
    As per the nits checker, the document uses RFC 2119 terminology. 
The usage seems quite appropriate.  The document should therefore cite
RFC 2119.
    Also, as per the nits checker, the document references RFC 6106. 
It should reference RFC 8106.



From nobody Thu Apr 13 16:59:06 2017
Return-Path: <oritl@microsoft.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54E0D1276AF; Thu, 13 Apr 2017 16:59:05 -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 h2Eb-AFn5fGu; Thu, 13 Apr 2017 16:59:02 -0700 (PDT)
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (mail-by2nam03on0102.outbound.protection.outlook.com [104.47.42.102]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC029126579; Thu, 13 Apr 2017 16:59:02 -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=G2ZsdUrm33rZMSK2i+iYZQhZAnVsP7ePcPIBhV34mCw=; b=UVA3dY/vICtzuhNp7qC1dmvi+l2+6ktrSMorrnCHXETEqLuN+ddlTuudjDjF4yTMkaOWgyRkLjxPOrpjouiVdAhCkD/nWpzADS6eeICZVHQpFRRaNzr+z62g1r/o2o40nNonLSfW7wNZnS0Uiqa9J2Dvj7CHklBetdGcJUz2Zf4=
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) by CY1PR0301MB2121.namprd03.prod.outlook.com (10.164.2.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.10; Thu, 13 Apr 2017 23:59:01 +0000
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) by CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) with mapi id 15.01.1034.011; Thu, 13 Apr 2017 23:59:00 +0000
From: Orit Levin <oritl@microsoft.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-isis-mi-bis.all@tools.ietf.org" <draft-ietf-isis-mi-bis.all@tools.ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJABiHiqgAJGI1kA=
Date: Thu, 13 Apr 2017 23:59:00 +0000
Message-ID: <CY1PR0301MB21222E388C390E119F583D4DAD020@CY1PR0301MB2122.namprd03.prod.outlook.com>
References: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com> <dc04ef63da5242d6a57386cb9d07b005@XCH-ALN-001.cisco.com>
In-Reply-To: <dc04ef63da5242d6a57386cb9d07b005@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [124.74.42.142]
x-microsoft-exchange-diagnostics: 1; CY1PR0301MB2121; 7:Acny2Gpm73Rjtjh4y1fdgJKq6HqKCx25oVZrc/WT49AAwRi8CO+aZCkv6/d+5MfEtLPIlXll6VedD303PBxRkZhh/3sJJ3uUfKFc42GkWbULUKgSHirXMx20R2YUEsiRa0uG8fWkbcN6A9YgnB5gZfa6R98xqriOdUFFDA8vsUpahvIK1XNeLb4rCOKiA9bkAA8PZmY2nAFzUSVrxVj6Gv4w/zGlMmDRy+ZxRZPEi7kQbMprxqrozf74K9QlQiKkQ4T+y0e5ojE+b7wv/p0I6Fmv6BPR25fN9TXXM7XaLnc8GTTQoG2yBWvdtGzO0ZfH+Sv9uvkfpV3WKIzN/4P2NFMMfts+5dY38VI2FlczZiE=
x-ms-office365-filtering-correlation-id: b06ab864-2084-4960-c2eb-08d482c90e7e
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081)(201702281549075); SRVR:CY1PR0301MB2121; 
x-microsoft-antispam-prvs: <CY1PR0301MB21215A4F16D7A6959936887AAD020@CY1PR0301MB2121.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705)(131327999870524)(788757137089)(95692535739014); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(20161123560025)(20161123555025)(6072148); SRVR:CY1PR0301MB2121; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB2121; 
x-forefront-prvs: 02760F0D1C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39400400002)(39850400002)(39860400002)(39840400002)(39450400003)(377454003)(13464003)(129404003)(85664002)(377424004)(8676002)(9686003)(10090500001)(81166006)(6246003)(5005710100001)(8936002)(53546009)(25786009)(122556002)(99286003)(74316002)(5660300001)(55016002)(305945005)(7736002)(86362001)(229853002)(4326008)(7696004)(2900100001)(8990500004)(6306002)(54906002)(86612001)(3846002)(3660700001)(50986999)(38730400002)(53936002)(77096006)(102836003)(33656002)(10290500002)(3280700002)(54356999)(76176999)(6506006)(66066001)(6436002)(189998001)(230783001)(2906002)(2950100002)(2501003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB2121; H:CY1PR0301MB2122.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: 13 Apr 2017 23:59:00.7589 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB2121
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/_yOjBPTVBMx3IW0sLiJw2EI5JJw>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Apr 2017 23:59:05 -0000

Hi Les,
Sorry for the delay in response.
Your feedback was very helpful. Below is a refresh of my comments. I tried =
to make them more pointed and some are new.

Summary: This draft is "ready with issues" for publication.

General:
1) For implementers who are familiar with the history and the intent of thi=
s extension, the information in the draft is probably sufficient to serve a=
s a check list for implementing a multi-instance IS-IS router. For all othe=
r readers, the document doesn't contain an overview of the new mode of oper=
ation, i.e. where the instances are not a configuration and an internal imp=
lementation choice only, but are exposed through the protocol to achieve th=
e stated objective. Lacking such an overview, the reader needs to reverse-e=
ngineer the logic behind the documented guidance.
2) The draft talks about "extensions" in plural. Based on a single extensio=
n on the wire and the overall goal of the new mechanism, I would say that i=
t is a single extension only.  How many protocol extensions does this docum=
ent define? If they can be clearly separated, then it needs to be clarified=
 throughout the document. Otherwise, the language throughout the document n=
eeds to be changed from "extensions" to "the extention".
3) Editorial: Please, compare (Diff) the current draft with the published R=
FC 6822. You will find that various RFC Editor corrections got lost in this=
 bis document. Some repeating examples of the lost corrections are "instanc=
e-specific", " topology (or topologies)" and "Type-Length-Value".

My comments below are a result of a reverse-engineering exercise. Please, c=
onsider incorporating the suggested clarifications to improve the document =
readability. I might have misunderstood some of the parts; in such cases, p=
lease, provide an alternative text.

Abstract
1) Add clarification: "This document is not backwards compatible with RFC 6=
822."
2) Par. 2, replace the first two sentences with: "Configuration of multiple=
 protocol instances within a router allow the isolation of resources associ=
ated with each instance. This document introduces a new mode of operation w=
here the protocol instances are not a matter of configuration only, but are=
 exposed through the new protocol extension to achieve the objective stated=
 above."
3) Par. 3 uses both present and future time. Does it mean before and after =
the extension? Please, clarify by spelling out the intent and/or changing t=
he grammar.

1. Introduction
1) Move par. 3 to become the opening paragraph (i.e., par.1 ) in the Introd=
uction to improve its logical flow (also related to the next comment).
2) Par 4, sentence #2 says "This document defines an extension to IS-IS to =
allow non-zero instances...". My assumption is that the intent of this draf=
t is to define a single extension, which will improve the routing operation=
s in a number of ways. If this is the case, the quote needs to be replaced =
with "The MI-IS-IS extension, defined in this document, also allows so-call=
ed "non-zero instances"..." .
3) Par 4, sentences #4 and #5 are not sufficient to describe the new mode o=
f operation introduced by this extension. Below is my attempt to describe i=
t. Please, correct, if I got it wrong.
"IS-IS router instances that support this extension are preconfigured with =
unique non-zero Instance Identifiers (IIDs) giving them the name "non-zero =
instances". In addition, MI RTRs MAY (or SHOULD ?) implement the legacy (or=
 so-called "standard") instance of the IS-IS router for backwards compatibi=
lity with legacy IS-IS routers. IID #0 is only used by MI-RTRs to convey in=
formation associated with such standard interface if implemented. See secti=
on 2.6 Interoperability Considerations for more details."
4) Par 4, replace the two "may" with "can" to clarify the intent.
5) Par 5, change "defined" to "described" since the examples are not normat=
ive.
5) Par 5, add references to the (sub)sections containing the description of=
 the two methods.
6) Par 7, move the last paragraph before listing the two examples and adjus=
t the text accordingly, to improve the logical flow.
7) In the end of the Introduction add a reference: "This RFC is not backwar=
ds compatible with RFC 6822. Differences between this document and RFC 6822=
 are described in Annex A." ... so that others don't skip it by mistake as =
I did earlier...

2. Elements of Procedure
1) It seems that this section (informational) and its subsections (normativ=
e) use present and future times and, at times,  the normative language inco=
nsistently both within the sections and among the sub-sections. Please, exp=
lain the reasons and improve consistency accordingly.=20
2) Par 1, clarify the scope by adding "within a routing domain" at the end =
of the first sentence.
3) Par 1, after the first sentence add a new sentence alone the following l=
ines "Routers form adjacencies and exchange routing updates only if their I=
IDs correspond." This explains the basic premise of the whole mechanism.
4) Par 2, change "may" to "can" or "might" for consistency.

Section 2.1
1) Par 2, change "may" to "MAY".
2) Par 3, remove "supported by legacy systems" from the first sentence to a=
void confusion. My understanding is that IID #0 is reserved  for use by MI-=
RTRs that also implement the standard instance and advertise it in IIH usin=
g IID-TLV.
3) Par 3, change "except where noted" to "except as noted in section 2.6.2 =
(?)".  This is an excellent place to explain the logic behind this MUST NOT=
 statement or, at least, state the general circumstances where IID #0 is in=
cluded in IID-TLV.
4) Par 9 (4th after the picture), change "as described later" to " as descr=
ibed in section 2.6.2 (?)". =20
5) Par 13, change "recommended" to "RECOMMENDED".
6) Editorial: Par 13, change "particularf" to "particular".

Section 2.2
1) Add that MI-RTR MAY (or SHOULD) implement the standard instance as well =
and which packets are used to advertise it.
2) Rephrase "marks ... by including" to "MUST include" to use requirements =
language.

Section 2.3
Editorial: Replace "normal" with "usual".

Section 2.4.1=20
1) Par 1. Replace "IID #0" with "standard instance".
2) Par 1. Replace "instances other than IID #0" with "non-zero instances".
3) Par 2 second sentence. What does it mean "normal expectations"? Is this =
a network configuration requirement? Please, clarify in the text.

Section 2.4.2 Improve language consistency=20
1) Verbs are used inconsistently: some are used in present time, others in =
future time.=20

Section 2.5, replace "exists" with "MUST be performed".
Section 2.5.1, replace "only operates" with "MUST only be performed".
Section 2.5.2, replace "This requires" with "It is REQUIRED".
Section 2.5.2 third sentence, after "inconsistent" insert "due to their con=
figuration". (Please, correct me if I am wrong.)

Section 2.6.1=20
1) Editorial: Par 1, first sentence, replace "not to cause" to "to avoid".
2) Par 2, remove "(IID #0)".
3) Par 2, replace "non-zero IID" with "non-zero instance".
4) Par 5 NOTE, replace "IID #0" with "standard instance".

Section 2.6.2=20
Replace all four appearances of "IID #0" with "standard instance".=20

Section 3.1
Replace the two "MAY" to "can".=20

7 Security Considerations
Discuss possible additional security considerations (or the lack of them) r=
elated to the exposure of "instances" on the wire.
Reason: Beyond the normal IETF procedure, this is especially important beca=
use "multiple instances allow isolation of resources..." Can this isolation=
, if observed or interfered on the wire, be damaging beyond the previous "s=
tandard instance" situation.

Thanks,
Orit.
-----Original Message-----
From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]=20
Sent: Saturday, April 8, 2017 4:23 PM
To: Orit Levin <oritl@microsoft.com>; gen-art@ietf.org
Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02

Orit -

Thanx for the review.
Responses inline.

> -----Original Message-----
> From: Orit Levin [mailto:oritl@microsoft.com]
> Sent: Thursday, April 06, 2017 8:27 PM
> To: gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=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
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-ietf-isis-mi-bis-02
> Reviewer: Orit Levin
> Review Date: 2017-04-06
> IETF LC End Date: 2017-04-07
> IESG Telechat date: 2017-04-13
>=20
> Summary: This draft is "ready with issues" for publication.
>=20
> Major issues: None.
>=20
> Minor issues:
>=20
> 1. Add text explaining the reason (or reasons) for replacing the=20
> original RFC
> 6822 from 2012.
> Reason: It is a "bis" draft and there is no mention about it in the text.

[Les:] Note that the latest revision of the draft correctly identifies the =
draft as obsoleting RFC 6822. Previous versions had incorrectly identified =
this as an update to RFC 6822.
This is then the new Standard for the IS-IS MI support.

There are two classes of future readers of this document:

a)Readers who are unfamiliar with RFC 6822. For them what changed between R=
FC 6822 and this document is irrelevant.=20

b)Readers who are familiar with RFC 6822. For them it is useful to know wha=
t changed - which is described in Appendix A.

In order not to distract readers of type "a" - as well as to provide an "un=
interrupted" description of the normative behavior I believe placement of t=
he change description in an Appendix improves the readability of the docume=
nt.

Does this make sense to you?

> 2. In Abstract, state clearly that this standard introduces the=20
> support for instances vs. other already existing concepts also listed=20
> in the Abstract (i.e., circuits, adjacencies,  topologies, etc.).

[Les:] The Abstract currently says:

"This draft describes a mechanism that allows a single router to share
   one or more circuits among multiple Intermediate System To
   Intermediate System (IS-IS) routing protocol instances."

Previous to this extension, a router could have multiple instances of the I=
S-IS protocol, but multiple instance could not be run over the same interfa=
ce.=20
So we are not introducing "instances", but we are introducing the ability t=
o enable multiple instances on the same interface.

> Reason: The wording is not clear about what is the new feature vs.=20
> what are the new benefits vs. what was the original baseline

>3. Throughout the
> document, use "standard instance" instead of "IID =3D 0" or "IID #0".
> Reason: Expressions "standard instance", "IID =3D 0" and "IID #0" are=20
>used  interchangeably throughout the document. It seems that they all=20
>refer to the  same thing - the implementation of the original protocol=20
>without the concept  of instances. Please, correct me if I am wrong.

[Les:]  I don't think this is possible without seriously compromising the d=
ocument. For example:

Section 2.1

" IID #0 is reserved for the standard instance supported by legacy
   systems. "

Changing this to  " Standard instance is reserved for the standard instance=
 ..."

Is clearly nonsensical.

Later in Section 2.1

"When the IID =3D 0, the list of supported ITIDs MUST NOT be present."

What is being discussed here is what is the correct behavior when an MI-cap=
able router sends a PDU associated IID #0 and includes the new IID TLV.=20
Replacing this with "When the standard instance..." loses the important poi=
nt that the value of the IID in the IID TLV in this case is "0".

Hope this helps clarify things.

> 4. In section 2 par 3, change "support" and "operates" to "MUST=20
> support" to use requirements language.

[Les:] I am on the fence as regards this change. Section 2 is an introducti=
on to the following sub-sections - which define the normative behavior. But=
 the introduction itself is not defining normative behavior - it is providi=
ng a context in which the protocol extensions defined in the following sub-=
sections can be understood.=20

I am more inclined to change the "MAY" used later in the same paragraph you=
 mention to "may" so it is consistent with the rest of this section.

???


> 5. In section 2 par 2, change "may" to either "can" or "MAY" to=20
> clarify the intent.

[Les:] Did you mean Section 2.1 para 2?
If so I agree to the change.

> 6. In section 2.1 par 3, clarify whether IID #0 is ever being used on the=
 wire.

[Les:] There are numerous places in the document where the legal use of IID=
  #0 is discussed. I do not understand how a reader would conclude that IID=
 #0 is never sent on the wire.

> Explain the concept of the "standard interface" (see previous comment)

[Les:] There is no mention of "standard interface" - did you mean "standard=
 instance"?

If so, Section 1 paragraph 4 states:

"Legacy routers support the standard
   or zero instance of the protocol."

   Les


From nobody Thu Apr 13 20:05:49 2017
Return-Path: <ginsberg@cisco.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82362129463; Thu, 13 Apr 2017 20:05:40 -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 KlZFEpQE6ZIT; Thu, 13 Apr 2017 20:05:37 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB00C12947D; Thu, 13 Apr 2017 20:05:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17076; q=dns/txt; s=iport; t=1492139136; x=1493348736; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=1lU4EDQ6UQmwqTjczhBtUvLhEoV34v5gBd5YdsnzV8w=; b=XnU7xhQLQ9G4A9gQ69wfuFGjHqTAtqzC2izwZltyvPDXVriHzvxB4exE TtKqM9lCgKvV2gkYMSQOfSDmX/dE8U/EtpOwANC3bXttgL5obVXITK0gx Lg5gW4ZT5Dz/YZ44filB03EurCH5OQHxKkBoXpq/2GX8ywlVLRwFEbAkP E=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AWAQDrO/BY/4gNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgygrYYELB410kVqVWIIPLIV4AoN4PxgBAgEBAQEBAQFrKIUVAQE?= =?us-ascii?q?BAQIBOj8FBwQCAQgRAwEBAR8JBzIUCQgBAQQBDQUIigYIDqtYixEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEdhlGBXYMXhB2GHgEEiS6GRYY7hmQBhwGDK4gsgghVhFm?= =?us-ascii?q?KF4hnix0BHziBBVsVQYRbHIFjdQGILYENAQEB?=
X-IronPort-AV: E=Sophos;i="5.37,195,1488844800"; d="scan'208";a="411575674"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 14 Apr 2017 03:05:35 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id v3E35ZFP028735 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 14 Apr 2017 03:05:35 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 13 Apr 2017 22:05:34 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1210.000; Thu, 13 Apr 2017 22:05:34 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Orit Levin <oritl@microsoft.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-isis-mi-bis.all@tools.ietf.org" <draft-ietf-isis-mi-bis.all@tools.ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJABiHiqgAJGI1kAAbW6QgA==
Date: Fri, 14 Apr 2017 03:05:34 +0000
Message-ID: <1fa6af5d967d45d4b45d09afdb8fcc85@XCH-ALN-001.cisco.com>
References: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com> <dc04ef63da5242d6a57386cb9d07b005@XCH-ALN-001.cisco.com> <CY1PR0301MB21222E388C390E119F583D4DAD020@CY1PR0301MB2122.namprd03.prod.outlook.com>
In-Reply-To: <CY1PR0301MB21222E388C390E119F583D4DAD020@CY1PR0301MB2122.namprd03.prod.outlook.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.32.152.12]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/vSCKZgWSblo_aFdnk-cn9RZcX6k>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Apr 2017 03:05:41 -0000

Orit -

It is obvious you spent a lot of time on this review - and I do want to be =
respectful of that.
However, there is a larger context here which I think has a significant bea=
ring on handling of many of your comments.

RFC 6822 was published over 4 years ago. Multiple interoperable implementat=
ions exist. The bis version makes some modest - but significant changes. Ho=
wever, we deliberately strived to keep the bis version as consistent as pos=
sible with RFC 6822 in order to minimize the possibility that aspects of th=
e specification which had NOT been changed would be reinterpreted simply be=
cause the wording had changed. So, in cases where you suggest (below) that =
a different wording is desirable I am very reluctant to make such changes b=
ecause of the above concern.
If I do not indicate any response to a particular comment you can interpret=
 as meaning:

"Unnecessary changes relative to RFC 6822 are not desirable."

Inline.

> -----Original Message-----
> From: Orit Levin [mailto:oritl@microsoft.com]
> Sent: Thursday, April 13, 2017 4:59 PM
> To: Les Ginsberg (ginsberg); gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> Hi Les,
> Sorry for the delay in response.
> Your feedback was very helpful. Below is a refresh of my comments. I trie=
d
> to make them more pointed and some are new.
>=20
> Summary: This draft is "ready with issues" for publication.
>=20
> General:
> 1) For implementers who are familiar with the history and the intent of t=
his
> extension, the information in the draft is probably sufficient to serve a=
s a
> check list for implementing a multi-instance IS-IS router. For all other =
readers,
> the document doesn't contain an overview of the new mode of operation,
> i.e. where the instances are not a configuration and an internal
> implementation choice only, but are exposed through the protocol to
> achieve the stated objective. Lacking such an overview, the reader needs =
to
> reverse-engineer the logic behind the documented guidance.

[Les:] I am not sure I understand your concern. You seem to be suggesting t=
hat readers won't know when to use MI and when to simply create multiple no=
n-MI instances of the protocol.
The short answer to that is that it is not the purpose of this document to =
make that decision. We have provided some new functionality - it is up to t=
he user to decide when it is appropriate to use the new functionality and w=
hen it is not. We have provided some guidance in Sections 3 and 4 - but thi=
s is non-normative - as it should be.
But your use of "reverse-engineer" confuses me, so likely I do not understa=
nd your point.

As regards new vs old readers, the new version of the document provides as =
much (or as little) guidance as RFC 6822 - so I do not see why new readers =
would have any more issues than new readers of RFC 6822 had 4 years ago.


> 2) The draft talks about "extensions" in plural. Based on a single extens=
ion on
> the wire and the overall goal of the new mechanism, I would say that it i=
s a
> single extension only.  How many protocol extensions does this document
> define? If they can be clearly separated, then it needs to be clarified
> throughout the document. Otherwise, the language throughout the
> document needs to be changed from "extensions" to "the extention".

[Les:] There are multiple changes in protocol behavior described - hence th=
e term extensions is correct.

> 3) Editorial: Please, compare (Diff) the current draft with the published=
 RFC
> 6822. You will find that various RFC Editor corrections got lost in this =
bis
> document. Some repeating examples of the lost corrections are "instance-
> specific", " topology (or topologies)" and "Type-Length-Value".

[Les:] Noted - thanx.

> My comments below are a result of a reverse-engineering exercise. Please,
> consider incorporating the suggested clarifications to improve the docume=
nt
> readability. I might have misunderstood some of the parts; in such cases,
> please, provide an alternative text.
>=20
> Abstract
> 1) Add clarification: "This document is not backwards compatible with RFC
> 6822."

[Les:] This statement is made explicitly in the Appendix - and I believe th=
at is where it belongs for reasons I have previously stated.

> 2) Par. 2, replace the first two sentences with: "Configuration of multip=
le
> protocol instances within a router allow the isolation of resources assoc=
iated
> with each instance. This document introduces a new mode of operation
> where the protocol instances are not a matter of configuration only, but =
are
> exposed through the new protocol extension to achieve the objective state=
d
> above."
> 3) Par. 3 uses both present and future time. Does it mean before and afte=
r
> the extension? Please, clarify by spelling out the intent and/or changing=
 the
> grammar.
>=20
[Les:] The sentence will in any case be changed when the document becomes a=
n RFC - not worth discussing.

> 1. Introduction
> 1) Move par. 3 to become the opening paragraph (i.e., par.1 ) in the
> Introduction to improve its logical flow (also related to the next commen=
t).
> 2) Par 4, sentence #2 says "This document defines an extension to IS-IS t=
o
> allow non-zero instances...". My assumption is that the intent of this dr=
aft is
> to define a single extension, which will improve the routing operations i=
n a
> number of ways. If this is the case, the quote needs to be replaced with =
"The
> MI-IS-IS extension, defined in this document, also allows so-called "non-=
zero
> instances"..." .
> 3) Par 4, sentences #4 and #5 are not sufficient to describe the new mode=
 of
> operation introduced by this extension. Below is my attempt to describe i=
t.
> Please, correct, if I got it wrong.
> "IS-IS router instances that support this extension are preconfigured wit=
h
> unique non-zero Instance Identifiers (IIDs) giving them the name "non-zer=
o
> instances". In addition, MI RTRs MAY (or SHOULD ?) implement the legacy (=
or
> so-called "standard") instance of the IS-IS router for backwards compatib=
ility
> with legacy IS-IS routers. IID #0 is only used by MI-RTRs to convey
> information associated with such standard interface if implemented. See
> section 2.6 Interoperability Considerations for more details."
> 4) Par 4, replace the two "may" with "can" to clarify the intent.
> 5) Par 5, change "defined" to "described" since the examples are not
> normative.
> 5) Par 5, add references to the (sub)sections containing the description =
of
> the two methods.
> 6) Par 7, move the last paragraph before listing the two examples and adj=
ust
> the text accordingly, to improve the logical flow.
> 7) In the end of the Introduction add a reference: "This RFC is not backw=
ards
> compatible with RFC 6822. Differences between this document and RFC 6822
> are described in Annex A." ... so that others don't skip it by mistake as=
 I did
> earlier...
>=20
 [Les:] Reading of the Appendix is optional - the new version is usable wit=
hout any need to refer to RFC 6822 - and that is its primary purpose.

> 2. Elements of Procedure
> 1) It seems that this section (informational) and its subsections (normat=
ive)
> use present and future times and, at times,  the normative language
> inconsistently both within the sections and among the sub-sections. Pleas=
e,
> explain the reasons and improve consistency accordingly.
> 2) Par 1, clarify the scope by adding "within a routing domain" at the en=
d of
> the first sentence.
> 3) Par 1, after the first sentence add a new sentence alone the following=
 lines
> "Routers form adjacencies and exchange routing updates only if their IIDs
> correspond." This explains the basic premise of the whole mechanism.
> 4) Par 2, change "may" to "can" or "might" for consistency.
>=20
> Section 2.1
> 1) Par 2, change "may" to "MAY".
> 2) Par 3, remove "supported by legacy systems" from the first sentence to
> avoid confusion. My understanding is that IID #0 is reserved  for use by =
MI-
> RTRs that also implement the standard instance and advertise it in IIH us=
ing
> IID-TLV.
> 3) Par 3, change "except where noted" to "except as noted in section 2.6.=
2
> (?)".  This is an excellent place to explain the logic behind this MUST N=
OT
> statement or, at least, state the general circumstances where IID #0 is
> included in IID-TLV.
> 4) Par 9 (4th after the picture), change "as described later" to " as des=
cribed
> in section 2.6.2 (?)".
> 5) Par 13, change "recommended" to "RECOMMENDED".
> 6) Editorial: Par 13, change "particularf" to "particular".
>=20
[Les:] #6 - Agreed.

> Section 2.2
> 1) Add that MI-RTR MAY (or SHOULD) implement the standard instance as
> well and which packets are used to advertise it.
> 2) Rephrase "marks ... by including" to "MUST include" to use requirement=
s
> language.
>=20
> Section 2.3
> Editorial: Replace "normal" with "usual".
>=20
> Section 2.4.1
> 1) Par 1. Replace "IID #0" with "standard instance".
> 2) Par 1. Replace "instances other than IID #0" with "non-zero instances"=
.
> 3) Par 2 second sentence. What does it mean "normal expectations"? Is thi=
s a
> network configuration requirement? Please, clarify in the text.
>=20
> Section 2.4.2 Improve language consistency
> 1) Verbs are used inconsistently: some are used in present time, others i=
n
> future time.
>=20
> Section 2.5, replace "exists" with "MUST be performed".
> Section 2.5.1, replace "only operates" with "MUST only be performed".
> Section 2.5.2, replace "This requires" with "It is REQUIRED".
> Section 2.5.2 third sentence, after "inconsistent" insert "due to their
> configuration". (Please, correct me if I am wrong.)
>=20
> Section 2.6.1
> 1) Editorial: Par 1, first sentence, replace "not to cause" to "to avoid"=
.
> 2) Par 2, remove "(IID #0)".
> 3) Par 2, replace "non-zero IID" with "non-zero instance".
> 4) Par 5 NOTE, replace "IID #0" with "standard instance".
>=20
> Section 2.6.2
> Replace all four appearances of "IID #0" with "standard instance".
>=20
> Section 3.1
> Replace the two "MAY" to "can".
>=20
> 7 Security Considerations
> Discuss possible additional security considerations (or the lack of them)
> related to the exposure of "instances" on the wire.
> Reason: Beyond the normal IETF procedure, this is especially important
> because "multiple instances allow isolation of resources..." Can this iso=
lation,
> if observed or interfered on the wire, be damaging beyond the previous
> "standard instance" situation.
>=20

[Les:] There are no security concerns associated with the use of multiple i=
nstances.
Security reviews of the document have been satisfied w the current contents=
.

   Les

> Thanks,
> Orit.
> -----Original Message-----
> From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
> Sent: Saturday, April 8, 2017 4:23 PM
> To: Orit Levin <oritl@microsoft.com>; gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> Orit -
>=20
> Thanx for the review.
> Responses inline.
>=20
> > -----Original Message-----
> > From: Orit Levin [mailto:oritl@microsoft.com]
> > Sent: Thursday, April 06, 2017 8:27 PM
> > To: gen-art@ietf.org
> > Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> > Subject: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
> >
> > I am the assigned Gen-ART reviewer for this draft. The General Area
> > Review Team (Gen-ART) reviews all IETF documents being processed by
> > the IESG for the IETF Chair.  Please treat these comments just like
> > any other last call comments.
> >
> > For more information, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Document: draft-ietf-isis-mi-bis-02
> > Reviewer: Orit Levin
> > Review Date: 2017-04-06
> > IETF LC End Date: 2017-04-07
> > IESG Telechat date: 2017-04-13
> >
> > Summary: This draft is "ready with issues" for publication.
> >
> > Major issues: None.
> >
> > Minor issues:
> >
> > 1. Add text explaining the reason (or reasons) for replacing the
> > original RFC
> > 6822 from 2012.
> > Reason: It is a "bis" draft and there is no mention about it in the tex=
t.
>=20
> [Les:] Note that the latest revision of the draft correctly identifies th=
e draft as
> obsoleting RFC 6822. Previous versions had incorrectly identified this as=
 an
> update to RFC 6822.
> This is then the new Standard for the IS-IS MI support.
>=20
> There are two classes of future readers of this document:
>=20
> a)Readers who are unfamiliar with RFC 6822. For them what changed
> between RFC 6822 and this document is irrelevant.
>=20
> b)Readers who are familiar with RFC 6822. For them it is useful to know w=
hat
> changed - which is described in Appendix A.
>=20
> In order not to distract readers of type "a" - as well as to provide an
> "uninterrupted" description of the normative behavior I believe placement
> of the change description in an Appendix improves the readability of the
> document.
>=20
> Does this make sense to you?
>=20
> > 2. In Abstract, state clearly that this standard introduces the
> > support for instances vs. other already existing concepts also listed
> > in the Abstract (i.e., circuits, adjacencies,  topologies, etc.).
>=20
> [Les:] The Abstract currently says:
>=20
> "This draft describes a mechanism that allows a single router to share
>    one or more circuits among multiple Intermediate System To
>    Intermediate System (IS-IS) routing protocol instances."
>=20
> Previous to this extension, a router could have multiple instances of the=
 IS-IS
> protocol, but multiple instance could not be run over the same interface.
> So we are not introducing "instances", but we are introducing the ability=
 to
> enable multiple instances on the same interface.
>=20
> > Reason: The wording is not clear about what is the new feature vs.
> > what are the new benefits vs. what was the original baseline
>=20
> >3. Throughout the
> > document, use "standard instance" instead of "IID =3D 0" or "IID #0".
> > Reason: Expressions "standard instance", "IID =3D 0" and "IID #0" are
> >used  interchangeably throughout the document. It seems that they all
> >refer to the  same thing - the implementation of the original protocol
> >without the concept  of instances. Please, correct me if I am wrong.
>=20
> [Les:]  I don't think this is possible without seriously compromising the
> document. For example:
>=20
> Section 2.1
>=20
> " IID #0 is reserved for the standard instance supported by legacy
>    systems. "
>=20
> Changing this to  " Standard instance is reserved for the standard instan=
ce ..."
>=20
> Is clearly nonsensical.
>=20
> Later in Section 2.1
>=20
> "When the IID =3D 0, the list of supported ITIDs MUST NOT be present."
>=20
> What is being discussed here is what is the correct behavior when an MI-
> capable router sends a PDU associated IID #0 and includes the new IID TLV=
.
> Replacing this with "When the standard instance..." loses the important p=
oint
> that the value of the IID in the IID TLV in this case is "0".
>=20
> Hope this helps clarify things.
>=20
> > 4. In section 2 par 3, change "support" and "operates" to "MUST
> > support" to use requirements language.
>=20
> [Les:] I am on the fence as regards this change. Section 2 is an introduc=
tion to
> the following sub-sections - which define the normative behavior. But the
> introduction itself is not defining normative behavior - it is providing =
a
> context in which the protocol extensions defined in the following sub-
> sections can be understood.
>=20
> I am more inclined to change the "MAY" used later in the same paragraph
> you mention to "may" so it is consistent with the rest of this section.
>=20
> ???
>=20
>=20
> > 5. In section 2 par 2, change "may" to either "can" or "MAY" to
> > clarify the intent.
>=20
> [Les:] Did you mean Section 2.1 para 2?
> If so I agree to the change.
>=20
> > 6. In section 2.1 par 3, clarify whether IID #0 is ever being used on t=
he wire.
>=20
> [Les:] There are numerous places in the document where the legal use of I=
ID
> #0 is discussed. I do not understand how a reader would conclude that IID=
 #0
> is never sent on the wire.
>=20
> > Explain the concept of the "standard interface" (see previous comment)
>=20
> [Les:] There is no mention of "standard interface" - did you mean "standa=
rd
> instance"?
>=20
> If so, Section 1 paragraph 4 states:
>=20
> "Legacy routers support the standard
>    or zero instance of the protocol."
>=20
>    Les


From nobody Sat Apr 15 02:36:00 2017
Return-Path: <Francis.Dupont@fdupont.fr>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98FBF12704B; Sat, 15 Apr 2017 02:35:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Francis Dupont <Francis.Dupont@fdupont.fr>
To: <gen-art@ietf.org>
Cc: dhcwg@ietf.org, ietf@ietf.org, draft-ietf-dhc-relay-server-security.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149224895859.15792.12555844017714647455@ietfa.amsl.com>
Date: Sat, 15 Apr 2017 02:35:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/N1eSc1DxjrRDJBiulaRSVTBGjl4>
Subject: [Gen-art] Genart telechat review of draft-ietf-dhc-relay-server-security-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 15 Apr 2017 09:35:59 -0000

Reviewer: Francis Dupont
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-dhc-relay-server-security-??
Reviewer: Francis Dupont
Review Date: 2017-04-15
IETF LC End Date: 2017-03-13
IESG Telechat date: Not scheduled for a telechat

Summary: Ready

Major issues: None

Minor issues: None

Nits/editorial comments: I talked with authors at the IETF meeting: my
comments were addressed.




From nobody Mon Apr 17 16:00:22 2017
Return-Path: <oritl@microsoft.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CD3D1242F7; Mon, 17 Apr 2017 16:00:21 -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, RCVD_IN_DNSWL_NONE=-0.0001, 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 YeJzoQCAjaeM; Mon, 17 Apr 2017 16:00:17 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0107.outbound.protection.outlook.com [104.47.36.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B89491286AB; Mon, 17 Apr 2017 16:00:17 -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=3Z3RglyQQF+6Uu9MogXhgZRakBbd4MaKZUEgzrjEDGg=; b=Q+Nc5lNjQioJTb2fUrCyOINf2o7zbcJuOegwYQLxCfBp07utkV9pIpC/stkGuo5CE6DBNz+vtQrj5pkb+/TPly+CFO1TsdC0Jd8p20wK3iL+I3C6Hb326ZSNG7hVlO78zKIOklJs1SQj43cBhpdFgwKj/bg7TORFexqR/4AxvDY=
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com (10.164.2.156) by CY1PR0301MB2123.namprd03.prod.outlook.com (10.164.2.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.10; Mon, 17 Apr 2017 23:00:14 +0000
Received: from CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) by CY1PR0301MB2122.namprd03.prod.outlook.com ([10.164.2.156]) with mapi id 15.01.1034.013; Mon, 17 Apr 2017 23:00:14 +0000
From: Orit Levin <oritl@microsoft.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "ietf@ietf.org" <ietf@ietf.org>, "draft-ietf-isis-mi-bis.all@tools.ietf.org" <draft-ietf-isis-mi-bis.all@tools.ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
Thread-Index: AdKvMQJviOL5quEPRPel7BR3psjAJABiHiqgAJGI1kAAbW6QgADEG3NQ
Date: Mon, 17 Apr 2017 23:00:13 +0000
Message-ID: <CY1PR0301MB2122E2E3ED639D1E1D85A8AFAD060@CY1PR0301MB2122.namprd03.prod.outlook.com>
References: <CY1PR0301MB21227CD18EA946CE8286711DAD0C0@CY1PR0301MB2122.namprd03.prod.outlook.com> <dc04ef63da5242d6a57386cb9d07b005@XCH-ALN-001.cisco.com> <CY1PR0301MB21222E388C390E119F583D4DAD020@CY1PR0301MB2122.namprd03.prod.outlook.com> <1fa6af5d967d45d4b45d09afdb8fcc85@XCH-ALN-001.cisco.com>
In-Reply-To: <1fa6af5d967d45d4b45d09afdb8fcc85@XCH-ALN-001.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [130.217.31.226]
x-microsoft-exchange-diagnostics: 1; CY1PR0301MB2123; 7:z4+LZfQnD+ZkOutVtivsZlOPd6Qe26vIxjfBak2qY+XAogsDKavWtxmIugCIA1pszSzNoUofJqlozivv5IX5M9lU7HTvxIeC4cimzA/vFbhQl4ct+vxH2vLHRntGWFABkKLAdO+Mn2Q4CSJg+ekfxlWcRndR9plpLNY/FNQ0n3kr4VkAD37+N4KuV4pKWdpUMVii18mBnqcBZMvkl71cvumz0jeg6kDkeqjSLdvuZi3S/erjTfBREX3mJkwQIxVHSXYlaKbsZcdU4b8xBJrazChIAhAs+EuRnDvfDHJ6gWwDVEhniISEWl9v99KDUlouIX0rwOZJ9cXdw7gToXXkzhoX9iPReeNR6Wgi/csAyRQ=
x-ms-office365-filtering-correlation-id: 3be57a2a-018c-4451-dbc0-08d485e58210
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081);  SRVR:CY1PR0301MB2123; 
x-microsoft-antispam-prvs: <CY1PR0301MB2123AC233EF855D13F7F3DC1AD060@CY1PR0301MB2123.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(192374486261705)(131327999870524)(788757137089)(95692535739014); 
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3002001)(6055026)(61426038)(61427038)(6041248)(201703131423075)(201702281528075)(201703061421075)(20161123564025)(20161123555025)(20161123560025)(20161123562025)(6072148); SRVR:CY1PR0301MB2123; BCL:0; PCL:0; RULEID:; SRVR:CY1PR0301MB2123; 
x-forefront-prvs: 02801ACE41
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39850400002)(39450400003)(39400400002)(39860400002)(39840400002)(39410400002)(377424004)(13464003)(129404003)(377454003)(5660300001)(7736002)(8676002)(54356999)(8936002)(81166006)(50986999)(76176999)(38730400002)(189998001)(66066001)(6116002)(2501003)(10090500001)(5005710100001)(33656002)(3846002)(122556002)(74316002)(10290500002)(102836003)(93886004)(305945005)(2900100001)(53546009)(6436002)(230783001)(99286003)(7696004)(4326008)(2950100002)(55016002)(9686003)(6506006)(6306002)(2906002)(53946003)(54906002)(86612001)(77096006)(25786009)(53936002)(6246003)(86362001)(3280700002)(3660700001); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR0301MB2123; H:CY1PR0301MB2122.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 Apr 2017 23:00:13.9886 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR0301MB2123
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/QE_6hQLOk9UoSdwev0_YsRQxSF0>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 17 Apr 2017 23:00:21 -0000

Dear Les,

I see that you "agreed" to correct two typos only.
I disagree with your reasons for not making the document more readable and =
complete. Note that "more complete" doesn't necessarily mean "more prescrip=
tive". It means removing ambiguities that will continue hurting interoperab=
ility of new and existing implementations.=20
Since your guiding principle is "don't rock the boat / don't describe what =
to do - only what NOT to do", I see no point in arguing point-by-point.=20
I know that different Areas have different standards for their documents, s=
o I leave it to your community.

Thanks,
Orit.

-----Original Message-----
From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]=20
Sent: Thursday, April 13, 2017 8:06 PM
To: Orit Levin <oritl@microsoft.com>; gen-art@ietf.org
Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02

Orit -

It is obvious you spent a lot of time on this review - and I do want to be =
respectful of that.
However, there is a larger context here which I think has a significant bea=
ring on handling of many of your comments.

RFC 6822 was published over 4 years ago. Multiple interoperable implementat=
ions exist. The bis version makes some modest - but significant changes. Ho=
wever, we deliberately strived to keep the bis version as consistent as pos=
sible with RFC 6822 in order to minimize the possibility that aspects of th=
e specification which had NOT been changed would be reinterpreted simply be=
cause the wording had changed. So, in cases where you suggest (below) that =
a different wording is desirable I am very reluctant to make such changes b=
ecause of the above concern.
If I do not indicate any response to a particular comment you can interpret=
 as meaning:

"Unnecessary changes relative to RFC 6822 are not desirable."

Inline.

> -----Original Message-----
> From: Orit Levin [mailto:oritl@microsoft.com]
> Sent: Thursday, April 13, 2017 4:59 PM
> To: Les Ginsberg (ginsberg); gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> Hi Les,
> Sorry for the delay in response.
> Your feedback was very helpful. Below is a refresh of my comments. I=20
> tried to make them more pointed and some are new.
>=20
> Summary: This draft is "ready with issues" for publication.
>=20
> General:
> 1) For implementers who are familiar with the history and the intent=20
> of this extension, the information in the draft is probably sufficient=20
> to serve as a check list for implementing a multi-instance IS-IS=20
> router. For all other readers, the document doesn't contain an=20
> overview of the new mode of operation, i.e. where the instances are=20
> not a configuration and an internal implementation choice only, but=20
> are exposed through the protocol to achieve the stated objective.=20
> Lacking such an overview, the reader needs to reverse-engineer the logic =
behind the documented guidance.

[Les:] I am not sure I understand your concern. You seem to be suggesting t=
hat readers won't know when to use MI and when to simply create multiple no=
n-MI instances of the protocol.
The short answer to that is that it is not the purpose of this document to =
make that decision. We have provided some new functionality - it is up to t=
he user to decide when it is appropriate to use the new functionality and w=
hen it is not. We have provided some guidance in Sections 3 and 4 - but thi=
s is non-normative - as it should be.
But your use of "reverse-engineer" confuses me, so likely I do not understa=
nd your point.

As regards new vs old readers, the new version of the document provides as =
much (or as little) guidance as RFC 6822 - so I do not see why new readers =
would have any more issues than new readers of RFC 6822 had 4 years ago.


> 2) The draft talks about "extensions" in plural. Based on a single=20
> extension on the wire and the overall goal of the new mechanism, I=20
> would say that it is a single extension only.  How many protocol=20
> extensions does this document define? If they can be clearly=20
> separated, then it needs to be clarified throughout the document.=20
> Otherwise, the language throughout the document needs to be changed from =
"extensions" to "the extention".

[Les:] There are multiple changes in protocol behavior described - hence th=
e term extensions is correct.

> 3) Editorial: Please, compare (Diff) the current draft with the=20
> published RFC 6822. You will find that various RFC Editor corrections=20
> got lost in this bis document. Some repeating examples of the lost=20
> corrections are "instance- specific", " topology (or topologies)" and "Ty=
pe-Length-Value".

[Les:] Noted - thanx.

> My comments below are a result of a reverse-engineering exercise.=20
> Please, consider incorporating the suggested clarifications to improve=20
> the document readability. I might have misunderstood some of the=20
> parts; in such cases, please, provide an alternative text.
>=20
> Abstract
> 1) Add clarification: "This document is not backwards compatible with=20
> RFC 6822."

[Les:] This statement is made explicitly in the Appendix - and I believe th=
at is where it belongs for reasons I have previously stated.

> 2) Par. 2, replace the first two sentences with: "Configuration of=20
> multiple protocol instances within a router allow the isolation of=20
> resources associated with each instance. This document introduces a=20
> new mode of operation where the protocol instances are not a matter of=20
> configuration only, but are exposed through the new protocol extension=20
> to achieve the objective stated above."
> 3) Par. 3 uses both present and future time. Does it mean before and=20
> after the extension? Please, clarify by spelling out the intent and/or=20
> changing the grammar.
>=20
[Les:] The sentence will in any case be changed when the document becomes a=
n RFC - not worth discussing.

> 1. Introduction
> 1) Move par. 3 to become the opening paragraph (i.e., par.1 ) in the=20
> Introduction to improve its logical flow (also related to the next commen=
t).
> 2) Par 4, sentence #2 says "This document defines an extension to=20
> IS-IS to allow non-zero instances...". My assumption is that the=20
> intent of this draft is to define a single extension, which will=20
> improve the routing operations in a number of ways. If this is the=20
> case, the quote needs to be replaced with "The MI-IS-IS extension,=20
> defined in this document, also allows so-called "non-zero instances"..." =
.
> 3) Par 4, sentences #4 and #5 are not sufficient to describe the new=20
> mode of operation introduced by this extension. Below is my attempt to de=
scribe it.
> Please, correct, if I got it wrong.
> "IS-IS router instances that support this extension are preconfigured=20
> with unique non-zero Instance Identifiers (IIDs) giving them the name=20
> "non-zero instances". In addition, MI RTRs MAY (or SHOULD ?) implement=20
> the legacy (or so-called "standard") instance of the IS-IS router for=20
> backwards compatibility with legacy IS-IS routers. IID #0 is only used=20
> by MI-RTRs to convey information associated with such standard=20
> interface if implemented. See section 2.6 Interoperability Considerations=
 for more details."
> 4) Par 4, replace the two "may" with "can" to clarify the intent.
> 5) Par 5, change "defined" to "described" since the examples are not=20
> normative.
> 5) Par 5, add references to the (sub)sections containing the=20
> description of the two methods.
> 6) Par 7, move the last paragraph before listing the two examples and=20
> adjust the text accordingly, to improve the logical flow.
> 7) In the end of the Introduction add a reference: "This RFC is not=20
> backwards compatible with RFC 6822. Differences between this document=20
> and RFC 6822 are described in Annex A." ... so that others don't skip=20
> it by mistake as I did earlier...
>=20
 [Les:] Reading of the Appendix is optional - the new version is usable wit=
hout any need to refer to RFC 6822 - and that is its primary purpose.

> 2. Elements of Procedure
> 1) It seems that this section (informational) and its subsections=20
> (normative) use present and future times and, at times,  the normative=20
> language inconsistently both within the sections and among the=20
> sub-sections. Please, explain the reasons and improve consistency accordi=
ngly.
> 2) Par 1, clarify the scope by adding "within a routing domain" at the=20
> end of the first sentence.
> 3) Par 1, after the first sentence add a new sentence alone the=20
> following lines "Routers form adjacencies and exchange routing updates=20
> only if their IIDs correspond." This explains the basic premise of the wh=
ole mechanism.
> 4) Par 2, change "may" to "can" or "might" for consistency.
>=20
> Section 2.1
> 1) Par 2, change "may" to "MAY".
> 2) Par 3, remove "supported by legacy systems" from the first sentence=20
> to avoid confusion. My understanding is that IID #0 is reserved  for=20
> use by MI- RTRs that also implement the standard instance and=20
> advertise it in IIH using IID-TLV.
> 3) Par 3, change "except where noted" to "except as noted in section=20
> 2.6.2 (?)".  This is an excellent place to explain the logic behind=20
> this MUST NOT statement or, at least, state the general circumstances=20
> where IID #0 is included in IID-TLV.
> 4) Par 9 (4th after the picture), change "as described later" to " as=20
> described in section 2.6.2 (?)".
> 5) Par 13, change "recommended" to "RECOMMENDED".
> 6) Editorial: Par 13, change "particularf" to "particular".
>=20
[Les:] #6 - Agreed.

> Section 2.2
> 1) Add that MI-RTR MAY (or SHOULD) implement the standard instance as=20
> well and which packets are used to advertise it.
> 2) Rephrase "marks ... by including" to "MUST include" to use=20
> requirements language.
>=20
> Section 2.3
> Editorial: Replace "normal" with "usual".
>=20
> Section 2.4.1
> 1) Par 1. Replace "IID #0" with "standard instance".
> 2) Par 1. Replace "instances other than IID #0" with "non-zero instances"=
.
> 3) Par 2 second sentence. What does it mean "normal expectations"? Is=20
> this a network configuration requirement? Please, clarify in the text.
>=20
> Section 2.4.2 Improve language consistency
> 1) Verbs are used inconsistently: some are used in present time,=20
> others in future time.
>=20
> Section 2.5, replace "exists" with "MUST be performed".
> Section 2.5.1, replace "only operates" with "MUST only be performed".
> Section 2.5.2, replace "This requires" with "It is REQUIRED".
> Section 2.5.2 third sentence, after "inconsistent" insert "due to=20
> their configuration". (Please, correct me if I am wrong.)
>=20
> Section 2.6.1
> 1) Editorial: Par 1, first sentence, replace "not to cause" to "to avoid"=
.
> 2) Par 2, remove "(IID #0)".
> 3) Par 2, replace "non-zero IID" with "non-zero instance".
> 4) Par 5 NOTE, replace "IID #0" with "standard instance".
>=20
> Section 2.6.2
> Replace all four appearances of "IID #0" with "standard instance".
>=20
> Section 3.1
> Replace the two "MAY" to "can".
>=20
> 7 Security Considerations
> Discuss possible additional security considerations (or the lack of=20
> them) related to the exposure of "instances" on the wire.
> Reason: Beyond the normal IETF procedure, this is especially important=20
> because "multiple instances allow isolation of resources..." Can this=20
> isolation, if observed or interfered on the wire, be damaging beyond=20
> the previous "standard instance" situation.
>=20

[Les:] There are no security concerns associated with the use of multiple i=
nstances.
Security reviews of the document have been satisfied w the current contents=
.

   Les

> Thanks,
> Orit.
> -----Original Message-----
> From: Les Ginsberg (ginsberg) [mailto:ginsberg@cisco.com]
> Sent: Saturday, April 8, 2017 4:23 PM
> To: Orit Levin <oritl@microsoft.com>; gen-art@ietf.org
> Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> Subject: RE: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
>=20
> Orit -
>=20
> Thanx for the review.
> Responses inline.
>=20
> > -----Original Message-----
> > From: Orit Levin [mailto:oritl@microsoft.com]
> > Sent: Thursday, April 06, 2017 8:27 PM
> > To: gen-art@ietf.org
> > Cc: ietf@ietf.org; draft-ietf-isis-mi-bis.all@tools.ietf.org
> > Subject: Gen-ART Last Call review of draft-ietf-isis-mi-bis-02
> >
> > 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.
> >
> > For more information, please see the FAQ at
> >
> > <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
> >
> > Document: draft-ietf-isis-mi-bis-02
> > Reviewer: Orit Levin
> > Review Date: 2017-04-06
> > IETF LC End Date: 2017-04-07
> > IESG Telechat date: 2017-04-13
> >
> > Summary: This draft is "ready with issues" for publication.
> >
> > Major issues: None.
> >
> > Minor issues:
> >
> > 1. Add text explaining the reason (or reasons) for replacing the=20
> > original RFC
> > 6822 from 2012.
> > Reason: It is a "bis" draft and there is no mention about it in the tex=
t.
>=20
> [Les:] Note that the latest revision of the draft correctly identifies=20
> the draft as obsoleting RFC 6822. Previous versions had incorrectly=20
> identified this as an update to RFC 6822.
> This is then the new Standard for the IS-IS MI support.
>=20
> There are two classes of future readers of this document:
>=20
> a)Readers who are unfamiliar with RFC 6822. For them what changed=20
> between RFC 6822 and this document is irrelevant.
>=20
> b)Readers who are familiar with RFC 6822. For them it is useful to=20
> know what changed - which is described in Appendix A.
>=20
> In order not to distract readers of type "a" - as well as to provide=20
> an "uninterrupted" description of the normative behavior I believe=20
> placement of the change description in an Appendix improves the=20
> readability of the document.
>=20
> Does this make sense to you?
>=20
> > 2. In Abstract, state clearly that this standard introduces the=20
> > support for instances vs. other already existing concepts also=20
> > listed in the Abstract (i.e., circuits, adjacencies,  topologies, etc.)=
.
>=20
> [Les:] The Abstract currently says:
>=20
> "This draft describes a mechanism that allows a single router to share
>    one or more circuits among multiple Intermediate System To
>    Intermediate System (IS-IS) routing protocol instances."
>=20
> Previous to this extension, a router could have multiple instances of=20
> the IS-IS protocol, but multiple instance could not be run over the same =
interface.
> So we are not introducing "instances", but we are introducing the=20
> ability to enable multiple instances on the same interface.
>=20
> > Reason: The wording is not clear about what is the new feature vs.
> > what are the new benefits vs. what was the original baseline
>=20
> >3. Throughout the
> > document, use "standard instance" instead of "IID =3D 0" or "IID #0".
> > Reason: Expressions "standard instance", "IID =3D 0" and "IID #0" are=20
> >used  interchangeably throughout the document. It seems that they all=20
> >refer to the  same thing - the implementation of the original=20
> >protocol without the concept  of instances. Please, correct me if I am w=
rong.
>=20
> [Les:]  I don't think this is possible without seriously compromising=20
> the document. For example:
>=20
> Section 2.1
>=20
> " IID #0 is reserved for the standard instance supported by legacy
>    systems. "
>=20
> Changing this to  " Standard instance is reserved for the standard instan=
ce ..."
>=20
> Is clearly nonsensical.
>=20
> Later in Section 2.1
>=20
> "When the IID =3D 0, the list of supported ITIDs MUST NOT be present."
>=20
> What is being discussed here is what is the correct behavior when an=20
> MI- capable router sends a PDU associated IID #0 and includes the new IID=
 TLV.
> Replacing this with "When the standard instance..." loses the=20
> important point that the value of the IID in the IID TLV in this case is =
"0".
>=20
> Hope this helps clarify things.
>=20
> > 4. In section 2 par 3, change "support" and "operates" to "MUST=20
> > support" to use requirements language.
>=20
> [Les:] I am on the fence as regards this change. Section 2 is an=20
> introduction to the following sub-sections - which define the=20
> normative behavior. But the introduction itself is not defining=20
> normative behavior - it is providing a context in which the protocol=20
> extensions defined in the following sub- sections can be understood.
>=20
> I am more inclined to change the "MAY" used later in the same=20
> paragraph you mention to "may" so it is consistent with the rest of this =
section.
>=20
> ???
>=20
>=20
> > 5. In section 2 par 2, change "may" to either "can" or "MAY" to=20
> > clarify the intent.
>=20
> [Les:] Did you mean Section 2.1 para 2?
> If so I agree to the change.
>=20
> > 6. In section 2.1 par 3, clarify whether IID #0 is ever being used on t=
he wire.
>=20
> [Les:] There are numerous places in the document where the legal use=20
> of IID
> #0 is discussed. I do not understand how a reader would conclude that=20
> IID #0 is never sent on the wire.
>=20
> > Explain the concept of the "standard interface" (see previous=20
> > comment)
>=20
> [Les:] There is no mention of "standard interface" - did you mean=20
> "standard instance"?
>=20
> If so, Section 1 paragraph 4 states:
>=20
> "Legacy routers support the standard
>    or zero instance of the protocol."
>=20
>    Les


From nobody Mon Apr 17 23:49:24 2017
Return-Path: <martin.thomson@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 98D66127077; Mon, 17 Apr 2017 23:49:16 -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 2F4hiGK-YXXS; Mon, 17 Apr 2017 23:49:15 -0700 (PDT)
Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1CB6D1201F2; Mon, 17 Apr 2017 23:49:15 -0700 (PDT)
Received: by mail-lf0-x232.google.com with SMTP id c80so25193812lfh.3; Mon, 17 Apr 2017 23:49:14 -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=46B7kiD6ba1pzb7vIdLBMFVYv+IG93qlNGNk9dYnH68=; b=Gg1sfv5x2Bu/sbnTz4vsZOvQUKRhIquqmIoNHeqfRxczIua2KNSpmvm2lHLqY6VnRL LxtPwi1cA8EnTDCXqPgXUyexNoSXQBQQb26857mvSThe+a6uz9NZldlp66WoC8ndLYJy x1ThhMGfN1Z1UaSQr98bg/ftIX2RQpLakVqOgN9TcV+szLNtguiaZ9SaAVL+gRaxgegb pW51A4Qk13gA/I9FfopvNwVFkO7UJUu17EOIDbp+Dtdk6GuZz5/t+FH/smQ1SCo6gODO 2Ph1tUrnXcJ+Cy2g9SgWcsFx9jtS+HkghaxV7L4YZ8q2Mu1ltPZEzvziHnJ0ldk9eQ+I UDWg==
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=46B7kiD6ba1pzb7vIdLBMFVYv+IG93qlNGNk9dYnH68=; b=gZrSf/7eRV2Li+glLB6UxSgcSEKVvoDWku/NO8G7WNQfgv8cugS2MuHzuNhu/3akPp Dq8jAnJXjBXxq2v160RTjc91jYJF9lpyeXpCuKbhm1DB1xxOG1sqj7cCHZJJKtDfZaaQ iRk/WRRVkQkeAmuEb5ajLBW4J710u8Gl7MWpPdjWVKGTVCQXq4/nVWs9C0YljKI0nYAl mLofFjcck/JZJkpn+nAl+wf9r7zh+W7xAPq/U459OnW8Gjk5iBLCqaFXSa01ngEyEoXN Okq5kBTBrB3gwsLXM5CFc73PL18vudvXlfhC5iemsqPjR5TCCoEb+5P6Ab5JuTXF47cV ocaA==
X-Gm-Message-State: AN3rC/5Jzmytpy9S5dF0kW1vmHys7Je9RreFlMrbz535Q/Q9v/mm0T6g SAU12lJ8/sBH+6hi+vuFHd3CCH74WQ==
X-Received: by 10.25.79.27 with SMTP id d27mr2802667lfb.76.1492498153390; Mon, 17 Apr 2017 23:49:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.83.5 with HTTP; Mon, 17 Apr 2017 23:49:12 -0700 (PDT)
In-Reply-To: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
References: <149145796867.21962.18267109107454658774@ietfa.amsl.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 18 Apr 2017 16:49:12 +1000
Message-ID: <CABkgnnUFBGngUzqM0GjpwyvF0w9pCB3eqFgxL8LY_R1otp49dw@mail.gmail.com>
To: Pete Resnick <presnick@qti.qualcomm.com>
Cc: "gen-art@ietf.org" <gen-art@ietf.org>, draft-ietf-httpbis-encryption-encoding.all@ietf.org,  "ietf@ietf.org" <ietf@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/g4d1CGjr5WzGell1ax2Ujpgv-ok>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-httpbis-encryption-encoding-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 06:49:17 -0000

Thanks Pete,

On 6 April 2017 at 15:52, Pete Resnick <presnick@qti.qualcomm.com> wrote:
>       A "keyid" parameter SHOULD be a UTF-8
>       [RFC3629] encoded string, particularly where the identifier
> might
>       need to appear in a textual form.
>
> I presume that simply means "might need to be rendered" and does not
> include "might need to be typed in by someone", correct? The former is
> easy; the latter probably requires a bit more text.

Indeed.  Until we have a good copy-and-paste version of the Unicode
typed/spoken/interpretive-danced input problem for security
identifiers, it is not a goal to have specifications casually tackling
problems that are outside their (and maybe anyone's) capabilities.

I made the suggested change in the editor's copy.


From nobody Tue Apr 18 06:41:16 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E99D12EC51; Tue, 18 Apr 2017 06:41:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stewart Bryant <stewart.bryant@gmail.com>
To: <gen-art@ietf.org>
Cc: grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.49.1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
Date: Tue, 18 Apr 2017 06:41:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/yEue8PvXACcy7p4hYicEtXtT1oI>
Subject: [Gen-art] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 13:41:16 -0000

Reviewer: Stewart Bryant
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-grow-large-communities-usage-??
Reviewer: Stewart Bryant
Review Date: 2017-04-18
IETF LC End Date: 2017-04-21
IESG Telechat date: Not scheduled for a telechat

Summary:

This is mostly a well written document, although unfortunately there
are a number of matters that really need to be looked at.

Major issues:

Abstract

   Examples and inspiration for operators to use BGP Large
Communities.

SB> Even if you just copy the Introduction, the Abstract should really
be expanded
SB> to help the reader understand whether or not they want read the
RFC
SB> or if they had read it what it was about.

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

5.  Security Considerations

   Operators should note the recommendations in Section 11 of BGP
   Operations and Security [RFC7454].

SB> You do not address the question of whether there are new
considerations, or considerations
SB> that are of increased importance? Is there is text somewhere
SB> that discusses the integrity and synchronization of the
parameters
SB> and any consequences that arise?

===========

Minor issues:

2.2.  Action Communities

   Action Communities are added as a label to request that a route be
   treated in a particular way within an AS.  The operator of the AS
   defines a routing policy that adjusts path attributes based on the
   community.  For example, the route's propagation characteristics,
the
   LOCAL_PREF (local preference), the next-hop, or the number of
AS_PATH
   prepends to be added when it is received or propagated can be
   changed.

SB> Although these are well known to the target audience, I think you
SB> need some references in the above para.


Nits/editorial comments: 

6.  IANA Considerations

   None.

SB> A little briefer than normal. 


From nobody Tue Apr 18 08:26:59 2017
Return-Path: <heas@shrubbery.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11BBE126C0F; Tue, 18 Apr 2017 08:26:50 -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 96s72pE_IZqe; Tue, 18 Apr 2017 08:26:48 -0700 (PDT)
Received: from guelah.shrubbery.net (guelah.shrubbery.net [198.58.5.1]) by ietfa.amsl.com (Postfix) with ESMTP id C47D2126E01; Tue, 18 Apr 2017 08:26:48 -0700 (PDT)
Received: by guelah.shrubbery.net (Postfix, from userid 7053) id CC476816B5; Tue, 18 Apr 2017 15:09:29 +0000 (UTC)
Date: Tue, 18 Apr 2017 15:09:29 +0000
From: heasley <heas@shrubbery.net>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Message-ID: <20170418150929.GC99602@shrubbery.net>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <149252287543.16134.18005737444773296286@ietfa.amsl.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/gen-art/KX0m6HnI4vUnF8E0p4xPi4P-O4E>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 15:26:50 -0000

Tue, Apr 18, 2017 at 06:41:15AM -0700, Stewart Bryant:
> 5.  Security Considerations
> 
>    Operators should note the recommendations in Section 11 of BGP
>    Operations and Security [RFC7454].
> 
> SB> You do not address the question of whether there are new
> considerations, or considerations
> SB> that are of increased importance? Is there is text somewhere
> SB> that discusses the integrity and synchronization of the
> parameters
> SB> and any consequences that arise?

I agree that this draft lacks one detail of how RFC7454 applies to it, but
I also note that RFC7454 also does not explain the dangers of ignoring
the recommendations in S11.  I suggest that the subject of removing one's
own communities is subjective and a local issue for which we can only
hypothesize.  I'll try to address the latter, but I do not personally feel
this is necessary.

> ===========
> 
> Minor issues:
> 
> 2.2.  Action Communities
> 
>    Action Communities are added as a label to request that a route be
>    treated in a particular way within an AS.  The operator of the AS
>    defines a routing policy that adjusts path attributes based on the
>    community.  For example, the route's propagation characteristics,
> the
>    LOCAL_PREF (local preference), the next-hop, or the number of
> AS_PATH
>    prepends to be added when it is received or propagated can be
>    changed.
> 
> SB> Although these are well known to the target audience, I think you
> SB> need some references in the above para.

How so?  Do you mean actual community values similar to the example in 3.1.1?
Because these are int 4.x, as 3.x are examples related to 2.1.

> Nits/editorial comments: 
> 
> 6.  IANA Considerations
> 
>    None.
> 
> SB> A little briefer than normal. 

Isn't it elegant. :)

thanks for the review.


From nobody Tue Apr 18 16:59:22 2017
Return-Path: <job@instituut.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D818A12EB30 for <gen-art@ietfa.amsl.com>; Tue, 18 Apr 2017 16:59:06 -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=instituut-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 6Px3F6P6dxb0 for <gen-art@ietfa.amsl.com>; Tue, 18 Apr 2017 16:59:06 -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 665C7129463 for <gen-art@ietf.org>; Tue, 18 Apr 2017 16:59:02 -0700 (PDT)
Received: by mail-wm0-x236.google.com with SMTP id o81so67841380wmb.1 for <gen-art@ietf.org>; Tue, 18 Apr 2017 16:59:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=DF3uJat12kvgKRtdU59rkzOHPq8lXIuqdOvP0M2DTjw=; b=Kh0xYTjmgskNnBOGVDhZn9LtH50yrnyxJ439ZHvMvFTWqUlSZL/m1CA0bl237YHyEL x95F0wCozvcHjVhdjm8sXJGfe8jZuzd6vMfZ/HaKKZX4POnP5AkOvfPybKbgA7wsz0k4 XFJTDeJZSd7LlHbprNN0uoMozZWHcNup8vIS5ZCTL1ZN1AwVTHUMicrqWjQOLUFm/Ma+ G/sOa4Frjm8g8Hqqm2FiPrAixFZ3MPS7EQuzI8As0Vx/n8uSWpaAEpAgCJQPCtxmw+aR PMh7rxRdt/LKtShZ0V/u0arHAJTMcJCSMMgfNOpXjiOXU4SSMIt0H2MLaAy4rjBce/89 59pA==
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=DF3uJat12kvgKRtdU59rkzOHPq8lXIuqdOvP0M2DTjw=; b=FSUdtIz9hvww6esdLocaMemTxozzBD+XXw/Rr5ExkscTZ1AyQF4yk5+5wSL7o5O81G 4zg2/49T4z9zXvis9LaqmilKp8fP/JWwOoaOsC4QnTI1KX9tPz91zBNjSVs/XtknHMnk E1vPM4eNlQxf9mrNWlVi7vT96FkPIz6Jup8B6Ok3fv1lpnmFJyU2E9cvGgwf2C2h0l5I 9L7Z3lsZCd6ZCiBf/RRh9BDCrWFN5oK06AmvrXp//0bBDjpPalKvjIzOMs30CMuTfpph Ji2x6T0bmHAWddLf9Xnq1LLASC7/0FTf8+1ADOWmbnSiX+sAgOGKhAsl2bwzi0KsCswb HsCQ==
X-Gm-Message-State: AN3rC/61q6fZqQIYaCPmgPizL/qm5usJXkOcOHqr5PlcHfjwzaG3JClL IZ/dvaNvxqQFqIpfc/Qd7w==
X-Received: by 10.28.100.195 with SMTP id y186mr15705406wmb.68.1492559940550;  Tue, 18 Apr 2017 16:59:00 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:b007:e025:f7a1:2601]) by smtp.gmail.com with ESMTPSA id 31sm862871wrt.35.2017.04.18.16.58.59 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 18 Apr 2017 16:58:59 -0700 (PDT)
Date: Wed, 19 Apr 2017 01:58:58 +0200
From: Job Snijders <job@instituut.net>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Message-ID: <20170418235858.sgsa64r7b5th7zam@Vurt.local>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <149252287543.16134.18005737444773296286@ietfa.amsl.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/9gMFA385HHjY8jZTzf7kxv0PVVQ>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2017 23:59:07 -0000

Hi Bryant,

Thank you for taking the time to go through the document.

On Tue, Apr 18, 2017 at 06:41:15AM -0700, Stewart Bryant wrote:
> Please treat these comments just like any other last call comments.
> 
> SB> Even if you just copy the Introduction, the Abstract should
> SB> really be expanded to help the reader understand whether or not
> SB> they want read the RFC or if they had read it what it was about.

OK, we'll copy some text from the introduction section to the abstract
section to provide a better pitch why one would want to read this
document.

> ============
> 
> 5.  Security Considerations
> 
>    Operators should note the recommendations in Section 11 of BGP
>    Operations and Security [RFC7454].
> 
> SB> You do not address the question of whether there are new
> SB> considerations, or considerations that are of increased importance?

It is my understanding that RFC 8092 "BGP Large Communities" are just
like RFC 1997 "BGP Communities", but ...  larger (for lack of better
words). Referencing RFC 7454 seems plenteous.

So, what if there are not any additional considerations, If there were,
they would've been (or are) covered in RFC 8092's security section,
right?

This is an Internet-Draft targetted for Informational status, I'm not
sure what you expect here.

> SB> Is there is text somewhere that discusses the integrity and
> SB> synchronization of the parameters and any consequences that arise?

the what now? Can you elaborate on the above?

> ===========
> 
> Minor issues:
> 
> 2.2.  Action Communities
> 
>    Action Communities are added as a label to request that a route be
>    treated in a particular way within an AS.  The operator of the AS
>    defines a routing policy that adjusts path attributes based on the
>    community.  For example, the route's propagation characteristics,
>    the LOCAL_PREF (local preference), the next-hop, or the number of
>    AS_PATH prepends to be added when it is received or propagated can
>    be changed.
> 
> SB> Although these are well known to the target audience, I think you
> SB> need some references in the above para.

What reference would you suggest? You feel the section 2.2 text cannot
stand on its own?

Kind regards,

Job


From nobody Tue Apr 18 18:06:14 2017
Return-Path: <randy@psg.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50E8D124D68; Tue, 18 Apr 2017 18:06:12 -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 5x8X-9bjccYI; Tue, 18 Apr 2017 18:06:11 -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 0E8F31243F3; Tue, 18 Apr 2017 18:06:11 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com) by ran.psg.com with esmtp (Exim 4.86_2) (envelope-from <randy@psg.com>) id 1d0e4N-0000At-9m; Wed, 19 Apr 2017 01:06:07 +0000
Date: Wed, 19 Apr 2017 10:06:05 +0900
Message-ID: <m2vaq1p5oi.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Job Snijders <job@instituut.net>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
In-Reply-To: <20170418235858.sgsa64r7b5th7zam@Vurt.local>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local>
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/gen-art/yP5u1_IXhYB3Fek63Ko0SbyyfPA>
Subject: Re: [Gen-art] [GROW] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 01:06:12 -0000

>> 5.  Security Considerations
>> 
>>    Operators should note the recommendations in Section 11 of BGP
>>    Operations and Security [RFC7454].
>> 
>> SB> You do not address the question of whether there are new
>> SB> considerations, or considerations that are of increased importance?
> 
> It is my understanding that RFC 8092 "BGP Large Communities" are just
> like RFC 1997 "BGP Communities", but ...  larger (for lack of better
> words). Referencing RFC 7454 seems plenteous.
> 
> So, what if there are not any additional considerations, If there were,
> they would've been (or are) covered in RFC 8092's security section,
> right?
> 
> This is an Internet-Draft targetted for Informational status, I'm not
> sure what you expect here.
> 
>> SB> Is there is text somewhere that discusses the integrity and
>> SB> synchronization of the parameters and any consequences that arise?
> 
> the what now? Can you elaborate on the above?

you're supposed to guess

the normal hack here is

  this document introduces no new security issues beyond those discussed
  in 1997


From nobody Wed Apr 19 01:47:13 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C16213157F; Wed, 19 Apr 2017 01:46:58 -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 jfQ1uRl2DjPz; Wed, 19 Apr 2017 01:46:57 -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 DF713131576; Wed, 19 Apr 2017 01:46:56 -0700 (PDT)
Received: by mail-wm0-x230.google.com with SMTP id o81so74223789wmb.1; Wed, 19 Apr 2017 01:46:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=Ougxf9uJ25t+oNOaLThwQnfKjE44NoNBJsTUmD9K0i4=; b=bUpgBR07/A2qO3WX3zR+Z1rvZ/ajfcZUeL3Vr5dHQUCS1yc/OmAdcoD+Yi/ljXLOe9 iYSz1f8wxAuujq/pXBM8eZLenaCPzi08RWXHYRohd09oHqOPVgwXcUZrq/Eg7PTeCRC5 Ibr5ZFwvvZbp/k9+eM9CR220zBmhNhwDp0XDzlTIkzZk2d8s/hur4Rt+d/vxx0rJfcyw KYPs+LVyrLaopLXiNFjDNO6xlOtPWe0/MytWFFvr+YP6UySLrdfD8K0tw28Sm0C/Hotb QEUDAmhU7HTnHQ0kVaJ87XfTWJ+o5Ed74nFOIzmzxQdCHtCP6lggpmK9/77oy28iVj/1 iSjg==
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=Ougxf9uJ25t+oNOaLThwQnfKjE44NoNBJsTUmD9K0i4=; b=cOh4MxD/NFa1mrwuzc87qNjP7xvcpMz9u6OUkT74aji1SveD9sxA8NhMG6TRel6mGW wh0CH/X1rD5frnIvLjN8lA1UJfjKc5IiSPD8e6dAR+kd9Bp78k1WhK46cyLnqXCKhWQl wsn/h7ylIiopOquneAhtMOTrAmk4IBdNUKb7ycE3BlJZCD73iNiwXacHLSGJIRFbl1iY 3jI90OpninU4LQIxqjJXf4mzDgkerHFhUef/RsKo03aR+WMONuzmbMkWqTzHyr9Wod60 uXs6DxwjIcbnBUr+mgkbMQiFf7ynD9XNwLpgb2X0zB5oOnnn2ysd7oYtnBxmUe6DFCkK t/XA==
X-Gm-Message-State: AN3rC/5Z7UYN8Akrscu8iuQuP4x/Q85IRjcvromNAfR7B7JV646TKQZE TjbLG+fjJ6zMQFyIHSs=
X-Received: by 10.28.165.13 with SMTP id o13mr1909942wme.139.1492591615207; Wed, 19 Apr 2017 01:46:55 -0700 (PDT)
Received: from [10.66.4.239] ([131.227.23.37]) by smtp.gmail.com with ESMTPSA id e21sm2859828wma.5.2017.04.19.01.46.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 01:46:54 -0700 (PDT)
To: Job Snijders <job@instituut.net>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com>
Date: Wed, 19 Apr 2017 09:46:53 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170418235858.sgsa64r7b5th7zam@Vurt.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ojA1bvh9rm8lFvn9t4HbkWLCLdU>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 08:46:58 -0000

On 19/04/2017 00:58, Job Snijders wrote:
>
>> ============
>>
>> 5.  Security Considerations
>>
>>     Operators should note the recommendations in Section 11 of BGP
>>     Operations and Security [RFC7454].
>>
>> SB> You do not address the question of whether there are new
>> SB> considerations, or considerations that are of increased importance?
> It is my understanding that RFC 8092 "BGP Large Communities" are just
> like RFC 1997 "BGP Communities", but ...  larger (for lack of better
> words). Referencing RFC 7454 seems plenteous.
>
> So, what if there are not any additional considerations, If there were,
> they would've been (or are) covered in RFC 8092's security section,
> right?
>
> This is an Internet-Draft targetted for Informational status, I'm not
> sure what you expect here.
I was wondering if there was more scope to make mischief at a distance 
in a less
less obvious way than before.

If everyone is happy that there is no additional risk then I am fine, 
but seems to
me the more knobs you give the mischeif maker to turn the more security 
risks
you have.

>> SB> Is there is text somewhere that discusses the integrity and
>> SB> synchronization of the parameters and any consequences that arise?
> the what now? Can you elaborate on the above?
So you rely on the nodes that receive these community strings to 
interpret them in
a common way. Maybe this is an already solved problem, or an known risk, 
but what
if the dictionaries get out of sync?

>> ===========
>>
>> Minor issues:
>>
>> 2.2.  Action Communities
>>
>>     Action Communities are added as a label to request that a route be
>>     treated in a particular way within an AS.  The operator of the AS
>>     defines a routing policy that adjusts path attributes based on the
>>     community.  For example, the route's propagation characteristics,
>>     the LOCAL_PREF (local preference), the next-hop, or the number of
>>     AS_PATH prepends to be added when it is received or propagated can
>>     be changed.
>>
>> SB> Although these are well known to the target audience, I think you
>> SB> need some references in the above para.
> What reference would you suggest? You feel the section 2.2 text cannot
> stand on its own?
As I said I imagine that all readers will know the definition of 
LOCAL_PREF and
AS_PATH, but normally we give a reference in a documnet like this.

- Stewart


From nobody Wed Apr 19 01:52:23 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B61DA131585; Wed, 19 Apr 2017 01:52: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 k91G6eHyPaqD; Wed, 19 Apr 2017 01:52:13 -0700 (PDT)
Received: from mail-wr0-x243.google.com (mail-wr0-x243.google.com [IPv6:2a00:1450:400c:c0c::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6E69213158E; Wed, 19 Apr 2017 01:52:13 -0700 (PDT)
Received: by mail-wr0-x243.google.com with SMTP id l44so2264420wrc.2; Wed, 19 Apr 2017 01:52:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=SFAYnSLEx54i0XkbEkVy9DdmlNHF7h2XeHEkNh/A5Nw=; b=vMLw/BTfm9G+enfXJDe+pOEOSyiZeSvtslYVR68V9FiVzKvQ9WsOxnzTPkzPNdfCTl +bRTS9wr42JFuY4oNcz7d/RQwDFs7UsTJDB6EnTXk1biEx6AgjIodvb0A+5ExfeiD9eX L+NdBgR5C66MxeOxfwDje3tblEONa8s1nEVpLmjQ65NUzQCuL/FM6GuUVgH5xnEU4L44 3cKdsSaYB9ogE/p3dCnw+8/nOHVRSCXGYC2eJ9qLiD2JzuHrUqJOTlHLk33zoWPZq+An 0WBDHo2Jy6HzWzH/PO7iTVsKHLf+MRIBKD4ojUTVKPCbdsoNA1Haa3t9ZBx+hoUwC1DG goRg==
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=SFAYnSLEx54i0XkbEkVy9DdmlNHF7h2XeHEkNh/A5Nw=; b=kPSC8DOI3Hd6I9us+uR3VvSFcPt69CcfVpMAoD4ea0sUAL9Ysm6+MgFITDVdKet26w YP5iFUTNdI5cPr8WSHrXYC2Bv3He0dfb9Fe/vE54zXPZUYt4P6iNFt2st6erVr/481DW /mNaRiPToYDhABWymzuoMB+3Pjxgmr4nKKKbCpwS2CLexaJM7BCGKSW3cIfqATS6PetO OOJLQu/wc1RQsLRzzMpuNSdQkC2U2GVU/rfyevaaOYO6c+4DUQTY8+5IuXgKqAccJcHu hyRAyjZzXUBx/i977xHFhsXBBOtwUJa+7NU3YYC3I89i149+OJLCYllKLRIKEGMMaWuD AVdw==
X-Gm-Message-State: AN3rC/4PURalyj1gZODNHTrgjxOYAyQwm9S3D8CIpvenoDpOfH56s09C kBt0qr9fa1lYuLZ7rKs=
X-Received: by 10.223.162.152 with SMTP id s24mr1901087wra.27.1492591931635; Wed, 19 Apr 2017 01:52:11 -0700 (PDT)
Received: from [10.66.4.239] ([131.227.23.37]) by smtp.gmail.com with ESMTPSA id w16sm1486809wmd.0.2017.04.19.01.52.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 01:52:11 -0700 (PDT)
To: Randy Bush <randy@psg.com>, Job Snijders <job@instituut.net>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <m2vaq1p5oi.wl-randy@psg.com>
Cc: gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
Date: Wed, 19 Apr 2017 09:52:10 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <m2vaq1p5oi.wl-randy@psg.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/TjRZYXbd2N5dUPPwxBNgBsSRwwM>
Subject: Re: [Gen-art] [GROW] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 08:52:16 -0000

On 19/04/2017 02:06, Randy Bush wrote:
>>> 5.  Security Considerations
>>>
>>>     Operators should note the recommendations in Section 11 of BGP
>>>     Operations and Security [RFC7454].
>>>
>>> SB> You do not address the question of whether there are new
>>> SB> considerations, or considerations that are of increased importance?
>> It is my understanding that RFC 8092 "BGP Large Communities" are just
>> like RFC 1997 "BGP Communities", but ...  larger (for lack of better
>> words). Referencing RFC 7454 seems plenteous.
>>
>> So, what if there are not any additional considerations, If there were,
>> they would've been (or are) covered in RFC 8092's security section,
>> right?
>>
>> This is an Internet-Draft targetted for Informational status, I'm not
>> sure what you expect here.
>>
>>> SB> Is there is text somewhere that discusses the integrity and
>>> SB> synchronization of the parameters and any consequences that arise?
>> the what now? Can you elaborate on the above?
> you're supposed to guess
>
> the normal hack here is
>
>    this document introduces no new security issues beyond those discussed
>    in 1997

Guessing is horrible, but if that is what you do, that is what you do, 
and if the risks are the accepted norm in the BGP
community I am fine.

Is corruption (deliberate or otherwise) of the community strings 
something that BGPsec will address?

- Stewart


From nobody Wed Apr 19 01:55:22 2017
Return-Path: <randy@psg.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5CDA7131585; Wed, 19 Apr 2017 01:55: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 lXUOhXgiH8BY; Wed, 19 Apr 2017 01:55: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 6103813158F; Wed, 19 Apr 2017 01:55: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 1d0lOI-0002pN-OT; Wed, 19 Apr 2017 08:55:11 +0000
Date: Wed, 19 Apr 2017 17:55:07 +0900
Message-ID: <m237d493pw.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Job Snijders <job@instituut.net>, gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
In-Reply-To: <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <m2vaq1p5oi.wl-randy@psg.com> <1c121aaf-fae7-94ec-71ae-7ac618d86f31@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/gen-art/x3SSZB-xnjwTucxjSThQeIUyOPc>
Subject: Re: [Gen-art] [GROW] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 08:55:14 -0000

>> you're supposed to guess
>> 
>> the normal hack here is
>> 
>>    this document introduces no new security issues beyond those discussed
>>    in 1997
> 
> Guessing is horrible, but if that is what you do, that is what you do,
> and if the risks are the accepted norm in the BGP community I am fine.

i meant that, instead of being specific, you left it to the authors to
guess what you wanted.

> Is corruption (deliberate or otherwise) of the community strings
> something that BGPsec will address?

no.  bgpsec does not sign over communities.  this is because hops may
validly remove them, thus invalidating signatures.

randy


From nobody Wed Apr 19 02:27:59 2017
Return-Path: <nick@foobar.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD5781315A7; Wed, 19 Apr 2017 02:27: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, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NjrcPVK4OZgK; Wed, 19 Apr 2017 02:27:56 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 586441292D3; Wed, 19 Apr 2017 02:27:56 -0700 (PDT)
X-Envelope-To: draft-ietf-grow-large-communities-usage.all@ietf.org
Received: from cupcake.local ([194.88.241.232]) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v3J9RpJO048586 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 19 Apr 2017 10:27:52 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host [194.88.241.232] claimed to be cupcake.local
Message-ID: <58F72D8F.6020106@foobar.org>
Date: Wed, 19 Apr 2017 12:27:43 +0300
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.12 (Macintosh/20170323)
MIME-Version: 1.0
To: Stewart Bryant <stewart.bryant@gmail.com>
CC: Randy Bush <randy@psg.com>, Job Snijders <job@instituut.net>, gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <m2vaq1p5oi.wl-randy@psg.com> <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
In-Reply-To: <1c121aaf-fae7-94ec-71ae-7ac618d86f31@gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/K-rki6E1ZuHwGDIp3pfOqwd9jfg>
Subject: Re: [Gen-art] [GROW] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 09:27:58 -0000

Stewart Bryant wrote:
> Guessing is horrible, but if that is what you do, that is what you do,
> and if the risks are the accepted norm in the BGP
> community I am fine.

there's a general understanding out there that if you're directly
connect to $asn, you can somewhat believe $asn:* or $asn:*:*
communities, assuming you trust the remote ASN. Otherwise all bets are off.

Nick


From nobody Wed Apr 19 06:37:53 2017
Return-Path: <randy@psg.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1A2F1293F4; Wed, 19 Apr 2017 06:37:51 -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 Gl1jzugwCKd0; Wed, 19 Apr 2017 06:37:50 -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 68249127275; Wed, 19 Apr 2017 06:37:50 -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 1d0pnn-0004HA-RV; Wed, 19 Apr 2017 13:37:48 +0000
Date: Wed, 19 Apr 2017 22:37:45 +0900
Message-ID: <m2bmrs7c2e.wl-randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: Job Snijders <job@instituut.net>, gen-art@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, grow@ietf.org, ietf@ietf.org
In-Reply-To: <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <21c205d9-eac4-9403-8450-6bce56b3bfe6@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/gen-art/VGZYxV7ahGF4MinAAoZ3djLvJS0>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 13:37:51 -0000

> I was wondering if there was more scope to make mischief at a distance
> in a less less obvious way than before.

there isn't

but where were you when the blackhole community was passed?

> So you rely on the nodes that receive these community strings to
> interpret them in a common way.

no.  as with bgp communities since they were handed down to us by our
mothers, unless specified in some other document, there is no assumption
that all apply the same semantic to the same syntax.

randy


From nobody Wed Apr 19 07:19:04 2017
Return-Path: <job@instituut.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D7521296CD for <gen-art@ietfa.amsl.com>; Wed, 19 Apr 2017 07:18:49 -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=instituut-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 zHH4hUGpMZeP for <gen-art@ietfa.amsl.com>; Wed, 19 Apr 2017 07:18:48 -0700 (PDT)
Received: from mail-wr0-x22f.google.com (mail-wr0-x22f.google.com [IPv6:2a00:1450:400c:c0c::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47BF3129AA2 for <gen-art@ietf.org>; Wed, 19 Apr 2017 07:18:45 -0700 (PDT)
Received: by mail-wr0-x22f.google.com with SMTP id c55so16577526wrc.3 for <gen-art@ietf.org>; Wed, 19 Apr 2017 07:18:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=6f/MLbmZcIGt0635Dmfko5kO55hiUY0E1UeOldlQ1Gc=; b=VIhUD1GBPSI1iKiZ2vM0X2jhTeS3O3vKWSVhTQXGZUB8XTh9G8p/FUOyIMlagSN/3P PCbJxePkEzigdXhFn70Z/m2pL4ZCtibfNXK6Iar3DMedwFDOMCYzBS9gYa/bPNSF1vTw jBe+ryP/ujtppIGcuwOBjUuQDp+QfJgc/9iu7CrlqZ2UCPc7Gj1oWwVTn4SqN3IVE82x IP8NtOubJ6S7DB9wBXLyz5W1XkQs7n92eVJiJq8DWp32vfvVO7WrIaRTTNEiWLxO+q3J NlI98im97rAYrlzk6UhSgceOE1ECSVoPBEIY2YmFJBYhapGp87VDLv3EJJurgUUjuMSL +WPg==
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=6f/MLbmZcIGt0635Dmfko5kO55hiUY0E1UeOldlQ1Gc=; b=NtVkzLbQ9HTrEPrvFgr0OTIad4B29WDeudatdPoaoXjnyvpTfU2B/ibrablCsAFxL6 cWm9OlYFdqYKhkB4VrIAk1aP5b+NRvDbGI5pZ7fk/FxKtGniFan7hJl01STdrhoK/gFb hLejt6HbXArSll5AjeewQpcluBK33+4hdDRYgSwBP7J/3MbTgla0deaRXTQzM59T1JhS 5e83e2raWcb0KEhbn2VVr21T5ssoJJ9C2LfPxqiHzddc5zDWyiW5DtFQzNvmceR3rIR6 sgDwPffS/90GLrPB3g6Fk+HW58UYMUB/GHh+AcBwZCrL0adLdgXnah8dpmoSv63MSBVU S2Zw==
X-Gm-Message-State: AN3rC/5H6sHc7g5fsGCSqNk7YyRqt40CBmnaAHO6k3niQ+xfOwaLfMpe fvS0lC7RFk0oxg==
X-Received: by 10.223.130.212 with SMTP id 78mr2970192wrc.106.1492611523758; Wed, 19 Apr 2017 07:18:43 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:1558:83a0:4ae5:75f7]) by smtp.gmail.com with ESMTPSA id d10sm3498962wrd.54.2017.04.19.07.18.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 07:18:42 -0700 (PDT)
Date: Wed, 19 Apr 2017 16:18:41 +0200
From: Job Snijders <job@instituut.net>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Message-ID: <20170419141841.5agsblcuiqvyxek4@Vurt.local>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/K0NXSyoJLpFx7fMdjO0H2BXfViY>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 14:18:49 -0000

On Wed, Apr 19, 2017 at 09:46:53AM +0100, Stewart Bryant wrote:
> > >     Operations and Security [RFC7454].
> > > 
> > > SB> You do not address the question of whether there are new
> > > SB> considerations, or considerations that are of increased importance?
> > 
> > It is my understanding that RFC 8092 "BGP Large Communities" are
> > just like RFC 1997 "BGP Communities", but ...  larger (for lack of
> > better words). Referencing RFC 7454 seems plenteous.
> > 
> > So, what if there are not any additional considerations, If there
> > were, they would've been (or are) covered in RFC 8092's security
> > section, right?
> > 
> > This is an Internet-Draft targetted for Informational status, I'm
> > not sure what you expect here.
>
> I was wondering if there was more scope to make mischief at a distance
> in a less less obvious way than before.
> 
> If everyone is happy that there is no additional risk then I am fine,
> but seems to me the more knobs you give the mischeif maker to turn the
> more security risks you have.

Ah, I see now. This document does not create new knobs. RFC 8092
definded the BGP Large Community attribute, and this internet-draft
reflects on possible use cases, much like RFC 1998 was a companion for
RFC 1997.

> > > SB> Is there is text somewhere that discusses the integrity and
> > > SB> synchronization of the parameters and any consequences that arise?
> >
> > the what now? Can you elaborate on the above?
>
> So you rely on the nodes that receive these community strings to
> interpret them in a common way. Maybe this is an already solved
> problem, or an known risk, but what if the dictionaries get out of
> sync?

Yes, there is not anything novel here. How to keep a list of integers
like UN M.49 up to date (or how to write bug-free software) is out of
scope for this internet draft. ;-)

Deploy coherent routing policy configurations on an autonomous
system-wide level is not for this document to cover.

Kind regards,

Job


From nobody Wed Apr 19 07:54:20 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58A3F129AC9; Wed, 19 Apr 2017 07:54: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, 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 JyL6cKcLQggt; Wed, 19 Apr 2017 07:54:11 -0700 (PDT)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::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 A07FE129AC4; Wed, 19 Apr 2017 07:54:10 -0700 (PDT)
Received: by mail-wr0-x22b.google.com with SMTP id z109so17367484wrb.1; Wed, 19 Apr 2017 07:54:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=g5s24NlMTYgrKxKepXovDtryOUxF0WN0Cpl3Vv+C0Sk=; b=r9QUxQk52Eqp05KuZRWFW21MNJtK4PEpzAvg/ArI1OTEbC0aUYKFeLGOsF0PFcoYfB MPcIsqcm/v56uCUJTrMyxo7wg6FN4ocBMxndhqaJZaZRwogEB8KH/39ZQwBy1OmFKYSK sg972JWRhfC4pA/sAYduXa8OUjNGZpRxp4lDn4Wjq7FtVWTeFUBB0Bz6T8XLmpFfkg3L E4HdZPfvCx0mJgpCj55s67jFSAYDd2jZ5os9nigY9H+e09fvoRCj6y22JQMEPAdIrp0r cs1XVbxIRo2uV19oL3Q8MRKTH3WgFYdqqOfxgezBehcLcbh2iuvl+ySspTzQaiidzanz sCsQ==
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=g5s24NlMTYgrKxKepXovDtryOUxF0WN0Cpl3Vv+C0Sk=; b=HqnWalPjklSm2N64pttEmnOqj41GnpNBTZKY+yBo3D6EqfgjTQg8lvrhhNKWNVLSlk G+vdI2KfoJKmgPfJu9iyMXFKbbSGb16kb9dfmq0SaafQI58S4P7PVXEfFZee+FGZOKnq JF/JImIhTnsl/ponNpC2fduGPlnXj0FjijxMYtJob9U6Rb9Wx+QQT+xWqkdfaOOaXN4v dQwupIkXg9DqKMdTOcxWByWAdyf9Q0NltEvM1R6C58YnPuthEktFKkO3XyKx1zWbt38K ymUdvlnvzcxbqMVN88pP7WJxXjeVmAsuc2eL/acsREABJkA//xRyMU0JbCjdT/jXOBNE 0WfQ==
X-Gm-Message-State: AN3rC/5iva/42V8/2qKWusQcmHpqjq0ZyDqAQvt8tnOp6Klp9hEhRTcs YmVByHaHU7zMLA==
X-Received: by 10.223.150.121 with SMTP id c54mr3130046wra.202.1492613649035;  Wed, 19 Apr 2017 07:54:09 -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 h199sm13062217wme.4.2017.04.19.07.54.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 07:54:08 -0700 (PDT)
To: Job Snijders <job@instituut.net>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com> <20170419141841.5agsblcuiqvyxek4@Vurt.local>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <63963b8c-6e76-b59f-1af2-45dcc68c5422@gmail.com>
Date: Wed, 19 Apr 2017 15:54:06 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <20170419141841.5agsblcuiqvyxek4@Vurt.local>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/sSfQpCDzkgYqc3jP1y1QjkOxhBo>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 14:54:12 -0000

Thanks

I think I have done the required Genart level of due diligence on Security.

Stewart

On 19/04/2017 15:18, Job Snijders wrote:
> On Wed, Apr 19, 2017 at 09:46:53AM +0100, Stewart Bryant wrote:
>>>>      Operations and Security [RFC7454].
>>>>
>>>> SB> You do not address the question of whether there are new
>>>> SB> considerations, or considerations that are of increased importance?
>>> It is my understanding that RFC 8092 "BGP Large Communities" are
>>> just like RFC 1997 "BGP Communities", but ...  larger (for lack of
>>> better words). Referencing RFC 7454 seems plenteous.
>>>
>>> So, what if there are not any additional considerations, If there
>>> were, they would've been (or are) covered in RFC 8092's security
>>> section, right?
>>>
>>> This is an Internet-Draft targetted for Informational status, I'm
>>> not sure what you expect here.
>> I was wondering if there was more scope to make mischief at a distance
>> in a less less obvious way than before.
>>
>> If everyone is happy that there is no additional risk then I am fine,
>> but seems to me the more knobs you give the mischeif maker to turn the
>> more security risks you have.
> Ah, I see now. This document does not create new knobs. RFC 8092
> definded the BGP Large Community attribute, and this internet-draft
> reflects on possible use cases, much like RFC 1998 was a companion for
> RFC 1997.
>
>>>> SB> Is there is text somewhere that discusses the integrity and
>>>> SB> synchronization of the parameters and any consequences that arise?
>>> the what now? Can you elaborate on the above?
>> So you rely on the nodes that receive these community strings to
>> interpret them in a common way. Maybe this is an already solved
>> problem, or an known risk, but what if the dictionaries get out of
>> sync?
> Yes, there is not anything novel here. How to keep a list of integers
> like UN M.49 up to date (or how to write bug-free software) is out of
> scope for this internet draft. ;-)
>
> Deploy coherent routing policy configurations on an autonomous
> system-wide level is not for this document to cover.
>
> Kind regards,
>
> Job


From nobody Wed Apr 19 07:58:21 2017
Return-Path: <job@instituut.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63E17129ADE for <gen-art@ietfa.amsl.com>; Wed, 19 Apr 2017 07:58:06 -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=instituut-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 COPdd3Lk7yqv for <gen-art@ietfa.amsl.com>; Wed, 19 Apr 2017 07:58:05 -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 C85D1129AE0 for <gen-art@ietf.org>; Wed, 19 Apr 2017 07:58:03 -0700 (PDT)
Received: by mail-wm0-x22d.google.com with SMTP id o81so82314234wmb.1 for <gen-art@ietf.org>; Wed, 19 Apr 2017 07:58:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=sc4106xRtU0hgDKmgSRewO1J4wd551XL6qIrTHHTK/s=; b=U1PZy+mlmDILpYfo/sB2grp+xs5NWIl9X2KV6Fv3KPus+bmjndOZwFIPrib4M2rHfU OaZOpAGNHoOVzxPJnntzJ1N+rAJ7Qov7NU9JUcKdvZ1dLLPMtErYb3VtTkWL9FyJvR6J KmoDA26/BN3Ya1oI1LfMJEzE6zbERiex2glzze8V+tXvZupUAi4h6alnGyBS2iKhxAgU xjFiffkcPmlGD8bfzcsEN+xGesahqzVgCLazf3IqdzY5oJ06RHqoh4GBAj9AkjAzaqMB Ds+oSLNCP36ENhujua9Yw4DmFM54cPT+yrS2oNk6Z7jocYHciZrA/oFVv5kzctHFI1Qq p2aQ==
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=sc4106xRtU0hgDKmgSRewO1J4wd551XL6qIrTHHTK/s=; b=mXgc8ltM71SiETyAEWkXZMpcL5u3uUWzYhMojsRm4+NJ554SdAqyPTlexOadejXuKZ POg2OELYl6AEyA1sYfYqWLzhWSk3bzkDfK2OWQlDAfHwS36QMoxU2DFZcH7DKv3C2YPv Aewh10e+1HPjd8rs4og7o3UTigzlXYLRQWza1PQxSKqHg42VzErmQM/exOQi1KoAfvBl CN7xyY9/pGyv6XuDBeJOQRXPvxFTQSYJMcJPCWJyk6/irNt3CJrCnFNUpANcBgomZqsh p+wkvKyZ/CH21LX4ADjM2XzINl9KZ+Sv+fR8w9ZoSWZW49cx8q1gaLQMmhpMRN3RbuYG Njog==
X-Gm-Message-State: AN3rC/4sB9cHWHNIq9HQeCnCZTCCh5fIrr/2+LkBYRccfbfjRv9QcRjF fWPLLksb5HZWyA==
X-Received: by 10.28.128.197 with SMTP id b188mr17478718wmd.115.1492613882182;  Wed, 19 Apr 2017 07:58:02 -0700 (PDT)
Received: from localhost ([2001:67c:208c:10:1558:83a0:4ae5:75f7]) by smtp.gmail.com with ESMTPSA id 3sm3650231wrv.33.2017.04.19.07.58.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 19 Apr 2017 07:58:01 -0700 (PDT)
Date: Wed, 19 Apr 2017 16:58:00 +0200
From: Job Snijders <job@instituut.net>
To: Stewart Bryant <stewart.bryant@gmail.com>
Cc: gen-art@ietf.org, grow@ietf.org, draft-ietf-grow-large-communities-usage.all@ietf.org, ietf@ietf.org
Message-ID: <20170419145800.nwczhjy5lzygpaqp@Vurt.local>
References: <149252287543.16134.18005737444773296286@ietfa.amsl.com> <20170418235858.sgsa64r7b5th7zam@Vurt.local> <21c205d9-eac4-9403-8450-6bce56b3bfe6@gmail.com> <20170419141841.5agsblcuiqvyxek4@Vurt.local> <63963b8c-6e76-b59f-1af2-45dcc68c5422@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <63963b8c-6e76-b59f-1af2-45dcc68c5422@gmail.com>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: NeoMutt/20170306 (1.8.0)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/5i0uisWFBm1Ri-mNJC4VEU3IYQM>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-grow-large-communities-usage-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 14:58:06 -0000

On Wed, Apr 19, 2017 at 03:54:06PM +0100, Stewart Bryant wrote:
> Thanks
> 
> I think I have done the required Genart level of due diligence on
> Security.

Much appreciated, stay tuned for an updated version which incorporates
your feedback.

Kind regards,

Job


From nobody Wed Apr 19 12:57:18 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5755D128D40 for <gen-art@ietf.org>; Wed, 19 Apr 2017 12:57:17 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-to: mahoney@nostrum.com
Message-ID: <149263183726.19272.12882158523579470910.idtracker@ietfa.amsl.com>
Date: Wed, 19 Apr 2017 12:57:17 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/vwL_MBeHa5ct6qkZmOdpJ-UI31k>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Apr 2017 19:57:17 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-04-27

Reviewer               Type      LC end     Draft
Stewart Bryant         Telechat  2017-03-01 draft-ietf-6man-rfc1981bis-06 *
Francis Dupont         Telechat  2017-04-18 draft-ietf-ipsecme-tcp-encaps-09 *
Paul Kyzivat           Telechat  2017-03-10 draft-bchv-rfc6890bis-06 *
Matthew Miller         Telechat  2017-04-07 draft-ietf-rtgwg-yang-key-chain-20 *
Dale Worley            Telechat  2017-03-22 draft-ietf-i2nsf-problem-and-use-cases-12 *
Lucy Yong              Telechat  None       draft-ietf-isis-l2bundles-04

Last calls:

Reviewer               Type      LC end     Draft
Elwyn Davies           Last Call 2017-04-21 draft-ietf-core-links-json-07
Vijay Gurbani          Last Call 2017-04-20 draft-ietf-avtcore-rfc5285-bis-09
Robert Sparks          Last Call 2017-05-02 draft-ietf-bmwg-ipv6-tran-tech-benchmarking-06

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Peter Yee
  Lucy Yong
  Jari Arkko
  Stewart Bryant
  Brian Carpenter
  Elwyn Davies
  Ralph Droms
  Francis Dupont
  Roni Even
  Fernando Gont

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Thu Apr 20 11:14:41 2017
Return-Path: <Brian.Raymor@microsoft.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97A83129446 for <gen-art@ietfa.amsl.com>; Thu, 20 Apr 2017 11:14:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level: 
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 gBqKsiWBbxTG for <gen-art@ietfa.amsl.com>; Thu, 20 Apr 2017 11:14:37 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0119.outbound.protection.outlook.com [104.47.36.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 4D1C1126C25 for <gen-art@ietf.org>; Thu, 20 Apr 2017 11:14: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=Lu+IDveaJ8fTJclgIrry86cl2GnNyC/Fk+g6wn8IK2c=; b=kCPhv1Lkdm5/35gEd0/IrM/VsXaUtG+JJWPvD72dRBFs5TNFkQdL2XZFcEY0gFj1zoFvXjseR2bqvTlPpYXzqT5BwVNu+JWpg86iN1FyOnQ+7e2H5kbfnwdve9qgcXMAC67sBZbIbs/psNibDN/tTJrpi/mm5pmbttCjTs4gqeo=
Received: from BY2PR21MB0084.namprd21.prod.outlook.com (10.162.78.141) by BY2PR21MB0083.namprd21.prod.outlook.com (10.162.78.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1061.1; Thu, 20 Apr 2017 18:14:35 +0000
Received: from BY2PR21MB0084.namprd21.prod.outlook.com ([10.162.78.141]) by BY2PR21MB0084.namprd21.prod.outlook.com ([10.162.78.141]) with mapi id 15.01.1061.003; Thu, 20 Apr 2017 18:14:36 +0000
From: Brian Raymor <Brian.Raymor@microsoft.com>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>, "draft-ietf-core-coap-tcp-tls.all@tools.ietf.org" <draft-ietf-core-coap-tcp-tls.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-core-coap-tcp-tls-07
Thread-Index: AdKxxgRKbG1uB6t+RkGgQFfE5vWQ3wIOngUw
Date: Thu, 20 Apr 2017 18:14:35 +0000
Message-ID: <BY2PR21MB00849A2926B7F6CAF35118A1831B0@BY2PR21MB0084.namprd21.prod.outlook.com>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A4F471630@eusaamb107.ericsson.se>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A4F471630@eusaamb107.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ericsson.com; dkim=none (message not signed) header.d=none; ericsson.com; dmarc=none action=none header.from=microsoft.com; 
x-originating-ip: [174.61.159.182]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR21MB0083; 7:HFHYaGuBjyzPba9so/z7YO1+x6xX+qLptJEpORgP35NpWDYVzHPN2bUA/Eh2O1NAbVVeRLZOuJWSJ469XyUUWeIWLKPwwWLDCC9o/gC9g3+hX5K6bcreBkNvC3PXJ/1sPdzAjRU9KjbVGe+QOrqc2yNt/PslidqZE9bSiQHxeEDS0mG6nzBYF4MGIq8YkfUzTtgkoWUwNFwtMBYAh3XPXluZ1uyiPtCXTjLM5D+t9tOJ67UORAp4sijOzD4qc52wuffjqxwnhRt6D+IKMweEOpXqUHWuzUt8uF5RyLX3yBhRHK3g0RnCLbsFYUVqs3qpND97iizdvbyfWU1MEFNV3iBEC0EIX6n9YzouyewLZSw=
x-ms-office365-filtering-correlation-id: 710a1588-0d5f-4a4a-ba62-08d488191a2b
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081)(201702281549075); SRVR:BY2PR21MB0083; 
x-microsoft-antispam-prvs: <BY2PR21MB0083E7069CB50E7364E5C335831B0@BY2PR21MB0083.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(6055026)(61426038)(61427038)(6041248)(20161123562025)(20161123555025)(20161123558043)(201703131423075)(201702281528075)(201703061421075)(201703061406096)(20161123564025)(20161123560025)(6072148); SRVR:BY2PR21MB0083; BCL:0; PCL:0; RULEID:; SRVR:BY2PR21MB0083; 
x-forefront-prvs: 02830F0362
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39840400002)(39410400002)(39450400003)(39860400002)(39850400002)(39400400002)(230783001)(33656002)(77096006)(2201001)(8990500004)(10090500001)(5005710100001)(189998001)(2501003)(122556002)(10290500002)(86362001)(2906002)(3280700002)(3660700001)(76176999)(19609705001)(2900100001)(53936002)(54896002)(6246003)(790700001)(55016002)(74316002)(6116002)(50986999)(6506006)(66066001)(99286003)(38730400002)(25786009)(5660300001)(7696004)(2950100002)(102836003)(7736002)(8936002)(6306002)(81166006)(9686003)(8676002)(3846002)(229853002)(54356999); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR21MB0083; H:BY2PR21MB0084.namprd21.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY2PR21MB00849A2926B7F6CAF35118A1831B0BY2PR21MB0084namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2017 18:14:35.9024 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR21MB0083
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/-iR4ImsOVjk6Q2u-cVhwdvc3PEA>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-core-coap-tcp-tls-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 18:14:40 -0000

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



Thanks for your feedback.



> Nits/editorial comments:

> -Please spell out acronyms at first use.



I will correct the BERT case and also review https://www.rfc-editor.org/mat=
erials/abbrev.expansion.txt for other potential cases.



Tracked in https://github.com/core-wg/coap-tcp-tls/issues/132



> -Not sure if other documents address this, but does this document assume =
fixed CoAP devices

> as end point (not > moving and connectivity is assumed 'the same' during =
the TCP session?)



It assumes fixed CoAP devices.



...Brian




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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thanks for your feedback.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt; Nits/editorial comments: <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; -Please spell out acronyms at first use.<o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I will correct the BERT case and also review http=
s://www.rfc-editor.org/materials/abbrev.expansion.txt for other potential c=
ases.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Tracked in https://github.com/core-wg/coap-tcp-tl=
s/issues/132<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt; -Not sure if other documents address this, b=
ut does this document assume fixed CoAP devices<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; as end point (not &gt; moving and connectivi=
ty is assumed 'the same' during the TCP session?)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">It assumes fixed CoAP devices.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&#8230;Brian<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_BY2PR21MB00849A2926B7F6CAF35118A1831B0BY2PR21MB0084namp_--


From nobody Thu Apr 20 14:43:37 2017
Return-Path: <meral.shirazipour@ericsson.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC5241316C0 for <gen-art@ietfa.amsl.com>; Thu, 20 Apr 2017 14:43:35 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BwPYNK_H53Qw for <gen-art@ietfa.amsl.com>; Thu, 20 Apr 2017 14:43:33 -0700 (PDT)
Received: from usplmg20.ericsson.net (usplmg20.ericsson.net [198.24.6.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 60994129C71 for <gen-art@ietf.org>; Thu, 20 Apr 2017 14:43:33 -0700 (PDT)
X-AuditID: c618062d-767ff700000029b8-da-58f93df8319e
Received: from EUSAAHC004.ericsson.se (Unknown_Domain [147.117.188.84]) by  (Symantec Mail Security) with SMTP id 04.56.10680.8FD39F85; Fri, 21 Apr 2017 01:02:19 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC004.ericsson.se ([147.117.188.84]) with mapi id 14.03.0319.002; Thu, 20 Apr 2017 17:43:27 -0400
From: Meral Shirazipour <meral.shirazipour@ericsson.com>
To: Brian Raymor <Brian.Raymor@microsoft.com>, "draft-ietf-core-coap-tcp-tls.all@tools.ietf.org" <draft-ietf-core-coap-tcp-tls.all@tools.ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>
Thread-Topic: Gen-ART Last Call review of draft-ietf-core-coap-tcp-tls-07
Thread-Index: AdKxxgRKbG1uB6t+RkGgQFfE5vWQ3wIOngUwAAesEqA=
Date: Thu, 20 Apr 2017 21:43:26 +0000
Message-ID: <ABCAA4EF18F17B4FB619EA93DEF7939A4F4851C4@eusaamb107.ericsson.se>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A4F471630@eusaamb107.ericsson.se> <BY2PR21MB00849A2926B7F6CAF35118A1831B0@BY2PR21MB0084.namprd21.prod.outlook.com>
In-Reply-To: <BY2PR21MB00849A2926B7F6CAF35118A1831B0@BY2PR21MB0084.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.10]
Content-Type: multipart/alternative; boundary="_000_ABCAA4EF18F17B4FB619EA93DEF7939A4F4851C4eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplkeLIzCtJLcpLzFFi42KZXLonRPe37c8Ig9d/WSzuz3vEZNE64TOr xdVXn1kcmD2WLPnJ5NG64y+7x5fLn9kCmKO4bFJSczLLUov07RK4Mh5cqCo4ZVDRPGk2awPj N60uRk4OCQETiY7JP9lBbCGBDYwS73f7dTFyAdnLGSU63n1kAkmwCVhIbP/9nBUkISKwn1Fi 0dHdYAlhAQ+J3Wsvg9kiAp4Sa262QdlWEnfuLGUEsVkEVCUW/XjCAmLzCvhKbJneC7VtAaPE v8OKIDanQKzEr/kdbCA2o4CYxPdTa8DmMAuIS9x6Mp8J4lIBiSV7zjND2KISLx//Y4WwlSQm LT3HClGfL7Fi0Q9miF2CEidnPmGZwCg8C8moWUjKZiEpg4jrSCzY/YkNwtaWWLbwNTOMfebA YyZk8QWM7KsYOUqLC3Jy040MNjECI+eYBJvuDsb70z0PMQpwMCrx8D7Y9yNCiDWxrLgy9xCj BAezkgivsOjPCCHelMTKqtSi/Pii0pzU4kOM0hwsSuK8E85fiBASSE8sSc1OTS1ILYLJMnFw SjUwzraLjTJ+Ydm+fMIN9/kLfnvtbLphd0LEsHEeoz7rlfiA2tg91/cENYtO3hv0auKS6VHT voc65t3jMK/54CXw2iiCw07oXOOsxyYXJv56pHHC8KlpuOPOijvBG1cptZ3oPTid52eskOI6 BYYtVak7CzZOeJr/9u7C8GeyuzLD3O9u/KTcadDQo8RSnJFoqMVcVJwIAOKwuyuYAgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/U0MhKQaMgPf0DXV2wu3zS7OmOBA>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-core-coap-tcp-tls-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 21:43:36 -0000

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

Hi,
  Thank you.

Best,
Meral

From: Brian Raymor [mailto:Brian.Raymor@microsoft.com]
Sent: Thursday, April 20, 2017 11:15 AM
To: Meral Shirazipour <meral.shirazipour@ericsson.com>; draft-ietf-core-coa=
p-tcp-tls.all@tools.ietf.org; gen-art@ietf.org
Subject: RE: Gen-ART Last Call review of draft-ietf-core-coap-tcp-tls-07



Thanks for your feedback.



> Nits/editorial comments:

> -Please spell out acronyms at first use.



I will correct the BERT case and also review https://www.rfc-editor.org/mat=
erials/abbrev.expansion.txt for other potential cases.



Tracked in https://github.com/core-wg/coap-tcp-tls/issues/132



> -Not sure if other documents address this, but does this document assume =
fixed CoAP devices

> as end point (not > moving and connectivity is assumed 'the same' during =
the TCP session?)



It assumes fixed CoAP devices.



...Brian




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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.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><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; Thank you.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Best,<o:p></o:p></p>
<p class=3D"MsoNormal">Meral<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Brian Raymor [mailto:Brian.Raymor@micro=
soft.com]
<br>
<b>Sent:</b> Thursday, April 20, 2017 11:15 AM<br>
<b>To:</b> Meral Shirazipour &lt;meral.shirazipour@ericsson.com&gt;; draft-=
ietf-core-coap-tcp-tls.all@tools.ietf.org; gen-art@ietf.org<br>
<b>Subject:</b> RE: Gen-ART Last Call review of draft-ietf-core-coap-tcp-tl=
s-07<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Thanks for your feedback.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt; Nits/editorial comments: <o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; -Please spell out acronyms at first use.<o:p=
></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I will correct the BERT case and also review <a h=
ref=3D"https://www.rfc-editor.org/materials/abbrev.expansion.txt">
https://www.rfc-editor.org/materials/abbrev.expansion.txt</a> for other pot=
ential cases.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Tracked in <a href=3D"https://github.com/core-wg/=
coap-tcp-tls/issues/132">
https://github.com/core-wg/coap-tcp-tls/issues/132</a><o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&gt; -Not sure if other documents address this, b=
ut does this document assume fixed CoAP devices<o:p></o:p></p>
<p class=3D"MsoPlainText">&gt; as end point (not &gt; moving and connectivi=
ty is assumed 'the same' during the TCP session?)<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">It assumes fixed CoAP devices.<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&#8230;Brian<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
</body>
</html>

--_000_ABCAA4EF18F17B4FB619EA93DEF7939A4F4851C4eusaamb107erics_--


From nobody Thu Apr 20 16:35:25 2017
Return-Path: <Henning.Schulzrinne@fcc.gov>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0DFEB129BBD; Thu, 20 Apr 2017 16:35:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fccoffice.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 u4kH07lFe4tQ; Thu, 20 Apr 2017 16:35:21 -0700 (PDT)
Received: from mx0b-0024ed01.pphosted.com (mx0b-0024ed01.pphosted.com [148.163.153.198]) (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 85B11129B75; Thu, 20 Apr 2017 16:35:21 -0700 (PDT)
Received: from pps.filterd (m0102174.ppops.net [127.0.0.1]) by mx0b-0024ed01.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v3KNZHRt005226; Thu, 20 Apr 2017 23:35:17 GMT
Received: from gcc01-dm2-obe.outbound.protection.outlook.com (mail-dm2gcc01lp0056.outbound.protection.outlook.com [23.103.198.56]) by mx0b-0024ed01.pphosted.com with ESMTP id 29wqpe9qhg-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 20 Apr 2017 23:35:17 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fccoffice.onmicrosoft.com; s=selector1-fcc-gov; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=cT/p4kNmjuakHzCvMpKfn/S5Lqj9tsgvVNVbESH5/Ks=; b=sXC/HsxJGuFps6k6lA3l3X0uATNMTAhJ925uNrRBtwWJN34Ted/4nCiZDn/N9Xk4xDfhgbPct4jLhNSM03iEaO/kSJJJw36jFBuDOpmUACH9hBiMI3BGPQzFmar8ubJ8uEwfRj78Km9wxOGG+DVdv1356sDXyaeXPZVi0ZEfbZo=
Received: from CY1PR09MB0634.namprd09.prod.outlook.com (10.160.151.21) by CY1PR09MB0636.namprd09.prod.outlook.com (10.160.151.23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1034.10; Thu, 20 Apr 2017 23:35:16 +0000
Received: from CY1PR09MB0634.namprd09.prod.outlook.com ([10.160.151.21]) by CY1PR09MB0634.namprd09.prod.outlook.com ([10.160.151.21]) with mapi id 15.01.1034.018; Thu, 20 Apr 2017 23:35:16 +0000
From: Henning Schulzrinne <Henning.Schulzrinne@fcc.gov>
To: Peter Yee <peter@akayla.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "sipcore@ietf.org" <sipcore@ietf.org>, "draft-ietf-sipcore-status-unwanted.all@ietf.org" <draft-ietf-sipcore-status-unwanted.all@ietf.org>
Thread-Topic: Review of draft-ietf-sipcore-status-unwanted-04
Thread-Index: AQHSor6bOa15gxoBWk6pbW5i+wNrkKHPEZ67
Date: Thu, 20 Apr 2017 23:35:15 +0000
Message-ID: <CY1PR09MB0634018DB677B3D60B82AF84EA1B0@CY1PR09MB0634.namprd09.prod.outlook.com>
References: <149015426220.3518.3546300688917567228@ietfa.amsl.com>
In-Reply-To: <149015426220.3518.3546300688917567228@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=fcc.gov;
x-originating-ip: [172.56.3.117]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; CY1PR09MB0636; 7:vg5JZ6KS8IOaAiVnZl1tsL4kesizWSXmF9+zHmRq8YY0JLMgZ4VWq5OLO0v8HvQydbobclJT3/Lxlz8v/i88EqyQiByD6yuve4QbTHYYWdgEnNH+LHtYG8/0hCto2A68Qy+YN7lxokMmQwS5tnFCK3piT0ccgtXrsv71Q3rtutWGA4nwHVrl7Qgmt97pI7BCs0TKTlGOWLTfi3N2qTuAOu2tNEU46Ok75bolM47k3fv83bvr95wxAtbB3shB+D8pcBQr2yP/yZ2I2aU3jVkYGmaJUa2v6jpo3/Ye372aUh7yfXfhcaMlueBtMITLgkV2Ihic6iWeMCZcnFj3CymHrQ==
x-ms-office365-filtering-correlation-id: ada04fe3-f616-488d-207a-08d48845e616
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:CY1PR09MB0636; 
x-microsoft-antispam-prvs: <CY1PR09MB0636474D7E439CE503745243EA1B0@CY1PR09MB0636.namprd09.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(6041248)(20161123564025)(20161123560025)(20161123562025)(201703131423075)(201702281528075)(201703061421075)(20161123555025)(6072148); SRVR:CY1PR09MB0636; BCL:0; PCL:0; RULEID:; SRVR:CY1PR09MB0636; 
x-forefront-prvs: 02830F0362
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39410400002)(39840400002)(39400400002)(39450400003)(377454003)(377424004)(6436002)(7696004)(6306002)(54896002)(229853002)(8676002)(2900100001)(76176999)(81166006)(53936002)(38730400002)(345774005)(5660300001)(9686003)(7736002)(54356999)(99286003)(54906002)(74316002)(236005)(733005)(8936002)(53546009)(50986999)(6506006)(66066001)(77096006)(4326008)(25786009)(55016002)(6246003)(19627405001)(3660700001)(3280700002)(189998001)(575784001)(86362001)(2501003)(2950100002)(6116002)(33656002)(122556002)(3846002)(102836003)(6606003)(230783001)(2906002)(18265965002); DIR:OUT; SFP:1102; SCL:1; SRVR:CY1PR09MB0636; H:CY1PR09MB0634.namprd09.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; 
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_CY1PR09MB0634018DB677B3D60B82AF84EA1B0CY1PR09MB0634namp_"
MIME-Version: 1.0
X-OriginatorOrg: fcc.gov
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Apr 2017 23:35:15.8061 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72970aed-3669-4ca8-b960-dd016bc72973
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR09MB0636
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-04-20_21:, , signatures=0
X-Proofpoint-Spam-Reason: safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ea1TIaRh1HG9YHM_n6s6tci6l9g>
Subject: Re: [Gen-art] Review of draft-ietf-sipcore-status-unwanted-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Apr 2017 23:35:24 -0000

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


Thank you for your comments. You have captured the spirit of the discussion=
 well [??]


I will be submitting an updated version soon, including your suggestions.


Henning

________________________________
From: Peter Yee <peter@akayla.com>
Sent: Tuesday, March 21, 2017 11:44:22 PM
To: gen-art@ietf.org
Cc: sipcore@ietf.org; ietf@ietf.org; draft-ietf-sipcore-status-unwanted.all=
@ietf.org
Subject: Review of draft-ietf-sipcore-status-unwanted-04

Reviewer: Peter Yee
Review result: Ready with Nits

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

For more information, please see the FAQ at

<https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__trac.ietf.org_trac_=
gen_wiki_GenArtfaq&d=3DDwICaQ&c=3Dy0h0omCe0jAUGr4gAQ02Fw&r=3DFJcVoDkWM5EiVc=
V0ReX8lDU1XeHIYRHfarpk4MK59RE&m=3DW4wBo6GdFdfpAg5ssVa_1afyCooA6uWETUt3nUwbQ=
Xw&s=3DUF7qskUlKSBGGMotRXuQPGcmFLyJIvmjjjiMNnXFdNQ&e=3D >.

Document: draft-ietf-sipcore-status-unwanted-04
Reviewer: Peter Yee
Review Date: 2017-03-21
IETF LC End Date: 2017-03-21
IESG Telechat date: Not scheduled for a telechat

Summary: This draft specifies a SIP response code for the callee to
indicate that the call is unwanted.  It goes to great lengths to
specify what may be done as a result of sending this response code,
all the while mandating nothing.

The document has a couple of nits, but nothing seriously wrong.
[Ready with nits]

Major issues: None

Minor issues: None

Nits/editorial comments:

Page 4, 1st full paragraph, 2nd sentence: I can't parse this sentence
as written.  It appears to be a list, but then has a clause (starting
at "based on") that doesn't fit neatly in the sequence.  Perhaps
inserting "and" before "based" would help.  Append "as" after "well".

Page 5, Section 6, 2nd paragraph, 1st sentence: change "extract" to
"exact".


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

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Arial,Helvetica,sans-serif;" dir=3D"ltr">
<p><br>
</p>
<meta content=3D"text/html; charset=3DUTF-8">
<div dir=3D"ltr">
<div id=3D"x_divtagdefaultwrapper" dir=3D"ltr" style=3D"font-size:12pt; col=
or:#000000; font-family:Calibri,Arial,Helvetica,sans-serif">
<p>Thank you for your comments. You have captured the spirit of the discuss=
ion well
<img class=3D"x_EmojiInsert" id=3D"OWAEmoji930739" alt=3D"&#55357;&#56842;"=
 style=3D"vertical-align: bottom; user-select: none;" src=3D"data:image/png=
;base64,iVBORw0KGgoAAAANSUhEUgAAABMAAAATCAYAAAByUDbMAAAAGXRFWHRTb2Z0d2FyZQB=
BZG9iZSBJbWFnZVJlYWR5ccllPAAAAYpJREFUeNpi/P//PwO1ACM2wf9njBWAVD4QBwCxApLUAy=
DeAMQTGU3OPkDRA3QUIxaD&#43;oFUAREOaQQa2IDTMKBB84FUAgk&#43;WwA0MBFmGBOaixJID=
KYEoD6465igBjkge&#43;3CrW94TUCTr4eGMdxl8TCZxMYHDIZR1xk2HPiA1SCQOEgepA4J5CMb=
FgAPhM1vwfTFW9&#43;xGgYTh6lD1s8IdKIAkH4PEz1w9jOYVpBiZ1CQZMMw7MHzXwwPnv0Esx2=
MeRESxmcYWYCUAbJiFAVYAMgCbJbAvPmAWjmACZqS4aHdOOs5wdgEBcWE5a8Y0HIGPAIOwETtjX=
kYJqIqxAAgeQM1ThTzkQ2biB5mC7a8xZ7kgeICvMzoYTsRJaMDY3U9chIBpaMHz34xxPsKgwMcF=
IsLgckB5KL&#43;YllkgyYAg6oQJW9Ck8h&#43;5NgFhd3GAx/humAGI2cGIHYEGvYBW0YHGTgf=
2YX4MjkQF4IMwlkEIeXVfByGwsqzAwTLMywGg7wNcvED9AIR3TCAAAMAqh&#43;p&#43;YMVeBQ=
AAAAASUVORK5CYII=3D"></p>
<p><br>
</p>
<p>I will be submitting an updated version soon, including your suggestions=
.</p>
<p><br>
</p>
<p>Henning</p>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" =
color=3D"#000000" style=3D"font-size:11pt"><b>From:</b> Peter Yee &lt;peter=
@akayla.com&gt;<br>
<b>Sent:</b> Tuesday, March 21, 2017 11:44:22 PM<br>
<b>To:</b> gen-art@ietf.org<br>
<b>Cc:</b> sipcore@ietf.org; ietf@ietf.org; draft-ietf-sipcore-status-unwan=
ted.all@ietf.org<br>
<b>Subject:</b> Review of draft-ietf-sipcore-status-unwanted-04</font>
<div>&nbsp;</div>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:10pt;">
<div class=3D"PlainText">Reviewer: Peter Yee<br>
Review result: Ready with Nits<br>
<br>
I am the assigned Gen-ART reviewer for this draft. The General Area<br>
Review Team (Gen-ART) reviews all IETF documents being processed<br>
by the IESG for the IETF Chair.&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""></a>https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A_=
_trac.ietf.org_trac_gen_wiki_GenArtfaq&amp;d=3DDwICaQ&amp;c=3Dy0h0omCe0jAUG=
r4gAQ02Fw&amp;r=3DFJcVoDkWM5EiVcV0ReX8lDU1XeHIYRHfarpk4MK59RE&amp;m=3DW4wBo=
6GdFdfpAg5ssVa_1afyCooA6uWETUt3nUwbQXw&amp;s=3DUF7qskUlKSBGGMotRXuQPGcmFLyJ=
IvmjjjiMNnXFdNQ&amp;e=3D
 &gt;.<br>
<br>
Document: draft-ietf-sipcore-status-unwanted-04<br>
Reviewer: Peter Yee<br>
Review Date: 2017-03-21<br>
IETF LC End Date: 2017-03-21<br>
IESG Telechat date: Not scheduled for a telechat<br>
<br>
Summary: This draft specifies a SIP response code for the callee to<br>
indicate that the call is unwanted.&nbsp; It goes to great lengths to<br>
specify what may be done as a result of sending this response code,<br>
all the while mandating nothing.<br>
<br>
The document has a couple of nits, but nothing seriously wrong. <br>
[Ready with nits]<br>
<br>
Major issues: None<br>
<br>
Minor issues: None<br>
<br>
Nits/editorial comments: <br>
<br>
Page 4, 1st full paragraph, 2nd sentence: I can't parse this sentence<br>
as written.&nbsp; It appears to be a list, but then has a clause (starting<=
br>
at &quot;based on&quot;) that doesn't fit neatly in the sequence.&nbsp; Per=
haps<br>
inserting &quot;and&quot; before &quot;based&quot; would help.&nbsp; Append=
 &quot;as&quot; after &quot;well&quot;.<br>
<br>
Page 5, Section 6, 2nd paragraph, 1st sentence: change &quot;extract&quot; =
to<br>
&quot;exact&quot;.<br>
<br>
</div>
</span></font></div>
</body>
</html>

--_000_CY1PR09MB0634018DB677B3D60B82AF84EA1B0CY1PR09MB0634namp_--


From nobody Sat Apr 22 12:23:29 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B45A1205F0 for <gen-art@ietfa.amsl.com>; Sat, 22 Apr 2017 12:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.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 Kbt58xtmrYis for <gen-art@ietfa.amsl.com>; Sat, 22 Apr 2017 12:23:26 -0700 (PDT)
Received: from resqmta-ch2-09v.sys.comcast.net (resqmta-ch2-09v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00468128854 for <gen-art@ietf.org>; Sat, 22 Apr 2017 12:23:25 -0700 (PDT)
Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-09v.sys.comcast.net with SMTP id 20cfd2XwfQe9c20cudvIIf; Sat, 22 Apr 2017 19:23:24 +0000
Received: from [192.168.1.110] ([24.62.227.142]) by resomta-ch2-10v.sys.comcast.net with SMTP id 20ctdUSKAX2Fj20ctdgrgB; Sat, 22 Apr 2017 19:23:24 +0000
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
To: draft-bchv-rfc6890bis.all@ietf.org
Cc: General Area Review Team <gen-art@ietf.org>
Message-ID: <48bebccb-4cf0-a218-38aa-af3fde41ad19@alum.mit.edu>
Date: Sat, 22 Apr 2017 15:23:22 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfPOhP1Txwc+Puf7JSP2xzUI5Y7syKq/0VN2GxCHAFHuhxbIJN3tWqjwHQ7voc3NCoePQyGoGDHwXkPKqS30wSYKK17jaHdGUHeiCqN7ORa19OE9jHwwB T1lWMwD5v5sWrz5tvdZNjq0rvq7R87wbyqN4EOa+1CNbRo0xWWkAJA+rvD+5gj0Ix5TsYqs6eBrCnpCUUQnfChYRpLKSqz0EH09H5FEdsuhItGf6nqE40pYK
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/8oBAETWtapdY8WJ2aM5KPz4HnVM>
Subject: [Gen-art]  Gen-ART Last Call review of draft-bchv-rfc6890bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Apr 2017 19:23:27 -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 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-bchv-rfc6890bis-06
Reviewer: Paul Kyzivat
Review Date: 2017-04-22
IETF LC End Date: 2017-03-10
IESG Telechat date: 2017-04-25

Summary:

This draft is basically ready for publication, but has nits that should 
be fixed before publication.

General Comments:

This version is *much* easier to understand than the -04 version that I 
previously reviewed.

Issues:

Major: 0
Minor: 0
Nits:  1

(1) Nit:

In section 2.3 the requested handling of footnotes is confusing.
IIUC, the intent is:

- add a new footnote between the existing [1] and [2];

- add a new footnote at the end after the existing [5];

- renumber the footnotes sequentially (from [1] to [7]);

- adjust all the existing footnote references to refer to the same
   footnote as previously, but using the new numbering;

- then, add references to the new footnotes [2] and [7] to the entries
   for TEREDO and Unique-Local.

It took me a few readings of the current text to convince myself that is 
what you intended. It would be better to be more explicit about it.


From nobody Sun Apr 23 19:04:32 2017
Return-Path: <worley@ariadne.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8751A127071; Sun, 23 Apr 2017 19:04: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: i2nsf@ietf.org, ietf@ietf.org, draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149299947052.25893.14183369388246516074@ietfa.amsl.com>
Date: Sun, 23 Apr 2017 19:04:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/sb05vONUcxu3wNHu7i4rk6DuLrM>
Subject: [Gen-art] Genart telechat review of draft-ietf-i2nsf-problem-and-use-cases-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 02:04:30 -0000

Reviewer: Dale Worley
Review result: Ready with Nits

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

Document:  draft-ietf-i2nsf-problem-and-use-cases-12
Reviewer:  Dale R. Worley
Review Date:  2017-04-23
IETF LC End Date:  2017-03-22
IESG Telechat date:  2017-04-27

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

All of these nits are editorial.

3.1.1.  Diverse Types of Security Functions

   Security gateways and VPN concentrators:    Examples of these
      functions are; IPsec gateways, Secure VPN concentrators that
      handle bridging secure VPNs, and secure VPN controllers for
data
      flows.

Unless "Secure VPN" is a name in itself, "secure" shouldn't be
capitalized.  (Between -11 and -12, one instance of this was fixed,
but the other one remains.)

3.1.2.  Diverse Interfaces to Control and Monitor NSFs

   A challenge for monitoring prior to mitigation of a security
   intrusion is that an NSF cannot monitor what it cannot view.
   Therefore, enabling a security function to mitigate an intrusion
   (e.g., firewall [I-D.ietf-opsawg-firewalls]) does not mean that a
   network is protected if there is no monitoring feedback.  As such,
it
   is necessary to have a mechanism to monitor and provide execution
   status of NSFs to security and compliance management tools.  There
   exist various network security monitoring vendor-specific
interfaces
   for forensics and troubleshooting, but an industry standard
interface
   could provide monitoring across a variety of NSFs.

This paragraph still seems to have problems.  What the second
sentence
seems to mean (though it doesn't say it) is that if you enable a
security function, you don't *know* that the network is protected if
you don't have any monitoring feedback.  (The sentence is stated in
terms of whether the network *is* protected, which it might well be,
even if you don't have monitoring.)  It seems that you need to
replace
"does not mean that a network is protected" with something that is
more literally correct.

The third sentence is constructed "... to have a mechanism to monitor
and provide execution status of NSFs to ...".  There's an awkwardness
that "monitor" isn't connected to "security and compliance management
tools", whereas "provide ... status ... to" *is* connected; there's a
problem that the "monitor" and "provide" are written as if they're
parallel, but they're not.  I think the wording is less confusing
this
way:

   As such, it is necessary to have a mechanism to monitor NSFs and
   provide their execution status to security and compliance
   management tools.

--

   There
   exist various network security monitoring vendor-specific
interfaces
   for forensics and troubleshooting, but an industry standard
interface
   could provide monitoring across a variety of NSFs.

I think it's easier to read "vendor-specific network security
monitoring interfaces".

3.1.4.  More Demand to Control NSFs Dynamically

   The Security Service Providers ...

The capitalization of "security service providers" is inconsistent.
Some times all three words are capitalized (in 3.1.2, 3.1.4, and 4),
and some times they're not (two places in 3).

3.2.2.  Today's Control Requests are Vendor Specific

   Managing by scripts de-jour:    The current practices rely upon
the
      use of scripts that generate other scripts which automatically
run
      to upload or download configuration changes, log information
and
      other things.  These scripts have to be adjusted each time an
      implementation from a different vendor technology is enabled by
a
      provider side.

What is "a provider side"?  I suspect it means "the provider side of
an XXX", but I'm not familiar enough with the subject to know what
XXX
is.

[END]



From nobody Mon Apr 24 10:12:17 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2468B13189E; Mon, 24 Apr 2017 10:12:08 -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: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149305392811.25808.15115824976388262628@ietfa.amsl.com>
Date: Mon, 24 Apr 2017 10:12:08 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/qC6H14_XREOPQbsikbOHZspQYS0>
Subject: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 24 Apr 2017 17:12:08 -0000

Reviewer: Stewart Bryant
Review result: Ready with Issues

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

For more information, please see the FAQ at

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

Document: draft-ietf-6man-rfc1981bis-??
Reviewer: Stewart Bryant
Review Date: 2017-04-24
IETF LC End Date: 2017-03-01
IESG Telechat date: 2017-05-11

Summary: This is can be published as is, but I think could be
improved.

I thank the authors you for dealing with most of my comments in the
previous round.
There are two unaddressed points that the IETF Chair may wish to
consider, and one
that I missed.

Major issues:
The text has a lot of RFC2119 language, but no RFC2119 declaration.
and the document seems inconsistent about when it uses RFC2119
language and
when it does not. This sends a mixed messages to authors if we are not

consistent on this point throughout the RFC Series.

=======

5.3.  Purging stale PMTU information

   Internetwork topology is dynamic; routes change over time.  While
the
   local representation of a path may remain constant, the actual
   path(s) in use may change.  Thus, PMTU information cached by a
node
   can become stale.

   If the stale PMTU value is too large, this will be discovered
almost
   immediately once a large enough packet is sent on the path.  No
such
   mechanism exists for realizing that a stale PMTU value is too
small,
   so an implementation should "age" cached values.  When a PMTU
value
   has not been decreased for a while (on the order of 10 minutes),
the
   PMTU estimate should be set to the MTU of the first-hop link, and
the
   packetization layers should be notified of the change.  This will
   cause the complete Path MTU Discovery process to take place again.

SB> I still worry that the impact of this advice is going to be a
disruption to what might
SB> be a critical service every 10 mins, and wonder if there should be
some advice along the 
SB> lines of noting the importance of service delivery as part of
deciding whether to
SB> test for bigger PMTU vs improving efficiency?

Minor issues:

 A node MUST NOT reduce its estimate of the Path MTU below the IPv6
 minimum link MTU.

SB> I missed this last time.
SB>
SB> Presumably you mean "A node MUST NOT reduce its estimate of the 
SB> Path MTU below the IPv6 minimum link MTU in response to such
SB> a message."
SB> 
SB> Otherwise I would have thought that this was entirely a matter 
SB> for the host whether it wanted to use a Path MTU below the IPv6 
SB> link minimum. Nothing breaks if the host takes a more conservative

SB> decision.
SB> 

Nits/editorial comments:  None.



From nobody Tue Apr 25 05:20:48 2017
Return-Path: <brian@innovationslab.net>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BFC212EC6E; Tue, 25 Apr 2017 05:20:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 NGSK_BrEb3Db; Tue, 25 Apr 2017 05:20:44 -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 2E00B12EC5A; Tue, 25 Apr 2017 05:20:44 -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 1228488138; Tue, 25 Apr 2017 05:20:44 -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 745093280AE4; Tue, 25 Apr 2017 05:20:43 -0700 (PDT)
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-bchv-rfc6890bis.all@ietf.org
References: <48bebccb-4cf0-a218-38aa-af3fde41ad19@alum.mit.edu>
Cc: General Area Review Team <gen-art@ietf.org>
From: Brian Haberman <brian@innovationslab.net>
Message-ID: <5716a6ec-0b08-1851-4c1d-7c6cbe35c1f0@innovationslab.net>
Date: Tue, 25 Apr 2017 08:20:42 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <48bebccb-4cf0-a218-38aa-af3fde41ad19@alum.mit.edu>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="wD5kocct6Ne92gsOboOJlaRBSkKqPA1WG"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/O2HlQnOuHheFS7V2Aa5zxTblrQ0>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-bchv-rfc6890bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 12:20:45 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--wD5kocct6Ne92gsOboOJlaRBSkKqPA1WG
Content-Type: multipart/mixed; boundary="2eFEv5mg7Da9Dbc0ciKCKES3tFBs8r2wD";
 protected-headers="v1"
From: Brian Haberman <brian@innovationslab.net>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, draft-bchv-rfc6890bis.all@ietf.org
Cc: General Area Review Team <gen-art@ietf.org>
Message-ID: <5716a6ec-0b08-1851-4c1d-7c6cbe35c1f0@innovationslab.net>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-bchv-rfc6890bis-06
References: <48bebccb-4cf0-a218-38aa-af3fde41ad19@alum.mit.edu>
In-Reply-To: <48bebccb-4cf0-a218-38aa-af3fde41ad19@alum.mit.edu>

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

Hi Paul,

On 4/22/17 3:23 PM, Paul Kyzivat wrote:
> 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 <=E2=80=8B
> http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-bchv-rfc6890bis-06
> Reviewer: Paul Kyzivat
> Review Date: 2017-04-22
> IETF LC End Date: 2017-03-10
> IESG Telechat date: 2017-04-25
>=20
> Summary:
>=20
> This draft is basically ready for publication, but has nits that should=

> be fixed before publication.
>=20
> General Comments:
>=20
> This version is *much* easier to understand than the -04 version that I=

> previously reviewed.
>=20
> Issues:
>=20
> Major: 0
> Minor: 0
> Nits:  1
>=20
> (1) Nit:
>=20
> In section 2.3 the requested handling of footnotes is confusing.
> IIUC, the intent is:
>=20
> - add a new footnote between the existing [1] and [2];
>=20
> - add a new footnote at the end after the existing [5];
>=20
> - renumber the footnotes sequentially (from [1] to [7]);
>=20
> - adjust all the existing footnote references to refer to the same
>   footnote as previously, but using the new numbering;
>=20
> - then, add references to the new footnotes [2] and [7] to the entries
>   for TEREDO and Unique-Local.
>=20
> It took me a few readings of the current text to convince myself that i=
s
> what you intended. It would be better to be more explicit about it.

Your understanding is correct. To help the reader, I have added the
following to the beginning of 2.3:

The following changes to the IPv6 Special-Purpose Address Registry
involves the insertion of two new footnotes. These changes require the
footnotes to be re-numbered.

Does that help explain the changes in a clearer manner?

Regards,
Brian



--2eFEv5mg7Da9Dbc0ciKCKES3tFBs8r2wD--

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

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

iQEcBAEBCAAGBQJY/z8aAAoJEBOZRqCi7goq1LYH/2S4RFKXKaBOBrNDPnZj4CZp
t+1ujDAnlJlbq//A94DbVdnNA+JXMEWqOi/epFTI4IXCuC31LfqgrgiW46mp/7de
0+pm3EmHlMFy5QY2qOD2rZXl/tCBremUCNhsSkXPtx1jKGzYq5Sf6/cxhTOj8+zG
xIgCcv9FE7DgN7LqPV/s87UROnKbvaVx7OYyYceF7AYC1ILDhl7HbxDYm6Tz58GW
RX7dwt3d8slXXUkYPqAt4KeWP3qMRUgJhrpD8Q3OQn1JiSNQFX6pe+qf74easVvy
xUCn95lOdWLdwofTDLof0MSpQSE0N6hUyWMPTlbgPxwQxq9+bEfmWbh0k9ggmsc=
=vT6k
-----END PGP SIGNATURE-----

--wD5kocct6Ne92gsOboOJlaRBSkKqPA1WG--


From nobody Tue Apr 25 07:16:56 2017
Return-Path: <shares@ndzh.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BC95131452; Tue, 25 Apr 2017 07:16:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, 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 Kril4VnfMUYW; Tue, 25 Apr 2017 07:16:52 -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 CAFD313144B; Tue, 25 Apr 2017 07:16:51 -0700 (PDT)
X-Default-Received-SPF: pass (skip=loggedin (res=PASS)) x-ip-name=70.194.18.96; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Dale Worley'" <worley@ariadne.com>, <gen-art@ietf.org>
Cc: <i2nsf@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org>
References: <149299947052.25893.14183369388246516074@ietfa.amsl.com>
In-Reply-To: <149299947052.25893.14183369388246516074@ietfa.amsl.com>
Date: Tue, 25 Apr 2017 10:11:31 -0400
Message-ID: <006201d2bdcd$d8d21e40$8a765ac0$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJj1w0Rmgy1J+ijI/wBRaCzRiot8qCz7RLA
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Jpu8zc9eMSmmA15ZR3a4XU5Dr8k>
Subject: Re: [Gen-art] [I2nsf] Genart telechat review of draft-ietf-i2nsf-problem-and-use-cases-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 14:16:54 -0000

Dale: 

Thank you for the second review.  I'll address these issues along with
others later today. 

Sue Hares  

-----Original Message-----
From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Dale Worley
Sent: Sunday, April 23, 2017 10:05 PM
To: gen-art@ietf.org
Cc: i2nsf@ietf.org; ietf@ietf.org;
draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Subject: [I2nsf] Genart telechat review of
draft-ietf-i2nsf-problem-and-use-cases-12

Reviewer: Dale Worley
Review result: Ready with Nits

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

Document:  draft-ietf-i2nsf-problem-and-use-cases-12
Reviewer:  Dale R. Worley
Review Date:  2017-04-23
IETF LC End Date:  2017-03-22
IESG Telechat date:  2017-04-27

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

All of these nits are editorial.

3.1.1.  Diverse Types of Security Functions

   Security gateways and VPN concentrators:    Examples of these
      functions are; IPsec gateways, Secure VPN concentrators that
      handle bridging secure VPNs, and secure VPN controllers for data
      flows.

Unless "Secure VPN" is a name in itself, "secure" shouldn't be capitalized.
(Between -11 and -12, one instance of this was fixed, but the other one
remains.)

3.1.2.  Diverse Interfaces to Control and Monitor NSFs

   A challenge for monitoring prior to mitigation of a security
   intrusion is that an NSF cannot monitor what it cannot view.
   Therefore, enabling a security function to mitigate an intrusion
   (e.g., firewall [I-D.ietf-opsawg-firewalls]) does not mean that a
   network is protected if there is no monitoring feedback.  As such, it
   is necessary to have a mechanism to monitor and provide execution
   status of NSFs to security and compliance management tools.  There
   exist various network security monitoring vendor-specific interfaces
   for forensics and troubleshooting, but an industry standard interface
   could provide monitoring across a variety of NSFs.

This paragraph still seems to have problems.  What the second sentence seems
to mean (though it doesn't say it) is that if you enable a security
function, you don't *know* that the network is protected if you don't have
any monitoring feedback.  (The sentence is stated in terms of whether the
network *is* protected, which it might well be, even if you don't have
monitoring.)  It seems that you need to replace "does not mean that a
network is protected" with something that is more literally correct.

The third sentence is constructed "... to have a mechanism to monitor and
provide execution status of NSFs to ...".  There's an awkwardness that
"monitor" isn't connected to "security and compliance management tools",
whereas "provide ... status ... to" *is* connected; there's a problem that
the "monitor" and "provide" are written as if they're parallel, but they're
not.  I think the wording is less confusing this
way:

   As such, it is necessary to have a mechanism to monitor NSFs and
   provide their execution status to security and compliance
   management tools.

--

   There
   exist various network security monitoring vendor-specific interfaces
   for forensics and troubleshooting, but an industry standard interface
   could provide monitoring across a variety of NSFs.

I think it's easier to read "vendor-specific network security monitoring
interfaces".

3.1.4.  More Demand to Control NSFs Dynamically

   The Security Service Providers ...

The capitalization of "security service providers" is inconsistent.
Some times all three words are capitalized (in 3.1.2, 3.1.4, and 4), and
some times they're not (two places in 3).

3.2.2.  Today's Control Requests are Vendor Specific

   Managing by scripts de-jour:    The current practices rely upon
the
      use of scripts that generate other scripts which automatically run
      to upload or download configuration changes, log information and
      other things.  These scripts have to be adjusted each time an
      implementation from a different vendor technology is enabled by a
      provider side.

What is "a provider side"?  I suspect it means "the provider side of an
XXX", but I'm not familiar enough with the subject to know what XXX is.

[END]


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


From nobody Tue Apr 25 09:27:21 2017
Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 33A5F131688 for <gen-art@ietfa.amsl.com>; Tue, 25 Apr 2017 09:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.934
X-Spam-Level: 
X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 BipZ5c6itkR1 for <gen-art@ietfa.amsl.com>; Tue, 25 Apr 2017 09:27:18 -0700 (PDT)
Received: from resqmta-ch2-01v.sys.comcast.net (resqmta-ch2-01v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:33]) (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 E4641131684 for <gen-art@ietf.org>; Tue, 25 Apr 2017 09:27:17 -0700 (PDT)
Received: from resomta-ch2-01v.sys.comcast.net ([69.252.207.97]) by resqmta-ch2-01v.sys.comcast.net with SMTP id 33IidAuQhO3Qo33J7d1k9z; Tue, 25 Apr 2017 16:27:17 +0000
Received: from [192.168.1.110] ([24.62.227.142]) by resomta-ch2-01v.sys.comcast.net with SMTP id 33J6daJRjY10N33J6dsBoS; Tue, 25 Apr 2017 16:27:17 +0000
To: Brian Haberman <brian@innovationslab.net>, draft-bchv-rfc6890bis.all@ietf.org
References: <48bebccb-4cf0-a218-38aa-af3fde41ad19@alum.mit.edu> <5716a6ec-0b08-1851-4c1d-7c6cbe35c1f0@innovationslab.net>
Cc: General Area Review Team <gen-art@ietf.org>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <ed7a65b4-d9ab-c38e-9915-a4c3abd5eb68@alum.mit.edu>
Date: Tue, 25 Apr 2017 12:27:16 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <5716a6ec-0b08-1851-4c1d-7c6cbe35c1f0@innovationslab.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-CMAE-Envelope: MS4wfDVJEWs6ljPpM5zDsn4rYYQdlklfA663bqA3+r58w0Y+Eddo3h1juxl57bPBmBv1RRWTKRiipZzY+6Ig3uZ+G9Mu7GPWwsU7vwz10cgjQ4DpqtvSIG5N 2r0N88vMkyTJsIfnlaHh4AvKej9ZHj6r/8nvIkILBVydyQ8SxYflCrLC794TdrlOi93vCuVwNBcq3rHf/hlSnIp9CZNQa/qdRK2ydKmIu8CjHUW6dpYeFuEZ yaD4R3wAcOrFwiyGvPE6tg==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/1SQJQQiAfjMVtas4umtF15QiN10>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-bchv-rfc6890bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 16:27:19 -0000

On 4/25/17 8:20 AM, Brian Haberman wrote:
> Hi Paul,
>
> On 4/22/17 3:23 PM, Paul Kyzivat wrote:
>> 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-bchv-rfc6890bis-06
>> Reviewer: Paul Kyzivat
>> Review Date: 2017-04-22
>> IETF LC End Date: 2017-03-10
>> IESG Telechat date: 2017-04-25
>>
>> Summary:
>>
>> This draft is basically ready for publication, but has nits that should
>> be fixed before publication.
>>
>> General Comments:
>>
>> This version is *much* easier to understand than the -04 version that I
>> previously reviewed.
>>
>> Issues:
>>
>> Major: 0
>> Minor: 0
>> Nits:  1
>>
>> (1) Nit:
>>
>> In section 2.3 the requested handling of footnotes is confusing.
>> IIUC, the intent is:
>>
>> - add a new footnote between the existing [1] and [2];
>>
>> - add a new footnote at the end after the existing [5];
>>
>> - renumber the footnotes sequentially (from [1] to [7]);
>>
>> - adjust all the existing footnote references to refer to the same
>>   footnote as previously, but using the new numbering;
>>
>> - then, add references to the new footnotes [2] and [7] to the entries
>>   for TEREDO and Unique-Local.
>>
>> It took me a few readings of the current text to convince myself that is
>> what you intended. It would be better to be more explicit about it.
>
> Your understanding is correct. To help the reader, I have added the
> following to the beginning of 2.3:
>
> The following changes to the IPv6 Special-Purpose Address Registry
> involves the insertion of two new footnotes. These changes require the
> footnotes to be re-numbered.
>
> Does that help explain the changes in a clearer manner?

Yes. And since it is essentially a one-time thing and IANA will confirm 
the changes with the authors I see no need to wordsmith it.

	Thanks,
	Paul



From nobody Tue Apr 25 11:26:58 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73967128616; Tue, 25 Apr 2017 11:26:56 -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 V060TpduJo6C; Tue, 25 Apr 2017 11:26:55 -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 DCBD212946A; Tue, 25 Apr 2017 11:26:54 -0700 (PDT)
Received: from [128.9.184.33] ([128.9.184.33]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v3PIQ1sq026365 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 25 Apr 2017 11:26:03 -0700 (PDT)
To: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu>
Date: Tue, 25 Apr 2017 11:26:00 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <149305392811.25808.15115824976388262628@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Bixz8aDCQj8eEeSco3zaCgvhsBk>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 18:26:56 -0000

Hi, Stewart,


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

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

Joe


From nobody Tue Apr 25 15:19:55 2017
Return-Path: <elwynd@dial.pipex.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A999413162A; Tue, 25 Apr 2017 15:19:53 -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: ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
Date: Tue, 25 Apr 2017 15:19:53 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/2c7e3l52OaE-scVT1N4ZgFtWrr4>
Subject: [Gen-art] Genart last call review of draft-ietf-core-links-json-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 22:19:54 -0000

Reviewer: Elwyn Davies
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-core-links-json-07
Reviewer: Elwyn Davies
Review Date: 2017-04-25
IETF LC End Date: 2017-04-21
IESG Telechat date: 2017-04-27

Summary:Not ready for publication.  There a number of issues that need
to be addressed  as discussed below.  In particular whether the
formats could be returned as the web link specification instead of RFC
6990 format in response to a GET /.well-known/core request.

Having thought about the quote stripping/addition issue cited in Adam
Roach's DISCUSS, I would take a slightly different view... see below.

Major issues:

Intentions:
Is it one of the intentions of this draft that a server should be able
to return web link descriptions using JSON or CBOR, specifically in
response to GET /.well-known/core?  Content formats for the new
formats are registered (s3.2) - could a user ask for the alternative
formats by specifying at ct filter with the GET request?  It strikes
me that if one has a constrained server of sufficiently limited
capabilities that it wants to use CBOR then having to encode the RFC
6690 format responses for the web links requests is wasting resources.
 Some more thought needs to be given to this as an update to RFC 6690
- If I read correctly, RFC 6690 implicitly requires that a response to
GET /.well-known/core MUST be encoded as described in RFC6690.

Minor issues:
Title:  The document appears only to address the CoRE Web Links format
rather than any other.  Should the title reflect this more precisely,
e.g.,
      Representing CoRE Web Links Format in JSON and CBOR

s1.1: Concerning:
   o  The simplest thing that could possibly work

      *  Do not cater for RFC 5988 complications caused by HTTP
header
         character set issues [RFC2047]

Having ferreted around in RFC 5988 and RFC 2047, I can't see what is
being referred to here.  However, I observe later that the "title*"
attribute (with language specifier) does not appear to be supported
(It is missing from Table 1) - is this what is relevant here? If so it
needs clarification. 
[Aside: I notice that the relevant ABNF in s5 of RFC 5998 is missing
external references to various productions (e.g., ext-value,
quoted-string) that are defined in other documents - in the given
examples RFC 2987, RFC 2616.]

s2.2/s5: This statement:
   The resulting structure can be represented in CDDL
   [I-D.greevenbosch-appsawg-cbor-cddl] as:

requires that the CDDL draft is a normative reference rather than
informative.
[Aside:  Having skimmed the CDDL draft, I am of the opinion that a
good deal more work will be needed to get this ready for publication,
possibly to the extent that the CDDL quoted here becomes invalid. 
Given the simplicity of the specification could it be done without the
use of CDDL?] 

s2.2: There needs to be some discussion of handling of double quoted
and non-double quoted strings during conversion:
I think it works to require that...
>From RFC 6690 to JSON:
- If the parameter value is a double quoted string then it should have
the double quotes stripped, any necessary JSON character encodings
performed and the double quotes repapplied.
- if the parameter value is anything else, then the necessary JSON
character encodings are done and the result enclosed in double
quotes.
[what about % encodings on the RFC 6690 side?]

>From RFC 6690 to CBOR:
- If the parameter value is a double quoted string, the double quotes
are stripped and the result used as the CBOR string type value.
- Otherwise, the parameter value is used as the CBOR string value. 
[what about % encodings on the RFC 6690 side?]

>From JSON to RFC 6690: 
- Remove the double quotes from the JSON string value and do any
necessary decoding and encoding.  Reapply double quotes.  Note that
this may result in values that were originally not enclosed in double
quotes in the RFC 6690 repreentation becoming enclosed in double
quotes. However, [AFAICS] this does not alter the semantics of any of
the predefined parameters.  For example the ABNF productions mean that
ct=40 and ct="40" are equivalent (the second case is needed so that
one can also have ct="40 41 42").  What IS needed is a statement that
this must also apply to any application specific parameters.  For
example the case in examples 4 and 5 of ..;foo="bar";foo=3;...
transforming to "foo":["bar","3"] and then back to
...;foo="bar";foo="3";.. MUST require that the two RFC 6690
representations are equivalent.

>From CBOR to RFC 6690: 
[Essentially the same process - decode/encode and apply double quotes.
The discussion of equivalent semantics is equally applicable.]

The conversion from CBOR to JSON or in reverse is similar. 

s2.3: It is not stated whether a CBOR decoder should accept literal
use of the encodable parameters - i.e., if the encoded CBOR contains [
"href": "/mumble" ] rather than [1 : "mumbleÂ£ ] in CDDL format. 
Similarly, should the use of the encoded values be mandatory on the
CBOR encoder?

s2.3, Table 1:  Is the omission of title* from the list of parameter
names deliberate?  If so the omission justifies a note and rationale. 
Clearly the format of the value for a title* parameter is different
from all the others, which may have something to do with this.

s2.3/s5: eEfereences in Table 1 make RFC 7252 and RFC 7641 normative.

Nits/editorial comments: 
s1: s/e.g. /e.g., / (two places)

s1.1: The term "round-tripping" and the associated text are opaque
jargon that would normally  be applied to message transmission round a
loop rather than format conversion.  A more explicit formulation would
help naive readers.  Suggest (if I understand what was intended):
OLD:
   o  Canonical mapping

      *  lossless round-tripping with [RFC6690] and between JSON and
         CBOR

      *  but not trying for bit-preserving (DER-style) round-tripping
NEW:
   o  Canonical mapping

      *  supporting inter-conversion in both directions between any
pair 
         of [RFC6690] format and the CBOR and JSON formats defined
here 
         with unaltered and unambiguous semantics

      *  but not attempting to ensure that a sequence of conversions
from 
         one of the formats through one or both of the others and back
to 
         the original would result in an identical representation
(c.f., 
         as might be achieved by different BER transcoders rather than
by all 
         DER transcoders with ASN.1 [X.690]).
ENDS
This needs an informative reference to X.690 ... but I am not sure
that the DER comparison is essential.

s2.2:  Suggest:
OLD:
   We straightforwardly map:

   o  the outer collection to an array of links;

   o  each link to a JSON object or CBOR map, mapping attribute names
to
      attribute values.

NEW:
   We straightforwardly map:

   o  the outer collection to an array of parameterized web links;

   o  each parameterized web link to a JSON object or CBOR map,
mapping attribute names to
      attribute values.
ENDS

s2.2:
OLD:
The resulting structure can be represented in CDDL
   [I-D.greevenbosch-appsawg-cbor-cddl] as:
NEW:
The resulting structure can be represented in CBOR Data Definition
Language (CDDL)
   [I-D.greevenbosch-appsawg-cbor-cddl] as shown in Figure 1.
 
s2.4: Note that the use of ct=40 in RFC 6690 is an anchronism.  The ct
parameter appeared in earlier versions of the draft that led to RFC
6690 but was moved out to be used more generally in CoAP and is
actually defined in RFC 7252 as mentioned in Table 1 here.  Thus use
of ct=40 in the example copied from RFC 6690 really needs an erratum
for 6690 but that is for another day!   


From nobody Tue Apr 25 16:08:40 2017
Return-Path: <cabo@tzi.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 053DB1205F0; Tue, 25 Apr 2017 16:08:39 -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 Tq8gvNDBxS4f; Tue, 25 Apr 2017 16:08:35 -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 14F7E126B71; Tue, 25 Apr 2017 16:08:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3PN8TaM010863; Wed, 26 Apr 2017 01:08:29 +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 3wCJmF1FYXzDJ8x; Wed, 26 Apr 2017 01:08:29 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 01:08:28 +0200
Cc: gen-art@ietf.org, ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514854508.320519-706d79887a403956b4df6ab96ff401e3
Content-Transfer-Encoding: quoted-printable
Message-Id: <720C9B43-B803-4C99-A366-3C79F463FB23@tzi.org>
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/T-GbPhXqncPNIuuhLoQ4qddwrBo>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-core-links-json-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Apr 2017 23:08:39 -0000

Hi Elwyn,

thank you for your review =E2=80=94 that is a lot of good input.

Before I start thinking about fixes for the WG to consider, let me =
comment on a few items:

> Summary:Not ready for publication.  There a number of issues that need
> to be addressed  as discussed below.  In particular whether the
> formats could be returned as the web link specification instead of RFC
> 6990 format in response to a GET /.well-known/core request.
>=20
> Having thought about the quote stripping/addition issue cited in Adam
> Roach's DISCUSS, I would take a slightly different view... see below.
>=20
> Major issues:
>=20
> Intentions:
> Is it one of the intentions of this draft that a server should be able
> to return web link descriptions using JSON or CBOR, specifically in
> response to GET /.well-known/core? =20

Maybe not as much an intention as a possible direction that should =
remain open.

This draft defines two media types.  RFC 6690 defined another media =
type.
=46rom the point of RFC 6690=E2=80=99s registration of =
/.well-known/core, RFC 6690 was the only media type available, so the =
assumption there is that application/link-format is returned.
But if a client sends a CoAP Accept option for one of the two media =
types defined here, that should be returnable, too.
So we probably should say this explicitly (i.e., update RFC 6690 by =
saying this).

> Content formats for the new
> formats are registered (s3.2) - could a user ask for the alternative
> formats by specifying at ct filter with the GET request?  It strikes
> me that if one has a constrained server of sufficiently limited
> capabilities that it wants to use CBOR then having to encode the RFC
> 6690 format responses for the web links requests is wasting resources.
> Some more thought needs to be given to this as an update to RFC 6690
> - If I read correctly, RFC 6690 implicitly requires that a response to
> GET /.well-known/core MUST be encoded as described in RFC6690.

That is one way to read it =E2=80=94 however, if you apply the Web model =
and the fact that the Accept and Content-Format (integer version of =
media type + content coding) options are central to CoAP, a reading that =
RFC 6690 just specifies the initial media type for the well-known URI it =
defines becomes more likely.
But, again, we should make this explicit.

> Minor issues:
> Title:  The document appears only to address the CoRE Web Links format
> rather than any other.  Should the title reflect this more precisely,
> e.g.,
>      Representing CoRE Web Links Format in JSON and CBOR

The RFC editor will force us to expand CoRE.
Probably even simpler:
          Representing
          Constrained RESTful Environments (CoRE) Link Format
	  in JSON and CBOR

(The middle line is the title of RFC 6690.)

> s1.1: Concerning:
>   o  The simplest thing that could possibly work
>=20
>      *  Do not cater for RFC 5988 complications caused by HTTP
> header
>         character set issues [RFC2047]
>=20
> Having ferreted around in RFC 5988 and RFC 2047, I can't see what is
> being referred to here.  However, I observe later that the "title*"
> attribute (with language specifier) does not appear to be supported
> (It is missing from Table 1) - is this what is relevant here? If so it
> needs clarification.=20

Indeed.

> [Aside: I notice that the relevant ABNF in s5 of RFC 5998 is missing
> external references to various productions (e.g., ext-value,
> quoted-string) that are defined in other documents - in the given
> examples RFC 2987, RFC 2616.]
>=20
> s2.2/s5: This statement:
>   The resulting structure can be represented in CDDL
>   [I-D.greevenbosch-appsawg-cbor-cddl] as:
>=20
> requires that the CDDL draft is a normative reference rather than
> informative.

Well, this was meant to be interpreted as informative, but maybe that =
should be made more explicit.

> [Aside:  Having skimmed the CDDL draft, I am of the opinion that a
> good deal more work will be needed to get this ready for publication,
> possibly to the extent that the CDDL quoted here becomes invalid.=20

I don=E2=80=99t think so, but we would like to hear this opinion in the =
CBOR WG, where CDDL is being worked on.

> Given the simplicity of the specification could it be done without the
> use of CDDL?]=20

The intention was that all the normative information is in English, =
that=E2=80=99s why the CDDL reference is informative.

> s2.2: There needs to be some discussion of handling of double quoted
> and non-double quoted strings during conversion:
> I think it works to require that...
>> =46rom RFC 6690 to JSON:
> - If the parameter value is a double quoted string then it should have
> the double quotes stripped, any necessary JSON character encodings
> performed and the double quotes repapplied.

That=E2=80=99s not how the spec is written.  The assumption is that you =
already have a JSON or CBOR implementation, so the spec is at the data =
model level; it is not going to tell you how to parse or generate JSON =
or CBOR.  (Parsing and generating does, however, play a role for =
RFC6690.  Compare the example implementation, which is 90 % RFC 6690 =
implementation=E2=80=A6)

> - if the parameter value is anything else, then the necessary JSON
> character encodings are done and the result enclosed in double
> quotes.
> [what about % encodings on the RFC 6690 side?]

We are having a lovely discussion about percent-encoding right now in a =
thread over at art@, ietf@, core@.
Let me cite this part from RFC 6690 so you can share the fun:

   In
   order to convert an HTTP Link Header field to this link format, first
   the "Link:" HTTP header is removed, any linear whitespace (LWS) is
   removed, the header value is converted to UTF-8, and any percent-
   encodings are decoded.

(This obviously creates a limitation on RFC 6690; essentially it can=E2=80=
=99t represent URIs with percent-encoded reserved characters.  Whether =
that limitation should mirror over to the JSON/CBOR side is to be =
discussed in that other discussion.)

>> =46rom RFC 6690 to CBOR:
> - If the parameter value is a double quoted string, the double quotes
> are stripped and the result used as the CBOR string type value.
> - Otherwise, the parameter value is used as the CBOR string value.=20
> [what about % encodings on the RFC 6690 side?]

(See above)

>=20
>> =46rom JSON to RFC 6690:=20
> - Remove the double quotes from the JSON string value and do any
> necessary decoding and encoding.  Reapply double quotes.  Note that
> this may result in values that were originally not enclosed in double
> quotes in the RFC 6690 repreentation becoming enclosed in double
> quotes. However, [AFAICS] this does not alter the semantics of any of
> the predefined parameters.  For example the ABNF productions mean that
> ct=3D40 and ct=3D"40" are equivalent (the second case is needed so =
that
> one can also have ct=3D"40 41 42").  What IS needed is a statement =
that
> this must also apply to any application specific parameters. =20

Yes, that was one of the points that Mark=E2=80=99s comments pointed =
out.

> For
> example the case in examples 4 and 5 of ..;foo=3D"bar";foo=3D3;...
> transforming to "foo":["bar","3"] and then back to
> ...;foo=3D"bar";foo=3D"3";.. MUST require that the two RFC 6690
> representations are equivalent.

That is essentially an RFC 5988 limitation that RFC 6690 inherits and =
Mark=E2=80=99s RFC5988bis repairs by pretty much stating just this.

>> =46rom CBOR to RFC 6690:=20
> [Essentially the same process - decode/encode and apply double quotes.
> The discussion of equivalent semantics is equally applicable.]
>=20
> The conversion from CBOR to JSON or in reverse is similar.=20

(Ditto)

> s2.3: It is not stated whether a CBOR decoder should accept literal
> use of the encodable parameters - i.e., if the encoded CBOR contains [
> "href": "/mumble" ] rather than [1 : "mumble=C2=A3 ] in CDDL format.=20=


It should not.

   The above specification for JSON could be used as is for the CBOR
   encoding as well.  However, to further reduce message sizes, an extra
   encoding step is performed: "href" and some commonly occurring
   attribute names are encoded as small integers.

The =E2=80=9Cis=E2=80=9D/=E2=80=9Care" should be interpreted as MUST do =
that =E2=80=94 maybe again this needs to be explicit.

Should a links-cbor decoder required to reject those 13 strings?  Hmm.
Interoperability probably says yes, complexity says no.

> Similarly, should the use of the encoded values be mandatory on the
> CBOR encoder?

Yes.

> s2.3, Table 1:  Is the omission of title* from the list of parameter
> names deliberate?  If so the omission justifies a note and rationale.=20=

> Clearly the format of the value for a title* parameter is different
> from all the others, which may have something to do with this.

Yes.  I=E2=80=99m forgetting what title* is being used for over in the =
Big Web, so I=E2=80=99ll have to look this up again.

>=20
> s2.3/s5: eEfereences in Table 1 make RFC 7252 and RFC 7641 normative.

Here, I fully disagree (sorry, pet peeve =E2=80=94 we are way too lax =
with the concept of normative references in the IETF).
When specification B uses a string that is mentioned in specification A, =
without needing anything else from specification A, this doesn=E2=80=99t =
make specification A normative for B.
A is normative if you need to read it to implement B; that is not the =
case here.


> Nits/editorial comments:=20
> s1: s/e.g. /e.g., / (two places)

Thanks, a favorite mistake of this non-native speaker.

> s1.1: The term "round-tripping" and the associated text are opaque
> jargon that would normally  be applied to message transmission round a
> loop rather than format conversion. =20

(Actually, for me that is a term of art in format conversion.  But I =
only have worked on format conversions since 1982 :-)
Yes, we need to avoid jargon.

> A more explicit formulation would
> help naive readers.  Suggest (if I understand what was intended):
> OLD:
>   o  Canonical mapping
>=20
>      *  lossless round-tripping with [RFC6690] and between JSON and
>         CBOR
>=20
>      *  but not trying for bit-preserving (DER-style) round-tripping
> NEW:
>   o  Canonical mapping
>=20
>      *  supporting inter-conversion in both directions between any
> pair=20
>         of [RFC6690] format and the CBOR and JSON formats defined
> here=20
>         with unaltered and unambiguous semantics
>=20
>      *  but not attempting to ensure that a sequence of conversions
> from=20
>         one of the formats through one or both of the others and back
> to=20
>         the original would result in an identical representation
> (c.f.,=20
>         as might be achieved by different BER transcoders rather than
> by all=20
>         DER transcoders with ASN.1 [X.690]).
> ENDS
> This needs an informative reference to X.690 ... but I am not sure
> that the DER comparison is essential.

(I hope, not.  But thanks for the text suggestion, that will certainly =
help.)

> s2.2:  Suggest:
> OLD:
>   We straightforwardly map:
>=20
>   o  the outer collection to an array of links;
>=20
>   o  each link to a JSON object or CBOR map, mapping attribute names
> to
>      attribute values.
>=20
> NEW:
>   We straightforwardly map:
>=20
>   o  the outer collection to an array of parameterized web links;
>=20
>   o  each parameterized web link to a JSON object or CBOR map,
> mapping attribute names to
>      attribute values.
> ENDS

Hmm, do we need the term =E2=80=9Cparameterized web link=E2=80=9D for =
what most of us call =E2=80=9Clink=E2=80=9D?

> s2.2:
> OLD:
> The resulting structure can be represented in CDDL
>   [I-D.greevenbosch-appsawg-cbor-cddl] as:
> NEW:
> The resulting structure can be represented in CBOR Data Definition
> Language (CDDL)
>   [I-D.greevenbosch-appsawg-cbor-cddl] as shown in Figure 1.

Yes.

> s2.4: Note that the use of ct=3D40 in RFC 6690 is an anchronism.  The =
ct
> parameter appeared in earlier versions of the draft that led to RFC
> 6690 but was moved out to be used more generally in CoAP and is
> actually defined in RFC 7252 as mentioned in Table 1 here.  Thus use
> of ct=3D40 in the example copied from RFC 6690 really needs an erratum
> for 6690 but that is for another day!  =20

Actually, not quite, as =E2=80=9Cct=E2=80=9D is deliberately used in RFC =
6690 in an example only =E2=80=94 you wouldn=E2=80=99t look for a =
normative reference to a document defining =E2=80=9Cfoo=E2=80=9D if we =
had used that :-)

Again, thank you for that thoughtful feedback, this will help us =
significantly in making the specification better.

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


From nobody Wed Apr 26 01:49:08 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDFE3131A10; Wed, 26 Apr 2017 01:48:53 -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 9wWFl6aZayu3; Wed, 26 Apr 2017 01:48:52 -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 19730131A12; Wed, 26 Apr 2017 01:48:52 -0700 (PDT)
Received: by mail-wr0-x235.google.com with SMTP id l9so19315062wre.1; Wed, 26 Apr 2017 01:48:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=OPpzDn4dLZdj73y5j1tvgCeWiWSxiLQI1WqVx/K5boc=; b=q94HxZQRuMSPwczQZB9fM30LBtX35/tdscfe6z6QHtCAh0C/nZkzyDz0e4nxWJUuYm pRs6xyZa0q/GR0YOcx16NaIO7J+2vxpvptduZxWKn67hmPJZ10KET+4rLkpZlCAFVDyf 3NOSYiLkLkiZGeg67rszTHH/ZIp1tBv9oeQO7zfqs7knHRVLyNfJ1t4OTX1npC9/8ajP broo/Q81BmyVnH1FoMyqIOMLVPthto7GLNVHuwOBJd/YQ5I2Frzvc4bgqQFruh3yCaTG d3drm0OC16Vv9MzPieFKKEX72uFsu8QAY8z7YaBZp7PpkJ7x28tbx+0YwgIBU6MxtI14 0UfQ==
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=OPpzDn4dLZdj73y5j1tvgCeWiWSxiLQI1WqVx/K5boc=; b=qP8/wkLxZa35sgnrPv8us9JI3RwoD/cyufwbaTBX7grioj6Rerl52EFBkb8udWZ73b VEYm0FG2qOI9TQ5t/Lbtv1r4gB7JYU7QRrHoUI3Bz9QYoow6RZvInciPnmRUmsA0IA+V ovvq/v7UJW05iqWiMcaMbObdNEIa5Uo6zNKzFx8RVdvM3xwRYCAPsI1OMeX+6jakf6TW 5OlPr1lDv7S/EaWWcEmCMhjWMiyx3t0o/C/OkB9Ra71GruS/zMGWoT0EwwtQ2aLjnzKh v7SeWLYTjdp51psafr9RQc03YbAUeaFa3tLi95TgtLQbKkl0KIeQxumFA6Ew2WA+ILq7 7GjA==
X-Gm-Message-State: AN3rC/50tcG2b6HxoG+cTrlreiGJjeAfZrc+wLRtnUAC/UyyDGxUd/xj 8kTM0WoZ7iLo5odjfms=
X-Received: by 10.223.165.138 with SMTP id g10mr14232293wrc.19.1493196530389;  Wed, 26 Apr 2017 01:48:50 -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 m83sm7988509wmc.7.2017.04.26.01.48.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 01:48:49 -0700 (PDT)
To: Joe Touch <touch@isi.edu>, gen-art@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu>
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com>
Date: Wed, 26 Apr 2017 09:48:43 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/DqBlQC95ebAOqaqW47GOJeErKys>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 08:48:54 -0000

On 25/04/2017 19:26, Joe Touch wrote:
> Hi, Stewart,
>
>
> On 4/24/2017 10:12 AM, Stewart Bryant wrote:
>> Minor issues:
>>
>>   A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>>   minimum link MTU.
>>
>> SB> I missed this last time.
>> SB>
>> SB> Presumably you mean "A node MUST NOT reduce its estimate of the
>> SB> Path MTU below the IPv6 minimum link MTU in response to such
>> SB> a message."
> This seems fine to me, FWIW - i.e., limiting the advice in this doc to
> the mechanism in  this doc.
>
>> SB>
>> SB> Otherwise I would have thought that this was entirely a matter
>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>> SB> link minimum. Nothing breaks if the host takes a more conservative
>> SB> decision.
> I don't agree; the host at that point is violating RFC2460. It should
> never think that an IPv6 link or path with an MTU below what RFC2460
> requires is valid.
>
> Joe
>

That is as maybe, but a host can do more or less what it wants, so this 
is surely an
unenforceable constraint, or are you telling me that the receiving host 
MUST drop a
fragment that is shorter than this? In which case the question whether 
in practice
they do, and whether such a constraint is reasonable.

- Stewart


From nobody Wed Apr 26 07:21:15 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8ACC12EC6D; Wed, 26 Apr 2017 07:21:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.721
X-Spam-Level: 
X-Spam-Status: No, score=-2.721 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=QlbgIf9h; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=VTIHCQM5
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZbhUtUMEKzyY; Wed, 26 Apr 2017 07:20:59 -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 C363C12EAA8; Wed, 26 Apr 2017 07:13:53 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 401E82148F; Wed, 26 Apr 2017 10:13:53 -0400 (EDT)
Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Wed, 26 Apr 2017 10:13:53 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=FoOpNf1wunpNHLG16T GDzYkvX7aWLPJ4GCr4fxmWhME=; b=QlbgIf9hpyLAczQ6dqnotspcVG0Ds1iOhP LxRZOwKpmaJ01In/LPpRsbcIZ8MWtE4qr3qht9arQmdx3Ds7TrZpBlYyL0+9COEr dr6RIjTf96J9nAexwODNBMKU316l6yN1k2VCxUmuJWj1vNyOUS3R9d+tJ4+wPwb1 fvZHsU3L6ofJdwVG/dwVimRifWF0zy6rtgOW+eeJWVZp0Qa9eIPezYP5NcwEk0E7 MbX2tbi511PSPB2rIbdZdUKX0sZovD/WJPce162l/SajEi5bhiwwSJSyKt84m2c3 yI8Ei7BK6PKcQ4XYBy4xFBdWBf3o44cg26/pm/8M/5anH97KuloQ==
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=FoOpNf1wunpNHLG16TGDzYkvX7aWLPJ4GCr4fxmWhME=; b=VTIHCQM5 xRcCBvj10sW+545XF5yndDcWSSEanVc1k0dCw1zYWa2182Znxh3z4RFFKSTeFp9k Fp4pcJYr0X2b0KWXZOJZt9WcSmyHMEc906XpS0TrJBqe4JOVUT1txCG2NlASAr5N ISa5Sb3nFbcTL/ouXymftKaLe4sYD12FPMMMbBEvuXB7aih29IuVWTtO8OgDKb/D ZJMg0n/wfayjtwF4uqfvaWr4C9SYSaMF3orh9dIvlnszRSRJlPTA6vDArR5gzlO2 nJ/BVbyr1OnngFlbouKXBc26inA9TgXQvWDduYzfxjDEpJPBonoAon5J9Ew8iEVr n7RrCYOZ8s9Wxg==
X-ME-Sender: <xms:IasAWdUKM0fpYqbC8woLZk_bSCgLu6YF2ymIP4PVWBTpCIQONoKn8A>
X-Sasl-enc: BaM8S32cIUuJonPPxeKpHo/c5Wj+TM/UPs9RmY8tafer 1493216032
Received: from [10.24.116.101] (unknown [128.107.241.169]) by mail.messagingengine.com (Postfix) with ESMTPA id 1AB6C24765; Wed, 26 Apr 2017 10:13:51 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 10:13:50 -0400
Cc: gen-art@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <62FD1D61-8C72-45EB-9614-95CA14B91D7B@cooperw.in>
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/k1o_f7OhzeUyXIvnPMNSVQqfuk0>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-core-links-json-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 14:21:01 -0000

Elwyn, many thanks for your review. I=E2=80=99ve included it in my =
ballot position and am holding a DISCUSS while the major issue gets =
resolved.

Authors/WG, thanks for engaging with Elwyn=E2=80=99s review.

Alissa

> On Apr 25, 2017, at 6:19 PM, Elwyn Davies <elwynd@dial.pipex.com> =
wrote:
>=20
> Reviewer: Elwyn Davies
> Review result: Not 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>.
>=20
> Document: draft-ietf-core-links-json-07
> Reviewer: Elwyn Davies
> Review Date: 2017-04-25
> IETF LC End Date: 2017-04-21
> IESG Telechat date: 2017-04-27
>=20
> Summary:Not ready for publication.  There a number of issues that need
> to be addressed  as discussed below.  In particular whether the
> formats could be returned as the web link specification instead of RFC
> 6990 format in response to a GET /.well-known/core request.
>=20
> Having thought about the quote stripping/addition issue cited in Adam
> Roach's DISCUSS, I would take a slightly different view... see below.
>=20
> Major issues:
>=20
> Intentions:
> Is it one of the intentions of this draft that a server should be able
> to return web link descriptions using JSON or CBOR, specifically in
> response to GET /.well-known/core?  Content formats for the new
> formats are registered (s3.2) - could a user ask for the alternative
> formats by specifying at ct filter with the GET request?  It strikes
> me that if one has a constrained server of sufficiently limited
> capabilities that it wants to use CBOR then having to encode the RFC
> 6690 format responses for the web links requests is wasting resources.
> Some more thought needs to be given to this as an update to RFC 6690
> - If I read correctly, RFC 6690 implicitly requires that a response to
> GET /.well-known/core MUST be encoded as described in RFC6690.
>=20
> Minor issues:
> Title:  The document appears only to address the CoRE Web Links format
> rather than any other.  Should the title reflect this more precisely,
> e.g.,
>      Representing CoRE Web Links Format in JSON and CBOR
>=20
> s1.1: Concerning:
>   o  The simplest thing that could possibly work
>=20
>      *  Do not cater for RFC 5988 complications caused by HTTP
> header
>         character set issues [RFC2047]
>=20
> Having ferreted around in RFC 5988 and RFC 2047, I can't see what is
> being referred to here.  However, I observe later that the "title*"
> attribute (with language specifier) does not appear to be supported
> (It is missing from Table 1) - is this what is relevant here? If so it
> needs clarification.=20
> [Aside: I notice that the relevant ABNF in s5 of RFC 5998 is missing
> external references to various productions (e.g., ext-value,
> quoted-string) that are defined in other documents - in the given
> examples RFC 2987, RFC 2616.]
>=20
> s2.2/s5: This statement:
>   The resulting structure can be represented in CDDL
>   [I-D.greevenbosch-appsawg-cbor-cddl] as:
>=20
> requires that the CDDL draft is a normative reference rather than
> informative.
> [Aside:  Having skimmed the CDDL draft, I am of the opinion that a
> good deal more work will be needed to get this ready for publication,
> possibly to the extent that the CDDL quoted here becomes invalid.=20
> Given the simplicity of the specification could it be done without the
> use of CDDL?]=20
>=20
> s2.2: There needs to be some discussion of handling of double quoted
> and non-double quoted strings during conversion:
> I think it works to require that...
>> =46rom RFC 6690 to JSON:
> - If the parameter value is a double quoted string then it should have
> the double quotes stripped, any necessary JSON character encodings
> performed and the double quotes repapplied.
> - if the parameter value is anything else, then the necessary JSON
> character encodings are done and the result enclosed in double
> quotes.
> [what about % encodings on the RFC 6690 side?]
>=20
>> =46rom RFC 6690 to CBOR:
> - If the parameter value is a double quoted string, the double quotes
> are stripped and the result used as the CBOR string type value.
> - Otherwise, the parameter value is used as the CBOR string value.=20
> [what about % encodings on the RFC 6690 side?]
>=20
>> =46rom JSON to RFC 6690:=20
> - Remove the double quotes from the JSON string value and do any
> necessary decoding and encoding.  Reapply double quotes.  Note that
> this may result in values that were originally not enclosed in double
> quotes in the RFC 6690 repreentation becoming enclosed in double
> quotes. However, [AFAICS] this does not alter the semantics of any of
> the predefined parameters.  For example the ABNF productions mean that
> ct=3D40 and ct=3D"40" are equivalent (the second case is needed so =
that
> one can also have ct=3D"40 41 42").  What IS needed is a statement =
that
> this must also apply to any application specific parameters.  For
> example the case in examples 4 and 5 of ..;foo=3D"bar";foo=3D3;...
> transforming to "foo":["bar","3"] and then back to
> ...;foo=3D"bar";foo=3D"3";.. MUST require that the two RFC 6690
> representations are equivalent.
>=20
>> =46rom CBOR to RFC 6690:=20
> [Essentially the same process - decode/encode and apply double quotes.
> The discussion of equivalent semantics is equally applicable.]
>=20
> The conversion from CBOR to JSON or in reverse is similar.=20
>=20
> s2.3: It is not stated whether a CBOR decoder should accept literal
> use of the encodable parameters - i.e., if the encoded CBOR contains [
> "href": "/mumble" ] rather than [1 : "mumble=C2=A3 ] in CDDL format.=20=

> Similarly, should the use of the encoded values be mandatory on the
> CBOR encoder?
>=20
> s2.3, Table 1:  Is the omission of title* from the list of parameter
> names deliberate?  If so the omission justifies a note and rationale.=20=

> Clearly the format of the value for a title* parameter is different
> from all the others, which may have something to do with this.
>=20
> s2.3/s5: eEfereences in Table 1 make RFC 7252 and RFC 7641 normative.
>=20
> Nits/editorial comments:=20
> s1: s/e.g. /e.g., / (two places)
>=20
> s1.1: The term "round-tripping" and the associated text are opaque
> jargon that would normally  be applied to message transmission round a
> loop rather than format conversion.  A more explicit formulation would
> help naive readers.  Suggest (if I understand what was intended):
> OLD:
>   o  Canonical mapping
>=20
>      *  lossless round-tripping with [RFC6690] and between JSON and
>         CBOR
>=20
>      *  but not trying for bit-preserving (DER-style) round-tripping
> NEW:
>   o  Canonical mapping
>=20
>      *  supporting inter-conversion in both directions between any
> pair=20
>         of [RFC6690] format and the CBOR and JSON formats defined
> here=20
>         with unaltered and unambiguous semantics
>=20
>      *  but not attempting to ensure that a sequence of conversions
> from=20
>         one of the formats through one or both of the others and back
> to=20
>         the original would result in an identical representation
> (c.f.,=20
>         as might be achieved by different BER transcoders rather than
> by all=20
>         DER transcoders with ASN.1 [X.690]).
> ENDS
> This needs an informative reference to X.690 ... but I am not sure
> that the DER comparison is essential.
>=20
> s2.2:  Suggest:
> OLD:
>   We straightforwardly map:
>=20
>   o  the outer collection to an array of links;
>=20
>   o  each link to a JSON object or CBOR map, mapping attribute names
> to
>      attribute values.
>=20
> NEW:
>   We straightforwardly map:
>=20
>   o  the outer collection to an array of parameterized web links;
>=20
>   o  each parameterized web link to a JSON object or CBOR map,
> mapping attribute names to
>      attribute values.
> ENDS
>=20
> s2.2:
> OLD:
> The resulting structure can be represented in CDDL
>   [I-D.greevenbosch-appsawg-cbor-cddl] as:
> NEW:
> The resulting structure can be represented in CBOR Data Definition
> Language (CDDL)
>   [I-D.greevenbosch-appsawg-cbor-cddl] as shown in Figure 1.
>=20
> s2.4: Note that the use of ct=3D40 in RFC 6690 is an anchronism.  The =
ct
> parameter appeared in earlier versions of the draft that led to RFC
> 6690 but was moved out to be used more generally in CoAP and is
> actually defined in RFC 7252 as mentioned in Table 1 here.  Thus use
> of ct=3D40 in the example copied from RFC 6690 really needs an erratum
> for 6690 but that is for another day!  =20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 26 09:05:46 2017
Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 960B11300E8; Wed, 26 Apr 2017 09:05:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Sparks <rjsparks@nostrum.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-bmwg-ipv6-tran-tech-benchmarking.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149322271242.5954.6564310624067283031@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 09:05:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/_U4aUjrxJ5VOq25ymWLyE1913fA>
Subject: [Gen-art] Genart last call review of draft-ietf-bmwg-ipv6-tran-tech-benchmarking-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 16:05:22 -0000

Reviewer: Robert Sparks
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-ipv6-tran-tech-benchmarking-06
Reviewer: Robert Sparks
Review Date: 2017-04-26
IETF LC End Date: 2017-05-02
IESG Telechat date: Not scheduled for a telechat

Summary: Essentially Ready for publication as an Informational RFC,
but with some minor issues to address before publication

This document is (with exceptions noted below) straightforward and
easy to follow

Minor Issues:

Section 8 is very confusing - I suspect it has been made so by
removing things that were in it earlier. Right now it claims to
provide additional tests, but the only content is about testing things
with firewalls, along with a statement that this document is only
targeting network devices that do not have a firewall function. I
think you can keep most of the text here (except the statement that
you aren't talking about things with firewalls) and remove the
confusion by changing the section heading to something like "Tests in
the presence of a firewall function".

It's unclear how to apply the formula in Section 10.2.1 to the results
that come out of, say, Section 7.3.2, where you are reporting a
(minimum, median, maximum) tuple. Some discussion about the
applicability of the tests where you recommend against reporting a
single number to the methods in this section would help. It would also
help to point out that the Xpd result can be go negative (it will go
negative for things that become smaller as the number of flows
increase, and positive for things that get bigger). If I read this
correctly, if throughput (for example) goes to 0 as n increases, Xpd
will go to -100%. Similary if latency doubles as n increases, Xpd will
go to +100% (and will go to +200% if latency triples).

Nits:

There are several places where you point to Section 6 where I think
you meant to point to Section 7. See the Procedure: line in 10.2.1 for
an example. Also make sure 9 is correct where you say "Sections 6
through 9" in section 12.

Please double-check that you meant "larger MTU" in the last paragraph
of 5.1. It might be correct, but I find the paragraph confusing.

In 8.1 you meant to point to 5.2, not 5.3

Please try to simplify this sentence: 
  "The duration of each trial SHOULD be at least 60 seconds to reduce
the potential gain of a DNS64 server, which is able to exhibit higher
performance by storing the requests and thus utilizing also the
timeout time for answering them."

(Style comment - please feel free to ignore): Consider deleting "as
well" everywhere it occurs in the document - most of the places it is
used, the sentence works just as well, and sometimes better, without
it.

Typos:
end of section 5.1.1: Appendix A1 should be Appendix A
please remove the comma in the first sentence of the second paragraph
of section 5.2



From nobody Wed Apr 26 09:27:51 2017
Return-Path: <sarah.banks@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF73131491; Wed, 26 Apr 2017 09:27:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham 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 UngOZXbxf_3e; Wed, 26 Apr 2017 09:27:39 -0700 (PDT)
Received: from mail-oi0-x242.google.com (mail-oi0-x242.google.com [IPv6:2607:f8b0:4003:c06::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 196D0124B0A; Wed, 26 Apr 2017 09:27:36 -0700 (PDT)
Received: by mail-oi0-x242.google.com with SMTP id m34so1441646oik.2; Wed, 26 Apr 2017 09:27:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=IKasMraTRyvHWJ8U7oqEhFKH4QCq8fy89khGsA2KoEA=; b=q+Khg7PM6cHv+h6kIywxgD3N625KZZ+0dgw/qFTDraneg+3tohcuDHhLcDyidvxRaW VeKtoKnGUEWVqzdpwe7qYxS5gbh8PXMMkYCLW1FYRwJQB/5JLTezRgimyQ813GB8DjeS rgU0uLip2qVlgdbuk7JPaC+h3riN6K7UVy14Gp8B6nZ4sixtdCxPd7bRxuLYdCGDiGNh p/YKXKYJo/nOzDb7TTKASrmqkKLDoJnS4gUnsoL7AU08hssnUMTeezHlCE1DmOVbDtX1 s+VKscfvOQlQ3y8Cr/Q/i8OLjC0YfNhb83k2ndhf/iFpJQye7mEzXypibG8asHfCFg6K KKHg==
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=IKasMraTRyvHWJ8U7oqEhFKH4QCq8fy89khGsA2KoEA=; b=Ooc4CkMXonMYH9V0F8ELNksjQFeG7/wbzvAVdFy8dDBjt4Wsc//O/8ju2D2khD89Et 1rq/boqVlAxXViOlfXz1Fi1Duage+k9Rh60TdYz+AfELueqeJ7yaz5tsNxgefiOH883R zwUl/dRZ81BW16q52bVkxNOf3Bx3gI+Ofq3yM9Ko3qRkEXQ1/Ma3RK43qgtwzn0xJ9AB /eBoXPXIPHjwwdicueTKOetinkmywsh8p+8S/BpFQzkisgb26vGoVCoFf1XAchiwTVq0 ZZNkkSEBtpA9RalZPq67OGS7PVnI5vScR18777hstl4ev3PFcDy9GdVmwHmjKSgmCQs/ QIxA==
X-Gm-Message-State: AN3rC/62HfgqOSf85sOZzfuiVkfmCfuyXhEabmdTDcDk2Vo5xUiGrNui xwFVYsu+NdaR/e0pytQ=
X-Received: by 10.157.49.17 with SMTP id e17mr405178otc.42.1493224055173; Wed, 26 Apr 2017 09:27:35 -0700 (PDT)
Received: from [10.211.187.101] (mobile-166-176-123-51.mycingular.net. [166.176.123.51]) by smtp.gmail.com with ESMTPSA id j51sm291042otc.47.2017.04.26.09.27.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 09:27:34 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Sarah Banks <sarah.banks@gmail.com>
X-Mailer: iPhone Mail (14E304)
In-Reply-To: <149322271242.5954.6564310624067283031@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 12:27:33 -0400
Cc: gen-art@ietf.org, draft-ietf-bmwg-ipv6-tran-tech-benchmarking.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <85B5ED62-14E2-4103-9B59-20DAA8763E01@gmail.com>
References: <149322271242.5954.6564310624067283031@ietfa.amsl.com>
To: Robert Sparks <rjsparks@nostrum.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/pEBYI8oL63OfjbRtFyhTY5H5wFY>
Subject: Re: [Gen-art] [bmwg] Genart last call review of draft-ietf-bmwg-ipv6-tran-tech-benchmarking-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 16:27:41 -0000

Hi Robert,
    Thank you for your review; we appreciate your time and comments, and the=
 authors will review in due course.=20

Thanks
Sarah

> On Apr 26, 2017, at 12:05 PM, Robert Sparks <rjsparks@nostrum.com> wrote:
>=20
> Reviewer: Robert Sparks
> 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-ipv6-tran-tech-benchmarking-06
> Reviewer: Robert Sparks
> Review Date: 2017-04-26
> IETF LC End Date: 2017-05-02
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: Essentially Ready for publication as an Informational RFC,
> but with some minor issues to address before publication
>=20
> This document is (with exceptions noted below) straightforward and
> easy to follow
>=20
> Minor Issues:
>=20
> Section 8 is very confusing - I suspect it has been made so by
> removing things that were in it earlier. Right now it claims to
> provide additional tests, but the only content is about testing things
> with firewalls, along with a statement that this document is only
> targeting network devices that do not have a firewall function. I
> think you can keep most of the text here (except the statement that
> you aren't talking about things with firewalls) and remove the
> confusion by changing the section heading to something like "Tests in
> the presence of a firewall function".
>=20
> It's unclear how to apply the formula in Section 10.2.1 to the results
> that come out of, say, Section 7.3.2, where you are reporting a
> (minimum, median, maximum) tuple. Some discussion about the
> applicability of the tests where you recommend against reporting a
> single number to the methods in this section would help. It would also
> help to point out that the Xpd result can be go negative (it will go
> negative for things that become smaller as the number of flows
> increase, and positive for things that get bigger). If I read this
> correctly, if throughput (for example) goes to 0 as n increases, Xpd
> will go to -100%. Similary if latency doubles as n increases, Xpd will
> go to +100% (and will go to +200% if latency triples).
>=20
> Nits:
>=20
> There are several places where you point to Section 6 where I think
> you meant to point to Section 7. See the Procedure: line in 10.2.1 for
> an example. Also make sure 9 is correct where you say "Sections 6
> through 9" in section 12.
>=20
> Please double-check that you meant "larger MTU" in the last paragraph
> of 5.1. It might be correct, but I find the paragraph confusing.
>=20
> In 8.1 you meant to point to 5.2, not 5.3
>=20
> Please try to simplify this sentence:=20
>  "The duration of each trial SHOULD be at least 60 seconds to reduce
> the potential gain of a DNS64 server, which is able to exhibit higher
> performance by storing the requests and thus utilizing also the
> timeout time for answering them."
>=20
> (Style comment - please feel free to ignore): Consider deleting "as
> well" everywhere it occurs in the document - most of the places it is
> used, the sentence works just as well, and sometimes better, without
> it.
>=20
> Typos:
> end of section 5.1.1: Appendix A1 should be Appendix A
> please remove the comma in the first sentence of the second paragraph
> of section 5.2
>=20
>=20
> _______________________________________________
> bmwg mailing list
> bmwg@ietf.org
> https://www.ietf.org/mailman/listinfo/bmwg


From nobody Wed Apr 26 10:05:09 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 62722126DDF; Wed, 26 Apr 2017 10:05:08 -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=EVawIT4w; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=RPzXeEoc
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bWJoKNs0L2fw; Wed, 26 Apr 2017 10:05:06 -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 0BF1E131518; Wed, 26 Apr 2017 10:05:06 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 7755B21C0A; Wed, 26 Apr 2017 13:05:05 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 26 Apr 2017 13:05:05 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=oLGgU71r95Kza0LlJu 3POH2BBPeWbooEa6BjOMSvKSo=; b=EVawIT4w8Z6Qgp/eozreuuoDZuy2+t0Q0b CsMotjaZR9F2hbDbgMd0JAkeq8VNN4V0/q38t6oqkwy13GrBPR1lEl3Mn5x2no41 1IsIE56CnOkpzjmcDd2awZm3/Tk/0Xu8ro5JTSFIb748DaVRT1zhnJsatu1HFT5E c5t/eMfb6wF+yVuc+Hxdz6Nif9kk4WwQqeMGdfJr9PKdRojobXWSKyoCBhx7Hi84 trTlh7IARRItVuKNEw6p5o/J8Ee6MmTaE7DGEZhOVUhMUt1XWaH9sGloS67jGPhi 0E0uw5V8dujI+jlSfmWdjPqElYuS1vdiCLCkpqFXxUaS8h6HgFKg==
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=oLGgU71r95Kza0LlJu3POH2BBPeWbooEa6BjOMSvKSo=; b=RPzXeEoc KwOZFbQTqaqmFMGHGKgMnqb0mxHBdwv+7huMonJaHUuo0MbMRhEw7uS/T+8xdsY9 MMReU9PWGCIcdJ1WhfB2d16T9W1YTaUa3p2dWII2HUiVBQkg0NjesOtfNXBio3gQ zXKMzHhV374W4Aje2z+A0P58N6LuOvndRqmX0o18AhI8DciaRfFuv/STQdmbhagv HT2OM3tFgdk7ffhnQ8J9yUJYb1qesaWuQSNyMisc17pHWUtR1LyfXQeuoDQBJ2Ei BATGExUW8j5LkCvssKdh8C+mDH9TeSDyR4PKV5TwvBDKtIPoi0HGlL0DXLH/jmGG U6+9791aEaA/CQ==
X-ME-Sender: <xms:QdMAWfF420_kwV1NVRiyGcC0BgIqMwIb1jnXxO0myJ_iJ-3YyjaOIA>
X-Sasl-enc: Cs8pMiCu2xNUHMGqA9UZ/JI8Enkfh8ZH1VIkBpP6Xyob 1493226305
Received: from [10.24.116.101] (unknown [128.107.241.169]) by mail.messagingengine.com (Postfix) with ESMTPA id 68A0C7E0A4; Wed, 26 Apr 2017 13:05:04 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <149158793224.11224.1489071223626497682@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 13:05:03 -0400
Cc: gen-art@ietf.org, draft-ietf-rtgwg-yang-key-chain.all@ietf.org, rtgwg@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <60BA3230-F2EF-4DDB-B9F0-694DBD674762@cooperw.in>
References: <149158793224.11224.1489071223626497682@ietfa.amsl.com>
To: Matthew Miller <linuxwolf+ietf@outer-planes.net>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/31vw94j_OXKX9M8i7qLH_iltPc0>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-rtgwg-yang-key-chain-17
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 17:05:08 -0000

Matt, thanks for your review. Authors, thanks for your engagement with =
Matt. I have ballotted no-objection.

Alissa

> On Apr 7, 2017, at 1:58 PM, Matthew Miller =
<linuxwolf+ietf@outer-planes.net> wrote:
>=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>.
>=20
> Document: draft-ietf-rtgwg-yang-key-chain-17
> Reviewer: Matthew A. Miller
> Review Date: 2017-04-07
> IETF LC End Date: 2017-04-07
> IESG Telechat date: 2017-04-13
>=20
> Summary:
>=20
> This document is almost ready to be published as a Proposed Standard,
> once the issues noted herein are resolved.
>=20
> Major issues:
>=20
> NONE
>=20
> Minor issues:
>=20
> * Forgive me for my limited knowledge of YANG, but is there a reason
> key-strings are only representable as either a YANG string or
> hex-string type, and not the YANG binary type?
>=20
> * This document does not provide much guidance around AES key wrap
> other than it can be used and the KEK is provided
> out-of-band/-context.
> For instance, AES key-wrapped key-strings probably require using
> "hexidecimal-string".  Also, assuming I'm reading the model
> correctly,
> it appears this feature applies to the whole chain, which I think is
> worth calling out.
>=20
> * This document warns against using the "clear-text" algorithm, which
> the
> reader is lead to understand is for legacy implementation reasons.
> However, is there not a similar concern with cryptographically weak
> algorithms, such as md5 and (arguably) sha1?
>=20
> Nits/editorial comments:
>=20
> * In Section 3.2. "Key Chain Model Features", the word "of" is
> missing
> between "configuration" and "an" in the phrase "support configuration
> an
> acceptance tolerance".
>=20
> Non-nits:
>=20
> * I note that idnits is calling out some odd spacing issues, but I
> think
> they are safe to ignore.
>=20
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 26 10:07:14 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAF5B129552; Wed, 26 Apr 2017 10:07:12 -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=qEu/NtAm; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=DbzTZaOz
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eOGlmr_7o93J; Wed, 26 Apr 2017 10:07:11 -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 0DD1D13151F; Wed, 26 Apr 2017 10:07:07 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 73B6E20A82; Wed, 26 Apr 2017 13:07:06 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 26 Apr 2017 13:07:06 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=CmwfLrsGG0E77orm2v LwCGijUOAfNGRlEbFVqEAGTYU=; b=qEu/NtAmKh4S9q2mH8FnRdQH4Wv1gogdfe q02qnuGTy3iUMjWoWeVGMfaRg7CQTfeo1T7XXYXtulyDartl07U8GWksw0zYM9ym kHegf0w7fDx1poDEDPoHwGc76oO/vT/mqLt2Glw1nDIWXrfCCHh4noKzgBYIZpab iO0bUd+v8Iov9zYkSrA5wUqTiUNCBHvc9T4DQQsrpxRBG9hUN3D9RRY1EsjpQXvP ScOJdigyF/9tfWAh/gshF73GbGpDHPApYPPkmEnKLDLXY9O5gKLWgS+ZoIgUoajR nJrO3/vAWCLPSk7bqLJQjrzCz9fximWkRjnpfXTtRmarLX3P9vRg==
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=CmwfLrsGG0E77orm2vLwCGijUOAfNGRlEbFVqEAGTYU=; b=DbzTZaOz Zemw8HP0PsRWz40RGcMqgK7bD61YQSslfK4UN6kbJ33LwUJATcBwzsjap9cAiNjZ Q+OV/yaSAf1FHy/fwcVrSPTSP/PJKyuaLBzoRsRP6pO5nGYDSx4RJivZiyYDnxaG fpqv819r8EKmfACjhc0IvZwUEQw+6Gx6FCXTa+5GHJtDVmKdiDrHtvB6eqN82JFZ /xflQqMUJKr4nshKxGBMGhCFewt5Te+ilBibGI+sEkwOQyxXgSQo4B+0pYZZv4lL YNM5eedMC+d7gtl2EQteVptNJaFo8IBiPusDf3bCUXRM2XHaGG6CnLIgx4lWlf2H sbsPgkPCxmFTOQ==
X-ME-Sender: <xms:utMAWUNAUAunt5bz-dJkHCHAdzue8QcHX_wjdVDQW-Q6v7g1rQmI0w>
X-Sasl-enc: 4DyybWUtGedBhl/jtDynx3RNpllPpvvPZRcxeGhWWg4J 1493226426
Received: from [10.24.116.101] (unknown [128.107.241.169]) by mail.messagingengine.com (Postfix) with ESMTPA id 930F17E6E3; Wed, 26 Apr 2017 13:07:05 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <48bebccb-4cf0-a218-38aa-af3fde41ad19@alum.mit.edu>
Date: Wed, 26 Apr 2017 13:07:04 -0400
Cc: draft-bchv-rfc6890bis.all@ietf.org, General Area Review Team <gen-art@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9402B2B5-4D15-4E66-B648-38382A8996C1@cooperw.in>
References: <48bebccb-4cf0-a218-38aa-af3fde41ad19@alum.mit.edu>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/a0aEWLvtWa2BrVQvXLoUuEiN-q0>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-bchv-rfc6890bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 17:07:13 -0000

Paul, thank you for your review! I have ballotted no-objection.

Alissa


> On Apr 22, 2017, at 3:23 PM, Paul Kyzivat <pkyzivat@alum.mit.edu> =
wrote:
>=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 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 =
<=E2=80=8Bhttp://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>=20
> Document: draft-bchv-rfc6890bis-06
> Reviewer: Paul Kyzivat
> Review Date: 2017-04-22
> IETF LC End Date: 2017-03-10
> IESG Telechat date: 2017-04-25
>=20
> Summary:
>=20
> This draft is basically ready for publication, but has nits that =
should be fixed before publication.
>=20
> General Comments:
>=20
> This version is *much* easier to understand than the -04 version that =
I previously reviewed.
>=20
> Issues:
>=20
> Major: 0
> Minor: 0
> Nits:  1
>=20
> (1) Nit:
>=20
> In section 2.3 the requested handling of footnotes is confusing.
> IIUC, the intent is:
>=20
> - add a new footnote between the existing [1] and [2];
>=20
> - add a new footnote at the end after the existing [5];
>=20
> - renumber the footnotes sequentially (from [1] to [7]);
>=20
> - adjust all the existing footnote references to refer to the same
>  footnote as previously, but using the new numbering;
>=20
> - then, add references to the new footnotes [2] and [7] to the entries
>  for TEREDO and Unique-Local.
>=20
> It took me a few readings of the current text to convince myself that =
is what you intended. It would be better to be more explicit about it.
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 26 10:12:24 2017
Return-Path: <linuxwolf+ietf@outer-planes.net>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D71A12EE44; Wed, 26 Apr 2017 10:12:10 -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: draft-ietf-rtgwg-yang-key-chain.all@ietf.org, ietf@ietf.org, rtgwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149322673002.13018.17056147061701748095@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 10:12:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/YksS10J0a-2TDQ1BIQWfwblahUk>
Subject: [Gen-art] Genart telechat review of draft-ietf-rtgwg-yang-key-chain-20
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 17:12:10 -0000

Reviewer: Matthew Miller
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-rtgwg-yang-key-chain-??
Reviewer: Matthew Miller
Review Date: 2017-04-26
IETF LC End Date: 2017-04-07
IESG Telechat date: 2017-04-27

Summary:

This document is ready to be published as Proposed Standard.  This
version (-20) addresses all concerns raised in the review of a
previous version (-17).

Major issues: NONE

Minor issues: NONE

Nits/editorial comments:  NONE



From nobody Wed Apr 26 10:13:07 2017
Return-Path: <adam@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9432712955D; Wed, 26 Apr 2017 10:12:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level: 
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CsqE8Dichnhf; Wed, 26 Apr 2017 10:12:54 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACCBB131544; Wed, 26 Apr 2017 10:12:54 -0700 (PDT)
Received: from Orochi.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id v3QHCgq7059727 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 26 Apr 2017 12:12:43 -0500 (CDT) (envelope-from adam@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Orochi.local
To: Elwyn Davies <elwynd@dial.pipex.com>, gen-art@ietf.org
Cc: ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <20e3b49f-4868-bc4e-baa9-ec777fdf34f2@nostrum.com>
Date: Wed, 26 Apr 2017 12:12:37 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <149315879365.13684.3263173090290877403@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/b1y3YouB9AL3jA5pHU3O-F1q54A>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-core-links-json-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 17:12:56 -0000

On 4/25/17 17:19, Elwyn Davies wrote:
> >From JSON to RFC 6690: 
> - Remove the double quotes from the JSON string value and do any
> necessary decoding and encoding.  Reapply double quotes.  Note that
> this may result in values that were originally not enclosed in double
> quotes in the RFC 6690 repreentation becoming enclosed in double
> quotes. However, [AFAICS] this does not alter the semantics of any of
> the predefined parameters.  For example the ABNF productions mean that
> ct=40 and ct="40" are equivalent (the second case is needed so that
> one can also have ct="40 41 42").  What IS needed is a statement that
> this must also apply to any application specific parameters.  For
> example the case in examples 4 and 5 of ..;foo="bar";foo=3;...
> transforming to "foo":["bar","3"] and then back to
> ...;foo="bar";foo="3";.. MUST require that the two RFC 6690
> representations are equivalent.


This has the reciprocal problem that using quotes with (e.g.) sz and 
hreflang is a violation of the ABNF in RFC6690.

/a


From nobody Wed Apr 26 10:20:05 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82AD2131500; Wed, 26 Apr 2017 10:20:02 -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=GQemiDGA; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=djBvRg06
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4rtXNz2S1bL7; Wed, 26 Apr 2017 10:20:01 -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 E455B1314CA; Wed, 26 Apr 2017 10:20:00 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 5879421AE9; Wed, 26 Apr 2017 13:20:00 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Wed, 26 Apr 2017 13:20:00 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; 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=CmG74M5yLRQIOVHQe1 tdNMJimFLjUmtXEaSfTRhszhU=; b=GQemiDGAKq0vz0XMnshGg9G47TSRycG5jT 0SOeAnI5Rge6gZrbO1efIzYN7aZ9XT25l7ZN2+utOjuXD/DTqFLh69Ar85hwbX9X BkNCpmoF3TziMhyUdx9hNRO2oJWDVrBMjdUlwA5jxHxfByQgfyRYf+nzKYbfB6pa Vou0zNaslzErJaWvLWZv13ied87d3DTwID4Gdc+SEkQ7RXmXgxo74U9vTbxzKofW SLIx9UJtTwR8V7THxBrTHbWmabovqPs/rCl6IJGkFNtoTMpJ1nGBxiQ9BJJELisL ATJp0h0a9orrEFeBibi0XWK1w2/aPRqQ10g3qviqIz88IzuReqMg==
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=CmG74M5yLRQIOVHQe1tdNMJimFLjUmtXEaSfTRhszhU=; b=djBvRg06 bphBr0INyzDBsUQ5J8tEkVr502JYE4m0Cs558SbPup2FOXX1LeSnhfEjmVPyQYx6 l1RBEGhYlXXkwzLYPGiMn+jXoiHY6ZAK+cmwNAorv/RS1CwDY1lzvS33Bgn6FG0p e499U4+KOgwbQXzatDujoIO5qd7JVGo1opIrFPSaSlbNOPjCVAvJYZHcscIGz49s lpQcRK3rHPOXR2zhVaYRn7p3KMFMDfleGe+kF1g55z8+FcXHq718HbLmwbaGRRwZ MymJrKBu1ElbrOyy4MHP7bbgCdtI1zTU6dSbE96A3z2Dy8bfPvnpjJdmUZ72BoQl azNOUdzrymBaxg==
X-ME-Sender: <xms:wNYAWRQ_4TeiYWayl-Ld_RaTBrlbxpjBeqKlDCqkrku6yw04N9kvtg>
X-Sasl-enc: Si42MChYfH/hPJduUUF0y4HQxzKL8Seb28hPCS6Tmmy1 1493227200
Received: from [10.24.116.101] (unknown [128.107.241.169]) by mail.messagingengine.com (Postfix) with ESMTPA id 608787E70C; Wed, 26 Apr 2017 13:19:59 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <149015426220.3518.3546300688917567228@ietfa.amsl.com>
Date: Wed, 26 Apr 2017 13:19:58 -0400
Cc: General Area Review Team <gen-art@ietf.org>, sipcore@ietf.org, draft-ietf-sipcore-status-unwanted.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DFF9921A-7F19-463D-A9CC-D2553643AB4F@cooperw.in>
References: <149015426220.3518.3546300688917567228@ietfa.amsl.com>
To: Peter Yee <peter@akayla.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/wE2neXwxcRaVf6a4QNhAWGfe3Es>
Subject: Re: [Gen-art] Review of draft-ietf-sipcore-status-unwanted-04
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 17:20:03 -0000

Peter, thanks for your review. Henning, thanks for taking the changes =
into account. I have ballotted no-objection.

Alissa


> On Mar 21, 2017, at 11:44 PM, Peter Yee <peter@akayla.com> wrote:
>=20
> Reviewer: Peter Yee
> Review result: Ready with Nits
>=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-sipcore-status-unwanted-04
> Reviewer: Peter Yee
> Review Date: 2017-03-21
> IETF LC End Date: 2017-03-21
> IESG Telechat date: Not scheduled for a telechat
>=20
> Summary: This draft specifies a SIP response code for the callee to
> indicate that the call is unwanted.  It goes to great lengths to
> specify what may be done as a result of sending this response code,
> all the while mandating nothing.
>=20
> The document has a couple of nits, but nothing seriously wrong.=20
> [Ready with nits]
>=20
> Major issues: None
>=20
> Minor issues: None
>=20
> Nits/editorial comments:=20
>=20
> Page 4, 1st full paragraph, 2nd sentence: I can't parse this sentence
> as written.  It appears to be a list, but then has a clause (starting
> at "based on") that doesn't fit neatly in the sequence.  Perhaps
> inserting "and" before "based" would help.  Append "as" after "well".
>=20
> Page 5, Section 6, 2nd paragraph, 1st sentence: change "extract" to
> "exact".
>=20
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art


From nobody Wed Apr 26 11:21:15 2017
Return-Path: <cabo@tzi.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EE9C13156A; Wed, 26 Apr 2017 11:20: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, 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 4yTDYMOUd1-9; Wed, 26 Apr 2017 11:20:55 -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 40982131565; Wed, 26 Apr 2017 11:20:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3QIKnc6028132; Wed, 26 Apr 2017 20:20:49 +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 3wCpKs0RWgzDH41; Wed, 26 Apr 2017 20:20:49 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <20e3b49f-4868-bc4e-baa9-ec777fdf34f2@nostrum.com>
Date: Wed, 26 Apr 2017 20:20:47 +0200
Cc: Elwyn Davies <elwynd@dial.pipex.com>, gen-art@ietf.org, IETF <ietf@ietf.org>, core <core@ietf.org>, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514923647.182059-f87b135b40f402b437f2bb96c0d3467d
Content-Transfer-Encoding: quoted-printable
Message-Id: <E6D9E89E-2D94-401C-9B00-84CE7E36657C@tzi.org>
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com> <20e3b49f-4868-bc4e-baa9-ec777fdf34f2@nostrum.com>
To: Adam Roach <adam@nostrum.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/83mgqE8QbO5Yx5FFuY-HEmoYB1o>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-core-links-json-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 18:20:58 -0000

On Apr 26, 2017, at 19:12, Adam Roach <adam@nostrum.com> wrote:
>=20
> This has the reciprocal problem that using quotes with (e.g.) sz and =
hreflang is a violation of the ABNF in RFC6690.

Yes.  Using ABNF for the serialization of an item that should be =
described at the data model level (as in 5988bis) is now generally =
considered a mistake.  To stay compatible with the letter of RFC 6690 =
(which probably continues to be a good idea), the reference =
implementation in Appendix A of links-json uses the quote-less form =
whenever the value is a ptoken, i.e. a sequence of one or more =
ptokenchar characters(*).  Should we require this, and if yes, should =
this be a SHOULD or a MUST?

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

(*)
    ptoken         =3D 1*ptokenchar
    ptokenchar     =3D "!" / "#" / "$" / "%" / "&" / "'" / "("
                   / ")" / "*" / "+" / "-" / "." / "/" / DIGIT
                   / ":" / "<" / "=3D" / ">" / "?" / "@" / ALPHA
                   / "[" / "]" / "^" / "_" / "`" / "{" / "|"
                   / "}" / "~"


From nobody Wed Apr 26 11:35:51 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07FF4131586; Wed, 26 Apr 2017 11:35:43 -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 XcqK_u85ov-y; Wed, 26 Apr 2017 11:35:40 -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 B1782131582; Wed, 26 Apr 2017 11:35:40 -0700 (PDT)
Received: from [128.9.184.33] ([128.9.184.33]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v3QIZDKk005153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 26 Apr 2017 11:35:13 -0700 (PDT)
To: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org
Cc: ipv6@ietf.org, ietf@ietf.org, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu>
Date: Wed, 26 Apr 2017 11:35:12 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <a974da1d-a9e7-8c64-8086-0955f2dffb12@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/gen-art/htbPTP2m_6JT39VB9StjMwKzWaM>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 18:35:43 -0000

Hi, Stewart,


On 4/26/2017 1:48 AM, Stewart Bryant wrote:
>
>
> On 25/04/2017 19:26, Joe Touch wrote:
>> Hi, Stewart,
>>
>> ...
>>
>>> SB>
>>> SB> Otherwise I would have thought that this was entirely a matter
>>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>>> SB> link minimum. Nothing breaks if the host takes a more conservative
>>> SB> decision.
>> I don't agree; the host at that point is violating RFC2460. It should
>> never think that an IPv6 link or path with an MTU below what RFC2460
>> requires is valid.
>>
>> Joe
>>
>
> That is as maybe, but a host can do more or less what it wants, so
> this is surely an
> unenforceable constraint, or are you telling me that the receiving
> host MUST drop a
> fragment that is shorter than this? In which case the question whether
> in practice
> they do, and whether such a constraint is reasonable.

A "path MTU" is a value calculated from information from various sources
(attached links, ICMP messages, and perhaps other information), but IMO
it's never appropriate to set a "path MTU" smaller than the limit
established by IPv6 for a single link.

Individual packets and fragments can be smaller than the MTU, of course.
Nothing forces fragments to push up against any MTU limit at all. But I
would not describe that has a host changing its path MTU; it's just
sending packets.

Joe


From nobody Wed Apr 26 13:09:00 2017
Return-Path: <fredbaker.ietf@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5ABA12EB55; Wed, 26 Apr 2017 13:08:38 -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 Wxfv12-ExCL2; Wed, 26 Apr 2017 13:08:37 -0700 (PDT)
Received: from mail-wr0-x241.google.com (mail-wr0-x241.google.com [IPv6:2a00:1450:400c:c0c::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 925CB1294A9; Wed, 26 Apr 2017 13:08:31 -0700 (PDT)
Received: by mail-wr0-x241.google.com with SMTP id g12so1450040wrg.2; Wed, 26 Apr 2017 13:08:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Zjkl0qMkyaeqzgOEKMUFJke58SC/VxzeNgHcnRnjEp0=; b=Ai/urVsadKiIfFc6DOvBt563jFnPvN0xV4kTW14eAA5w2aoUYKHsG6UysZW6RCNdjl it9eBmgWpfqdumyzKJU0JnsdO8KVHkG/Fvx2KfLlF/mswmu4wU49XhznVKZOxrxwomKZ BfuT7/wcMR6G/0Gh2afvMzfyxhHbG3kDX1bWPSMc0WOn/85Tke6DCMqJxl4nxPe9wNHL VfTRcsr34/6g4fGKimDMCmunu13xs7SgTc5FVgbXyDQhT4FeR4x+pIDBRsWIP3kDrKT7 D7hOKIqRNqFts6NZReAKFujY8JuoPwaEq4z7sU1jYfA0krr391veCHWS3v4sArR2+KeZ RP7Q==
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=Zjkl0qMkyaeqzgOEKMUFJke58SC/VxzeNgHcnRnjEp0=; b=Bju76Gica9+F0AH9R1ABK11P9S3Obf8C8krFHIUf+OZ1N16ZRjrKxA6t9vISWcBwdG s6voANOYt3ud3aUA/GqwQ5o/laI79Cawc9+6mDNtpkTi6vUZAxmK03ot01JRTRZ63uDv aj8deDH+dv7d7kHvvK65VLVJ5YMkUsWaCltSD2EqQ0OIAMn4OBr7JeM2aodc2PvQ+Eze wya0CbIadG5V0yvCX4KUos8t/8U77/NPz33O9q0+nptxs3bZgo2Zbsf/Bl/ycx/lqNR4 kAls4T8JpDfwi9sQkkdk4wrrGjC+rmt9eGiXcnQ4h7RahgTgFsRPPjy/112SkfNn9TeT TbnA==
X-Gm-Message-State: AN3rC/4usKrtpzWbHh1OPG4u9RO73sBHOmpCrVVux7TOqExoMs9FwICn AqOVQS3Yaw83CVoOSAM=
X-Received: by 10.223.154.240 with SMTP id a103mr1018926wrc.5.1493237310104; Wed, 26 Apr 2017 13:08:30 -0700 (PDT)
Received: from 202.66.20.149.in-addr.arpa (202.66.20.149.in-addr.arpa. [149.20.66.202]) by smtp.gmail.com with ESMTPSA id 39sm280734wru.50.2017.04.26.13.08.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 13:08:29 -0700 (PDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu>
Date: Wed, 26 Apr 2017 13:08:25 -0700
Cc: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/0BGhFBnrAOUi2UNTvw5oQrsxFx0>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:08:39 -0000

> On Apr 26, 2017, at 11:35 AM, Joe Touch <touch@isi.edu> wrote:
>=20
> Hi, Stewart,
>=20
>=20
> On 4/26/2017 1:48 AM, Stewart Bryant wrote:
>>=20
>>=20
>> On 25/04/2017 19:26, Joe Touch wrote:
>>> Hi, Stewart,
>>>=20
>>> ...
>>>=20
>>>> SB>
>>>> SB> Otherwise I would have thought that this was entirely a matter
>>>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>>>> SB> link minimum. Nothing breaks if the host takes a more =
conservative
>>>> SB> decision.
>>> I don't agree; the host at that point is violating RFC2460. It =
should
>>> never think that an IPv6 link or path with an MTU below what RFC2460
>>> requires is valid.
>>>=20
>>> Joe
>>>=20
>>=20
>> That is as maybe, but a host can do more or less what it wants, so
>> this is surely an
>> unenforceable constraint, or are you telling me that the receiving
>> host MUST drop a
>> fragment that is shorter than this? In which case the question =
whether
>> in practice
>> they do, and whether such a constraint is reasonable.
>=20
> A "path MTU" is a value calculated from information from various =
sources
> (attached links, ICMP messages, and perhaps other information), but =
IMO
> it's never appropriate to set a "path MTU" smaller than the limit
> established by IPv6 for a single link.

You are, of course, quoting RFC 1981:
   A node MUST NOT reduce its estimate of the Path MTU below the IPv6
   minimum link MTU.

> Individual packets and fragments can be smaller than the MTU, of =
course.
> Nothing forces fragments to push up against any MTU limit at all. But =
I
> would not describe that has a host changing its path MTU; it's just
> sending packets.

I disagree, both on the definition and the action. You are correct in =
"how the Path MTU is calculated". But the Path MTU, by definition, is =
the largest packet that can be sent end to end under current routing =
conditions. It is not, actually, an IP concept: it's a TCP concept if =
anything, or a transport layer concept (if UDP ever decides to have =
one). I can imagine TCP probing the Path MTU by trying packets that are =
larger than its current estimate to see if the estimate is still =
accurate (1981 section 4), but I can't imagine any reason that TCP would =
send packets larger than the "largest packet that can be sent end to end =
under current routing conditions" in the normal case, as those packets =
will by definition either be fragmented or not arrive.


From nobody Wed Apr 26 13:18:48 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D48EE13144C; Wed, 26 Apr 2017 13:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 FtEpxc8LSQFm; Wed, 26 Apr 2017 13:18:39 -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 440E21314D6; Wed, 26 Apr 2017 13:18:25 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v3QKIBwB000870 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 26 Apr 2017 13:18:11 -0700 (PDT)
To: Fred Baker <fredbaker.ietf@gmail.com>
Cc: Stewart Bryant <stewart.bryant@gmail.com>, gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu> <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <b1a1dba3-4d8f-4fb7-984f-5fd4689069f9@isi.edu>
Date: Wed, 26 Apr 2017 13:18:11 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
Content-Type: multipart/alternative; boundary="------------9304196B38F0127139E7B07B"
Content-Language: en-US
X-MailScanner-ID: v3QKIBwB000870
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/DwgcK5uZH4S2Em7ONd--BfYvRg8>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:18:42 -0000

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

Hi, Fred,


On 4/26/2017 1:08 PM, Fred Baker wrote:
>> Individual packets and fragments can be smaller than the MTU, of course.
>> Nothing forces fragments to push up against any MTU limit at all. But I
>> would not describe that has a host changing its path MTU; it's just
>> sending packets.
> I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). 
While it might apply differently based on port-based routing, path MTU
is an IP concept. It sets IP limits (MTU is an IP-ism, including all its
variants, such as EMTU_S, EMTUR, etc. - from RFC1122), which then
cascades into TCP limits (MSS and MMS_*, again per RFC1122).

And it's not the largest packet - it's strictly the largest IP fragment.
Transport uses that as the limit on IP messages to avoid fragmentation.
Technically, though, PMTU could also be used by the IP layer to guide
source fragmentation if the transport layer presents messages that are
too large to fit in a single datagram.

> I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.
TCP probably wouldn't, but UDP can, would, and does.

Joe



--------------9304196B38F0127139E7B07B
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">
    <p>Hi, Fred,<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 4/26/2017 1:08 PM, Fred Baker wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com">
      <blockquote type="cite" style="color: #000000;">
        <pre wrap="">Individual packets and fragments can be smaller than the MTU, of course.
Nothing forces fragments to push up against any MTU limit at all. But I
would not describe that has a host changing its path MTU; it's just
sending packets.
</pre>
      </blockquote>
      <pre wrap="">I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). </pre>
    </blockquote>
    While it might apply differently based on port-based routing, path
    MTU is an IP concept. It sets IP limits (MTU is an IP-ism, including
    all its variants, such as EMTU_S, EMTUR, etc. - from RFC1122), which
    then cascades into TCP limits (MSS and MMS_*, again per RFC1122). <br>
    <br>
    And it's not the largest packet - it's strictly the largest IP
    fragment. Transport uses that as the limit on IP messages to avoid
    fragmentation. Technically, though, PMTU could also be used by the
    IP layer to guide source fragmentation if the transport layer
    presents messages that are too large to fit in a single datagram.<br>
    <br>
    <blockquote type="cite"
      cite="mid:99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com">
      <pre wrap="">I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.</pre>
    </blockquote>
    TCP probably wouldn't, but UDP can, would, and does.<br>
    <br>
    Joe<br>
    <pre wrap="">
</pre>
    <br>
  </body>
</html>

--------------9304196B38F0127139E7B07B--


From nobody Wed Apr 26 13:30:34 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 606FF12778D; Wed, 26 Apr 2017 13:30:16 -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 yVwXCARIihF3; Wed, 26 Apr 2017 13:30:13 -0700 (PDT)
Received: from mail-pf0-x243.google.com (mail-pf0-x243.google.com [IPv6:2607:f8b0:400e:c00::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 98562127342; Wed, 26 Apr 2017 13:30:13 -0700 (PDT)
Received: by mail-pf0-x243.google.com with SMTP id c198so2441387pfc.0; Wed, 26 Apr 2017 13:30:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=ymWQklo4o9ij64ii/b86yWzGhaOzaFyAGJZ/J4JYBLE=; b=sQeaVh2FsTQDRk20qfOBW1igbOt+ANsnOafDOcPDBPvsTXc8+0dKeXdiaViPn+SmYo 3X5D62xxbKresEHJpzsCAQer6bx8vQeVHut0OHBMytple68v0kt8m6B05uBisj8RzKEB 770QN5f1FeCepeoKCRUF8ZoJu2di0FZ9rqEkQe1LWc+3bot5r+9ln0gnRfViYgJe60VD L8yR329zH0wGELlfD7nYLIvHMiBu4juR9DxZipIBhwX8KP17TIdTv+X/4Gt3IrIlBQIt 9P4L4dzeCCqN1q1/s4hCfL+bVqkeHeDEYyBDjMYNwC5/LNMPrzfFrGcwXMGWLn7/+0Ne fWYQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=ymWQklo4o9ij64ii/b86yWzGhaOzaFyAGJZ/J4JYBLE=; b=DBWpTLnsL9qR0N4Vtf9pMGyt+oPo410S54a3dbGaUDDpNsamK28XE7pChlR8tEUxfB 5xTt6bfgPBYbkEWOKTvZh6sw8Ps2s2sWnZkbwCt4agpAHJdeoMtgFfgtMMQeTOVInthb uS0msE6V9DLd3kvbapSXFb3tTDEByB7wYuomO8vo4uAEaQ0gWnTI9Lolg2JszGX3cVDT XmzlSVE3tEhfGfOkOiXxPXMw+52rxTzKGEWuhaM4Onm6t2slLee0P7ca8scCHqJrej7W iYVFPOaNpPkeecL9OF0I11IpzRLkRusf0tFJnBp3Ohk26mJyyyHpe7+8JTCdaTYGm7Y7 8SOA==
X-Gm-Message-State: AN3rC/540o9QkrrRT6bTmNvL0DbVW5IwVAf3Kxrg+IP2biZSs/QvtVOU dDlfKTqz6xnQ3A==
X-Received: by 10.84.217.215 with SMTP id d23mr2189439plj.59.1493238613087; Wed, 26 Apr 2017 13:30:13 -0700 (PDT)
Received: from [192.168.178.21] ([118.149.100.28]) by smtp.gmail.com with ESMTPSA id 17sm259899pgg.48.2017.04.26.13.30.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 26 Apr 2017 13:30:12 -0700 (PDT)
To: Fred Baker <fredbaker.ietf@gmail.com>, Joe Touch <touch@isi.edu>
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu> <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
Cc: gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com>
Date: Thu, 27 Apr 2017 08:30:12 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/icCIr-4lqXwYBxfu-I4vbWy_Xic>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:30:16 -0000

On 27/04/2017 08:08, Fred Baker wrote:
> 
>> On Apr 26, 2017, at 11:35 AM, Joe Touch <touch@isi.edu> wrote:
>>
>> Hi, Stewart,
>>
>>
>> On 4/26/2017 1:48 AM, Stewart Bryant wrote:
>>>
>>>
>>> On 25/04/2017 19:26, Joe Touch wrote:
>>>> Hi, Stewart,
>>>>
>>>> ...
>>>>
>>>>> SB>
>>>>> SB> Otherwise I would have thought that this was entirely a matter
>>>>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>>>>> SB> link minimum. Nothing breaks if the host takes a more conservative
>>>>> SB> decision.
>>>> I don't agree; the host at that point is violating RFC2460. It should
>>>> never think that an IPv6 link or path with an MTU below what RFC2460
>>>> requires is valid.
>>>>
>>>> Joe
>>>>
>>>
>>> That is as maybe, but a host can do more or less what it wants, so
>>> this is surely an
>>> unenforceable constraint, or are you telling me that the receiving
>>> host MUST drop a
>>> fragment that is shorter than this? In which case the question whether
>>> in practice
>>> they do, and whether such a constraint is reasonable.
>>
>> A "path MTU" is a value calculated from information from various sources
>> (attached links, ICMP messages, and perhaps other information), but IMO
>> it's never appropriate to set a "path MTU" smaller than the limit
>> established by IPv6 for a single link.
> 
> You are, of course, quoting RFC 1981:
>    A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>    minimum link MTU.
> 
>> Individual packets and fragments can be smaller than the MTU, of course.
>> Nothing forces fragments to push up against any MTU limit at all. But I
>> would not describe that has a host changing its path MTU; it's just
>> sending packets.
> 
> I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.

istm that the robustness principle argues for what Fred is saying. Yes, any path that doesn't transmit 1280 byte packets is breaking the law, but (given that the protocol police do such a lousy job) if the objective fact is that the path only transmits 1279 byte packets, what's best for the user?

    Brian


From nobody Wed Apr 26 13:34:15 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84CFE1294AB; Wed, 26 Apr 2017 13:34: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, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ulEldP2NKcW2; Wed, 26 Apr 2017 13:34:06 -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 1BAE9129464; Wed, 26 Apr 2017 13:34:06 -0700 (PDT)
Received: from [128.9.160.211] (mul.isi.edu [128.9.160.211]) (authenticated bits=0) by nitro.isi.edu (8.13.8/8.13.8) with ESMTP id v3QKXrTa006565 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 26 Apr 2017 13:33:53 -0700 (PDT)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Fred Baker <fredbaker.ietf@gmail.com>
Cc: gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu> <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com> <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <c1888839-94fb-437c-a9af-e8309308cc8b@isi.edu>
Date: Wed, 26 Apr 2017 13:33:53 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com>
Content-Type: multipart/alternative; boundary="------------7459DC2F1AB0CBA15FBD1564"
Content-Language: en-US
X-MailScanner-ID: v3QKXrTa006565
X-ISI-4-69-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/MTj9umHyCWoPgJsp6jnpsNbSnHw>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Apr 2017 20:34:08 -0000

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



On 4/26/2017 1:30 PM, Brian E Carpenter wrote:
>>> Individual packets and fragments can be smaller than the MTU, of course.
>>> Nothing forces fragments to push up against any MTU limit at all. But I
>>> would not describe that has a host changing its path MTU; it's just
>>> sending packets.
>> I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.
> istm that the robustness principle argues for what Fred is saying. Yes, any path that doesn't transmit 1280 byte packets is breaking the law, but (given that the protocol police do such a lousy job) if the objective fact is that the path only transmits 1279 byte packets, what's best for the user?
IMO, the best thing is to loudly flag the path as no longer valid.

Either we have required minimums or not. If not, then we have a LOT of
new work to do.

Joe


--------------7459DC2F1AB0CBA15FBD1564
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">
    <p><br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 4/26/2017 1:30 PM, Brian E Carpenter
      wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com">
      <blockquote type="cite" style="color: #000000;">
        <blockquote type="cite" style="color: #000000;">
          <pre wrap="">Individual packets and fragments can be smaller than the MTU, of course.
Nothing forces fragments to push up against any MTU limit at all. But I
would not describe that has a host changing its path MTU; it's just
sending packets.
</pre>
        </blockquote>
        <pre wrap="">I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.
</pre>
      </blockquote>
      <pre wrap="">istm that the robustness principle argues for what Fred is saying. Yes, any path that doesn't transmit 1280 byte packets is breaking the law, but (given that the protocol police do such a lousy job) if the objective fact is that the path only transmits 1279 byte packets, what's best for the user?</pre>
    </blockquote>
    IMO, the best thing is to loudly flag the path as no longer valid.<br>
    <br>
    Either we have required minimums or not. If not, then we have a LOT
    of new work to do.<br>
    <br>
    Joe<br>
    <br>
  </body>
</html>

--------------7459DC2F1AB0CBA15FBD1564--


From nobody Thu Apr 27 05:30:41 2017
Return-Path: <cabo@tzi.org>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B685129463; Thu, 27 Apr 2017 05:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 nqUhh2g3iTSg; Thu, 27 Apr 2017 05:30:37 -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 DF56A1273B1; Thu, 27 Apr 2017 05:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::b]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id v3RCURe0018959; Thu, 27 Apr 2017 14:30:27 +0200 (CEST)
Received: from client-0199.vpn.uni-bremen.de (client-0199.vpn.uni-bremen.de [134.102.107.199]) (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 3wDGW70pv5zDHMX; Thu, 27 Apr 2017 14:30:27 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <720C9B43-B803-4C99-A366-3C79F463FB23@tzi.org>
Date: Thu, 27 Apr 2017 14:30:26 +0200
Cc: gen-art@ietf.org, ietf@ietf.org, core@ietf.org, draft-ietf-core-links-json.all@ietf.org
X-Mao-Original-Outgoing-Id: 514989026.323576-92920dfcf09ad9fd924409fa3dea0ae4
Content-Transfer-Encoding: quoted-printable
Message-Id: <218E712A-7379-4764-B59A-FD0A186F4520@tzi.org>
References: <149315879365.13684.3263173090290877403@ietfa.amsl.com> <720C9B43-B803-4C99-A366-3C79F463FB23@tzi.org>
To: Elwyn Davies <elwynd@dial.pipex.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Rsr7EMPO0xXOMj8txJtwegciH3o>
Subject: Re: [Gen-art] [core] Genart last call review of draft-ietf-core-links-json-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 12:30:39 -0000

Hi Elwyn,

we tried one round at your comments.

We didn=E2=80=99t tackle the interaction with /.well-known/core =E2=80=94 =
I continue to believe what I said yesterday, but we still have to find a =
good way to put this into the document.

We added a note that we need to decide whether there is an onus on a =
receiving CBOR implementation to check for the absence of the 13 strings =
as names (=E2=80=9CAdam=E2=80=99s second issue=E2=80=9D).

The title* issue also requires some more thinking =E2=80=94 do we even =
want to have language tags on a constrained device.  Right now, the =
document simply leaves the whole subject out, but probably needs a =
position on that.

Finally, there is the issue that RFC 6690 percent-decodes and how that =
should be reflected in the JSON and CBOR variants.

We added a whole subsection on converting back to RFC 6690, which =
discusses the current pragmatic approach on solving the =E2=80=9Cto =
quote or not to quote=E2=80=9D issue.

On the editorial side, we addressed the document title, added some =
language to make it clear that the CDDL is informative (and actually =
added build tool rules to check the examples against the CDDL, ouch), =
and quite a few nits.  Thank you for the text suggestions (and no, we =
didn=E2=80=99t add a reference to X.690 yet :-).  Based on Adam=E2=80=99s =
suggestions, we found a way to fix the bullet list in 2.2.

We still need to review the editorial comments on the detailed =
processing of strings etc. (see may previous comments why these didn=E2=80=
=99t just drop in).

Please have a look at the new text at:

https://tools.ietf.org/rfcdiff?url2=3Ddraft-ietf-core-links-json-08.txt

Thank you!

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


From nobody Thu Apr 27 05:36:38 2017
Return-Path: <stewart.bryant@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2D0A127909; Thu, 27 Apr 2017 05:36:36 -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 tidE2CuCJ5qs; Thu, 27 Apr 2017 05:36:34 -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 8EB0D126B7F; Thu, 27 Apr 2017 05:36:34 -0700 (PDT)
Received: by mail-wr0-x242.google.com with SMTP id v42so3630544wrc.3; Thu, 27 Apr 2017 05:36:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=5VudjgTR5zvQXsq5QUfqINOO5xHr5CN60JUHEd4AQzc=; b=oOo9XLx2hviC5JdIn/usK3Tb55cNEHmC7gztnhPPd611GAMDWWRA4EAWOuLKGxunTj 0qNs8hpFCAPrvRplPJi2hR6gcFq/uHT4tf4DJAUUE48NU8z5fPUp780jnVgssGFwrumE xZ1gc6RUZ/iF3aGODy3ulFAiljtRQ+pC+X8N3L/QZsLpqActVx8Xp/tfeJOvl1kpR1c1 9bGv2VILBv6eQo9zNq02pm7fQCaBDSXM3rEHAN93II82iMRtq1Zy9+jthv9vRiamXoe0 XT8zeuPMFlILbQ44SVLLeMDLN2l+ThLfH/qyLdF7H74IPFUEPlJUia7HOtJQ6tQXdWvQ mAsA==
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=5VudjgTR5zvQXsq5QUfqINOO5xHr5CN60JUHEd4AQzc=; b=SjZP/3Umm8t7Qa0oGjCxkbd+RMy6s0UtZPvfFwzSOy2nq8UTE2l6uXJXFq4BEbAxmk 1kNZTVqJBKOwL1yLGdbWb/KNVjM03UKEtC89cMPIgQAJ7SpZ3sQy2lLW0toft+PGiB6y XD13BJ2DJ6Gnyt1F9990cpJeq7+IBh7knqY/FXqly0bCrOSHXnEJKtPx0ld01pDRtbge JAHhicuBW2bJ3I+ScsZL4KlEq0rEzmwc05SDBzqqOANtig8xhs8PeAxh9JQmDaprZSU/ LOs+9fHe8fuQPU2IPA2AmwW/9FsLAoxeeQWd9l1koqjCtXccAJHJHRGa1VBVlUnllOd9 NmpQ==
X-Gm-Message-State: AN3rC/4pgIHaPxfz5VZoBzJbk1w9D6bj6Iy+4DsiVKCjjdsJbqOvQj24 IMlFa7M7yknPvA==
X-Received: by 10.223.162.147 with SMTP id s19mr3355901wra.142.1493296592995;  Thu, 27 Apr 2017 05:36:32 -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 i199sm3164441wmf.33.2017.04.27.05.36.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 27 Apr 2017 05:36:32 -0700 (PDT)
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Fred Baker <fredbaker.ietf@gmail.com>, Joe Touch <touch@isi.edu>
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu> <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com> <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com>
Cc: gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <8fdddab8-dba8-d151-6552-882d2c9a7918@gmail.com>
Date: Thu, 27 Apr 2017 13:36:25 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/nZQNsa6QX8jHa0WD-Q0I1PTivTM>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 12:36:37 -0000

On 26/04/2017 21:30, Brian E Carpenter wrote:
> On 27/04/2017 08:08, Fred Baker wrote:
>>> On Apr 26, 2017, at 11:35 AM, Joe Touch <touch@isi.edu> wrote:
>>>
>>> Hi, Stewart,
>>>
>>>
>>> On 4/26/2017 1:48 AM, Stewart Bryant wrote:
>>>>
>>>> On 25/04/2017 19:26, Joe Touch wrote:
>>>>> Hi, Stewart,
>>>>>
>>>>> ...
>>>>>
>>>>>> SB>
>>>>>> SB> Otherwise I would have thought that this was entirely a matter
>>>>>> SB> for the host whether it wanted to use a Path MTU below the IPv6
>>>>>> SB> link minimum. Nothing breaks if the host takes a more conservative
>>>>>> SB> decision.
>>>>> I don't agree; the host at that point is violating RFC2460. It should
>>>>> never think that an IPv6 link or path with an MTU below what RFC2460
>>>>> requires is valid.
>>>>>
>>>>> Joe
>>>>>
>>>> That is as maybe, but a host can do more or less what it wants, so
>>>> this is surely an
>>>> unenforceable constraint, or are you telling me that the receiving
>>>> host MUST drop a
>>>> fragment that is shorter than this? In which case the question whether
>>>> in practice
>>>> they do, and whether such a constraint is reasonable.
>>> A "path MTU" is a value calculated from information from various sources
>>> (attached links, ICMP messages, and perhaps other information), but IMO
>>> it's never appropriate to set a "path MTU" smaller than the limit
>>> established by IPv6 for a single link.
>> You are, of course, quoting RFC 1981:
>>     A node MUST NOT reduce its estimate of the Path MTU below the IPv6
>>     minimum link MTU.
>>
>>> Individual packets and fragments can be smaller than the MTU, of course.
>>> Nothing forces fragments to push up against any MTU limit at all. But I
>>> would not describe that has a host changing its path MTU; it's just
>>> sending packets.
>> I disagree, both on the definition and the action. You are correct in "how the Path MTU is calculated". But the Path MTU, by definition, is the largest packet that can be sent end to end under current routing conditions. It is not, actually, an IP concept: it's a TCP concept if anything, or a transport layer concept (if UDP ever decides to have one). I can imagine TCP probing the Path MTU by trying packets that are larger than its current estimate to see if the estimate is still accurate (1981 section 4), but I can't imagine any reason that TCP would send packets larger than the "largest packet that can be sent end to end under current routing conditions" in the normal case, as those packets will by definition either be fragmented or not arrive.
> istm that the robustness principle argues for what Fred is saying. Yes, any path that doesn't transmit 1280 byte packets is breaking the law, but (given that the protocol police do such a lousy job) if the objective fact is that the path only transmits 1279 byte packets, what's best for the user?
>
>      Brian
>
> _______________________________________________
> Gen-art mailing list
> Gen-art@ietf.org
> https://www.ietf.org/mailman/listinfo/gen-art

So this seems to me to be an argument of principle vs pragmatism, and in 
general pragmatism has served the Internet well so far.

I think pragmatism is what Fred and Brian arguing for. It is certainly 
the general approach that I support.

I think we have agreed that nothing actually breaks if the host takes a 
more conservative approach, and that the communications path is less 
likely to be disrupted if that is what the host does. I would have 
thought that we should write the text in such a way to "allow" a 
pragmatic mode of operation.

- Stewart




From nobody Thu Apr 27 05:46:35 2017
Return-Path: <alissa@cooperw.in>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6179A129463 for <gen-art@ietfa.amsl.com>; Thu, 27 Apr 2017 05:46:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 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, 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=eJtHRdxB; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=lByImN3r
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WfP_Eej4ImaF for <gen-art@ietfa.amsl.com>; Thu, 27 Apr 2017 05:46: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 B767412949D for <gen-art@ietf.org>; Thu, 27 Apr 2017 05:46:30 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 31AE020869; Thu, 27 Apr 2017 08:46:30 -0400 (EDT)
Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Thu, 27 Apr 2017 08:46:30 -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=/+e/I++6dOHRUPBJ2KEaHb169wnkUwhLNnh8Itff9 DM=; b=eJtHRdxBpcWcGW7LkAOaT/5pmeRnwSyKv+4m4loS6RSAcCK4JYDn3FOBH JdjYNC516OavxwF5cU+sECrfvqmlYr5BXMCZesY89/3KoFe1/el7KB2hx199+XkJ XZlBUYfqOVC8GLRqBJPBOr8nJOxHWRRdgc7E+S4S5iaKKMdkvhja6KexHQ6LQs/7 3myFz86WxpbV/qyKEzo0jDtE15AVnk5H47CRHQbzGN/TnQY1wsbkZrrh8IbGBMP7 qhXiIaTabZK8dZeXKnIoQTtUb67iEuTDy/oGH8/JTx7a4MzFEHoB3Oan9W0L/hTW xvbXHMOf/yHFEMccXLZHXgFtyLhsA==
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=/+e/I++6dOHRUPBJ2K EaHb169wnkUwhLNnh8Itff9DM=; b=lByImN3rgsdJp/jApX5PJVOQumAg34Lr6w 2Np+hiS7fAmfkFnwGHamPpavap20frzO8M61WEqyZi3p8CyCo5vw/AckMlFDS5XK xl0he6/WKPp0UhbzEOzi9dbC1GWq3jJxTJrWCN1fgRviuUTRvuiwe/8zL/DX7dR5 h1fJosVY0M8gMaf6cITOkNWelYo2jamlwNoGkox2VWutEH85ymI7grwMx5p2eWPt pd1VvCOmlTXEkdkdipKp+t/5gP/sxlvUoxuFp9Nc4jMuqrVr37wujX97NUo/DO0n CyfPcT8+uU7XEPON6I/TYHWb6T5BMkMCYjfEoOzKSTm4Qv4q0IjA==
X-ME-Sender: <xms:JugBWf4wMx3NydWMVGOJIA6s67ZJc8SIOUQyZ-jwI-5bgVh0dHIO3g>
X-Sasl-enc: MwJSol6xAcQgQ2ldS0i9wGjmjvvEEkQzqoymyTErT+Q5 1493297189
Received: from sjc-alcoop-8815.cisco.com (unknown [128.107.241.178]) by mail.messagingengine.com (Postfix) with ESMTPA id 183B07E8C8; Thu, 27 Apr 2017 08:46:28 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_BBCAD33A-1819-44BF-B0CC-847A7E542FA9"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <ABCAA4EF18F17B4FB619EA93DEF7939A4F443A6F@eusaamb107.ericsson.se>
Date: Thu, 27 Apr 2017 08:46:29 -0400
Cc: "draft-ietf-rtcweb-overview.all@tools.ietf.org" <draft-ietf-rtcweb-overview.all@tools.ietf.org>,  "gen-art@ietf.org" <gen-art@ietf.org>
Message-Id: <71610D77-ADB4-4A6F-BB29-A86773AB4C85@cooperw.in>
References: <ABCAA4EF18F17B4FB619EA93DEF7939A4F443A6F@eusaamb107.ericsson.se>
To: Meral Shirazipour <meral.shirazipour@ericsson.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/_xM485AJckoJDt99YHgymEhlsgM>
Subject: Re: [Gen-art] Gen-ART Last Call review of draft-ietf-rtcweb-overview-18
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 12:46:33 -0000

--Apple-Mail=_BBCAD33A-1819-44BF-B0CC-847A7E542FA9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Meral, thanks for your review! Sean, thanks for your response to =
Meral=E2=80=99s comments. I have ballotted yes.

Alissa

> On Mar 16, 2017, at 8:43 PM, Meral Shirazipour =
<meral.shirazipour@ericsson.com> wrote:
>=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.
> For more information, please see the FAQ at =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq =
<http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>>.
> =20
> =20
> Document: draft-ietf-rtcweb-overview-18
> Reviewer: Meral Shirazipour
> Review Date: 2017-03-16
> IETF LC End Date:   2017-03-20
> IESG Telechat date: 2017-04-13
> =20
> =20
> Summary:
> This draft is ready to be published as Standards Track RFC but I have =
comments.
> =20
> Major issues:
> Minor issues:
> Nits/editorial comments:
> -[Page 3] "an other hardware has"---->"and other hardware have"
> -[Page 4], the word "subprotocol" was not clear to me. Would it be =
possible to add in parenthesis a few example for protocol and =
subprotocol?
> -[Page 4], "an WebRTC"--->""a WebRTC"
> -[Page 7], "Interactive Connectivty"--->"Interactive Connectivity"
> -General: please spell out acronyms at first use
> -General: the writing (or perhaps lack of punctuation) in this draft =
made it hard to read. Please consider reviewing it especially if the =
draft is intended as Standards Track.
> =20
> =20
> =20
> Best Regards,
> Meral
> ---
> Meral Shirazipour
> Ericsson Research
> www.ericsson.com <http://www.ericsson.com/>

--Apple-Mail=_BBCAD33A-1819-44BF-B0CC-847A7E542FA9
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><div class=3D"">Meral, thanks for your review! Sean, thanks =
for your response to Meral=E2=80=99s comments. I have ballotted =
yes.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Alissa</div><br class=3D""><div><blockquote type=3D"cite" =
class=3D""><div class=3D"">On Mar 16, 2017, at 8:43 PM, Meral =
Shirazipour &lt;<a href=3D"mailto:meral.shirazipour@ericsson.com" =
class=3D"">meral.shirazipour@ericsson.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: =
0px;"><div style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">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.&nbsp; =
Please treat these comments just like any other last call comments.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">For more =
information, please see the FAQ at &lt;<a =
href=3D"http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq</a>&gt;=
.<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Document: =
draft-ietf-rtcweb-overview-18<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Reviewer: Meral Shirazipour<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Review =
Date: 2017-03-16<o:p class=3D""></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">IETF LC End Date:&nbsp;&nbsp; 2017-03-20<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">IESG =
Telechat date: 2017-04-13<o:p class=3D""></o:p></div><div style=3D"margin:=
 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Summary:<o:p class=3D""></o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">This draft is ready to be published as Standards Track RFC =
but I have comments.<o:p class=3D""></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in =
0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Major issues:<o:p class=3D""></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Minor issues:<o:p class=3D""></o:p></div><div style=3D"margin: =
0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Nits/editorial comments:<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">-[Page 3] "an other hardware =
has"----&gt;"and other hardware have"<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">-[Page 4], the word "subprotocol" was =
not clear to me. Would it be possible to add in parenthesis a few =
example for protocol and subprotocol?<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">-[Page 4], "an WebRTC"---&gt;""a =
WebRTC"<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">-[Page 7], "Interactive Connectivty"---&gt;"Interactive =
Connectivity"<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">-General: please spell out acronyms at first use<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">-General: =
the writing (or perhaps lack of punctuation) in this draft made it hard =
to read. Please consider reviewing it especially if the draft is =
intended as Standards Track.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Best Regards,<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Meral<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">---<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in 0in 0.0001pt; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D"">Meral =
Shirazipour<o:p class=3D""></o:p></div><div style=3D"margin: 0in 0in =
0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Ericsson Research<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><a href=3D"http://www.ericsson.com/" =
style=3D"color: purple; text-decoration: underline;" =
class=3D"">www.ericsson.com</a></div></div></div></blockquote></div><br =
class=3D""></body></html>=

--Apple-Mail=_BBCAD33A-1819-44BF-B0CC-847A7E542FA9--


From nobody Thu Apr 27 05:52:10 2017
Return-Path: <shares@ndzh.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E0BF01294A1; Thu, 27 Apr 2017 05:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.946
X-Spam-Level: 
X-Spam-Status: No, score=0.946 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DOS_OUTLOOK_TO_MX=2.845, 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 WAS7zLiJza0e; Thu, 27 Apr 2017 05:52:01 -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 EED371294C5; Thu, 27 Apr 2017 05:52:00 -0700 (PDT)
X-Default-Received-SPF: pass (skip=forwardok (res=PASS)) x-ip-name=70.194.23.139; 
From: "Susan Hares" <shares@ndzh.com>
To: "'Dale Worley'" <worley@ariadne.com>, <gen-art@ietf.org>
Cc: <i2nsf@ietf.org>, <ietf@ietf.org>, <draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org>
References: <149299947052.25893.14183369388246516074@ietfa.amsl.com>
In-Reply-To: <149299947052.25893.14183369388246516074@ietfa.amsl.com>
Date: Thu, 27 Apr 2017 08:46:06 -0400
Message-ID: <012d01d2bf54$3d9bbb60$b8d33220$@ndzh.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJj1w0Rmgy1J+ijI/wBRaCzRiot8qC29IzQ
Content-Language: en-us
X-Authenticated-User: skh@ndzh.com 
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/ZQntlF2qC6NNSs2UN9I-Zag3gqc>
Subject: Re: [Gen-art] [I2nsf] Genart telechat review of draft-ietf-i2nsf-problem-and-use-cases-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 12:52:03 -0000

Dale: 

Thank you for taking the time do a second careful review.   I can only wish
I such an excellent review of documents I am an editor on. Version 14
addresses all of your comments. 

Sue 

-----Original Message-----
From: I2nsf [mailto:i2nsf-bounces@ietf.org] On Behalf Of Dale Worley
Sent: Sunday, April 23, 2017 10:05 PM
To: gen-art@ietf.org
Cc: i2nsf@ietf.org; ietf@ietf.org;
draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
Subject: [I2nsf] Genart telechat review of
draft-ietf-i2nsf-problem-and-use-cases-12

Reviewer: Dale Worley
Review result: Ready with Nits

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

Document:  draft-ietf-i2nsf-problem-and-use-cases-12
Reviewer:  Dale R. Worley
Review Date:  2017-04-23
IETF LC End Date:  2017-03-22
IESG Telechat date:  2017-04-27

Summary:

       This draft is basically ready for publication, but has nits
       that should be fixed before publication.

All of these nits are editorial.

3.1.1.  Diverse Types of Security Functions

   Security gateways and VPN concentrators:    Examples of these
      functions are; IPsec gateways, Secure VPN concentrators that
      handle bridging secure VPNs, and secure VPN controllers for data
      flows.

Unless "Secure VPN" is a name in itself, "secure" shouldn't be capitalized.
(Between -11 and -12, one instance of this was fixed, but the other one
remains.)

Changed in version 14.  

3.1.2.  Diverse Interfaces to Control and Monitor NSFs

   A challenge for monitoring prior to mitigation of a security
   intrusion is that an NSF cannot monitor what it cannot view.
   Therefore, enabling a security function to mitigate an intrusion
   (e.g., firewall [I-D.ietf-opsawg-firewalls]) does not mean that a
   network is protected if there is no monitoring feedback.  As such, it
   is necessary to have a mechanism to monitor and provide execution
   status of NSFs to security and compliance management tools.  There
   exist various network security monitoring vendor-specific interfaces
   for forensics and troubleshooting, but an industry standard interface
   could provide monitoring across a variety of NSFs.

This paragraph still seems to have problems.  What the second sentence seems
to mean (though it doesn't say it) is that if you enable a security
function, you don't *know* that the network is protected if you don't have
any monitoring feedback.  (The sentence is stated in terms of whether the
network *is* protected, which it might well be, even if you don't have
monitoring.)  It seems that you need to replace "does not mean that a
network is protected" with something that is more literally correct.

The third sentence is constructed "... to have a mechanism to monitor and
provide execution status of NSFs to ...".  There's an awkwardness that
"monitor" isn't connected to "security and compliance management tools",
whereas "provide ... status ... to" *is* connected; there's a problem that
the "monitor" and "provide" are written as if they're parallel, but they're
not.  I think the wording is less confusing this
way:

   As such, it is necessary to have a mechanism to monitor NSFs and
   provide their execution status to security and compliance
   management tools.

--

   There
   exist various network security monitoring vendor-specific interfaces
   for forensics and troubleshooting, but an industry standard interface
   could provide monitoring across a variety of NSFs.

I think it's easier to read "vendor-specific network security monitoring
interfaces".

Sue:  Dale I rewrote the whole paragraph in version 14. 

New/ A challenge for monitoring prior to mitigation of a security intrusion
is that an NSF cannot monitor what it cannot view. For example, enabling a 
security function to mitigate an intrusion 
(e.g., firewall <xref target="I-D.ietf-opsawg-firewalls"></xref>) 
must include a mechanism to provide monitoring feedback in order to 
determine the intrusion has been stopped. Therefore, it is  
 necessary to have a mechanism to monitor 
and provide execution status of NSFs to security and
compliance management tools. There exist such mechanisms 
in vendor-specific network security interfaces for forensics and
troubleshooting, but an industry standard interface could 
provide monitoring across a variety of NSFs./


3.1.4.  More Demand to Control NSFs Dynamically

   The Security Service Providers ...

The capitalization of "security service providers" is inconsistent.
Some times all three words are capitalized (in 3.1.2, 3.1.4, and 4), and
some times they're not (two places in 3).

Sue: Thank you for catching this.  I moved all of these words to small case
except in titles. 

3.2.2.  Today's Control Requests are Vendor Specific

   Managing by scripts de-jour:    The current practices rely upon
the
      use of scripts that generate other scripts which automatically run
      to upload or download configuration changes, log information and
      other things.  These scripts have to be adjusted each time an
      implementation from a different vendor technology is enabled by a
      provider side.

What is "a provider side"?  I suspect it means "the provider side of an
XXX", but I'm not familiar enough with the subject to know what XXX is.

Sue:
Old/provider side/New/Provide/ 


[END]


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


From nobody Thu Apr 27 08:36:30 2017
Return-Path: <worley@alum.mit.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA930129B18 for <gen-art@ietfa.amsl.com>; Thu, 27 Apr 2017 08:36:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.933
X-Spam-Level: 
X-Spam-Status: No, score=-1.933 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w1D7mAjR4JSf for <gen-art@ietfa.amsl.com>; Thu, 27 Apr 2017 08:36:23 -0700 (PDT)
Received: from resqmta-ch2-04v.sys.comcast.net (resqmta-ch2-04v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:36]) (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 B4B66129B1A for <gen-art@ietf.org>; Thu, 27 Apr 2017 08:34:42 -0700 (PDT)
Received: from resomta-ch2-04v.sys.comcast.net ([69.252.207.100]) by resqmta-ch2-04v.sys.comcast.net with SMTP id 3lR9dxV4hscBP3lRJd8QA4; Thu, 27 Apr 2017 15:34:41 +0000
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4603:9471:222:fbff:fe91:d396]) by resomta-ch2-04v.sys.comcast.net with SMTP id 3lRHd0yrWFcZ23lRJd6sqp; Thu, 27 Apr 2017 15:34:41 +0000
Received: from hobgoblin.ariadne.com (hobgoblin.ariadne.com [127.0.0.1]) by hobgoblin.ariadne.com (8.14.7/8.14.7) with ESMTP id v3RFYbmi010046; Thu, 27 Apr 2017 11:34:38 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.14.7/8.14.7/Submit) id v3RFYa2n010027; Thu, 27 Apr 2017 11:34:36 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com (Dale R. Worley)
To: "Susan Hares" <shares@ndzh.com>
Cc: gen-art@ietf.org, i2nsf@ietf.org, ietf@ietf.org, draft-ietf-i2nsf-problem-and-use-cases.all@ietf.org
In-Reply-To: <012d01d2bf54$3d9bbb60$b8d33220$@ndzh.com> (shares@ndzh.com)
Sender: worley@ariadne.com (Dale R. Worley)
Date: Thu, 27 Apr 2017 11:34:34 -0400
Message-ID: <8737ctrhit.fsf@hobgoblin.ariadne.com>
X-CMAE-Envelope: MS4wfMU/myGjX5MRLWJJP6QFWDh0apPIByWYoYsEzaVfPzskhuCu/rClk3pHbAP4uHRsBZebwTWZRiC4sYcIULtiNuz+tjykKzqMPboSJmL7oyfph72a6S/P 5CJ/QBMh1Qg1alyj28HAXDbABcVyNKngDGCkmpU9rf/KBFCeoB/JdTM4kivOaHxQ1bLbtngcn62gmaz2ljUWJkYTqDsE1hbw4Az4SSqC5fYGzpcX6Fpwm1or TleS5qh3zmamY7li4nJNhbOQZcszYA3JktIE8h2KWiKW3Xn0BIyvAriciDvbs1hBAnonvgd3bdQE8HcmrPmRFw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/Fyneb5eCvq1AFvG7TlYrGBHYIgU>
Subject: Re: [Gen-art] [I2nsf] Genart telechat review of draft-ietf-i2nsf-problem-and-use-cases-12
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 15:36:24 -0000

"Susan Hares" <shares@ndzh.com> writes:
> Thank you for taking the time do a second careful review.   I can only wish
> I such an excellent review of documents I am an editor on. Version 14
> addresses all of your comments. 

Thanks!  -15 looks great, except (ugh) for one remaining nit:

> Sue:  Dale I rewrote the whole paragraph in version 14. 

When I read the new paragraph, I get a slightly different impression
than I did from the old paragraph (which is likely something you
indend), viz., that it's about what could be called "the mitigation
action lifecycle", the entire process from identification of the problem
to verification that it has been mitigated, rather than just the
*action* of mitigating the traffic problem.  Within that broader
context, the importance of monitoring is obvious.

> 3.1.4.  More Demand to Control NSFs Dynamically
>
>    The Security Service Providers ...
>
> The capitalization of "security service providers" is inconsistent.
> Some times all three words are capitalized (in 3.1.2, 3.1.4, and 4), and
> some times they're not (two places in 3).
>
> Sue: Thank you for catching this.  I moved all of these words to small case
> except in titles. 

I overlooked (ugh) that there's an instance in section 2:

   Security Service Provider:    A provider of security services to the
      customers (end-users or enterprises) using NSF equipment purchased
      from vendors or created by the service provider.

It turns out that there are only 2 multi-word terms defined in section
2 where the later words aren't acronyms, which are the terms whose
capitalization should be consistent.  The other one is:

   Bespoke security management:   Security management which is made to
      fit a particular customer.

Dale


From nobody Thu Apr 27 10:00:32 2017
Return-Path: <touch@isi.edu>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE4F2129B37; Thu, 27 Apr 2017 10:00:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vy4WfhiOxJxD; Thu, 27 Apr 2017 10:00:15 -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 A61B0129B51; Thu, 27 Apr 2017 09:57:59 -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 v3RGvh92009153 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 27 Apr 2017 09:57:43 -0700 (PDT)
To: Stewart Bryant <stewart.bryant@gmail.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>, Fred Baker <fredbaker.ietf@gmail.com>
Cc: gen-art@ietf.org, 6man WG <ipv6@ietf.org>, IETF-Discussion Discussion <ietf@ietf.org>, draft-ietf-6man-rfc1981bis.all@ietf.org
References: <149305392811.25808.15115824976388262628@ietfa.amsl.com> <497d3868-406a-a38f-56d8-391b0fc16032@isi.edu> <a974da1d-a9e7-8c64-8086-0955f2dffb12@gmail.com> <f6088ab8-3533-96f1-d9eb-f8462b1f4a1b@isi.edu> <99FD5A05-EDBE-4764-941C-C95BD689237B@gmail.com> <a7c8a2d8-6a67-e78c-a3d9-7bf7f0b767a9@gmail.com> <8fdddab8-dba8-d151-6552-882d2c9a7918@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <d998ea12-71d3-1a8f-03cf-91be1f710f9e@isi.edu>
Date: Thu, 27 Apr 2017 09:57:43 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.0.1
MIME-Version: 1.0
In-Reply-To: <8fdddab8-dba8-d151-6552-882d2c9a7918@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/PgWALFfeW5cw4SionWqxtBfS3zI>
Subject: Re: [Gen-art] Genart telechat review of draft-ietf-6man-rfc1981bis-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 17:00:17 -0000

On 4/27/2017 5:36 AM, Stewart Bryant wrote:
> ...
> So this seems to me to be an argument of principle vs pragmatism, and
> in general pragmatism has served the Internet well so far.
>
> I think pragmatism is what Fred and Brian arguing for. It is certainly
> the general approach that I support.

IMO, 1981bis should limit its advice to behavior in response to ICMPs, e.g.:

   In reaction to a received ICMP message, a node MUST NOT reduce its estimate of the Path MTU below the IPv6
   minimum link MTU.

Doing otherwise presents too big an attack surface.

Any other advice on how an end system manages its idea of MTU or
otherwise overrides the 1981bis computation of path MTU should be
limited to host requirements documents, not this one.

Joe


From nobody Thu Apr 27 14:39:14 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F0F0129BF2 for <gen-art@ietf.org>; Thu, 27 Apr 2017 14:39:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-to: mahoney@nostrum.com
Message-ID: <149332915357.2951.7541800746439497216.idtracker@ietfa.amsl.com>
Date: Thu, 27 Apr 2017 14:39:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/McntTIrNqq1LVuvGBL-MFCDN4GQ>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Apr 2017 21:39:14 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-05-11

Reviewer               Type      LC end     Draft
Stewart Bryant         Telechat  2017-04-21 draft-ietf-grow-large-communities-usage-07 *
Francis Dupont         Telechat  2017-03-02 draft-ietf-dprive-dtls-and-tls-profiles-09
Joel Halpern           Telechat  2017-03-02 draft-ietf-anima-grasp-11 *
Dale Worley            Telechat  2017-03-22 draft-ietf-i2nsf-problem-and-use-cases-15 *
Peter Yee              Last Call 2017-05-04 draft-ietf-manet-olsrv2-multipath-12

For telechat 2017-05-25

Reviewer               Type      LC end     Draft
Lucy Yong              Telechat  None       draft-ietf-isis-l2bundles-04

Last calls:

Reviewer               Type      LC end     Draft
Stewart Bryant         Last Call 2017-05-04 draft-ietf-spring-ipv6-use-cases-10
Brian Carpenter        Last Call 2017-05-04 draft-ietf-spring-resiliency-use-cases-08
Vijay Gurbani          Last Call 2017-04-20 draft-ietf-avtcore-rfc5285-bis-09
Peter Yee              Telechat  2017-03-01 draft-ietf-6man-rfc2460bis-10 *

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Stewart Bryant
  Brian Carpenter
  Elwyn Davies
  Ralph Droms
  Francis Dupont
  Roni Even
  Fernando Gont
  Vijay Gurbani
  Wassim Haddad
  Joel Halpern

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Fri Apr 28 14:12:14 2017
Return-Path: <mahoney@nostrum.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 896A4129B56 for <gen-art@ietf.org>; Fri, 28 Apr 2017 14:12:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Jean Mahoney <mahoney@nostrum.com>
To: <gen-art@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-to: mahoney@nostrum.com
Message-ID: <149341393246.3032.5302339943826558262.idtracker@ietfa.amsl.com>
Date: Fri, 28 Apr 2017 14:12:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/-kcJtiScCbQW_s8RE7wr9oHD9_0>
Subject: [Gen-art] Review Assignments
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 28 Apr 2017 21:12:12 -0000

Hi all,

The following reviewers have assignments:

For telechat 2017-05-11

Reviewer               Type      LC end     Draft
Stewart Bryant         Telechat  2017-04-21 draft-ietf-grow-large-communities-usage-07 *
Francis Dupont         Telechat  2017-03-02 draft-ietf-dprive-dtls-and-tls-profiles-09
Roni Even              Telechat  2017-04-28 draft-ietf-bess-evpn-vpws-12 *
Joel Halpern           Telechat  2017-03-02 draft-ietf-anima-grasp-11 *
Dale Worley            Telechat  2017-03-22 draft-ietf-i2nsf-problem-and-use-cases-15 *
Peter Yee              Last Call 2017-05-04 draft-ietf-manet-olsrv2-multipath-12

For telechat 2017-05-25

Reviewer               Type      LC end     Draft
Joel Halpern           Telechat  2017-03-27 draft-ietf-dnsop-nsec-aggressiveuse-09 *
Jouni Korhonen         Last Call 2017-05-12 draft-ietf-mpls-tp-shared-ring-protection-05
Lucy Yong              Telechat  None       draft-ietf-isis-l2bundles-04

Last calls:

Reviewer               Type      LC end     Draft
Stewart Bryant         Last Call 2017-05-26 draft-nottingham-rfc5988bis-05
Stewart Bryant         Last Call 2017-05-04 draft-ietf-spring-ipv6-use-cases-10
Brian Carpenter        Last Call 2017-05-04 draft-ietf-spring-resiliency-use-cases-08
Francis Dupont         Last Call 2017-05-15 draft-freytag-lager-variant-rules-05 *
Fernando Gont          Last Call 2017-05-12 draft-ietf-nfsv4-umask-03
Vijay Gurbani          Last Call 2017-04-20 draft-ietf-avtcore-rfc5285-bis-09
Russ Housley           Last Call 2017-05-12 draft-ietf-nfsv4-versioning-09
Peter Yee              Telechat  2017-03-01 draft-ietf-6man-rfc2460bis-10 *

* Other revision previously reviewed
** This revision already reviewed

Next in the reviewer rotation:

  Orit Levin
  Matthew Miller
  Pete Resnick
  Dan Romascanu
  Meral Shirazipour
  Robert Sparks
  Dale Worley
  Peter Yee
  Lucy Yong
  Jari Arkko

The LC and Telechat review templates are included below:
-------------------------------------------------------

-- Begin LC Template --
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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments: 

-- End LC Template --

-- Begin Telechat Template --
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:
Reviewer:
Review Date:
IETF LC End Date:
IESG Telechat date: (if known)

Summary:

Major issues:

Minor issues:

Nits/editorial comments:

-- End Telechat Template --



From nobody Sat Apr 29 00:49:53 2017
Return-Path: <marius.georgescu@rcs-rds.ro>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D604129B5A; Sat, 29 Apr 2017 00:49:44 -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, 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=rcs-rds.ro
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9XS4QChOOzzf; Sat, 29 Apr 2017 00:49:41 -0700 (PDT)
Received: from mailproxy5.rcs-rds.ro (mailproxy5.rcs-rds.ro [212.54.124.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44AC5129568; Sat, 29 Apr 2017 00:47:22 -0700 (PDT)
Received: from [10.252.6.123] (unknown [10.252.6.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mailproxy5.rcs-rds.ro (Postfix) with ESMTPSA id F0E262836A1; Sat, 29 Apr 2017 10:47:18 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=rcs-rds.ro; s=MailProxy; t=1493452039; bh=Zb8otDAsXI/AYQAqTa++lYnEj6tDRePlfRNT1gEps+E=; h=Subject:To:References:Cc:From:Date:In-Reply-To; b=aY0Um0bFsdNK2zVbOn4Q7zu+/6QtbUWypmp/mUcvcIrgdWiMK4WNzel9YF6zE2j4u KYXd8B7K+DLjRemnhVImorOVYi6SD1UZlXe38DJfZxjikFPvvcMd2K1hHBUNfH0wAv rcUklW2plV3m7Hi6CkwwEY+KSvxPc/wTUsJtAc4w=
To: Robert Sparks <rjsparks@nostrum.com>, gen-art@ietf.org
References: <149322271242.5954.6564310624067283031@ietfa.amsl.com>
Cc: draft-ietf-bmwg-ipv6-tran-tech-benchmarking.all@ietf.org, ietf@ietf.org, bmwg@ietf.org
From: Marius Georgescu <marius.georgescu@rcs-rds.ro>
Message-ID: <303391a2-84f1-31dc-1b67-e3cc8b0aea3c@rcs-rds.ro>
Date: Sat, 29 Apr 2017 10:52:23 +0300
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: <149322271242.5954.6564310624067283031@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/M3ADUEykDXWqvH6s9yDezTs8R4Q>
Subject: Re: [Gen-art] Genart last call review of draft-ietf-bmwg-ipv6-tran-tech-benchmarking-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 07:49:44 -0000

Hello Robert,

Thank you very much for your detailed review.

We have revised the draft according to your comments.

The result was uploaded as:

https://tools.ietf.org/html/draft-ietf-bmwg-ipv6-tran-tech-benchmarking-07

Please find inline a punctual overview of the changes.

On 4/26/2017 7:05 PM, Robert Sparks wrote:
> Reviewer: Robert Sparks
> 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-ipv6-tran-tech-benchmarking-06
> Reviewer: Robert Sparks
> Review Date: 2017-04-26
> IETF LC End Date: 2017-05-02
> IESG Telechat date: Not scheduled for a telechat
>
> Summary: Essentially Ready for publication as an Informational RFC,
> but with some minor issues to address before publication
>
> This document is (with exceptions noted below) straightforward and
> easy to follow
>
> Minor Issues:
>
> Section 8 is very confusing - I suspect it has been made so by
> removing things that were in it earlier. Right now it claims to
> provide additional tests, but the only content is about testing things
> with firewalls, along with a statement that this document is only
> targeting network devices that do not have a firewall function. I
> think you can keep most of the text here (except the statement that
> you aren't talking about things with firewalls) and remove the
> confusion by changing the section heading to something like "Tests in
> the presence of a firewall function".
- we have removed the second paragraph , which was indeed confusing.
The point, which may be clearer in Section 1.1 is that we need
additional benchmarks for stateful IPv6 transition technologies,
which may be (or not) labeled as having a firewall function.  
> It's unclear how to apply the formula in Section 10.2.1 to the results
> that come out of, say, Section 7.3.2, where you are reporting a
> (minimum, median, maximum) tuple. Some discussion about the
> applicability of the tests where you recommend against reporting a
> single number to the methods in this section would help.
+ we added a note in the reporting format part stating: "

*In the case of benchmarks for which more than one value is reported
(e.g. IPDV Section 7.3.2), a column for each of the values SHOULD be
included.*

"
>  It would also
> help to point out that the Xpd result can be go negative (it will go
> negative for things that become smaller as the number of flows
> increase, and positive for things that get bigger). If I read this
> correctly, if throughput (for example) goes to 0 as n increases, Xpd
> will go to -100%. Similary if latency doubles as n increases, Xpd will
> go to +100% (and will go to +200% if latency triples).
+ This was one of the important points which needed clarification. Thank
you for pointing it out.
In order to keep the  performance degradation results in the Lower is
better  direction, we proposed a secondary calculation formula for
higher is better benchmarks (e.g. Throughput). This makes, in our
opinion, the results easier to interpret.

> Nits:
>
> There are several places where you point to Section 6 where I think
> you meant to point to Section 7. See the Procedure: line in 10.2.1 for
> an example. Also make sure 9 is correct where you say "Sections 6
> through 9" in section 12.
+Corrected
>
> Please double-check that you meant "larger MTU" in the last paragraph
> of 5.1. It might be correct, but I find the paragraph confusing.
We find this part to be correct. However, keeping only the 1280 +
overhead recommendation might make it less confusing.
Do you think that would be a viable solution?
> In 8.1 you meant to point to 5.2, not 5.3
>
> Please try to simplify this sentence: 
>   "The duration of each trial SHOULD be at least 60 seconds to reduce
> the potential gain of a DNS64 server, which is able to exhibit higher
> performance by storing the requests and thus utilizing also the
> timeout time for answering them."
+corrected
>
> (Style comment - please feel free to ignore): Consider deleting "as
> well" everywhere it occurs in the document - most of the places it is
> used, the sentence works just as well, and sometimes better, without
> it.
+corrected
> Typos:
> end of section 5.1.1: Appendix A1 should be Appendix A
+corrected

Best regards,
Marius


From nobody Sat Apr 29 10:31:55 2017
Return-Path: <elwynd@folly.org.uk>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45C2C129BAB; Sat, 29 Apr 2017 10:31:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.719
X-Spam-Level: 
X-Spam-Status: No, score=-0.719 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kQWzgU_ptJOU; Sat, 29 Apr 2017 10:31:51 -0700 (PDT)
Received: from a-painless.mh.aa.net.uk (a-painless.mh.aa.net.uk [81.187.30.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C9AFE128CFF; Sat, 29 Apr 2017 10:30:00 -0700 (PDT)
Received: from 153.107.2.81.in-addr.arpa ([81.2.107.153] helo=[192.168.0.132]) by a-painless.mh.aa.net.uk with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <elwynd@folly.org.uk>) id 1d4Vqf-0000sl-BL; Sat, 29 Apr 2017 18:07:57 +0100
Date: Sat, 29 Apr 2017 18:07:55 +0100
Message-ID: <1elqpqqykntu62veby5o1nuo.1493485675772@email.android.com>
Importance: normal
From: Elwyn Davies <elwynd@folly.org.uk>
To: draft-ietf-jsonbis-rfc7159bis.all@ietf.org
Cc: gen-art@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_678588509670880"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/K8fonViRtu1at4_wEoUbzM11dpI>
Subject: [Gen-art] Last paragraph of RFC Editor notes for rfc7159bis
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Apr 2017 17:31:53 -0000

----_com.samsung.android.email_678588509670880
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64

SGkuCkkgd2FzIGp1c3QgcmVhZGluZyB0aHJvdWdoIHRoZSBwcm9wb3NlZCBSRkMgRWRpdG9yIG5v
dGVzIGZvciB0aGlzIGRvY3VtZW50LiDCoEkgdGhpbmsgaXQgbmVlZHMgdG8gYmUgbW9yZSBleHBs
aWNpdCB0aGF0IHRoZSAwIDwgKDFzdCBjaGFyYWN0ZXIpIDwgMTI4IG9jY3VycyB3aGVuIGl0IGlz
IGVuY29kZWQgaW4gVVRGLTguIFRodXM6T0xEOsKgUmVjaXBpZW50cyB0aGF0IHdpc2ggdG8gc3Vw
cG9ydCBVbmljb2RlIGVuY29kaW5ncyBvdGhlciB0aGFuIFVURi04IGNhbiBkbyB0aGlzIHVzaW5n
IGEgZGV0ZWN0aW9uIG1lY2hhbmlzbSB0aGF0IGlzIGJhc2VkIG9uIHRoZSBmYWN0IHRoYXQgdGhl
IGZpcnN0IFVuaWNvZGUgY2hhcmFjdGVyIHdpbGwgYWx3YXlzIGhhdmUgYSBVbmljb2RlIGNvZGUg
cG9pbnQgdmFsdWUgZ3JlYXRlciB0aGFuIDAgYW5kIGxlc3MgdGhhbiAxMjgsIHRodXMgdGhlIFVU
Ri0xNi8zMiB2YXJpYW50cyBjYW4gYmUgZGV0ZWN0ZWQgYnkgaW5zcGVjdGluZyB0aGUgZmlyc3Qg
ZmV3IG9jdGV0cyBmb3IgbnVsbHMuCk5FVzrCoFJlY2lwaWVudHMgdGhhdCB3aXNoIHRvIHN1cHBv
cnQgVW5pY29kZSBlbmNvZGluZ3Mgb3RoZXIgdGhhbiBVVEYtOCBjYW4gZG8gdGhpcyB1c2luZyBh
IGRldGVjdGlvbiBtZWNoYW5pc20gdGhhdCBpcyBiYXNlZCBvbiB0aGUgZmFjdCB0aGF0LCB3aGVu
IGVuY29kZWQgaW4gVVRGLTgsIHRoZSBmaXJzdCBVbmljb2RlIGNoYXJhY3RlciB3aWxsIGFsd2F5
cyBoYXZlIGEgVW5pY29kZSBjb2RlIHBvaW50IHZhbHVlIGdyZWF0ZXIgdGhhbiAwIGFuZCBsZXNz
IHRoYW4gMTI4LCB0aHVzIHRoZSBVVEYtMTYvMzIgdmFyaWFudHMgY2FuIGJlIGRldGVjdGVkIGJ5
IGluc3BlY3RpbmcgdGhlIGZpcnN0IGZldyBvY3RldHMgZm9yIG51bGxzLgpFTkRTCkNoZWVycyxF
bHd5bgoKU2VudCBmcm9tIFNhbXN1bmcgdGFibGV0Lg==

----_com.samsung.android.email_678588509670880
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64

PGh0bWw+PGhlYWQ+PG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0
L2h0bWw7IGNoYXJzZXQ9VVRGLTgiPjwvaGVhZD48Ym9keT48ZGl2PkhpLjwvZGl2PjxkaXY+PGJy
PjwvZGl2PjxkaXY+SSB3YXMganVzdCByZWFkaW5nIHRocm91Z2ggdGhlIHByb3Bvc2VkIFJGQyBF
ZGl0b3Igbm90ZXMgZm9yIHRoaXMgZG9jdW1lbnQuICZuYnNwO0kgdGhpbmsgaXQgbmVlZHMgdG8g
YmUgbW9yZSBleHBsaWNpdCB0aGF0IHRoZSAwICZsdDsgKDFzdCBjaGFyYWN0ZXIpICZsdDsgMTI4
IG9jY3VycyB3aGVuIGl0IGlzIGVuY29kZWQgaW4gVVRGLTguIFRodXM6PC9kaXY+PGRpdj5PTEQ6
PC9kaXY+PGRpdj4mbmJzcDtSZWNpcGllbnRzIHRoYXQgd2lzaCB0byBzdXBwb3J0IFVuaWNvZGUg
ZW5jb2RpbmdzIG90aGVyIHRoYW4gVVRGLTggY2FuIGRvIHRoaXMgdXNpbmcgYSBkZXRlY3Rpb24g
bWVjaGFuaXNtIHRoYXQgaXMgYmFzZWQgb24gdGhlIGZhY3QgdGhhdCB0aGUgZmlyc3QgVW5pY29k
ZSBjaGFyYWN0ZXIgd2lsbCBhbHdheXMgaGF2ZSBhIFVuaWNvZGUgY29kZSBwb2ludCB2YWx1ZSBn
cmVhdGVyIHRoYW4gMCBhbmQgbGVzcyB0aGFuIDEyOCwgdGh1cyB0aGUgVVRGLTE2LzMyIHZhcmlh
bnRzIGNhbiBiZSBkZXRlY3RlZCBieSBpbnNwZWN0aW5nIHRoZSBmaXJzdCBmZXcgb2N0ZXRzIGZv
ciBudWxscy48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pk5FVzo8L2Rpdj48ZGl2PiZuYnNwO1Jl
Y2lwaWVudHMgdGhhdCB3aXNoIHRvIHN1cHBvcnQgVW5pY29kZSBlbmNvZGluZ3Mgb3RoZXIgdGhh
biBVVEYtOCBjYW4gZG8gdGhpcyB1c2luZyBhIGRldGVjdGlvbiBtZWNoYW5pc20gdGhhdCBpcyBi
YXNlZCBvbiB0aGUgZmFjdCB0aGF0LCB3aGVuIGVuY29kZWQgaW4gVVRGLTgsIHRoZSBmaXJzdCBV
bmljb2RlIGNoYXJhY3RlciB3aWxsIGFsd2F5cyBoYXZlIGEgVW5pY29kZSBjb2RlIHBvaW50IHZh
bHVlIGdyZWF0ZXIgdGhhbiAwIGFuZCBsZXNzIHRoYW4gMTI4LCB0aHVzIHRoZSBVVEYtMTYvMzIg
dmFyaWFudHMgY2FuIGJlIGRldGVjdGVkIGJ5IGluc3BlY3RpbmcgdGhlIGZpcnN0IGZldyBvY3Rl
dHMgZm9yIG51bGxzLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+RU5EUzwvZGl2PjxkaXY+PGJy
PjwvZGl2PjxkaXY+Q2hlZXJzLDwvZGl2PjxkaXY+RWx3eW48L2Rpdj48ZGl2Pjxicj48L2Rpdj48
ZGl2Pjxicj48L2Rpdj48ZGl2IGlkPSJjb21wb3Nlcl9zaWduYXR1cmUiPjxkaXYgc3R5bGU9ImZv
bnQtc2l6ZTo4NSU7Y29sb3I6IzU3NTc1NyIgZGlyPSJhdXRvIj5TZW50IGZyb20gU2Ftc3VuZyB0
YWJsZXQuPC9kaXY+PC9kaXY+PC9ib2R5PjwvaHRtbD4=

----_com.samsung.android.email_678588509670880--


From nobody Sun Apr 30 18:18:45 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8D7129ADD; Sun, 30 Apr 2017 18:18:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Joel Halpern <jmh@joelhalpern.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-anima-grasp.all@ietf.org, ietf@ietf.org, anima@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149360151701.9927.14136920563894865857@ietfa.amsl.com>
Date: Sun, 30 Apr 2017 18:18:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/A-OzjFqeWYNWjNiW0s4kWOFRZ5A>
Subject: [Gen-art] Genart telechat review of draft-ietf-anima-grasp-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 May 2017 01:18:37 -0000

Reviewer: Joel Halpern
Review result: Ready

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

For more information, please see the FAQ at

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

Document: draft-ietf-anima-grasp-??
Reviewer: Joel Halpern
Review Date: 2017-04-30
IETF LC End Date: 2017-03-02
IESG Telechat date: 2017-05-11

Summary: This document is ready to be Proposed Standard
    The changes in revisions 10 and 11 address all of the concerns in
my review of revision 09

Major issues: N/A

Minor issues: N/A

Nits/editorial comments:  N/A



From nobody Sun Apr 30 19:03:37 2017
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5282E129B63; Sun, 30 Apr 2017 19:03:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Brian Carpenter <brian.e.carpenter@gmail.com>
To: <gen-art@ietf.org>
Cc: draft-ietf-spring-resiliency-use-cases.all@ietf.org, spring@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149360420729.9840.1135726446843394242@ietfa.amsl.com>
Date: Sun, 30 Apr 2017 19:03:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/MvQv_TancT0ySmZtyqnez0sDXlc>
Subject: [Gen-art] Genart last call review of draft-ietf-spring-resiliency-use-cases-08
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 May 2017 02:03:27 -0000

Reviewer: Brian Carpenter
Review result: Ready with Issues

Gen-ART Last Call review of draft-ietf-spring-resiliency-use-cases-08

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

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

Document: draft-ietf-spring-resiliency-use-cases-08.txt
Reviewer: Brian Carpenter
Review Date: 2017-05-01
IETF LC End Date: 2017-05-04
IESG Telechat date:  

Summary: Ready with issues
--------

Comment:
--------

I wonder about the value to the community of publishing use cases and
requirements late in the standards process. They clearly have value
while designing solutions, but do they really have archival value,
since
RFC7855 was published a year ago? (An alternative approach to use
case
documents is to structure them as example applications to validate
the
protocol design, but that would be a major rewrite.)

Major issue: 
------------

I agree with the AD review dated 2017-04-20; if we publish a use case
document of this kind, it should be historically consistent.

Minor issue:
------------

The text of section 3 doesn't explain what requirements for SPRING it
generates. Really it just describes what any IGP will do anyway.
How does that impact SPRING? If there is no impact, please say so!

The other sections are quite clear on this aspect.



From nobody Sun Apr 30 19:44:34 2017
Return-Path: <jmh@joelhalpern.com>
X-Original-To: gen-art@ietf.org
Delivered-To: gen-art@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EA0D3127241; Sun, 30 Apr 2017 19:44:31 -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: dnsop@ietf.org, ietf@ietf.org, draft-ietf-dnsop-nsec-aggressiveuse.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.50.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149360667193.9876.7534874775326889081@ietfa.amsl.com>
Date: Sun, 30 Apr 2017 19:44:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/AjnRX8psdt-9_8RxQKxT2ySkMMc>
Subject: [Gen-art] Genart telechat review of draft-ietf-dnsop-nsec-aggressiveuse-09
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 May 2017 02:44:32 -0000

Reviewer: Joel Halpern
Review result: Ready with Issues

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

For more information, please see the FAQ at

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

Document: draft-ietf-dnsop-nsec-aggressiveuse-09
Reviewer: Joel Halpern
Review Date: 2017-04-30
IETF LC End Date: 2017-03-27
IESG Telechat date: 2017-05-25

Summary: This document is almost ready for publication as a Proposed
Standard RFC

Major issues:
    Procedural - ID Nits notes that there are normative references to
RFCs 7129 and 7719.  Those are informational RFCs.  The shepherd
writeup does not note these downrefs.  (I see this was also noted by
Jouni Korhonen, but I do not see a resolution.)

Minor issues:

Nits/editorial comments: 


