Re: [ippm] Adoption call for draft-mizrahi-ippm-ioam-flags Re: Regarding draft-mizrahi-ippm-ioam-flags

Tommy Pauly <tpauly@apple.com> Fri, 26 July 2019 14:12 UTC

Return-Path: <tpauly@apple.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 11F881200F1; Fri, 26 Jul 2019 07:12:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.com
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 KNjjbBwasyra; Fri, 26 Jul 2019 07:12:39 -0700 (PDT)
Received: from nwk-aaemail-lapp01.apple.com (nwk-aaemail-lapp01.apple.com [17.151.62.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26C471200EC; Fri, 26 Jul 2019 07:12:39 -0700 (PDT)
Received: from pps.filterd (nwk-aaemail-lapp01.apple.com [127.0.0.1]) by nwk-aaemail-lapp01.apple.com (8.16.0.27/8.16.0.27) with SMTP id x6QEBSSW006198; Fri, 26 Jul 2019 07:12:35 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : content-type : mime-version : subject : from : in-reply-to : date : cc : content-transfer-encoding : message-id : references : to; s=20180706; bh=0SRgPc0SPm1y9Pm41dB3pHwtaGGIs6uVypmTGmvRLbE=; b=lUYQjY+betqYm00JXqwD99fckvzPk8CmMftT6k+7qBFSJcwKYZm2BiFOBUgkZSnr7Dv5 aLNPCNoc/5g+1QbV5OyYyIjNk/jczhayRolhpNGi325N0jaJuoDcW74HzP9PskxlSHv/ y8IR8Ww+81B5SjjDQIdAyfSStOhKhjY6nAabG+lqo76dTpam9OZ1kN4C6uwbsT7hebff v5EXrTyTGG8yktOupRe1T52Wv3o4k9AWxlhL0Whx8+zkX7/t97ybJm1EvCO9TGvXnh+p IUaQ4xbri6PFQFqdJXcAkCZBjrI5FbcPIRY5mUYcbBnTJgjruHHoy7K0M4SSp302MuZ9 yw==
Received: from ma1-mtap-s01.corp.apple.com (ma1-mtap-s01.corp.apple.com [17.40.76.5]) by nwk-aaemail-lapp01.apple.com with ESMTP id 2tymes9dk2-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Fri, 26 Jul 2019 07:12:35 -0700
Received: from nwk-mmpp-sz10.apple.com (nwk-mmpp-sz10.apple.com [17.128.115.122]) by ma1-mtap-s01.corp.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPS id <0PV90046964SQT00@ma1-mtap-s01.corp.apple.com>; Fri, 26 Jul 2019 07:12:32 -0700 (PDT)
Received: from process_milters-daemon.nwk-mmpp-sz10.apple.com by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) id <0PV9009005WZGC00@nwk-mmpp-sz10.apple.com>; Fri, 26 Jul 2019 07:12:31 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 3de5f1eb6222ee3271b312a383cb6138
X-Va-E-CD: bb48c2d760d9d5acb5a59acf663c18ea
X-Va-R-CD: c7fc89ff8e4d841ba012a74c99d2f8d0
X-Va-CD: 0
X-Va-ID: d6d23363-8042-4e6d-aa45-7bc6383696fa
X-V-A:
X-V-T-CD: 3de5f1eb6222ee3271b312a383cb6138
X-V-E-CD: bb48c2d760d9d5acb5a59acf663c18ea
X-V-R-CD: c7fc89ff8e4d841ba012a74c99d2f8d0
X-V-CD: 0
X-V-ID: f8a99303-8713-48f4-bfc4-24b89639c794
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-07-26_10:,, signatures=0
Received: from [17.235.29.186] by nwk-mmpp-sz10.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May 7 2019)) with ESMTPSA id <0PV900B8T63IOU20@nwk-mmpp-sz10.apple.com>; Fri, 26 Jul 2019 07:11:44 -0700 (PDT)
Sender: tpauly@apple.com
Content-type: text/plain; charset=utf-8
MIME-version: 1.0 (Mac OS X Mail 12.4 \(3445.104.2\))
From: Tommy Pauly <tpauly@apple.com>
In-reply-to: <CF18FEAC-D27B-4F56-BBAD-C6A52AEA31B1@broadcom.com>
Date: Fri, 26 Jul 2019 10:11:37 -0400
Cc: "Brian Trammell (IETF)" <ietf@trammell.ch>, Greg Mirsky <gregimirsky@gmail.com>, IPPM Chairs <ippm-chairs@ietf.org>, IETF IPPM WG <ippm@ietf.org>
Content-transfer-encoding: quoted-printable
Message-id: <0C653836-3404-4546-A8F4-CE14FF9B74F2@apple.com>
References: <CA+RyBmVnkMFEQv=Hr3y9OD09+_vocHRgnGQnLwEVO=yuTcptEQ@mail.gmail.com> <EAB5C70D-A160-423E-84FE-3CE7AC079168@trammell.ch> <CF18FEAC-D27B-4F56-BBAD-C6A52AEA31B1@broadcom.com>
To: Jai Kumar <jai.kumar@broadcom.com>
X-Mailer: Apple Mail (2.3445.104.2)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-07-26_10:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/VpdKgpzR69MolbhwZ9M0UT5D34Y>
Subject: Re: [ippm] Adoption call for draft-mizrahi-ippm-ioam-flags Re: Regarding draft-mizrahi-ippm-ioam-flags
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 26 Jul 2019 14:12:41 -0000

Any document adopted by the working group can and will receive edits from the group as a whole. Feel free to send reviews now, but the primary question at hand here is if IPPM as a group believes that the mechanism that this document aims to add is something the group should work on, and that this document is a good starting place for the work.

Thanks!
Tommy

> On Jul 25, 2019, at 4:09 PM, Jai Kumar <jai.kumar@broadcom.com> wrote:
> 
> Hello Chairs,
> 
> What is the procedure for requesting edits.
> 
> Can it happen after the adoption call or requests need to be made before.
> 
> -Jai
> 
> On 7/25/19, 11:07 AM, "ippm on behalf of Brian Trammell (IETF)" <ippm-bounces@ietf.org on behalf of ietf@trammell.ch> wrote:
> 
>    hi Greg,
> 
>    Thanks for the feedback; absolutely, we can do this the normal way. Authors: let's do a normal two-week adoption call for this document before publishing the update.
> 
>    This adoption call starts now.
> 
>    IPPM, please respond to this message with an indication to the mailing list of your support for adopting draft-mizrahi-ippm-ioam-flags as a working group document, in partial fulfillment of our charter milestone "submit a Standards Track draft on inband OAM based measurement methodologies to the IESG" (obviously, depending on how many documents we end up sending to the IESG, we may have to change the plurality of this milestone). If you do not support this, please send a message to the list explaining why.
> 
>    Thanks, cheers,
> 
>    Brian (as IPPM co-chair)
> 
> 
>> On 25 Jul 2019, at 13:15, Greg Mirsky <gregimirsky@gmail.com> wrote:
>> 
>> Dear Chairs, et al.,
>> I appreciate that editors of draft-ietf-ippm-ioam-data followed on the decision of the WG reached at the meeting in Prague to extract material not directly related to the definition of iOAM data elements from the document. The new draft was presented earlier this week and generated many comments. I feel that it would be right to discuss the draft and its relevance to the charter of the IPPM WG before starting WG adoption poll.
>> 
>> Regards,
>> Greg
> 
>    _______________________________________________
>    ippm mailing list
>    ippm@ietf.org
>    https://www.ietf.org/mailman/listinfo/ippm
> 
> 
>