Re: [v6ops] Mail regarding draft-ietf-v6ops-464xlat

Warren Kumari <warren@kumari.net> Fri, 11 January 2013 15:24 UTC

Return-Path: <warren@kumari.net>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE5BD21F896B for <v6ops@ietfa.amsl.com>; Fri, 11 Jan 2013 07:24:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.299
X-Spam-Level:
X-Spam-Status: No, score=-102.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
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 JqAzQvVsvh3E for <v6ops@ietfa.amsl.com>; Fri, 11 Jan 2013 07:24:55 -0800 (PST)
Received: from vimes.kumari.net (smtp1.kumari.net [204.194.22.1]) by ietfa.amsl.com (Postfix) with ESMTP id CBCA721F8949 for <v6ops@ietf.org>; Fri, 11 Jan 2013 07:24:54 -0800 (PST)
Received: from [192.168.1.136] (unknown [66.84.81.126]) by vimes.kumari.net (Postfix) with ESMTPSA id 8B75F1B407DD; Fri, 11 Jan 2013 10:24:53 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <50EFD38E.10901@gmail.com>
Date: Fri, 11 Jan 2013 10:24:52 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <F25B2F8E-9B7F-4A87-9EE1-64648CA78EB3@kumari.net>
References: <2CF4CB03E2AA464BA0982EC92A02CE2501E2E981@BY2PRD0512MB653.namprd05.prod.outlook.com> <m2r4ls3611.wl%randy@psg.com> <CAD6AjGQqSHoUu37zqaL7KAjzDj3YPT153zCs1HiooeNCo=-YoA@mail.gmail.com> <50EFD38E.10901@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1499)
Cc: IPv6 Operations <v6ops@ietf.org>, Hui Deng <denghui@chinamobile.com>
Subject: Re: [v6ops] Mail regarding draft-ietf-v6ops-464xlat
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Jan 2013 15:24:55 -0000

On Jan 11, 2013, at 3:55 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:

> On 11/01/2013 01:23, Cameron Byrne wrote:
>> Hui, Deng and v6ops,
>> 
>> On Thu, Jan 10, 2013 at 4:41 PM, Randy Bush <randy@psg.com> wrote:
>>> thanks for the flag, ron.  imiho
>>> 
>>> "Reasonable and Non-Discriminatory License to All Implementers with
>>> Possible Royalty/Fee."
>>> 
>>> is a pretty much a show-stopper
>>> 
>> 
>> 
>> As you can see, we have a problem.  The IESG only has this final IPR
>> issue to resolve before publishing 464XLAT.
>> 
>> I see a few ways forward:
>> 
>> 1.  China Mobile can grant free use for the benefit of the IETF and
>> the benefit of global IPv6 adoption and on-going evolution of the
>> Internet
>> 
>> 2.  The IETF can move forward on the basis that the IPR claim is invalid*.
>> 
>> 3.  Other options???
> 
> 4. The IETF can move forward because its rules allow RAND conditions.

Yes, the IETF *can* move forward, but *can* also decide that the IPR is annoying, discourages implementation, and makes possible risks for implements, and so it *can* (I believe) decide not to move forward.

Not saying that it should do this, but..
> 
> There are innumerable IETF standards with RAND disclosures against them.
> We may not like it, but we do it all the time.
> 

Yes, yes we do. We also sometimes decide to choose other, non-encumbered options.

> The summary of the claims (http://ip.com/patfam/en/43370583) is
> very broad. Judging by that, if this disclosure was required, a disclosure
> against draft-huang-behave-bih or RFC 6535 would also have been required.
> However, the prior art for that goes back to RFC 2767, which is way before
> this recent patent.
> 
> It isn't the IETF's job to determine whether a patent is valid. But if
> we have a strong inclination to believe it's invalid, and the disclosure
> in any case meets our rules, we can <shrug>. It's then for implementors
> to decide what to do.
> 
>   Brian


IANAL, nor do I pretend to play one on TV, 
W

> 
>> 
>> Regards,
>> 
>> CB
>> 
>> *I am not a lawyer, but the 464XLAT draft is just a combination of
>> existing technologies, none of which has IPR.  And, AFAIK [1], it is
>> not legitimate to patent a combination of existing technologies ....
>> which is what the IPR claim is.  NAT-PT goes back to the year 2000 as prior art.
>> 
>> So, simple analysis, says this patent is not valid.  Yet, we have this claim.
>> 
>> CB
>> 
>> [1] -- http://www.nolo.com/legal-encyclopedia/combination-invention-patentable-patents-29891.html
>> _______________________________________________
>> v6ops mailing list
>> v6ops@ietf.org
>> https://www.ietf.org/mailman/listinfo/v6ops
>> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
> 

-- 
I had no shoes and wept.  Then I met a man who had no feet.  So I said, "Hey man, got any shoes you're not using?"