Re: [Lime] IETF96 LIME *Draft* minutes

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Sat, 23 July 2016 22:52 UTC

Return-Path: <cpignata@cisco.com>
X-Original-To: lime@ietfa.amsl.com
Delivered-To: lime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40FC212D771 for <lime@ietfa.amsl.com>; Sat, 23 Jul 2016 15:52:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.808
X-Spam-Level:
X-Spam-Status: No, score=-15.808 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.287, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 Ycd0YjQZ44Id for <lime@ietfa.amsl.com>; Sat, 23 Jul 2016 15:52:23 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 350BC12D0CF for <lime@ietf.org>; Sat, 23 Jul 2016 15:52:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4664; q=dns/txt; s=iport; t=1469314343; x=1470523943; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=0873Ktb0We6EVIPjUY853JQweB9kj0vNJcm/9Ct2j9g=; b=V/SEFJicS0lbCQS6axwXDKoBBt4uC2BnE2+ZIPZ2bOZrRCNXCprsvq3/ 52RI11j70TU5ayLaAIthX70abR2aSt68whdfCfwsyzUBx7uB5e3Rzwiys Ksz50Dp2AlSS3knLBtqHauqeJJtIJIMqJcYp5GQCC7GdI1BKbURBfuCv8 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AQAgAr9JNX/4YNJK1dgz9WfAa4XYF8I4V5AhyBDDgUAQEBAQEBAV0nhFwBAQQBAQEbBhE6CwUHBAIBCBEEAQEBAgIjAwICAiULFAEICAEBBA4FiCgIDqpmjSkBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBYEBhSmBeIJVhEAXgmorgi8Fk2SFQgGObYFshFmDMYVFkCABHjaCCxyBTG4Bhmp/AQEB
X-IronPort-AV: E=Sophos;i="5.28,411,1464652800"; d="scan'208";a="129222981"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 23 Jul 2016 22:52:22 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id u6NMqMgL007626 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sat, 23 Jul 2016 22:52:22 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sat, 23 Jul 2016 18:52:21 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Sat, 23 Jul 2016 18:52:21 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Adrian Farrel <adrian@olddog.co.uk>
Thread-Topic: [Lime] IETF96 LIME *Draft* minutes
Thread-Index: AdHkEIFKt1W+1kTlRFCWOhFu3heYgQBReNqA
Date: Sat, 23 Jul 2016 22:52:21 +0000
Message-ID: <F87B94C5-357D-45B1-B8B4-8A4CA89C44AD@cisco.com>
References: <0a4901d1e410$d6fe1340$84fa39c0$@olddog.co.uk>
In-Reply-To: <0a4901d1e410$d6fe1340$84fa39c0$@olddog.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.61.165.229]
Content-Type: text/plain; charset="utf-8"
Content-ID: <99065CB909984C4B8CB6E7F9AA777D06@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lime/VvIXAG7GDL73WgJCk7TlRtLC2kE>
Cc: "lime@ietf.org" <lime@ietf.org>
Subject: Re: [Lime] IETF96 LIME *Draft* minutes
X-BeenThere: lime@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Layer Independent OAM Management in Multi-Layer Environment \(LIME\) discussion list." <lime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lime>, <mailto:lime-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lime/>
List-Post: <mailto:lime@ietf.org>
List-Help: <mailto:lime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lime>, <mailto:lime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jul 2016 22:52:25 -0000

Hi Adrian,

Thanks for the note, please see inline.

> On Jul 22, 2016, at 1:01 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
> 
> Hi Carlos,
> 
> I read the minutes (unable to be in the room for the meeting).

We missed you at the meeting.

> 
> Looking at the data tracker I see for draft-kumar-lime-yang-connectionless-oam
>> 2016-03-02 00 Carlos Pignataro IETF WG state changed to Candidate for WG Adoption 
> 
> I note from the minutes that you seem to be "close" to taking this to the list as a question, and I wonder if you could explain the delay. Is there a different document that might be a candidate? Is there a question about whether this is in scope of the charter? Has anyone suggested that the document is so badly broken that the WG cannot fix it?
> 
> My concerns are: 
> - If the document is outside the WG, the WG has no significant ability to
>   influence the content. Once it is a WG document, the WG can dictate
>   the content.
> - Continued delay in adopting the document is reducing the interest and
>   enthusiasm for the work as people wonder what the point is if there 
>   is never going to be a WG draft.

Noted with agreement. 

Coming from Berlin, Ron and I have a number of actions, and calling for adoption of draft-kumar-lime-yang-connectionless-oam is indeed at the very top of the priority list.

Answering your questions, this document is clearly within charter, and there is no different document as a candidate. The document has steadily been increasing in quality, and although there were some areas that were actively discussed and some were presented as potential showstoppers, my sense of the WG is there’s convergence, interest, and energy. In fact, we dedicated an entire interim meeting before Berlin to collective work and real-time edit.

But coming back, indeed, high time for a call for the WG adoption of this document. I see your concerns, but in my view, those did not realize (but they might if we delay much more).

> 
> So I would like to call on you and Ron to move ahead rapidly and adopt this document so that we can all work on it and turn it into a quality RFC.
> 
> [Obviously, it is up to you how you run the WG, but when something is clearly a WG deliverable and when there is a single candidate draft, you are within the rules to simply adopt it leaving the WG to work on the content rather than to debate the process.]
> 

I don’t think the WG debated the process, the focus has been on content.

Thanks!

— Carlos.

> Thanks,
> Adrian
> 
>> -----Original Message-----
>> From: Lime [mailto:lime-bounces@ietf.org] On Behalf Of Carlos Pignataro
>> (cpignata)
>> Sent: 22 July 2016 01:52
>> To: lime@ietf.org
>> Subject: [Lime] IETF96 LIME *Draft* minutes
>> 
>> LIME,
>> 
>> Thank you for a very productive meeting in Berlin!
>> 
>> Please find below our *draft* meeting minutes, with many thanks to Ignas
>> Bagdonas for very detailed and clear notes!
>> 
>> https://www.ietf.org/proceedings/96/minutes/minutes-96-lime
>> 
>> Please send any corrections to the list.
>> 
>> You can also find the full meeting proceedings at
>> https://www.ietf.org/proceedings/96/lime.html
>> 
>> Thanks,
>> 
>> — Carlos.
>> 
>> _______________________________________________
>> Lime mailing list
>> Lime@ietf.org
>> https://www.ietf.org/mailman/listinfo/lime
>