RFC 8770 on Host Router Support for OSPFv2

rfc-editor@rfc-editor.org Thu, 09 April 2020 17:20 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 8EDC43A0AB6; Thu, 9 Apr 2020 10:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 euvP3Upzix1v; Thu, 9 Apr 2020 10:20:33 -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 BF9033A0CAA; Thu, 9 Apr 2020 10:20:30 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id A9E82F406F6; Thu, 9 Apr 2020 10:20:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: =?UTF-8?B?UkZDIDg3NzAgb24gSG9zdCBSb3V0ZXIgU3VwcG9ydCBmb3IgT1NQRnYy?=
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, lsr@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20200409172017.A9E82F406F6@rfc-editor.org>
Date: Thu, 9 Apr 2020 10:20:17 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/sBRdeYTWObKuG3LsuFVnPOjt_LA>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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, 09 Apr 2020 17:20:36 -0000

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

        
        RFC 8770

        Title:      Host Router Support for OSPFv2 
        Author:     K. Patel, 
                    P. Pillay-Esnault,
                    M. Bhardwaj,
                    S. Bayraktar
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2020
        Mailbox:    keyur@arrcus.com, 
                    padma.ietf@gmail.com, 
                    manbhard@cisco.com,
                    serpil@cisco.com
        Pages:      8
        Updates:    RFC 6987

        I-D Tag:    draft-ietf-ospf-ospfv2-hbit-12.txt

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

        DOI:        10.17487/RFC8770

The Open Shortest Path First Version 2 (OSPFv2) protocol does not
have a mechanism for a node to repel transit traffic if it is on the
shortest path.  This document defines a bit called the Host-bit
(H-bit). This bit enables a router to advertise that it is a
non-transit router.  This document also describes the changes needed
to support the H-bit in the domain.  In addition, this document
updates RFC 6987 to advertise Type 2 External and Not-So-Stubby Area
(NSSA) Link State Advertisements (LSAs) (RFC 3101) with a high cost
in order to repel traffic effectively.

This document is a product of the Link State Routing 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