[OSPF] RFC 7684 on OSPFv2 Prefix/Link Attribute Advertisement

rfc-editor@rfc-editor.org Wed, 25 November 2015 00:38 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 6C1971AC3E5; Tue, 24 Nov 2015 16:38:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.487
X-Spam-Status: No, score=-107.487 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Z7lYEw_lAQUp; Tue, 24 Nov 2015 16:38:38 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id C03D81AC3E4; Tue, 24 Nov 2015 16:38:38 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A374C180006; Tue, 24 Nov 2015 16:37:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20151125003700.A374C180006@rfc-editor.org>
Date: Tue, 24 Nov 2015 16:37:00 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/u_zTmdix-rvZRitYcZvZqoiJp4s>
Cc: drafts-update-ref@iana.org, ospf@ietf.org, rfc-editor@rfc-editor.org
Subject: [OSPF] RFC 7684 on OSPFv2 Prefix/Link Attribute Advertisement
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Nov 2015 00:38:40 -0000

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

        RFC 7684

        Title:      OSPFv2 Prefix/Link Attribute Advertisement 
        Author:     P. Psenak, H. Gredler,
                    R. Shakir, W. Henderickx,
                    J. Tantsura, A. Lindem
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2015
        Mailbox:    ppsenak@cisco.com, 
        Pages:      15
        Characters: 33236
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ospf-prefix-link-attr-13.txt

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

        DOI:        http://dx.doi.org/10.17487/RFC7684

OSPFv2 requires functional extension beyond what can readily be done
with the fixed-format Link State Advertisements (LSAs) as described
in RFC 2328.  This document defines OSPFv2 Opaque LSAs based on
Type-Length-Value (TLV) tuples that can be used to associate additional
attributes with prefixes or links.  Depending on the application,
these prefixes and links may or may not be advertised in the fixed-format
LSAs.  The OSPFv2 Opaque LSAs are optional and fully backward

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

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

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