RFC 8362 on OSPFv3 Link State Advertisement (LSA) Extensibility
rfc-editor@rfc-editor.org Wed, 04 April 2018 04:08 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 A43FC126CD8 for <ietf-announce@ietfa.amsl.com>; Tue, 3 Apr 2018 21:08:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham autolearn_force=no
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 1hNEBytOvR9N for <ietf-announce@ietfa.amsl.com>; Tue, 3 Apr 2018 21:08:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9366124207 for <ietf-announce@ietf.org>; Tue, 3 Apr 2018 21:08:52 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E33F2B8271A; Tue, 3 Apr 2018 21:08:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8362 on OSPFv3 Link State Advertisement (LSA) Extensibility
X-PHP-Originating-Script: 1005:ams_util_lib.php
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: <20180404040824.E33F2B8271A@rfc-editor.org>
Date: Tue, 03 Apr 2018 21:08:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dd-sxdg2allXlH49j1FASFir-RI>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 04 Apr 2018 04:08:55 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8362 Title: OSPFv3 Link State Advertisement (LSA) Extensibility Author: A. Lindem, A. Roy, D. Goethals, V. Reddy Vallem, F. Baker Status: Standards Track Stream: IETF Date: April 2018 Mailbox: acee@cisco.com, akr@cisco.com, dirk.goethals@nokia.com, vallem.veerendra@gmail.com, FredBaker.IETF@gmail.com Pages: 33 Characters: 70850 Updates: RFC 5340, RFC 5838 I-D Tag: draft-ietf-ospf-ospfv3-lsa-extend-23.txt URL: https://www.rfc-editor.org/info/rfc8362 DOI: 10.17487/RFC8362 OSPFv3 requires functional extension beyond what can readily be done with the fixed-format Link State Advertisement (LSA) as described in RFC 5340. Without LSA extension, attributes associated with OSPFv3 links and advertised IPv6 prefixes must be advertised in separate LSAs and correlated to the fixed-format LSAs. This document extends the LSA format by encoding the existing OSPFv3 LSA information in Type-Length-Value (TLV) tuples and allowing advertisement of additional information with additional TLVs. Backward-compatibility mechanisms are also described. This document updates RFC 5340, "OSPF for IPv6", and RFC 5838, "Support of Address Families in OSPFv3", by providing TLV-based encodings for the base OSPFv3 unicast support and OSPFv3 address family support. This document is a product of the Open Shortest Path First IGP 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