Re: [netconf] I-D Action: draft-dai-quic-netconf-01.txt
Mahesh Jethanandani <mjethanandani@gmail.com> Tue, 29 October 2019 18:53 UTC
Return-Path: <mjethanandani@gmail.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 B6B391209D4 for <netconf@ietfa.amsl.com>; Tue, 29 Oct 2019 11:53:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 Yq6KoFRgyfzO for <netconf@ietfa.amsl.com>; Tue, 29 Oct 2019 11:53:35 -0700 (PDT)
Received: from mail-pl1-x62f.google.com (mail-pl1-x62f.google.com [IPv6:2607:f8b0:4864:20::62f]) (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 926D612088A for <netconf@ietf.org>; Tue, 29 Oct 2019 11:53:35 -0700 (PDT)
Received: by mail-pl1-x62f.google.com with SMTP id k7so8107101pll.1 for <netconf@ietf.org>; Tue, 29 Oct 2019 11:53:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=tipdjot2Z7EKqdgkClTCHutL/mqeSdVKFX5OKwDkl3I=; b=K2c2/u/6KgvroSpWu8Wz6hvJALAP/w0/hT7lupxhK6o4XpA7T0P83urquhR5NXjx3F 59alDgqiIEqjYrkFDw6NaSp3YKn+OEt/OpyNdsGr2z9d385+blEqeruqis5WGtVVDlVe 2VnIb23T6h4rFfDM6XqkUiiEoJse5dEg+Fc+B7rYo4Bg4CoxRy7wK2SwWBcOI3h1+aJ6 nOZqyP792619fPZ6kwtgPiu0te3s/tWqAN8lx+1RQ39fhFQV+RX5w3yYftu/ayzKUwlF s1AegwUYLAb83iqO8lhJUKfD41J8tXMIQFGWTtAo5KR3pEitFWN6tTBDd4KQq/QahHXC FtWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=tipdjot2Z7EKqdgkClTCHutL/mqeSdVKFX5OKwDkl3I=; b=ssOQ3c/QjAc6BYK7dRdU3W7k+MpsmZZrqHxZyJhTZJXZjQnFib6003ckA5KZCRcRZn /NlsTWW+A7qWOe0lQG0HDJ8W0gggygPcSXE35cjPHfnk6evIh2zsA4gPg6jhjVVQ2kTj p+wzDh5P4DYM+quP92M8jHRDq7gTS4+LTKrroB36xE7nUnRK3EUbzcvbvh6CQ0W8AWFe 9z6rY3M0Lvl1xnR50Oabngx1+VAhom3eGqRquuE02z/cEx3OV5hWt8HVEDY5bupW8j+j 24y15xhAKui5HDnLO4kLoEq/EUNEF9yZl3m173kqgpORAxZllODEfECwICeK4t0XYUSN crWw==
X-Gm-Message-State: APjAAAX/rYaSLMMle2OmuKSDSoaM+PJIiJlpeeoKfiFz/vaT2rozlVVR 4Xx1ukmNalpNtpLrVwulq9c=
X-Google-Smtp-Source: APXvYqxhDwawQVhGH8DO1UOHRSMOblRE1jgdQLeeiN5FE1vtUVgFywf0UlD5CNGniQG10CxAXq6/BQ==
X-Received: by 2002:a17:902:b20b:: with SMTP id t11mr140256plr.89.1572375214834; Tue, 29 Oct 2019 11:53:34 -0700 (PDT)
Received: from [10.33.123.155] ([66.170.99.2]) by smtp.gmail.com with ESMTPSA id d10sm14001671pfh.8.2019.10.29.11.53.33 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 Oct 2019 11:53:33 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <01C76D74-D327-4AA7-9824-7FC90434A22B@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_2CD182DB-2D92-469F-8E6E-BF26662EA741"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Tue, 29 Oct 2019 11:53:32 -0700
In-Reply-To: <06a501d58e50$fa7b2540$4001a8c0@gateway.2wire.net>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: tom petch <ietfc@btconnect.com>
References: <157227295327.19834.10106980669998711276@ietfa.amsl.com> <06a501d58e50$fa7b2540$4001a8c0@gateway.2wire.net>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/ERcC3Ur4rpLLLJM9bp5CD_nMduI>
Subject: Re: [netconf] I-D Action: draft-dai-quic-netconf-01.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, 29 Oct 2019 18:53:40 -0000
Thanks Tom for bringing it to the NETCONF mailing list. Authors, have you considered presenting this draft in the NETCONF WG? Some quick comment: s/This document specifies how to use QUIC as the secure transport protocol for QUIC./This document specifies how to use QUIC as the secure transport protocol for NETCONF./ Can you also expand on the following statement, in light of the fact that NETCONF is a client/server protocol, and that each NETCONF session is a separate TCP connection? As is well know, TCP has some shortcomings such as head-of-line blocking Thanks. > On Oct 29, 2019, at 5:06 AM, tom petch <ietfc@btconnect.com> wrote: > > Dai > > There is something wrong with the formatting of this I-D which, for me, > makes it too hard to read. The text is littered with additional > spaces, like tab characters gone wild or a malign word processor. I > would like that fixed before I try and read it (extra spaces > inserted for effect:-). > > Tom Petch > > ----- Original Message ----- > From: <internet-drafts@ietf.org> > To: <i-d-announce@ietf.org> > Sent: Monday, October 28, 2019 2:29 PM > >> A New Internet-Draft is available from the on-line Internet-Drafts > directories. >> >> >> Title : Using NETCONF over QUIC connection >> Authors : Jinyou Dai >> Xueshun Wang >> Yang Kou >> Lifen Zhou >> Filename : draft-dai-quic-netconf-01.txt >> Pages : 13 >> Date : 2019-10-28 >> >> Abstract: >> The Network Configuration Protocol (NETCONF) provides mechanisms to >> install, manipulate, and delete the configuration of network > devices. >> At present, almost all implementations of NETCONF are based on TCP >> protocol. QUIC, a new UDP-based transport protocol, can facilitate > to >> improve the transportation performance when being used as an >> infrastructure layer of NETCONF. This document describes how to > use >> the QUIC protocol as the transport protocol of >> NETCONF(NETCONFoQUIC). >> >> >> >> >> The IETF datatracker status page for this draft is: >> https://datatracker.ietf.org/doc/draft-dai-quic-netconf/ >> >> There are also htmlized versions available at: >> https://tools.ietf.org/html/draft-dai-quic-netconf-01 >> https://datatracker.ietf.org/doc/html/draft-dai-quic-netconf-01 >> >> A diff from the previous version is available at: >> https://www.ietf.org/rfcdiff?url2=draft-dai-quic-netconf-01 >> >> >> Please note that it may take a couple of minutes from the time of > submission >> until the htmlized version and diff are available at tools.ietf.org. >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> _______________________________________________ >> I-D-Announce mailing list >> I-D-Announce@ietf.org >> https://www.ietf.org/mailman/listinfo/i-d-announce >> Internet-Draft directories: http://www.ietf.org/shadow.html >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > _______________________________________________ > netconf mailing list > netconf@ietf.org > https://www.ietf.org/mailman/listinfo/netconf Mahesh Jethanandani mjethanandani@gmail.com
- Re: [netconf] I-D Action: draft-dai-quic-netconf-… tom petch
- Re: [netconf] I-D Action: draft-dai-quic-netconf-… Mahesh Jethanandani