Re: Normatively referenced specifications

todd glassey <tglassey@earthlink.net> Wed, 18 December 2013 19:51 UTC

Return-Path: <tglassey@earthlink.net>
X-Original-To: ipr-wg@ietfa.amsl.com
Delivered-To: ipr-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D486D1AE108 for <ipr-wg@ietfa.amsl.com>; Wed, 18 Dec 2013 11:51:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level:
X-Spam-Status: No, score=-2.538 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_NONE=-0.0001, RP_MATCHES_RCVD=-0.538] autolearn=ham
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 EwHwy6rRmlMd for <ipr-wg@ietfa.amsl.com>; Wed, 18 Dec 2013 11:51:52 -0800 (PST)
Received: from elasmtp-kukur.atl.sa.earthlink.net (elasmtp-kukur.atl.sa.earthlink.net [209.86.89.65]) by ietfa.amsl.com (Postfix) with ESMTP id 83ED71AE1FA for <ipr-wg@ietf.org>; Wed, 18 Dec 2013 11:51:52 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=f5TTTWpjDoF53TUJyP7+GRJ1xfQZiAcbXrkssj0CyVJf1Hmx9T5r9xWbKCFv1UC3; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=localhost.localdomain) by elasmtp-kukur.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1VtN9q-00005m-G8 for ipr-wg@ietf.org; Wed, 18 Dec 2013 14:51:50 -0500
Message-ID: <52B1FCD4.2000904@earthlink.net>
Date: Wed, 18 Dec 2013 11:51:48 -0800
From: todd glassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ipr-wg@ietf.org
Subject: Re: Normatively referenced specifications
References: <CED46C85.AC4EC%stewe@stewe.org> <6.2.5.6.2.20131217001052.0c5bff98@resistor.net> <8D3D17ACE214DC429325B2B98F3AE712026ECD3A9B@MX15A.corp.emc.com> <6.2.5.6.2.20131218001051.0c266ed0@resistor.net> <CED70C71.119D0%dmohlenh@cisco.com> <52B1CF27.3010905@joelhalpern.com> <52B1DE0C.8010201@dcrocker.net> <36BAA6A693139D4BBCB37CCCA660E08A02B87FCC@eusaamb101.ericsson.se> <52B1E830.30001@dcrocker.net> <36BAA6A693139D4BBCB37CCCA660E08A02B88190@eusaamb101.ericsson.se> <993E6E5E6EA5F13E50293C74@JcK-HP8200.jck.com> <CED72CDA.11A3B%dmohlenh@cisco.com>
In-Reply-To: <CED72CDA.11A3B%dmohlenh@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79cd4534028e037c07cbeb4a47569a86ef350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-BeenThere: ipr-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IPR-WG <ipr-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipr-wg/>
List-Post: <mailto:ipr-wg@ietf.org>
List-Help: <mailto:ipr-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipr-wg>, <mailto:ipr-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Dec 2013 19:51:55 -0000

BS - the IETF's policies are that it is immune from any legal
repercussions from its actions, that the members are working on a holy
mission to create more technology they can sell.

You people crack me up - you talk about transparency and then integrate
enough wiggle room into your practices and standards to allow the BGP4
Route Flap and the other key security flaws in the network to be built
into place.

You want to make the IETF transparent - its simple. Everyone registers
and executes a formal statement complying with BCP78 and BCP79...

Oh wait - that would make you criminally liable for the lies told here
too wouldn't it?  You see my point Counsel?


Todd Glassey


>> Much as some people persist in assuming otherwise, the IETF
>> doesn't have an IPR policy that would touch on what
>> non-copyright grants or rights to implement or use something are
>> required.  There is only a disclosure policy.  So Dave --and I
>> and others-- are talking about the disclosure policy.  As far as
>> what licensing terms are required in referenced documents, there
>> is no such requirement, not because the documents are
>> incorporated by reference but because there or no requirements
>> on the primary/ referencing document either.  Just a requirement
>> about disclosure by any who can reasonably be expected to know
>> about the IPR.
>>
>>   john
>>
>>> -----Original Message-----
>>> From: Dave Crocker [mailto:dhc@dcrocker.net]
>>> Sent: Wednesday, December 18, 2013 10:24 AM
>>> To: Michael Cameron; ipr-wg@ietf.org
>>> Subject: Re: Normatively referenced specifications
>>>
>>> On 12/18/2013 10:09 AM, Michael Cameron wrote:
>>>> But Dave may be right when the IPR is owned by one entity
>>>
>>> This is the sort of attempt at nuance that is impractical and,
>>> by my reading, does not apply to the IETF's disclosure
>>> requirement:
>>
>>
>>
>> _______________________________________________
>> Ipr-wg mailing list
>> Ipr-wg@ietf.org
>> https://www.ietf.org/mailman/listinfo/ipr-wg
> _______________________________________________
> Ipr-wg mailing list
> Ipr-wg@ietf.org
> https://www.ietf.org/mailman/listinfo/ipr-wg
>

-- 
Todd Glasey - Personal Account Disclaimers apply

Restricted content (intended for the original distribution list only),
standard unintended delivery rules and destruction demand apply to any emails wrongly delivered to you, no IP rights conveyance in any emailing is made, intended or others contemplated.