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

"Acee Lindem (acee)" <acee@cisco.com> Mon, 26 June 2017 22:50 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 3F79F1270A3 for <ospf@ietfa.amsl.com>; Mon, 26 Jun 2017 15:50:27 -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 uCCtMqRWEhaP for <ospf@ietfa.amsl.com>; Mon, 26 Jun 2017 15:50:25 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDEFB12702E for <ospf@ietf.org>; Mon, 26 Jun 2017 15:50:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4394; q=dns/txt; s=iport; t=1498517425; x=1499727025; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=O9dQjjIZJQ94n2bRJIYqV/3wDWXRz4ja3FR7/CE/NFM=; b=X/Lby1g+wfXIM3AduFO6iPe9thzk99KN4KUckURL0CFn5BZRJ2jGEhrz DfnGP4L1REPFsnPqjpVJ1gp8TtxHgfCryaj5FUiFKArVMa+qW24OeVtfV g/wigjn53DZa9IFabCHIrecaodiTZ68Fy+Yf3guCOX9+Y6tz1NuTju/LG g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DlAADrjlFZ/5hdJa1dGQEBAQEBAQEBAQEBBwEBAQEBg1hifBEHg2WKGZFilXqCESELhXgcglM/GAECAQEBAQEBAWsohRkBAQEDAQEbBhE6BgUSAQgYAgImAgQlCxUSBAENBYosELAcgiaLWwEBAQEBAQEBAQEBAQEBAQEBAQEfgQuCHIhRgyaBFRIBHIMTgmEFnmkChzKMM4IJVoRyikGVIAEfOH8LdBUfKocPdocGgSOBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.39,397,1493683200"; d="scan'208";a="262770854"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Jun 2017 22:50:23 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v5QMoNYD027710 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 26 Jun 2017 22:50:23 GMT
Received: from xch-rtp-015.cisco.com (64.101.220.155) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Mon, 26 Jun 2017 18:50:23 -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:50:22 -0400
From: "Acee Lindem (acee)" <acee@cisco.com>
To: "Acee Lindem (acee)" <acee@cisco.com>, "draft-ietf-ospf-ospfv2-hbit@ietf.org" <draft-ietf-ospf-ospfv3-hbit@ietf.org>
CC: OSPF WG List <ospf@ietf.org>
Thread-Topic: [OSPF] IPR Call for "H-Support for OSPFv2"
Thread-Index: AQHS7s6X4Wov4XfIrkul8Ncbp0ekHA==
Date: Mon, 26 Jun 2017 22:50:22 +0000
Message-ID: <D57707A0.B661F%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: <809A3703D0997D45929F320B1775A976@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/9XLVkBMBQZB9VrbqbS-OWFLIsBM>
Subject: Re: [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:50:27 -0000

Corrected draft alias - reply to this one.

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

>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
>
>_______________________________________________
>OSPF mailing list
>OSPF@ietf.org
>https://www.ietf.org/mailman/listinfo/ospf