IETF Logo Mail Archive

Re: [netconf] Call for Authors

Douglas Hubler <dhubler@gmail.com> Mon, 22 April 2024 22:21 UTC

Return-Path: <dhubler@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 5A3F0C1CAF55 for <netconf@ietfa.amsl.com>; Mon, 22 Apr 2024 15:21:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 L51AP1WL_Y6a for <netconf@ietfa.amsl.com>; Mon, 22 Apr 2024 15:21:00 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (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 84092C18DBAB for <netconf@ietf.org>; Mon, 22 Apr 2024 15:21:00 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id 38308e7fff4ca-2dae975d0dcso60266081fa.1 for <netconf@ietf.org>; Mon, 22 Apr 2024 15:21:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713824458; x=1714429258; darn=ietf.org; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=GRrNCPZ/bmI2A6oPNudzPdCZ+eL2CYf69Eh/inyyrbI=; b=SFNSAtLY+qfuQ+ENQyqUJmPF3WAMwdcM7h/onMczzTfOBJMKxt88MX/CUqCP69dV/L gTEHPMdHXTIhaHGSwrjI3Lbj7JkU6n/OxdWf5PieNBi0MeGc0yIGv0TSHL8FWWT68Ktj w2dusohFMLpi7OCFK3Kt3p7l8MrQZVcJfTIRyns2fTKR9qYHGWOxz3bv9nulpZVF96HU lHJMZDhQylVdmY78xxrxN3JG1gdhEwsYOwesbJpG0hG55c52dzwIX8Ae28BrVuhkvuDm 7arVH3ig86m60NmwcRdk4E7KfUig3352MH61Pdi3pHR84gmJ+aT1Cv84mUv3F/43YTK/ NiOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713824458; x=1714429258; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=GRrNCPZ/bmI2A6oPNudzPdCZ+eL2CYf69Eh/inyyrbI=; b=MvnAsxnzuggTUh7H3yNnmNYwxWzJVfxXiJvUA8PcFM485seBa18blk70NCBt0lWoOu d2xbyH/RCu6pMQDchGXAjwdLkImm+rxSMVvNJ98Wak1ewpciiKOKpGfAbjdbBdQGZnp7 K9uCp/gM1FgR9RA3fh7KNtYyy/4ruW9wD0B2QcqpKidC4plAa03KzQEZEvZEjtMVMTH3 nbuqf7x5GpEicqNX5qckrCQM218vTwCGt1RCd6FhHurfyJJkzvomHm/FTzrI/WzVY+Jk /Sw4LAavC6S5gFb2Rb25XGVW+cL0h7wXhF5fhbN2fdX81GNtvBt2JnFKJzoKMthD4j9V kg0w==
X-Gm-Message-State: AOJu0YyLfwnwytMroYb4sTleif7iGI8f68LgNgbD9bZ5QAvdNEmnOcL4 8j4RVv0h2yUWx0x3YFeevspp9eMZV1IbbWsiNzpu/9mtXNZdZ/5HJfG9cZkD4iA03WbiBKJuw5Y BjHqXOhAyq6NsWimUCblB1/hFqL/Aa39I
X-Google-Smtp-Source: AGHT+IF8vc6O4pl6exVFGjT7HsuK+vLGIUlo/FftO0a3p7TsZqwGgMu6+WJ89FmVLpfUPRPicubmS0zifPRKEXn0cis=
X-Received: by 2002:a05:651c:509:b0:2db:b1c6:aaf0 with SMTP id o9-20020a05651c050900b002dbb1c6aaf0mr285017ljp.1.1713824457929; Mon, 22 Apr 2024 15:20:57 -0700 (PDT)
MIME-Version: 1.0
References: <0100018f07d2cb22-852f429d-19bd-4a08-9860-cc2132b14357-000000@email.amazonses.com>
In-Reply-To: <0100018f07d2cb22-852f429d-19bd-4a08-9860-cc2132b14357-000000@email.amazonses.com>
Reply-To: douglas@hubler.us
From: Douglas Hubler <dhubler@gmail.com>
Date: Mon, 22 Apr 2024 18:20:46 -0400
Message-ID: <CALAkb6d-tKYHx=w-r8z+_HEuRV2NVLXVzRzb-uaMAtKLAk9b3g@mail.gmail.com>
To: Kent Watsen <kent+ietf@watsen.net>
Cc: "netconf@ietf.org" <netconf@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000005bd830616b6daf4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/netconf/RDVWken9hYZ67JKZ2c2EPhRnxKY>
Subject: Re: [netconf] Call for Authors
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, 22 Apr 2024 22:21:04 -0000

On Mon, Apr 22, 2024 at 6:00 PM Kent Watsen <kent+ietf@watsen.net> wrote:
> Would anyone like to help me write an INFORMATIONAL document that
evangelizes the use of RESTCONF for generic web applications?   Attached is
what I have so far.

As a huge fan of RESTCONF and also do a lot of swagger I would have some
input  for section 5. RESTCONF, a Superior REST-ful API

Adjustable data granularity
Traditional REST APIs struggle with what level of information to return for
each GET request and this is called granularity. Return too little data and
scripts will need to make constant trips for more. Return too much data and
the majority of it will likely be unused. Both situations cause delays and
additional resource consumption.

RESTCONF APIs do not have this issue. Clients can precisely control the
data they want from depth, to list pagination. From selecting fields to
excluding fields.



On Mon, Apr 22, 2024 at 6:00 PM Kent Watsen <kent+ietf@watsen.net> wrote:

> Would anyone like to help me write an INFORMATIONAL document that
> evangelizes the use of RESTCONF for generic web applications?   Attached is
> what I have so far.
>
> Cheers,
> Kent
>
>
> _______________________________________________
> netconf mailing list
> netconf@ietf.org
> https://www.ietf.org/mailman/listinfo/netconf
>

v2.27.6 | Report a Bug | By Email | System Status