Re: [lisp] [EXTENDED] draft-saucez-lisp-impact-07 - Call for WG Adoption

Fabio Maino <fmaino@cisco.com> Tue, 23 December 2014 16:06 UTC

Return-Path: <fmaino@cisco.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 080381A90D3 for <lisp@ietfa.amsl.com>; Tue, 23 Dec 2014 08:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 R02A6VX2lYF7 for <lisp@ietfa.amsl.com>; Tue, 23 Dec 2014 08:06:24 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37B5A1A90DB for <lisp@ietf.org>; Tue, 23 Dec 2014 08:06:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3043; q=dns/txt; s=iport; t=1419350783; x=1420560383; h=message-id:date:from:mime-version:to:subject:references: in-reply-to:content-transfer-encoding; bh=yg/fdPdfo9AzezarvC8h57EobQzVYcVY2XrJ4cJs3v0=; b=HxATNN0ybLqqjWQnzg89+5Y83MallRn+Ry4XtA42fKMDs6+7iJEpS0Jg aOE1Z9PWn6xs2LocMpzqoBS1hY0ztrWutVQfBLy6LF1+GgGSdB6oHySyj MUd/j6vxrcYfP5jE0APAWlfN7QBZlVE26OYb2A4Y5AOtFFShw0TptR9Ez k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AjMFALeSmVStJA2I/2dsb2JhbABbgwZSWIMEwzIKhXACgRkWAQEBAQF9hA0BAQQBAQEaBg8BBTYKEQsYAgIFFggDAgIJAwIBAgEVHxETBgIBAYgoDbhJlgIBAQEBBgEBAQEaBIEhjliCaIFBBYlKgnOFFoU0gQ2CZYISiBGDOSKEDx0xgkMBAQE
X-IronPort-AV: E=Sophos;i="5.07,632,1413244800"; d="scan'208";a="107842459"
Received: from alln-core-3.cisco.com ([173.36.13.136]) by alln-iport-1.cisco.com with ESMTP; 23 Dec 2014 16:06:10 +0000
Received: from [10.24.167.120] ([10.24.167.120]) by alln-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sBNG68Wt030826 for <lisp@ietf.org>; Tue, 23 Dec 2014 16:06:09 GMT
Message-ID: <549992F9.7090004@cisco.com>
Date: Tue, 23 Dec 2014 08:06:17 -0800
From: Fabio Maino <fmaino@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: lisp@ietf.org
References: <2529C978-FA62-47B0-A223-0B85276DC2D3@gigix.net> <40D65A23-0FB0-4D1B-BC87-367AE8367541@gigix.net> <549834F6.1090609@joelhalpern.com>
In-Reply-To: <549834F6.1090609@joelhalpern.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/0H2gtEN1mg9bdwQh4aolGjDiPoo
Subject: Re: [lisp] [EXTENDED] draft-saucez-lisp-impact-07 - Call for WG Adoption
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Dec 2014 16:06:31 -0000

I support option 1.

Fabio

On 12/22/14, 7:12 AM, Joel M. Halpern wrote:
> To amplify Luigi's comment, we have several choices:
> 1) We can use this document as the basis for the working group action 
> to address the milestone.
> 2) We can use something else as a basis for working group action to 
> address the milestone.
> 3) We can go fight about whether this matters because we don't want to 
> do this.
>
> If you like option (1), tell us you want the document adopted.
> If you like option (2), please say so and give us some idea of what 
> "different" looks like.  Best if you offer to provide a draft by a 
> date, but even just a paragraph or two on what "different" is would 
> help us understand your opposition.
> If you like (3), please explain.  That path seems likely to waste more 
> time than producing a good document.  Particularly since we have what 
> looks to the chairs like a very good start on this deliverable.
>
> Speak up, please.
>
> Yours,
> Joel
>
> On 12/22/14 10:08 AM, Luigi Iannone wrote:
>> Hi All,
>>
>> the two weeks have elapsed since the beginning of the WG Adoption Call
>>   for draft-saucez-lisp-impact-07.
>>
>> There was actually very little reaction on this call.
>>
>> Silence does not help to make a decision, one way or another.
>>
>> Recall that our charter explicitly state that we will work on "A
>> description of the impacts of LISP”.
>>
>> The WG Adoption Call is extended for another two weeks (until 5th
>> January 2015).
>>
>> Please take this opportunity to express your opinion on this document.
>>
>> Thanks
>>
>> Luigi & Joel
>>
>>> On 04 Dec 2014, at 12:27, Luigi Iannone <ggx@gigix.net
>>> <mailto:ggx@gigix.net>> wrote:
>>>
>>> Hi All,
>>>
>>> During the 91st IETF authors of the draft-saucez-lisp-impact-07
>>> [https://tools.ietf.org/html/draft-saucez-lisp-impact-07]
>>> asked for WG adoption. Meeting participants expressed consensus on
>>> adoption.
>>>
>>> This message begins the two weeks call for WG adoption to confirm the
>>> meeting outcome.
>>> The call ends on  December 19th 2014.
>>>
>>> Please respond to the LISP mailing list with any statements of
>>> approval or disapproval.
>>>
>>> Recall that:
>>>
>>> - This is not WG Last Call. The document is not final, and the WG is
>>> expected to
>>>   modify the document’s content until there is WG consensus that the
>>> content is solid.
>>>   Therefore, please don’t oppose adoption just because you want to see
>>> changes to its content.
>>>
>>> - If you have objections to adoption of the document, please state
>>> your reasons why,
>>>   and explain what it would take to address your concerns.
>>>
>>> - If you have issues with the content, by all means raise those issues
>>> and we can
>>>   begin a dialog about how best to address them.
>>> Luigi and Joel
>>>
>>>
>>
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp