[OSPF] RFC 7503 on OSPFv3 Autoconfiguration

rfc-editor@rfc-editor.org Mon, 06 April 2015 20:46 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50911A923A; Mon, 6 Apr 2015 13:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Level:
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 GiPqcA1-ysPN; Mon, 6 Apr 2015 13:46:07 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id C8CE01A923C; Mon, 6 Apr 2015 13:45:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 06336180470; Mon, 6 Apr 2015 13:45:27 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150406204527.06336180470@rfc-editor.org>
Date: Mon, 06 Apr 2015 13:45:27 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ospf/V4NXbbED_582qSZEKRrZEKMznkY>
Cc: drafts-update-ref@iana.org, ospf@ietf.org, rfc-editor@rfc-editor.org
Subject: [OSPF] RFC 7503 on OSPFv3 Autoconfiguration
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: <http://www.ietf.org/mail-archive/web/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: Mon, 06 Apr 2015 20:46:08 -0000

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

        
        RFC 7503

        Title:      OSPFv3 Autoconfiguration 
        Author:     A. Lindem, J. Arkko
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2015
        Mailbox:    acee@cisco.com, 
                    jari.arkko@piuha.net
        Pages:      15
        Characters: 33521
        Updates:    RFC 5340

        I-D Tag:    draft-ietf-ospf-ospfv3-autoconfig-15.txt

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

OSPFv3 is a candidate for deployments in environments where
autoconfiguration is a requirement.  One such environment is the IPv6
home network where users expect to simply plug in a router and have
it automatically use OSPFv3 for intra-domain routing.  This document
describes the necessary mechanisms for OSPFv3 to be self-configuring.
This document updates RFC 5340 by relaxing the HelloInterval/
RouterDeadInterval checking during OSPFv3 adjacency formation and
adding hysteresis to the update of self-originated Link State
Advertisements (LSAs).

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