Return-Path: <0100016b48687180-05d46ca8-d13d-46ba-93e7-cac92b63e392-000000@amazonses.watsen.net>
X-Original-To: netconf@ietfa.amsl.com
Delivered-To: netconf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id 0FE13120098
 for <netconf@ietfa.amsl.com>; Tue, 11 Jun 2019 14:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5
 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
 HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001,
 SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key)
 header.d=amazonses.com
Received: from mail.ietf.org ([4.31.198.44])
 by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 78MRFNMVuMij for <netconf@ietfa.amsl.com>;
 Tue, 11 Jun 2019 14:18:54 -0700 (PDT)
Received: from a8-83.smtp-out.amazonses.com (a8-83.smtp-out.amazonses.com
 [54.240.8.83])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-SHA256 (128/128 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 0FA45120018
 for <netconf@ietf.org>; Tue, 11 Jun 2019 14:18:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple;
 s=6gbrjpgwjskckoa6a5zn6fwqkn67xbtw; d=amazonses.com; t=1560287932;
 h=From:Message-Id:Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To:References:Feedback-ID;
 bh=SGK0Af92QPIjH33hGq3dfiHpJSpmOuLpLOe76HqjvgE=;
 b=hb1HlUdrfnuoecoswwHJa/K64ddUVQlqcCY8n53SS2y/p9jmo8xErhqiVhdqiXYV
 Vzp8v8lTU6rLffT2cq9EHpNOwLQaZN5cE/bkp8jcr0b2m6h4B3iMGx3RQaFKmUGxuOl
 9okNgFuK+gIZ25m37PZD9mA768p/16wbaw457ezE=
From: Kent Watsen <kent@watsen.net>
Message-ID: <0100016b48687180-05d46ca8-d13d-46ba-93e7-cac92b63e392-000000@email.amazonses.com>
Content-Type: multipart/alternative;
 boundary="Apple-Mail=_6BE0E4A0-0156-41DA-9B5D-3B107C46EBAA"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 11 Jun 2019 21:18:52 +0000
In-Reply-To: <0537B9CE-83CF-4E5C-95AC-ABEB46C92804@cisco.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: "Reshad Rahman (rrahman)" <rrahman@cisco.com>
References: <156020896295.32199.7617469401232263908@ietfa.amsl.com>
 <F45C8148-7D85-4F9E-A2EA-CD58DBCA86E6@cisco.com>
 <0100016b477bd2b9-b33bafa5-224c-43d4-9467-0ffbdae769e6-000000@email.amazonses.com>
 <0537B9CE-83CF-4E5C-95AC-ABEB46C92804@cisco.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-SES-Outgoing: 2019.06.11-54.240.8.83
Feedback-ID: 1.us-east-1.DKmIRZFhhsBhtmFMNikgwZUWVrODEw9qVcPhqJEI2DA=:AmazonSES
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/nwA0VljCuAxFo1TcM9Yjs1Qlu1o>
Subject: Re: [netconf] I-D Action: draft-ietf-netconf-restconf-notif-14.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETCONF WG list <netconf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netconf>,
 <mailto:netconf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf/>
List-Post: <mailto:netconf@ietf.org>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netconf>,
 <mailto:netconf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2019 21:18:56 -0000


--Apple-Mail=_6BE0E4A0-0156-41DA-9B5D-3B107C46EBAA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8


Hi Reshad,

> Yes, this is over RESTCONF so http1.1/http2 are both ok. One change =
<https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-netconf-restconf-notif-08>=
 which was done ~8 months ago is to have 1 callflow =E2=80=9Cover =
RESTCONF/SSE=E2=80=9D as opposed to the previous separate callflows for =
http1.1 and http2. The reason http2 is mentioned in a few places is =
because of http2 streams. Section 4 already mentions =E2=80=9Cwhere =
HTTP2 is available to=E2=80=A6=E2=80=9D, so it looks like section 3.4 is =
the only place missing =E2=80=9Cwhen HTTP2 is used=E2=80=9D?

I recall that conversion and hence my alarm seeing all the HTTP2 text.  =
Yes, adding "when/if HTTP2 is used" everywhere, to constantly remind the =
reader that it may not always be the case would be good.   =20

For Section 4, would replacing "where HTTP2 transport is available" with =
"when the HTTP2 transport is used" be better?


Kent // contributor


--Apple-Mail=_6BE0E4A0-0156-41DA-9B5D-3B107C46EBAA
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; line-break: after-white-space;" class=3D""><br =
class=3D""><div>Hi Reshad,</div><div><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><span style=3D"font-family: =
Calibri, sans-serif; font-size: 11pt; caret-color: rgb(0, 0, 0);" =
class=3D"">Yes, this is over RESTCONF so http1.1/http2 are both ok. =
One</span>&nbsp;<a =
href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-netconf-restconf-no=
tif-08" class=3D"" style=3D"font-family: Calibri, sans-serif; font-size: =
11pt; caret-color: rgb(0, 0, 0); color: purple;">change</a>&nbsp;<span =
style=3D"font-family: Calibri, sans-serif; font-size: 11pt; caret-color: =
rgb(0, 0, 0);" class=3D"">which was done ~8 months ago is to have 1 =
callflow =E2=80=9Cover RESTCONF/SSE=E2=80=9D as opposed to the previous =
separate callflows for http1.1 and http2. The reason http2 is mentioned =
in a few places is because of http2 streams. Section 4 already mentions =
=E2=80=9Cwhere HTTP2 is available to=E2=80=A6=E2=80=9D, so it looks like =
section 3.4 is the only place missing =E2=80=9Cwhen HTTP2 is =
used=E2=80=9D?</span></div></blockquote><div><br class=3D""></div><div>I =
recall that conversion and hence my alarm seeing all the HTTP2 text. =
&nbsp;Yes, adding "when/if HTTP2 is used" everywhere, to constantly =
remind the reader that it may not always be the case would be good. =
&nbsp; &nbsp;</div><div><br class=3D""></div><div>For Section 4, would =
replacing "where HTTP2 transport is available" with "when the HTTP2 =
transport is used" be better?</div><div><br class=3D""></div></div><div =
class=3D""><br class=3D""></div>Kent // contributor<div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_6BE0E4A0-0156-41DA-9B5D-3B107C46EBAA--

