Re: [ippm] Calls for adoption as WG items

Joachim Fabini <Joachim.Fabini@tuwien.ac.at> Tue, 08 July 2014 06:42 UTC

Return-Path: <Joachim.Fabini@tuwien.ac.at>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2355C1B2A69 for <ippm@ietfa.amsl.com>; Mon, 7 Jul 2014 23:42:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.682
X-Spam-Level:
X-Spam-Status: No, score=-3.682 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651] 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 dImapOmLnN6t for <ippm@ietfa.amsl.com>; Mon, 7 Jul 2014 23:42:21 -0700 (PDT)
Received: from mail1.zserv.tuwien.ac.at (mail1.zserv.tuwien.ac.at [128.130.35.37]) by ietfa.amsl.com (Postfix) with ESMTP id BEA031B2A66 for <ippm@ietf.org>; Mon, 7 Jul 2014 23:42:20 -0700 (PDT)
Received: from [128.131.67.239] (jason.nt.tuwien.ac.at [128.131.67.239]) (authenticated bits=0) by mail1.zserv.tuwien.ac.at (8.13.8/8.13.8) with ESMTP id s686gIG4013239 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 8 Jul 2014 08:42:18 +0200
Message-ID: <53BB92C5.1080400@tuwien.ac.at>
Date: Tue, 08 Jul 2014 08:42:13 +0200
From: Joachim Fabini <Joachim.Fabini@tuwien.ac.at>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Brian Trammell <ietf@trammell.ch>, ippm@ietf.org
References: <20140529194155.17884.67924.idtracker@ietfa.amsl.com> <47EC9EAE-25A9-4E0F-B5F9-10593A4DDD0C@trammell.ch> <CD6C53A6-9219-48E9-A03E-69E6786F4FAE@trammell.ch> <017EE38A-2B06-429F-AAC9-27F45932AD5C@trammell.ch>
In-Reply-To: <017EE38A-2B06-429F-AAC9-27F45932AD5C@trammell.ch>
X-Enigmail-Version: 1.6
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ippm/efJoe2PTc5DGk8F3r2m9ZX-CKNc
Subject: Re: [ippm] Calls for adoption as WG items
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Jul 2014 06:42:24 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Brian, IPPM,

Having finally read (1) and (2) I support adoption of these
drafts/milestones. I will submit a summary of my review to the list
for discussion within the next week(s) and I plan to contribute to the
review process of these two documents in the future.

best regards
Joachim




On 02.07.2014 11:30, Brian Trammell wrote:
> Greetings, IPPM,
> 
> A gentle reminder: We would like very much to have discussion on
> adoption completed before the Toronto meeting, so we can spend face
> to face time on the documents themselves. And we cannot adopt
> drafts as Working Group items for which there is not a strong
> demonstration of support and commitment to read, review, and
> improve the drafts.
> 
> So, please see last week's call for adoption notice, consider
> whether you support adoption of the named drafts, and whether you
> can commit to review them.
> 
> The deadline for this call for adoption is, as before, end of day
> Thursday 10 July 2014.
> 
> Many thanks and best regards,
> 
> Brian Trammell, as co-chair.
> 
> On 24 Jun 2014, at 16:17, Brian Trammell <ietf@trammell.ch> wrote:
> 
>> Greetings, IPPM,
>> 
>> This is a call for adoption for four new milestones under the
>> current IPPM charter.
>> 
>> (1) Submit a draft updating RFC2679 based on testing and
>> implementation experience (RFC 6808) to the IESG as Proposed
>> Standard (under consideration for this milestone is
>> draft-morton-ippm-2679-bis-04)
>> 
>> (2) Submit a draft updating RFC2680 based on testing and
>> implementation experience (draft-ietf-ippm-testplan-rfc2680-05)
>> to the IESG as Proposed Standard (under consideration for this
>> milestone is draft-morton-ippm-2679-bis-04)
>> 
>> (3) Submit a draft adding DSCP and ECN monitoring to TWAMP to the
>>  IESG as Proposed Standard (under consideration for this
>> milestone is draft-hedin-ippm-type-p-monitor-03)
>> 
>> (4) Submit a draft adding a UDP Checksum Trailer to OWAMP and
>> TWAMP to the IESG as Informational (under consideration for this
>> milestone is draft-mizrahi-ippm-checksum-trailer-00)
>> 
>> For each draft, please indicate the following to the list at
>> ippm@ietf.org
>> 
>> (a) whether you support the addition of the milestone and the
>> adoption of the draft as a WG item to fulfill that milestone (b)
>> whether you have read the draft (c) whether you pledge to review
>> the draft during the WG process.
>> 
>> This call for adoption will last until Thursday 10 July 2014.
>> 
>> Many thanks, best regards,
>> 
>> Brian
>> 
>> On 02 Jun 2014, at 18:07, Brian Trammell <ietf@trammell.ch>
>> wrote:
>> 
>>> Greetings, IPPM,
>>> 
>>> Thanks and congratulations to the authors on the approval of
>>> our first draft from the "new" (March 2013) charter!
>>> 
>>> As we're moving forward in our charter, it's time to consider
>>> adopting new drafts.
>>> 
>>> I've seen implicit requests for a call for adoption for the
>>> following two drafts, which were not adopted in Orlando because
>>> we wanted to see if 2330-update would change their scope
>>> significantly:
>>> 
>>> draft-morton-ippm-2679-bis-04 draft-morton-ippm-2680-bis-02
>>> 
>>> We have at least one explicit request for a call for adoption:
>>> 
>>> draft-hedin-ippm-type-p-monitor-03
>>> 
>>> If there are other documents which you would like to have
>>> considered for adoption as IPPM WG items in the next round
>>> under the present charter, please notify the chairs at
>>> ippm-chairs@tools.ietf.org by Friday, June 6th; we'll run the
>>> call for adoption after that.
>>> 
>>> Thanks, cheers,
>>> 
>>> Brian (as chair)
>>> 
>>> 
>>> Begin forwarded message:
>>> 
>>>> From: The IESG <iesg-secretary@ietf.org> Subject: Document
>>>> Action: 'Advanced Stream and Sampling Framework for IPPM' to
>>>> Informational RFC (draft-ietf-ippm-2330-update-05.txt) Date:
>>>> 29 May 2014 21:41:55 GMT+2 Resent-To: bill@wjcerveny.com,
>>>> ietf@trammell.ch, To: IETF-Announce <ietf-announce@ietf.org> 
>>>> Cc: RFC Editor <rfc-editor@rfc-editor.org>, ippm mailing list
>>>> <ippm@ietf.org>, ippm chair <ippm-chairs@tools.ietf.org>
>>>> 
>>>> The IESG has approved the following document: - 'Advanced
>>>> Stream and Sampling Framework for IPPM' 
>>>> (draft-ietf-ippm-2330-update-05.txt) as Informational RFC
>>>> 
>>>> This document is the product of the IP Performance Metrics
>>>> Working Group.
>>>> 
>>>> The IESG contact persons are Spencer Dawkins and Martin
>>>> Stiemerling.
>>>> 
>>>> A URL of this Internet Draft is: 
>>>> http://datatracker.ietf.org/doc/draft-ietf-ippm-2330-update/
>>>> 
>>>> 
>>>> 
>>>> 
>>>> 
>>>> Technical Summary
>>>> 
>>>> To obtain repeatable results in modern networks, test
>>>> descriptions need an expanded stream parameter framework that
>>>> also augments aspects specified as Type-P for test packets.
>>>> This memo updates the IP Performance Metrics (IPPM)
>>>> Framework, RFC 2330, with advanced considerations for
>>>> measurement methodology and testing. The existing framework
>>>> mostly assumes deterministic connectivity, and that a single
>>>> test stream will represent the characteristics of the path
>>>> when it is aggregated with other flows.  Networks have
>>>> evolved and test stream descriptions must evolve with them,
>>>> otherwise unexpected network features may dominate the
>>>> measured performance. This memo describes new stream
>>>> parameters for both network characterization and support of
>>>> application design using IPPM metrics.
>>>> 
>>>> Working Group Summary
>>>> 
>>>> This draft was first introduced to the working group in
>>>> October 2012. Support for the draft was indicated at meetings
>>>> with no dissent.
>>>> 
>>>> Document Quality
>>>> 
>>>> As an update to the IPPM Framework, this document adds new
>>>> and updated considerations for stream parameters.
>>>> 
>>>> The document shepherd reviewed the document as a “-02” draft
>>>> and reviewed the changes which constitute “-03” and “-04”.
>>>> 
>>>> As documented, other topics in the IPPM Framework which might
>>>> be updated or augmented are deferred to future work.  This 
>>>> includes the topics of passive and various forms of of hybrid
>>>>  active/passive measurements.
>>>> 
>>>> Personnel
>>>> 
>>>> The document shepherd was Bill Cerveny. The responsible area
>>>> director is Spencer Dawkins.
>>> 
>>> _______________________________________________ ippm mailing
>>> list ippm@ietf.org https://www.ietf.org/mailman/listinfo/ippm
>> 
>> _______________________________________________ ippm mailing
>> list ippm@ietf.org https://www.ietf.org/mailman/listinfo/ippm
> 
> 
> 
> _______________________________________________ ippm mailing list 
> ippm@ietf.org https://www.ietf.org/mailman/listinfo/ippm
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTu5LFAAoJEKCP3BPvRqfSawMH/2S+os0oHNt6MrCWIY9Tbpas
9nu/chFiah4vKNVbak4n8ac3TmZZtGw0QIyL0dev1ZssUwUjArlZrzET7IoqnLr1
lbVFoPA0tyuR+AH0XaBCDB/CepbYwOq/L7IpUKAY0hVVZtuaXQcZL5/JI1LsxK0o
2RrQOiClLGl/ihaPyuLibEl8C3GrJIV29IN/bp3S2jk4YyymI8nebJJSn7vS4xAf
IlB31d2F201PfiM25RKKyZEIZNbUtpQ1nbrImZCdhz5zRSCENad8z57Vki3vZ14P
jvSWgz0HIKA3jRyhn/mv7fFjRL9H6FuK6y2gKACCKzYo5QvX4odSgqF6pkVzuw4=
=xw7U
-----END PGP SIGNATURE-----