Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice

Russ Housley <housley@vigilsec.com> Thu, 02 January 2014 21:44 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 54DF81ADF9C; Thu, 2 Jan 2014 13:44:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] 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 NyCsLLAzek94; Thu, 2 Jan 2014 13:44:31 -0800 (PST)
Received: from odin.smetech.net (mail.smetech.net [209.135.209.4]) by ietfa.amsl.com (Postfix) with ESMTP id 1D63D1ADF8E; Thu, 2 Jan 2014 13:44:31 -0800 (PST)
Received: from localhost (unknown [209.135.209.5]) by odin.smetech.net (Postfix) with ESMTP id 25B699A423A; Thu, 2 Jan 2014 16:44:14 -0500 (EST)
X-Virus-Scanned: amavisd-new at smetech.net
Received: from odin.smetech.net ([209.135.209.4]) by localhost (ronin.smeinc.net [209.135.209.5]) (amavisd-new, port 10024) with ESMTP id n2B-dJtkz9zh; Thu, 2 Jan 2014 16:43:53 -0500 (EST)
Received: from [192.168.2.110] (pool-96-255-140-248.washdc.fios.verizon.net [96.255.140.248]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by odin.smetech.net (Postfix) with ESMTP id 1D3C89A4220; Thu, 2 Jan 2014 16:43:53 -0500 (EST)
Subject: Re: Concerns about draft-moonesamy-ietf-conduct-3184bis-05 becoming a Best Current Practice
Mime-Version: 1.0 (Apple Message framework v1085)
Content-Type: text/plain; charset="us-ascii"
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com>
Date: Thu, 02 Jan 2014 16:43:41 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <3574E3F1-F5B4-4218-A834-B94144AC59B3@vigilsec.com>
References: <20131209225636.27148.57076.idtracker@ietfa.amsl.com> <0066A55B-A033-4FC9-8C4C-23C1306F6E98@vigilsec.com> <6.2.5.6.2.20131230120808.0c0188f0@resistor.net> <3442080B-EFB3-46A8-9581-E9165C8CD1CC@vigilsec.com> <6.2.5.6.2.20131231235656.0bc510d8@elandnews.com>
To: S Moonesamy <sm+ietf@elandsys.com>
X-Mailer: Apple Mail (2.1085)
Cc: IESG <iesg@ietf.org>, IETF <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 02 Jan 2014 21:44:33 -0000

SM:

> An alternative might be:
> 
>   3. IETF participants devise solutions for the Internet that meet the
>      needs of diverse technical and operational environments.
> 
>      The mission of the IETF is to produce high quality, relevant
>      technical and engineering documents that influence the way people
>      design, use, and manage the Internet in such a way as to make the
>      Internet work better.  The IETF puts its emphasis on technical
>      competence, rough consensus and individual participation, and needs
>      to be open to competent input from any source.
> 
>      IETF participants use their best engineering judgment to find the
>      best solution for the whole Internet, not just the best solution
>      for any particular network, technology, vendor, or user.  While we
>      all have ideas that may stand improvement from time to time, no
>      one shall ever knowingly contribute advice or text that would make
>      a standard technically inferior.

This proposed text is an improvement, but I would be much happier with the addition of one word to the first sentence:  ... devise solutions for the global Internet ...

>> BCP 79 is the proper reference.
>> 
>> Following the IPR rules is an obligation for all IETF participants.  It was in RFC 3184, and I think we need to keep in this document.
> 
> The text in RFC 3184 is as follows:
> 
>  "We follow the intellectual property guidelines outlined in BCP 9."
> 
> In my opinion that text does not fit under the third statement.  An alternative, which was suggested, is to have it under another guideline.  The comment mentions that it is an obligation and I agree with that.  The point being discussed is that the obligation has to be kept in this document because it was in RFC 3184.  The document has been described as being about personal conduct and personal interaction.  The document does not discuss about rules.

Disclosure of IPR that you know about is personal conduct.

> The Note Well is used to direct people to BCP 79.  A person attending a working group session will be told about the Note Well.  A person subscribing to an IETF mailing list will be sent a pointer to the Note Well.  I suggest leaving it to the Note Well to list the rules as it has not been argued that the Note Well is inadequate.

RFC 3184 included a sentence telling people about the expected conduct regarding IPR disclosure.  I strongly believe that 3184 should do the same.

Russ