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

"Acee Lindem (acee)" <acee@cisco.com> Mon, 26 June 2017 22:45 UTC

Return-Path: <acee@cisco.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B698126E3A for <ospf@ietfa.amsl.com>; Mon, 26 Jun 2017 15:45:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ejgsIWkOOgxQ for <ospf@ietfa.amsl.com>; Mon, 26 Jun 2017 15:45:29 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0148912702E for <ospf@ietf.org>; Mon, 26 Jun 2017 15:45:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3868; q=dns/txt; s=iport; t=1498517128; x=1499726728; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=4asSOY1M3sz8UIxbcuUEPYeOhAePFTl/gOMtbiMTnyk=; b=KV31HKagpuh7YnjT027xFhA/Ccnxq9xE+KiS3nyZ05B6WFAtzOuVkc7g n/HgMAcsIwOgluf6RNYHoUwwnXi4U8n9ZoPB5NcMaoi3dSY5x7KRzLK8R obbaOCmk+Jy2awWI2VZybA6166nFIJcXn86jd0qHQ1xvq4k7SW0mWNhav U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DkAAB8jVFZ/5tdJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1higQ0Hg2WKGadcghEhC4V4HIJTPxgBAgEBAQEBAQFrHQuFGgE?= =?us-ascii?q?FARsGEToGBRIBIAICJgIEJQsVEgQOBYosELAigiaLWwEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBASCBC4Ici3eBFRIBgy+CYQWeaQKHMowzgglWhHKKQZUgAR84fwt0FR8qhw9?= =?us-ascii?q?2hwaBI4ENAQEB?=
X-IronPort-AV: E=Sophos;i="5.39,397,1493683200"; d="scan'208";a="44781316"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jun 2017 22:45:27 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id v5QMjRP4014407 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 26 Jun 2017 22:45:27 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 26 Jun 2017 18:45:26 -0400
Received: from xch-rtp-015.cisco.com ([64.101.220.155]) by XCH-RTP-015.cisco.com ([64.101.220.155]) with mapi id 15.00.1210.000; Mon, 26 Jun 2017 18:45:26 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "draft-ietf-ospf-ospfv3-hbit@ietf.org" <draft-ietf-ospf-ospfv3-hbit@ietf.org>
CC: OSPF WG List <ospf@ietf.org>
Thread-Topic: IPR Call for "H-Support for OSPFv2"
Thread-Index: AQHS7s3nAFk0mNy600SIz+nT2QUcAA==
Date: Mon, 26 Jun 2017 22:45:26 +0000
Message-ID: <D577049C.B6608%acee@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.116.152.196]
Content-Type: text/plain; charset="utf-8"
Content-ID: <B411456223B59F42A272DE1D103BA662@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/yBj-zXVdeLBPkJTM6V4HIu7PQ30>
Subject: [OSPF] 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: Mon, 26 Jun 2017 22:45:31 -0000

Authors,

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.
 

Thanks,
Acee



On 6/14/17, 3:48 PM, "OSPF on behalf of Acee Lindem (acee)"
<ospf-bounces@ietf.org on behalf of 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 last
>call this document. Does anyone see any issues?
>Thanks,
>Acee 
>
>On 6/14/17, 12:44 PM, "OSPF on behalf of internet-drafts@ietf.org"
><ospf-bounces@ietf.org on behalf of internet-drafts@ietf.org> wrote:
>
>>
>>A New Internet-Draft is available from the on-line Internet-Drafts
>>directories.
>>This draft is a work item of the Open Shortest Path First IGP of the
>>IETF.
>>
>>        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
>>
>>Abstract:
>>   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:
>>https://datatracker.ietf.org/doc/draft-ietf-ospf-ospfv2-hbit/
>>
>>There are also htmlized versions available at:
>>https://tools.ietf.org/html/draft-ietf-ospf-ospfv2-hbit-03
>>https://datatracker.ietf.org/doc/html/draft-ietf-ospf-ospfv2-hbit-03
>>
>>A diff from the previous version is available at:
>>https://www.ietf.org/rfcdiff?url2=draft-ietf-ospf-ospfv2-hbit-03
>>
>>
>>Please note that it may take a couple of minutes from the time of
>>submission
>>until the htmlized version and diff are available at tools.ietf.org.
>>
>>Internet-Drafts are also available by anonymous FTP at:
>>ftp://ftp.ietf.org/internet-drafts/
>>
>>_______________________________________________
>>OSPF mailing list
>>OSPF@ietf.org
>>https://www.ietf.org/mailman/listinfo/ospf
>
>_______________________________________________
>OSPF mailing list
>OSPF@ietf.org
>https://www.ietf.org/mailman/listinfo/ospf