Letter sent to FSF, needs a follow-up...
Alex Loret de Mola <edgarverona@gmail.com> Tue, 10 February 2009 14:38 UTC
Return-Path: <edgarverona@gmail.com>
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74C1D28C238 for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 06:38:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 tagged_above=-999 required=5 tests=[AWL=0.198, BAYES_00=-2.599, DEAR_SOMETHING=1.605, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMRAN2Yg7r45 for <ietf@core3.amsl.com>; Tue, 10 Feb 2009 06:37:59 -0800 (PST)
Received: from el-out-1112.google.com (el-out-1112.google.com [209.85.162.179]) by core3.amsl.com (Postfix) with ESMTP id 3C58328C223 for <ietf@ietf.org>; Tue, 10 Feb 2009 06:37:59 -0800 (PST)
Received: by el-out-1112.google.com with SMTP id r27so1744084ele.13 for <ietf@ietf.org>; Tue, 10 Feb 2009 06:38:02 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=S6GL27dEpqD6KJz4qW4IMM+ifwBxteU5pxYmGsZN+Z4=; b=CE0TEE/aPNBGjMGjXw/76mAwmsckAD7YoSEtB4K2x31Dz6UxR6n5dopPRPct9GfuXa tYQmeu9AL2ZczmuJBTr9McBogGKnQYHWZccnNpmCXi9kBfaV+n8GRjEKBtE/w3NXh/w8 8yv0pt2ELrd2iT1S6Tmg4c0JyCKB9YqVbAOsA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=ZfnM4GsTePESWzx/SE/3d4Lngsv6A0hXCXAjX+mRGA+ob/7XnYjH1TAi3hROlHHdXG iJITYldw38KGWhWJstcoAsIjD3bepyYh15s/b2d6Sp0VD0+tmweNZEy4DIhwbSMia6Q4 4YoHqSnLNmTZ/bgoajidsjIlSCN0T4NorUBxw=
MIME-Version: 1.0
Received: by 10.90.102.15 with SMTP id z15mr632720agb.107.1234276682069; Tue, 10 Feb 2009 06:38:02 -0800 (PST)
Date: Tue, 10 Feb 2009 09:38:02 -0500
Message-ID: <789dbae90902100638j57365b07t127600161923aae8@mail.gmail.com>
Subject: Letter sent to FSF, needs a follow-up...
From: Alex Loret de Mola <edgarverona@gmail.com>
To: ietf@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Feb 2009 14:38:00 -0000
Dear All: As promised last night, I have sent the FSF's Campaign E-Mail address an E-Mail detailing the following: "Dear Sirs: Good morning! During the ensuing discussion at the IETF concerning TLS-authz, I found out about several avenues that may be more productive to channel input than the general mailing list. In sharing these, hopefully you can help those who are interested in this subject and who want to participate in the process to reach the right people and make their voices heard in the right place. * File an IPR disclosure if a specific instance of encumberance can be found: https://datatracker.ietf.org/ipr/about/, thus bringing attention to the subject directly to the relevant task force and all interested parties. (Ideally, this should only be done once per IPR discovered, as having "duplicate" disclosures would be counterproductive to your cause) * Review the latest disclosure from RedPhone (https://datatracker.ietf.org/ipr/1026/) and determine if the IPR disclosed is unsatisfactory or too wide-reaching. If it is, send your queries and concerns directly to the assigned Working Group (which, supposedly, should be http://www.ietf.org/html.charters/tls-charter.html , though admittedly it is not appearing in their list of current internet drafts. I will look into this and see why such is the case) * Users who do not do the above steps should join the IUCG (http://iucg.org/) so that you may contribute to the discussion in the context of internet users who are concerned by the proposal, and join in the discussion about what is troubling and how it may be resolved. Hopefully this helps!" The only problem I ran into, which I must follow up on, is why the TLS working group doesn't seem to have jurisdiction over the draft in question (draft-housley-tls-authz-extns-07). The draft in question must've been considered an individual submission, according to RFC 2026. I was told that I should direct those interested in discussion of the subject to the appropriate working group for discussion with them directly as opposed to in the general list, however that currently seems to not be possible. Is there any course of action I can advise in my follow-up E-Mail, or can they still go to the TLS working group with their concerns (if they feel the desire to do so)? Sincerely, Alex Loret de Mola Lead Software Engineer, iScan Services
- Letter sent to FSF, needs a follow-up... Alex Loret de Mola