[OSPF] FW: IPR Call for "H-Support for OSPFv2"

"Acee Lindem (acee)" <acee@cisco.com> Sun, 02 July 2017 18:09 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 35DF012ECB7 for <ospf@ietfa.amsl.com>; Sun, 2 Jul 2017 11:09:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id uS3HB8K0GaHf for <ospf@ietfa.amsl.com>; Sun, 2 Jul 2017 11:09:33 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 617DC127ABE for <ospf@ietf.org>; Sun, 2 Jul 2017 11:09:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=23941; q=dns/txt; s=iport; t=1499018973; x=1500228573; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=wAyQru0sAG7zzvv8sKq3znOmdVtcz1aScNtJrGo3e5Y=; b=CQ7ofF4EGGmUmZ0+/EAYnlRaJm/zTLiZ7z9hk0C1Ou0Rk8oBeTtqdN1t rmiAvFXlgZs8Q+Q8VxAns27m88wIxYYVIHp2sUS2AQYTMp+ckBpX3RWmU SmpAck3uUI2pi5nkV0gZWERbSr7IZgZLvlsKTmvtzrRdVNieU8sHQ6/d3 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.40,298,1496102400"; d="scan'208,217";a="444150121"
Received: from rcdn-core-11.cisco.com ([]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jul 2017 18:09:32 +0000
Received: from XCH-RTP-012.cisco.com (xch-rtp-012.cisco.com []) by rcdn-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id v62I9VsA031804 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <ospf@ietf.org>; Sun, 2 Jul 2017 18:09:32 GMT
Received: from xch-rtp-015.cisco.com ( by XCH-RTP-012.cisco.com ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 2 Jul 2017 14:09:31 -0400
Received: from xch-rtp-015.cisco.com ([]) by XCH-RTP-015.cisco.com ([]) with mapi id 15.00.1210.000; Sun, 2 Jul 2017 14:09:30 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: OSPF WG List <ospf@ietf.org>
Thread-Topic: [OSPF] IPR Call for "H-Support for OSPFv2"
Thread-Index: AQHS731K4Wov4XfIrkul8Ncbp0ekHKI/zFOAgAERYYA=
Date: Sun, 02 Jul 2017 18:09:30 +0000
Message-ID: <D57EAED1.B6F96%acee@cisco.com>
References: <D5782C55.B694F%acee@cisco.com> <E66CD551-D434-4480-B94B-E4E1F9E2EC13@cisco.com>
In-Reply-To: <E66CD551-D434-4480-B94B-E4E1F9E2EC13@cisco.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D57EAED1B6F96aceeciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/jU3UG8lonOZnL8pQmq6eICuitLo>
Subject: [OSPF] FW: IPR Call for "H-Support for OSPFv2"
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 02 Jul 2017 18:09:36 -0000

From: "Serpil Bayraktar (serpil)" <serpil@cisco.com<mailto:serpil@cisco.com>>
Date: Saturday, July 1, 2017 at 11:50 PM
To: Acee Lindem <acee@cisco.com<mailto:acee@cisco.com>>, Padmadevi Pillay Esnault <padma@huawei.com<mailto:padma@huawei.com>>, Keyur Patel <keyur@arrcus.com<mailto:keyur@arrcus.com>>
Subject: Re: [OSPF] IPR Call for "H-Support for OSPFv2"

I am not aware of any IPR.

Apologies for the late response, I am out on PTO.



If you are listed as a document author or contributor, please respond to
this email stating whether or not you are aware of any relevant IPR. The
response needs to be sent to the OSPF mailing list. The document will
not advance to the next stage until a response has been received from
each author and each individual that has contributed to the document.


On 6/14/17, 3:48 PM, "OSPF on behalf of Acee Lindem (acee)"
<ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org> on behalf of acee@cisco.com<mailto:acee@cisco.com>> wrote:

The question of OSPFv2 complete blocking of transit routing support
(similar to OSPFv3) seems to come up every year or so. I’d like to WG
call this document. Does anyone see any issues?

On 6/14/17, 12:44 PM, "OSPF on behalf of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>"
<ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org> on behalf of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts
This draft is a work item of the Open Shortest Path First IGP of the

        Title           : H-bit Support for OSPFv2
        Authors         : Keyur Patel
                          Padma Pillay-Esnault
                          Manish Bhardwaj
                          Serpil Bayraktar
            Filename        : draft-ietf-ospf-ospfv2-hbit-03.txt
            Pages           : 8
            Date            : 2017-06-14

   OSPFv3 defines an option field for router-LSAs known as a R-bit in
   RFC5340.  If the R-bit is clear, an OSPFv3 router can participate in
   OSPF topology distribution without acting as a forwarder to forward
   the transit traffic.  In such cases, an OSPF router would only accept
   traffic intended for local delivery.  This draft defines R-bit
   functionality for OSPFv2 defined in RFC2328.

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:

OSPF mailing list

OSPF mailing list

OSPF mailing list