[netconf] About 'Call home considerations' in 'NETCONF over QUIC'
戴锦友 <djy@fiberhome.com> Mon, 01 June 2026 08:00 UTC
Return-Path: <djy@fiberhome.com>
X-Original-To: netconf@mail2.ietf.org
Delivered-To: netconf@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 300B5F88D1CE; Mon, 1 Jun 2026 01:00:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780300843; bh=m16ITcf32bjJ9ddkWx2VBDEycGX5jiGTyCEED3hsxv4=; h=Date:From:To:Cc:Subject; b=HqXzn1oLUYL5dy9j3CD6E7DfNIoP3+l4WjuqfHqkyLnVHLdOrx1CE9lMDIvd4m4wO 1WXMSA8kQGYB7gPDtRHy3N2c8dlSLPZ5cg+vX+HG//bKX4bs0HSiaAlcQ/e98+WiFC 4LbS36ixJz9V5qjEVGp7b4p0Q6Xu9rDQ5e8f974k=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pkaAndWSi4Qq; Mon, 1 Jun 2026 01:00:42 -0700 (PDT)
Received: from mxuc.fiberhome.com (mxuc.fiberhome.com [113.57.179.111]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 0F7DCF88D136; Mon, 1 Jun 2026 01:00:27 -0700 (PDT)
Received: from fiberhome.com (unknown [10.132.0.75]) by mxuc.fiberhome.com (MailData Gateway V2.8.8) with ESMTP id 4346238004A29; Mon, 1 Jun 2026 15:55:23 +0800 (CST)
Received: from LAPTOP-MAVU81J9 (unknown [10.39.6.30]) by app1 (Coremail) with UTF8SMTPA id AwSECgBQq6TjOh1quqTEAA--.30189S2; Mon, 01 Jun 2026 15:55:15 +0800 (CST)
Date: Mon, 01 Jun 2026 15:55:14 +0800
X-MD-Sfrom: djy@fiberhome.com
X-MD-SrcIP: 10.132.0.75
From: 戴锦友 <djy@fiberhome.com>
To: netconf <netconf@ietf.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.528[cn]
Mime-Version: 1.0
Message-ID: <2026060115551448198214@fiberhome.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart043823772337_=----"
X-CM-TRANSID: AwSECgBQq6TjOh1quqTEAA--.30189S2
X-Coremail-Antispam: 1UD129KBjvJXoWxAFW8JFyrKF17WF4UCFW3ZFb_yoWrAry8pF W3tr43KrWDtF17C34kX3WkWF9rtrWkArW7Jr12qr1kZa9xZF1ktFWay3Z5ta47GryUAr10 qr4jq39xZa40yaDanT9S1TB71UUUUU7qnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUvmb7Iv0xC_KF4lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_tr0E3s1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_GcCE3s1l84ACjcxK6I8E87Iv67AKxVW0oVCq3wA2z4x0Y4vEx4 A2jsIEc7CjxVAFwI0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAv7VC0I7IYx2IY 67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r1j6r4UM4x0Y4 8IcxkI7VAKI48JM4xvF2IEb7IF0Fy264kE64k0F24lFcxC0VAYjxAxZF0Ex2IqxwCY02Av z4vE-syl42xK82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67 AKxVWUGVWUWwC20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1Y6r17MIIY rxkI7VAKI48JMIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14 v26r1j6r4UMIIF0xvE42xK8VAvwI8IcIk0rVWUJVWUCwCI42IY6I8E87Iv67AKxVWUJVW8 JwCI42IY6I8E87Iv6xkF7I0E14v26r1j6r4UMVCEFcxC0VAYjxAxZFUvcSsGvfC2KfnxnU UI43ZEXa7IU8VyI5UUUUU==
X-CM-SenderInfo: hgm1qwhleh2xxrphhudrp/
Message-ID-Hash: QZC3CILJS57MJERMPGI3R63BIHAXELJU
X-Message-ID-Hash: QZC3CILJS57MJERMPGI3R63BIHAXELJU
X-MailFrom: djy@fiberhome.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-netconf.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "netconf-chairs@ietf.org" <netconf-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [netconf] About 'Call home considerations' in 'NETCONF over QUIC'
List-Id: NETCONF WG list <netconf.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/gTDxKIa3fE6AlNRvF2gh3LpAfSc>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netconf>
List-Help: <mailto:netconf-request@ietf.org?subject=help>
List-Owner: <mailto:netconf-owner@ietf.org>
List-Post: <mailto:netconf@ietf.org>
List-Subscribe: <mailto:netconf-join@ietf.org>
List-Unsubscribe: <mailto:netconf-leave@ietf.org>
Dear colleagues,
Good morning or good afternoon!
Before IETF 125 Shenzhen meeting, a concern about
"call home"(section 5) in "NoQ" (draft-ietf-netconf-over-quic)
has been brought forward.
Through discussion among co-authors of "NoQ", we've got
several sugguested solutions, and one of the properest solution
is given in the following section 5 of 'NoQ'.
Please review and comment on it.
Thank you!
Best regards!
The proposed solution is given as follows:
{
5. Call home considerations
5.1. protocol-layering perspective
Netconf call home mechanism is described in [RFC 8071]. However, [RFC 8071] is based on SSH and TLS, and the intrastructure transport protocol of is TCP. Because ifrastructure transport of NETCONF over QUIC is QUIC, implementation of call home mechanism of NoQ is also different. TLS 1.3 is implemented in QUIC with TLS record layer being omitted (see RFC 9001)
The following diagram illustrates call home from a protocol-layering perspective based on QUIC:
Server Client
| |
| 1. QUIC |
|----------------------------------------------->|
| |
| |
| 2. NoQ |
|<-----------------------------------------------|
| |
| |
| 3. NETCONF |
|<-----------------------------------------------|
| |
Note: Arrows point from the "client" to
the "server" at each protocol layer.
Figure 2: Call Home Sequence Diagram based on QUIC
This diagram makes the following points:
* The NETCONF server begins by initiating a QUIC connection to the
NETCONF client.
* Using this QUIC connection, the NETCONF client initiates a NETCONF
session to the NETCONF server.
5.2. Operation of the client
C1 The NETCONF client listens for QUIC connection requests
from NETCONF servers. The client MUST support accepting
QUIC connections on the IANA-assigned ports.
C2 The NETCONF client accepts an incoming QUIC connection
request and a QUIC connection is established.
C3 Using this QUIC connection, the NETCONF client starts
certificate path validation.
C4 Tthe NETCONF client MUST ensure that the presented certificate
has a valid chain of trust to a preconfigured issuer certificate, and that
the presented certificate encodes an "identifier" [RFC6125] that
the client was aware of before the connection attempt. How
identifiers are encoded in certificates MAY be determined by a
policy associated with the certificate's issuer. For instance, a
given issuer may be known to only sign IDevID certificates
[Std-802.1AR-2009] having a unique identifier (e.g., a serial
number) in the X.509 certificate's "CommonName" field.
C5 the NETCONF client starts the NETCONF client [RFC6241] over the
QUIC connection, assuming the use of the IANA-assigned ports.
5.3. Operation of the server
S1 The NETCONF server initiates a QUIC connection request to
the NETCON client. The source port may be per local
policy or randomly assigned by the operating system. The server
MUST support connecting to one of the IANA-assigned ports.
S2 The QUIC connection request is accepted and a QUIC connection is
established.
S3 Using this QUIC connection, The NETCONF server will send its certificate
to the client. the server MUST also send all intermediate certificates leading
up to a well-known and trusted issuer.
S4 The NETCONF server starts either the NETCONF server [RFC6241]
protocol based on QUIC, assuming the use of the IANA-assigned ports.
S5 If a persistent connection is desired, the NETCONF server,
as the connection initiator, SHOULD actively test the
aliveness of the connection using a keep-alive mechanism.
5.4. RFC8071 Call Home Specific Case
In the case of [RFC8071] Call home feature, where the NETCONF server
initiates the transport connection to the NETCONF client, Table 1
will be used as follows: - the Client, referred in the Table, means
the QUIC initiating party, therefore the NETCONF server and - the
Server means the QUIC receiving party, therefore the NETCONF client.
}
David Dai
Fiberhome Technologies/CICT
Addr: Gaoxin Road 6#, Wuhan, Hubei, China
Tel: +86 27-87693442-8318
MObile: +86 15377065812
Fax: +86 27-87693784
E-mail: djy@fiberhome.com
- [netconf] About 'Call home considerations' in 'NE… 戴锦友
- [netconf] Re: About 'Call home considerations' in… Kent Watsen
- [netconf] Re: About 'Call home considerations' in… 戴锦友
- [netconf] Re: About 'Call home considerations' in… 戴锦友
- [netconf] Re: About 'Call home considerations' in… 戴锦友
- [netconf] Re: About 'Call home considerations' in… Kent Watsen
- [netconf] Re: About 'Call home considerations' in… 戴锦友
- [netconf] Re: About 'Call home considerations' in… Kent Watsen
- [netconf] Re: About 'Call home considerations' in… 戴锦友
- [netconf] Re: About 'Call home considerations' in… Per Andersson
- [netconf] Re: About 'Call home considerations' in… Per Andersson
- [netconf] Re: About 'Call home considerations' in… 戴锦友
- [netconf] Re: About 'Call home considerations' in… 戴锦友