Re: [conex] Last Call: <draft-ietf-conex-concepts-uses-04.txt> (ConEx Concepts and Use Cases) to Informational RFC

marcelo bagnulo braun <marcelo@it.uc3m.es> Fri, 30 March 2012 09:56 UTC

Return-Path: <marcelo@it.uc3m.es>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D86A21F894F; Fri, 30 Mar 2012 02:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.599
X-Spam-Level:
X-Spam-Status: No, score=-106.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KK-lIpjD8Z-1; Fri, 30 Mar 2012 02:56:02 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by ietfa.amsl.com (Postfix) with ESMTP id 5587521F8926; Fri, 30 Mar 2012 02:56:01 -0700 (PDT)
X-uc3m-safe: yes
Received: from dhcp-117d.meeting.ietf.org (dhcp-117d.meeting.ietf.org [130.129.17.125]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp03.uc3m.es (Postfix) with ESMTP id 9B0FA9C63A0; Fri, 30 Mar 2012 11:56:00 +0200 (CEST)
Message-ID: <4F758327.3000104@it.uc3m.es>
Date: Fri, 30 Mar 2012 11:55:51 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Christopher Morrow <morrowc.lists@gmail.com>
Subject: Re: [conex] Last Call: <draft-ietf-conex-concepts-uses-04.txt> (ConEx Concepts and Use Cases) to Informational RFC
References: <20120329141002.22903.96428.idtracker@ietfa.amsl.com> <CAL9jLaZYt0kEWm4rHGZ4JMXraDjRsCP8t7DLKn_bRMZOTy9GTg@mail.gmail.com>
In-Reply-To: <CAL9jLaZYt0kEWm4rHGZ4JMXraDjRsCP8t7DLKn_bRMZOTy9GTg@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.8.0.1017-18806.006
Cc: ietf@ietf.org, IETF-Announce <ietf-announce@ietf.org>, conex@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 30 Mar 2012 09:56:03 -0000

Hi,

Bob's email specifically said specifications and mechanisms would be 
likely to be tagged with the IPR. This particular document is neither a 
specification nor a mechanism as it describes the use cases for conex. 
When the drafts describing the conex spec are sent to the IESG, the IPR 
claim will be propely pointed out.

I hope this clarifies the issue.

Regards, marcelo


El 29/03/12 18:11, Christopher Morrow escribió:
> On Thu, Mar 29, 2012 at 10:10 AM, The IESG<iesg-secretary@ietf.org>  wrote:
>> The IESG has received a request from the Congestion Exposure WG (conex)
>> to consider the following document:
>> - 'ConEx Concepts and Use Cases'
>>   <draft-ietf-conex-concepts-uses-04.txt>  as an Informational RFC
>>
>> The IESG plans to make a decision in the next few weeks, and solicits
>> final comments on this action. Please send substantive comments to the
>> ietf@ietf.org mailing lists by 2012-04-12. Exceptionally, comments may be
>> sent to iesg@ietf.org instead. In either case, please retain the
>> beginning of the Subject line to allow automated sorting.
>>
>> Abstract
>>
>>
>>    This document provides the entry point to the set of documentation
>>    about the Congestion Exposure (ConEx) protocol.  It explains the
>>    motivation for including a ConEx marking at the IP layer: to expose
>>    information about congestion to network nodes.  Although such
>>    information may have a number of uses, this document focuses on how
>>    the information communicated by the ConEx marking can serve as the
>>    basis for significantly more efficient and effective traffic
>>    management than what exists on the Internet today.
>>
>>
>>
>>
>> The file can be obtained via
>> http://datatracker.ietf.org/doc/draft-ietf-conex-concepts-uses/
>>
>> IESG discussion can be tracked via
>> http://datatracker.ietf.org/doc/draft-ietf-conex-concepts-uses/ballot/
>>
>>
>> No IPR declarations have been submitted directly on this I-D.
> Didn't Mr Briscoe just email that there was a BT IPR claim against
> this ID, related to re-ECN work he did/does for BT?
>
>> _______________________________________________
>> conex mailing list
>> conex@ietf.org
>> https://www.ietf.org/mailman/listinfo/conex
> _______________________________________________
> conex mailing list
> conex@ietf.org
> https://www.ietf.org/mailman/listinfo/conex
>