[rfc-dist] RFC 9296 on ifStackTable for the Point-to-Point (P2P) Interface over a LAN Type: Definition and Examples
rfc-editor@rfc-editor.org Tue, 23 August 2022 22:59 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57275C1526FA for <ietf-announce@ietfa.amsl.com>; Tue, 23 Aug 2022 15:59:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.658
X-Spam-Level:
X-Spam-Status: No, score=-6.658 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, 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=unavailable 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 JmoTkWOti1e3 for <ietf-announce@ietfa.amsl.com>; Tue, 23 Aug 2022 15:59:14 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [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 B3CEDC1526F3 for <ietf-announce@ietf.org>; Tue, 23 Aug 2022 15:59:14 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 94FFDC88A6; Tue, 23 Aug 2022 15:59:09 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: [rfc-dist] RFC 9296 on ifStackTable for the Point-to-Point (P2P) Interface over a LAN Type: Definition and Examples
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: <20220823225909.94FFDC88A6@rfcpa.amsl.com>
Date: Tue, 23 Aug 2022 15:59:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/aZ9oVynZhOZjCeGfvlNUfeh0Xaw>
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Aug 2022 22:59:18 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9296
Title: ifStackTable for the Point-to-Point (P2P)
Interface over a LAN Type: Definition
and Examples
Author: D. Liu,
J. Halpern,
C. Zhang
Status: Informational
Stream: Independent
Date: August 2022
Mailbox: harold.liu@ericsson.com,
joel.halpern@ericsson.com,
congjie.zhang@ericsson.com
Pages: 9
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-liu-lsr-p2poverlan-12.txt
URL: https://www.rfc-editor.org/info/rfc9296
DOI: 10.17487/RFC9296
RFC 5309 defines the Point-to-Point (P2P) circuit type, one of the
two circuit types used in the link-state routing protocols, and
highlights that it is important to identify the correct circuit type
when forming adjacencies, flooding link-state database packets, and
monitoring the link state.
This document provides advice about the ifStack for the P2P interface
over a LAN Type to facilitate operational control, maintenance, and
statistics.
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