Re: [netconf] Adoption-suitability for draft-kwatsen-netconf-sztp-csr

Mahesh Jethanandani <mjethanandani@gmail.com> Mon, 10 August 2020 21:58 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 F15FE3A0A68 for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 14:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, 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 en6CXrp4WN4Y for <netconf@ietfa.amsl.com>; Mon, 10 Aug 2020 14:58:33 -0700 (PDT)
Received: from mail-pl1-x62e.google.com (mail-pl1-x62e.google.com [IPv6:2607:f8b0:4864:20::62e]) (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 47CE53A0C3D for <netconf@ietf.org>; Mon, 10 Aug 2020 14:58:33 -0700 (PDT)
Received: by mail-pl1-x62e.google.com with SMTP id t11so5806033plr.5 for <netconf@ietf.org>; Mon, 10 Aug 2020 14:58:33 -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=l9vO9aB1FLCeQV4Sh3/4d9mG9VJfEQfdxFaOlrL1lpc=; b=Ry6shVfoetPB30XRxIV+Qn5khk1mqEid4wa2YVPVk5Zf813BxhVRjlgter/uTPjc+c pAXRj7F3uU7E/6Cdq5kJRg1hGbBHFx1pPiu8xDuW0ugdUuhL1iH0MT3VVDimOvasP83U WuiZMiQPv3vw3Va/0pgoZl5z5isK5a1MDvgMa0z/zBcoIBYhTBCorNgdAeBY5hfiL4WF jmZauMo/NJoTmRHrBYU2nzg4oIdkC2K4FWKv70xKdUN0O0sY6M5epajmUaW4wyRvvGdD JH2iULs8SjaNfw5/nJHPYiQS8TrCJJP7WZjfYepUx43nQa/h8O6UPe/VBwEKUZBJ33MS /wfQ==
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=l9vO9aB1FLCeQV4Sh3/4d9mG9VJfEQfdxFaOlrL1lpc=; b=jb62Wx1mbME8HrENtYFCkTpVDebbdPzRgY/+OuFg2vFcHqktyQu2iF1BRgd8LXHMcU jDrGhvTwJOeQTvETwiBaHjjxA49OFB1g5p8hP2CJmBKXTCxU85vfWe1LPgSEfRCKVsg8 G9sBL1KifstXnFaxFuTC1948J5sydp1OZczbcltp1YTILRZiJY4m1Nr+1/7+onhKIAYN iI/V2yDIuoVb1Wl0jyMf46PNY1s9apzh8M3g8QmEMlMq8oibKxttWWagxQE0kG8W78Vd qGFDJU7rKLOgn2YDQdR+AcI/Cu2OX+uXEjcBuiGWG4DTbdXu54Zw9qW3SnTfAxSORlVu 2Jpg==
X-Gm-Message-State: AOAM532erG00I2EycmOSo8z0/lDNxaaLDYhKv2yJGB+uAXaqA+zlzyKB UKmxOpOZfbe5YnDZFU8hb1k=
X-Google-Smtp-Source: ABdhPJxi8IWiTOlN7XkfmnP1Irv9jN6BJakApK9sYVVESsB7c5hAoyzCIee4kf7cLM3TuLohq9xnXA==
X-Received: by 2002:a17:902:a9c8:: with SMTP id b8mr26328115plr.2.1597096712724; Mon, 10 Aug 2020 14:58:32 -0700 (PDT)
Received: from ?IPv6:2601:647:5600:5020:89a1:175d:59c8:8fe? ([2601:647:5600:5020:89a1:175d:59c8:8fe]) by smtp.gmail.com with ESMTPSA id y12sm14028578pgi.75.2020.08.10.14.58.31 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Aug 2020 14:58:31 -0700 (PDT)
From: Mahesh Jethanandani <mjethanandani@gmail.com>
Message-Id: <0D9FA9D4-043C-4316-A525-261569E81197@gmail.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_1EDDFBFA-D3D2-4B8D-9B0A-DC86F342CBCD"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.6\))
Date: Mon, 10 Aug 2020 14:58:31 -0700
In-Reply-To: <CABCOCHTZ3Bhw-YY-NdRjXYtcjhVjtKbZ3xe1n4kEwAPJ=zFWig@mail.gmail.com>
Cc: "netconf@ietf.org" <netconf@ietf.org>
To: Andy Bierman <andy@yumaworks.com>
References: <01000173c0b4ee99-d5627c91-eac2-4ea9-ba1b-b86e37c5293a-000000@us-east-1.amazonses.com> <CABCOCHTZ3Bhw-YY-NdRjXYtcjhVjtKbZ3xe1n4kEwAPJ=zFWig@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.9.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/fszxNRht2bnstTQpZJQEXZwimC4>
Subject: Re: [netconf] Adoption-suitability for draft-kwatsen-netconf-sztp-csr
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: Mon, 10 Aug 2020 21:58:35 -0000

Hi Andy,

> On Aug 10, 2020, at 12:40 PM, Andy Bierman <andy@yumaworks.com> wrote:
> 
> Hi,
> 
> I am trying to understand the problem addressed in this draft.
> It appears to be a well-constrained enhancement to SZTP to provide
> more data in the get-bootstrapping-info RPC.
> 
> It is not clear that NETCONF WG is the right place for this draft, but
> given the co-authors involved I think it will get sufficient security area review.

The charter for NETCONF WG includes ZTP, and this comes as a natural extension of that item. Every WG and draft has to address security considerations, which this draft tries to do, and the co-authors, who are security experts, have agreed to review the draft. Therefore, I feel that NETCONF WG would be a natural place for this draft to progress.

> 
> I am willing to review the draft (wrt/ RESTCONF related issues).
> I may implement it in the future, but no plans now.
> 
> 
> Andy
> 
> 
> 
> 
> 
> On Wed, Aug 5, 2020 at 3:19 PM Kent Watsen <kent+ietf@watsen.net <mailto:kent%2Bietf@watsen.net>> wrote:
> 
> NETCONF WG,
> 
> Per the previous email sent moments ago, the chairs would like to solicit input on the following draft:
> 
>    Title: Conveying a CSR in an SZTP Bootstrapping Request
>    Link: https://tools..ietf.org/html/ <https://tools.ietf.org/html/>draft-kwatsen-netconf-sztp-csr
>    Abstract:
> 
>       This draft extends the "get-bootstrapping-data" RPC defined in
>       RFC 8572 to include an optional certificate signing request (CSR),
>       enabling a bootstrapping device to additionally obtain an identity
>       certificate (e.g., an LDevID, from IEEE 802.1AR) as part of the
>       "onboarding information" response provided in the RPC-reply.
> 
> 
> In particular, please discuss adoption-suitability as it regards to the following questions:
> 
>     1) is the problem important for the NETCONF WG to solve?
>     2) is the draft a suitable basis for the work?
> 
> 
> PS: this message is itself not an adoption poll, but rather an attempt to gauge interest/support for a potential future adoption poll.
> 
> NETCONF Chairs
> _______________________________________________
> netconf mailing list
> netconf@ietf.org <mailto:netconf@ietf.org>
> https://www.ietf.org/mailman/listinfo/netconf <https://www.ietf.org/mailman/listinfo/netconf>
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf

Mahesh Jethanandani
mjethanandani@gmail.com