IETF Logo Mail Archive

Re: [netconf] New Version Notification for draft-turner-netconf-over-tls13-00.txt

Mahesh Jethanandani <mjethanandani@gmail.com> Mon, 20 June 2022 17:45 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 A35E5C14F75F for <netconf@ietfa.amsl.com>; Mon, 20 Jun 2022 10:45:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4K39OhNWcwQX for <netconf@ietfa.amsl.com>; Mon, 20 Jun 2022 10:45:26 -0700 (PDT)
Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE903C14F745 for <netconf@ietf.org>; Mon, 20 Jun 2022 10:45:26 -0700 (PDT)
Received: by mail-pj1-x1029.google.com with SMTP id h9-20020a17090a648900b001ecb8596e43so1790178pjj.5 for <netconf@ietf.org>; Mon, 20 Jun 2022 10:45:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=6K/5Wv0mwOFW6wSko5gvjuaDzxL0QPGy3xaec7Xp3yY=; b=kI5JgGlCB9CFKS5Pi8NGjJXtk+U4qO7CyAgfIiG7ykIU3Sfd/a9jc82KsAsJRikOby y1/mADBy04FYFVSubM/L/WevpH842S/M3o9M0IQ4aqFxI67A6Ykyjv34jETcagGeKjdH AXxJlvik67Te+zIJgqOx9ngFCQYPLsQLs+SxHXFVelu4SiD65UpD37j0yARgjp0e99GH 4QPWDTl/6MMnujvDjXsaHoWWH5S54e734jTOOimhOxrpHBOKWHzXZ/AEAjCTUDZS2y+s zTDl4wGxZPEWewhzMBCES0SyGN7sfVmrTIWvuzeZFKWuTJH7W0YZSrIfr7TDrOWJqdyU pSzw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=6K/5Wv0mwOFW6wSko5gvjuaDzxL0QPGy3xaec7Xp3yY=; b=4qAYc+k8hGBpaIXkmx/YaFzG5ZEgOBN17zMPmA0lHR02oQwrL5YQT66+v05ZJfy/A+ 2LdZdhuQE6SNOaUMvO5XCVQQ7D25R5o42JNZSz04UtrQAT647vibiZMMNZJj70zuic8S AeFwW2WTyBerbzFU4ujXtSIP5R6KHvP94RVFbBlwktn4lk1Q0Q9dEMXvFYITalSdaUl2 eRDu5wMWZsnGgmKtPzkDbb56xIh2d1+IzumDVFde2Dn0yTDnSd9gms0GFbx46nrwZtyI cb31c7xD7W4rb/RVToOb7eeAC7Slx3KfslialsEth53OFntQgZoZKfbm3PbRGNinBIha N7YQ==
X-Gm-Message-State: AJIora9/d9q5kPLZ7xMNLlgLz8eaMdxRRNbZYxnEcEt23mNyj7bWxcAV uj1bSF9thTNxlQ22HcROvROpa8EdbtE=
X-Google-Smtp-Source: AGRyM1uqi+8eZLurb/MGrn1tATOh258JGqGqeH8TyFf9kcZs8k/ghpaxllGZ/HqIZYMEem2EZvlk8w==
X-Received: by 2002:a17:90a:1c09:b0:1ea:91d4:5a7f with SMTP id s9-20020a17090a1c0900b001ea91d45a7fmr38994022pjs.232.1655747126355; Mon, 20 Jun 2022 10:45:26 -0700 (PDT)
Received: from smtpclient.apple (adsl-70-234-233-187.dsl.rcsntx.sbcglobal.net. [70.234.233.187]) by smtp.gmail.com with ESMTPSA id b193-20020a6334ca000000b0040c95aeae26sm4182641pga.12.2022.06.20.10.45.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 20 Jun 2022 10:45:25 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <4B98C49D-2749-4A51-ACE8-563F8F3BFC83@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_F3AD0206-AE6F-4B2B-A759-533495D96B0A"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\))
Date: Mon, 20 Jun 2022 10:45:25 -0700
In-Reply-To: <4B82E1ED-C8BF-4E96-9C9C-E5BD24232884@sn3rd.com>
Cc: Netconf <netconf@ietf.org>
To: Sean Turner <sean@sn3rd.com>
References: <165542805965.61010.3200558486270989010@ietfa.amsl.com> <4B82E1ED-C8BF-4E96-9C9C-E5BD24232884@sn3rd.com>
X-Mailer: Apple Mail (2.3654.120.0.1.13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/YIPIJhtQdhH2qza8baMs0-CRARo>
Subject: Re: [netconf] New Version Notification for draft-turner-netconf-over-tls13-00.txt
X-BeenThere: netconf@ietf.org
X-Mailman-Version: 2.1.39
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: Mon, 20 Jun 2022 17:45:30 -0000

Hi Sean,

As a contributor, I would support this work. Thanks for bringing it forth.

Considering that you are relying on 7589 for most of the text, the WG can debate whether this should be a -bis or a separate RFC.

> On Jun 16, 2022, at 6:19 PM, Sean Turner <sean@sn3rd.com> wrote:
> 
> Hi! Russ and I submitted this I-D to address how to use NETCONF over TLS1.3. The I-D is based on RFC 7589 (in fact we refer to RFC 7589 for the vast majority of the text) and only add the TLS 1.3 specific recommendations, which are 0-RTT and cipher suites.
> 
> The GH repo can be found here if you have any comments:
> https://github.com/seanturner/netconf-over-tls13 <https://github.com/seanturner/netconf-over-tls13>
> 
> Wondering if the WG would be interested in adopting this I-D?
> 
> spt
> 
>> Begin forwarded message:
>> 
>> From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>> Subject: New Version Notification for draft-turner-netconf-over-tls13-00.txt
>> Date: June 16, 2022 at 21:07:39 EDT
>> To: "Russ Housley" <housley@vigilsec.com <mailto:housley@vigilsec.com>>, "Sean Turner" <sean@sn3rd.com <mailto:sean@sn3rd.com>>
>> 
>> 
>> A new version of I-D, draft-turner-netconf-over-tls13-00.txt
>> has been successfully submitted by Sean Turner and posted to the
>> IETF repository.
>> 
>> Name:		draft-turner-netconf-over-tls13
>> Revision:	00
>> Title:		NETCONF over TLS 1.3
>> Document date:	2022-06-17
>> Group:		Individual Submission
>> Pages:		6
>> URL:            https://www.ietf.org/archive/id/draft-turner-netconf-over-tls13-00.txt <https://www.ietf.org/archive/id/draft-turner-netconf-over-tls13-00.txt>
>> Status:         https://datatracker.ietf.org/doc/draft-turner-netconf-over-tls13/ <https://datatracker.ietf.org/doc/draft-turner-netconf-over-tls13/>
>> Html:           https://www.ietf.org/archive/id/draft-turner-netconf-over-tls13-00.html <https://www.ietf.org/archive/id/draft-turner-netconf-over-tls13-00.html>
>> Htmlized:       https://datatracker.ietf.org/doc/html/draft-turner-netconf-over-tls13 <https://datatracker.ietf.org/doc/html/draft-turner-netconf-over-tls13>
>> 
>> 
>> Abstract:
>>   RFC 7589 defines how to protect NETCONF messages with TLS 1.2.  This
>>   document describes how to protect NETCONF messages with TLS 1.3.
>> 
>> Discussion Venues
>> 
>>   This note is to be removed before publishing as an RFC.
>> 
>>   Discussion of this document takes place on the Network Configuration
>>   Working Group mailing list (netconf@ietf.org <mailto:netconf@ietf.org>), which is archived at
>>   https://mailarchive.ietf.org/arch/browse/netconf/ <https://mailarchive.ietf.org/arch/browse/netconf/>.
>> 
>>   Source for this draft and an issue tracker can be found at
>>   https://github.com/seanturner/netconf-over-tls13 <https://github.com/seanturner/netconf-over-tls13>.
>> 
>> 
>> 
>> 
>> The IETF Secretariat
>> 
>> 
> 
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf


Mahesh Jethanandani
mjethanandani@gmail.com

v2.23.0 | Report a Bug | By Email