Re: [OPSEC] Fwd: Reminder about IPR relating to draft-ietf-opsec-ipv6-implications-on-ipv4-nets

"Will Liu (Shucheng)" <liushucheng@huawei.com> Fri, 01 February 2013 01:02 UTC

Return-Path: <liushucheng@huawei.com>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47EFB21F8A61 for <opsec@ietfa.amsl.com>; Thu, 31 Jan 2013 17:02:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qaKJBY3evPh6 for <opsec@ietfa.amsl.com>; Thu, 31 Jan 2013 17:02:56 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id B5ECD21F8A14 for <opsec@ietf.org>; Thu, 31 Jan 2013 17:02:55 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id APH40833; Fri, 01 Feb 2013 01:02:54 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 1 Feb 2013 01:02:11 +0000
Received: from SZXEML408-HUB.china.huawei.com (10.82.67.95) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 1 Feb 2013 01:02:53 +0000
Received: from SZXEML546-MBX.china.huawei.com ([169.254.3.40]) by szxeml408-hub.china.huawei.com ([10.82.67.95]) with mapi id 14.01.0323.007; Fri, 1 Feb 2013 09:02:10 +0800
From: "Will Liu (Shucheng)" <liushucheng@huawei.com>
To: "warren@kumari.net" <warren@kumari.net>
Thread-Topic: Fwd: Reminder about IPR relating to draft-ietf-opsec-ipv6-implications-on-ipv4-nets
Thread-Index: AQHOAAXuVP52Xb/r7kCaQIPgdrQCQphkLm+Q
Date: Fri, 01 Feb 2013 01:02:09 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB2BA0FEB3@szxeml546-mbx.china.huawei.com>
References: <CF23F18F-B403-47D9-8B1F-4D35D3C8187D@kumari.net> <510AF609.5080802@si6networks.com>
In-Reply-To: <510AF609.5080802@si6networks.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.78.117]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: Fernando Gont <fgont@si6networks.com>, "opsec@ietf.org" <opsec@ietf.org>
Subject: Re: [OPSEC] Fwd: Reminder about IPR relating to draft-ietf-opsec-ipv6-implications-on-ipv4-nets
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/opsec>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Feb 2013 01:02:57 -0000

Hi, Warren,

Sorry for being late.
I'm personally not aware of any relevant IPR. Thanks. 

Regards,
Will

> -------- Original Message --------
> From: Warren Kumari <warren@kumari.net>
> Date: Thu, 31 Jan 2013 14:39:23 -0500
> Cc: Warren Kumari <warren@kumari.net>
> Content-Transfer-Encoding: quoted-printable
> Message-Id: <CF23F18F-B403-47D9-8B1F-4D35D3C8187D@kumari.net>
> References: <E7CA55FD-DF4B-4B5E-B391-6247C9E9352E@kumari.net>
> To: opsec@ietf.org <OpSec@ietf.org>,
> draft-ietf-opsec-ipv6-implications-on-ipv4-nets@tools.ietf.org
> <draft-ietf-opsec-ipv6-implications-on-ipv4-nets@tools.ietf.org>, opsec
> chairs <opsec-chairs@tools.ietf.org>
> Subject: Fwd: Reminder about IPR relating to
> draft-ietf-opsec-ipv6-implications-on-ipv4-nets
> 
> For some reason this seems to have been eaten by the mailer...
> 
> Resending...
> 
> W
> 
> Begin forwarded message:
> 
> > From: Warren Kumari <warren@kumari.net>
> > Subject: Reminder about IPR relating to
> draft-ietf-opsec-ipv6-implications-on-ipv4-nets
> > Date: January 24, 2013 12:02:07 PM EST
> > To: "opsec@ietf.org" <OpSec@ietf.org>,
> draft-ietf-opsec-ipv6-implications-on-ipv4-nets@tools.ietf.org, opsec chairs
> <opsec-chairs@tools.ietf.org>
> > Cc: Warren Kumari <warren@kumari.net>
> >
> > Dear OpSec WG,
> >
> > Be not alarmed.
> > This email was created to satisfy RFC 6702 "Promoting Compliance with
> Intellectual Property Rights (IPR)"  (http://tools.ietf.org/rfc/rfc6702.txt).
> >
> > We are doing the IPR reminder in parallel with the WGLC so that we have
> all our ducks in a row...
> >
> > Are you personally aware of any IPR that applies to
> draft-ietf-opsec-ipv6-implications-on-ipv4-nets?  If so, has this IPR been
> disclosed in compliance with IETF IPR rules?
> > (See RFCs 3979, 4879, 3669, and 5378 for more details.)
> >
> > If you are a document author or listed contributor on this document,
> please reply to this email regardless of whether or not you are personally
> aware of any relevant IPR.  We might not be able to advance this document
> to the next stage until we have received a reply from each author and listed
> contributor.
> >
> > If you are on the OpSec WG email list but are not an author or listed
> contributor for this document, you are reminded of your opportunity for a
> voluntary IPR disclosure under BCP 79.  Please do not reply unless you want
> to make such a voluntary disclosure.
> >
> > Online tools for filing IPR disclosures can be found at
> <http://www.ietf.org/ipr/file-disclosure>.
> >
> > Thanks,
> > Warren Kumari
> > (as OpSec WG co-chair)
> >
> > --
> > "I think perhaps the most important problem is that we are trying to
> understand the fundamental workings of the universe via a language devised
> for telling one another when the best fruit is." --Terry Prachett
> >
> >
> 
> --
> "I think perhaps the most important problem is that we are trying to
> understand the fundamental workings of the universe via a language
> devised for telling one another when the best fruit is." --Terry Prachett
> 
> 
> 
>