Re: [sfc] RFC 9452 on Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data

Joel Halpern <jmh@joelhalpern.com> Thu, 24 August 2023 03:16 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D0D9EC15153F; Wed, 23 Aug 2023 20:16:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.898
X-Spam-Level:
X-Spam-Status: No, score=-2.898 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, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (1024-bit key) header.d=joelhalpern.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 fQNJd8mnn_xZ; Wed, 23 Aug 2023 20:16:00 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 78A1FC1516E2; Wed, 23 Aug 2023 20:16:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4RWSsD0p0qz6Gsxn; Wed, 23 Aug 2023 20:16:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1692846960; bh=2QW7XinYMBUdktvjYamzenuOuygrx1P4rnyNCLePggI=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=A3xe6sdPiAdtj4H821Wlk1OYA3jhHW6FEsemptfpSfINIvYuKHyD3EdtqCGA4w21Z hmUPpKPJ07IfI4K+djNtTeOF++a+jbLUfGYcXYGDMrXnGU6okYUPcexTQ1zdg5yqHU vDad6BkLnNQ9BgxvRX3wD3PAWjjzHuUhuX3HJAE8=
X-Quarantine-ID: <ERAaQgurWyOg>
X-Virus-Scanned: Debian amavisd-new at a2.tigertech.net
Received: from [192.168.20.19] (unknown [50.233.136.230]) (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 maila2.tigertech.net (Postfix) with ESMTPSA id 4RWSsB3yKpz6G9K4; Wed, 23 Aug 2023 20:15:58 -0700 (PDT)
Message-ID: <46546351-b0f9-ea35-7bcb-3c068a16e83c@joelhalpern.com>
Date: Wed, 23 Aug 2023 23:15:56 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.14.0
Content-Language: en-US
To: rfc-editor@rfc-editor.org, ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Cc: drafts-update-ref@iana.org, sfc@ietf.org
References: <20230824020841.A7E26AFB45@rfcpa.amsl.com>
From: Joel Halpern <jmh@joelhalpern.com>
In-Reply-To: <20230824020841.A7E26AFB45@rfcpa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/_ga_HBj6abJuUbkh6G6vk2uKwTY>
Subject: Re: [sfc] RFC 9452 on Network Service Header (NSH) Encapsulation for In Situ OAM (IOAM) Data
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Aug 2023 03:16:05 -0000

Congratulations to the editors and working group.  Another RFC as we 
wind down the SFC Working Group.

Thank you,

Joel

On 8/23/2023 10:08 PM, rfc-editor@rfc-editor.org wrote:
> A new Request for Comments is now available in online RFC libraries.
>
>          
>          RFC 9452
>
>          Title:      Network Service Header (NSH) Encapsulation
>                      for In Situ OAM (IOAM) Data
>          Author:     F. Brockners, Ed.,
>                      S. Bhandari, Ed.
>          Status:     Standards Track
>          Stream:     IETF
>          Date:       August 2023
>          Mailbox:    fbrockne@cisco.com,
>                      shwetha.bhandari@thoughtspot.com
>          Pages:      9
>          Updates/Obsoletes/SeeAlso:   None
>
>          I-D Tag:    draft-ietf-sfc-ioam-nsh-13.txt
>
>          URL:        https://www.rfc-editor.org/info/rfc9452
>
>          DOI:        10.17487/RFC9452
>
> In situ Operations, Administration, and Maintenance (IOAM) is used
> for recording and collecting operational and telemetry information
> while the packet traverses a path between two points in the network.
> This document outlines how IOAM-Data-Fields are encapsulated with the
> Network Service Header (NSH).
>
> This document is a product of the Service Function Chaining Working Group of the IETF.
>
> This is now a Proposed Standard.
>
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
> standardization state and status of this protocol.  Distribution of this
> memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>    https://www.ietf.org/mailman/listinfo/ietf-announce
>    https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see 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