Re: IETF Last Call for two IPR WG Dcouments

Harald Tveit Alvestrand <harald@alvestrand.no> Mon, 31 March 2008 06:12 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 46F913A68A5; Sun, 30 Mar 2008 23:12:07 -0700 (PDT)
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 EA2033A68A5 for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 23:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 VwwWUt4BHrBh for <ietf@core3.amsl.com>; Sun, 30 Mar 2008 23:12:05 -0700 (PDT)
Received: from eikenes.alvestrand.no (eikenes.alvestrand.no [158.38.152.233]) by core3.amsl.com (Postfix) with ESMTP id D730E3A689A for <ietf@ietf.org>; Sun, 30 Mar 2008 23:12:04 -0700 (PDT)
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id DA0342596FD; Mon, 31 Mar 2008 08:12:02 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 01886-01; Mon, 31 Mar 2008 08:11:57 +0200 (CEST)
Received: from [192.168.1.54] (162.80-203-220.nextgentel.com [80.203.220.162]) by eikenes.alvestrand.no (Postfix) with ESMTP id 9283A2596F0; Mon, 31 Mar 2008 08:11:57 +0200 (CEST)
Message-ID: <47F08147.7010507@alvestrand.no>
Date: Mon, 31 Mar 2008 08:14:31 +0200
From: Harald Tveit Alvestrand <harald@alvestrand.no>
User-Agent: Thunderbird 2.0.0.12 (X11/20080227)
MIME-Version: 1.0
To: Olaf Kolkman <olaf@NLnetLabs.nl>
Subject: Re: IETF Last Call for two IPR WG Dcouments
References: <20080324200545.D6E6328C3AE@core3.amsl.com> <59EDC2DC-7692-4716-8753-50A1826198A3@NLnetLabs.nl>
In-Reply-To: <59EDC2DC-7692-4716-8753-50A1826198A3@NLnetLabs.nl>
X-Virus-Scanned: by amavisd-new at alvestrand.no
Cc: ietf@ietf.org
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-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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Olaf Kolkman skrev:
>
>
> While reviewing the documents I tried to determine how the 4 streams 
> currently defined in RFC4844 fit into the framework.
>
> Although the stream is not specifically mentioned it is clear that the 
> incoming rights document applies to the IETF Stream.
That was my interpretation too. I (wearing my WG chair hat) take under 
advisement that this needs to be made clear, possibly with a 4844 reference.

In the terms of pre-4844 terminology, I (wearing my contributor hat) 
always thought of IRTF and IAB streams as subsets of the "non-IETF" stream.
>
> To me it is clear that a contribution to the IAB is explicitly bound 
> by the rules (including the No Duty to Publish rule, that allows for 
> confidential information to be supplied to the IAB), so are 
> contributions from the IAB, i.e. IAB stream document. I conclude this 
> from the fact that "IAB" is part of the IETF under the definition in 
> 1.e. However, I may be over-interpreting, and the status of the 
> incoming rights for the IAB stream is also not captured.
I think the IAB will have to make the rules for the IAB stream; a rule 
that says "-incoming and -outgoing applies as appropriate" would be nice 
and short - but it's not within the scope of an IETF WG to make that 
determination.

                        Harald

_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf