From nobody Thu Dec 1 13:54:45 2016 Return-Path: X-Original-To: lisp@ietf.org Delivered-To: lisp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B3791294E4; Thu, 1 Dec 2016 13:54:44 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "Stephen Farrell" To: "The IESG" X-Test-IDTracker: no X-IETF-IDTracker: 6.39.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148062928403.2918.8998203874070943286.idtracker@ietfa.amsl.com> Date: Thu, 01 Dec 2016 13:54:44 -0800 Archived-At: Cc: lisp-chairs@ietf.org, draft-ietf-lisp-lcaf@ietf.org, lisp@ietf.org Subject: [lisp] Stephen Farrell's Abstain on draft-ietf-lisp-lcaf-22: (with COMMENT) X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2016 21:54:44 -0000 Stephen Farrell has entered the following ballot position for draft-ietf-lisp-lcaf-22: Abstain When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-lisp-lcaf/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thanks for resolving most of my discuss points. I remain unconvinced about the wisdom of including section 5, hence my abstain ballot. From nobody Thu Dec 1 14:07:12 2016 Return-Path: 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 872DE1293F2; Thu, 1 Dec 2016 14:07:05 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 8KAQYUUvjN6B; Thu, 1 Dec 2016 14:07:03 -0800 (PST) Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 18967129982; Thu, 1 Dec 2016 14:07:03 -0800 (PST) Received: by mail-pf0-x242.google.com with SMTP id 144so12458373pfv.0; Thu, 01 Dec 2016 14:07:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dIcnLfG7WG2bqhtEmSvMCqVmmzSJ+Uqq2IRg1aVc38U=; b=p235kz5pJltbKwxuXc6fl2qBLJTRqmAGYQ6XC/PhdlzCJVf3g0QWh4dtrCTkYHHTrb itYekSKRwyt46afebLI/5bPZksUggV4+4Z3oU3cTX4d3jCi/RxpoSm+wLdlsMUqsbGya /Tur8cpprampO27Np20RQA0VPbPNUf0dhY159ASyaJ3/pcmgkAnrPbU7BUxqwGw5mBMV xLNiTYrloP35Bt8ydFGJKQtwhW3+y2NlzBkNcDAyri84G33dIRAm+Pca/XJYTzSBkDA0 VNyqAQB2O5+yjLGCLMVBHOEVfJzenxtq/WrM+kEE60DB0UAdLYjRMea0U9qf+CQVF6mI n+aA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=dIcnLfG7WG2bqhtEmSvMCqVmmzSJ+Uqq2IRg1aVc38U=; b=mTXZvY6KjoG0INo2b/qj2Zx7bhC5O1KgOKAT+pCGivvyflScZXUg+KKVwEsnSJL7M/ 033KQDiVdFAEer0/BBuz0jGjwa3NhGeaC/68EXlYZOgDQwi/xvJSduT/DzjHNQwCfICC Xyl5g/fMau1N1Gp1+IrByrcEf1lweOgrT/w5aighxw0YQmUnM5HRyF2rn445iuhzn/eC G0vROndANuACrjomMD3Nz7W2KmEze5O3w7vAKoir0OeS3SgLuh77wV8VnPc6vmpYp4WA iXhRcr301BIE6QCiDkfmPEZuO1qgxeDQBIUrbX0kR99SRktLne/X+7WuR1XgKjBT1X+4 mm7g== X-Gm-Message-State: AKaTC00sjsFI2egQl+2CKWGDJX7JtQ//de+lr/OaL5Xv9Z6XihGyb5Y6t4IvJT+e1SPBXA== X-Received: by 10.99.61.6 with SMTP id k6mr73176241pga.154.1480630022686; Thu, 01 Dec 2016 14:07:02 -0800 (PST) Received: from [172.20.10.2] ([166.177.249.116]) by smtp.gmail.com with ESMTPSA id f23sm2350375pff.59.2016.12.01.14.07.00 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Dec 2016 14:07:01 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) From: Dino Farinacci In-Reply-To: <148062928403.2918.8998203874070943286.idtracker@ietfa.amsl.com> Date: Thu, 1 Dec 2016 14:06:59 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <148062928403.2918.8998203874070943286.idtracker@ietfa.amsl.com> To: Stephen Farrell X-Mailer: Apple Mail (2.3251) Archived-At: Cc: lisp-chairs@ietf.org, draft-ietf-lisp-lcaf@ietf.org, The IESG , lisp@ietf.org Subject: Re: [lisp] Stephen Farrell's Abstain on draft-ietf-lisp-lcaf-22: (with COMMENT) X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Dec 2016 22:07:06 -0000 Thanks Stephen for time spent on this. You are making LISP better and = certainly more secure. Grateful, Dino > On Dec 1, 2016, at 1:54 PM, Stephen Farrell = wrote: >=20 > Stephen Farrell has entered the following ballot position for > draft-ietf-lisp-lcaf-22: Abstain >=20 > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut = this > introductory paragraph, however.) >=20 >=20 > Please refer to = https://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. >=20 >=20 > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-lisp-lcaf/ >=20 >=20 >=20 > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- >=20 >=20 > Thanks for resolving most of my discuss points. I remain unconvinced > about the wisdom of including section 5, hence my abstain ballot. >=20 >=20 From nobody Fri Dec 2 08:50:12 2016 Return-Path: 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 351D81297AA for ; Fri, 2 Dec 2016 08:50:10 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20150623.gappssmtp.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 XIxIo3rH9d51 for ; Fri, 2 Dec 2016 08:50:08 -0800 (PST) Received: from mail-wj0-x22a.google.com (mail-wj0-x22a.google.com [IPv6:2a00:1450:400c:c01::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 697B91297F3 for ; Fri, 2 Dec 2016 08:50:08 -0800 (PST) Received: by mail-wj0-x22a.google.com with SMTP id qp4so237078360wjc.3 for ; Fri, 02 Dec 2016 08:50:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=VZBYJRB7OiyXdySHPG78w3Oa/hnP0m0QWRaIVC1aBNw=; b=eQKTmAleK2MLnXosQrpUrzMYF7MEs14sRlc+nxzDYzcXmOMgFdS+m9yk88ndX3B95g 0UkW1VIyW5zyL1xe6h15S5g9xcz8LPrXGoOp1GAUWZrdzkrLxvbToAIlbsPETnP0HMl5 sWNQiq9vrxgKA8ChGM7ClnYe0VVwpbEljOB2WEF2sv2puieVJhv1293tpbd/wTSKCQol dilHrIhAQaSCc5FrNZqlmpGkufLf34H8Pq3Ngf6oa9+gxzc1doGdjHN0cOxTVag5B2Ns mt/5c1OGC3oZrk+xJEPDfJ0eHe5MalodUvEiswqK021Tw9C1eosdrGZ50XYWQYbHuazX RPZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=VZBYJRB7OiyXdySHPG78w3Oa/hnP0m0QWRaIVC1aBNw=; b=DTuaTVaMBiZXrLnhdAP3dAeeMdGgQBbzDPxynVFoR530ZvhNtx1ncgixU2I0ENJ3D/ RvZZ42/IYW7kFrG0r+KdbrxvccVO1ynr7EYKg+dnI3oGkad2S8F/9BBryR6E4xhdVHJK c1KQMsRKqIJhPQMip0LiLornbghOhDXfV5FYl7I+Os6DAedmQaxN6b9nLqk5Dla3UYh5 7Nsq09XG2T2QGsVsjvuu93m0nTcrJyt62BepMckHx8/Sa6lseWCaQRBaCb4lbzhKjnWH f0eESSmJGlPf4GGfToQ90ql9BSJFVbxvnmvZJPlAY5KLUuCVpkqKpRXeAx4VmVtAlG5k 7z0w== X-Gm-Message-State: AKaTC005p9CCgpEnrQJ6G7dwbI7CgV3KdiiV1Ht9Z3/SIQ20sma5O36VwRb6LNZYfrAL+w== X-Received: by 10.194.82.163 with SMTP id j3mr45753535wjy.232.1480697406562; Fri, 02 Dec 2016 08:50:06 -0800 (PST) Received: from ?IPv6:2a01:e35:1381:3430:c9ed:cb46:e3be:df59? ([2a01:e35:1381:3430:c9ed:cb46:e3be:df59]) by smtp.gmail.com with ESMTPSA id d65sm4086500wmh.11.2016.12.02.08.50.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Dec 2016 08:50:05 -0800 (PST) From: Luigi Iannone Message-Id: <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_D28BF77E-8EEB-4C77-B440-165F56155073" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Date: Fri, 2 Dec 2016 17:50:03 +0100 In-Reply-To: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> To: LISP mailing list list References: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> X-Mailer: Apple Mail (2.3251) Archived-At: Cc: lisp-chairs@ietf.org Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 16:50:10 -0000 --Apple-Mail=_D28BF77E-8EEB-4C77-B440-165F56155073 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi All, feedback for this last call has been quite low. For this reason we = decide to extend the last call for another two weeks, ending December = 16th. Please state your opinion on whether this document is ready for = publication. Silence is NOT consensus. Ciao Luigi & Joel > On 17 Nov 2016, at 09:36, Luigi Iannone wrote: >=20 > Hi All, >=20 > The authors of the LISP-Security (LISP-SEC) document = [https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/ = ] asked for WG = Last Call.=20 >=20 > This email starts the usual two weeks WG Last Call, to end December = 1st, 2016. >=20 > Please review this WG document and let the WG know if you agree that = it is ready for handing to the AD. > If you have objections, please state your reasons why, and explain = what it would take to address your concerns. >=20 > Thanks >=20 > Luigi & Joel --Apple-Mail=_D28BF77E-8EEB-4C77-B440-165F56155073 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi All,

feedback for this last call has been quite low. For this = reason we decide to extend the last call for another two weeks, ending = December 16th.

Please state your opinion on whether this document is ready = for publication.

Silence is NOT consensus.

Ciao

Luigi & Joel
On = 17 Nov 2016, at 09:36, Luigi Iannone <ggx@gigix.net> wrote:

Hi All,

The authors of the LISP-Security (LISP-SEC) document [https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/] = asked for WG Last Call. 

This email starts the usual two weeks = WG Last Call, to end December  1st, 2016.

Please review this WG = document and let the WG know if you agree that it is ready for handing = to the AD.
If you have objections, please = state your reasons why, and explain what it would take to address your = concerns.

Thanks

Luigi & = Joel

= --Apple-Mail=_D28BF77E-8EEB-4C77-B440-165F56155073-- From nobody Fri Dec 2 08:52:39 2016 Return-Path: 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 EC4381295E4 for ; Fri, 2 Dec 2016 08:52:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20150623.gappssmtp.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 BsbWibTGLbq6 for ; Fri, 2 Dec 2016 08:52:35 -0800 (PST) Received: from mail-wj0-x232.google.com (mail-wj0-x232.google.com [IPv6:2a00:1450:400c:c01::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE51B1296E4 for ; Fri, 2 Dec 2016 08:52:32 -0800 (PST) Received: by mail-wj0-x232.google.com with SMTP id qp4so237135175wjc.3 for ; Fri, 02 Dec 2016 08:52:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Ul93YKwDIcpNiAgQCyXAgHb3S0NpJv2ylH05CvWahaY=; b=qvORBcqVG4Bpu8vmpdiaSid+clitO0naIznAd0R8n7KFOFOb13Lzp3IRpdHJ2Gegvv GuVIi6UKwSxzLWpMX2i5/ZBj2CatMvW+MU6ocfAYOlF80Zpjr5y0jndBssWHSnfxyfAa E4nnMXf6KDKmyoJJqZM27fUWJsrq2f9dXN8j7KuHPAhHdNeLSO3HlIQeg/+RD5TIrAF/ 7+5kAv5cWXQ49siDn56WuNSp1BWiCsYN/5B+oo6Gjgl85l4omOwGAbnX7igiHFsoGneg jz9TuoEqULUZB5w66GWX8iX3YX2JS8j40n6MsMuxsqjRehgh0ad1bMFbwe4FVZ3uaeMJ qQNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Ul93YKwDIcpNiAgQCyXAgHb3S0NpJv2ylH05CvWahaY=; b=bT6KIVyPFUB8WChk/keS4XB6Vl9r/dH6GoS+xxtxozaBL33J5tNHCW3TSwygCiGb+u Plnhj7MsvyCokxRivY+hknBui2atez6nrtuPc3bWDBgUt+egi0k1aVH3GMYeuVqqePeR oeCF+YgV27GPpi+uIgAN4rH06R/sPM8RzT+0t15kfkKO6J04twSwj61NZHJ7NVe8k2VZ GTKaIRBUbxwkP85IXUmHIkQtjIlGEksL/JFu9MJFKZvXjZr8OzVngcgfcZ+tg3qkD/bV +k7VfkCUZrhw/4ILyAG9cs4scrPLIP+2jfvKDnn9pFdrd2AtvDlk9DhDvWxs4o9wjBRH VX2w== X-Gm-Message-State: AKaTC01jxB787+/i0nL52aJ6qOXEjs/Scw48UqvWTPsYukOOtLD7tZDwGIwHD3NNHiUpmA== X-Received: by 10.194.93.37 with SMTP id cr5mr38699502wjb.95.1480697551047; Fri, 02 Dec 2016 08:52:31 -0800 (PST) Received: from ?IPv6:2a01:e35:1381:3430:c9ed:cb46:e3be:df59? ([2a01:e35:1381:3430:c9ed:cb46:e3be:df59]) by smtp.gmail.com with ESMTPSA id i15sm6468204wjs.16.2016.12.02.08.52.27 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Dec 2016 08:52:29 -0800 (PST) From: Luigi Iannone Message-Id: <63B39785-96E7-4999-B6AB-CA624288514F@gigix.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_1B034532-ABA8-436F-B407-DF6EE60AA49F" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Date: Fri, 2 Dec 2016 17:52:24 +0100 In-Reply-To: <653192D8-E2DD-4741-9882-BBA8ADB8F6C7@gigix.net> To: LISP mailing list list References: <653192D8-E2DD-4741-9882-BBA8ADB8F6C7@gigix.net> X-Mailer: Apple Mail (2.3251) Archived-At: Cc: lisp-chairs@ietf.org Subject: Re: [lisp] Call for adoption draft-farinacci-lisp-rfc6833bis X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 16:52:37 -0000 --Apple-Mail=_1B034532-ABA8-436F-B407-DF6EE60AA49F Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii HI All, the call for adoption for this document is now over. =46rom the replies received we can conclude that=20 there is consensus in adopting the document as WG document. The authors are invited to submit a new version of the document with = name draft-ietf-lisp-rfc6833bis-00.txt. Such document should include all comments received so far. Thanks you all =20 ciao Luigi=20 Joel > On 16 Nov 2016, at 03:58, Luigi Iannone wrote: >=20 > Folks, >=20 > The chairs received a request for the following document to be > adopted as a WG item: >=20 > https://datatracker.ietf.org/doc/draft-farinacci-lisp-rfc6833bis/ = >=20 > Here starts a 14 day call for adoption, this call will end on > Wednesday the 30 November, 2016. >=20 > Please email the WG list stating whether or not you support = acceptance. >=20 > If you email to support the acceptance of this document as a WG item, = please > also indicate if you are able and willing to either contribute to, or = review, (or both) the draft. >=20 > Sitting in silence does not indicate support, please respond = appropriately. >=20 >=20 > The Chairs > Joel & Luigi --Apple-Mail=_1B034532-ABA8-436F-B407-DF6EE60AA49F Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii HI All,

the=  call for adoption for this document is now over.
=46rom the replies received we can conclude = that 
there is consensus in adopting the = document as WG document.
The authors are invited to = submit a new version of the document with name = draft-ietf-lisp-rfc6833bis-00.txt.
Such document = should include all comments received so far.

Thanks you all  

ciao

Luigi 
Joel

On 16 Nov 2016, at 03:58, = Luigi Iannone <ggx@gigix.net> wrote:

Folks,

The chairs received a = request for the following document to be
adopted as a WG = item:

https://datatracker.ietf.org/doc/draft-farinacci-lisp-rfc6833bi= s/

Here starts a 14 day call for adoption, this call will end = on
Wednesday the 30 November, 2016.
Please email the WG list stating whether or not you support = acceptance.

If you email to support the = acceptance of this document as a WG item, please
also = indicate if you are able and willing to either contribute to, = or review, (or both) the draft.

Sitting = in silence does not indicate support, please respond appropriately.


The Chairs
Joel & = Luigi

= --Apple-Mail=_1B034532-ABA8-436F-B407-DF6EE60AA49F-- From nobody Fri Dec 2 08:52:48 2016 Return-Path: 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 26E011295E4 for ; Fri, 2 Dec 2016 08:52:38 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20150623.gappssmtp.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 23hQAjn3t-a5 for ; Fri, 2 Dec 2016 08:52:36 -0800 (PST) Received: from mail-wj0-x236.google.com (mail-wj0-x236.google.com [IPv6:2a00:1450:400c:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 928E21297AA for ; Fri, 2 Dec 2016 08:52:34 -0800 (PST) Received: by mail-wj0-x236.google.com with SMTP id xy5so237011888wjc.0 for ; Fri, 02 Dec 2016 08:52:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=S80HsUYB3hAkWDiVimsGi3vo3Fc7fk+7arcFSic9xKY=; b=Ua+8expGUPqvPZ+DxO407loxZOh7j1gmuV+D4F/1cyIDBfrRtBvWPqWnb3teo6XYPN TY9dyNscmpo7H0rrkMAnN3BQem5Pk0TbMeDK2b23je5iUrNHdLUfk/VhQEHsxY5Uh8lu FYAO24slg3Lnwu14aMavEy1kaxXdgQFRVuNy7wIUz7xhoR32Axdx8wm90IFZPJWdZRxk SGOV1jzCRLfP9vRcQUNnFC36mB2bYmveMhVXRWNYA8e7x12AnqaiCi/jRzedB1KpbcgU jZoN9xLqYq4UHUf5M5y7uzTztZ3ELh/wcXmXxPWV5N2UWSX5fFInRDnB3X7FQNaom6ir uLfg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=S80HsUYB3hAkWDiVimsGi3vo3Fc7fk+7arcFSic9xKY=; b=UrKzaala0cPdURNWIISW8eq5WeRTCYEoICqsXd/+ItESX3ojaMKfaollmafmzvHsqi 1RX8kE+md2fRIMQAM1n2oyLMfor+fG37Ypxt/Kld8C1qbtiH25fOPySk+6Pb9WGdcQbw h1Knum05rV52yWaUEeG4hYXcqJhWlGjXs0BJeyfuTwLSKqeX0VSCIEM/52xkOtwtJZqZ VrPCgHEE6MeaR2TZsh3EF4BN1Y6AXPP+ZlF9G2Sk0N6N7vMLFTVCeFIyZB0AVq2xvQJb Iqq0kCNv7XPJZRBPDJGpmcjq6q0ApadSfI4WGAwoP9zgT/dRNP6Zj4Kk62nNqBRUt9oA UJtA== X-Gm-Message-State: AKaTC0103yuzG3cYKRpdDA3PSIAGHgrZ7v3zY/m6LNWl2uBKNgrLgAhQSeBqeX2+vs5CEg== X-Received: by 10.194.57.9 with SMTP id e9mr37317749wjq.116.1480697552998; Fri, 02 Dec 2016 08:52:32 -0800 (PST) Received: from ?IPv6:2a01:e35:1381:3430:c9ed:cb46:e3be:df59? ([2a01:e35:1381:3430:c9ed:cb46:e3be:df59]) by smtp.gmail.com with ESMTPSA id i15sm6468204wjs.16.2016.12.02.08.52.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Dec 2016 08:52:31 -0800 (PST) From: Luigi Iannone Message-Id: <39505195-A2E2-4DB7-BF73-3A73C16DB496@gigix.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_EE693F51-274E-42A2-B769-3617D7AE822E" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Date: Fri, 2 Dec 2016 17:52:27 +0100 In-Reply-To: To: LISP mailing list list References: X-Mailer: Apple Mail (2.3251) Archived-At: Cc: lisp-chairs@ietf.org Subject: Re: [lisp] Call for adoption draft-farinacci-lisp-rfc6830bis X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 16:52:38 -0000 --Apple-Mail=_EE693F51-274E-42A2-B769-3617D7AE822E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii HI All, the call for adoption for this document is now over. =46rom the replies received we can conclude that=20 there is consensus in adopting the document as WG document. The authors are invited to submit a new version of the document with = name draft-ietf-lisp-rfc6830bis-00.txt. Such document should include all comments received so far. Thanks you all =20 ciao Luigi=20 Joel > On 16 Nov 2016, at 03:57, Luigi Iannone wrote: >=20 > Folks, >=20 > The chairs received a request for the following document to be > adopted as a WG item: >=20 > https://datatracker.ietf.org/doc/draft-farinacci-lisp-rfc6830bis/ = >=20 > Here starts a 14 day call for adoption, this call will end on > Wednesday the 30 November, 2016. >=20 > Please email the WG list stating whether or not you support = acceptance. >=20 > If you email to support the acceptance of this document as a WG item, = please > also indicate if you are able and willing to either contribute to, or = review, (or both) the draft. >=20 > Sitting in silence does not indicate support, please respond = appropriately. >=20 >=20 > The Chairs > Joel & Luigi --Apple-Mail=_EE693F51-274E-42A2-B769-3617D7AE822E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii HI All,

the=  call for adoption for this document is now over.
=46rom the replies received we can conclude = that 
there is consensus in adopting the = document as WG document.
The authors are invited to = submit a new version of the document with name = draft-ietf-lisp-rfc6830bis-00.txt.
Such document = should include all comments received so far.

Thanks you all  

ciao

Luigi 
Joel
On 16 Nov 2016, at 03:57, Luigi Iannone <ggx@gigix.net> = wrote:

Folks,

The chairs received a = request for the following document to be
adopted as a WG = item:

https://datatracker.ietf.org/doc/draft-farinacci-lisp-rfc6830bi= s/

Here starts a 14 day call for adoption, this call will end = on
Wednesday the 30 November, 2016.
Please email the WG list stating whether or not you support = acceptance.

If you email to support the = acceptance of this document as a WG item, please
also = indicate if you are able and willing to either contribute to, = or review, (or both) the draft.

Sitting = in silence does not indicate support, please respond appropriately.


The Chairs
Joel & = Luigi

= --Apple-Mail=_EE693F51-274E-42A2-B769-3617D7AE822E-- From nobody Fri Dec 2 09:36:50 2016 Return-Path: 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 16930129629; Fri, 2 Dec 2016 09:36:49 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 iqxY1Q495AUE; Fri, 2 Dec 2016 09:36:46 -0800 (PST) Received: from mail-pf0-x242.google.com (mail-pf0-x242.google.com [IPv6:2607:f8b0:400e:c00::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FF5D129673; Fri, 2 Dec 2016 09:36:46 -0800 (PST) Received: by mail-pf0-x242.google.com with SMTP id c4so13933198pfb.3; Fri, 02 Dec 2016 09:36:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kWJJHGyzBoSMDjulexhuvPNz9V6iUy9WfmKUqbqY+7I=; b=bIfEaUtyOu8WqbqDPOQZmGoYE1hTqY3rbZp+xyD3JyHBPzm0DbSxk61PqcvHdsivPP 2hA1/6w8sm59xYl15Sp6ngRLe2i80Ej8wT0CpzaLa6E3io5P7sjNJ0lHYko+xin1JIWy ZRmu1NK99S0l5Luz9efDHsH6FDBKMnHOACQXv8aYti5YeRwZo6ZtFs/BYUKwf+U5msS9 jzNYGgcIDIJ+TWdk3ME11Esm+N4+iJczbn9eLO1in9bsf/nqdnqcsKleKXQcKsYT2mKY IgeJpJim/5dPHLaEmk47nZVnCubQeiW0KYDWN/w3OOT1yupRi0awIFgqYj1Iy1tPNrZg lFIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=kWJJHGyzBoSMDjulexhuvPNz9V6iUy9WfmKUqbqY+7I=; b=W+EGcF0jYFhVkyi/KgR5G1iAf1rmUfloEWiDjYmP26sxvOK7/UCliU+TXI3MQ98VcQ 55Qcs1lF7MrhYn0evlxSr4xG/mROYHMnfstDqrfuJvaKlDBDuryF7e0zlOZfyTuMhjwc DcbqEfWxOzA6R7DbLDkFIzPj/J8rx53c4pdWe8z/NxzA8mdXGDvSSV0GPtkVpt+QGi3a K+3AZjdNlpcumExEVmXP0jZRuvLjjy69GLR6tBBI74RjCcCzRLrOf/6zXJV3QJ1u9uBa iJFTzZDa8YSEKJmfeMIv3rnHCrEeAFoGyy6IFNS7ve9wnNWPvOtwavZOhNPearizApjU BUPA== X-Gm-Message-State: AKaTC03P+5v1Dy/ytJIuYGqUueOGJsMKLOp7ep1tLiQnIGrw9KCsn0EdI/nE7NxnHqFaDA== X-Received: by 10.84.136.75 with SMTP id 69mr97005080plk.52.1480700205660; Fri, 02 Dec 2016 09:36:45 -0800 (PST) Received: from [10.197.31.157] (173-11-119-245-SFBA.hfc.comcastbusiness.net. [173.11.119.245]) by smtp.gmail.com with ESMTPSA id t67sm9278845pfg.13.2016.12.02.09.36.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Dec 2016 09:36:45 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) From: Dino Farinacci In-Reply-To: <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> Date: Fri, 2 Dec 2016 09:36:42 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <581EF3B1-820D-4A1A-A76E-F0EF83C85D47@gmail.com> References: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> To: Luigi Iannone X-Mailer: Apple Mail (2.3251) Archived-At: Cc: lisp-chairs@ietf.org, LISP mailing list list Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 17:36:49 -0000 The document is absolutely necessary to complete the full-feature = security model that the LISP architecture needs. There are multiple = implementations of it and it is ready to advance and has been in that = state, IMO, for a long time. So I support moving it along the process. Dino > On Dec 2, 2016, at 8:50 AM, Luigi Iannone wrote: >=20 > Hi All, >=20 > feedback for this last call has been quite low. For this reason we = decide to extend the last call for another two weeks, ending December = 16th. >=20 > Please state your opinion on whether this document is ready for = publication. >=20 > Silence is NOT consensus. >=20 > Ciao >=20 > Luigi & Joel >=20 >> On 17 Nov 2016, at 09:36, Luigi Iannone wrote: >>=20 >> Hi All, >>=20 >> The authors of the LISP-Security (LISP-SEC) document = [https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/] asked for WG = Last Call.=20 >>=20 >> This email starts the usual two weeks WG Last Call, to end December = 1st, 2016. >>=20 >> Please review this WG document and let the WG know if you agree that = it is ready for handing to the AD. >> If you have objections, please state your reasons why, and explain = what it would take to address your concerns. >>=20 >> Thanks >>=20 >> Luigi & Joel >=20 > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp From nobody Fri Dec 2 10:00:21 2016 Return-Path: X-Original-To: lisp@ietf.org Delivered-To: lisp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 08F1612973A; Fri, 2 Dec 2016 10:00:13 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: "IETF-Announce" X-Test-IDTracker: no X-IETF-IDTracker: 6.39.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148070161303.29677.3957750875756746405.idtracker@ietfa.amsl.com> Date: Fri, 02 Dec 2016 10:00:13 -0800 Archived-At: Cc: lisp-chairs@ietf.org, lisp@ietf.org, The IESG , draft-ietf-lisp-lcaf@ietf.org, rfc-editor@rfc-editor.org Subject: [lisp] Document Action: 'LISP Canonical Address Format (LCAF)' to Experimental RFC (draft-ietf-lisp-lcaf-22.txt) X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 18:00:13 -0000 The IESG has approved the following document: - 'LISP Canonical Address Format (LCAF)' (draft-ietf-lisp-lcaf-22.txt) as Experimental RFC This document is the product of the Locator/ID Separation Protocol Working Group. The IESG contact persons are Alvaro Retana, Alia Atlas and Deborah Brungard. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-lcaf/ Technical Summary This document describes a canonical address format encoding used in the ocator/ID Separation Protocol (LISP), more precisely in the lookup keys of the LISP mapping system and related control messages. The intent is to define a general syntax that includes Address Family Identifier (AFI), length, and value fields. Such general syntax aims at enabling an easy evolution of the protocol to support future applications. Working Group Summary The document has been around for a while, and has been discussed several times. From the beginning, there was strong support, because the WG felt that the flexibility introduced by a canonical address encoding was an important feature, which would enable using LISP to be used for use-cases and applications which are not in the original scope of the protocol. Such support never faded. Discussion in the WG group mostly focused on the initial type allocation and their definition. The WG converged on splitting the initial type allocation and their usage in two different sections. Section 4 of the document defines types for which the use-cases are well defined and implementation exists or are ongoing. Section 5 contains types that have a more experimental nature, for which they usage is either not yet clearly identified or not completely defined. Document Quality The LCAF is currently supported by various LISP implementations. May be not all of the types are supported but the basic encoding syntax and types are there. Personnel Who is the Document Shepherd for this document? Luigi Iannone Who is the Responsible Area Director? Deborah Brungard From nobody Fri Dec 2 13:26:32 2016 Return-Path: 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 6BF0012940B; Fri, 2 Dec 2016 13:26:30 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 MFW7aZ66B12I; Fri, 2 Dec 2016 13:26:27 -0800 (PST) Received: from mail-pg0-x242.google.com (mail-pg0-x242.google.com [IPv6:2607:f8b0:400e:c05::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BC6B128E19; Fri, 2 Dec 2016 13:26:25 -0800 (PST) Received: by mail-pg0-x242.google.com with SMTP id 3so8943821pgd.0; Fri, 02 Dec 2016 13:26:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=8emTZWNFKzQFptocB6akKJMGA3eaUoLO9lbbBN41Z6Q=; b=R1E62NObqrKxm6MvKHoB5qrkIV1ANKHkSg2h0NSm614egu1OnXYniWbkS5lk+fTKf1 OyZ0+xIO5GaIiqHblwsymKCwlTUqkF9YU4JSckPTruRzudW3pEGDF1yqbEFKM/rgzRum ZHdFS4dLXjiBvuA9XKWyBdmhfcW08c9X2VshHISouQfmBh3X7DsfZBuDreu96ZnsRZLv L4kvtWqK7CYwgmF5Jr2UsUWeXfR78cP7sUefDzw6JiHV9ucNJC1ejFu4Kh2d4+owr5AU N5Vk/7foalyS4CQXHfKIkIzIad2twjkyH91t39ALflUZgNFjPtfMMrgkWvj4jvO6SxOz +i/A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=8emTZWNFKzQFptocB6akKJMGA3eaUoLO9lbbBN41Z6Q=; b=PZv5bHNy/n8qGdbv4b7HZbThd2o5MVSHf4KIEQv3f99w2ACyUjPhH+R9iciEiogCtX xGKvRMjgCkEhsGbfbt2R5PAg4EhV3YhfdDO3de12UXu2IDIQdfIO6AKHBJaDlkl62OMr bTffco7LiMK8lNjB4JodWTUlEeKNE3173+IYVkWs7gwFesv971VXdjobKAnmeKz61O7S OOkJDF5kPV2uG2Y0Xf5z6u/N25WYeuGLATuuaBCAD6uXvVZwOv57ZpCTAx6feQheQAqg BS00lEKqqfk6A0Pg4Fyu2bkJz9zUc0l6mHYHfJqPEEmdKqoMfuOnc3EuMV2FxF8l7/WZ 5z8Q== X-Gm-Message-State: AKaTC00xAnx8/nnqTAG153y7T44npg7AwN9NmoGvCHqFSYN+2ZXmbSTkoTFV/2V1JGx70g== X-Received: by 10.99.168.10 with SMTP id o10mr82986131pgf.105.1480713985045; Fri, 02 Dec 2016 13:26:25 -0800 (PST) Received: from dhcp-10-154-232-187.cisco.com ([128.107.241.169]) by smtp.gmail.com with ESMTPSA id q12sm9913382pfj.18.2016.12.02.13.26.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 02 Dec 2016 13:26:24 -0800 (PST) From: Florin Coras Message-Id: <2C9F0CFC-8301-4AA8-A927-9BC183BBD8B2@gmail.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_0B481ADA-031D-4DF9-AF64-F64B4E0AA629" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Date: Fri, 2 Dec 2016 13:26:23 -0800 In-Reply-To: <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> To: Luigi Iannone References: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> X-Mailer: Apple Mail (2.3251) Archived-At: Cc: lisp-chairs@ietf.org, LISP mailing list list Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 21:26:30 -0000 --Apple-Mail=_0B481ADA-031D-4DF9-AF64-F64B4E0AA629 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I support handing the document to the AD.=20 Florin > On Dec 2, 2016, at 8:50 AM, Luigi Iannone wrote: >=20 > Hi All, >=20 > feedback for this last call has been quite low. For this reason we = decide to extend the last call for another two weeks, ending December = 16th. >=20 > Please state your opinion on whether this document is ready for = publication. >=20 > Silence is NOT consensus. >=20 > Ciao >=20 > Luigi & Joel >=20 >> On 17 Nov 2016, at 09:36, Luigi Iannone > wrote: >>=20 >> Hi All, >>=20 >> The authors of the LISP-Security (LISP-SEC) document = [https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/ = ] asked for WG = Last Call.=20 >>=20 >> This email starts the usual two weeks WG Last Call, to end December = 1st, 2016. >>=20 >> Please review this WG document and let the WG know if you agree that = it is ready for handing to the AD. >> If you have objections, please state your reasons why, and explain = what it would take to address your concerns. >>=20 >> Thanks >>=20 >> Luigi & Joel >=20 > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp --Apple-Mail=_0B481ADA-031D-4DF9-AF64-F64B4E0AA629 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I support handing the document to the AD. 

Florin

On Dec 2, 2016, at 8:50 AM, Luigi Iannone = <ggx@gigix.net> = wrote:

Hi All,

feedback for this last = call has been quite low. For this reason we decide to extend the last = call for another two weeks, ending December 16th.
Please state your opinion on whether = this document is ready for publication.

Silence is NOT consensus.

Ciao

Luigi & = Joel

On 17 Nov 2016, at 09:36, Luigi = Iannone <ggx@gigix.net> wrote:

Hi All,

The authors of the LISP-Security (LISP-SEC) document [https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/] = asked for WG Last Call. 

This email starts the usual two weeks = WG Last Call, to end December  1st, 2016.

Please review this WG = document and let the WG know if you agree that it is ready for handing = to the AD.
If you have objections, please = state your reasons why, and explain what it would take to address your = concerns.

Thanks

Luigi & = Joel

_______________________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp

= --Apple-Mail=_0B481ADA-031D-4DF9-AF64-F64B4E0AA629-- From nobody Fri Dec 2 14:30:02 2016 Return-Path: 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 D70FD129453; Fri, 2 Dec 2016 14:30:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.417 X-Spam-Level: X-Spam-Status: No, score=-17.417 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=-2.896, SPF_HELO_PASS=-0.001, 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 80H2knWy5CBC; Fri, 2 Dec 2016 14:30:00 -0800 (PST) Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF2DB129449; Fri, 2 Dec 2016 14:29:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7070; q=dns/txt; s=iport; t=1480717799; x=1481927399; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Ieo8kTffjVOUlBYWibnHCGFLwn27AkiOfd2PBjo2yXE=; b=ZkW3IJgeCTpLPwhaGNSpXLl4AFhE/X5/tNkDWbKRhKY3Ig4QXKkBFwVB 1ujWBdGpgh+sA+7EXR3m6vLo9h9dej2kBKnbzFKHeGtLXyl8hf7HWm8EZ 1yIyfR0jv8ykbmg7XS7Fwh4vTa9zwKO50zvj2qYdJJW6VJ5pZYDwM0zfS 4=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AVAQBT9UFY/4wNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgnNFAQEBAQEfWoEGB40/lwuHc4dnhSKCBh4BCoV5AoIdPxQBAgE?= =?us-ascii?q?BAQEBAQFiKIRoAQEBBAEBG1ELEAIBCA4DAwECKAchBgEKFAkIAgQBDQWIVQMXD?= =?us-ascii?q?q5jh0ENg3YBAQEBAQEBAQEBAQEBAQEBAQEBAQEXBYY+hFuCSIFTEQE8hUEFlHq?= =?us-ascii?q?FNDUBhkqFbX6DXoFyhHyIG4EwiUyENIQMAR83YTgjhTJyhlCBIYENAQEB?= X-IronPort-AV: E=Sophos;i="5.33,288,1477958400"; d="scan'208,217";a="180925141" Received: from alln-core-7.cisco.com ([173.36.13.140]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Dec 2016 22:29:58 +0000 Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id uB2MTw6M016274 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 2 Dec 2016 22:29:58 GMT Received: from xch-rcd-005.cisco.com (173.37.102.15) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 2 Dec 2016 16:29:57 -0600 Received: from xch-rcd-005.cisco.com ([173.37.102.15]) by XCH-RCD-005.cisco.com ([173.37.102.15]) with mapi id 15.00.1210.000; Fri, 2 Dec 2016 16:29:57 -0600 From: "Reshad Rahman (rrahman)" To: Florin Coras , Luigi Iannone Thread-Topic: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt Thread-Index: AQHSQK3CjQ956AzD/EetyuksM+RG0aD1W3qAgABNNYD//73zgA== Date: Fri, 2 Dec 2016 22:29:57 +0000 Message-ID: References: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> <2C9F0CFC-8301-4AA8-A927-9BC183BBD8B2@gmail.com> In-Reply-To: <2C9F0CFC-8301-4AA8-A927-9BC183BBD8B2@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.6.8.160830 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.86.240.24] Content-Type: multipart/alternative; boundary="_000_D46758EC1FEBB4rrahmanciscocom_" MIME-Version: 1.0 Archived-At: Cc: "lisp-chairs@ietf.org" , LISP mailing list list Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 22:30:02 -0000 --_000_D46758EC1FEBB4rrahmanciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I support publication of this document. Regards, Reshad. From: lisp > on behalf = of Florin Coras > Date: Friday, December 2, 2016 at 4:26 PM To: Luigi Iannone > Cc: "lisp-chairs@ietf.org" >, LISP mailing list list > Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt I support handing the document to the AD. Florin On Dec 2, 2016, at 8:50 AM, Luigi Iannone > wrote: Hi All, feedback for this last call has been quite low. For this reason we decide t= o extend the last call for another two weeks, ending December 16th. Please state your opinion on whether this document is ready for publication= . Silence is NOT consensus. Ciao Luigi & Joel On 17 Nov 2016, at 09:36, Luigi Iannone > wrote: Hi All, The authors of the LISP-Security (LISP-SEC) document [https://datatracker.i= etf.org/doc/draft-ietf-lisp-sec/] asked for WG Last Call. This email starts the usual two weeks WG Last Call, to end December 1st, 2= 016. Please review this WG document and let the WG know if you agree that it is = ready for handing to the AD. If you have objections, please state your reasons why, and explain what it = would take to address your concerns. Thanks Luigi & Joel _______________________________________________ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp --_000_D46758EC1FEBB4rrahmanciscocom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
I support publication of this document.

Regards,
Reshad.

From: lisp <lisp-bounces@ietf.org> on behalf of Florin Cora= s <fcoras.lists@gmail.com&= gt;
Date: Friday, December 2, 2016 at 4= :26 PM
To: Luigi Iannone <ggx@gigix.net>
Cc: "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>, LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] WG Last Call fo= r draft-ietf-lisp-sec-12.txt

I support handing the document to the AD. 

Florin

On Dec 2, 2016, at 8:50 AM, Luigi Iannone <ggx@gigix.net> wrote:

Hi All,

feedback for this last call has been quite low. For this re= ason we decide to extend the last call for another two weeks, ending Decemb= er 16th.

Please state your opinion on whether this document is ready= for publication.

Silence is NOT consensus.

Ciao

Luigi & Joel

On 17 Nov 2016, at 09:36, Luigi Iannone <ggx@gigix.net> wrote:

Hi All,

The authors of the LISP-Security (LISP-SEC) document [htt= ps://datatracker.ietf.org/doc/draft-ietf-lisp-sec/] asked for WG Last C= all. 

This email starts the usual two weeks WG Last Call, to end = December  1st, 2016.

Please review this WG document and let the WG know if you a= gree that it is ready for handing to the AD.
If you have objections, please state your reasons why, and = explain what it would take to address your concerns.
Thanks

Luigi & Joel

_______________________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org= /mailman/listinfo/lisp

 --_000_D46758EC1FEBB4rrahmanciscocom_-- From nobody Fri Dec 2 15:09:36 2016 Return-Path: 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 622D812946E; Fri, 2 Dec 2016 15:09:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 pJ1LYpGPuJ2X; Fri, 2 Dec 2016 15:09:30 -0800 (PST) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ED0DD129463; Fri, 2 Dec 2016 15:09:26 -0800 (PST) Received: by mail-oi0-x22b.google.com with SMTP id b126so282765858oia.2; Fri, 02 Dec 2016 15:09:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+7Uu/D9+k/C2smpGWuRH0477AhD5hRWtGXjqHCweACs=; b=AkaNqRgP9jqWMHOfJZnsn9WpYU8vxqvTlw8/xW0Cj5U4ENyeB8jnbxxlt+JUaSYb3B llW6CEKT4u280cRALMh0pEWLn7bf/EYKX2IySG3zke60Yykg0EZTtAaILYLLHcJ27gEQ S/np46uoo4L/Vbz2NbudmlKDXmTdsLS71fAElUf/2PruV2p/dXu5uOa1xRGSFZ2h5mEO RcPfu3/xVtj6rAGcuJVW4e68HoceDivjX7VI2K5YUoVxn+6dmTTSzUBjK2VFKcaBv9B0 IDPKRCFBdPVflaPQh/uqi57LqNpg6JkQjiUJ8Hdhri1MjAapCCT1OG+5s6zw+kSXaB2e cvdw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+7Uu/D9+k/C2smpGWuRH0477AhD5hRWtGXjqHCweACs=; b=KoEszP237fqdSo/3Mbnk1IdVB0HQu47tCWVEHReL4DIflH2mMk9J/Oe7r8vIZymy7s 9a685Qn4QOwdOgaCqXAOUc5ExY4Lpbps06xbA3NyPaRjXnVBkt+lONPEuY2LKGWvKUXc Chy1iqnJDQtXaoH1zgEo9ykQmIJZSeAMnE0vQ5wLe+pwNGpC1yuYeQ2aWKTBwJEatP+S flO/Ppd574elYmbmhBf/FMI2PKnM5poxGTfThnStflOLxktrSwgt2YPbXAsSzT94T/aA Qexd9gh8zP+J+pxNpt1IswaHZ7D/iJ2fUa5vx6IHwBQ7o9phjI5pu2IxQYnuScqNtUw2 n8fA== X-Gm-Message-State: AKaTC01i7Ph07OydKV5RjBzdtDA8RHC934/7wtjuBwv8qawbQS7jn7hjDfJtvMQ8jA4mfgO4hdvybHT3P4F7+w== X-Received: by 10.202.195.18 with SMTP id t18mr25268016oif.110.1480720166307; Fri, 02 Dec 2016 15:09:26 -0800 (PST) MIME-Version: 1.0 Received: by 10.182.69.110 with HTTP; Fri, 2 Dec 2016 15:09:05 -0800 (PST) In-Reply-To: <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> References: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> From: Alberto Rodriguez-Natal Date: Fri, 2 Dec 2016 15:09:05 -0800 Message-ID: To: Luigi Iannone Content-Type: multipart/alternative; boundary=001a1134fbce864b850542b50771 Archived-At: Cc: lisp-chairs@ietf.org, LISP mailing list list Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Dec 2016 23:09:33 -0000 --001a1134fbce864b850542b50771 Content-Type: text/plain; charset=UTF-8 Hi all, I think the document is ready for publication. Thanks, Alberto On Fri, Dec 2, 2016 at 8:50 AM, Luigi Iannone wrote: > Hi All, > > feedback for this last call has been quite low. For this reason we decide > to extend the last call for another two weeks, ending December 16th. > > Please state your opinion on whether this document is ready for > publication. > > Silence is NOT consensus. > > Ciao > > Luigi & Joel > > On 17 Nov 2016, at 09:36, Luigi Iannone wrote: > > Hi All, > > The authors of the LISP-Security (LISP-SEC) document [ > https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/] asked for WG Last > Call. > > This email starts the usual two weeks WG Last Call, to end December 1st, > 2016. > > Please review this WG document and let the WG know if you agree that it is > ready for handing to the AD. > If you have objections, please state your reasons why, and explain what it > would take to address your concerns. > > Thanks > > Luigi & Joel > > > > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp > > --001a1134fbce864b850542b50771 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi all,

I think the document i= s ready for publication.

Thanks,
Alberto

On Fri, Dec 2, 2016 = at 8:50 AM, Luigi Iannone <ggx@gigix.net> wrote:
Hi All,

feedback for this last call has been quite low. For this reason we d= ecide to extend the last call for another two weeks, ending December 16th.<= /div>

Please state your opinion on whether this document= is ready for publication.

Silence is NOT consensu= s.

Ciao

Luigi & Joel<= /div>

On= 17 Nov 2016, at 09:36, Luigi Iannone <ggx@gigix.net> wrote:

Hi All,

The authors of the LISP-Security (LISP-SEC) document [https://dat= atracker.ietf.org/doc/draft-ietf-lisp-sec/] asked for WG Last Call= .=C2=A0

This email starts the usual two weeks WG L= ast Call, to end December =C2=A01st, 2016.

Pl= ease review this WG document and let the WG know if you agree that it is re= ady for handing to the AD.
If you have objections, please s= tate your reasons why, and explain what it would take to address your conce= rns.

Thanks

Luigi & Joel


_______________= ________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp


--001a1134fbce864b850542b50771-- From nobody Sat Dec 3 07:17:36 2016 Return-Path: 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 6B208129890; Sat, 3 Dec 2016 07:17:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.201 X-Spam-Level: X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001] autolearn=ham autolearn_force=no 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 IVUpAxvMqIsB; Sat, 3 Dec 2016 07:17:32 -0800 (PST) Received: from roura.ac.upc.es (roura.ac.upc.es [147.83.33.10]) by ietfa.amsl.com (Postfix) with ESMTP id 9F2D412989E; Sat, 3 Dec 2016 07:17:30 -0800 (PST) Received: from gw-2.ac.upc.es (gw-2.ac.upc.es [147.83.30.8]) by roura.ac.upc.es (8.13.8/8.13.8) with ESMTP id uB3FHPGL022786; Sat, 3 Dec 2016 16:17:25 +0100 Received: from [10.61.163.165] (unknown [173.38.220.45]) by gw-2.ac.upc.es (Postfix) with ESMTPSA id 5206A3AD; Sat, 3 Dec 2016 16:17:24 +0100 (CET) To: Luigi Iannone , LISP mailing list list References: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> From: Lori Jakab Organization: LISPmob Message-ID: Date: Sat, 3 Dec 2016 17:17:21 +0200 MIME-Version: 1.0 In-Reply-To: <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Archived-At: Cc: lisp-chairs@ietf.org Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Dec 2016 15:17:34 -0000 On 12/2/16 6:50 PM, Luigi Iannone wrote: > Hi All, > > feedback for this last call has been quite low. For this reason we > decide to extend the last call for another two weeks, ending December 16th. > > Please state your opinion on whether this document is ready for publication. Yes, please start the publication process. -Lori > > Silence is NOT consensus. > > Ciao > > Luigi & Joel > >> On 17 Nov 2016, at 09:36, Luigi Iannone > > wrote: >> >> Hi All, >> >> The authors of the LISP-Security (LISP-SEC) document >> [https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/] asked for WG >> Last Call. >> >> This email starts the usual two weeks WG Last Call, to end December >> 1st, 2016. >> >> Please review this WG document and let the WG know if you agree that >> it is ready for handing to the AD. >> If you have objections, please state your reasons why, and explain >> what it would take to address your concerns. >> >> Thanks >> >> Luigi & Joel > > > > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp > From nobody Sun Dec 4 18:17:03 2016 Return-Path: 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 EBECF1296B4; Sun, 4 Dec 2016 18:17:01 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.418 X-Spam-Level: X-Spam-Status: No, score=-17.418 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=-2.896, SPF_HELO_PASS=-0.001, 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 v-8EJH_GibdT; Sun, 4 Dec 2016 18:17:00 -0800 (PST) Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E494B12968D; Sun, 4 Dec 2016 18:16:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=983; q=dns/txt; s=iport; t=1480904220; x=1482113820; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=ThczzBNEXax6YNSE6BJVzofHQMdfVrTag4g13/ULwBs=; b=fQ9MXEkzw1O/QvsrDwApKAlqMe/AtqVd9+zmKXcDN5eXkQ/st1Ud4oM1 OOHp5J/xAriRLDgD87zKZ6+qTwAbV8HIn9mOxVaj/WKmMlOmaEvh9v2HG t5JYLc+LFA89+UT8QNelVnGW85IaOIFBfxlHvqpCHDDhx/37Ra2K/iSRQ 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ATAQAGzURY/5BdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgzgBAQEBAR9agQYHjUCXCZR9gggeC4V5AoIdPxQBAgEBAQEBAQF?= =?us-ascii?q?iKIRpAQEEAQEbHTQLEAIBCA4KHhAnCyUCBA4FiG8OriyLLgEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEBARcFhj6BfQiCVoQaEQEcgzGCMAEEmmYBkRaBcoR9iB6BMI4ChAw?= =?us-ascii?q?BHzdhOCMOAQGFInKGLoEhgQ0BAQE?= X-IronPort-AV: E=Sophos;i="5.33,302,1477958400"; d="scan'208";a="356638463" Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Dec 2016 02:16:59 +0000 Received: from XCH-ALN-019.cisco.com (xch-aln-019.cisco.com [173.36.7.29]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id uB52GxVr028951 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 5 Dec 2016 02:16:59 GMT Received: from xch-rcd-018.cisco.com (173.37.102.28) by XCH-ALN-019.cisco.com (173.36.7.29) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 4 Dec 2016 20:16:58 -0600 Received: from xch-rcd-018.cisco.com ([173.37.102.28]) by XCH-RCD-018.cisco.com ([173.37.102.28]) with mapi id 15.00.1210.000; Sun, 4 Dec 2016 20:16:58 -0600 From: "Darrel Lewis (darlewis)" To: Luigi Iannone Thread-Topic: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt Thread-Index: AQHSTp2oG+mfysCXLkmNHz+SCT+Y5g== Date: Mon, 5 Dec 2016 02:16:58 +0000 Message-ID: References: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> In-Reply-To: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> 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.19.253.182] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Archived-At: Cc: LISP mailing list list , "lisp-chairs@ietf.org" Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2016 02:17:02 -0000 Given this document describes technology that has not only been thoroughly = reviewed, and that its been implemented, and finally that its been deployed= across thousands of devices, I believe it may just be ready to be publishe= d. -Darrel > On Nov 17, 2016, at 12:36 AM, Luigi Iannone wrote: >=20 > Hi All, >=20 > The authors of the LISP-Security (LISP-SEC) document [https://datatracker= .ietf.org/doc/draft-ietf-lisp-sec/] asked for WG Last Call.=20 >=20 > This email starts the usual two weeks WG Last Call, to end December 1st,= 2016. >=20 > Please review this WG document and let the WG know if you agree that it i= s ready for handing to the AD. > If you have objections, please state your reasons why, and explain what i= t would take to address your concerns. >=20 > Thanks >=20 > Luigi & Joel > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp From nobody Mon Dec 5 00:45:57 2016 Return-Path: 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 788E5129862; Mon, 5 Dec 2016 00:45:56 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 DUrTB68vyBtj; Mon, 5 Dec 2016 00:45:55 -0800 (PST) Received: from mail-wm0-x229.google.com (mail-wm0-x229.google.com [IPv6:2a00:1450:400c:c09::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C200812985F; Mon, 5 Dec 2016 00:45:54 -0800 (PST) Received: by mail-wm0-x229.google.com with SMTP id a197so85603827wmd.0; Mon, 05 Dec 2016 00:45:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=PwCcANQ7BAe7lUePySmvE+EOS5g57ZVS6FXNEgW9SLY=; b=P9bx3eAVeaHSLz/jOOm2r5OgoKP76l4esBa3sqsNKKf1dVLXXMOKKFC9ROss8HkFkN 6ztEPB2GrJ3l/AdYbWXGow7AQnMi25EiYSwPKgu5NSWkSSDhWMgeGjvL9wfaQbi4PR7B A1SSonldnvMYKFHtgWs90J3oDqS7h+eCdphHSNMJdF6xWuM2j99yL8p5kPCdXTyYg9bn XHk+E1mFTYefX1C9y0C5Et3lZjwFmQcLF7xlRGKHBDtd3Aoxa6QGojppJByh1c7QkhO2 FxGyQ3oTfNziQI4wRRrpQYiAnh1D9RDtRSl4PEM+jIM44KJ1cd3RqrmgToap60vKwJGp YfdQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=PwCcANQ7BAe7lUePySmvE+EOS5g57ZVS6FXNEgW9SLY=; b=MC0awfyrcwq10ku3gRerKMF0BC0M2y5Ja+Czwy19nvWQE8h1bHI0k9v6Y0O5eXZ0/C ZRDiibrL+EYO++6pUnkpCeFX+eg1n7Bazw28R/lWQ9385I4EtUECpWDvnko/1ZHdUtF9 gBLXEgYQf0dQ1ujL9YSOUHhfqhE2+pmUKQYoQiW6DEDquIIYDXgzVjx4w8zX8K4NIJ48 tPdpUOxjOZA1d7PN3njpQ2LEpyzEYIAb+ehy0DG0ongDIS/bxiUextpdjCm3PowEaI2H h6lgkJjfimMmzmus8NhPUxWu1ZXY5D6Ylj6R4rha/a7nkF0IReLJJniccWYA6fHzaoI8 2Lbw== X-Gm-Message-State: AKaTC01rTT/qFjWLTY3W9TQKkzgGy0+JnkYpLQRKL1LJMRn8uYtwfALrN0t07NC6k7hyhS48CxtHLwdbFV6IEw== X-Received: by 10.28.153.201 with SMTP id b192mr8738263wme.61.1480927553175; Mon, 05 Dec 2016 00:45:53 -0800 (PST) MIME-Version: 1.0 Received: by 10.80.132.162 with HTTP; Mon, 5 Dec 2016 00:45:52 -0800 (PST) In-Reply-To: <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> References: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> From: =?UTF-8?Q?Roger_J=C3=B8rgensen?= Date: Mon, 5 Dec 2016 09:45:52 +0100 Message-ID: To: Luigi Iannone Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: lisp-chairs@ietf.org, LISP mailing list list Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Dec 2016 08:45:56 -0000 On Fri, Dec 2, 2016 at 5:50 PM, Luigi Iannone wrote: > Hi All, > > feedback for this last call has been quite low. For this reason we decide to > extend the last call for another two weeks, ending December 16th. > > Please state your opinion on whether this document is ready for publication. I think it's ready for publication. -- Roger Jorgensen | ROJO9-RIPE rogerj@gmail.com | - IPv6 is The Key! http://www.jorgensen.no | roger@jorgensen.no From nobody Tue Dec 6 11:43:03 2016 Return-Path: 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 19489129538 for ; Tue, 6 Dec 2016 11:42:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 aUgQXd5DT0mN for ; Tue, 6 Dec 2016 11:42:52 -0800 (PST) Received: from mail-pf0-x22f.google.com (mail-pf0-x22f.google.com [IPv6:2607:f8b0:400e:c00::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39305129534 for ; Tue, 6 Dec 2016 11:42:49 -0800 (PST) Received: by mail-pf0-x22f.google.com with SMTP id d2so72021909pfd.0 for ; Tue, 06 Dec 2016 11:42:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:mime-version:subject:message-id:references:to:date; bh=kTEJlwzA0YDA+2WmldTgrq7bR4wUNpxo+zqvH1XisYo=; b=YfzeRZdMOsrXxiz7rJtljoWOtvtvc1tUCK4Kh+CYu42my2yC4AiXV/lqzKTBeoGCFG iWNYZcnJtkBbIKnJve+Z7S2YEAGrNWurVTaujtlGuEUmOljRlkO5ykCacz8Y3aIZY9h+ dOp64DWdqytMo2RFOER63SMyrgcysMOFdfu0rN2d30axQ/HXKjyNaIodpGvbcfnkVTFc s1jykZn4i42CheD/KAybGjtcF5LLN3nceP1lv6xXm6n9+FShDa7E21HZGu7yDmtKGgs5 x2pSBEEcyphz5rwAvd/yDIOG/+n01ZDxyHeqYaOvE6IlNoaVx34L0A81YjyGSn8/x66p RydQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:mime-version:subject:message-id:references :to:date; bh=kTEJlwzA0YDA+2WmldTgrq7bR4wUNpxo+zqvH1XisYo=; b=myfwpJz8JYcquo17RDaurBblljDj11tqFjs70P2+Q2T7XmIItLDPs4TWBWsmOmGnhF aRjWWkcTBi5kXYD3vfgR/PJcyIqWwLkr4pWOu5nBA2WE8hEGXhk2ezrGESphw0mzBSmP rZuypPssK98LrhxeehGi1JZqYvcimUJJxVVGfk26xxZNwVtVF9LIvK6xJOsAA9g8qccF p4L4BNFQQ0hLEU7doq97GVpl4HJ38T3aWvyXxcoFcAJtTNNqVNXUlPiqHf+OBj9xbdHj W6e4Zek4bF9iOifDKNA8CINJnYRfm+vFPOuoy0x040TIXMYjgDr39CrPQhWRIc9FK0FF T8KA== X-Gm-Message-State: AKaTC02qTurgBCRcZ6/omYOanJ2757zoMOUiyC2rob9L1QwYBYWLVn3Fu5AaZnUyUgXTlw== X-Received: by 10.84.215.148 with SMTP id l20mr139453350pli.120.1481053368616; Tue, 06 Dec 2016 11:42:48 -0800 (PST) Received: from [10.197.31.157] (173-11-119-245-SFBA.hfc.comcastbusiness.net. [173.11.119.245]) by smtp.gmail.com with ESMTPSA id k25sm36626089pfg.84.2016.12.06.11.42.46 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Dec 2016 11:42:48 -0800 (PST) From: Dino Farinacci Content-Type: multipart/alternative; boundary="Apple-Mail=_C7D7A91B-A226-4B1D-8124-79E5B0E8D7AC" Mime-Version: 1.0 (Mac OS X Mail 10.1 \(3251\)) Message-Id: <74448453-073F-4511-B1A0-2B7E1807F76D@gmail.com> References: <148105218804.1726.13286775839176108227.idtracker@ietfa.amsl.com> To: LISP mailing list list Date: Tue, 6 Dec 2016 11:42:46 -0800 X-Mailer: Apple Mail (2.3251) Archived-At: Subject: [lisp] Fwd: I-D Action: draft-ietf-pim-join-attributes-for-lisp-06.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2016 19:42:55 -0000 --Apple-Mail=_C7D7A91B-A226-4B1D-8124-79E5B0E8D7AC Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii FYI. Dino > Begin forwarded message: >=20 > From: internet-drafts@ietf.org > Subject: I-D Action: draft-ietf-pim-join-attributes-for-lisp-06.txt > Date: December 6, 2016 at 11:23:08 AM PST > To: > Cc: pim@ietf.org > Reply-To: internet-drafts@ietf.org >=20 >=20 > A New Internet-Draft is available from the on-line Internet-Drafts = directories. > This draft is a work item of the Protocols for IP Multicast of the = IETF. >=20 > Title : PIM Join Attributes for LISP Environments > Authors : Jesus Arango > Stig Venaas > Isidor Kouvelas > Dino Farinacci > Filename : draft-ietf-pim-join-attributes-for-lisp-06.txt > Pages : 9 > Date : 2016-12-06 >=20 > Abstract: > This document defines two PIM Join/Prune attributes that support the > construction of multicast distribution trees where the root and > receivers are located in different LISP sites. These attributes > allow the receiver site to select between unicast and multicast > underlay transport and to convey the RLOC (Routing Locator) address > of the receiver ETR (Egress Tunnel Router) to the control plane of > the root ITR (Ingress Tunnel Router). >=20 >=20 > The IETF datatracker status page for this draft is: > = https://datatracker.ietf.org/doc/draft-ietf-pim-join-attributes-for-lisp/ >=20 > There's also a htmlized version available at: > https://tools.ietf.org/html/draft-ietf-pim-join-attributes-for-lisp-06 >=20 > A diff from the previous version is available at: > = https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pim-join-attributes-for-lis= p-06 >=20 >=20 > Please note that it may take a couple of minutes from the time of = submission > until the htmlized version and diff are available at tools.ietf.org. >=20 > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ >=20 > _______________________________________________ > I-D-Announce mailing list > I-D-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/i-d-announce > Internet-Draft directories: http://www.ietf.org/shadow.html > or ftp://ftp.ietf.org/ietf/1shadow-sites.txt --Apple-Mail=_C7D7A91B-A226-4B1D-8124-79E5B0E8D7AC Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii FYI.

Dino

Begin forwarded = message:

From: = internet-drafts@ietf.org
Subject: = I-D Action: = draft-ietf-pim-join-attributes-for-lisp-06.txt
Date: = December 6, 2016 at 11:23:08 AM = PST
To: = <i-d-announce@ietf.org>
Cc: pim@ietf.org
Reply-To: = internet-drafts@ietf.org


A New = Internet-Draft is available from the on-line Internet-Drafts = directories.
This draft is a work item of the Protocols = for IP Multicast of the IETF.

=        Title =           : PIM Join = Attributes for LISP Environments
=        Authors =         : Jesus Arango
=             &n= bsp;           &nbs= p;Stig Venaas
=             &n= bsp;           &nbs= p;Isidor Kouvelas
=             &n= bsp;           &nbs= p;Dino Farinacci
Filename =        : = draft-ietf-pim-join-attributes-for-lisp-06.txt
Pages =           : 9
= Date =            : = 2016-12-06

Abstract:
=   This document defines two PIM Join/Prune attributes that = support the
  construction of multicast = distribution trees where the root and
=   receivers are located in different LISP sites.  These = attributes
  allow the receiver site to select = between unicast and multicast
  underlay = transport and to convey the RLOC (Routing Locator) address
=   of the receiver ETR (Egress Tunnel Router) to the control = plane of
  the root ITR (Ingress Tunnel = Router).


The IETF = datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-pim-join-attributes= -for-lisp/

There's also a htmlized = version available at:
https://tools.ietf.org/html/draft-ietf-pim-join-attributes-for-= lisp-06

A diff from the previous version is = available at:
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-pim-join-attribu= tes-for-lisp-06


Please note = that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at = tools.ietf.org.

Internet-Drafts are also = available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: = http://www.ietf.org/shadow.html
or = ftp://ftp.ietf.org/ietf/1shadow-sites.txt

= --Apple-Mail=_C7D7A91B-A226-4B1D-8124-79E5B0E8D7AC-- From nobody Tue Dec 6 14:25:37 2016 Return-Path: X-Original-To: lisp@ietf.org Delivered-To: lisp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F2EC0129CDB; Tue, 6 Dec 2016 14:25:31 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.39.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148106313199.1710.924767624051318736.idtracker@ietfa.amsl.com> Date: Tue, 06 Dec 2016 14:25:31 -0800 Archived-At: Cc: lisp@ietf.org Subject: [lisp] I-D Action: draft-ietf-lisp-rfc6830bis-00.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2016 22:25:32 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Locator/ID Separation Protocol of the IETF. Title : The Locator/ID Separation Protocol (LISP) Authors : Dino Farinacci Vince Fuller Dave Meyer Darrel Lewis Albert Cabellos Filename : draft-ietf-lisp-rfc6830bis-00.txt Pages : 53 Date : 2016-12-06 Abstract: This document describes the Locator/ID Separation Protocol (LISP) data-plane encapsulation protocol. LISP defines two namespaces, End- point Identifiers (EIDs) that identify end-hosts and Routing Locators (RLOCs) that identify network attachment points. With this, LISP effectively separates control from data, and allows routers to create overlay networks. LISP-capable routers exchange encapsulated packets according to EID-to-RLOC mappings stored in a local map-cache. The map-cache is populated by the LISP Control-Plane protocol [REF_TO_RFC6833bis]. LISP requires no change to either host protocol stacks or to underlay routers and offers Traffic Engineering, multihoming and mobility, among other features. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6830bis/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-lisp-rfc6830bis-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Tue Dec 6 14:31:02 2016 Return-Path: X-Original-To: lisp@ietf.org Delivered-To: lisp@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 988801295E7; Tue, 6 Dec 2016 14:31:00 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.39.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148106346061.1750.5986676530033120449.idtracker@ietfa.amsl.com> Date: Tue, 06 Dec 2016 14:31:00 -0800 Archived-At: Cc: lisp@ietf.org Subject: [lisp] I-D Action: draft-ietf-lisp-rfc6833bis-00.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Dec 2016 22:31:00 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Locator/ID Separation Protocol of the IETF. Title : Locator/ID Separation Protocol (LISP) Control-Plane Authors : Vince Fuller Dino Farinacci Albert Cabellos Filename : draft-ietf-lisp-rfc6833bis-00.txt Pages : 37 Date : 2016-12-06 Abstract: This document describes the Control-Plane and Mapping Service for the Locator/ID Separation Protocol (LISP), implemented by two new types of LISP-speaking devices -- the LISP Map-Resolver and LISP Map-Server -- that provides a simplified "front end" for one or more Endpoint ID to Routing Locator mapping databases. By using this control-plane service interface and communicating with Map-Resolvers and Map-Servers, LISP Ingress Tunnel Routers (ITRs) and Egress Tunnel Routers (ETRs) are not dependent on the details of mapping database systems, which facilitates experimentation with different database designs. Since these devices implement the "edge" of the LISP infrastructure, connect directly to LISP-capable Internet end sites, and comprise the bulk of LISP-speaking devices, reducing their implementation and operational complexity should also reduce the overall cost and effort of deploying LISP. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6833bis/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-lisp-rfc6833bis-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Sun Dec 11 09:15:47 2016 Return-Path: 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 4FA6B12946E; Sun, 11 Dec 2016 09:15:43 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 uNI9ik6A-KEf; Sun, 11 Dec 2016 09:15:40 -0800 (PST) Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6158C129479; Sun, 11 Dec 2016 09:15:40 -0800 (PST) Received: by mail-qk0-x232.google.com with SMTP id n204so63290762qke.2; Sun, 11 Dec 2016 09:15:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc; bh=k7BVP0pwg4/KYayEJ/yX8Mb1v+XjC+j2iacsXGUkSyw=; b=iMIhvDR/iAxuI/OyNFe+jplMLyokPUbsXi6quS9MCKo7bFz+I4ZAAiBChtNkToDgVq obc1rqtOmN0l/gDSiMQamYwraSoSu6oNfbjWCDjyLLh9iDd/X1ThETYVEcMD854x7aea zGycE1TOHl9Rqa9N90WpfGv8IdKYf4eMMcDuC4Cc7SRnAbk5xsqHqbICng9DWVDnHMvb TNq4u5HzepEqUbvlJ3AE/x6pNMsijK/qwDfula0sdyhfm8F0WEd37miQFSSRCiP7EafX XUkPiAB1oYBleUdp6Z70Kwxhy3vo4MPBhoWrhu1Wv6HLAPYTUem48DP3D+f2NQyfz1lc tLdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=k7BVP0pwg4/KYayEJ/yX8Mb1v+XjC+j2iacsXGUkSyw=; b=WbT8qQxZphCL66s1YYpmXIf3HSeqQfB6vyKlMrNz+nUBAxewgttv3d+U8xw4WSQSIk 2b7rnMDILe1c8E8/d7ldhkOyntfpg3VXY342F/AnOVG+vWbpMDyX2DpbhIAaI5pFxIs2 nyGOUr+DZFRlijyNuX4vhLugXixFxi5vOxQ9fzP4xXQBT+2GzV1PL+3NqLLQMWe3hf7h J0MnbOS/o36JlQbDu+CEkAjl6c0DTS5d97PI70D06k+PGLu1SAnIpDSAm+yC56NgRkoN Dz5KtWkdRln6E4rhENe5t+kBm50f7vcr9Yd92Z4qPt8leomPJy8OUupqa/oco7WXewH8 MbNA== X-Gm-Message-State: AKaTC02DwYs5NUGy5wlpbjZr9RU3fwpn4UUkISLyI9ACQPZYNvhi6Cv3vuXqc1mhfsY1z1PonvI8otjCf46zBg== X-Received: by 10.55.183.197 with SMTP id h188mr84595413qkf.107.1481476539342; Sun, 11 Dec 2016 09:15:39 -0800 (PST) MIME-Version: 1.0 Received: by 10.200.41.198 with HTTP; Sun, 11 Dec 2016 09:15:38 -0800 (PST) From: Padma Pillay-Esnault Date: Sun, 11 Dec 2016 09:15:38 -0800 Message-ID: To: LISP mailing list list Content-Type: multipart/mixed; boundary=94eb2c06af0adf0261054365226e Archived-At: Cc: ideas@ietf.org Subject: [lisp] FW: [Ideas] Minutes of IDEAS side meeting @IETF97 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Dec 2016 17:15:43 -0000 --94eb2c06af0adf0261054365226e Content-Type: multipart/alternative; boundary=94eb2c06af0adf025e054365226c --94eb2c06af0adf025e054365226c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable FYI. Feel free to forward. Looking forward to working with you all Padma *From:* Ideas [mailto:ideas-bounces@ietf.org] *On Behalf Of *Padma Pillay-Esnault *Sent:* Sunday, December 11, 2016 8:51 AM *To:* ideas@ietf.org *Subject:* [Ideas] Minutes of IDEAS side meeting @IETF97 Hello IDEAS! Please find below the minutes of IDEAS side meeting @IETF97. Thanks to all of you who attended the meeting and to Les Ginsberg for taking minutes. Please take a look and let us know if there are any changes needed. Looking forward to your contributions. Padma IDEAS Side Meeting Minutes IETF97 1. Agenda Padma Pillay-Esnault (Huawei) - Introduction on problem statement for IDEAS (10 mins) Presented the problem statement draft and the Use cases. Robert Raszuk: Should we define what identity is? Padma: Agree. The document take a stab at this by defining identities and in which context. There is a table in the document that captures the different aspects of ID usage, allocation and its impact on a dynamic mapping system. Sam Aldrin: What is primary focus? What problem are you really trying to solve? Narrow the scope - or are we trying to define a problem because we have a solution? Padma: The primary focus is the design and deployment of a dynamic mapping system. The Problem statement discusses in detail the problems we are trying to solve. Among those many problems is Session continuity in mobility which is important as we have more and more mobile modes in cellular as well as ip mobility(DC). Another important problem that can be solved and is discussed in the paper is Cross-silo communication. Encourage everyone to read the document. Luigi: We have multiple encaps and mappings and want to manage in a common way. But what is a common ID? Please clarify. Padma: In this case we are not necessarily looking for a common single ID. What we are trying to do is to map an ID to location. So that we can have the Identity dissociated with the locator so that mobility is fully supported. What we are proposing is to have a common control plane that have access to a mapping system used by all. It is not very practical to deploy one global mapping system per protocol or application. Luigi: Do we have to solve who is allocating the ID? Maybe we do not have to solve this problem. Padma: Well it depends. We have both the case for public and private IDs. For public IDs to be used by a common control plane, we will require some rules. Luigi: But what form will the ID take? Dino: Different EID types for different purposes. Hopefully they will be used for different purposes. Should it be geographical, first come first served, assigned at birth,...many types allocated differently. L2 overlays have the MAC address. ID allocation independent of database. ~General discussion about EID types and mapping systems. Bob Moskowitz: I am the Last member of the EID cabal. :-) Many discussions have been already What characteristics required of an EID? What is good/bad? Capturing that would be good. There is two decades of experience available =E2=80=93 would be good to make use of that. Padma: There is a table in the draft which captures some aspects of this discussion. How are we actually using IDs today? And how it should be used or restricted. Can we use ID properties to provide better security for example? Georgios: Take into account use cases in 5G and IoT, since they will impose requirements that we did not have up to now. ********************************************************** Tom Herbert ( Facebook) - The ILA protocol and NMS (10 mins) Scale to 100=E2=80=99s of billion aggregate mappings No aggregation assumed, 1%change per second Able to attach ancillary data to mapping Bob: Is this intended to be globally unique? Tom: Globally unique in a domain. Bob: with 7B population w 64 bit # 74% probability of collision. This must be accounted for. Will post the formula for calculating likelihood of collision. Tom: We do have a method to generate unique identifiers. Covers 20 years of experience. Mapping system detects conflicts at registration. Bob: Agreed. But 10 devices/person gives high probability of collisions Kiran: Scope of identifier determined by locator? Tom: Identifiers unique for a domain. Reverse translation requires locator to map back to the original prefix. Ingress/Egress translation. Both sides have to agree on the pairing. Kiran Makhijani: If age out of cache how can you detect? Tom: If we lose ILA routers need to have other ILA addresses available. An open issue Kiran Makhijani: Need to have reliability solution base requirements related to NMS ************************************************ Dino Farinacci ( Lispers) - LISP Mapping system, How it works? (10 mins) Presented LISP Site to access of mapping System, Site Registration 10 years of experience and DDT mapping server. Hierarchical network structure based on EID Allocation 3 levels of hierarchy to get 1billion registrations: 1 Million for 1 MS Multiple mapping systems Tom: With DNS have to wait for resolution - looks like you have same issue w LISP DDT? Dino: Solved by LISP has default cache in ITR. Albert: if you don=E2=80=99t was to resolve, you can set default route to p= roxy RTR which has all the mappings Fabio: Proxy DNS - you send to the router which has all the information. Dino points that if there are too many mappings In LISP we can use proxy ETRs , where requests can be distributed. Tom: In ILA had too many mappings in one device and now ILA does something similar. ************************************************ Gerry Forster ( UoSurrey) - ETSi NGP: GTP, Mobility & Flat 5G Architecture( 15 mins) Presented the mobile network as being most successful system, however GTP is expensive and adds to the cost for whoever is paying for spectrum. The user data is tunneled at least 3 times and GTP need to be updated for mobility. Smaller native headers (most of the time). Presented UoS work. Association-based secure membership of each level of network access Scalable addressing (16 bit most of the time, 52 bit global). 3-level ID-based Mobility (Cluster, Inter-Cluster, Network) Routing tables are local, but indexed for gateway function by 3-level ID lookup (not DNS, but intelligent network hierarchy and Meta-Data). Transmis= sion is tailored by profile to level of access, access type and networking level Lookups/ routes are through intelligent use of meta-data based =E2=80=98Con= text=E2=80=99 =3D ID Enabled Networking Dino: Can we assign IPv6 address but use a 16 bit address? Gerry : Yes - can virtualize end-to-end. Gerry: New protocol for access networks - can do the same for wifi. Dino: Only limit is 65K connections at one time. Gerry: Limit the number of translations or compromise the delay. ************************************************ Fabio Maino(Cisco) - Deployment experience of Mapping Systems ( 10 mins) Presented various use cases and deployment experience Internet based VPN, IPv6 transition, BGP free multihoming, DC host mobility Up to now mapping system in the router. Based on current requirements it is needed to bring mapping system out of the router. ************************************************ Dave Meyer (UoOregon/Brocade) - Machine Learning and Network Mapping System ( 15 Mins) ??: How did you get the parameters from networking? Are they addresses Dave: Just flattened the number - used different parameters e.g. number of map requests? Other parameters - will need to learn what works in the network case. ************************************************ A. Cabellos, J Vilanova & F Maino (UoCatalunya, Ecole P. Lausanne, Cisco) - A Blockchain-based Mapping System (15 mins) Padma: Have you looked at scalability? Fabio: Yes - scales well. ??: Is it clear that use cases are enforcing new requirements other than are provided by LISP (for example)? Will problem scope be different than in LISP? What might be the advantage of IDEAS work rather than LISP? Padma: Out of time - take it to the list. How can we be most useful? Need to work on defining the exact scope. ??:Will it be a BOF? Padma: Not sure yet. 2. Admin & Location Date: Thursday, 17th November 2016 Time : 6:00 - 8:00pm Venue: Studio2 Mailing list: IDEAS List address: ideas@ietf.org Archive: https://mailarchive.ietf.org/arch/search/?email_list=3Dideas To subscribe: https://www.ietf.org/mailman/listinfo/ideas Related areas: RTG, OPS Scribe: Les Ginsberg Number of attendees: 40+3. 3. Related Documents and Reads: https://tools.ietf.org/html/draft-padma-ideas-problem-statement-00 https://tools.ietf.org/html/draft-herbert-nvo3-ila-03 https://tools.ietf.org/html/rfc6830 https://tools.ietf.org/html/rfc6833 http://www.3gpp.org/release-14 --94eb2c06af0adf025e054365226c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
FYI.=C2=A0Feel free to forward.

Looking forward to working with you= all
Padma
<= div class=3D"gmail_quote">

=C2=A0

From: Ideas [m= ailto:ideas-bou= nces@ietf.org] On Behalf Of Padma Pillay-Esnault
Sent: Sunday, December 11, 2016 8:51 AM
To: ideas@ietf.o= rg
Subject: [Ideas] Minutes of IDEAS side meeting @IETF97=

=C2=A0

Hello IDEAS!<= u>

=C2=A0=

Please find below th= e minutes of IDEAS side meeting @IETF97.

Thanks to all of you= who attended the meeting and to=C2=A0Les Ginsberg for taking minutes.

=C2=A0=

Please take a look a= nd let us know if there are any changes needed.

=C2=A0=

Looking forward to y= our contributions.

Padma<= /span>

=C2=A0

=C2=A0

IDEAS Side Meeting M= inutes=C2=A0 IETF97

=C2=A0=

=C2=A0=

1. Agenda=C2=A0

Padma Pillay-Esnault= (Huawei) - Introduction on problem statement for IDEAS (10 mins)=

Presented the proble= m statement draft and the Use cases.

=C2=A0=

Robert Raszuk: Shoul= d we define what identity is?

Padma: Agree. The do= cument take a stab at this by defining identities and in which context. The= re is a table in the document that captures the different aspects of ID usage, allocation and its impact on a dynamic mapping system= .

=C2=A0=

Sam Aldrin: What is = primary focus? What problem are you really trying to solve? Narrow the scop= e - or are we trying to define a problem because we have a solution?

Padma: The primary f= ocus is the design and deployment of a dynamic mapping system.

The Problem statemen= t discusses in detail the problems we are trying to solve. Among those many= problems is Session continuity in mobility which is important as we have more and more mobile modes in cellular as well as ip = mobility(DC). Another important problem that can be solved and is discussed= in the paper is Cross-silo communication. Encourage everyone to read the d= ocument.

=C2=A0=

Luigi: We have multi= ple encaps and mappings and want to manage in a common way.

But what is a common= ID? Please clarify.

=C2=A0=

Padma: In this case = we are not necessarily looking for a common single ID. What we are trying t= o do is to map an ID to location. So that we can have the Identity dissociated with the locator so that mobility is fully suppor= ted. What we are proposing is to have a common control plane that have acce= ss to a mapping system used by all. It is not very practical to deploy one = global mapping system per protocol or application.

=C2=A0=

Luigi: Do we have to= solve who is allocating the ID? Maybe we do not have to solve this problem= .

Padma: Well it depen= ds. We have both the case for public and private IDs. For public IDs to be = used by a common control plane, we will require some rules.

Luigi: But what form= will the ID take?

Dino: Different EID = types for different purposes. Hopefully they will be used

for different purpos= es. Should it be geographical, first come first served,

assigned at birth,..= .many types allocated differently.

L2 overlays have the= MAC address.

ID allocation indepe= ndent of database.

=C2=A0=

~General discussion = about EID types and mapping systems.

=C2=A0=

Bob Moskowitz: I am = the Last member of the EID cabal. :-)

Many discussions hav= e been already What characteristics required of an EID? What is good/bad? C= apturing that would be good. There is two decades of experience available =E2=80=93 would be good to make use of that.

Padma: There is a ta= ble in the draft which captures some aspects of this discussion.<= /u>

How are we actually = using IDs today? And how it should be used or restricted.

Can we use ID proper= ties to provide better security for example?

Georgios: Take into = account use cases in 5G and IoT, since they will impose requirements that w= e did not have up to now.

=C2=A0=

********************= **************************************

Tom Herbert ( Facebo= ok) - The ILA protocol and NMS (10 mins)

Scale to 100=E2=80= =99s of billion aggregate mappings

No aggregation assum= ed, 1%change per second

Able to attach ancil= lary data to mapping

=C2=A0=

Bob: Is this intende= d to be globally unique?

Tom: Globally unique= in a domain.=C2=A0

Bob: with 7B populat= ion w 64 bit # 74% probability of collision.

This must be account= ed for. Will post the formula for calculating likelihood of collision.

Tom: We do have a me= thod to generate unique identifiers.=C2=A0

Covers 20 years of e= xperience.=C2=A0=C2=A0

Mapping system detec= ts conflicts at registration.

Bob: Agreed. But 10 = devices/person gives high probability of collisions

Kiran: Scope of iden= tifier determined by locator?

Tom: Identifiers uni= que for a domain.=C2=A0

Reverse translation = requires locator to map back to the original prefix.

Ingress/Egress trans= lation. Both sides have to agree on the pairing.

Kiran Makhijani: If = age out of cache how can you detect?

Tom: If we lose ILA = routers need to have other ILA addresses available.

An open issue=

Kiran Makhijani: Nee= d to have reliability solution base requirements related to NMS

=C2=A0=

********************= ****************************

Dino Farinacci ( Lis= pers) - LISP Mapping system, How it works? (10 mins)

Presented LISP Site = to access of mapping System, Site Registration

10 years of experien= ce and DDT mapping server.

Hierarchical network= structure based on EID Allocation

3 levels of hierarch= y to get 1billion registrations: 1 Million for 1 MS

Multiple mapping sys= tems

=C2=A0=

Tom: With DNS have t= o wait for resolution - looks like you have same issue=

w LISP DDT?

Dino: Solved by LISP= has default cache in ITR.

Albert: if you don= =E2=80=99t was to resolve, you can set default route to proxy RTR which has= all the mappings

Fabio: Proxy DNS - y= ou send to the router which has all the information.

Dino points that if = there are too many mappings In LISP we can use proxy ETRs , where requests = can be distributed.

Tom: In ILA had too = many mappings in one device and now ILA does something similar.

=C2=A0=

********************= ****************************

Gerry Forster ( UoSu= rrey) - ETSi NGP: GTP, Mobility=C2=A0 & Flat 5G Architecture( 15 mins) = Presented the mobile network as being most successful system, however GTP is expensive and adds to the cost for whoever is paying for sp= ectrum. The user data is tunneled at least 3 times and GTP need to be updat= ed for mobility.=C2=A0Smaller native headers (most of the time).

=C2=A0=

Presented UoS work.= =C2=A0

Assoc= iation-based secure membership of each level of network access

Scala= ble addressing (16 bit most of the time, 52 bit global). 3-level ID-based M= obility (Cluster, Inter-Cluster, Network)

Routi= ng tables are local, but indexed for gateway function by 3-level ID lookup = (not DNS, but intelligent network hierarchy and Meta-Data).=C2=A0Transmission is tailored by profile to level of access, access type and networking leve= l

Looku= ps/ routes are through intelligent use of meta-data based =E2=80=98Context= =E2=80=99 =3D ID Enabled Networking=C2=A0

=C2=A0=

Dino: Can we assign = IPv6 address but use a 16 bit address?

Gerry : Yes - can vi= rtualize end-to-end.

Gerry: New protocol = for access networks - can do the same for wifi.

Dino: Only limit is = 65K connections at one time.

Gerry: Limit the num= ber of translations or compromise the delay.

=C2=A0=

********************= ****************************

Fabio Maino(Cisco) -= Deployment experience of=C2=A0 Mapping Systems ( 10 mins)

Presented various us= e cases and deployment experience Internet based VPN, IPv6 transition, BGP = free multihoming, DC host mobility

Up to now mapping sy= stem in the router. Based on current requirements it is needed to bring map= ping system out of the router.

=C2=A0=

********************= ****************************

Dave Meyer (UoOregon= /Brocade) - Machine Learning=C2=A0 and Network Mapping System=C2=A0 ( 15 Mi= ns)

??: How did you get = the parameters from networking? Are they addresses

Dave: Just flattened= the number - used different parameters e.g. number of=

map requests? Other = parameters - will need to learn what works in the network case.

********************= ****************************

A. Cabellos, J Vilan= ova & F Maino (UoCatalunya, Ecole P. Lausanne, Cisco) - A Blockchain-ba= sed Mapping System (15 mins)=C2=A0

Padma: Have you look= ed at scalability?

Fabio: Yes - scales = well.

??: Is it clear that= use cases are enforcing new requirements other than are provided by LISP (= for example)?

Will problem scope b= e different than in LISP? What might be the advantage of IDEAS work rather = than LISP?

Padma: Out of time -= take it to the list. How can we be most useful?

Need to work on defi= ning the exact scope.

??:Will it be a BOF?=

Padma: Not sure yet.=

=C2=A0=

2. Admin & Locat= ion=C2=A0

Date: Thursday, 17th= November 2016

Time :=C2=A06:00 - 8:00pm

Venue: Studio2

Mailing list: IDEAS<= u>

List address:=C2=A0<= a href=3D"mailto:ideas@ietf.org" target=3D"_blank">ideas@ietf.org

Archive:=C2=A0https://mailarchive.ietf.org/arch/search/?email_list= =3Dideas

To subscribe:=C2=A0<= a href=3D"https://www.ietf.org/mailman/listinfo/ideas" target=3D"_blank">ht= tps://www.ietf.org/mailman/listinfo/ideas

Related areas: RTG, = OPS=C2=A0

Scribe: Les Ginsberg=

Number of attendees:= 40+3.=C2=A0

=C2=A0=

3. Related Documents= and Reads:

https://tools.ietf.org/html/draft-padma-ideas-problem-statement= -00

https://too= ls.ietf.org/html/draft-herbert-nvo3-ila-03

https://tools.ietf.org/html/<= wbr>rfc6830

https://tools.ietf.org/html/<= wbr>rfc6833

http://www.3gpp.org/release-14=

=C2=A0=


--94eb2c06af0adf025e054365226c-- --94eb2c06af0adf0261054365226e Content-Type: text/plain; charset=US-ASCII; name="ATT00002.txt" Content-Disposition: attachment; filename="ATT00002.txt" Content-Transfer-Encoding: base64 Content-ID: <1F561182C838AA40A70F9AC78D7BE3F0@huawei.com> X-Attachment-Id: 2808fa1db41272f3_0.1 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCklkZWFzIG1h aWxpbmcgbGlzdA0KSWRlYXNAaWV0Zi5vcmcNCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v bGlzdGluZm8vaWRlYXMNCg== --94eb2c06af0adf0261054365226e-- From nobody Fri Dec 16 12:44:33 2016 Return-Path: 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 00860129B92; Fri, 16 Dec 2016 12:44:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.702 X-Spam-Level: X-Spam-Status: No, score=-2.702 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_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.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 qXsPoHuCXajb; Fri, 16 Dec 2016 12:44:30 -0800 (PST) Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 611CF1296CB; Fri, 16 Dec 2016 12:44:30 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 4B37E2693F6; Fri, 16 Dec 2016 12:44:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=1.tigertech; t=1481921070; bh=EoTo4ZKQtH3P85OXQ+Yvx1f9zVgIqDMvrerdAPoB0CA=; h=Subject:References:To:From:Date:In-Reply-To:From; b=cbJVf73Zq6TgbmMC9KNfTmULR7eIznjTKSawHrihDcGYXrW0uq3KIbwi8o+i81k2O HEujDu0MJHeA+ksrJ2qXXEypGBfzo+ecz+p3ET2ulhB/vBZdKEyLPKlB3Z+lQJwixy 1o6j0YbT8IypW4E7IfBav2wNJQ3l+5XgzAp1rUmM= X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net Received: from Joels-MacBook-Pro.local (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 65DDE2693B2; Fri, 16 Dec 2016 12:44:29 -0800 (PST) References: <2530302c-cab3-09b1-6c2d-39c2bd84ecf6@rfc-editor.org> To: "lisp@ietf.org" , "sfc@ietf.org" From: "Joel M. Halpern" X-Forwarded-Message-Id: <2530302c-cab3-09b1-6c2d-39c2bd84ecf6@rfc-editor.org> Message-ID: <686ccaa4-388e-1d9d-513b-d475a04633eb@joelhalpern.com> Date: Fri, 16 Dec 2016 15:44:27 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 MIME-Version: 1.0 In-Reply-To: <2530302c-cab3-09b1-6c2d-39c2bd84ecf6@rfc-editor.org> Content-Type: multipart/mixed; boundary="------------6CC3E4F30C6E45C39C4486D8" Archived-At: Subject: [lisp] Fwd: [rfc-i] The RFC Format docs are now RFCs X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Dec 2016 20:44:32 -0000 This is a multi-part message in MIME format. --------------6CC3E4F30C6E45C39C4486D8 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit The RFCs described the intended evolution of the RFC Format are, as per the notice from Heather below, now available. Please take a look. The IESG has indicated that as the tooling development progress, they will allow these features in IDs. They also note that early testing is obviously welcome. Yours, Joel -------- Forwarded Message -------- Subject: [rfc-i] The RFC Format docs are now RFCs Date: Fri, 16 Dec 2016 09:14:27 -0800 From: Heather Flanagan (RFC Series Editor) To: rfc-interest@rfc-editor.org, ietf@ietf.org Hello all, The RFC Format requirements documents were published this morning. This represents an enormous amount of work on the part of the RFC Format Design Team, and an enormous amount of patience and feedback from the community. Of course, the work isn't quite done - all of these RFCs will undergo a -bis cycle so we can document the "as built" instead of just the "as proposed." But regardless of the amount of work still to come, this is a big milestone for the project! So, thank you all, and stay tuned for the next steps of code development, testing, and collecting feedback! -Heather Flanagan, RSE The RFC Format Design Team: * Nevil Brownlee (ISE) * Heather Flanagan (RSE) * Tony Hansen * Joe Hildebrand * Paul Hoffman * Ted Lemon * Julian Reschke * Adam Roach * Alice Russo * Robert Sparks (Tools Team liaison) * Dave Thaler The RFCs, in suggested reading order: * "RFC Format Framework " - https://www.rfc-editor.org/info/rfc7990 * "The "xml2rfc" Version 3 Vocabulary" - https://www.rfc-editor.org/info/rfc7991 * "HTML Format for RFCs" - https://www.rfc-editor.org/info/rfc7992 * "Cascading Style Sheets (CSS) Requirements for RFCs" - https://www.rfc-editor.org/info/rfc7993 * "Requirements for Plain-Text RFCs" - https://www.rfc-editor.org/info/rfc7994 * "PDF Format for RFCs" - https://www.rfc-editor.org/info/rfc7995 * "SVG Drawings for RFCs: SVG 1.2 RFC" - https://www.rfc-editor.org/info/rfc7996 * "The Use of Non-ASCII Characters in RFCs" - https://www.rfc-editor.org/info/rfc7997 * ""xml2rfc" Version 3 Preparation Tool Description" - https://www.rfc-editor.org/info/rfc7997 --------------6CC3E4F30C6E45C39C4486D8 Content-Type: text/plain; charset=UTF-8; name="Attached Message Part" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Attached Message Part" X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KcmZjLWlu dGVyZXN0IG1haWxpbmcgbGlzdApyZmMtaW50ZXJlc3RAcmZjLWVkaXRvci5vcmcKaHR0cHM6 Ly93d3cucmZjLWVkaXRvci5vcmcvbWFpbG1hbi9saXN0aW5mby9yZmMtaW50ZXJlc3QKCg== --------------6CC3E4F30C6E45C39C4486D8-- From nobody Mon Dec 19 05:33:49 2016 Return-Path: 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 ADB8A129A5A for ; Mon, 19 Dec 2016 05:33:48 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gigix-net.20150623.gappssmtp.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 eVRtOvKdE6_8 for ; Mon, 19 Dec 2016 05:33:46 -0800 (PST) Received: from mail-ua0-x234.google.com (mail-ua0-x234.google.com [IPv6:2607:f8b0:400c:c08::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 649CC129A3F for ; Mon, 19 Dec 2016 05:33:46 -0800 (PST) Received: by mail-ua0-x234.google.com with SMTP id b35so74024457uaa.0 for ; Mon, 19 Dec 2016 05:33:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=E+Z65o043lbgun6BE7qXrgZHPvA1N47pWFcyDPZDAtY=; b=K8KuRA+o2TGkfKcXaN8UUU9LQezcN+LgzFpORVyWAn9JT26CAEaMn5xyxVDBi1WrW7 duJvnKdFNeWvpzyEpKkZEUT6BDYuJBkG0+hKEDJrj7h21NKQ1s+m5yQbO8UnA7y0mdgr T1cp2sPPGg6sX+TuYeyeSzPz3kj7iz2ufCtzXzy/tTU3MB0S8bUMdFQsTkR3R9+Cx+6V zz8ZAkcFOPaxyoz+zZGIEbDwfOrMP5MP8O9Nmn9Gql0d2N6u0tyZ/70ZbFMBQSKaAMM0 fTgb8OAmvm/5hcwgj+Ha5XOCy3CfzeFU470khoyrDAQOOttEjvamPBsB0agPHXB2Lri4 2hFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=E+Z65o043lbgun6BE7qXrgZHPvA1N47pWFcyDPZDAtY=; b=WZ8/XUzA94YAuFcxKrT4vinqLIJ+UCAoClWur0jwkxI5xqUeCXdB9jzJ11LKNTOQQU zjE3DasrF7dnUGZaFawmDir8GBUxg3DtXIWlwrm/Mm0M955dAdIddW/c7oWRKwIrxchJ rkFzESWEyC3Dzk6/alW7BLq790wpSe4EzqLpgLWRtPABsxeOkBXjX1V93MeVmev6mO5Q IiONIOs5FLdmcxtGMFcx6AcMNkXC57tfgL/eelbPGzOAfNjj26Dpdkj4kewqMKR8H68V DqjuHlNeRM/YtB+0tSx24oK35duJ4xX3+GWKpyuWlZVG5hQU+NdnKsvR1YWxSVfULo5D fFxg== X-Gm-Message-State: AKaTC00lljcf5RGJvbDGG5eAqW1Aq8P2FsfFxEF9w/OEZdrjP+za+HARQBPCPfXJwWET6g== X-Received: by 10.176.66.227 with SMTP id j90mr13245768uaj.105.1482154425156; Mon, 19 Dec 2016 05:33:45 -0800 (PST) Received: from [192.168.0.18] ([179.221.97.207]) by smtp.gmail.com with ESMTPSA id 15sm4700695uai.18.2016.12.19.05.33.42 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Dec 2016 05:33:43 -0800 (PST) From: Luigi Iannone Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_E27A7AF0-4118-4295-A1D5-9EDF0FC94C2B" Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Date: Mon, 19 Dec 2016 14:33:42 +0100 In-Reply-To: <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> To: LISP mailing list list References: <4F0F4D9C-DEB1-485E-951C-553F42223C96@gigix.net> <730AD986-1C72-48D4-B93A-0594A75C5514@gigix.net> X-Mailer: Apple Mail (2.3259) Archived-At: Cc: lisp-chairs@ietf.org Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-sec-12.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List for the discussion of the Locator/ID Separation Protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Dec 2016 13:33:49 -0000 --Apple-Mail=_E27A7AF0-4118-4295-A1D5-9EDF0FC94C2B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Hi All, the extended WG LC for draft-ietf-lisp-sec-12 is now closed. Several emails were in favour of moving this document forward and no = objections were raised. It seems that there is consensus to request publication of this = document. The writeup will follow soon. Thanks you all for the work done and Merry Xmas Luigi & Joel > On 2 Dec 2016, at 17:50, Luigi Iannone wrote: >=20 > Hi All, >=20 > feedback for this last call has been quite low. For this reason we = decide to extend the last call for another two weeks, ending December = 16th. >=20 > Please state your opinion on whether this document is ready for = publication. >=20 > Silence is NOT consensus. >=20 > Ciao >=20 > Luigi & Joel >=20 >> On 17 Nov 2016, at 09:36, Luigi Iannone > wrote: >>=20 >> Hi All, >>=20 >> The authors of the LISP-Security (LISP-SEC) document = [https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/ = ] asked for WG = Last Call.=20 >>=20 >> This email starts the usual two weeks WG Last Call, to end December = 1st, 2016. >>=20 >> Please review this WG document and let the WG know if you agree that = it is ready for handing to the AD. >> If you have objections, please state your reasons why, and explain = what it would take to address your concerns. >>=20 >> Thanks >>=20 >> Luigi & Joel >=20 --Apple-Mail=_E27A7AF0-4118-4295-A1D5-9EDF0FC94C2B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Hi All,

the= extended WG LC for draft-ietf-lisp-sec-12 is now closed.

Several emails were in = favour of moving this document forward and no objections were = raised.
It seems that there is consensus to request = publication of this document.

The writeup will follow soon.

Thanks you all for the = work done and Merry Xmas

Luigi & Joel


On 2 Dec 2016, at 17:50, Luigi Iannone <ggx@gigix.net> = wrote:

Hi All,

feedback for this last = call has been quite low. For this reason we decide to extend the last = call for another two weeks, ending December 16th.
Please state your opinion on whether = this document is ready for publication.

Silence is NOT consensus.

Ciao

Luigi & = Joel

On 17 Nov 2016, at 09:36, Luigi = Iannone <ggx@gigix.net> wrote:

Hi All,

The authors of the LISP-Security (LISP-SEC) document [https://datatracker.ietf.org/doc/draft-ietf-lisp-sec/] = asked for WG Last Call. 

This email starts the usual two weeks = WG Last Call, to end December  1st, 2016.

Please review this WG = document and let the WG know if you agree that it is ready for handing = to the AD.
If you have objections, please = state your reasons why, and explain what it would take to address your = concerns.

Thanks

Luigi & = Joel


= --Apple-Mail=_E27A7AF0-4118-4295-A1D5-9EDF0FC94C2B--