RFC 9419 on Considerations on Application - Network Collaboration Using Path Signals

rfc-editor@rfc-editor.org Thu, 06 July 2023 23:09 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1FAC151091 for <ietf-announce@ietfa.amsl.com>; Thu, 6 Jul 2023 16:09:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.315
X-Spam-Level:
X-Spam-Status: No, score=-2.315 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.84, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
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 2pBvxIY7IlYM for <ietf-announce@ietfa.amsl.com>; Thu, 6 Jul 2023 16:09:43 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (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 339F3C15108B for <ietf-announce@ietf.org>; Thu, 6 Jul 2023 16:09:43 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id F14D8B3622; Thu, 6 Jul 2023 16:09:42 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9419 on Considerations on Application - Network Collaboration Using Path Signals
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230706230942.F14D8B3622@rfcpa.amsl.com>
Date: Thu, 06 Jul 2023 16:09:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/3yHpKW8zdcpaYwAbhkK3fAy0MH8>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jul 2023 23:09:47 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9419

        Title:      Considerations on Application - Network 
                    Collaboration Using Path Signals 
        Author:     J. Arkko,
                    T. Hardie,
                    T. Pauly,
                    M. Kühlewind
        Status:     Informational
        Stream:     IAB
        Date:       July 2026
        Mailbox:    jari.arkko@ericsson.com,
                    ted.ietf@gmail.com,
                    tpauly@apple.com,
                    mirja.kuehlewind@ericsson.com
        Pages:      15
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-iab-path-signals-collaboration-03.txt

        URL:        https://www.rfc-editor.org/info/rfc9419

        DOI:        10.17487/RFC9419

This document discusses principles for designing mechanisms that use
or provide path signals and calls for standards action in specific
valuable cases.  RFC 8558 describes path signals as messages to or
from on-path elements and points out that visible information will be
used whether or not it is intended as a signal. The principles in
this document are intended as guidance for the design of explicit
path signals, which are encouraged to be authenticated and include a
minimal set of parties to minimize information sharing. These
principles can be achieved through mechanisms like encryption of
information and establishing trust relationships between entities on
a path.

This document is a product of the Internet Architecture Board.


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 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