IETF Logo Mail Archive

Re: [Int-area] [Iotops] YANG was Last Call: Moving TPC.INT and NSAP.INT infrastructure domains to historic

Michael Sweet <msweet@msweet.org> Fri, 08 April 2022 13:23 UTC

Return-Path: <msweet@msweet.org>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6EB83A1A0C; Fri, 8 Apr 2022 06:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.11
X-Spam-Level:
X-Spam-Status: No, score=-2.11 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, 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 (1024-bit key) header.d=msweet.org
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 9pwgQP9jtE9O; Fri, 8 Apr 2022 06:23:18 -0700 (PDT)
Received: from mail.msweet.org (mail.msweet.org [173.255.209.91]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA233A1A08; Fri, 8 Apr 2022 06:23:18 -0700 (PDT)
Received: from smtpclient.apple (cbl-66-186-76-47.vianet.ca [66.186.76.47]) by mail.msweet.org (Postfix) with ESMTPSA id 73F3B81DA5; Fri, 8 Apr 2022 13:23:17 +0000 (UTC)
DKIM-Filter: OpenDKIM Filter v2.11.0 mail.msweet.org 73F3B81DA5
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=msweet.org; s=default; t=1649424197; bh=orEbQDMpwOSrtReb1n5SkgXAoMYBbuGN7WjJOOSDnmc=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=MeY2tSF7VYVhHC02qs/UaZPE1C3qEh4dWN7neyca4ZYIyxG+f0Ox5bSHMqCwIEKtx ZO61+N6DpXw46FuS2FgFroH1In24mRuDwzuSqTTr3osmoBqsPz4CS7Bomqe1EFt4d9 o4PVhTT5ONWN9Z9fD6vJ8H1KUsj0UGxysoeYNe28=
Content-Type: multipart/signed; boundary="Apple-Mail=_69F0B873-B93C-464D-B158-C2339C413B82"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.100.1\))
From: Michael Sweet <msweet@msweet.org>
In-Reply-To: <AM7PR07MB624855262900101EC0ECD176A0E99@AM7PR07MB6248.eurprd07.prod.outlook.com>
Date: Fri, 08 Apr 2022 09:23:15 -0400
Cc: Michael Sweet <msweet=40msweet.org@dmarc.ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "iotops@ietf.org" <iotops@ietf.org>
Message-Id: <87B698E6-CE3A-4334-B77B-EA45BBC06E45@msweet.org>
References: <164867508759.15594.2523981628049164116@ietfa.amsl.com> <Yk6w/Dga2GhGo/im@faui48e.informatik.uni-erlangen.de> <18339826-74F7-411E-BCE9-67C665A1A230@msweet.org> <AM7PR07MB624855262900101EC0ECD176A0E99@AM7PR07MB6248.eurprd07.prod.outlook.com>
To: tom petch <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.3696.100.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/kUdmPx0mEpJBFmwcy12owoxUmbc>
X-Mailman-Approved-At: Fri, 08 Apr 2022 06:27:36 -0700
Subject: Re: [Int-area] [Iotops] YANG was Last Call: Moving TPC.INT and NSAP.INT infrastructure domains to historic
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area WG Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Apr 2022 13:23:24 -0000

Tom,

> On Apr 8, 2022, at 5:02 AM, tom petch <ietfc@btconnect.com> wrote:
> 
> From: Int-area <int-area-bounces@ietf.org> on behalf of Michael Sweet <msweet=40msweet.org@dmarc.ietf.org>
> Sent: 07 April 2022 15:11
> Re: [Int-area] [Iotops] Last Call: Moving TPC.INT and NSAP.INT infrastructure domains to historic
> 
> Michael
> 
> I am well familiar with the work of IPP in the IETF.  You mention MIBs which I know of.  Is there anything similar in YANG?

Not that I am aware of, but doing a YANG model for IPP to allow configuration via NETCONF is certainly feasible - the IPP model and semantics are well insulated from the transport and implementation/encoding details.

In fact, the Printer Working Group spent quite a few years developing an XML schema for the IPP model and semantics (RFC 8011) and various printing MIBs, what is known collectively as the PWG Semantic Model.  However, its usage has been limited to bridging mechanisms with other vendor/standard printing models since IPP is generally able to work everywhere...

________________________
Michael Sweet

v2.23.0 | Report a Bug | By Email