Re: [rtcweb] Counting NOs (Re: Straw Poll on Nokia mincing)

Stephan Wenger <stewe@stewe.org> Fri, 20 December 2013 22:46 UTC

Return-Path: <stewe@stewe.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 379FE1AE224 for <rtcweb@ietfa.amsl.com>; Fri, 20 Dec 2013 14:46:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.602
X-Spam-Level:
X-Spam-Status: No, score=-4.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 7ypvmYaXEI8E for <rtcweb@ietfa.amsl.com>; Fri, 20 Dec 2013 14:46:37 -0800 (PST)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0158.outbound.protection.outlook.com [207.46.163.158]) by ietfa.amsl.com (Postfix) with ESMTP id A9F2B1A1F5E for <rtcweb@ietf.org>; Fri, 20 Dec 2013 14:46:36 -0800 (PST)
Received: from CO1PR07MB363.namprd07.prod.outlook.com (10.141.75.22) by CO1PR07MB364.namprd07.prod.outlook.com (10.141.75.13) with Microsoft SMTP Server (TLS) id 15.0.842.7; Fri, 20 Dec 2013 22:46:25 +0000
Received: from CO1PR07MB363.namprd07.prod.outlook.com ([169.254.3.31]) by CO1PR07MB363.namprd07.prod.outlook.com ([169.254.3.31]) with mapi id 15.00.0842.003; Fri, 20 Dec 2013 22:46:25 +0000
From: Stephan Wenger <stewe@stewe.org>
To: Ron <ron@debian.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Counting NOs (Re: Straw Poll on Nokia mincing)
Thread-Index: AQHO/cIV9+pQ+kVXvkK26hGEf9R4Y5pdnF8A//+MmgA=
Date: Fri, 20 Dec 2013 22:46:24 +0000
Message-ID: <CEDA07B9.3E240%stewe@stewe.org>
In-Reply-To: <20131220213922.GP3245@audi.shelbyville.oz>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [50.174.124.99]
x-forefront-prvs: 0066D63CE6
x-forefront-antispam-report: SFV:NSPM; SFS:(10009001)(24454002)(189002)(199002)(51704005)(479174003)(377454003)(76176001)(47446002)(74502001)(87936001)(36756003)(81342001)(66066001)(74876001)(87266001)(80022001)(74706001)(76796001)(2656002)(76482001)(76786001)(79102001)(77982001)(81542001)(49866001)(19580405001)(4396001)(56816005)(85306002)(81686001)(47976001)(63696002)(83322001)(81816001)(50986001)(19580395003)(80976001)(74366001)(51856001)(69226001)(54356001)(53806001)(85852003)(59766001)(83072002)(31966008)(47736001)(54316002)(65816001)(46102001)(56776001)(74662001)(90146001)(77096001)(14444003)(42262001); DIR:OUT; SFP:1101; SCL:1; SRVR:CO1PR07MB364; H:CO1PR07MB363.namprd07.prod.outlook.com; CLIP:50.174.124.99; FPR:; RD:InfoNoRecords; MX:1; A:0; LANG:en;
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F3B78197DACD794D81B35092BD2388F4@namprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: stewe.org
Subject: Re: [rtcweb] Counting NOs (Re: Straw Poll on Nokia mincing)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Dec 2013 22:46:39 -0000

Ron,

On 12/20/13, 1:39 PM, "Ron" <ron@debian.org> wrote:

>[Š]
>And it would also seem to be subject to the IETF requirement that security
>technologies MUST be strictly RF.

There is no such requirement.  The only requirement that I recall related
to security technologies is that, whenever security is mandated, that
there MUST be at least one RF security technology be mandated.  Optional
other security technologies can be royalty bearing or otherwise encumbered.

Also please note that security is the one single exception we currently
have in the IETF where there exists an actual licensing requirement.  I
would argue very strongly against creating another such precedence.

>Which leaves the door open that the IETF
>_could_ always assume change control of it if the need ever arose.  Which
>seems reasonably pragmatic, even absent the "mandatory unless" language,
>and the IETF does make sensible exceptions for strictly RF technologies.
>
>We don't appear to have that option in the case of H.264 though, in the
>light of declarations and statements that insist there would never be a
>licence granted for an alternative but similar technology, by at least
>one major IPR holder.
>
>
>I know we're edging out of the scope of things that this group is
>chartered
>to decide on, but I don't see any document that explicitly gives us the
>option to ignore these requirements either, and it does seem relevant to
>the decision that we need to make.
>
>Even after we decide on something (assuming that we do), it's still going
>to need to run the gauntlet of the broader IETF, and we seem to be
>somewhat
>perilously close to a loophole whereby I could reference something which
>I hold IPR on, that was published in the newsletter of my mother's
>knitting
>group, and then assert with a Straight Face, that I have no obligation to
>disclose, since it was Published Elsewhere.  And point to the discussion
>here as precedent for that.
>
>
>The IETF requirements as published would seem to be very clear.  Where
>does
>our leeway come from to blur those lines here?
>
>  Cheers,
>  Ron
>
>
>_______________________________________________
>rtcweb mailing list
>rtcweb@ietf.org
>https://www.ietf.org/mailman/listinfo/rtcweb