[Capwap] IPR alert on MIB drafts

"Mani, Mahalingam (Mani)" <mmani@avaya.com> Fri, 30 May 2008 19:49 UTC

Return-Path: <capwap-bounces+capwap-archive=lists.ietf.org@frascone.com>
X-Original-To: ietfarch-capwap-archive@core3.amsl.com
Delivered-To: ietfarch-capwap-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 620E63A68C0 for <ietfarch-capwap-archive@core3.amsl.com>; Fri, 30 May 2008 12:49:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CeruuQheBdNm for <ietfarch-capwap-archive@core3.amsl.com>; Fri, 30 May 2008 12:49:22 -0700 (PDT)
Received: from mx2.tigertech.net (mx2.tigertech.net [64.62.209.32]) by core3.amsl.com (Postfix) with ESMTP id 50E3E3A68B3 for <capwap-archive@lists.ietf.org>; Fri, 30 May 2008 12:49:22 -0700 (PDT)
Received: from hermes.tigertech.net (localhost [127.0.0.1]) by hermes.tigertech.net (Postfix) with ESMTP id 2B0E81C40F6E for <capwap-archive@lists.ietf.org>; Fri, 30 May 2008 12:49:20 -0700 (PDT)
Received: from mx1.tigertech.net (mx1.tigertech.net [64.62.209.31]) by hermes.tigertech.net (Postfix) with ESMTP id DB0F01C40F42 for <capwap@lists.tigertech.net>; Fri, 30 May 2008 12:49:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id A21FB1D8C9B1 for <capwap@frascone.com>; Fri, 30 May 2008 12:49:00 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from hgblob.tigertech.net (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id D18651D8C9A0 for <capwap@frascone.com>; Fri, 30 May 2008 12:48:56 -0700 (PDT)
X-TigerTech-Content-Filter: Clean
X-TigerTech-Spam-Status: Level 1 (Low); Accepted (Neutral)
Received: from co300216-co-outbound.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) by hgblob.tigertech.net (Postfix) with ESMTP for <capwap@frascone.com>; Fri, 30 May 2008 12:48:56 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.27,568,1204520400"; d="scan'208,217";a="129204173"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.avaya.com with ESMTP; 30 May 2008 15:48:54 -0400
X-IronPort-AV: E=Sophos;i="4.27,568,1204520400"; d="scan'208,217";a="210158230"
Received: from unknown (HELO 306181ANEX2.global.avaya.com) ([135.9.6.103]) by co300216-co-erhwest-out.avaya.com with ESMTP; 30 May 2008 15:48:54 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Fri, 30 May 2008 13:48:50 -0600
Message-ID: <EBB9BE2655816245BBCAE52B97E72D66024956F3@306181ANEX2.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: IPR alert on MIB drafts
Thread-Index: AcjCji5hmE+upisxTcGjETY1re0WMA==
X-Priority: 1
Priority: Urgent
Importance: high
From: "Mani, Mahalingam (Mani)" <mmani@avaya.com>
To: capwap <capwap@frascone.com>
Subject: [Capwap] IPR alert on MIB drafts
X-BeenThere: capwap@frascone.com
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: A list for CAPWAP technical discussions <capwap.frascone.com>
List-Unsubscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=unsubscribe>
List-Archive: <http://lists.frascone.com/pipermail/capwap>
List-Post: <mailto:capwap@frascone.com>
List-Help: <mailto:capwap-request@frascone.com?subject=help>
List-Subscribe: <http://lists.frascone.com/mailman/listinfo/capwap>, <mailto:capwap-request@frascone.com?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0136003491=="
Errors-To: capwap-bounces+capwap-archive=lists.ietf.org@frascone.com

On the basis of IETF71 discussions and questions; and subsequently the
question popped by the chair(s) on the list - we had adopted the MIB
drafts

 

draft-yangshi-capwap-802dot11-mib
<http://www.ietf.org/internet-drafts/draft-yangshi-capwap-802dot11-mib-0
2.txt> 

draft-yangshi-capwap-base-mib
<http://www.ietf.org/internet-drafts/draft-yangshi-capwap-base-mib-02.tx
t> 

 

as WG items - given there were no objections to the call for adopting
them as WG items made on the list 3/14/08.[this tracked the rough
consensus recorded in

IETF71].

 

Since then the authors have apparently submitted to the IETF as WG items
and the drafts now in the process of being posted as such, I understand.

 

Since then I came to note, on 5/27, that there are two IPR disclosures
made on the aforementioned individual submissions by  H3C (one of the
editors has affiliation to it) - disclosure #s 946, 947:

 

2008-04-23

946

H3C Technology's Statement about IPR related to
draft-yangshi-capwap-802dot11-mib-02
<https://datatracker.ietf.org/ipr/946/>  

2008-04-23

947

H3C Technology's Statement about IPR related to
draft-yangshi-capwap-base-mib-02 <https://datatracker.ietf.org/ipr/947/>


 

It is not clear if the other two editors are aware of this either.

 

This is to let WG take note of these disclosures and also opine whether
that changes anyone's position in this WG regarding accepting these
drafts as WG items

(again - as it stands now and as stated above - the drafts are accepted
as WG items).

 

[This is in anticipation of the formality that these disclosures will
carry forward to the WG drafts when they get posted - given that the
draft semantics related to these disclosures will carry forward].

 

Regards,

-mani

=============

Mahalingam Mani

(408)321-4840 (w)

 

_________________________________________________________________
To unsubscribe or modify your subscription options, please visit:
http://lists.frascone.com/mailman/listinfo/capwap

Archives: http://lists.frascone.com/pipermail/capwap