Re: [Netconf] HTTP2 configured subscriptions, is SSE over HTTP1.1 necessary too? (was RE: Anyone want just Configured Subscriptions?)

Kent Watsen <kwatsen@juniper.net> Wed, 11 July 2018 23:41 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 68875130F06 for <netconf@ietfa.amsl.com>; Wed, 11 Jul 2018 16:41:38 -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 wE8XAXkVvBUq for <netconf@ietfa.amsl.com>; Wed, 11 Jul 2018 16:41:36 -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 12BC0130E86 for <netconf@ietf.org>; Wed, 11 Jul 2018 16:41:35 -0700 (PDT)
Received: from pps.filterd (m0108160.ppops.net [127.0.0.1]) by mx0b-00273201.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w6BNdYR8026829; Wed, 11 Jul 2018 16:41:33 -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=5A5DkzwyLAs8cSmze1sIBLRMU8384rDaK1baymqPXPE=; b=apo+Qhoxq08AQdY9ridQLv3TtNpGdcgTyWUOEMoy6Mh+tNoqiIaND9LQHmUOl6mkTPof AFo9RnyiqZhckoxScpPJkh25C1KgxQo6nWHpu6Rj7YdZDgxoLcsO3Ry8GKs2ldOqIhyM TGPZeo2eLFdlcG0G/CiR7/Gj2khbT3kiND0m6TVXpvkTqZQaGaXO/KXicdsLV4zpKy/y /ZoyrGd8qjkdVVMdYjGtF1LBbMatKa8yu9CF2N7jeECCq3etZFUBQbRZ0E4E4CMcxvAj RJL2KSybEoI/zqFoaj5dDYWjoNuyB5aKbXnu8iGJ430KM9D3PvME9KRzQqE6vcCymT1y Jg==
Received: from nam03-by2-obe.outbound.protection.outlook.com (mail-by2nam03lp0049.outbound.protection.outlook.com [216.32.180.49]) by mx0b-00273201.pphosted.com with ESMTP id 2k5mn5s6hb-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 11 Jul 2018 16:41:33 -0700
Received: from BYAPR05MB4230.namprd05.prod.outlook.com (52.135.200.153) by BYAPR05MB3992.namprd05.prod.outlook.com (52.135.199.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.952.12; Wed, 11 Jul 2018 23:41:30 +0000
Received: from BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::959d:9fbe:90e4:3cc]) by BYAPR05MB4230.namprd05.prod.outlook.com ([fe80::959d:9fbe:90e4:3cc%4]) with mapi id 15.20.0952.017; Wed, 11 Jul 2018 23:41:30 +0000
From: Kent Watsen <kwatsen@juniper.net>
To: "Eric Voit (evoit)" <evoit@cisco.com>, Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
CC: Andy Bierman <andy@yumaworks.com>, Netconf <netconf@ietf.org>
Thread-Topic: HTTP2 configured subscriptions, is SSE over HTTP1.1 necessary too? (was RE: Anyone want just Configured Subscriptions?)
Thread-Index: AdQYqufU0EVBnOscSI2bwl9YP08sXAAriGAAAAIb3oD//9thgA==
Date: Wed, 11 Jul 2018 23:41:30 +0000
Message-ID: <BB90E468-C41B-4C32-9255-45106EF8C094@juniper.net>
References: <837fb78118064c269d0312d010de5607@XCH-RTP-013.cisco.com> <20180711205210.simibmsmzrmlquou@anna.jacobs.jacobs-university.de> <2686183aa7e34ca78714d19d659eecc4@XCH-RTP-013.cisco.com>
In-Reply-To: <2686183aa7e34ca78714d19d659eecc4@XCH-RTP-013.cisco.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: [66.129.241.11]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR05MB3992; 7:OiF2H3yn/nN1AFAHUgKotQUbShxqRTlmdl0XS0h5hw+K6n+ZsRwcTewSPOfKfb6GBEIr0zRlyOUOvPZqrPiD1XUYn0a/A0MTnViA4CqtcrNlbU9dS8IDzWqobPlQ3kYzRoQqhMxo//Df9c7g4MwA7sDyaNXW+FJ1jpayPZQtDLZCfJvnydHpPArVg9RVD7itZZT8LqGQr8rFv4/1oJ5dH5iL/HfENPLp2wBwtDV/DGE9jbn3MGh4W4pbLD1zygSG
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-correlation-id: c6b132a1-7a94-4702-d177-08d5e787d427
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989117)(5600053)(711020)(4534165)(4627221)(201703031133081)(201702281549075)(8990107)(48565401081)(2017052603328)(7153060)(7193020); SRVR:BYAPR05MB3992;
x-ms-traffictypediagnostic: BYAPR05MB3992:
x-microsoft-antispam-prvs: <BYAPR05MB39927C9A577805170E77C5E3A55A0@BYAPR05MB3992.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)(8121501046)(5005006)(3002001)(93006095)(93001095)(10201501046)(3231311)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(20161123562045)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:BYAPR05MB3992; BCL:0; PCL:0; RULEID:; SRVR:BYAPR05MB3992;
x-forefront-prvs: 0730093765
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(396003)(366004)(376002)(39860400002)(346002)(199004)(189003)(25786009)(11346002)(6436002)(97736004)(8936002)(86362001)(476003)(106356001)(305945005)(105586002)(83716003)(82746002)(7736002)(4326008)(76176011)(2616005)(446003)(53936002)(66066001)(2906002)(6246003)(6486002)(6512007)(99286004)(5660300001)(33656002)(478600001)(81156014)(316002)(102836004)(14444005)(36756003)(256004)(6506007)(110136005)(14454004)(229853002)(3846002)(68736007)(186003)(26005)(486006)(58126008)(2900100001)(5250100002)(81166006)(8676002)(54906003)(6116002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR05MB3992; H:BYAPR05MB4230.namprd05.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
x-microsoft-antispam-message-info: YAldb0x4AcgM7GGoerWvIcXbRSEGNW6cERSUulYhnvWxsTVyQ6VovInu2knrf1bmaZiD6bN3EAXxkn6O5nU1IiuBPrY9GFsk/oC34Nm1A1fUweOPLV+S+pvty1wfnxKd4ZTfpL4CNHFs2Mg4xdi6OqcG1eaKtyu4AqEjK2HDzZlbxzu6RAupf7yHDQGnAQC/UgLdubDNBGufaeXock079KUDywREUobm+ekpga5RsTLUbi+bgKqwoUrqCyZc0CFnAyPz7rwxX56ACVVKehyJAsNANGzfl3u+oz9QyGc0PwJsIscYwJKfIVfkWYXk6IfXMM0LWCNG4CTJS6x7KZv6bUDFhyknDGqxB/184FgXS7U=
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <C2FFAC961D21F1488AB1DB0499519829@namprd05.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: c6b132a1-7a94-4702-d177-08d5e787d427
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Jul 2018 23:41:30.7012 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR05MB3992
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-07-11_06:, , 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-1806210000 definitions=main-1807110248
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/iB2LqwB4bQvXpJ-1EH5YgEIUf44>
Subject: Re: [Netconf] HTTP2 configured subscriptions, is SSE over HTTP1.1 necessary too? (was RE: Anyone want just Configured Subscriptions?)
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.27
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: Wed, 11 Jul 2018 23:41:39 -0000

Hi Eric,

> It took a while, but we are at a 100% solution for NETCONF.  Things 
> really are done, (pending the completion of Kent's netconf-server work.)
> Cutting things back to 80% would take another 20% time.  And per others' 
> emails, the market demand is now or never.

Where is the 100% solution?  The drafts are still churning.  As of right
now, we don't have a set of drafts that we can call another WGLC on.

As I see it, there are only two choices:

 1. reduce the scope to just dynamic subscriptions, hit WGLC around Sep
    and maybe have RFCs by the year's end.  After which, the WG should
    immediately start working on the configured solution, with hope of
    getting it published in 2019 (possibly achievable since must of the
    groundwork has been laid already)

 2. maintain the scope to dynamic + configured, which will take longer
    (maybe not much, hard to say) to reach WGLC, but any NETCONF or 
    RESTCONF based transport notif drafts will be blocked by RFC Editor
    until the client/server suite of drafts completes (read: sometime
    next year), and there is a chance that we'd need to update them
    again then, if only to generate correct/final tree-diagrams.

It's the WG's choice. I know that some have expressed interest in having
just dynamic now.  I don't have a strong opinion either way.  This question
would make for a good hum next week.


Kent // co-chair