Re: [Netconf] SSE and HTTP/2 in restcon-notif
Andy Bierman <andy@yumaworks.com> Sat, 29 September 2018 18:00 UTC
Return-Path: <andy@yumaworks.com>
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 E4240130E3F for <netconf@ietfa.amsl.com>; Sat, 29 Sep 2018 11:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=yumaworks-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pjdnBWhxFalJ for <netconf@ietfa.amsl.com>; Sat, 29 Sep 2018 11:00:35 -0700 (PDT)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 741BE1286D9 for <netconf@ietf.org>; Sat, 29 Sep 2018 11:00:34 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id g89-v6so7153035lfl.5 for <netconf@ietf.org>; Sat, 29 Sep 2018 11:00:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yumaworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iu7LwCCbv6Z2pt9L0PmYAYn0FCfKMnk6K+GOpxsq7Jw=; b=E4D5G2JuN23onqwQ3bk6TwuO8uh6N3YByTB3CyqutY3JUt3iqo95t78pBHKa7cKWun +Ev4CG7R98BWvHSDh6R8GBjOKlsMQfUU/T9eAqbHy8SKpK6+KlBAYRIxXgYPBCy/jkZU EHJNH68TDDU/AsnHIlhDKxIrug5WD85llNqqBZDJ5YygFqakhGhGZ6IKyO9Bkj0u6jnp vk532OieQUNPVA2nXUZUX29TwIe3RsEYAj+lu8o+h2dufukz7FuTWnMetCnL2jSzjdsx YAbgevFeK+RS6jcUHz2fuYeJKxrrTUjhK3bVzdpuDNs8Pfgl7Qi3+YphqrZhoiTtB1XR kfZA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iu7LwCCbv6Z2pt9L0PmYAYn0FCfKMnk6K+GOpxsq7Jw=; b=bDUVtr7/FR5wlqT1t1X6xE5IJHF91NTyifA1YW/r+0XFgKTEXYECn7Zc+fo8Cmais7 1VceKeTuKNAZ7PWJhPZTUwVhtMRmoebHgwVkalUlkk7fKPeZ8D+/aqNAQeMbQAGP3ySU 4ERPc5b7XfS1fSKlZaQOe+JWkVTLBgGBY2Vj1LntCYmf9USWrxZ5ABdgjPLxNlaZ/1C0 9oxOKgGvrnyO9Joxucw4aR/LN8w1RkJgwuy4z8ipBbgharZTM1DmuasrOHSbz+oQlWkU agK0N9FU+zEAQ9SfoyX54CmKXzbctzMgUbADfoNFXSGEkHJZELXjAWzkU2tfFhq50cTg 03Sg==
X-Gm-Message-State: ABuFfogi5PTz32HBg9iuMovMMsF1I7xgbGVCCyR3MNgtaC2Qzyw9MpjC 9FfBRNw7wdb7kthEWejISw0Dyr1IjqY9coI7wWkTAg==
X-Google-Smtp-Source: ACcGV63+knxPjgz63t5+R8KgeCOb9djopc4NW2y5NmRU/wGVZ+SnfrNCIOoH/snBjjQvY+vdbULj6pMk7wyf4ZJDWb4=
X-Received: by 2002:a19:3bcf:: with SMTP id d76-v6mr1828319lfl.126.1538244032514; Sat, 29 Sep 2018 11:00:32 -0700 (PDT)
MIME-Version: 1.0
References: <B51DAF9C-4294-44BF-9138-7145E61F42AB@juniper.net> <20180927.224854.1626742691261140238.mbj@tail-f.com> <CABCOCHSrEiibcUp99ho60FJr37RDLho+H14oc4htELjSHZqKvg@mail.gmail.com> <B8F9A780D330094D99AF023C5877DABA9B055E63@nkgeml513-mbx.china.huawei.com>
In-Reply-To: <B8F9A780D330094D99AF023C5877DABA9B055E63@nkgeml513-mbx.china.huawei.com>
From: Andy Bierman <andy@yumaworks.com>
Date: Sat, 29 Sep 2018 11:00:20 -0700
Message-ID: <CABCOCHRyuU712k+QHD0Ke5VF5bj7wSyHAcWxGyDsgT6NKA1ing@mail.gmail.com>
To: Qin Wu <bill.wu@huawei.com>
Cc: Martin Bjorklund <mbj@tail-f.com>, Netconf <netconf@ietf.org>, rrahman=40cisco.com@dmarc.ietf.org
Content-Type: multipart/alternative; boundary="00000000000022df540577065939"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/PaRsAEeck_4XaxQYiec6cyWinf0>
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: Sat, 29 Sep 2018 18:00:38 -0000
On Thu, Sep 27, 2018 at 8:40 PM Qin Wu <bill.wu@huawei.com> wrote: > > > > I envision the variation being relatively > > minor, something along the line of: > > > > if 1.1, then SSE. > > if 2.0, client MAY open a stream first. > > > > 3) resource URIs > > > > This is likely where we need to spend the most time. We know that > > establish-subscription returns a dynamically created URI, comparable > > to what a client might get from > ietf-restconf-monitoring:restconf-state\ > > /streams/stream/access/location. > > But it is not quite comparable. In the 8040 solution, the location > url is static, and then query parameters are provided by the client > in the POST to the SSE location. Thus, the server can free any > resources associated with the filter when the connection is > terminated. > > > > > > The RESTCONF procedure starts with the client > > examining /restconf-state/streams to determine stream and its location URL > > How does this monitoring information relate to the new solution? > > I assume both the old and new procedures can be supported by the same > server. > > Is it just ignored for a new subscription? > > > > Since all SSE data is always media type test/event-stream, each stream > entry indicates > > its secondary encoding format. This leaf is type string, and only 'xml' > and 'json' are supported > > in RFC 8040. The establish-subscription RPC has its own leaf for this > purpose. > > > > > > [Qin]: I am lost, should resource URIs returned by establish-subscription > same as location URL obtained from > > ietf-restconf-monitoring:restconf-state\/streams/stream/access/location. > > My understanding is if SSE is supported, let’s say HTTP 1.1, we will use > location URL returned from > > ietf-restconf-monitoring:restconf-state\/streams/stream/access/location > > as input parameter to trigger SSE. In case of SSE being supported, HTTP > GET(URI) is not needed ? wrong? > > But if SSE is not supported, let’s say HTTP/2, location URL is not needed. > HTTP POST(URI) is required. > > Please correct me, if I am wrong. > > > I think sec 3.2 Discovery says use a different /streams container https://tools.ietf.org/html/draft-ietf-netconf-restconf-notif-07#section-3.2 There should be a sub-section added in sec. 3 about coexistence between RFC 8040 notifications and this document. Obviously vendors need the option of supporting both in the same server. How do they interact, starting with the 2 different /streams data models. It should also be clear in this draft that the "uri" leaf contents are implementation-specific and MAY be predictable by a client application. Query parameters MAY be defined for use with the GET operation on this uri. Andy
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Kent Watsen
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Martin Bjorklund
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Reshad Rahman (rrahman)
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Eric Voit (evoit)
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Andy Bierman
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Kent Watsen
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Juergen Schoenwaelder
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Kent Watsen
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Qin Wu
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Andy Bierman
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Reshad Rahman (rrahman)
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Andy Bierman
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Kent Watsen
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Andy Bierman
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Martin Bjorklund
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Kent Watsen
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Andy Bierman
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Reshad Rahman (rrahman)
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Kent Watsen
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Eric Voit (evoit)
- Re: [Netconf] SSE and HTTP/2 in restcon-notif Kent Watsen