Re: [nmrg] RFC 9316 on Intent Classification

Jeff Tantsura <jefftant.ietf@gmail.com> Sun, 23 October 2022 01:51 UTC

Return-Path: <jefftant.ietf@gmail.com>
X-Original-To: nmrg@ietfa.amsl.com
Delivered-To: nmrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 89276C14CF15; Sat, 22 Oct 2022 18:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.213
X-Spam-Level:
X-Spam-Status: No, score=-1.213 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, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MIME_QP_LONG_LINE=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 i5sZIcUJOc40; Sat, 22 Oct 2022 18:50:57 -0700 (PDT)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (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 662ADC14F692; Sat, 22 Oct 2022 18:50:57 -0700 (PDT)
Received: by mail-pf1-x430.google.com with SMTP id y1so6137196pfr.3; Sat, 22 Oct 2022 18:50:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=to:references:message-id:date:cc:in-reply-to:from:subject :mime-version:content-transfer-encoding:from:to:cc:subject:date :message-id:reply-to; bh=COo6LIWXVXMpmY5s84MCCePukMZd8VssMy4nxt+bq8g=; b=a0ae7aTGj7yWI48IsLQ6abV61hOpd3Ex5MF2PAfHZW3OvstGxAXaQxDa6xc8wSLp/4 g/k9NrQguQqc/S6tx9YKiDyJ200JVZOSx/wmo6/CEx6dnj3/vcETusZ1N6QnltEkTmkV DrQg4c1RCJo6Oba8VAylyyPmSt6OiSXL9jls4Njb7oVoIXpAMjsma/5BVbWDeiP77PyN 6PwcGs8jrwEIYaGwQB15hoBaTCSVTo3ioBFerPSmdVRmFM/PzJfksnmQ1Qc+QiP/ulzE eTS9bPL1FAVAAvdMSWMgsFdaxP525pH4AtCLofOliQ6HqOIZ5fJAH92GIZjRRb3XUv+g loeQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:references:message-id:date:cc:in-reply-to:from:subject :mime-version:content-transfer-encoding:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=COo6LIWXVXMpmY5s84MCCePukMZd8VssMy4nxt+bq8g=; b=iZfISfVOPgKcNGIJqBlf5l+Wu5rnWNUSaGodF5Uzv7fGUa+HQcKujcVKuNwumX5iIj zjscSDPltz1JfLw7Na0pOfAwH+Ufw8o8f2dqTCsyA03YJYLaZuFIgWOZBN9bVerzGogZ wtRQy+XPJ5oKrsVJfKS99zymN0uiYCdxRzEZHpVH8e4qKqfOXM7OoUVFuSZswSHG1SYa qc9pICWXE9r9VvSg30SgMCSH4XdEqbSBA0huPrxH4o5wkADu/4Gkn+nhW5fOikEYkcAR HbExFdRFIwssTkV6WrJ0MQGUliV3KC4NpKkh9YlAjk+Gyqj/GJef1wIGdYLut/nyNWIH F+iw==
X-Gm-Message-State: ACrzQf1v/kXG/9e6Ny6qv4VBppAmp9tI1tdUAeXJEhf46+RkOURJZ9RY 1RjZKIyU8BHxPNe1gytav74=
X-Google-Smtp-Source: AMsMyM5pn/8Wiyl37wcEmZfXkRlP8kNN8oaUiOekE5vpmAEGXruPFwksOGVnznBBlBJQD2AR8N5hPA==
X-Received: by 2002:a05:6a00:18a2:b0:56b:6823:322c with SMTP id x34-20020a056a0018a200b0056b6823322cmr8191655pfh.18.1666489856476; Sat, 22 Oct 2022 18:50:56 -0700 (PDT)
Received: from smtpclient.apple (c-73-63-232-212.hsd1.ca.comcast.net. [73.63.232.212]) by smtp.gmail.com with ESMTPSA id w61-20020a17090a6bc300b0021282014066sm1959923pjj.9.2022.10.22.18.50.55 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 22 Oct 2022 18:50:55 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-C54B59E4-AC16-419D-B091-FE3682309F83"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (1.0)
From: Jeff Tantsura <jefftant.ietf@gmail.com>
In-Reply-To: <CAFvDQ9raymz8-RijGtYV+YgpTZLPFcJeSoiUkrMuQC9Oqv2mww@mail.gmail.com>
Cc: rfc-editor@rfc-editor.org, IETF-Announce <ietf-announce@ietf.org>, rfc-dist@rfc-editor.org, irtf-announce@irtf.org, drafts-update-ref@iana.org, nmrg@irtf.org
Date: Sat, 22 Oct 2022 18:50:44 -0700
Message-Id: <1420DF5D-1B59-4D80-A233-8FC44F8DC280@gmail.com>
References: <CAFvDQ9raymz8-RijGtYV+YgpTZLPFcJeSoiUkrMuQC9Oqv2mww@mail.gmail.com>
To: Hesham ElBakoury <helbakoury@gmail.com>
X-Mailer: iPhone Mail (20A392)
Archived-At: <https://mailarchive.ietf.org/arch/msg/nmrg/7IMkQsV3dmEIbSEHrdMlvpRI4vY>
Subject: Re: [nmrg] RFC 9316 on Intent Classification
X-BeenThere: nmrg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Management Research Group discussion list <nmrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmrg>, <mailto:nmrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmrg/>
List-Post: <mailto:nmrg@irtf.org>
List-Help: <mailto:nmrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmrg>, <mailto:nmrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 23 Oct 2022 01:51:01 -0000

No, there’s nothing to be standardized.
Category written on the front page BTW ;-)

Cheers,
Jeff

On Oct 22, 2022, at 15:07, Hesham ElBakoury <helbakoury@gmail.com> wrote:


Are there standards track RFCs related to IBN?

Thanks
Hesham

On Fri, Oct 21, 2022, 11:05 AM <rfc-editor@rfc-editor.org> wrote:
A new Request for Comments is now available in online RFC libraries.


        RFC 9316

        Title:      Intent Classification
        Author:     C. Li,
                    O. Havel,
                    A. Olariu,
                    P. Martinez-Julia,
                    J. Nobre,
                    D. Lopez
        Status:     Informational
        Stream:     IRTF
        Date:       October 2022
        Mailbox:    lichen6@chinatelecom.cn,
                    olga.havel@huawei.com,
                    adriana.olariu@huawei.com,
                    pedro@nict.go.jp,
                    jcnobre@inf.ufrgs.br,
                    diego.r.lopez@telefonica.com
        Pages:      35
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-irtf-nmrg-ibn-intent-classification-08.txt

        URL:        https://www.rfc-editor.org/info/rfc9316" rel="noreferrer noreferrer nofollow" target="_blank">https://www.rfc-editor.org/info/rfc9316

        DOI:        10.17487/RFC9316

Intent is an abstract, high-level policy used to operate a network.
An intent-based management system includes an interface for users to
input requests and an engine to translate the intents into the
network configuration and manage their life cycle.

This document mostly discusses the concept of network intents, but
other types of intents are also considered. Specifically, this
document highlights stakeholder perspectives of intent, methods to
classify and encode intent, and the associated intent taxonomy; it
also defines relevant intent terms where necessary, provides a
foundation for intent-related research, and facilitates solution
development.

This document is a product of the IRTF Network Management Research
Group (NMRG).

This document is a product of the Network Management Research Group of the IRTF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist" rel="noreferrer noreferrer nofollow" target="_blank">https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
  https://www.irtf.org/mailman/listinfo/irtf-announce" rel="noreferrer noreferrer nofollow" target="_blank">https://www.irtf.org/mailman/listinfo/irtf-announce

For searching the RFC series, see https://www.rfc-editor.org/search" rel="noreferrer noreferrer nofollow" target="_blank">https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk" rel="noreferrer noreferrer nofollow" target="_blank">https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce" rel="noreferrer noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/ietf-announce
_______________________________________________
nmrg mailing list
nmrg@irtf.org
https://www.irtf.org/mailman/listinfo/nmrg