Re: [lisp] [ERRATA] Call for WG Adoption of Vendor Specific LCAF [draft-rodrigueznatal-lisp-vendor-lcaf-00.txt]

"Marc Portoles Comeras (mportole)" <mportole@cisco.com> Thu, 27 July 2017 14:15 UTC

Return-Path: <mportole@cisco.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2816D131C96; Thu, 27 Jul 2017 07:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 yIYoN9WWFcWV; Thu, 27 Jul 2017 07:15:48 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 147B3131C84; Thu, 27 Jul 2017 07:15:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10758; q=dns/txt; s=iport; t=1501164948; x=1502374548; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=3kgd2d2ros+ODbTfs46t3BG6bxeRpVBkwInMpkG8xI4=; b=DkybbTd3TY3662BzBG/tyqQA6SvkKY08AXqmFg2Cjfd1n9CYPIoEAyTV mBt3eUaBJE0b3eh7fcD2FT/m0fL7mdBT5gfIjszraIeKtru2puzknMN/D Pd/aLVzVkh8jPZyaYVpH5uhPrvEqriUz60BqDtcEEpyuLcCJfLEmWWtXC U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DAAADz9HlZ/5FdJa1cGQEBAQEBAQEBAQEBBwEBAQEBgm9rZG0nB44GkWGQW4UvghIshRsCGoNIPxgBAgEBAQEBAQFrKIUYAQEBAQMdBksLEAIBCA4DAwECJAQDAgICMBQJCAIEAQ0FiUtkEK93giYnixkBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYMoglOCWyuCeYUTFoJdMIIxBZ9mAodNjFaCDIVSil6VcQEfOIEKdxVJEgGFOIFOdohygQ4BAQE
X-IronPort-AV: E=Sophos;i="5.40,419,1496102400"; d="scan'208,217";a="457318133"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Jul 2017 14:15:47 +0000
Received: from XCH-RTP-014.cisco.com (xch-rtp-014.cisco.com [64.101.220.154]) by rcdn-core-9.cisco.com (8.14.5/8.14.5) with ESMTP id v6REFkLr001744 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 27 Jul 2017 14:15:47 GMT
Received: from xch-rtp-011.cisco.com (64.101.220.151) by XCH-RTP-014.cisco.com (64.101.220.154) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 27 Jul 2017 10:15:46 -0400
Received: from xch-rtp-011.cisco.com ([64.101.220.151]) by XCH-RTP-011.cisco.com ([64.101.220.151]) with mapi id 15.00.1210.000; Thu, 27 Jul 2017 10:15:46 -0400
From: "Marc Portoles Comeras (mportole)" <mportole@cisco.com>
To: Luigi Iannone <ggx@gigix.net>, LISP mailing list list <lisp@ietf.org>
CC: "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>
Thread-Topic: [lisp] [ERRATA] Call for WG Adoption of Vendor Specific LCAF [draft-rodrigueznatal-lisp-vendor-lcaf-00.txt]
Thread-Index: AQHTBgCqb15ODnNNMkGNnRpxQcwyOKJnh2eA
Date: Thu, 27 Jul 2017 14:15:46 +0000
Message-ID: <6781F849-7E88-40F9-B29C-264819871E37@cisco.com>
References: <12777128-3072-493F-AA8B-247C884599C1@gigix.net> <7AFC6BD1-5E44-4146-AF97-DF0EBE340B78@gigix.net>
In-Reply-To: <7AFC6BD1-5E44-4146-AF97-DF0EBE340B78@gigix.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1d.0.161209
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.24.75.92]
Content-Type: multipart/alternative; boundary="_000_6781F8497E8840F9B29C264819871E37ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/499Tx3DBfWAEKQIUpvoiQpXPtbE>
Subject: Re: [lisp] [ERRATA] Call for WG Adoption of Vendor Specific LCAF [draft-rodrigueznatal-lisp-vendor-lcaf-00.txt]
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 27 Jul 2017 14:15:50 -0000

I support WG adoption of draft-rodrigueznatal-lisp-vendor-lcaf

Marc

From: lisp <lisp-bounces@ietf.org> on behalf of Luigi Iannone <ggx@gigix.net>
Date: Wednesday, July 26, 2017 at 4:16 AM
To: LISP mailing list list <lisp@ietf.org>
Cc: "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>
Subject: [lisp] [ERRATA] Call for WG Adoption of Vendor Specific LCAF [draft-rodrigueznatal-lisp-vendor-lcaf-00.txt]

The call ends August 10th 2017 !

Luigi

On 26 Jul 2017, at 11:41, Luigi Iannone <ggx@gigix.net<mailto:ggx@gigix.net>> wrote:

Hi All,

During the 99th IETF authors of the document draft-rodrigueznatal-lisp-vendor-lcaf-00.txt
[https://tools.ietf.org/html/draft-rodrigueznatal-lisp-vendor-lcaf-00]
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  August 3rd 2017.

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