IETF Logo Mail Archive

Re: [Netconf] SSE and HTTP/2 in restcon-notif

Kent Watsen <kwatsen@juniper.net> Thu, 27 September 2018 22:56 UTC

Return-Path: <kwatsen@juniper.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 A87EC130E03 for <netconf@ietfa.amsl.com>; Thu, 27 Sep 2018 15:56:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=juniper.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F0u4edw3yOJS for <netconf@ietfa.amsl.com>; Thu, 27 Sep 2018 15:55:59 -0700 (PDT)
Received: from mx0b-00273201.pphosted.com (mx0b-00273201.pphosted.com [67.231.152.164]) (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 79DFF130DE4 for <netconf@ietf.org>; Thu, 27 Sep 2018 15:55:59 -0700 (PDT)
Received: from pps.filterd (m0108163.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w8RMtumN001026; Thu, 27 Sep 2018 15:55:57 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=PPS1017; bh=RY1gJzdOwwX4hffgCulsCDwKFUsbk3e5+rtdmB75CxM=; b=K0d6v4lAv1hU1lMZHilq6FkE0C7QYye5mcSXd31+j39LbyTs5T06ItSFiN8QZKSB3sIi 5ffE8UKQ6tHE0jw/U8JmdMx5lBjb0o+LRe1dUpz+5i+LTqg8y0Jnnv0x1ndnc0GAnW3v zpsi1KdtmU74mWHXNAvJc2YBH6dWLNNRLqM/Cy6YaGJJU+8nnWlw1wm4cqmCc1wZGb0O lk8q+5MdqzxsmecapUNrP3fInYYARKLeQbt9O/4qaz3PbMEVUzGBKnkCPuvf3B/7jfa8 oHLwNDHmlwLRFyEcDOZq3mjGFTT9QE6M2U/9RdYQNjmvnuOcbXqbxhzAWd7pkeQMF/Fg 5g==
Received: from nam02-bl2-obe.outbound.protection.outlook.com (mail-bl2nam02lp0080.outbound.protection.outlook.com [207.46.163.80]) by mx0b-00273201.pphosted.com with ESMTP id 2ms3ujrhf1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 27 Sep 2018 15:55:57 -0700
Received: from DM6PR05MB4665.namprd05.prod.outlook.com (20.176.109.202) by DM6PR05MB4588.namprd05.prod.outlook.com (20.176.79.153) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1185.14; Thu, 27 Sep 2018 22:55:54 +0000
Received: from DM6PR05MB4665.namprd05.prod.outlook.com ([fe80::8574:3388:660d:e495]) by DM6PR05MB4665.namprd05.prod.outlook.com ([fe80::8574:3388:660d:e495%3]) with mapi id 15.20.1185.014; Thu, 27 Sep 2018 22:55:54 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: Andy Bierman <andy@yumaworks.com>, Martin Bjorklund <mbj@tail-f.com>
CC: Netconf <netconf@ietf.org>, "rrahman=40cisco.com@dmarc.ietf.org" <rrahman=40cisco.com@dmarc.ietf.org>
Thread-Topic: [Netconf] SSE and HTTP/2 in restcon-notif
Thread-Index: AQHUVpLBkBpJSSIQbkWRq5O8cMUK2aUEmdsAgAAMawD//9QCgA==
Date: Thu, 27 Sep 2018 22:55:54 +0000
Message-ID: <F8C1FF8F-3CCB-47B1-86F8-E43F9FCE1DFC@juniper.net>
References: <B51DAF9C-4294-44BF-9138-7145E61F42AB@juniper.net> <20180927.224854.1626742691261140238.mbj@tail-f.com> <CABCOCHSrEiibcUp99ho60FJr37RDLho+H14oc4htELjSHZqKvg@mail.gmail.com>
In-Reply-To: <CABCOCHSrEiibcUp99ho60FJr37RDLho+H14oc4htELjSHZqKvg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.2.180910
x-originating-ip: [66.129.241.13]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM6PR05MB4588; 6:iNFAQT5qLov8Ch7rPBmYVBRuj4shJRlJJIl2Rs8ysck+1/3DmuX6jHsezdzIzVwn2RiYCO86YS3OCvHyPtNiLQ1BR+0N0ZYsfoUjtfHXzDSH6m08BE1LNMf6bPQFCOqQMQGjRYTyNbzj+dsFQPghA/+J5gRpexipDnRaV8e73HLvevUMcXn9G9fivjLdUSmtyBVWpMns6Mk+Awe/tCE9ophahK/3gncPL0uKzM5Gkfr0vrQe07alJQURB5ZXg3MyhlXH03fRjwp6i1ClSHcaDJL0tLjs55yrmbb6cNaTxLz6aSXPzjmW0ZUOUG9PhoxAybbT2MNmMoI1NrLqEWVYGBi49bVztdQI57ywJSkP/2K8FSxd9p5b0CWt4PhxkvGO4Pi38McpVDvQJTFmu67A6WLI4JQIr/T4c0mqmOtgrzFg4aVct9arp7VhLa6Fcdn5WtrNIAZ+OBaBHvB84pWR2w==; 5:PqKOksdCXqemyT9PneSD0f0j3ZASmE9YpBlvvwnWhLOm+5v6SwK0a8TjilHrofcQsLb+Hs0Yf82HogrXutW0MHZhIIKSNf5N9P8Ztsq1KoUMXp39/johYZmKZqcggy+b8QgQ8AGgo7Z+eyzBhuxjfVKX586QOQ7TmWdvVpTpoAE=; 7:ZAc/kKvlX4pg3hq96HqS9sKdw4jYZ/GsEOi79ZEbRnQOOJ+00kgQBFZEok+H9oXprpRrYPeMeySKs34qOGDyCqBs8sbjS4hVK0VYHDXH6SthnbHBOOxTac1DMDu+vGDdxEy5WZPqqsevMJ8JNOj5+Itnb5wEOwRkM0x2ZKHvDWH6/KcD/7CDP/gTk80Kg6+z6Bzjerz/VKc022oqxboc9zHQMuSalTiA9L0Pjz4HFXQ/EUqtnNgtW1qdyhF1Cwdu
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: a6deea95-f54f-44f1-6898-08d624cc6192
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534165)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:DM6PR05MB4588;
x-ms-traffictypediagnostic: DM6PR05MB4588:
x-microsoft-antispam-prvs: <DM6PR05MB45889CAE9D01C5B36D5448F2A5140@DM6PR05MB4588.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3231355)(944501410)(52105095)(10201501046)(3002001)(93006095)(93001095)(6055026)(149066)(150057)(6041310)(20161123562045)(20161123560045)(20161123558120)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991041); SRVR:DM6PR05MB4588; BCL:0; PCL:0; RULEID:; SRVR:DM6PR05MB4588;
x-forefront-prvs: 0808323E97
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(136003)(376002)(396003)(366004)(346002)(189003)(199004)(2616005)(6246003)(82746002)(54906003)(68736007)(478600001)(58126008)(110136005)(25786009)(8936002)(316002)(2906002)(6436002)(34290500001)(81156014)(4326008)(6116002)(33656002)(6506007)(3846002)(99286004)(76176011)(81166006)(8676002)(305945005)(14454004)(446003)(71200400001)(71190400001)(229853002)(5250100002)(105586002)(186003)(11346002)(256004)(6512007)(53936002)(6486002)(86362001)(97736004)(486006)(5660300001)(102836004)(83716004)(2900100001)(26005)(7736002)(106356001)(66066001)(476003)(36756003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR05MB4588; H:DM6PR05MB4665.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: O8JVp5Y20ChYSO09rjBEomXfyMaEsEihn5BvQJcWcVx3oJUdMKt1zPfwGtCxuDCc3KMEPYpMIaiXdXjdh7VnBwduBxrRqcS8FvTQBz3XChKSZm7ERESwrX52SocsXYQOH3G9EsAVXMwD2cbm2FqVmNY5ouL39++h8CPjNZTpt6QtyfvLpaunBpghZbPVwthVHMh7c/SA8HtVIsPgXpShPl3GC1QX7xapeI3D99f7KAXwo8cqvphWtDdyC3wpj7kg+oB5VjcTB4XCr0U8SqNzEs2o7XuyccuxVYrL4G8Es5wd63tQotE8tLKGMVzHYOQisKIl8/Y+kt4K18ftUY6DrFGRzpWF1k2uH/vn+fOLWtM=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <71C1EC35407F094D8D4AB0148D77244C@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: a6deea95-f54f-44f1-6898-08d624cc6192
X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Sep 2018 22:55:54.7010 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR05MB4588
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-09-27_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_spam_notspam policy=outbound_spam score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1809270213
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/Ub1eM8Ruzz1qa2rMLwjKI_6if6o>
Subject: Re: [Netconf] SSE and HTTP/2 in restcon-notif
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Configuration WG mailing 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: Thu, 27 Sep 2018 22:56:02 -0000

>> 2) HTTP/2
>> 
>>    Not sure where this landed, but my thoughts are this draft needs
>>    to support both 1.1 and 2.0.
>
> Why?  I don't really understand why restconf-notif, or RESTCONF for
> that matter, need special handling for HTTP/2.  Won't RESTCONF "just
> work" with HTTP/2?
>
> Agreed

It seems that we're all in agreement - RN should work for both 1.1
and 2.0.  Unclear why this caused a stir. 

Still, I thought there was a perceived common case for a client to
be able to use another HTTP/2 stream to collect logs.  If the client
can do this already and it's completely transparent to the server,
then having a statement just saying that would be good.  This is
what my comment was about.

BTW, Section 3.1 regards how a RESTCONF client can promote HTTP 1.1
to HTTP 2.0.  It looks like a good approach, but should the text be 
in another document, if it's not specific to RN?  

Kent // contributor

v2.23.0 | Report a Bug | By Email