Re: IPR discussion: draft-ietf-tsvwg-rsvp-security-groupkeying

"t.petch" <ietfc@btconnect.com> Sat, 23 July 2011 20:00 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53CAB21F8B53 for <tsvwg@ietfa.amsl.com>; Sat, 23 Jul 2011 13:00:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.479
X-Spam-Level:
X-Spam-Status: No, score=-2.479 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599]
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 m8dj3JDQOJ3j for <tsvwg@ietfa.amsl.com>; Sat, 23 Jul 2011 13:00:52 -0700 (PDT)
Received: from mail.btconnect.com (c2bthomr10.btconnect.com [213.123.20.128]) by ietfa.amsl.com (Postfix) with ESMTP id EE3F821F8696 for <tsvwg@ietf.org>; Sat, 23 Jul 2011 13:00:51 -0700 (PDT)
Received: from host86-174-254-236.range86-174.btcentralplus.com (HELO pc6) ([86.174.254.236]) by c2bthomr10.btconnect.com with SMTP id DUD19806; Sat, 23 Jul 2011 21:00:08 +0100 (BST)
Message-ID: <024b01cc496a$53ee7800$4001a8c0@gateway.2wire.net>
From: "t.petch" <ietfc@btconnect.com>
To: gorry@erg.abdn.ac.uk, tsvwg WG <tsvwg@ietf.org>
References: <94007F3F05A24CF0AAFA916B42F93E69@davidPC> <4E2A9822.6020201@erg.abdn.ac.uk>
Subject: Re: IPR discussion: draft-ietf-tsvwg-rsvp-security-groupkeying
Date: Sat, 23 Jul 2011 20:57:07 +0200
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Mirapoint-IP-Reputation: reputation=Fair-1, source=Queried, refid=tid=0001.0A0B0302.4E2B2848.002C, actions=tag
X-Junkmail-Premium-Raw: score=7/50, refid=2.7.2:2011.7.23.183914:17:7.586, ip=86.174.254.236, rules=__HAS_MSGID, __OUTLOOK_MSGID_1, __SANE_MSGID, __TO_MALFORMED_2, __TO_NO_NAME, __BOUNCE_CHALLENGE_SUBJ, __BOUNCE_NDR_SUBJ_EXEMPT, __MIME_VERSION, __CT, CT_TP_8859_1, __CT_TEXT_PLAIN, __CTE, __HAS_X_PRIORITY, __HAS_MSMAIL_PRI, __HAS_X_MAILER, USER_AGENT_OE, __OUTLOOK_MUA_1, __USER_AGENT_MS_GENERIC, __ANY_URI, __URI_NO_WWW, __URI_NO_PATH, BODYTEXTP_SIZE_3000_LESS, BODY_SIZE_1600_1699, __MIME_TEXT_ONLY, RDNS_GENERIC_POOLED, BODY_SIZE_5000_LESS, RDNS_SUSP_GENERIC, __OUTLOOK_MUA, RDNS_SUSP, BODY_SIZE_2000_LESS, BODY_SIZE_7000_LESS
X-Junkmail-Status: score=10/50, host=c2bthomr10.btconnect.com
X-Junkmail-Signature-Raw: score=unknown, refid=str=0001.0A0B0208.4E2B286A.00A9, ss=1, fgs=0, ip=0.0.0.0, so=2010-07-22 22:03:31, dmn=2009-09-10 00:05:08, mode=multiengine
X-Junkmail-IWF: false
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tsvwg>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jul 2011 20:00:53 -0000

---- Original Message -----
From: "Gorry Fairhurst" <gorry@erg.abdn.ac.uk>
To: "tsvwg WG" <tsvwg@ietf.org>
Sent: Saturday, July 23, 2011 11:45 AM
>
> The draft above is now in Last Call, and there needs to now be a
> discussion within TSVWG relating to the acceptability of the IPR terms
> for this document.
>
> There is an IPR statement filed:
> ID # 988 "Cisco's Statement about IPR claimed in
> draft-ietf-tsvwg-rsvp-security-groupkeying-01.txt"
>
> This seems to provide RAND terms for compliance to a standard, but this
> I-D is not being submitted as a standards-track document. The terms in
> the IPR declaration do not seem to provide non-assert status for
> implementing an Informational document. Please can the WG discuss this?

I think that you are reading too much into the IPR claim, which is probably
written by a lawyer whose use of terms means what (s)he wants them to mean and
has no relationship to their usage by other people such as the IETF.

I suggest that the editors of this I-D contact the e-mail addresses in the IPR
claim and ask for clarification as the meaning of the word 'standard', whether
the term is being using in the IETF sense, and so excluding BCP, Experimental
etc of whether it is being used in another sense and so, for example,
encompassing any document that the IETF produces as part of the RFC series.

Tom Petch
>
> * Specifically, do other options exist that would not introduce this IPR
> dependence?
>
> * Have these options been explored?
>
> * What does the WG recommend? (We can discuss this further in the WG
> meeting next week).
>
> Best wishes,
>
> Gorry Fairhurst
>
> TSVWG Chair