From nobody Mon Jul 2 02:42:50 2018 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 B8590130E7F; Mon, 2 Jul 2018 02:42:43 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.81.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153052456369.28003.15653533065669973077@ietfa.amsl.com> Date: Mon, 02 Jul 2018 02:42:43 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-6834bis-00.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 02 Jul 2018 09:42:44 -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 WG of the IETF. Title : Locator/ID Separation Protocol (LISP) Map-Versioning Authors : Luigi Iannone Damien Saucez Olivier Bonaventure Filename : draft-ietf-lisp-6834bis-00.txt Pages : 19 Date : 2018-07-02 Abstract: This document describes the LISP (Locator/ID Separation Protocol) Map-Versioning mechanism, which provides in-packet information about Endpoint ID to Routing Locator (EID-to-RLOC) mappings used to encapsulate LISP data packets. The proposed approach is based on associating a version number to EID-to-RLOC mappings and the transport of such a version number in the LISP-specific header of LISP-encapsulated packets. LISP Map-Versioning is particularly useful to inform communicating Ingress Tunnel Routers (ITRs) and Egress Tunnel Routers (ETRs) about modifications of the mappings used to encapsulate packets. The mechanism is optional and transparent to implementations not supporting this feature, since in the LISP- specific header and in the Map Records, bits used for Map-Versioning can be safely ignored by ITRs and ETRs that do not support or do not want to use the mechanism. This document obsoletes [RFC6834], which is the inital experimental specifications of the mechanims updated by this document. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-6834bis/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-lisp-6834bis-00 https://datatracker.ietf.org/doc/html/draft-ietf-lisp-6834bis-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 Mon Jul 2 15:25:20 2018 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 BB090130E87; Mon, 2 Jul 2018 15:25:17 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.81.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153057031774.16070.10508023425869596797@ietfa.amsl.com> Date: Mon, 02 Jul 2018 15:25:17 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-vendor-lcaf-02.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 02 Jul 2018 22:25:18 -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 WG of the IETF. Title : Vendor Specific LISP Canonical Address Format (LCAF) Authors : Alberto Rodriguez-Natal Vina Ermagan Anton Smirnov Vrushali Ashtaputre Dino Farinacci Filename : draft-ietf-lisp-vendor-lcaf-02.txt Pages : 5 Date : 2018-07-02 Abstract: This document describes a new LISP Canonical Address Format (LCAF), the Vendor Specific LCAF. This LCAF enables organizations to have internal encodings for LCAF addresses. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-vendor-lcaf/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02 https://datatracker.ietf.org/doc/html/draft-ietf-lisp-vendor-lcaf-02 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-vendor-lcaf-02 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 Mon Jul 2 15:42:57 2018 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 508AC130E60; Mon, 2 Jul 2018 15:42:49 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.934 X-Spam-Level: X-Spam-Status: No, score=-1.934 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 4jXiHRgufzEB; Mon, 2 Jul 2018 15:42:47 -0700 (PDT) Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (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 B38AE1311C0; Mon, 2 Jul 2018 15:42:47 -0700 (PDT) Received: from [192.168.10.33] (c8r38-1-78-197-168-57.fbx.proxad.net [78.197.168.57]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id w62MgW7i010211 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 2 Jul 2018 15:42:34 -0700 References: <153057085187.16368.17027473724315322445.idtracker@ietfa.amsl.com> To: 5GANGIP <5gangip@ietf.org>, "lisp@ietf.org list" , dmm@ietf.org, ila@ietf.org From: Erik Nordmark X-Forwarded-Message-Id: <153057085187.16368.17027473724315322445.idtracker@ietfa.amsl.com> Message-ID: <3c9865b6-5819-ab4c-7d0d-87d36949591a@acm.org> Date: Mon, 2 Jul 2018 15:42:31 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <153057085187.16368.17027473724315322445.idtracker@ietfa.amsl.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVY1iNe6gkWLinv7Q6VYjHi47d9+sCFstg3x4j2TiABlzvWi8MAyoVZCUGc/hLuliQF0pKV9UCA4mBcMRaWIdXWB X-Sonic-ID: C;tNJaNUl+6BG7e6H3kFY0nw== M;6mlVNkl+6BG7e6H3kFY0nw== X-Sonic-Spam-Details: 0.0/5.0 by cerberusd Archived-At: Subject: [lisp] Fwd: New Version Notification for draft-nordmark-id-loc-privacy-00.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 02 Jul 2018 22:42:50 -0000 This is a rough draft, but hopefully it can stimulate more discussion around privacy considerations. -------- Forwarded Message -------- Subject: New Version Notification for draft-nordmark-id-loc-privacy-00.txt Date: Mon, 02 Jul 2018 15:34:11 -0700 From: internet-drafts@ietf.org To: Erik Nordmark A new version of I-D, draft-nordmark-id-loc-privacy-00.txt has been successfully submitted by Erik Nordmark and posted to the IETF repository. Name: draft-nordmark-id-loc-privacy Revision: 00 Title: Privacy issues in ID/locator separation systems Document date: 2018-07-02 Group: Individual Submission Pages: 6 URL: https://www.ietf.org/internet-drafts/draft-nordmark-id-loc-privacy-00.txt Status: https://datatracker.ietf.org/doc/draft-nordmark-id-loc-privacy/ Htmlized: https://tools.ietf.org/html/draft-nordmark-id-loc-privacy-00 Htmlized: https://datatracker.ietf.org/doc/html/draft-nordmark-id-loc-privacy Abstract: There exists several protocols and proposals for identifier/locator split which have some form of control plane by which participating nodes can use to share their current id to locator information with their peers. This document explores some of the privacy considerations for such a system. 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. The IETF Secretariat From nobody Mon Jul 2 22:02:04 2018 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 323C5130E2D; Mon, 2 Jul 2018 22:01:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.4 X-Spam-Level: X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 wXkRVcc7XDn4; Mon, 2 Jul 2018 22:01:44 -0700 (PDT) Received: from mail-wr0-x242.google.com (mail-wr0-x242.google.com [IPv6:2a00:1450:400c:c0c::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 3B9A9130E00; Mon, 2 Jul 2018 22:01:44 -0700 (PDT) Received: by mail-wr0-x242.google.com with SMTP id q10-v6so496118wrd.4; Mon, 02 Jul 2018 22:01:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=JI7xsfsq7t/Aa+gYJyVQwK7E7daUuRW1RNMsUGJKKeA=; b=ioiQ0EA4XGhE/O0IkRiugZCXAKjBeDu6bVHSxntIftdA2WoAHF8uMSJFOfWbrJdDUb em4qoAan5Uxs7B820NCRyL5gnciZ/NWFAkWOGJDWSVfR1uBkwdXlgHvT/hgViUHSFklP eGg9DK6N6JRndBJ0IqTru1F6E5qUWdCTwzXcVyPqDzDMHkoSncZgIhvR24bFxcvT3pdc 6a0sDslquhssgfTXfePAofNYnSSN4qxRLM7HI2jIJIvpbVMzNN8ZDRC/CqsISdynlewW mLA7nsL1lD7MOE8ayyB0F8hs7HVzS/qscxJL0HUvBK74kL+1j7PGxVucx0xryBn6JPIV m7sA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=JI7xsfsq7t/Aa+gYJyVQwK7E7daUuRW1RNMsUGJKKeA=; b=O2pCWh5qX84HsMJD0JkJJT6xYHJuPJJgyvHPHN6KI3c/s47WquJ8ZQF2TluALaWAJb 3T8poBZsMzw8OSmCmULiyJ9tpeXnaYpsv9HG5aOqmu+/L0VZYERBR7upbYBOklNXGtQV pNJdFgwiSTRGGjHH66OdhHvaLyp0opzo1h+DKOJUsVwxQ3DYaP13lQ7bQAUrDnixNyYU xbhDeFO1/kRnrj4e8E7TGrXoo/yQdTgxMoRoHwIA1EJjNVIcj5aLNu1mQLMTZ4h8fBb7 Ybtd1M91YVqT6xHO+e6V0T36c61fxBGNPPHWuEKhqv3BlCDJAVEZxq72Bm19LvQgbPbz o1AQ== X-Gm-Message-State: APt69E3IDVsEgXCbNw2q3sP6WIr3Q4E8yTexrYxauw3D0PndYNFCtGQR DiESzxnVuNZDruFHNhZFy6irv3FEq+/+RDm/txo= X-Google-Smtp-Source: AAOMgpfdHmXA7hmAnZ70nLGwU/U9R9PNklQIWoGNq+cc77sSPB364aIeXT5VhqTpAWm+XSGfYG3q5Zzumh+dLnOC7ws= X-Received: by 2002:adf:e0cc:: with SMTP id e12-v6mr13497971wri.199.1530594102742; Mon, 02 Jul 2018 22:01:42 -0700 (PDT) MIME-Version: 1.0 Sender: crowcroft@gmail.com Received: by 2002:a1c:ef11:0:0:0:0:0 with HTTP; Mon, 2 Jul 2018 22:01:42 -0700 (PDT) In-Reply-To: <3c9865b6-5819-ab4c-7d0d-87d36949591a@acm.org> References: <153057085187.16368.17027473724315322445.idtracker@ietfa.amsl.com> <3c9865b6-5819-ab4c-7d0d-87d36949591a@acm.org> From: Jon Crowcroft Date: Tue, 3 Jul 2018 06:01:42 +0100 X-Google-Sender-Auth: SCk-iy9uH3Y5I_JcFBlE4Cq8w7o Message-ID: To: Erik Nordmark Cc: 5GANGIP <5gangip@ietf.org>, "lisp@ietf.org list" , dmm@ietf.org, ila@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [lisp] [5gangip] Fwd: New Version Notification for draft-nordmark-id-loc-privacy-00.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 03 Jul 2018 05:01:47 -0000 what we need is compact onion routing - maybe we could call it garlic routing. in all seriousness, if people are worried about privacy with regards network operators, or state actors co-ercing network operators, at this level, that is what you want. otherwise forget about efficient mobile routing - the fact is that the signature of the set of locations you visit is enough to re-identify a node pretty quickly - its been done (see wetherall's work on this a few years back on simply looking at sequences of wifi AP associations, without bothing with end system mac addr, to uniquely matc individual (indeed, find their home) - you have to get the threat model appropriately...and proportioately On Mon, Jul 2, 2018 at 11:42 PM, Erik Nordmark wrote: > > This is a rough draft, but hopefully it can stimulate more discussion around > privacy considerations. > > -------- Forwarded Message -------- > Subject: New Version Notification for draft-nordmark-id-loc-privacy-00.txt > Date: Mon, 02 Jul 2018 15:34:11 -0700 > From: internet-drafts@ietf.org > To: Erik Nordmark > > > A new version of I-D, draft-nordmark-id-loc-privacy-00.txt > has been successfully submitted by Erik Nordmark and posted to the > IETF repository. > > Name: draft-nordmark-id-loc-privacy > Revision: 00 > Title: Privacy issues in ID/locator separation systems > Document date: 2018-07-02 > Group: Individual Submission > Pages: 6 > URL: > https://www.ietf.org/internet-drafts/draft-nordmark-id-loc-privacy-00.txt > Status: https://datatracker.ietf.org/doc/draft-nordmark-id-loc-privacy/ > Htmlized: https://tools.ietf.org/html/draft-nordmark-id-loc-privacy-00 > Htmlized: > https://datatracker.ietf.org/doc/html/draft-nordmark-id-loc-privacy > > > Abstract: > There exists several protocols and proposals for identifier/locator > split which have some form of control plane by which participating > nodes can use to share their current id to locator information with > their peers. This document explores some of the privacy > considerations for such a system. > > > > > 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. > > The IETF Secretariat > > _______________________________________________ > 5gangip mailing list > 5gangip@ietf.org > https://www.ietf.org/mailman/listinfo/5gangip From nobody Tue Jul 3 08:15:10 2018 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 4F7D91277CC for ; Tue, 3 Jul 2018 08:15:03 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-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 kMea_-j1SnlW for ; Tue, 3 Jul 2018 08:15:00 -0700 (PDT) Received: from mail-wr0-x229.google.com (mail-wr0-x229.google.com [IPv6:2a00:1450:400c:c0c::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 58773130DCC for ; Tue, 3 Jul 2018 08:15:00 -0700 (PDT) Received: by mail-wr0-x229.google.com with SMTP id t6-v6so2365154wrn.7 for ; Tue, 03 Jul 2018 08:15:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1knYTn4Igy2DtGW+jwxLw9hhqA9pKeHHD2etcB6mm9Y=; b=I7aJKjXq3FZCPkt6YH//KB5d14gxTLXAD01CzqPE+FBm4DeArFsNW3WUKBOVev1jLS /rJYDUEiNTqf0/EcwY4v+eZ4HuVfs8OBghEVam4NGKZIq9tIFO6qbUIGMP7xExvb2p/I rqweISc9hG8E6kdGMuMQuvTp8QGUV9+M+w6yaQIE8LLceRO5Guj+5UyRulsaGNV9opFa VbL3AL1LhsI+33MaVxqtECaAvJsawI2MyhuSjzVFqKD/K3QjZVhiOdUAjbaEz0gjAfvT U2sIf2JEG2YVV9mUmAg+OHzi1ooIXOPKu7Ty/PNlPigqbjRwaQbnhYQztWwpZOhRqvfF 7kBg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1knYTn4Igy2DtGW+jwxLw9hhqA9pKeHHD2etcB6mm9Y=; b=KjKRsVGzLFfadfRh/HFXo77FPgn4lHa8KL2mJgrOMqUk94j+OZy4T501JK2WPLof5q zBgY0tb8J+8SiJm+ui1Cmw0mSp59JxM4ptUQiBxHALdoA4Bxos2tqYuwPQs8JnyHpbAt Guqhc18JJvwE/c+kIgjeH3+/HYW4fUoaf2EtpWBfdzyDW3b5fnE5CbZGhaekIP9jpxNG hapMcoaf8ljtRD7pa54RBAjrOjsDS8tLNmlAVMvUv5Bi5oBcr2uHBVA6lKEAWVc/0Xd2 BKTZLrNBLiTIsVxUyClsbdxg5ibaR9RwIrOiGcs/XAYFtAK0xGn6fegHf0YAu/ZyOLd7 hiYw== X-Gm-Message-State: APt69E1NeworTsgzXwbZQDpeU4auDWFJww3kQG0gZ9kVNpvnk038UqM0 s7r7LIu+xlNrr+aL29doOR+mqCcORpCXc3GDghsuCA== X-Google-Smtp-Source: AAOMgpckblLdPtShOD9e2Vx9m4lU/mP7B7mmgoLYIFzYd+tjg8SphRlhpFqz8i3x4AsOr2t6MKbSpb+18Q5BTV1P44U= X-Received: by 2002:adf:ecc6:: with SMTP id s6-v6mr11026493wro.160.1530630898640; Tue, 03 Jul 2018 08:14:58 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:fa86:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 08:14:58 -0700 (PDT) In-Reply-To: References: <153057085187.16368.17027473724315322445.idtracker@ietfa.amsl.com> <3c9865b6-5819-ab4c-7d0d-87d36949591a@acm.org> From: Tom Herbert Date: Tue, 3 Jul 2018 08:14:58 -0700 Message-ID: To: Jon Crowcroft Cc: Erik Nordmark , 5GANGIP <5gangip@ietf.org>, ila@ietf.org, "lisp@ietf.org list" , dmm Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [lisp] [5gangip] Fwd: New Version Notification for draft-nordmark-id-loc-privacy-00.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 03 Jul 2018 15:15:04 -0000 On Mon, Jul 2, 2018 at 10:01 PM, Jon Crowcroft wrote: > what we need is compact onion routing - maybe we could call it garlic routing. > > in all seriousness, if people are worried about privacy with regards > network operators, or state actors co-ercing network operators, at > this level, that is what you want. otherwise forget about efficient > mobile routing - the fact is that the signature of the set of > locations you visit is enough to re-identify a node pretty quickly - > its been done (see wetherall's work on this a few years back on simply > looking at sequences of wifi AP associations, without bothing with end > system mac addr, to uniquely matc individual (indeed, find their home) > - you have to get the threat model appropriately...and proportioately Jon, The threat is not limited to coming from network operators, it is basically from the whole Internet. IP addresses must be sent as clear text, and when they encode personally identifiable information then that can be used by third parties to compromise privacy. In mobile addresses, the threat is both comprising identity and location of the user. Identity can be compromised when the same address (or device specific prefix in case of RFC4941 addresses) is reused for different flows, location is compromised when an address encodes a locator that can be used to determine specific location. There are publicized examples of third parties using IP addresses to expose identity and location (e.g. https://theintercept.com/2018/03/26/facebook-data-ice-immigration/). In order to provide privacy in addressing, IP addresses need to be purged of PII. This likely entails minimizing aggregation and a high frequency of address change in a host. On the surface, this does seem to be in conflict with "efficient mobile routing" as you mentioned, however I don't believe that efficient routing is an acceptable trade off for not providing adequate privacy to users. Alternatives that achieve both goals should be investigated. draft-herbert-ipv6-prefix-address-privacy-00 suggests "hidden aggregation" as one possibility. Tom > > On Mon, Jul 2, 2018 at 11:42 PM, Erik Nordmark wrote: >> >> This is a rough draft, but hopefully it can stimulate more discussion around >> privacy considerations. >> >> -------- Forwarded Message -------- >> Subject: New Version Notification for draft-nordmark-id-loc-privacy-00.txt >> Date: Mon, 02 Jul 2018 15:34:11 -0700 >> From: internet-drafts@ietf.org >> To: Erik Nordmark >> >> >> A new version of I-D, draft-nordmark-id-loc-privacy-00.txt >> has been successfully submitted by Erik Nordmark and posted to the >> IETF repository. >> >> Name: draft-nordmark-id-loc-privacy >> Revision: 00 >> Title: Privacy issues in ID/locator separation systems >> Document date: 2018-07-02 >> Group: Individual Submission >> Pages: 6 >> URL: >> https://www.ietf.org/internet-drafts/draft-nordmark-id-loc-privacy-00.txt >> Status: https://datatracker.ietf.org/doc/draft-nordmark-id-loc-privacy/ >> Htmlized: https://tools.ietf.org/html/draft-nordmark-id-loc-privacy-00 >> Htmlized: >> https://datatracker.ietf.org/doc/html/draft-nordmark-id-loc-privacy >> >> >> Abstract: >> There exists several protocols and proposals for identifier/locator >> split which have some form of control plane by which participating >> nodes can use to share their current id to locator information with >> their peers. This document explores some of the privacy >> considerations for such a system. >> >> >> >> >> 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. >> >> The IETF Secretariat >> >> _______________________________________________ >> 5gangip mailing list >> 5gangip@ietf.org >> https://www.ietf.org/mailman/listinfo/5gangip > > _______________________________________________ > 5gangip mailing list > 5gangip@ietf.org > https://www.ietf.org/mailman/listinfo/5gangip From nobody Tue Jul 3 08:19:42 2018 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 84028130E68; Tue, 3 Jul 2018 08:19:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.4 X-Spam-Level: X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 7JZUDAxuIXlC; Tue, 3 Jul 2018 08:19:37 -0700 (PDT) Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (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 334D1130DCC; Tue, 3 Jul 2018 08:19:37 -0700 (PDT) Received: by mail-wr0-x231.google.com with SMTP id t6-v6so2381301wrn.7; Tue, 03 Jul 2018 08:19:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=43g7kDFsMCls9rBLZ5vqTlZWAQfaXqhDUHs83lCoHTU=; b=b6yB/Gc20FlKVGgFvIOEGVMyQL30ik+3NI5nOERZ2FK9R5oKEU4j55HrZqemsbfUVf 9QJzTcrkrT9z5b/gS1/CnSqPQpBDT2I+VqNRR7mCNYDpjwdqJ08ujx9JZa7KTCRM5uFo 1Rb7Qvd4hhJ8m+6HC3eBgVZj+QKaU5ZAujQLpeNGGiRHIOdVJIERvT09BThmzEZdrkEO KEMBp/LWF7/rO7xGl5iCrAO0CmKmwMg+AO2QkjSiCQmFsNACgKe9JehZDAqkor19Y3jZ ebv468RbUIwBQqmIib4U4QTihK7oLI3BUUlO/B/ovd9ClP7WkDeXgPlT4f0ysE+5zHGz dmog== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=43g7kDFsMCls9rBLZ5vqTlZWAQfaXqhDUHs83lCoHTU=; b=CagzZ1WAvqZVQL2MWwx6ue5wXB409GNT6CWrCctRSrXDurgCzXHk4PXkHws6rh0CJz Tr2ICDDY/U/7Qv8A98JLGDjl67UhdQq4lduCf2armeQMQrpuI+RwSkVBx4vO07VUkhm/ Omo8wRfr+HtQRHhjcHsTSZh0mY23IOgeYd5DPfaEIvWpBYeFRUv7/6Uk6eQTDf6NZMVN I45l0LPn2507fKHbjcqYxx2qS8fai6PNEyCTL38O0Qbg58piRlJe9HLxEWLIItcb1rFH /111jnngexX36Dx4qucgHcNkQd3tCuiFRRlEA7bYeqaCRF57ZtOE5i+1Bv1sYsJ0wUNE EsUw== X-Gm-Message-State: APt69E29lC36m2Z8HPkOxZPXb4JoJt5+Lwy5s2VTIvYSWWAX/QIzdQGo prNI3ZE1TQsJNOdkvLGWk2UmtVrCYXD9Hu9HMqE= X-Google-Smtp-Source: AAOMgpeML0MCiWZTQBxK7Zq4zLqD+z2ev2eWXZxxow7Pb63TICRyKZPjBP60XRB7IPY3Yjeb31Ky1oIyIlkyInAI+4o= X-Received: by 2002:adf:e590:: with SMTP id l16-v6mr21609173wrm.190.1530631175595; Tue, 03 Jul 2018 08:19:35 -0700 (PDT) MIME-Version: 1.0 Sender: crowcroft@gmail.com Received: by 2002:a1c:ef11:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 08:19:34 -0700 (PDT) In-Reply-To: References: <153057085187.16368.17027473724315322445.idtracker@ietfa.amsl.com> <3c9865b6-5819-ab4c-7d0d-87d36949591a@acm.org> From: Jon Crowcroft Date: Tue, 3 Jul 2018 17:19:34 +0200 X-Google-Sender-Auth: GB7Gi7DJj-LXKQShAp918tp7b_s Message-ID: To: Tom Herbert Cc: Erik Nordmark , ila@ietf.org, "lisp@ietf.org list" , dmm , 5GANGIP <5gangip@ietf.org> Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [lisp] [5gangip] Fwd: New Version Notification for draft-nordmark-id-loc-privacy-00.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 03 Jul 2018 15:19:40 -0000 beware of sidechannel attacks - eg. a sequence of efficient routes can determine a sequence of locations just from latency/rtt estimation (observe outbound data and likely return path ack packets) - you want privacy, you're gonna pay On Tue, Jul 3, 2018 at 5:14 PM, Tom Herbert wrote: > On Mon, Jul 2, 2018 at 10:01 PM, Jon Crowcroft > wrote: >> what we need is compact onion routing - maybe we could call it garlic routing. >> >> in all seriousness, if people are worried about privacy with regards >> network operators, or state actors co-ercing network operators, at >> this level, that is what you want. otherwise forget about efficient >> mobile routing - the fact is that the signature of the set of >> locations you visit is enough to re-identify a node pretty quickly - >> its been done (see wetherall's work on this a few years back on simply >> looking at sequences of wifi AP associations, without bothing with end >> system mac addr, to uniquely matc individual (indeed, find their home) >> - you have to get the threat model appropriately...and proportioately > > Jon, > > The threat is not limited to coming from network operators, it is > basically from the whole Internet. IP addresses must be sent as clear > text, and when they encode personally identifiable information then > that can be used by third parties to compromise privacy. In mobile > addresses, the threat is both comprising identity and location of the > user. Identity can be compromised when the same address (or device > specific prefix in case of RFC4941 addresses) is reused for different > flows, location is compromised when an address encodes a locator that > can be used to determine specific location. There are publicized > examples of third parties using IP addresses to expose identity and > location (e.g. https://theintercept.com/2018/03/26/facebook-data-ice-immigration/). > > In order to provide privacy in addressing, IP addresses need to be > purged of PII. This likely entails minimizing aggregation and a high > frequency of address change in a host. On the surface, this does seem > to be in conflict with "efficient mobile routing" as you mentioned, > however I don't believe that efficient routing is an acceptable trade > off for not providing adequate privacy to users. Alternatives that > achieve both goals should be investigated. > draft-herbert-ipv6-prefix-address-privacy-00 suggests "hidden > aggregation" as one possibility. > > Tom > >> >> On Mon, Jul 2, 2018 at 11:42 PM, Erik Nordmark wrote: >>> >>> This is a rough draft, but hopefully it can stimulate more discussion around >>> privacy considerations. >>> >>> -------- Forwarded Message -------- >>> Subject: New Version Notification for draft-nordmark-id-loc-privacy-00.txt >>> Date: Mon, 02 Jul 2018 15:34:11 -0700 >>> From: internet-drafts@ietf.org >>> To: Erik Nordmark >>> >>> >>> A new version of I-D, draft-nordmark-id-loc-privacy-00.txt >>> has been successfully submitted by Erik Nordmark and posted to the >>> IETF repository. >>> >>> Name: draft-nordmark-id-loc-privacy >>> Revision: 00 >>> Title: Privacy issues in ID/locator separation systems >>> Document date: 2018-07-02 >>> Group: Individual Submission >>> Pages: 6 >>> URL: >>> https://www.ietf.org/internet-drafts/draft-nordmark-id-loc-privacy-00.txt >>> Status: https://datatracker.ietf.org/doc/draft-nordmark-id-loc-privacy/ >>> Htmlized: https://tools.ietf.org/html/draft-nordmark-id-loc-privacy-00 >>> Htmlized: >>> https://datatracker.ietf.org/doc/html/draft-nordmark-id-loc-privacy >>> >>> >>> Abstract: >>> There exists several protocols and proposals for identifier/locator >>> split which have some form of control plane by which participating >>> nodes can use to share their current id to locator information with >>> their peers. This document explores some of the privacy >>> considerations for such a system. >>> >>> >>> >>> >>> 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. >>> >>> The IETF Secretariat >>> >>> _______________________________________________ >>> 5gangip mailing list >>> 5gangip@ietf.org >>> https://www.ietf.org/mailman/listinfo/5gangip >> >> _______________________________________________ >> 5gangip mailing list >> 5gangip@ietf.org >> https://www.ietf.org/mailman/listinfo/5gangip > > _______________________________________________ > 5gangip mailing list > 5gangip@ietf.org > https://www.ietf.org/mailman/listinfo/5gangip From nobody Tue Jul 3 08:34:07 2018 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 C1C26130EA5 for ; Tue, 3 Jul 2018 08:34:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-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 HA8lA9g4R3Yd for ; Tue, 3 Jul 2018 08:33:58 -0700 (PDT) Received: from mail-wr0-x22a.google.com (mail-wr0-x22a.google.com [IPv6:2a00:1450:400c:c0c::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 81147130E09 for ; Tue, 3 Jul 2018 08:33:58 -0700 (PDT) Received: by mail-wr0-x22a.google.com with SMTP id u7-v6so2412351wrn.12 for ; Tue, 03 Jul 2018 08:33:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=xeMgB5yMuPi1Cjv1lu5FgXYHouIpe+QoOwAhrLzTXXM=; b=WFS8IwWbf3Rno8hGvaD7OiZoer8dsGeI7HCWhCDAKLZsel0kpZM3+Q8w+Mstf3TL1O EhO92gJ6iaKHqNHMqTYCkTtVhz9PQG0jriVefuIS3AiU4j6mxXH5uie5ckaKb07n9nBN DATEO6SDWHKFs/rtkbRNhQFhjPAso6rTMZE6yt0sz/hqkL95r9JHADhk/tDTNqUM7JIz h2P6btbgB/zUv9VDUfQQsysfbVUXWhIWjMMQMNaiEZ7Iw1ax8jQcO1SIhv0VbNPhUomr RCxr4pLaXfmZXpACDwx2GHX9ig3mCW+lLVnIXk0Dw9pL8lu6NjWE/Ise1lacA9AErb+x ON4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=xeMgB5yMuPi1Cjv1lu5FgXYHouIpe+QoOwAhrLzTXXM=; b=a8leWO1cpBHZbc+Lgk4VlJzltbfK+Jrrwv0QX1ZxXpvTW3fnzSQGdUq6ZLMshj/WJD dYv5Yc4rXA53vr8aNQ9USBumaGGbVEz12BQw97po/nmD/d+XeY5KwsesPBeNTNK6b2A7 WpDANqdtxEh1rvnOCjjVOrJn7HEJfQJGV/II3zcG3UQGK3REbtvQiJj8OywE9DiT/wbb iDch4Fwj3fOBgJY8tOuA9TqGwqgfXtQih0NPew/srrXFHJuU8qCv1W7Qs4tNYcVywDvi umfnhXGe1FJ519tI8aHuKghcbWPMf+jM7KfUwJN2vIRknKddNn7gB89ePpU+OR7SJ9Xv aFmg== X-Gm-Message-State: APt69E33HzMxc2WK/CeBxATtGSl6ka8q7tsKLhSdsmbWxsnheWqSFWQe A10mr5v01YdnLseqVunKwS5JqgfkSBhufxggdL/kYQ== X-Google-Smtp-Source: AAOMgpe6WgxRN8O9Jk9HFVTjCff6Q0t+gkXwgJ+PdIfxmQbpdwqVVxi2OhpEtVergdjPpGMPDnnhPEF9/gZCbAXQpIU= X-Received: by 2002:adf:a056:: with SMTP id l22-v6mr2123756wrl.153.1530632036864; Tue, 03 Jul 2018 08:33:56 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:fa86:0:0:0:0:0 with HTTP; Tue, 3 Jul 2018 08:33:56 -0700 (PDT) In-Reply-To: References: <153057085187.16368.17027473724315322445.idtracker@ietfa.amsl.com> <3c9865b6-5819-ab4c-7d0d-87d36949591a@acm.org> From: Tom Herbert Date: Tue, 3 Jul 2018 08:33:56 -0700 Message-ID: To: Jon Crowcroft Cc: Erik Nordmark , ila@ietf.org, "lisp@ietf.org list" , dmm , 5GANGIP <5gangip@ietf.org> Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [lisp] [5gangip] Fwd: New Version Notification for draft-nordmark-id-loc-privacy-00.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 03 Jul 2018 15:34:03 -0000 On Tue, Jul 3, 2018 at 8:19 AM, Jon Crowcroft wrote: > beware of sidechannel attacks - eg. a sequence of efficient routes can > determine a sequence of locations just from latency/rtt estimation > (observe outbound data and likely return path ack packets) - you want > privacy, you're gonna pay > Yep, we also know there is a lot of effort being done to extract information from cipher text like apply machine learning to the data. As compute and data acquisition techniques advance, attacks on the Internet only get more sophisticated. Work will always be needed to mitigate new attacks and that will have cost. It's a never ending problem, but it's worth it to continually try to solve IMHO. Tom > On Tue, Jul 3, 2018 at 5:14 PM, Tom Herbert wrote: >> On Mon, Jul 2, 2018 at 10:01 PM, Jon Crowcroft >> wrote: >>> what we need is compact onion routing - maybe we could call it garlic routing. >>> >>> in all seriousness, if people are worried about privacy with regards >>> network operators, or state actors co-ercing network operators, at >>> this level, that is what you want. otherwise forget about efficient >>> mobile routing - the fact is that the signature of the set of >>> locations you visit is enough to re-identify a node pretty quickly - >>> its been done (see wetherall's work on this a few years back on simply >>> looking at sequences of wifi AP associations, without bothing with end >>> system mac addr, to uniquely matc individual (indeed, find their home) >>> - you have to get the threat model appropriately...and proportioately >> >> Jon, >> >> The threat is not limited to coming from network operators, it is >> basically from the whole Internet. IP addresses must be sent as clear >> text, and when they encode personally identifiable information then >> that can be used by third parties to compromise privacy. In mobile >> addresses, the threat is both comprising identity and location of the >> user. Identity can be compromised when the same address (or device >> specific prefix in case of RFC4941 addresses) is reused for different >> flows, location is compromised when an address encodes a locator that >> can be used to determine specific location. There are publicized >> examples of third parties using IP addresses to expose identity and >> location (e.g. https://theintercept.com/2018/03/26/facebook-data-ice-immigration/). >> >> In order to provide privacy in addressing, IP addresses need to be >> purged of PII. This likely entails minimizing aggregation and a high >> frequency of address change in a host. On the surface, this does seem >> to be in conflict with "efficient mobile routing" as you mentioned, >> however I don't believe that efficient routing is an acceptable trade >> off for not providing adequate privacy to users. Alternatives that >> achieve both goals should be investigated. >> draft-herbert-ipv6-prefix-address-privacy-00 suggests "hidden >> aggregation" as one possibility. >> >> Tom >> >>> >>> On Mon, Jul 2, 2018 at 11:42 PM, Erik Nordmark wrote: >>>> >>>> This is a rough draft, but hopefully it can stimulate more discussion around >>>> privacy considerations. >>>> >>>> -------- Forwarded Message -------- >>>> Subject: New Version Notification for draft-nordmark-id-loc-privacy-00.txt >>>> Date: Mon, 02 Jul 2018 15:34:11 -0700 >>>> From: internet-drafts@ietf.org >>>> To: Erik Nordmark >>>> >>>> >>>> A new version of I-D, draft-nordmark-id-loc-privacy-00.txt >>>> has been successfully submitted by Erik Nordmark and posted to the >>>> IETF repository. >>>> >>>> Name: draft-nordmark-id-loc-privacy >>>> Revision: 00 >>>> Title: Privacy issues in ID/locator separation systems >>>> Document date: 2018-07-02 >>>> Group: Individual Submission >>>> Pages: 6 >>>> URL: >>>> https://www.ietf.org/internet-drafts/draft-nordmark-id-loc-privacy-00.txt >>>> Status: https://datatracker.ietf.org/doc/draft-nordmark-id-loc-privacy/ >>>> Htmlized: https://tools.ietf.org/html/draft-nordmark-id-loc-privacy-00 >>>> Htmlized: >>>> https://datatracker.ietf.org/doc/html/draft-nordmark-id-loc-privacy >>>> >>>> >>>> Abstract: >>>> There exists several protocols and proposals for identifier/locator >>>> split which have some form of control plane by which participating >>>> nodes can use to share their current id to locator information with >>>> their peers. This document explores some of the privacy >>>> considerations for such a system. >>>> >>>> >>>> >>>> >>>> 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. >>>> >>>> The IETF Secretariat >>>> >>>> _______________________________________________ >>>> 5gangip mailing list >>>> 5gangip@ietf.org >>>> https://www.ietf.org/mailman/listinfo/5gangip >>> >>> _______________________________________________ >>> 5gangip mailing list >>> 5gangip@ietf.org >>> https://www.ietf.org/mailman/listinfo/5gangip >> >> _______________________________________________ >> 5gangip mailing list >> 5gangip@ietf.org >> https://www.ietf.org/mailman/listinfo/5gangip From nobody Tue Jul 3 08:37:16 2018 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 5B710130EBB; Tue, 3 Jul 2018 08:36:54 -0700 (PDT) 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] 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 dZCYrHGkhZrH; Tue, 3 Jul 2018 08:36:48 -0700 (PDT) Received: from mta2.cl.cam.ac.uk (mta2.cl.cam.ac.uk [IPv6:2001:630:212:200::25:2]) (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 93358130F67; Tue, 3 Jul 2018 08:36:48 -0700 (PDT) Received: from ely.cl.cam.ac.uk ([2001:630:212:238:230:48ff:fefe:c314]) by mta2.cl.cam.ac.uk with esmtp (Exim 4.86_2) (envelope-from ) id 1faNME-0002QN-Lg; Tue, 03 Jul 2018 16:36:46 +0100 From: Jon Crowcroft To: Tom Herbert cc: Erik Nordmark , ila@ietf.org, "lisp@ietf.org list" , dmm , 5GANGIP <5gangip@ietf.org> In-reply-to: References: <153057085187.16368.17027473724315322445.idtracker@ietfa.amsl.com> <3c9865b6-5819-ab4c-7d0d-87d36949591a@acm.org> Comments: In-reply-to Tom Herbert message dated "Tue, 03 Jul 2018 08:33:56 -0700." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <20756.1530632206.1@ely.cl.cam.ac.uk> Date: Tue, 03 Jul 2018 16:36:46 +0100 Message-Id: Archived-At: Subject: Re: [lisp] [5gangip] Fwd: New Version Notification for draft-nordmark-id-loc-privacy-00.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 03 Jul 2018 15:36:55 -0000 agree...of course... just we need to start adding security +cost+ considerations... to drafts > On Tue, Jul 3, 2018 at 8:19 AM, Jon Crowcroft > wrote: > > beware of sidechannel attacks - eg. a sequence of efficient routes can > > determine a sequence of locations just from latency/rtt estimation > > (observe outbound data and likely return path ack packets) - you want > > privacy, you're gonna pay > > > > Yep, we also know there is a lot of effort being done to extract > information from cipher text like apply machine learning to the data. > As compute and data acquisition techniques advance, attacks on the > Internet only get more sophisticated. Work will always be needed to > mitigate new attacks and that will have cost. It's a never ending > problem, but it's worth it to continually try to solve IMHO. > > Tom > > > > On Tue, Jul 3, 2018 at 5:14 PM, Tom Herbert wrote: > >> On Mon, Jul 2, 2018 at 10:01 PM, Jon Crowcroft > >> wrote: > >>> what we need is compact onion routing - maybe we could call it garlic > routing. > >>> > >>> in all seriousness, if people are worried about privacy with regards > >>> network operators, or state actors co-ercing network operators, at > >>> this level, that is what you want. otherwise forget about efficient > >>> mobile routing - the fact is that the signature of the set of > >>> locations you visit is enough to re-identify a node pretty quickly - > >>> its been done (see wetherall's work on this a few years back on simply > >>> looking at sequences of wifi AP associations, without bothing with end > >>> system mac addr, to uniquely matc individual (indeed, find their home) > >>> - you have to get the threat model appropriately...and proportioately > >> > >> Jon, > >> > >> The threat is not limited to coming from network operators, it is > >> basically from the whole Internet. IP addresses must be sent as clear > >> text, and when they encode personally identifiable information then > >> that can be used by third parties to compromise privacy. In mobile > >> addresses, the threat is both comprising identity and location of the > >> user. Identity can be compromised when the same address (or device > >> specific prefix in case of RFC4941 addresses) is reused for different > >> flows, location is compromised when an address encodes a locator that > >> can be used to determine specific location. There are publicized > >> examples of third parties using IP addresses to expose identity and > >> location (e.g. > https://theintercept.com/2018/03/26/facebook-data-ice-immigration/). > >> > >> In order to provide privacy in addressing, IP addresses need to be > >> purged of PII. This likely entails minimizing aggregation and a high > >> frequency of address change in a host. On the surface, this does seem > >> to be in conflict with "efficient mobile routing" as you mentioned, > >> however I don't believe that efficient routing is an acceptable trade > >> off for not providing adequate privacy to users. Alternatives that > >> achieve both goals should be investigated. > >> draft-herbert-ipv6-prefix-address-privacy-00 suggests "hidden > >> aggregation" as one possibility. > >> > >> Tom > >> > >>> > >>> On Mon, Jul 2, 2018 at 11:42 PM, Erik Nordmark > wrote: > >>>> > >>>> This is a rough draft, but hopefully it can stimulate more > discussion around > >>>> privacy considerations. > >>>> > >>>> -------- Forwarded Message -------- > >>>> Subject: New Version Notification for > draft-nordmark-id-loc-privacy-00.txt > >>>> Date: Mon, 02 Jul 2018 15:34:11 -0700 > >>>> From: internet-drafts@ietf.org > >>>> To: Erik Nordmark > >>>> > >>>> > >>>> A new version of I-D, draft-nordmark-id-loc-privacy-00.txt > >>>> has been successfully submitted by Erik Nordmark and posted to the > >>>> IETF repository. > >>>> > >>>> Name: draft-nordmark-id-loc-privacy > >>>> Revision: 00 > >>>> Title: Privacy issues in ID/locator separation systems > >>>> Document date: 2018-07-02 > >>>> Group: Individual Submission > >>>> Pages: 6 > >>>> URL: > >>>> > https://www.ietf.org/internet-drafts/draft-nordmark-id-loc-privacy-00.txt > >>>> Status: > https://datatracker.ietf.org/doc/draft-nordmark-id-loc-privacy/ > >>>> Htmlized: > https://tools.ietf.org/html/draft-nordmark-id-loc-privacy-00 > >>>> Htmlized: > >>>> https://datatracker.ietf.org/doc/html/draft-nordmark-id-loc-privacy > >>>> > >>>> > >>>> Abstract: > >>>> There exists several protocols and proposals for > identifier/locator > >>>> split which have some form of control plane by which participating > >>>> nodes can use to share their current id to locator information > with > >>>> their peers. This document explores some of the privacy > >>>> considerations for such a system. > >>>> > >>>> > >>>> > >>>> > >>>> 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. > >>>> > >>>> The IETF Secretariat > >>>> > >>>> _______________________________________________ > >>>> 5gangip mailing list > >>>> 5gangip@ietf.org > >>>> https://www.ietf.org/mailman/listinfo/5gangip > >>> > >>> _______________________________________________ > >>> 5gangip mailing list > >>> 5gangip@ietf.org > >>> https://www.ietf.org/mailman/listinfo/5gangip > >> > >> _______________________________________________ > >> 5gangip mailing list > >> 5gangip@ietf.org > >> https://www.ietf.org/mailman/listinfo/5gangip > From nobody Tue Jul 3 09:04:47 2018 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 44376131065; Tue, 3 Jul 2018 09:00:21 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: lisp@ietf.org, db3546@att.com X-Test-IDTracker: no X-IETF-IDTracker: 6.81.3 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153063362127.4893.1401622142931927161.idtracker@ietfa.amsl.com> Date: Tue, 03 Jul 2018 09:00:21 -0700 Archived-At: Subject: [lisp] lisp - Requested session has been scheduled for IETF 102 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 03 Jul 2018 16:00:31 -0000 Dear Liz Flynn, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. lisp Session 1 (2:00 requested) Thursday, 19 July 2018, Afternoon Session I 1330-1530 Room Name: Van Horne size: 130 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/102/sessions/lisp.ics Request Information: --------------------------------------------------------- Working Group Name: Locator/ID Separation Protocol Area Name: Routing Area Session Requester: Liz Flynn Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 50 Conflicts to Avoid: First Priority: rtgwg nvo3 i2rs sidr grow sfc nfvrg pim intarea Second Priority: mboned icnrg irtfopen idr spring bier maprg Third Priority: bess People who must be present: Joel M. Halpern Wassim Haddad Deborah Brungard Luigi Iannone Padma Pillay-Esnault Resources Requested: Special Requests: --------------------------------------------------------- From nobody Tue Jul 3 12:00:05 2018 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 4E747130DEA for ; Tue, 3 Jul 2018 12:00:01 -0700 (PDT) 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 cfGq7uhhaIh2 for ; Tue, 3 Jul 2018 11:59:57 -0700 (PDT) Received: from mail-lf0-x232.google.com (mail-lf0-x232.google.com [IPv6:2a00:1450:4010:c07::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 128F0130DD8 for ; Tue, 3 Jul 2018 11:59:57 -0700 (PDT) Received: by mail-lf0-x232.google.com with SMTP id u202-v6so2443649lff.9 for ; Tue, 03 Jul 2018 11:59:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JlKdRoKaDa6I/sEMy+HTRoFQ6XkCNpKYMyphcGLSaGs=; b=hbc4HcRMMOgOBwAFjWUz673OeiF7r9zoYdkvfGVfb7G+wlWscUr7FR8MShjO4O7tjQ e3EJk5DjXBMjNDYJc3r787DXL5NQTLw8Odu4HvZKRCWNWHGKmY2qwsdrQ6O5jTWrGHNz 1fTL9HMx9zKLTk+++8GSYz3f7kSPPBRTI9im9jKX5ZI/kTcCFKCEELKU6oUAN8oX6x45 uiTaZSpYDJ4OaSJtfTnuVlcsb+3K2S40cFQigorr0b9/2gCvpNwJgNnKsFDneo9aoiGF e/GqovpKy8AlCQqb25LoD0XwM6deXcl1nOZoKY8MI2uXG1SdWNlzPkOvBVzu48Ci73a2 nKYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JlKdRoKaDa6I/sEMy+HTRoFQ6XkCNpKYMyphcGLSaGs=; b=nxnvyq31O/EYrm7EzZoNmqI0jeW4Q14dLzT7RlmoAe+Yt2/LyjRJEgEPj/5hABFRYp JBnHLOVN66NaYZ45U/o3wbMrOU+e/UaD13KpA1flek5IIZZznmRnDkdA3uD/PYx3qT53 N3VcM95OAek2i14cGj5sASzPw4KWSeTcKPHm31wAz6KOp01WIaJYEMfRr4xDmytX1lVi PjquFuZQgBzyuPlNFQh21ou0JdYq2ZrbTPbSTPgY3HKzap6i00n3akeSymuKdoir15mL G2iGOcs4TnxKjWD3D1jYoYMdlMlGvEzLzNOS+yN5bi6Nja+wHJM8ChhNJMvSRD8plKa2 Ul3w== X-Gm-Message-State: APt69E2L8DIc0ibxVDdxorADEhatXOCgQWmhbMuRgBfI9yZpmik1cu5V 65C+q2LNQmaPUSdFj8FZQdUEeb0wHI0ayLaVFNA8qVoW X-Google-Smtp-Source: AAOMgpekLjHViXbrRH5NdmmaXVNsC18FF2pdvkiCwHh58EpsAcu/DfdwMyegsIozZFfgIq8vHR4EWSmqKt1paoBCUHM= X-Received: by 2002:a19:d890:: with SMTP id r16-v6mr13250010lfi.7.1530644395170; Tue, 03 Jul 2018 11:59:55 -0700 (PDT) MIME-Version: 1.0 References: <650BB047-3B72-4C20-9FE1-9C11BC54FCDA@gigix.net> In-Reply-To: From: Alberto Rodriguez-Natal Date: Tue, 3 Jul 2018 11:59:43 -0700 Message-ID: To: Luigi Iannone Cc: "lisp@ietf.org list" Content-Type: multipart/alternative; boundary="00000000000073a13f05701ceb66" Archived-At: Subject: Re: [lisp] Review draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 03 Jul 2018 19:00:02 -0000 --00000000000073a13f05701ceb66 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi all, After a long delay we have finally pushed an updated version of the Vendor Specific LCAF [1] addressing the editorial comments from Luigi. There was rough consensus in London about moving this to last call. Luigi/Joel, let me know if we can move forward with this one or if anything else is needed on our end. Thanks! Alberto [1] https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02 On Sun, Mar 18, 2018 at 11:38 AM Alberto Rodriguez-Natal < rodrigueznatal@gmail.com> wrote: > Thanks for the review Luigi. All the proposed changes look good. We'll > update the draft to reflect them. > > Thanks! > Alberto > > On Sun, Mar 18, 2018 at 4:35 PM, Luigi Iannone wrote: > > > > Hi All, > > I did a quick review of the short vendor LCAF document. > > My few comment are inline. > > > > Ciao > > > > L. > > > > > > > > > > > > > > > > > > LISP Working Group A. Rodriguez-Nata= l > > Internet-Draft V. Ermaga= n > > Intended status: Experimental A. Smirno= v > > Expires: August 20, 2018 V. Ashtaputr= e > > Cisco System= s > > D. Farinacc= i > > lispers.ne= t > > 2 16, 201= 8 > > > > > > Vendor Specific LCAF > > draft-ietf-lisp-vendor-lcaf-01 > > > > Abstract > > > > This document describes a new LCAF for LISP, the Vendor Specific > > > > I would but in both the title and the first sentence of the abstract th= e > > long version of the LCAF acronym: > > =E2=80=9CLISP Canonical Address Format (LCAF)" > > > > > > LCAF. This LCAF enables organizations to have internal encodings fo= r > > LCAF addresses. > > > > Status of This Memo > > > > This Internet-Draft is submitted in full conformance with the > > provisions of BCP 78 and BCP 79. > > > > Internet-Drafts are working documents of the Internet Engineering > > Task Force (IETF). Note that other groups may also distribute > > working documents as Internet-Drafts. The list of current Internet- > > Drafts is at https://datatracker.ietf.org/drafts/current/. > > > > Internet-Drafts are draft documents valid for a maximum of six month= s > > and may be updated, replaced, or obsoleted by other documents at any > > time. It is inappropriate to use Internet-Drafts as reference > > material or to cite them other than as "work in progress." > > > > This Internet-Draft will expire on August 20, 2018. > > > > Copyright Notice > > > > Copyright (c) 2018 IETF Trust and the persons identified as the > > document authors. All rights reserved. > > > > This document is subject to BCP 78 and the IETF Trust's Legal > > Provisions Relating to IETF Documents > > (https://trustee.ietf.org/license-info) in effect on the date of > > publication of this document. Please review these documents > > carefully, as they describe your rights and restrictions with respec= t > > to this document. Code Components extracted from this document must > > include Simplified BSD License text as described in Section 4.e of > > > > > > > > Rodriguez-Natal, et al. Expires August 20, 2018 [Page 1= ] > > > > Internet-Draft LISP-Vendor-LCAF 2 201= 8 > > > > > > the Trust Legal Provisions and are provided without warranty as > > described in the Simplified BSD License. > > > > Table of Contents > > > > 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . = 2 > > 2. Requirements Language . . . . . . . . . . . . . . . . . . . . = 2 > > 3. Vendor Specific LCAF . . . . . . . . . . . . . . . . . . . . = 2 > > 4. Security Considerations . . . . . . . . . . . . . . . . . . . = 3 > > 5. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . = 3 > > 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . = 4 > > 7. Normative References . . . . . . . . . . . . . . . . . . . . = 4 > > Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . = 4 > > > > 1. Introduction > > > > The LISP Canonical Address Format > > > > add: =E2=80=9C(LCAF)" > > > > [RFC8060] defines the format and > > encoding for different address types that can be used on LISP > > [RFC6830] > > > > I would put 6830bis and 6833bis as reference since they are standard > track. > > > > deployments. However, certain deployments require specific > > format encodings that may not be applicable outside of the use-case > > for which they are defined. The Vendor Specific LCAF allows > > organizations to create LCAF addresses to be used only internally on > > particular LISP deployments. > > > > 2. Requirements Language > > > > The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", > > "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this > > document are to be interpreted as described in [RFC2119] > > > > 3. Vendor Specific LCAF > > > > The Vendor Specific LCAF relies on using the IEEE Organizationally > > Unique Identifier (OUI) [IEEE.802_2001] to prevent collisions across > > vendors or organizations using the LCAF. The format of the Vendor > > Specific LCAF is provided below. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Rodriguez-Natal, et al. Expires August 20, 2018 [Page 2= ] > > > > Internet-Draft LISP-Vendor-LCAF 2 201= 8 > > > > > > 0 1 2 3 > > 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > | AFI =3D 16387 | Rsvd1 | Flags = | > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > | Type =3D 255 | Rsvd2 | Length = | > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > | Rsvd3 | Organizationally Unique Identifier (OUI) | > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > | Internal format... | > > +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ > > > > Vendor Specific LCAF > > > > The Vendor Specific LCAF has the following fields. > > > > Rsvd3: This 8-bit field is reserved for future use. It MUST be > > set to 0 on transmit and MUST be ignored on receipt. > > > > Organizationally Unique Identifier (OUI): This is a 24-bit field > > that carries the IEEE OUI [IEEE.802_2001] of the organization. > > > > Internal format: This is a variable length field that is left > > undefined on purpose. Each vendor or organization can define its > > own internal format(s) to use with the Vendor Specific LCAF. > > > > The definition for the rest of the fields can be found in [RFC8060]. > > > > The Vendor Specific LCAF type SHOULD not be used in deployments wher= e > > different organizations interoperate. If a LISP device receives a > > LISP message containing a Vendor Specific LCAF with an OUI that it > > does not understand, it SHOULD drop the message and a log action MUS= T > > be taken. > > > > 4. Security Considerations > > > > This document enables organizations to define new LCAFs for their > > internal use. It is the responsibility of these organizations to > > properly assess the security implications of the formats they define= . > > > > 5. Acknowledgments > > > > The authors would like to thank Joel Halpern for his suggestions and > > comments regarding this document. > > > > > > > > > > > > > > > > Rodriguez-Natal, et al. Expires August 20, 2018 [Page 3= ] > > > > Internet-Draft LISP-Vendor-LCAF 2 201= 8 > > > > > > 6. IANA Considerations > > > > Following the guidelines of [RFC5226], > > > > RFC5226 is obsoleted by RFC 8126, this should be updated > > > > that=E2=80=99s all :-) > > > > L. > > > > > > > > > > _______________________________________________ > > lisp mailing list > > lisp@ietf.org > > https://www.ietf.org/mailman/listinfo/lisp > > > --00000000000073a13f05701ceb66 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

After a long delay w= e have finally pushed an updated version of the Vendor Specific LCAF [1] ad= dressing the editorial comments from Luigi. There was rough consensus in Lo= ndon about moving this to last call.

Luigi/Joel, l= et me know if we can move forward with this one or if anything else is need= ed on our end.

Thanks!

On Sun, Mar 18, 2018 at 11:38 AM Alberto Rodriguez-Natal <rodrigueznatal@gmail.com> w= rote:
Thanks for the review Luigi. = All the proposed changes look good. We'll
update the draft to reflect them.

Thanks!
Alberto

On Sun, Mar 18, 2018 at 4:35 PM, Luigi Iannone <ggx@gigix.net> wrote:
>
> Hi All,
> I did a quick review of the short vendor LCAF document.
> My few comment are inline.
>
> Ciao
>
> L.
>
>
>
>
>
>
>
>
> LISP Working Group=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 A= . Rodriguez-Natal
> Internet-Draft=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 V. Ermagan
> Intended status: Experimental=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0= =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0A. Smirnov
> Expires: August 20, 2018=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0V. Ashtaputre
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Cisco Sy= stems
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0D.= Farinacci
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <= a href=3D"http://lispers.net" rel=3D"noreferrer" target=3D"_blank">lispers.= net
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A02 16, 2018
>
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0Vendor Specific LCAF
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 draft-ietf-lisp-vendor-lcaf-01
>
> Abstract
>
>=C2=A0 =C2=A0 This document describes a new LCAF for LISP, the Vendor S= pecific
>
> I would but in both the title and the first sentence of the abstract t= he
> long version of the LCAF acronym:
> =E2=80=9CLISP Canonical Address Format (LCAF)"
>
>
>=C2=A0 =C2=A0 LCAF.=C2=A0 This LCAF enables organizations to have inter= nal encodings for
>=C2=A0 =C2=A0 LCAF addresses.
>
> Status of This Memo
>
>=C2=A0 =C2=A0 This Internet-Draft is submitted in full conformance with= the
>=C2=A0 =C2=A0 provisions of BCP 78 and BCP 79.
>
>=C2=A0 =C2=A0 Internet-Drafts are working documents of the Internet Eng= ineering
>=C2=A0 =C2=A0 Task Force (IETF).=C2=A0 Note that other groups may also = distribute
>=C2=A0 =C2=A0 working documents as Internet-Drafts.=C2=A0 The list of c= urrent Internet-
>=C2=A0 =C2=A0 Drafts is at https://datatracker.ietf.= org/drafts/current/.
>
>=C2=A0 =C2=A0 Internet-Drafts are draft documents valid for a maximum o= f six months
>=C2=A0 =C2=A0 and may be updated, replaced, or obsoleted by other docum= ents at any
>=C2=A0 =C2=A0 time.=C2=A0 It is inappropriate to use Internet-Drafts as= reference
>=C2=A0 =C2=A0 material or to cite them other than as "work in prog= ress."
>
>=C2=A0 =C2=A0 This Internet-Draft will expire on August 20, 2018.
>
> Copyright Notice
>
>=C2=A0 =C2=A0 Copyright (c) 2018 IETF Trust and the persons identified = as the
>=C2=A0 =C2=A0 document authors.=C2=A0 All rights reserved.
>
>=C2=A0 =C2=A0 This document is subject to BCP 78 and the IETF Trust'= ;s Legal
>=C2=A0 =C2=A0 Provisions Relating to IETF Documents
>=C2=A0 =C2=A0 (https://trustee.ietf.org/license-info) i= n effect on the date of
>=C2=A0 =C2=A0 publication of this document.=C2=A0 Please review these d= ocuments
>=C2=A0 =C2=A0 carefully, as they describe your rights and restrictions = with respect
>=C2=A0 =C2=A0 to this document.=C2=A0 Code Components extracted from th= is document must
>=C2=A0 =C2=A0 include Simplified BSD License text as described in Secti= on 4.e of
>
>
>
> Rodriguez-Natal, et al.=C2=A0 Expires August 20, 2018=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [Page 1]
>
> Internet-Draft=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 LISP-Ve= ndor-LCAF=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 2 2018
>
>
>=C2=A0 =C2=A0 the Trust Legal Provisions and are provided without warra= nty as
>=C2=A0 =C2=A0 described in the Simplified BSD License.
>
> Table of Contents
>
>=C2=A0 =C2=A0 1.=C2=A0 Introduction=C2=A0 . . . . . . . . . . . . . . .= . . . . . . . . .=C2=A0 =C2=A02
>=C2=A0 =C2=A0 2.=C2=A0 Requirements Language . . . . . . . . . . . . . = . . . . . . .=C2=A0 =C2=A02
>=C2=A0 =C2=A0 3.=C2=A0 Vendor Specific LCAF=C2=A0 . . . . . . . . . . .= . . . . . . . . .=C2=A0 =C2=A02
>=C2=A0 =C2=A0 4.=C2=A0 Security Considerations . . . . . . . . . . . . = . . . . . . .=C2=A0 =C2=A03
>=C2=A0 =C2=A0 5.=C2=A0 Acknowledgments . . . . . . . . . . . . . . . . = . . . . . . .=C2=A0 =C2=A03
>=C2=A0 =C2=A0 6.=C2=A0 IANA Considerations . . . . . . . . . . . . . . = . . . . . . .=C2=A0 =C2=A04
>=C2=A0 =C2=A0 7.=C2=A0 Normative References=C2=A0 . . . . . . . . . . .= . . . . . . . . .=C2=A0 =C2=A04
>=C2=A0 =C2=A0 Authors' Addresses=C2=A0 . . . . . . . . . . . . . . = . . . . . . . . .=C2=A0 =C2=A04
>
> 1.=C2=A0 Introduction
>
>=C2=A0 =C2=A0 The LISP Canonical Address Format
>
> add: =E2=80=9C(LCAF)"
>
> [RFC8060] defines the format and
>=C2=A0 =C2=A0 encoding for different address types that can be used on = LISP
>=C2=A0 =C2=A0 [RFC6830]
>
> I would put 6830bis and 6833bis as reference since they are standard t= rack.
>
> deployments.=C2=A0 However, certain deployments require specific
>=C2=A0 =C2=A0 format encodings that may not be applicable outside of th= e use-case
>=C2=A0 =C2=A0 for which they are defined.=C2=A0 The Vendor Specific LCA= F allows
>=C2=A0 =C2=A0 organizations to create LCAF addresses to be used only in= ternally on
>=C2=A0 =C2=A0 particular LISP deployments.
>
> 2.=C2=A0 Requirements Language
>
>=C2=A0 =C2=A0 The key words "MUST", "MUST NOT", &qu= ot;REQUIRED", "SHALL", "SHALL NOT",
>=C2=A0 =C2=A0 "SHOULD", "SHOULD NOT", "RECOMME= NDED", "MAY", and "OPTIONAL" in this
>=C2=A0 =C2=A0 document are to be interpreted as described in [RFC2119]<= br> >
> 3.=C2=A0 Vendor Specific LCAF
>
>=C2=A0 =C2=A0 The Vendor Specific LCAF relies on using the IEEE Organiz= ationally
>=C2=A0 =C2=A0 Unique Identifier (OUI) [IEEE.802_2001] to prevent collis= ions across
>=C2=A0 =C2=A0 vendors or organizations using the LCAF.=C2=A0 The format= of the Vendor
>=C2=A0 =C2=A0 Specific LCAF is provided below.
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Rodriguez-Natal, et al.=C2=A0 Expires August 20, 2018=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [Page 2]
>
> Internet-Draft=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 LISP-Ve= ndor-LCAF=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 2 2018
>
>
>=C2=A0 =C2=A0 =C2=A0 0=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A01=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A02=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A03
>=C2=A0 =C2=A0 =C2=A0 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 = 5 6 7 8 9 0 1
>=C2=A0 =C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-= +-+-+-+-+-+-+-+
>=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0AFI =3D = 16387=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0Rsvd1=C2=A0 =C2= =A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0Flags=C2=A0 =C2=A0 =C2=A0|
>=C2=A0 =C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-= +-+-+-+-+-+-+-+
>=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0Type =3D 255=C2=A0 |=C2=A0 =C2=A0 = =C2=A0Rsvd2=C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 L= ength=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|
>=C2=A0 =C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-= +-+-+-+-+-+-+-+
>=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 Rsvd3=C2=A0 =C2=A0 |=C2=A0 = =C2=A0 Organizationally Unique Identifier (OUI)=C2=A0 =C2=A0|
>=C2=A0 =C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-= +-+-+-+-+-+-+-+
>=C2=A0 =C2=A0 =C2=A0 |=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Internal format...=C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|
>=C2=A0 =C2=A0 =C2=A0 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-= +-+-+-+-+-+-+-+
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 Vendor Specific LCAF
>
>=C2=A0 =C2=A0 The Vendor Specific LCAF has the following fields.
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Rsvd3: This 8-bit field is reserved for futu= re use.=C2=A0 It MUST be
>=C2=A0 =C2=A0 =C2=A0 =C2=A0set to 0 on transmit and MUST be ignored on = receipt.
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Organizationally Unique Identifier (OUI): Th= is is a 24-bit field
>=C2=A0 =C2=A0 =C2=A0 =C2=A0that carries the IEEE OUI [IEEE.802_2001] of= the organization.
>
>=C2=A0 =C2=A0 =C2=A0 =C2=A0Internal format: This is a variable length f= ield that is left
>=C2=A0 =C2=A0 =C2=A0 =C2=A0undefined on purpose.=C2=A0 Each vendor or o= rganization can define its
>=C2=A0 =C2=A0 =C2=A0 =C2=A0own internal format(s) to use with the Vendo= r Specific LCAF.
>
>=C2=A0 =C2=A0 The definition for the rest of the fields can be found in= [RFC8060].
>
>=C2=A0 =C2=A0 The Vendor Specific LCAF type SHOULD not be used in deplo= yments where
>=C2=A0 =C2=A0 different organizations interoperate.=C2=A0 If a LISP dev= ice receives a
>=C2=A0 =C2=A0 LISP message containing a Vendor Specific LCAF with an OU= I that it
>=C2=A0 =C2=A0 does not understand, it SHOULD drop the message and a log= action MUST
>=C2=A0 =C2=A0 be taken.
>
> 4.=C2=A0 Security Considerations
>
>=C2=A0 =C2=A0 This document enables organizations to define new LCAFs f= or their
>=C2=A0 =C2=A0 internal use.=C2=A0 It is the responsibility of these org= anizations to
>=C2=A0 =C2=A0 properly assess the security implications of the formats = they define.
>
> 5.=C2=A0 Acknowledgments
>
>=C2=A0 =C2=A0 The authors would like to thank Joel Halpern for his sugg= estions and
>=C2=A0 =C2=A0 comments regarding this document.
>
>
>
>
>
>
>
> Rodriguez-Natal, et al.=C2=A0 Expires August 20, 2018=C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [Page 3]
>
> Internet-Draft=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 LISP-Ve= ndor-LCAF=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 2 2018
>
>
> 6.=C2=A0 IANA Considerations
>
>=C2=A0 =C2=A0 Following the guidelines of [RFC5226],
>
> RFC5226 is obsoleted by RFC 8126, this should be updated
>
> that=E2=80=99s all :-)
>
> L.
>
>
>
>
> _______________________________________________
> lisp mailing list
> lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp
>
--00000000000073a13f05701ceb66-- From nobody Tue Jul 3 18:20:12 2018 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 B0ECB12D949; Tue, 3 Jul 2018 18:20:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 nB6mLde27o0t; Tue, 3 Jul 2018 18:20:08 -0700 (PDT) Received: from mail-lf0-x22d.google.com (mail-lf0-x22d.google.com [IPv6:2a00:1450:4010:c07::22d]) (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 CA05F1292F1; Tue, 3 Jul 2018 18:20:07 -0700 (PDT) Received: by mail-lf0-x22d.google.com with SMTP id u202-v6so3035619lff.9; Tue, 03 Jul 2018 18:20:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xHuSKHcqWAtnMCTMUjpg44+kvPh/xd0uugoOde8G9QY=; b=m2ohFWMIqhwFugAoISLugr2Y6lK3MBGFZN0qb9qb9VERIV2AtHXEubCpVkiqXUUroZ QCUI6WPjq8qIuj+b6WAYN8HWqj/ROxaN3qII3rDLnxKmBfQsNBwv1d2iRTS2OqIZfrnz bOUo75TmgoO8+l1u/liWe8SxUlxR9qw4gXQu0Dki3w0GqVcawJEPVu9culXhRvGANUdW KGbNn2SOGLn4flzobpP7szeM+SjUr4sGfc5zvEa3Mn96nBYsOVfOmpaNpl9wW33I+ou3 zcJ+o40468sPYyxNo9SVVugE/NQvVMy8BGDruVwlBvsUtDBv0Atwta+WAS5K762PXwaX NckA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=xHuSKHcqWAtnMCTMUjpg44+kvPh/xd0uugoOde8G9QY=; b=PZaXFjYG2jd5Ej3Kd7e+taumBJ1SRCTnzYPxUpisF0zKgUx1pl4AKb9LepV8773YFA 0U9u2UyotfwmcgPbfYnexupYpiF+j6JOqN0WP61i4I+aaztBHnDJ5QEgg8p+2dOi3OSI /lSlzzu1bohjR/rGlq7rdN64xp/IXvpwt6YNn4f7tX8xFIoxYFI2ONWJFAuqRi8sgSMU PzXFRrs5/RtlkNQ86qMKVH7MpqDnnhdYz//VdjCjpJ4iNFHb2ej4yQZJw4zhIFZIvhqk Y/HeQrF23XZO/Ms4wTLs6nIV/7eTEPHE8/zjVEwbkQFyDUPVI/fQIC9WPAYkSGbplxHC Qh9w== X-Gm-Message-State: APt69E3rfUcVMKmbtry4p8JJFtC4q5y6Da8hmFVabZQbTSgrUBVPB9vP sj634FuRyjJBA9vqPQ/cyuWrTko7gb0pA7FeYEyMdJtD X-Google-Smtp-Source: AAOMgpcbkcJgh3P0VjA+H3obRZH1LNKewfzXPif4OP8qezsW02a0TWh2E/Resgrhwhq53tuI8UOR/jp8fXVrWIa83t4= X-Received: by 2002:a19:1a52:: with SMTP id a79-v6mr21753764lfa.43.1530667205745; Tue, 03 Jul 2018 18:20:05 -0700 (PDT) MIME-Version: 1.0 From: Alberto Rodriguez-Natal Date: Tue, 3 Jul 2018 18:19:54 -0700 Message-ID: To: "lisp@ietf.org list" , spring@ietf.org, dmm Content-Type: multipart/alternative; boundary="0000000000001161d20570223b70" Archived-At: Subject: [lisp] LISP for SRv6 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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: Wed, 04 Jul 2018 01:20:10 -0000 --0000000000001161d20570223b70 Content-Type: text/plain; charset="UTF-8" Hi all, We have published the draft "LISP Control Plane for SRv6 Endpoint Mobility" [1]. Please take a look and let us know any feedback you may have. Thanks! Alberto [1] https://tools.ietf.org/html/draft-rodrigueznatal-lisp-srv6-00 --0000000000001161d20570223b70 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

We have published th= e draft "LISP Control Plane for SRv6 Endpoint Mobility" [1]. Plea= se take a look and let us know any feedback you may have.

Thanks!
Alberto


--0000000000001161d20570223b70-- From nobody Fri Jul 6 03:06:13 2018 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 D80DB130EBD for ; Fri, 6 Jul 2018 03:06:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=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 2w5bgC6zly7k for ; Fri, 6 Jul 2018 03:06:09 -0700 (PDT) Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 DE3A4130EB0 for ; Fri, 6 Jul 2018 03:06:08 -0700 (PDT) Received: by mail-wr1-x435.google.com with SMTP id u7-v6so3607420wrn.12 for ; Fri, 06 Jul 2018 03:06:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=from:mime-version:subject:message-id:date:cc:to; bh=rROvtN9YA2Z5RAUofWqbxyhCN6BFFfHvzgAJ9lSZ9dk=; b=aB9+5TcN7XKKw88dR4blWycpWPYie3oui1lRHnvIc1bYpiQIE9XPJ97B63PA3X/Pzm dCbMJ+97TvlMyVYIhEkqtntk0jVdf8AYUEQpGZZRA75rm2SSKlv2U4rUwi8rTsjCqXjl T3jkwMWlXFTE2XUy8KWg2awYiAyYtPifGRFlZdxJW5Zo0b2ZbOtc9qeZs4LBoCwLls1f ajJHCvpXyIagJaiTmuto3Oz6JJj356tMaMstzFrW62pvdMQuxNod8hh3YToOmbnkbBCD V1mezavhMTdw+n5JMAguMiHMv8V4gP3fFekwztMSgFbNLSC8C8Srrb0EaWWLPETDjKu6 aPXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:cc:to; bh=rROvtN9YA2Z5RAUofWqbxyhCN6BFFfHvzgAJ9lSZ9dk=; b=J6UbAmjV9/oFBt2IYMe864qqsl/UzZnSKLteVjyu8O9wgbytfIQr5YIX3+BD2wcYUy CI0Aga0/8OG3eFkn4TxtQ/lt+x+g5/3jwiqQG8aLF3EiVjZxo6GCGxY8Ywyk+l5Znnrn /8hZUjahH/e2jYL9EMXaURhr4krpMSlmEw3RFGG1KtSAYDPFxGsWu3WGaOtbTK8c9Ysb cWE8XfJ6qt6DRgMSiAuZiNoPKSlKkoJdGeB8hm3FbDvkILlylr2xqK4QqEP3lwsUa6sq 9Ruq/Nu8RIsrCCqk+JcXZaMgBTUZbaBuMtJPL5kUhzkk32Xol7aG26N0W2KJm35dlOjc QRQQ== X-Gm-Message-State: APt69E3dqBOvnTwyOP1jUZ6UyTq1C3W9XSDef38b6nolW3q/SrHBb9EJ bagLkWwy7341pc4ZxA5eXAW8TiRghJI= X-Google-Smtp-Source: AAOMgpf//JgmQRfiP8BAoy0Bm6mt/0hI+wdgYhVrldiISJVU2Qcznz6TtvwO+Zm4GWLp1MkFRvu0Fg== X-Received: by 2002:adf:bc03:: with SMTP id s3-v6mr7538764wrg.211.1530871566975; Fri, 06 Jul 2018 03:06:06 -0700 (PDT) Received: from ?IPv6:2001:660:330f:a4:c0d3:fb78:6649:27fe? ([2001:660:330f:a4:c0d3:fb78:6649:27fe]) by smtp.gmail.com with ESMTPSA id 125-v6sm15347831wmw.9.2018.07.06.03.06.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Jul 2018 03:06:05 -0700 (PDT) From: Luigi Iannone Content-Type: multipart/alternative; boundary="Apple-Mail=_8E353C86-2391-4268-A1AE-9A1D2FC0140D" Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Message-Id: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> Date: Fri, 6 Jul 2018 12:06:04 +0200 Cc: lisp-chairs@ietf.org To: "lisp@ietf.org list" X-Mailer: Apple Mail (2.3445.8.2) Archived-At: Subject: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 06 Jul 2018 10:06:12 -0000 --Apple-Mail=_8E353C86-2391-4268-A1AE-9A1D2FC0140D Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Folks, As Alberto mentioned in a previous mail, in London there was consensus = to move forward draft-ietf-lisp-vendor-lcaf = [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02 = ] (after the = few fixes that I asked). Fixes are done, hence, this email starts the usual two weeks WG Last = Call, to end July 20th, 2018. 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=_8E353C86-2391-4268-A1AE-9A1D2FC0140D Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Folks,

As = Alberto mentioned in a previous mail, in London there was consensus to = move forward draft-ietf-lisp-vendor-lcaf [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02]=  (after the few fixes that I asked).

Fixes are done, hence, = this email starts the usual two weeks WG Last Call, to end July 20th, = 2018.

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=_8E353C86-2391-4268-A1AE-9A1D2FC0140D-- From nobody Fri Jul 6 04:06:13 2018 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 254A2130ECE for ; Fri, 6 Jul 2018 04:06:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=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 v9SL5hLHPkjc for ; Fri, 6 Jul 2018 04:06:08 -0700 (PDT) Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 A9BB6130F11 for ; Fri, 6 Jul 2018 04:06:07 -0700 (PDT) Received: by mail-wr1-x432.google.com with SMTP id b15-v6so3782239wrv.10 for ; Fri, 06 Jul 2018 04:06:07 -0700 (PDT) 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=FTqSlfA26ryh0VvFcF1ZkQjMAdfvC3kRZih9F29A6UI=; b=RQKLNmltnd89ivPKae2MCBApX0UgqGzUf5XxfSv5A/5W0UM5HC5mGR2vZITshAZhSG O44yYVi/5iwshJzl2GPFwl3sRdambEgnWcwPxihsZqDkSKSotou7PKpc7lczdOlVPMAi YpOgguj8dgEVzmWfeOALQwukAp/tqjzUuGSeZq8o1AsdmCBSaMv8vTHV0QcysLlICpWs 8+cE/fr9fKfgvwurwUc0aDhU8frhavBAfRp9Rb9MUHVJGbC4M0csUlJ4OsNN8EUTt6Bf +C3qVne0VOaMYYeY/WZN0ELrzerwTzj4klRvWF+svFyGOzhQwGQpfmOzwYQDta5nH+pU QiDg== 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=FTqSlfA26ryh0VvFcF1ZkQjMAdfvC3kRZih9F29A6UI=; b=YgBvNXUCBBSbFTMw9M92XV/IiTPw8t9ZY+BIxjlWJrSyu1MoQTbBJTwpkgX1jFUK/Z Zk8EVKI9g3M13D7kui90gtsGceAq7uXOcRZF/ZI+rGGLrfNAOaiY8r0nJgIwReTojS7y S5f2xsw2SOQvEYyB8ZGR3IuXoMrzVqFT4IyFV46gwK1KvDcX/EiMbskmtV/XTFe2n6Xj c2oLWTmulUrschsPtbxlzZxJZnSujrSIo/70kMcN1b4iVD7X8Pyx9XqC7Ou40UsqvGf3 5+z9geHpM9hzVTNmYYYXjvSStytlmI51PDO9KQp6CCqslzJaRuEoshS7MUFScO0D3EJh fAVQ== X-Gm-Message-State: APt69E16GFX2wAklm/HkxH6HenuuTAQ2pFc2oisiLyV7dzOKJCbeff6Y 1ZU+AnTYZJEcencVj1b+dQgqgYU0K64= X-Google-Smtp-Source: AAOMgpctjL6IArkLZA8BAzTZwLBx1N4lbgXw+LtVWMGNSSPWbGwEs4tMalv19RTIlfC2rKjmqFEZ5w== X-Received: by 2002:adf:bc92:: with SMTP id g18-v6mr7149735wrh.266.1530875165582; Fri, 06 Jul 2018 04:06:05 -0700 (PDT) Received: from ?IPv6:2001:660:330f:a4:c0d3:fb78:6649:27fe? ([2001:660:330f:a4:c0d3:fb78:6649:27fe]) by smtp.gmail.com with ESMTPSA id y5-v6sm1078458wrn.70.2018.07.06.04.06.02 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Jul 2018 04:06:02 -0700 (PDT) From: Luigi Iannone Message-Id: <8DFD34C0-3739-458D-96D5-583875D24D9B@gigix.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_89DB1B0B-BC02-4596-89A4-766F8F554385" Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Date: Fri, 6 Jul 2018 13:06:01 +0200 In-Reply-To: <5894923D-E885-4B43-BC73-45206F957827@gigix.net> Cc: lisp-chairs@ietf.org To: "lisp@ietf.org list" References: <5894923D-E885-4B43-BC73-45206F957827@gigix.net> X-Mailer: Apple Mail (2.3445.8.2) Archived-At: Subject: Re: [lisp] Call for Agenda Items @ 102 IETF X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 06 Jul 2018 11:06:12 -0000 --Apple-Mail=_89DB1B0B-BC02-4596-89A4-766F8F554385 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi All, the LISP WG Agenda is now online: = https://datatracker.ietf.org/meeting/102/materials/agenda-102-lisp-00 = There is still time available, so do not hesitate to ask for a slot. Ciao L. > On 25 Jun 2018, at 10:35, Luigi Iannone wrote: >=20 > Hi All, >=20 > We have a time slot during the next IETF in Montreal so it is time to = fix the agenda for our WG. > The LISP WG is scheduled to meet on Thursday, July 19th, 2018, from = 13:30 to 15:30 (2 hours)=20 >=20 > Please send your requests for agenda items (Presenter=E2=80=99s name, = title, slot duration)=20 > to lisp-chairs@tools.ietf.org by = Wednesday 4th July, 2018 (before the fireworks ;-) ). >=20 > Thanks >=20 > Joel & Luigi --Apple-Mail=_89DB1B0B-BC02-4596-89A4-766F8F554385 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi = All,

the LISP WG = Agenda is now online: https://datatracker.ietf.org/meeting/102/materials/agenda-102-l= isp-00

There= is still time available, so do not hesitate to ask for a = slot.

Ciao

L.


On 25 = Jun 2018, at 10:35, Luigi Iannone <ggx@gigix.net> wrote:

Hi All,

We have a time slot = during the next IETF in Montreal so it is time to fix the agenda = for our WG.
The LISP WG  is scheduled to meet on = Thursday, July 19th, 2018, from 13:30 to 15:30 (2 hours) 

Please send your requests for agenda = items (Presenter=E2=80=99s name, title, slot duration) 
to lisp-chairs@tools.ietf.org by Wednesday 4th July, = 2018  (before the fireworks ;-) ).

Thanks

Joel & = Luigi

= --Apple-Mail=_89DB1B0B-BC02-4596-89A4-766F8F554385-- From nobody Fri Jul 6 11:39:12 2018 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 38868130EB9; Fri, 6 Jul 2018 11:39:10 -0700 (PDT) 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 9Mfi-Tav2yeB; Fri, 6 Jul 2018 11:39:08 -0700 (PDT) Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (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 349A1130E97; Fri, 6 Jul 2018 11:39:08 -0700 (PDT) Received: by mail-pf0-x22d.google.com with SMTP id q7-v6so7989319pff.2; Fri, 06 Jul 2018 11:39:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=qSGl9yRR5vtqWwmlMC7Pf2oiiy7uSZrzBr7rn1mTwqo=; b=aiwWlE79GCJ4P52l0CTArx1rZC/m/qBDyHsBC4U70Dm4b0H/Q5l3BMsMrCUsvCouLS H0wEIn5AqH/6UDUeUGovqklVo47nV7wqvNP2XiTqUprIRNfN4eOYBrRm2kSayxwTB0nq uttToVOIzVrg5y4GRD/+1UNQJ6+Li/BJW/JRGhEctoZHI3GFORl2+S/4/HwZG2m/HQzQ DWa2HdB89EHxhmll3nLq+pjSgYuPIFZrmfWs588tIQwdh+KzQG9mHvUQsQvXU5mzRnD5 APKjBkec7psF0Ta2oAEPNKtuQC2TsEg5r6voeGqdUJdasz+DfeL6NKrRfUywxWx+xHeP BYoA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=qSGl9yRR5vtqWwmlMC7Pf2oiiy7uSZrzBr7rn1mTwqo=; b=bjGgKzTbovHLzBXkwbppXDkrXyb6C2Fy9m7QhMYNMBApYsH70cf2Es6dJ+vLIg9iEi 7pgYkrLe1SAlnB7YWorbZBn0toADWXeIV6SWyXvWwrY4hzToaqG2gvdU4x0zGgy/vrlq lp8uM03eBaN8l1mw0gqjoXZtoLYEWpLBdaz9bkZiVTkilw+o1nIgmCv515EVMWFmkfpO +ykAOskk+l+r+q+4+XRpGehUtSwSwNA0J3+liqyRfsAttmPtsnIlEioluAjptfWvD6WN IniilYhQzWStEdmW3OaxIG21IQflPS6LRzdcgZojbrLZTPtZzNGPCi/a9JWnDpCKqNeF w3pg== X-Gm-Message-State: APt69E0ow5hk7LWpwbJBLhQxghwB27KUzXyOSeZNpf1/QDHS9SMaBOgo rLOSUr+8ErU8g9PKl/WHrXE= X-Google-Smtp-Source: AAOMgpdzf4q7oVil4L6eN5uV7azzgs8PXlhK4+DyHhAbdf2NRFO8gGe7q2VwbVP94GzGZXfvXbA3tw== X-Received: by 2002:a62:cc4d:: with SMTP id a74-v6mr11793469pfg.200.1530902347771; Fri, 06 Jul 2018 11:39:07 -0700 (PDT) Received: from [10.31.79.139] ([96.72.181.209]) by smtp.gmail.com with ESMTPSA id s6-v6sm20877104pfs.115.2018.07.06.11.39.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 06 Jul 2018 11:39:07 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) From: Dino Farinacci In-Reply-To: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> Date: Fri, 6 Jul 2018 11:38:36 -0700 Cc: "lisp@ietf.org list" , lisp-chairs@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> To: Luigi Iannone X-Mailer: Apple Mail (2.3445.5.20) Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.26 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, 06 Jul 2018 18:39:11 -0000 I agree that it is ready for handing to the AD. Dino > On Jul 6, 2018, at 3:06 AM, Luigi Iannone wrote: >=20 > Folks, >=20 > As Alberto mentioned in a previous mail, in London there was consensus = to move forward draft-ietf-lisp-vendor-lcaf = [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after the = few fixes that I asked). >=20 > Fixes are done, hence, this email starts the usual two weeks WG Last = Call, to end July 20th, 2018. >=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 > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp From nobody Mon Jul 9 11:25:57 2018 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 C40C0130E7C; Mon, 9 Jul 2018 11:25:54 -0700 (PDT) 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 GE17knMPnUOx; Mon, 9 Jul 2018 11:25:53 -0700 (PDT) Received: from mail-lf0-x22f.google.com (mail-lf0-x22f.google.com [IPv6:2a00:1450:4010:c07::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 AE0FE130E73; Mon, 9 Jul 2018 11:25:52 -0700 (PDT) Received: by mail-lf0-x22f.google.com with SMTP id a4-v6so16034516lff.5; Mon, 09 Jul 2018 11:25:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=WFL0ANzAN0eyxp06t78bQbtquN9xTIg2rkR/d8GOfHg=; b=nohwkE+Ln0K0Qg0E9wFUlychBSU9g+JsqE3oZX2Ct6GkQ4zltgisqMXvDVO5dG8j9u PctpCsZzt/gOZ+la5Z1MPNnKUdUszTjJG8bHI6CbO5lYRtF24Ywp/cswAV7UvuVs9zVU +1EiiW6KHZOcLbTZzQAqDe1/vKKfI9LQVjAdmLx3ST48UI1ZAG9ZJGK8EQddG7bHvsvp 1A343yYpRY4XYSCpb0RuuNdxp79R8wB+UcsjXcKR0dbDERavfdsnAN4I7SePnPy99MKV eagJAqd86R2noV3Wv6w+p+FuuaCHxOgWtHLTpkQJuVgmSok5LVoXh+4+Typ6JN/t3fIp RKpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=WFL0ANzAN0eyxp06t78bQbtquN9xTIg2rkR/d8GOfHg=; b=Qnqg7hMRM1HMm5GWY6Isvelw0Jj6S8asP7oAIB8wXv20k0hwhqdyHHbn3V2/0xD21B sf1g5XPiGt8/GwmV+9CxYKA7A2+TKVT+JOpQ6SohBeqdBSx7FgUTQR7mVs2wb3/uLLn9 y68dsAg5bUk9ZzFGxJYK2u+FDFgRSrP5gmMzgkCavZblWF2CTgA+cu/DElFfDFCjgqmb h0uXdCrBXuNUwb/XhEtEnRHzoSVAmp74Kn8vz/WfnSAjIQpcYSFvDULoYWZpJm2CEmWL jVp5kyfUWuuhy+zVb08T5rw1gSUtabO5y4PTlDPClegPVOBCIHT1QD0oOf/UqQZaMA/V oepg== X-Gm-Message-State: APt69E1I/F5QikfRNFPPNQu9mgJ2/3G8VQ4QZTriLuUHGLvPBNSbQA33 REaL4dWyLe7gMkLvNVzdLyKCb3DUpoWM022yDDB56w== X-Google-Smtp-Source: AAOMgpdAJZrKRE4j+Yi5jPDTEM3Ol0Lu6Z38hoJxUjTl+jssb97+bIStx3eRCJYgHnAoa47NBAVla9gHDbHmMBc4ROs= X-Received: by 2002:a19:f015:: with SMTP id p21-v6mr415876lfc.77.1531160750799; Mon, 09 Jul 2018 11:25:50 -0700 (PDT) MIME-Version: 1.0 References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> In-Reply-To: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> From: Alberto Rodriguez-Natal Date: Mon, 9 Jul 2018 11:25:39 -0700 Message-ID: To: Luigi Iannone Cc: "lisp@ietf.org list" , lisp-chairs@ietf.org Content-Type: multipart/alternative; boundary="000000000000a53f880570952444" Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 09 Jul 2018 18:25:55 -0000 --000000000000a53f880570952444 Content-Type: text/plain; charset="UTF-8" As an author, I believe this document is ready for the review of the AD. Thanks, Alberto On Fri, Jul 6, 2018 at 3:06 AM Luigi Iannone wrote: > Folks, > > As Alberto mentioned in a previous mail, in London there was consensus to > move forward draft-ietf-lisp-vendor-lcaf [ > https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after the > few fixes that I asked). > > Fixes are done, hence, this email starts the usual two weeks WG Last Call, > to end July 20th, 2018. > > 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 > --000000000000a53f880570952444 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
As an author, I believe this document is ready for th= e review of the AD.

Thanks,
Alberto<= br>

On Fri, Jul = 6, 2018 at 3:06 AM Luigi Iannone <ggx@g= igix.net> wrote:
Folks,

As Alberto mentioned in a previous mail, in London there was consensu= s to move forward draft-ietf-lisp-vendor-lcaf [https://tools.= ietf.org/html/draft-ietf-lisp-vendor-lcaf-02]=C2=A0(after the few fixes= that I asked).

Fixes are done, hence, this e= mail starts the usual two weeks WG Last Call, to end July 20th, 2018.
=

Please review this WG document and let the WG know= if you agree that it is ready for handing to the AD.
If yo= u 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
--000000000000a53f880570952444-- From nobody Mon Jul 9 16:05:13 2018 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 85ABB130DE9; Mon, 9 Jul 2018 16:05:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.51 X-Spam-Level: X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 1nsCe2afP587; Mon, 9 Jul 2018 16:05:09 -0700 (PDT) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FF9F127332; Mon, 9 Jul 2018 16:05:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3336; q=dns/txt; s=iport; t=1531177509; x=1532387109; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=4pTDwsieqTwm4YIlulw4Q6bRVDUgkRJpXwaqFRcSxDc=; b=U1vAdMoGrdLcvWFvdfiFdXsLZNxJLcCLYass1PVVYeCAF6rDfk7l7ngI jeoIhsAvEKODD6hGDbtPgBWaAgod8BCL1b0mP8ctgwYmIstwrSKD/nlGH b5Ak7n2M5fQIaEkJFjVQZ07wr4EjzZlog+zCXVFyddmndLMZEPbB+Twzh s=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AtAQBH6UNb/5FdJa1dGgEBAQEBAgE?= =?us-ascii?q?BAQEIAQEBAYNJYn8oCot0jDSSK4UOFIFmCyOESQKCRSE0GAECAQECAQECbRw?= =?us-ascii?q?MhTcGHVwQAgEIBAoxBzIUEQIEDgWDIAGBG2QPq3OEW4NxgTUFiG6CFYE2gmi?= =?us-ascii?q?DGAEBA4EqAQ8CAgGDUIIkAplPCQKGBokcgUKEDoZ2gReKOIcxAhEUgSQdOGF?= =?us-ascii?q?xcBVlAYI+ixSFPm+NY4EaAQE?= X-IronPort-AV: E=Sophos;i="5.51,330,1526342400"; d="scan'208,217";a="421245444" Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Jul 2018 23:05:08 +0000 Received: from XCH-ALN-017.cisco.com (xch-aln-017.cisco.com [173.36.7.27]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id w69N58qd022341 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 9 Jul 2018 23:05:08 GMT Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-ALN-017.cisco.com (173.36.7.27) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 9 Jul 2018 18:05:07 -0500 Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1320.000; Mon, 9 Jul 2018 18:05:07 -0500 From: "Lorand Jakab -X (lojakab - AAP3 INC at Cisco)" To: Luigi Iannone CC: "lisp@ietf.org list" , "lisp-chairs@ietf.org" Thread-Topic: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf Thread-Index: AQHUFREBDXWSHSZ260mTIPnwKDAa9aSH3D6A Date: Mon, 9 Jul 2018 23:05:07 +0000 Message-ID: References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> In-Reply-To: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@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.61.144.76] Content-Type: multipart/alternative; boundary="_000_C39FCB54A9084C4BB6A86CD3DB6D2ED6ciscocom_" MIME-Version: 1.0 Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 09 Jul 2018 23:05:12 -0000 --_000_C39FCB54A9084C4BB6A86CD3DB6D2ED6ciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Jul 6, 2018, at 12:06 PM, Luigi Iannone > wrote: Folks, As Alberto mentioned in a previous mail, in London there was consensus to m= ove forward draft-ietf-lisp-vendor-lcaf [https://tools.ietf.org/html/draft-= ietf-lisp-vendor-lcaf-02] (after the few fixes that I asked). Fixes are done, hence, this email starts the usual two weeks WG Last Call, = to end July 20th, 2018. Please review this WG document and let the WG know if you agree that it is = ready for handing to the AD. I reviewed the document and I think it is ready to be handed to the AD. -Lori If you have objections, please state your reasons why, and explain what it = would take to address your concerns. Thanks Luigi & Joel --_000_C39FCB54A9084C4BB6A86CD3DB6D2ED6ciscocom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable On Jul 6, 2018, at 12:06 PM, Luigi Iannone <ggx@gigix.net> wrote:

Folks,

As Alberto mentioned in a previous mail, in London there wa= s consensus to move forward draft-ietf-lisp-vendor-lcaf [https://too= ls.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after the few fixes that I asked).

Fixes are done, hence, this email starts the usual two week= s WG Last Call, to end July 20th, 2018.

Please review this WG document and let the WG know if you a= gree that it is ready for handing to the AD.

I reviewed the document and I think it is ready to be handed to the AD= .

-Lori

If you have objections, please state your reasons why, and = explain what it would take to address your concerns.
Thanks

Luigi & Joel
--_000_C39FCB54A9084C4BB6A86CD3DB6D2ED6ciscocom_-- From nobody Tue Jul 10 13:05:49 2018 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 012741310CD; Tue, 10 Jul 2018 13:05:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.509 X-Spam-Level: X-Spam-Status: No, score=-14.509 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ewR_Yr3KvbRM; Tue, 10 Jul 2018 13:05:44 -0700 (PDT) Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA66113104C; Tue, 10 Jul 2018 13:05:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4589; q=dns/txt; s=iport; t=1531253143; x=1532462743; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=1sQyGtWgofSZUyijiPWcAeA/WXzNlY6OQBEyma29ZRI=; b=dlWTTHxgV0L2h8Ja0xlIDWmIm+6NJ8OpQ4Xp67EyKeZPq74SD1Wu+Bj0 elE2n6cqVU67+5coVeLtc4cvkFoRHGPEWzmQKi3wD5wd2iZAR7zkfWbpV ajqaeTTuim/iK+OJiMyXvoXfUZsBHEf0HXmm00K1IrYBvQEp08BxVzJ5B 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DIAABfEUVb/40NJK1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJTdmMPcCgKi3SMNoIKkCSFDhSBZgsjhEkCgiohNBgBAgE?= =?us-ascii?q?BAgEBAm0cDIU2AQEBAQMdXBACAQgECgMDAQIoBzIUCQgCBAENBYMhgRtkD6x?= =?us-ascii?q?ChFuDc4EzBYh5gVc/hCGDGQEBA4EqAQ8CAgE+hTYCmVIJAoYHiR2BQ4QPhne?= =?us-ascii?q?BF4o4hzMCERMBgSQdOGFxcBU7gmmLFYU+b4w8gRoBAQ?= X-IronPort-AV: E=Sophos;i="5.51,335,1526342400"; d="scan'208,217";a="141496820" Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 Jul 2018 20:05:25 +0000 Received: from XCH-RCD-019.cisco.com (xch-rcd-019.cisco.com [173.37.102.29]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id w6AK5Pdn020381 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 10 Jul 2018 20:05:25 GMT Received: from xch-rcd-019.cisco.com (173.37.102.29) by XCH-RCD-019.cisco.com (173.37.102.29) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 10 Jul 2018 15:05:24 -0500 Received: from xch-rcd-019.cisco.com ([173.37.102.29]) by XCH-RCD-019.cisco.com ([173.37.102.29]) with mapi id 15.00.1320.000; Tue, 10 Jul 2018 15:05:24 -0500 From: "Vina Ermagan (vermagan)" To: Luigi Iannone , "lisp@ietf.org list" CC: "lisp-chairs@ietf.org" Thread-Topic: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf Thread-Index: AQHUFRF3jxpYNHSpbkagDzySVAYfkaSIxwcA Date: Tue, 10 Jul 2018 20:05:24 +0000 Message-ID: References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> In-Reply-To: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.7.1.161129 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.154.208.120] Content-Type: multipart/alternative; boundary="_000_D76A5E38E8398vermaganciscocom_" MIME-Version: 1.0 Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 10 Jul 2018 20:05:47 -0000 --_000_D76A5E38E8398vermaganciscocom_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I believe the document is ready for handing to the AD. I am an author on this document. Best, Vina From: lisp > on behalf = of Luigi Iannone > Date: Friday, July 6, 2018 at 3:06 AM To: "lisp@ietf.org list" > Cc: "lisp-chairs@ietf.org" > Subject: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf Folks, As Alberto mentioned in a previous mail, in London there was consensus to m= ove forward draft-ietf-lisp-vendor-lcaf [https://tools.ietf.org/html/draft-= ietf-lisp-vendor-lcaf-02] (after the few fixes that I asked). Fixes are done, hence, this email starts the usual two weeks WG Last Call, = to end July 20th, 2018. 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 --_000_D76A5E38E8398vermaganciscocom_ Content-Type: text/html; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable
I believe the document is ready for handing to the AD. 

I am an author on this document.

Best,
Vina

From: lisp <lisp-bounces@ietf.org> on behalf of Luigi Ianno= ne <ggx@gigix.net>
Date: Friday, July 6, 2018 at 3:06 = AM
To: "lisp@ietf.org list" <l= isp@ietf.org>
Cc: "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>
Subject: [lisp] WG Last Call for dr= aft-ietf-lisp-vendor-lcaf

Folks,

As Alberto mentioned in a previous mail, in London there wa= s consensus to move forward draft-ietf-lisp-vendor-lcaf [https://too= ls.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after the few fixes that I asked).

Fixes are done, hence, this email starts the usual two week= s WG Last Call, to end July 20th, 2018.

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
 --_000_D76A5E38E8398vermaganciscocom_-- From nobody Wed Jul 11 11:28:28 2018 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 B8F2B130F2D for ; Wed, 11 Jul 2018 11:28:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 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_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 CLGJRtt5_jdl for ; Wed, 11 Jul 2018 11:28:19 -0700 (PDT) Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (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 BCF63130EA0 for ; Wed, 11 Jul 2018 11:28:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id A44E0684DA1 for ; Wed, 11 Jul 2018 11:28:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1531333698; bh=/405RAcXmYeeUfyGDi5DRSm393rTflM3yD3ZG+pdhpE=; h=To:From:Subject:Date:From; b=RrHeOAw8bQ9dDOs6dEGYtyaW0blzyygqsKMtBvFMHy1qC4xqsOB2qK5I+41PeBTmp SXfcX4ehCYkIytyuASjY+A5V96BpwCxzjgkGCTrjRPHDIVxd3HcGQXCTYRUqn1oe6a rYKV1YX3Biw++G/1RnooZzAw1LdLpDKmiaIToJi0= X-Virus-Scanned: Debian amavisd-new at b2.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 mailb2.tigertech.net (Postfix) with ESMTPSA id 4BE3C684DA0 for ; Wed, 11 Jul 2018 11:28:18 -0700 (PDT) To: "lisp@ietf.org" From: "Joel M. Halpern" Message-ID: Date: Wed, 11 Jul 2018 14:28:17 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Archived-At: Subject: [lisp] Presentations X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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: Wed, 11 Jul 2018 18:28:21 -0000 Presenters, please get your material to the chairs and WG secretary (sending to lisp-chairs@ietf.org will work fine). While we are scheduled later in the week, the earlier you get us the material, the better. Thank you, Joel From nobody Sun Jul 15 09:22:34 2018 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 CD01C130DDA; Sun, 15 Jul 2018 09:22:32 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.82.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: lisp@ietf.org Message-ID: <153167175280.21839.14266408988103548423@ietfa.amsl.com> Date: Sun, 15 Jul 2018 09:22:32 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-rfc6830bis-13.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 15 Jul 2018 16:22:33 -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 WG 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-13.txt Pages : 42 Date : 2018-07-15 Abstract: This document describes the Data-Plane protocol for the Locator/ID Separation Protocol (LISP). 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. LISP requires no change to either host protocol stacks or to underlay routers and offers Traffic Engineering, multihoming and mobility, among other features. This document obsoletes RFC 6830. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6830bis/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-lisp-rfc6830bis-13 https://datatracker.ietf.org/doc/html/draft-ietf-lisp-rfc6830bis-13 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-rfc6830bis-13 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 Jul 17 10:19:36 2018 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 94A87130ED4 for ; Tue, 17 Jul 2018 10:19:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.911 X-Spam-Level: X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] 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 v2GRXEr2mGn7 for ; Tue, 17 Jul 2018 10:19:32 -0700 (PDT) Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::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 83D08130DDE for ; Tue, 17 Jul 2018 10:19:32 -0700 (PDT) Received: by mail-it0-x22f.google.com with SMTP id 16-v6so201216itl.5 for ; Tue, 17 Jul 2018 10:19:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gigix-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=cGSRa5BUR9REmlBk2DZF31tB+tScjo/p6zyPsBoysq4=; b=XJrNMtv3uSM0lL4dvE7I8c/wAukcr+bWYNN3CVlInXTPFmE8r7JyqhSJ2xmElixB0a 7PBFX40mzUmHnAqWMQykWCQcbMu3BUXneyaWuTka23xlOJcpNf4hyu3cAtliTwmOb4xd sDdzRkN7vv2Ogsp5wv3RFu1zN/pBJUjG5VUH7V8o9X2mtqw7OuZmhOL4JxTFni/kS0ox VeZ0GUnPrGvv+F6PhsfezbLWNtBKipa93KVOtR9cy7FAwTjje2yuWlwNHO20ihJIbJ0U xjryHbvjEARFcC+FyigHNKecKFfKJjoMqX35N7/uAWtwRAAb0zZF56S8BGoPd/SBSmQe 62wg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=cGSRa5BUR9REmlBk2DZF31tB+tScjo/p6zyPsBoysq4=; b=D1QH4nQ0K5mFsteCmUV4zitMhkiyY44jChm9/JjpZix8U9tPMzwcocSRLtzHmHN0m8 IJifJ3eBczf/BDByEskM8I0su28QB2g6qrWzW5LVDImMP51R/qwSiXaV3TS/SFSe6WeL E8Hk0zF+2xrDsyGSNwl+/pisqrlR1fJCkxDl/E0wIvKJb/kl8hDPWEJcOUM+GWd3oQDe apghs3pknYlW4FYO9EY4HVR51vHhxLkF+21bCSZUU0BmW41mTlkf2MfAKUuZvYw07bwJ +WVEtgqxjgl3CWksFMoSO9ISqOAtoY5Ozny/y0PTbnkRGg1gNMttkvdd+hugV45JUiwX 2FkQ== X-Gm-Message-State: AOUpUlFtTPrF8Lpa3XV0CYqbv4/RCa3lBjHc3bUKRgjGuU7VMyFsV5zC KJ/6SwGNeuCp9Ha3+PmkRNDyIKpCSzI= X-Google-Smtp-Source: AAOMgpdqb1QcMWQW/1F1cyw5hvj08B+6ZsCGypCoe9gjoG3mMj5rTkQdn4PI0mrcpYfU6s6b3D516g== X-Received: by 2002:a24:800c:: with SMTP id g12-v6mr2358213itd.146.1531847971276; Tue, 17 Jul 2018 10:19:31 -0700 (PDT) Received: from ?IPv6:2001:67c:370:128:4926:776:136a:dbe9? ([2001:67c:370:128:4926:776:136a:dbe9]) by smtp.gmail.com with ESMTPSA id q6-v6sm691986iob.65.2018.07.17.10.19.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 17 Jul 2018 10:19:29 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) From: Luigi Iannone In-Reply-To: Date: Tue, 17 Jul 2018 13:19:35 -0400 Cc: lisp-chairs@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <74514654-D2E5-4CCC-A013-78A2A9CB8010@gigix.net> References: To: "lisp@ietf.org list" X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [lisp] Presentations X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 17 Jul 2018 17:19:35 -0000 Reminder for the presenters: Please send us the slides. Ciao L. > On 11 Jul 2018, at 14:28, Joel M. Halpern wrote: >=20 > Presenters, please get your material to the chairs and WG secretary = (sending to lisp-chairs@ietf.org will work fine). While we are = scheduled later in the week, the earlier you get us the material, the = better. >=20 > Thank you, > Joel >=20 > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp From nobody Tue Jul 17 16:51:28 2018 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 D4F71130E2E; Tue, 17 Jul 2018 16:51:18 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.82.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: lisp@ietf.org Message-ID: <153187147883.12835.12016811121216747482@ietfa.amsl.com> Date: Tue, 17 Jul 2018 16:51:18 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-rfc6830bis-14.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 17 Jul 2018 23:51:19 -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 WG 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-14.txt Pages : 42 Date : 2018-07-17 Abstract: This document describes the Data-Plane protocol for the Locator/ID Separation Protocol (LISP). 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. LISP requires no change to either host protocol stacks or to underlay routers and offers Traffic Engineering, multihoming and mobility, among other features. This document obsoletes RFC 6830. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6830bis/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-lisp-rfc6830bis-14 https://datatracker.ietf.org/doc/html/draft-ietf-lisp-rfc6830bis-14 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-rfc6830bis-14 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 Jul 17 16:52:41 2018 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 D083C130E55; Tue, 17 Jul 2018 16:52:33 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.82.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: lisp@ietf.org Message-ID: <153187155381.12789.4513070629016108785@ietfa.amsl.com> Date: Tue, 17 Jul 2018 16:52:33 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-rfc6833bis-11.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 17 Jul 2018 23:52:34 -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 WG of the IETF. Title : Locator/ID Separation Protocol (LISP) Control-Plane Authors : Vince Fuller Dino Farinacci Albert Cabellos Filename : draft-ietf-lisp-rfc6833bis-11.txt Pages : 48 Date : 2018-07-17 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 modularity with different database designs. Since these devices implement the "edge" of the LISP Control-Plane infrastructure, connect directly to LISP-capable Internet end sites, and comprising the bulk of LISP-speaking devices, reducing their implementation and operational complexity should also reduce the overall cost and effort of deploying LISP. This document obsoletes RFC 6833. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6833bis/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-lisp-rfc6833bis-11 https://datatracker.ietf.org/doc/html/draft-ietf-lisp-rfc6833bis-11 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-rfc6833bis-11 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 Wed Jul 18 13:19:42 2018 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 04167131006 for ; Wed, 18 Jul 2018 13:19:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.509 X-Spam-Level: X-Spam-Status: No, score=-14.509 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id cVFkoQlETsHS for ; Wed, 18 Jul 2018 13:19:37 -0700 (PDT) Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B110A130EC8 for ; Wed, 18 Jul 2018 13:19:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3775; q=dns/txt; s=iport; t=1531945177; x=1533154777; h=subject:to:references:from:message-id:date:mime-version: in-reply-to; bh=DNi5NybwRZIcakilgw6ALfdUnt8FKsOHWuee6NVe8Zo=; b=TcgvCgljZMpmwZgGef13OTxOJTFOPswoVMEsbohJkcYzNRo3kuhIjUi7 9tvzzVzWN8N05mlT60QFQAhZppKCijBxUWooR4YrSIJu4f0JOQekBhNXO T0fjMw5bIueIImGAXxhpEAWOcxeZJetdkf9FgfLs6SR634IF0VqA1bE79 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CXAgCfn09b/5FdJa1cGgEBAQEBAgE?= =?us-ascii?q?BAQEIAQEBAYNJY38omC6BYCyQKoUPFIFmCxgBCoRJAoJ5ITYWAQIBAQIBAQJ?= =?us-ascii?q?tHAyFNwEBBAEBG1EbCwQULicwEwYCAQGDHAGBfw+rTR+EPIVqBYkCgVc/gTi?= =?us-ascii?q?CaoMZAQEDgSoBDwICAWuFCQKZYAmGCokXBoFEhBGCSIQygReKO4dcgUgDLmF?= =?us-ascii?q?xMxoIGxU7gmmLFYVaIzCNCgEB?= X-IronPort-AV: E=Sophos;i="5.51,371,1526342400"; d="scan'208,217";a="422565426" Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Jul 2018 20:19:36 +0000 Received: from [10.82.240.100] (rtp-vpn2-100.cisco.com [10.82.240.100]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTP id w6IKJaB5008144 for ; Wed, 18 Jul 2018 20:19:36 GMT To: lisp@ietf.org References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> From: Fabio Maino Message-ID: <8bf7d49e-b3c8-b5b9-cac7-06190ab41252@cisco.com> Date: Wed, 18 Jul 2018 16:19:36 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> Content-Type: multipart/alternative; boundary="------------C3E5C0DB255DA60BC4C22931" Content-Language: en-US Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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: Wed, 18 Jul 2018 20:19:40 -0000 This is a multi-part message in MIME format. --------------C3E5C0DB255DA60BC4C22931 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit I support handing this document to the AD. It's pretty straightforward, and I'm aware of implementations that plan to take advantage of this feature. Fabio On 7/6/18 6:06 AM, Luigi Iannone wrote: > Folks, > > As Alberto mentioned in a previous mail, in London there was consensus > to move forward draft-ietf-lisp-vendor-lcaf > [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after > the few fixes that I asked). > > Fixes are done, hence, this email starts the usual two weeks WG Last > Call, to end July 20th, 2018. > > 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 --------------C3E5C0DB255DA60BC4C22931 Content-Type: text/html; charset=windows-1252 Content-Transfer-Encoding: 8bit
I support handing this document to the AD.

It's pretty straightforward, and I'm aware of implementations that plan to take advantage of this feature.

Fabio

On 7/6/18 6:06 AM, Luigi Iannone wrote:
Folks,

As Alberto mentioned in a previous mail, in London there was consensus to move forward draft-ietf-lisp-vendor-lcaf [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after the few fixes that I asked).

Fixes are done, hence, this email starts the usual two weeks WG Last Call, to end July 20th, 2018.

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


--------------C3E5C0DB255DA60BC4C22931-- From nobody Thu Jul 19 09:43:28 2018 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 A444B126CB6; Thu, 19 Jul 2018 09:43:26 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.511 X-Spam-Level: X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 mmpYPPNeJa7W; Thu, 19 Jul 2018 09:43:23 -0700 (PDT) Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C27C7130DD1; Thu, 19 Jul 2018 09:43:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=887; q=dns/txt; s=iport; t=1532018602; x=1533228202; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=A7h9lTJbVSe+weeEOj+defodgJ88nQsvMtwzRx/yUdk=; b=E6avL5O2FCUIYY9CW9tcU2j9RiJU9OkQuUj5LBS20KVYu2Xc8ierRMZZ +WudyFNcH/xr3ldla0uRDKkrrtK4qfHTcdxVmu+nAts8+OKdOD64CnqkA XTA13rc6pYtOOruxJRBk/HHoghZnHefdISf+b22cqFOdPeiV4DghCMeCN 0=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CvAAC/vlBb/4oNJK1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYNNY38oCot4jCyCDJU7FIFmCxgLhEkCgwUhNBgBAgEBAgE?= =?us-ascii?q?BAm0cDIU2AQEBAQIBAQEbHTQLBQsCAQgOCh4QJwslAgQOBYMgAYF3CA+qaYR?= =?us-ascii?q?dhWgFiQKBVz+BOIJqgxkBAQOBKgEPAgIBHoMygiQCmWgJAoYLiR+BRIQShn+?= =?us-ascii?q?BF4o/hzcCERSBJB04YXFwFTsqAYI+ixWFPm+KW4EaAQE?= X-IronPort-AV: E=Sophos;i="5.51,375,1526342400"; d="scan'208";a="429346840" Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jul 2018 16:43:22 +0000 Received: from XCH-ALN-014.cisco.com (xch-aln-014.cisco.com [173.36.7.24]) by alln-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id w6JGhLMI032730 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Jul 2018 16:43:21 GMT Received: from xch-rcd-014.cisco.com (173.37.102.24) by XCH-ALN-014.cisco.com (173.36.7.24) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 19 Jul 2018 11:43:21 -0500 Received: from xch-rcd-014.cisco.com ([173.37.102.24]) by XCH-RCD-014.cisco.com ([173.37.102.24]) with mapi id 15.00.1320.000; Thu, 19 Jul 2018 11:43:21 -0500 From: "Johnson Leong (joleong)" To: Luigi Iannone CC: "lisp@ietf.org list" , "lisp-chairs@ietf.org" Thread-Topic: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf Thread-Index: AQHUFREBz3em/kQpYU+mFZNvaGnl0aSXKOGA Date: Thu, 19 Jul 2018 16:43:21 +0000 Message-ID: References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> In-Reply-To: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@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.154.160.234] Content-Type: text/plain; charset="us-ascii" Content-ID: <5B1BFF5E66F452438AB2CA5669DE6671@emea.cisco.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Outbound-SMTP-Client: 173.36.7.24, xch-aln-014.cisco.com X-Outbound-Node: alln-core-5.cisco.com Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 19 Jul 2018 16:43:27 -0000 I support handing this document to the AD. -Johnson > On Jul 6, 2018, at 3:06 AM, Luigi Iannone wrote: >=20 > Folks, >=20 > As Alberto mentioned in a previous mail, in London there was consensus to= move forward draft-ietf-lisp-vendor-lcaf [https://tools.ietf.org/html/draf= t-ietf-lisp-vendor-lcaf-02] (after the few fixes that I asked). >=20 > Fixes are done, hence, this email starts the usual two weeks WG Last Call= , to end July 20th, 2018. >=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 Thu Jul 19 09:48:48 2018 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 C45A8126CB6; Thu, 19 Jul 2018 09:48:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.51 X-Spam-Level: X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 vxhmDkRDB0ZW; Thu, 19 Jul 2018 09:48:43 -0700 (PDT) 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 65FDD130DD1; Thu, 19 Jul 2018 09:48:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7854; q=dns/txt; s=iport; t=1532018923; x=1533228523; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=zTAW9nCgJ2n11MwlrBMjP3KdIyakGmeDmMI6y66n1ew=; b=D5QOd69c2XjM8nEL8m64/sgWotNvynQkM83fKb2kPN94IDiID90LHKaJ x6sBNg1ltqoZn7qMqg6fRIyCD8MojHW3lFvqjUbCTmKFE4xaDbiK4G39q AFO7SeNFcn+tzLHVTq1UcjTnTNiFXfPvXQp4nf7Gvg1gjuq/nOcAqJpMf Y=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CwAACzv1Bb/5pdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJXdmN/KAqDdIgEjCyBaCSQK4UQFIFmCyOESQIXgm4hNBg?= =?us-ascii?q?BAgEBAgEBAm0cDIU2AQEBAQMdBlYQAgEIDgMDAQIrAgICMB0IAgQBDQWDIAG?= =?us-ascii?q?BG2QPqT2BLoRdhWgFiQKBVz+BOAyCXoMZAQEDgSoBDwICAT6CYTGCJAKIVpE?= =?us-ascii?q?SCQKGC4kfgUSEEoZ/gReKP4c3AhEUgSQdOGFxcBU7KgGCPgmLDIU+b4pbgRo?= =?us-ascii?q?BAQ?= X-IronPort-AV: E=Sophos;i="5.51,375,1526342400"; d="scan'208,217";a="145536588" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jul 2018 16:48:42 +0000 Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id w6JGmgo6031896 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Jul 2018 16:48:42 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.1320.4; Thu, 19 Jul 2018 11:48:41 -0500 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.1320.000; Thu, 19 Jul 2018 11:48:41 -0500 From: "Reshad Rahman (rrahman)" To: Luigi Iannone , "lisp@ietf.org list" CC: "lisp-chairs@ietf.org" Thread-Topic: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf Thread-Index: AQHUFRF4S8RPFhS3o0y8DEMd9j1t36SW51KA Date: Thu, 19 Jul 2018 16:48:41 +0000 Message-ID: <57143EB6-CDA5-4553-9410-5B43CC10D5E1@cisco.com> References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> In-Reply-To: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.b.0.180311 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.86.240.61] Content-Type: multipart/alternative; boundary="_000_57143EB6CDA5455394105B43CC10D5E1ciscocom_" MIME-Version: 1.0 X-Outbound-SMTP-Client: 173.37.102.12, xch-rcd-002.cisco.com X-Outbound-Node: rcdn-core-3.cisco.com Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 19 Jul 2018 16:48:46 -0000 --_000_57143EB6CDA5455394105B43CC10D5E1ciscocom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SSBhZ3JlZSB0aGF0IHRoaXMgZG9jdW1lbnQgaXMgcmVhZHkgdG8gYmUgaGFuZGVkIHRvIHRoZSBB RC4NCg0KRnJvbTogbGlzcCA8bGlzcC1ib3VuY2VzQGlldGYub3JnPiBvbiBiZWhhbGYgb2YgTHVp Z2kgSWFubm9uZSA8Z2d4QGdpZ2l4Lm5ldD4NCkRhdGU6IEZyaWRheSwgSnVseSA2LCAyMDE4IGF0 IDY6MDkgQU0NClRvOiAibGlzcEBpZXRmLm9yZyBsaXN0IiA8bGlzcEBpZXRmLm9yZz4NCkNjOiAi bGlzcC1jaGFpcnNAaWV0Zi5vcmciIDxsaXNwLWNoYWlyc0BpZXRmLm9yZz4NClN1YmplY3Q6IFts aXNwXSBXRyBMYXN0IENhbGwgZm9yIGRyYWZ0LWlldGYtbGlzcC12ZW5kb3ItbGNhZg0KDQpGb2xr cywNCg0KQXMgQWxiZXJ0byBtZW50aW9uZWQgaW4gYSBwcmV2aW91cyBtYWlsLCBpbiBMb25kb24g dGhlcmUgd2FzIGNvbnNlbnN1cyB0byBtb3ZlIGZvcndhcmQgZHJhZnQtaWV0Zi1saXNwLXZlbmRv ci1sY2FmIFtodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1saXNwLXZlbmRv ci1sY2FmLTAyXSAoYWZ0ZXIgdGhlIGZldyBmaXhlcyB0aGF0IEkgYXNrZWQpLg0KDQpGaXhlcyBh cmUgZG9uZSwgaGVuY2UsIHRoaXMgZW1haWwgc3RhcnRzIHRoZSB1c3VhbCB0d28gd2Vla3MgV0cg TGFzdCBDYWxsLCB0byBlbmQgSnVseSAyMHRoLCAyMDE4Lg0KDQpQbGVhc2UgcmV2aWV3IHRoaXMg V0cgZG9jdW1lbnQgYW5kIGxldCB0aGUgV0cga25vdyBpZiB5b3UgYWdyZWUgdGhhdCBpdCBpcyBy ZWFkeSBmb3IgaGFuZGluZyB0byB0aGUgQUQuDQpJZiB5b3UgaGF2ZSBvYmplY3Rpb25zLCBwbGVh c2Ugc3RhdGUgeW91ciByZWFzb25zIHdoeSwgYW5kIGV4cGxhaW4gd2hhdCBpdCB3b3VsZCB0YWtl IHRvIGFkZHJlc3MgeW91ciBjb25jZXJucy4NCg0KVGhhbmtzDQoNCkx1aWdpICYgSm9lbA0K --_000_57143EB6CDA5455394105B43CC10D5E1ciscocom_ Content-Type: text/html; charset="utf-8" Content-ID: Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6 IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv cjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJw bGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25v cm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28t bWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1zby1tYXJnaW4tYm90 dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBjbTsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21z by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z LXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQt c3R5bGU6bm9ybWFsO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v bmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEy LjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2 LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPg0KPC9oZWFk Pg0KPGJvZHkgbGFuZz0iRU4tQ0EiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBj bGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJj b2xvcjpibGFjayI+SSBhZ3JlZSB0aGF0IHRoaXMgZG9jdW1lbnQgaXMgcmVhZHkgdG8gYmUgaGFu ZGVkIHRvIHRoZSBBRC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBz dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6 My4wcHQgMGNtIDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9 ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPkZyb206IDwvc3Bhbj48L2I+PHNwYW4gc3R5 bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPmxpc3AgJmx0O2xpc3AtYm91bmNlc0Bp ZXRmLm9yZyZndDsgb24gYmVoYWxmIG9mIEx1aWdpIElhbm5vbmUgJmx0O2dneEBnaWdpeC5uZXQm Z3Q7PGJyPg0KPGI+RGF0ZTogPC9iPkZyaWRheSwgSnVseSA2LCAyMDE4IGF0IDY6MDkgQU08YnI+ DQo8Yj5UbzogPC9iPiZxdW90O2xpc3BAaWV0Zi5vcmcgbGlzdCZxdW90OyAmbHQ7bGlzcEBpZXRm Lm9yZyZndDs8YnI+DQo8Yj5DYzogPC9iPiZxdW90O2xpc3AtY2hhaXJzQGlldGYub3JnJnF1b3Q7 ICZsdDtsaXNwLWNoYWlyc0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+W2xpc3Bd IFdHIExhc3QgQ2FsbCBmb3IgZHJhZnQtaWV0Zi1saXNwLXZlbmRvci1sY2FmPG86cD48L286cD48 L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz cDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIG5hbWU9Il9NYWls T3JpZ2luYWxCb2R5Ij5Gb2xrcywgPG86cD48L286cD48L2E+PC9wPg0KPGRpdj4NCjxwIGNsYXNz PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHki PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPkFz IEFsYmVydG8gbWVudGlvbmVkIGluIGEgcHJldmlvdXMgbWFpbCwgaW4gTG9uZG9uIHRoZXJlIHdh cyBjb25zZW5zdXMgdG8gbW92ZSBmb3J3YXJkIGRyYWZ0LWlldGYtbGlzcC12ZW5kb3ItbGNhZiBb PC9zcGFuPjxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWxp c3AtdmVuZG9yLWxjYWYtMDIiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5h bEJvZHkiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWxpc3AtdmVuZG9y LWxjYWYtMDI8L3NwYW4+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9k eSI+PC9zcGFuPjwvYT48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5 Ij5dJm5ic3A7KGFmdGVyDQogdGhlIGZldyBmaXhlcyB0aGF0IEkgYXNrZWQpLjxvOnA+PC9vOnA+ PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0 eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh biBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5GaXhlcyBhcmUgZG9uZSwg aGVuY2UsIHRoaXMgZW1haWwgc3RhcnRzIHRoZSB1c3VhbCB0d28gd2Vla3MgV0cgTGFzdCBDYWxs LCB0byBlbmQgSnVseSAyMHRoLCAyMDE4LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2tt YXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJr Ol9NYWlsT3JpZ2luYWxCb2R5Ij5QbGVhc2UgcmV2aWV3IHRoaXMgV0cgZG9jdW1lbnQgYW5kIGxl dCB0aGUgV0cga25vdyBpZiB5b3UgYWdyZWUgdGhhdCBpdCBpcyByZWFkeSBmb3IgaGFuZGluZyB0 byB0aGUgQUQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8 cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2lu YWxCb2R5Ij5JZiB5b3UgaGF2ZSBvYmplY3Rpb25zLCBwbGVhc2Ugc3RhdGUgeW91ciByZWFzb25z IHdoeSwgYW5kIGV4cGxhaW4gd2hhdCBpdCB3b3VsZCB0YWtlIHRvIGFkZHJlc3MgeW91ciBjb25j ZXJucy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv Tm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48bzpw PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw YW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+VGhhbmtzPG86cD48L286 cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs Ij48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48c3BhbiBzdHls ZT0iY29sb3I6IzAwQUZDRCI+PGJyPg0KPC9zcGFuPjwvc3Bhbj48c3BhbiBzdHlsZT0ibXNvLWJv b2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5MdWlnaSAmYW1wOyBKb2VsPG86cD48L286cD48L3Nw YW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K --_000_57143EB6CDA5455394105B43CC10D5E1ciscocom_-- From nobody Thu Jul 19 14:35:11 2018 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 AD637130ECB; Thu, 19 Jul 2018 14:35:09 -0700 (PDT) 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 zhhlS9ZCYxJS; Thu, 19 Jul 2018 14:35:06 -0700 (PDT) Received: from mail-pg1-x532.google.com (mail-pg1-x532.google.com [IPv6:2607:f8b0:4864:20::532]) (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 0E5AA130EC8; Thu, 19 Jul 2018 14:35:06 -0700 (PDT) Received: by mail-pg1-x532.google.com with SMTP id y5-v6so4906901pgv.1; Thu, 19 Jul 2018 14:35:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=72SmmOSbB1/48D4HKk4js9j8tIUiLmIDvgEqWqD/2T4=; b=qYnho1ocjFfxk4jWqO4ppRtSyDOr+vwU/KmVm2l6jHVV3eslpJZDJ3BAMDmwLKfdhj 1DMs8b0l8lEWvRpM87lXBySj7mKoKFoaucXi6XIPQc4dSSPwQRib07sRJd6uwHi7H99d N4MpUv08Pe3C1tH6ParDS0mORpeQHardve+onHU0IAiGHaDKSMN3NmMqfQPlygyq2wWw OmaX3utvrjLFkEeAAhvsYrmZIRNeVP6HwX+rOLWkEK0rLUxNo5ah3/F8RijRkV038wcy AKsFNxqU5Zyq8stYpbnW5S7TWZWsMFzYtAJef8m1sy5wagvqGWnkgby9dVJaCG2am0wV BpXQ== 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=72SmmOSbB1/48D4HKk4js9j8tIUiLmIDvgEqWqD/2T4=; b=AT5B2DWRDI6VpXIOoxceZBIiiYqum8BjhFq0z3PvhI27ZqKrKRfhBYG9QO0dxymXc3 BYoYcKJXnukUjgAHgkTtWsr+S5jG4iOXhMTpXvRgkryK0ALXiuv3XIq0r5vJduel8ful JCiN8pMBwP+IERYwpgcmumh1E14feECECKcEke+CzbQuHYrt8t6Mquypi+XOUG3eBkNq nXvYLeQOOimQfTnXzINxLw+kJOaobNHHeYyRDS+uA0yLBXjn/mp9qS9scc5RRNYTtuTB KJzGKjXLOQK8FwU+xslQS746St2MgisSBkCFOQhaJ70D4+xrAscRxThIXUcrf3cUYuv4 T79A== X-Gm-Message-State: AOUpUlHbAcLRPP+1nO5udInx8Zy/qUgf61WRWWcEJ8iNJitYbfPvNFJy zWVMDg7yg1KxWIvDcpibx/RwA7qn X-Google-Smtp-Source: AAOMgpfvmGrq29J73a2EYmuqtepT/rKrL/MycR9CeR06lzO6x5u3UUdVNRoy49oZSxyJxHj3XgsnJQ== X-Received: by 2002:a63:db05:: with SMTP id e5-v6mr11536763pgg.152.1532036105732; Thu, 19 Jul 2018 14:35:05 -0700 (PDT) Received: from sjc-fcoras-nitro2.cisco.com ([128.107.241.176]) by smtp.gmail.com with ESMTPSA id g11-v6sm145034pfh.63.2018.07.19.14.35.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Jul 2018 14:35:05 -0700 (PDT) From: Florin Coras Message-Id: <47D5348D-F84E-47EB-9418-8112ED1E4C79@gmail.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_DC7CB677-9788-4C64-8BFF-E30FBE24A48B" Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Date: Thu, 19 Jul 2018 14:35:03 -0700 In-Reply-To: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> Cc: "lisp@ietf.org list" , lisp-chairs@ietf.org To: Luigi Iannone References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> X-Mailer: Apple Mail (2.3445.8.2) Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 19 Jul 2018 21:35:10 -0000 --Apple-Mail=_DC7CB677-9788-4C64-8BFF-E30FBE24A48B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii I support handing this document to the AD. Florin > On Jul 6, 2018, at 3:06 AM, Luigi Iannone wrote: >=20 > Folks, >=20 > As Alberto mentioned in a previous mail, in London there was consensus = to move forward draft-ietf-lisp-vendor-lcaf = [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02 = ] (after the = few fixes that I asked). >=20 > Fixes are done, hence, this email starts the usual two weeks WG Last = Call, to end July 20th, 2018. >=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 > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp --Apple-Mail=_DC7CB677-9788-4C64-8BFF-E30FBE24A48B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii I support = handing this document to the AD.

Florin

On Jul = 6, 2018, at 3:06 AM, Luigi Iannone <ggx@gigix.net> wrote:

Folks,

As Alberto mentioned in = a previous mail, in London there was consensus to move forward = draft-ietf-lisp-vendor-lcaf [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02]=  (after the few fixes that I asked).

Fixes are done, hence, = this email starts the usual two weeks WG Last Call, to end July 20th, = 2018.

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=_DC7CB677-9788-4C64-8BFF-E30FBE24A48B-- From nobody Thu Jul 19 14:35:59 2018 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 B2959130F16; Thu, 19 Jul 2018 14:35:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -14.51 X-Spam-Level: X-Spam-Status: No, score=-14.51 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, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, 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 HaoQ88KeLrOY; Thu, 19 Jul 2018 14:35:55 -0700 (PDT) Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 250FE130EC8; Thu, 19 Jul 2018 14:35:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=7026; q=dns/txt; s=iport; t=1532036155; x=1533245755; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=bBE2AoHe76mCelRTPRkAGlqMs02XugfBvD2yvYh+RGs=; b=EcbhdDTq73R7mJdFIKECkyWqEmTW8o0bBfmoFiIGYMuNE/TpWVm2twTF m6dELAx4PpponYEbh20srs8mYspsCX3VuXxIUPAzU7envS26Zy4XEdxNP oGeV7EWtxKHtzN2EVC6umIxRTbAj8qN2pKAeXHLBWOaRDU6fR8oDy84zL 8=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CwAAAVA1Fb/5pdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJXdmN/KAqDdIgEjDCCDJArhRAUgWYLI4RJAheCbiE0GAE?= =?us-ascii?q?CAQECAQECbRwMhTYBAQEBAx0GVhACAQgOAwMBAisCAgIwHQgCBAENBYMgAYE?= =?us-ascii?q?bZA+pfYEuhF2FbAWJAlWBQYE4gmqDGQEBA4EqAQ8CAgE+gmExgiQCmWgJAoY?= =?us-ascii?q?LiR+BRIQShn+BF4o/hzcCERSBJB04YXFwFTsqAYI+ixWFPm+KW4EaAQE?= X-IronPort-AV: E=Sophos;i="5.51,376,1526342400"; d="scan'208,217";a="145660715" Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Jul 2018 21:35:54 +0000 Received: from XCH-RTP-013.cisco.com (xch-rtp-013.cisco.com [64.101.220.153]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id w6JLZraH001513 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 19 Jul 2018 21:35:54 GMT Received: from xch-rtp-011.cisco.com (64.101.220.151) by XCH-RTP-013.cisco.com (64.101.220.153) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 19 Jul 2018 17:35:53 -0400 Received: from xch-rtp-011.cisco.com ([64.101.220.151]) by XCH-RTP-011.cisco.com ([64.101.220.151]) with mapi id 15.00.1320.000; Thu, 19 Jul 2018 17:35:53 -0400 From: "Marc Portoles Comeras (mportole)" To: Luigi Iannone , "lisp@ietf.org list" CC: "lisp-chairs@ietf.org" Thread-Topic: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf Thread-Index: AQHUFREBoU5ib0xAdESkZhv4hS/XX6SW9IIA Date: Thu, 19 Jul 2018 21:35:53 +0000 Message-ID: <664A4380-2E20-464C-A825-3620A00901AC@cisco.com> References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> In-Reply-To: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/10.e.1.180613 x-ms-exchange-messagesentrepresentingtype: 1 x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.154.160.56] Content-Type: multipart/alternative; boundary="_000_664A43802E20464CA8253620A00901ACciscocom_" MIME-Version: 1.0 X-Outbound-SMTP-Client: 64.101.220.153, xch-rtp-013.cisco.com X-Outbound-Node: rcdn-core-3.cisco.com Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 19 Jul 2018 21:35:58 -0000 --_000_664A43802E20464CA8253620A00901ACciscocom_ Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SSBhbHNvIHN1cHBvcnQgaGFuZGluZyB0aGlzIGRvY3VtZW50IHRvIHRoZSBBRA0KDQpGcm9tOiBs aXNwIDxsaXNwLWJvdW5jZXNAaWV0Zi5vcmc+IG9uIGJlaGFsZiBvZiBMdWlnaSBJYW5ub25lIDxn Z3hAZ2lnaXgubmV0Pg0KRGF0ZTogRnJpZGF5LCBKdWx5IDYsIDIwMTggYXQgMzowNiBBTQ0KVG86 ICJsaXNwQGlldGYub3JnIGxpc3QiIDxsaXNwQGlldGYub3JnPg0KQ2M6ICJsaXNwLWNoYWlyc0Bp ZXRmLm9yZyIgPGxpc3AtY2hhaXJzQGlldGYub3JnPg0KU3ViamVjdDogW2xpc3BdIFdHIExhc3Qg Q2FsbCBmb3IgZHJhZnQtaWV0Zi1saXNwLXZlbmRvci1sY2FmDQoNCkZvbGtzLA0KDQpBcyBBbGJl cnRvIG1lbnRpb25lZCBpbiBhIHByZXZpb3VzIG1haWwsIGluIExvbmRvbiB0aGVyZSB3YXMgY29u c2Vuc3VzIHRvIG1vdmUgZm9yd2FyZCBkcmFmdC1pZXRmLWxpc3AtdmVuZG9yLWxjYWYgW2h0dHBz Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWxpc3AtdmVuZG9yLWxjYWYtMDJdIChh ZnRlciB0aGUgZmV3IGZpeGVzIHRoYXQgSSBhc2tlZCkuDQoNCkZpeGVzIGFyZSBkb25lLCBoZW5j ZSwgdGhpcyBlbWFpbCBzdGFydHMgdGhlIHVzdWFsIHR3byB3ZWVrcyBXRyBMYXN0IENhbGwsIHRv IGVuZCBKdWx5IDIwdGgsIDIwMTguDQoNClBsZWFzZSByZXZpZXcgdGhpcyBXRyBkb2N1bWVudCBh bmQgbGV0IHRoZSBXRyBrbm93IGlmIHlvdSBhZ3JlZSB0aGF0IGl0IGlzIHJlYWR5IGZvciBoYW5k aW5nIHRvIHRoZSBBRC4NCklmIHlvdSBoYXZlIG9iamVjdGlvbnMsIHBsZWFzZSBzdGF0ZSB5b3Vy IHJlYXNvbnMgd2h5LCBhbmQgZXhwbGFpbiB3aGF0IGl0IHdvdWxkIHRha2UgdG8gYWRkcmVzcyB5 b3VyIGNvbmNlcm5zLg0KDQpUaGFua3MNCg0KTHVpZ2kgJiBKb2VsDQo= --_000_664A43802E20464CA8253620A00901ACciscocom_ Content-Type: text/html; charset="utf-8" Content-ID: <463B2A16CE37084D916A4A1276F2B8C0@emea.cisco.com> Content-Transfer-Encoding: base64 PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4 bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2 IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5 Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNv bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6 bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47 DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQt c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5F bWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1p bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVm YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30N CkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4g MS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9u MTt9DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUi IHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN c29Ob3JtYWwiPkkgYWxzbyBzdXBwb3J0IGhhbmRpbmcgdGhpcyBkb2N1bWVudCB0byB0aGUgQUQ8 bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0 O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9 Im1hcmdpbi1sZWZ0Oi41aW4iPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9y OmJsYWNrIj5Gcm9tOg0KPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtj b2xvcjpibGFjayI+bGlzcCAmbHQ7bGlzcC1ib3VuY2VzQGlldGYub3JnJmd0OyBvbiBiZWhhbGYg b2YgTHVpZ2kgSWFubm9uZSAmbHQ7Z2d4QGdpZ2l4Lm5ldCZndDs8YnI+DQo8Yj5EYXRlOiA8L2I+ RnJpZGF5LCBKdWx5IDYsIDIwMTggYXQgMzowNiBBTTxicj4NCjxiPlRvOiA8L2I+JnF1b3Q7bGlz cEBpZXRmLm9yZyBsaXN0JnF1b3Q7ICZsdDtsaXNwQGlldGYub3JnJmd0Ozxicj4NCjxiPkNjOiA8 L2I+JnF1b3Q7bGlzcC1jaGFpcnNAaWV0Zi5vcmcmcXVvdDsgJmx0O2xpc3AtY2hhaXJzQGlldGYu b3JnJmd0Ozxicj4NCjxiPlN1YmplY3Q6IDwvYj5bbGlzcF0gV0cgTGFzdCBDYWxsIGZvciBkcmFm dC1pZXRmLWxpc3AtdmVuZG9yLWxjYWY8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+PG86cD4m bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn aW4tbGVmdDouNWluIj5Gb2xrcywgPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z b05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41 aW4iPkFzIEFsYmVydG8gbWVudGlvbmVkIGluIGEgcHJldmlvdXMgbWFpbCwgaW4gTG9uZG9uIHRo ZXJlIHdhcyBjb25zZW5zdXMgdG8gbW92ZSBmb3J3YXJkIGRyYWZ0LWlldGYtbGlzcC12ZW5kb3It bGNhZiBbPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbGlz cC12ZW5kb3ItbGNhZi0wMiI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYt bGlzcC12ZW5kb3ItbGNhZi0wMjwvYT5dJm5ic3A7KGFmdGVyDQogdGhlIGZldyBmaXhlcyB0aGF0 IEkgYXNrZWQpLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v cm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0Oi41aW4iPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k aXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVm dDouNWluIj5GaXhlcyBhcmUgZG9uZSwgaGVuY2UsIHRoaXMgZW1haWwgc3RhcnRzIHRoZSB1c3Vh bCB0d28gd2Vla3MgV0cgTGFzdCBDYWxsLCB0byBlbmQgSnVseSAyMHRoLCAyMDE4LjxvOnA+PC9v OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl PSJtYXJnaW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj5QbGVhc2UgcmV2 aWV3IHRoaXMgV0cgZG9jdW1lbnQgYW5kIGxldCB0aGUgV0cga25vdyBpZiB5b3UgYWdyZWUgdGhh dCBpdCBpcyByZWFkeSBmb3IgaGFuZGluZyB0byB0aGUgQUQuPG86cD48L286cD48L3A+DQo8L2Rp dj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVm dDouNWluIj5JZiB5b3UgaGF2ZSBvYmplY3Rpb25zLCBwbGVhc2Ugc3RhdGUgeW91ciByZWFzb25z IHdoeSwgYW5kIGV4cGxhaW4gd2hhdCBpdCB3b3VsZCB0YWtlIHRvIGFkZHJlc3MgeW91ciBjb25j ZXJucy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi IHN0eWxlPSJtYXJnaW4tbGVmdDouNWluIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8 cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6LjVpbiI+VGhhbmtzPG86cD48 L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0 eWxlPSJtYXJnaW4tbGVmdDouNWluIj48c3BhbiBzdHlsZT0iY29sb3I6IzAwQUZDRCI+PGJyPg0K PC9zcGFuPkx1aWdpICZhbXA7IEpvZWw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8 L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg== --_000_664A43802E20464CA8253620A00901ACciscocom_-- From nobody Thu Jul 19 20:53:32 2018 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 183F61277D2; Thu, 19 Jul 2018 20:53:25 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.82.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: lisp@ietf.org Message-ID: <153205880502.10600.44046491579488289@ietfa.amsl.com> Date: Thu, 19 Jul 2018 20:53:25 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-gpe-04.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 03:53:25 -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 WG of the IETF. Title : LISP Generic Protocol Extension Authors : Fabio Maino John Lemon Puneet Agarwal Darrel Lewis Michael Smith Filename : draft-ietf-lisp-gpe-04.txt Pages : 9 Date : 2018-07-19 Abstract: This document describes extending the Locator/ID Separation Protocol (LISP) Data-Plane, via changes to the LISP header, to support multi- protocol encapsulation. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-gpe/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-lisp-gpe-04 https://datatracker.ietf.org/doc/html/draft-ietf-lisp-gpe-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-gpe-04 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 Thu Jul 19 22:32:50 2018 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 8FB38130E72 for ; Thu, 19 Jul 2018 22:32:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 LYIqN_rk0QdD for ; Thu, 19 Jul 2018 22:32:44 -0700 (PDT) Received: from roura.ac.upc.es (roura.ac.upc.edu [147.83.33.10]) by ietfa.amsl.com (Postfix) with ESMTP id CFE52130E40 for ; Thu, 19 Jul 2018 22:32:43 -0700 (PDT) Received: from correu-1.ac.upc.es (correu-1.ac.upc.es [147.83.30.91]) by roura.ac.upc.es (8.13.8/8.13.8) with ESMTP id w6K5Wfxe007689 for ; Fri, 20 Jul 2018 07:32:41 +0200 Received: from [147.83.35.39] (sirius.ac.upc.es [147.83.35.39]) by correu-1.ac.upc.es (Postfix) with ESMTPSA id C828C35B for ; Fri, 20 Jul 2018 07:32:35 +0200 (CEST) To: lisp@ietf.org References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> <664A4380-2E20-464C-A825-3620A00901AC@cisco.com> From: =?UTF-8?Q?Albert_L=c3=b3pez?= Message-ID: <95c54d74-3a35-fdc6-658f-fe1fec7a4bfc@ac.upc.edu> Date: Fri, 20 Jul 2018 07:32:35 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <664A4380-2E20-464C-A825-3620A00901AC@cisco.com> Content-Type: multipart/alternative; boundary="------------B6E64D511375F07D2D6C3A85" Content-Language: ca Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 05:32:49 -0000 This is a multi-part message in MIME format. --------------B6E64D511375F07D2D6C3A85 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit +1 On 19/7/18 23:35, Marc Portoles Comeras (mportole) wrote: > > I also support handing this document to the AD > > *From: *lisp on behalf of Luigi Iannone > > *Date: *Friday, July 6, 2018 at 3:06 AM > *To: *"lisp@ietf.org list" > *Cc: *"lisp-chairs@ietf.org" > *Subject: *[lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf > > Folks, > > As Alberto mentioned in a previous mail, in London there was consensus > to move forward draft-ietf-lisp-vendor-lcaf > [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after > the few fixes that I asked). > > Fixes are done, hence, this email starts the usual two weeks WG Last > Call, to end July 20th, 2018. > > 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 --------------B6E64D511375F07D2D6C3A85 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit
+1

On 19/7/18 23:35, Marc Portoles Comeras (mportole) wrote:

I also support handing this document to the AD

 

From: lisp <lisp-bounces@ietf.org> on behalf of Luigi Iannone <ggx@gigix.net>
Date: Friday, July 6, 2018 at 3:06 AM
To: "lisp@ietf.org list" <lisp@ietf.org>
Cc: "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>
Subject: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf

 

Folks,

 

As Alberto mentioned in a previous mail, in London there was consensus to move forward draft-ietf-lisp-vendor-lcaf [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after the few fixes that I asked).

 

Fixes are done, hence, this email starts the usual two weeks WG Last Call, to end July 20th, 2018.

 

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

--------------B6E64D511375F07D2D6C3A85-- From nobody Fri Jul 20 01:59:05 2018 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 AE09F1310E6 for ; Fri, 20 Jul 2018 01:59:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 zKA3Uyp0hyA0 for ; Fri, 20 Jul 2018 01:58:59 -0700 (PDT) Received: from roura.ac.upc.es (roura.ac.upc.es [147.83.33.10]) by ietfa.amsl.com (Postfix) with ESMTP id 3E6EB1310E2 for ; Fri, 20 Jul 2018 01:58:59 -0700 (PDT) Received: from correu-1.ac.upc.es (correu-1.ac.upc.es [147.83.30.91]) by roura.ac.upc.es (8.13.8/8.13.8) with ESMTP id w6K8wwF0011675; Fri, 20 Jul 2018 10:58:58 +0200 Received: from [147.83.35.236] (dync-35-236.ac.upc.es [147.83.35.236]) by correu-1.ac.upc.es (Postfix) with ESMTPSA id C73441D8; Fri, 20 Jul 2018 10:58:52 +0200 (CEST) To: =?UTF-8?Q?Albert_L=c3=b3pez?= , lisp@ietf.org References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> <664A4380-2E20-464C-A825-3620A00901AC@cisco.com> <95c54d74-3a35-fdc6-658f-fe1fec7a4bfc@ac.upc.edu> From: =?UTF-8?Q?Jordi_Pailliss=c3=a9_Vilanova?= Message-ID: Date: Fri, 20 Jul 2018 10:58:52 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <95c54d74-3a35-fdc6-658f-fe1fec7a4bfc@ac.upc.edu> Content-Type: multipart/alternative; boundary="------------2584FAABFF9A0935BAFB96FA" Content-Language: en-US Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 08:59:03 -0000 This is a multi-part message in MIME format. --------------2584FAABFF9A0935BAFB96FA Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Support Jordi El 20/07/18 a les 07:32, Albert López ha escrit: > +1 > > On 19/7/18 23:35, Marc Portoles Comeras (mportole) wrote: >> >> I also support handing this document to the AD >> >> *From: *lisp on behalf of Luigi Iannone >> >> *Date: *Friday, July 6, 2018 at 3:06 AM >> *To: *"lisp@ietf.org list" >> *Cc: *"lisp-chairs@ietf.org" >> *Subject: *[lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf >> >> Folks, >> >> As Alberto mentioned in a previous mail, in London there was >> consensus to move forward draft-ietf-lisp-vendor-lcaf >> [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after >> the few fixes that I asked). >> >> Fixes are done, hence, this email starts the usual two weeks WG Last >> Call, to end July 20th, 2018. >> >> 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 > > > > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp --------------2584FAABFF9A0935BAFB96FA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Support

Jordi


El 20/07/18 a les 07:32, Albert López ha escrit:
+1

On 19/7/18 23:35, Marc Portoles Comeras (mportole) wrote:

I also support handing this document to the AD

 

From: lisp <lisp-bounces@ietf.org> on behalf of Luigi Iannone <ggx@gigix.net>
Date: Friday, July 6, 2018 at 3:06 AM
To: "lisp@ietf.org list" <lisp@ietf.org>
Cc: "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>
Subject: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf

 

Folks,

 

As Alberto mentioned in a previous mail, in London there was consensus to move forward draft-ietf-lisp-vendor-lcaf [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after the few fixes that I asked).

 

Fixes are done, hence, this email starts the usual two weeks WG Last Call, to end July 20th, 2018.

 

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




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

--------------2584FAABFF9A0935BAFB96FA-- From nobody Fri Jul 20 06:29:47 2018 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 6569613113C for ; Fri, 20 Jul 2018 06:29:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 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, URIBL_BLOCKED=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 a2-I-WtKcUaK for ; Fri, 20 Jul 2018 06:29:43 -0700 (PDT) Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::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 22EBE130DE7 for ; Fri, 20 Jul 2018 06:29:43 -0700 (PDT) Received: by mail-yw0-x229.google.com with SMTP id l189-v6so4336611ywb.10 for ; Fri, 20 Jul 2018 06:29:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=36um1elopiPcvagW8XEzazpTO+sNgFpI3egcVa/wmU8=; b=q7Go+REf0To2A7Eavr83bQ2q6VgwNUgVGaM/FNgnaFiFznrj2vJMhaB53w2BwEjDrr fGgTjmcRpBUORkGK3IxqOAtNwfUABc9ALP60rkL0h1stLpOJ1CMiz5lHxa0mZNK17mgY hP7aYn457psd89c/q8kqQJxymjzDiQHi2t/6bj0P6fQ51W+6qCZzo1Pw6r+oJyM/yKl7 +s4AMQ0DTEih+hX/yaMkzDDB4c8K/vq52BflUiTB3lD0slZOzkRuUdgFsrWPSnqBFTye ppKhguE2m0t5gqdtDPPNLo0aPwoXQY+W8iQDTGT/olhAX5pQxSA+5XEJNbeOZD/LIhjK HjSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=36um1elopiPcvagW8XEzazpTO+sNgFpI3egcVa/wmU8=; b=rmUaG4RgdfDAeD60OBV8BAW8lWenO44zx+4X16afLET7kedVDm0vmqEAz7ga9UTzj5 4EsNb9v/fj5wB9+HQvIuCExZ9ZKiAuBhvyVqgT7Wx8fC9+YXMm947QLZzmO7nrxHfw4w Z7EL8KQe9Dtt7HOOOOaEaNWo4StUIPa3QNA5bXefUsOu557zgfidpNsAEj3UX/7Xzx2H AP5uKyGGCoHzu4PIWHd7AtNHrxvZu+XoPFYFNoXWVlJSahwXcHYL1bd8W4K7sKbTa5mt 0zH8dcHFIMmVRHIX3LyUaGUpxBxctnqERZ0alTKyR9Ja5Ozl6LIV9vjH1fdLXmDdUu+g tsPw== X-Gm-Message-State: AOUpUlGVtQ/eYeGEFo/MpLNpUvpP6e6/fppKk/MGCuKPr2D6BsM0fUeO mLIbDZmtyTUXV53s8AG/arRmXDVp/zuP7byuj5QLKKFd X-Google-Smtp-Source: AAOMgpdGddw+8wbNJTrtsR47IA/N3ifq0ZYUnZP4JObl6+7P+RuBN82AC0OBRmd/iCBTylh0YVASNH9/68Xv6FTivnY= X-Received: by 2002:a81:af0b:: with SMTP id n11-v6mr989802ywh.211.1532093381940; Fri, 20 Jul 2018 06:29:41 -0700 (PDT) MIME-Version: 1.0 References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> <664A4380-2E20-464C-A825-3620A00901AC@cisco.com> <95c54d74-3a35-fdc6-658f-fe1fec7a4bfc@ac.upc.edu> In-Reply-To: From: Albert Cabellos Date: Fri, 20 Jul 2018 09:29:30 -0400 Message-ID: To: "lisp@ietf.org list" Content-Type: multipart/alternative; boundary="000000000000cb1cba05716e4906" Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 13:29:46 -0000 --000000000000cb1cba05716e4906 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Support Albert On Fri, Jul 20, 2018 at 4:59 AM Jordi Pailliss=C3=A9 Vilanova wrote: > Support > > Jordi > > El 20/07/18 a les 07:32, Albert L=C3=B3pez ha escrit: > > +1 > > On 19/7/18 23:35, Marc Portoles Comeras (mportole) wrote: > > I also support handing this document to the AD > > > > *From: *lisp on behalf of > Luigi Iannone > *Date: *Friday, July 6, 2018 at 3:06 AM > *To: *"lisp@ietf.org list" > > *Cc: *"lisp-chairs@ietf.org" > > *Subject: *[lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf > > > > Folks, > > > > As Alberto mentioned in a previous mail, in London there was consensus to > move forward draft-ietf-lisp-vendor-lcaf [ > https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02] (after the > few fixes that I asked). > > > > Fixes are done, hence, this email starts the usual two weeks WG Last Call= , > to end July 20th, 2018. > > > > 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. > > > > Thanks > > > Luigi & Joel > > > _______________________________________________ > lisp mailing listlisp@ietf.orghttps://www.ietf.org/mailman/listinfo/lisp > > > > > _______________________________________________ > lisp mailing listlisp@ietf.orghttps://www.ietf.org/mailman/listinfo/lisp > > > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp > --000000000000cb1cba05716e4906 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Support

Albert

On Fri, Jul 20, 2018 at 4:59 AM Jordi Pa= illiss=C3=A9 Vilanova <jordip@ac.up= c.edu> wrote:
=20 =20 =20

Support

Jordi


El 20/07/18 a les 0= 7:32, Albert L=C3=B3pez ha escrit:
=20
+1

On 19/7/18 23:35, Marc Portoles Comeras (mportole) wrote:
=20 =20 =20

I also support handing this document to the AD

=C2=A0

From: lisp <lisp-bo= unces@ietf.org> on behalf of Luigi Iannone <= ;ggx@gigix.net>
Date: Friday, July 6, 2018 at 3:06 AM
To: "lisp@ietf= .org list" <lisp@ietf= .org>
Cc: "lisp-c= hairs@ietf.org" <lisp-chair= s@ietf.org>
Subject: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf

=C2=A0=

Folks, <= u>

=C2=A0=

As Alberto mentioned in a previous mail, in London there was consensus to move forward draft-ietf-lisp-vendor-lcaf [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02]=C2= =A0(after the few fixes that I asked).

=C2=A0=

Fixes are done, hence, this email starts the usual two weeks WG Last Call, to end July 20th, 2018.

= =C2=A0

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.<= /p>

=C2= =A0

Thanks=


Luigi & Joel



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




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

_______________________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp
--000000000000cb1cba05716e4906-- From nobody Fri Jul 20 07:05:22 2018 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 05AF3130DF0 for ; Fri, 20 Jul 2018 07:05:20 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.909 X-Spam-Level: X-Spam-Status: No, score=-1.909 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, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=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 lJTt9g0mAK26 for ; Fri, 20 Jul 2018 07:05:18 -0700 (PDT) Received: from mail-it0-x22a.google.com (mail-it0-x22a.google.com [IPv6:2607:f8b0:4001:c0b::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 10C4B130DFF for ; Fri, 20 Jul 2018 07:05:17 -0700 (PDT) Received: by mail-it0-x22a.google.com with SMTP id p17-v6so14723173itc.2 for ; Fri, 20 Jul 2018 07:05:17 -0700 (PDT) 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=cOtGjCWgBWzpBguRCmVKiIFm/7MPHjDfTO1+97ofpZA=; b=2H9nN0vCRrgA2OFr+HEnCTMQwFwRO7gC8cYe2VCnbSn+W9sMPJsSAFESPnvrfyJJcw 125dLxEXIkc/WP3n95ivE3uP+fOuOM21m2xcpE/CmGfbPYJUohCNxusVAjYRqVjlYVdK kwggJlVBf5ege4nHj2IPklVYqOlJ211+0SkfmtHU3MVy53VnBT7eEC5sTh1bKJlFNm0i Wqm41o4KJbcjLivtWsUcSlAlqIQ66anBLfHWBByOf16XCP42VgaGXXLSj+ncDRWEIHbM voUzNltvilzrfqyLARs4mXHIwXsFLWYWNa5Bf69ejgp7Gbghj42SOFyuzkAyBCidGlSJ xPFA== 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=cOtGjCWgBWzpBguRCmVKiIFm/7MPHjDfTO1+97ofpZA=; b=i9qznWFVsj0dqQU/1LkV2y7w2UD9MDok8vBV4RWw8a+3kja5YHRbtCniUxV7jzzOGc 6DFbBG6hSG7+ozOeJDtPiGqJJ2qDlSjLpYfjoKX2fGh8mOpv/pSSEffCayRCTcZVb2tn aS2YMhWszAYMh0ysol0jqpQ5kGamfuK5zLyDnoTJY+oL8LaH/+PEgpy8suoME7fCj05u 5W5dXluGJTeHKuQc7+Fvs//n2cHm3R4+TYqPMUBvNBoG4W4kRUmkt+jvSKsFawIhhDJP GLOrHCnaXfUUVpP+Nrym8Vgq2DnPRpB963+wVF5PQZ3xm+HmKMIE/JJTr1QAei3Cn1Hc cVRQ== X-Gm-Message-State: AOUpUlFbhIaO9RovDHBshA6zJ2P+jqz28IJ7fBG5gaupjduEPx0KvKGE EI5fHLJ8hhdSbcYWwPBNxckEjjb1SN85Zg== X-Google-Smtp-Source: AAOMgpeXPkIuJc955VAnLrTQQrpSQjGAYopfpsYbebO6yHsTUQBC31WuZJrws5GresX5SNAHcmj52g== X-Received: by 2002:a02:8895:: with SMTP id n21-v6mr1928483jaj.21.1532095515791; Fri, 20 Jul 2018 07:05:15 -0700 (PDT) Received: from ?IPv6:2001:67c:1232:144:e062:b7f5:d64c:4288? ([2001:67c:1232:144:e062:b7f5:d64c:4288]) by smtp.gmail.com with ESMTPSA id q204-v6sm976476itb.27.2018.07.20.07.05.13 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Jul 2018 07:05:14 -0700 (PDT) From: Luigi Iannone Message-Id: <4B576DA3-4ABA-486D-9D9E-94B53A589165@gigix.net> Content-Type: multipart/alternative; boundary="Apple-Mail=_60DC4647-6B04-46C8-88A8-33B63EC1F39E" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Date: Fri, 20 Jul 2018 10:05:12 -0400 In-Reply-To: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> Cc: lisp-chairs@ietf.org To: "lisp@ietf.org list" References: <264A0327-FBC2-4768-89DA-53BEE10AC6CF@gigix.net> X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [lisp] WG Last Call for draft-ietf-lisp-vendor-lcaf X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 20 Jul 2018 14:05:20 -0000 --Apple-Mail=_60DC4647-6B04-46C8-88A8-33B63EC1F39E Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii HI All, the WG LC for this document is now closed. We received several email in support of the document, confirming the = consensus reach in London. As usual the shepherd writeup will follow and the document will then be = handed over to our AD. Ciao L. > On 6 Jul 2018, at 06:06, Luigi Iannone wrote: >=20 > Folks, >=20 > As Alberto mentioned in a previous mail, in London there was consensus = to move forward draft-ietf-lisp-vendor-lcaf = [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02 = ] (after the = few fixes that I asked). >=20 > Fixes are done, hence, this email starts the usual two weeks WG Last = Call, to end July 20th, 2018. >=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=_60DC4647-6B04-46C8-88A8-33B63EC1F39E Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii HI = All,

the WG LC for = this document is now closed.

We received several email in support of = the document, confirming the consensus reach in London.

As usual the shepherd = writeup will follow and the document will then be handed over to our = AD.

Ciao

L.


On 6 Jul = 2018, at 06:06, Luigi Iannone <ggx@gigix.net> wrote:

Folks,

As Alberto mentioned in = a previous mail, in London there was consensus to move forward = draft-ietf-lisp-vendor-lcaf [https://tools.ietf.org/html/draft-ietf-lisp-vendor-lcaf-02]=  (after the few fixes that I asked).

Fixes are done, hence, = this email starts the usual two weeks WG Last Call, to end July 20th, = 2018.

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=_60DC4647-6B04-46C8-88A8-33B63EC1F39E-- From nobody Wed Jul 25 02:35:51 2018 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 2EE70130F76 for ; Wed, 25 Jul 2018 02:35:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 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_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=bartschnet.de 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 mmar1tlYUm6Q for ; Wed, 25 Jul 2018 02:35:48 -0700 (PDT) Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 C416E130E1E for ; Wed, 25 Jul 2018 02:35:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bartschnet.de; s=2018030201; h=Content-Transfer-Encoding:MIME-Version:Date: Message-ID:Subject:From:To:content-disposition; bh=LLw2QDN3nAhmwAxsdhZFJrtCXFqzNj4+8QxZEYfM8ho=; b=VSusz1whk6CfQGgBj2fYqR73Xs tklmoKKieBhbt2Lo+p4at1Q5PU06Ki9h/3xjUfvJ0UqEMrlkJoAT5bu+5njsqGvW4vIAWCvnHemzJ 4bW4xIZ4wEFdM9fU+EXhbiGD7sYPxqaWdpeYEda+jFCflEj5pbPscgD1ss3RLL0qHRIWLhLNkoBku h2ENh+He99LDHKCDyr2aD0ZjiT9fPWWkI6nBEsQG8h5YVIZh2OyvgkJ5dFYifIP4I+tKMI8T3vlP3 K1KkQkg+Q8S4yCmYu7rmYDnAKc/Dsn0s7kbnqB+KAhKvsexTtLw1miJoC1wm+AlWiZ2WH+FVsuTju SHFD6xULXmCz+A+ft0SE7EunXpS7HUzQ5boEd4V9abm7hljE0kdb7ebn8bxZscKks53160BaR8CTB KUczO+maEa84F4LsyfJOfoXPcyQTvZvyyZgs0V/FFZX6qcU+91Ol8WUm6XadHySwuCBsYFp4gU9um II0w+kEAfTLDgWUHH4edGZ/jL6J7EtD8rYOfXrEX9lTV5Rgw2Kzi8B8MAJSRBhvmM2pIK9El2+8nX 9+hg5+bce+cTszGrnLG66dBrfA4sP+opeHOdpcd4r/Zvnwe/6caUcxnnpBKayDrJSIX2DtoQ+VO+g 9739k7+vqU3iEXmohcU+eRxe6/WeF86i8qYauKnEk=; Received: from localhost (localhost [127.0.0.1]) by mail.core-networks.de id 1fiGCu-00015F-0f with ESMTPSA (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) for lisp@ietf.org; Wed, 25 Jul 2018 11:35:45 +0200 To: "lisp@ietf.org list" From: "Rene 'Renne' Bartsch, B.Sc. Informatics" Message-ID: Date: Wed, 25 Jul 2018 11:35:43 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 7bit Archived-At: Subject: [lisp] Current IP addresses of LispBeta network servers? X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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: Wed, 25 Jul 2018 09:35:50 -0000 Hi, is there any current list with the IPv4/IPv6 addresses of map-servers, map-resolvers, PETRs and PITRs? Best regards, Renne From nobody Wed Jul 25 02:45:09 2018 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 910D612DD85 for ; Wed, 25 Jul 2018 02:45:06 -0700 (PDT) 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_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 6szReeuBCyob for ; Wed, 25 Jul 2018 02:45:02 -0700 (PDT) Received: from roura.ac.upc.es (roura.ac.upc.edu [147.83.33.10]) by ietfa.amsl.com (Postfix) with ESMTP id A07F6126DBF for ; Wed, 25 Jul 2018 02:45:01 -0700 (PDT) Received: from correu-1.ac.upc.es (correu-1.ac.upc.es [147.83.30.91]) by roura.ac.upc.es (8.13.8/8.13.8) with ESMTP id w6P9ipva021079; Wed, 25 Jul 2018 11:44:51 +0200 Received: from [147.83.35.39] (sirius.ac.upc.es [147.83.35.39]) by correu-1.ac.upc.es (Postfix) with ESMTPSA id 1DB92171; Wed, 25 Jul 2018 11:44:46 +0200 (CEST) To: "Rene 'Renne' Bartsch, B.Sc. Informatics" , "lisp@ietf.org list" References: From: =?UTF-8?Q?Albert_L=c3=b3pez?= Message-ID: <335f7212-c0f8-cef5-86d6-9200ec3bdd0c@ac.upc.edu> Date: Wed, 25 Jul 2018 11:44:45 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-GB Archived-At: Subject: Re: [lisp] Current IP addresses of LispBeta network servers? X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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: Wed, 25 Jul 2018 09:45:07 -0000 Hi Renne, If you refer to the ones of LISP beta network, you can find them in https://www.lisp4.net//images/lisp-ddt.pdf. From this list, you only have to remove NTT-AMER-PXTR which is broken. We are currently trying to replace it. Best regards Albert On 25/7/18 11:35, Rene 'Renne' Bartsch, B.Sc. Informatics wrote: > Hi, > > is there any current list with the IPv4/IPv6 addresses of map-servers, > map-resolvers, PETRs and PITRs? > > > Best regards, > > Renne > > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp From nobody Wed Jul 25 02:52:06 2018 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 9D46C126DBF for ; Wed, 25 Jul 2018 02:52:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.701 X-Spam-Level: X-Spam-Status: No, score=-2.701 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_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (4096-bit key) header.d=bartschnet.de 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 4Mm-tol7L5NL for ; Wed, 25 Jul 2018 02:52:03 -0700 (PDT) Received: from mail.core-networks.de (mail.core-networks.de [IPv6:2001:1bc0:d::4:9]) (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 C2A1A12DD85 for ; Wed, 25 Jul 2018 02:52:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bartschnet.de; s=2018030201; h=Content-Transfer-Encoding:MIME-Version:Date: Message-ID:From:To:Subject:content-disposition; bh=IsfKLsYvH9aMjpwTkUYSu/2fcqqtPss3Ih+dG9byGWA=; b=XVzoq4qLmeTuROrj/1ws/NZN0K jIgX7MGVNwnxVumQUxfstPsMvqC7S9PUhmeodHE7eqqonzRFuv4HDTMcAs+huP1WnfeHde+Xm1PmG TXJVHawtv4ZxjB6ZkRkkC4PvkYnybxzAmUm3tc9SmyTadoEpxERqO88JVM7pVNh9jhSTVG81MAFFf 2iw2+8p+9dHcjU09FnxxUUrP4FTMdMlfsK6tzs4oXAXoMGr50APhJbsQvAatrGQScgLtSWhVXvha0 XszqFFv4vocA3muMOLWTsVadjidf+QxVC92WWTr6NCQ5uXT9usVFuNHLpvllvoPtlLJRZ8Qip5nRK AZrzIMyolNOJPmY0ZRCgltMzQr47rkQNh7ieHA14ggmZ6fINuoVrN+EKXH0R564unIsIueYr8qN4s uUXZYwRfRdaFwflPfJobMkjeKIH153tJGhFEqrAvddNQFt2V5/Fh2O34lgauMx8cwH1FnDyGYbE7q CpJ5pLjnRKBr6XIXXh9gMepR0MEkhRljV7EdXWcAvJM/zeRSasLocF3EkptErdlu+51sconco0S4o 8akpPB6ZwT4t/dcDtR/+YfKJ3qsMhIVDNcUWXFKZ471EmLnsfDd2jBJMHtf7hKmxlQnaMQkMo22WZ Z5SkLIFlaH6nSxi6eJO0Dp30G2ui1VaxZhSWrPg9E=; Received: from localhost (localhost [127.0.0.1]) by mail.core-networks.de id 1fiGSd-0001yT-Hn with ESMTPSA (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) for lisp@ietf.org; Wed, 25 Jul 2018 11:52:01 +0200 To: "lisp@ietf.org list" References: <335f7212-c0f8-cef5-86d6-9200ec3bdd0c@ac.upc.edu> From: "Rene 'Renne' Bartsch, B.Sc. Informatics" Message-ID: Date: Wed, 25 Jul 2018 11:51:59 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <335f7212-c0f8-cef5-86d6-9200ec3bdd0c@ac.upc.edu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: de-DE Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [lisp] Current IP addresses of LispBeta network servers? X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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: Wed, 25 Jul 2018 09:52:05 -0000 Hi Albert, the following servers have no IPv6 addresses listed: CISCO-SJC-MR-MS-1 EQX-ASH-MR-MS INTOUCH-MR-MS-1 INTOUCH-PXTR-1 SG-NUS-MR-MS Do they lack IPv6 connectivity? Best regards Renne Am 25.07.2018 um 11:44 schrieb Albert López: > Hi Renne, > > If you refer to the ones of LISP beta network, you can find them in https://www.lisp4.net//images/lisp-ddt.pdf. From this list, you only have to remove NTT-AMER-PXTR which is broken. We are currently trying to replace it. > > Best regards > > Albert > > On 25/7/18 11:35, Rene 'Renne' Bartsch, B.Sc. Informatics wrote: >> Hi, >> >> is there any current list with the IPv4/IPv6 addresses of map-servers, map-resolvers, PETRs and PITRs? >> >> >> Best regards, >> >> Renne >> >> _______________________________________________ >> lisp mailing list >> lisp@ietf.org >> https://www.ietf.org/mailman/listinfo/lisp > From nobody Wed Jul 25 03:05:51 2018 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 3C68B130F76 for ; Wed, 25 Jul 2018 03:05:49 -0700 (PDT) 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_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 SxjSEhbuGj52 for ; Wed, 25 Jul 2018 03:05:47 -0700 (PDT) Received: from roura.ac.upc.es (roura.ac.upc.es [147.83.33.10]) by ietfa.amsl.com (Postfix) with ESMTP id 10E6D130E5A for ; Wed, 25 Jul 2018 03:05:46 -0700 (PDT) Received: from correu-2.ac.upc.es (correu-2.ac.upc.es [147.83.30.92]) by roura.ac.upc.es (8.13.8/8.13.8) with ESMTP id w6PA5gkP021574; Wed, 25 Jul 2018 12:05:42 +0200 Received: from [147.83.35.39] (sirius.ac.upc.es [147.83.35.39]) by correu-2.ac.upc.es (Postfix) with ESMTPSA id B3DAE386; Wed, 25 Jul 2018 12:05:37 +0200 (CEST) To: "Rene 'Renne' Bartsch, B.Sc. Informatics" , "lisp@ietf.org list" References: <335f7212-c0f8-cef5-86d6-9200ec3bdd0c@ac.upc.edu> From: =?UTF-8?Q?Albert_L=c3=b3pez?= Message-ID: Date: Wed, 25 Jul 2018 12:05:37 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-ZA Archived-At: Subject: Re: [lisp] Current IP addresses of LispBeta network servers? X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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: Wed, 25 Jul 2018 10:05:49 -0000 Yes, that's right. These nodes doesn't have IPv6 connectivity.  Intouch-pxtr-1 has IPv6 but it is only used for PiTR but not for PeTR as IPv6 connectivity in this node is provided through a tunnel and it is better users use other IPv6 PeTRs Best regards Albert On 25/7/18 11:51, Rene 'Renne' Bartsch, B.Sc. Informatics wrote: > Hi Albert, > > the following servers have no IPv6 addresses listed: > > CISCO-SJC-MR-MS-1 > EQX-ASH-MR-MS > INTOUCH-MR-MS-1 > INTOUCH-PXTR-1 > SG-NUS-MR-MS > > Do they lack IPv6 connectivity? > > Best regards > > Renne > > > Am 25.07.2018 um 11:44 schrieb Albert López: >> Hi Renne, >> >> If you refer to the ones of LISP beta network, you can find them in >> https://www.lisp4.net//images/lisp-ddt.pdf. From this list, you only >> have to remove NTT-AMER-PXTR which is broken. We are currently trying >> to replace it. >> >> Best regards >> >> Albert >> >> On 25/7/18 11:35, Rene 'Renne' Bartsch, B.Sc. Informatics wrote: >>> Hi, >>> >>> is there any current list with the IPv4/IPv6 addresses of >>> map-servers, map-resolvers, PETRs and PITRs? >>> >>> >>> Best regards, >>> >>> Renne >>> >>> _______________________________________________ >>> lisp mailing list >>> lisp@ietf.org >>> https://www.ietf.org/mailman/listinfo/lisp >> > > _______________________________________________ > lisp mailing list > lisp@ietf.org > https://www.ietf.org/mailman/listinfo/lisp From nobody Wed Jul 25 13:23:27 2018 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 6D7F612E039; Wed, 25 Jul 2018 13:23:25 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Luigi Iannone To: X-Test-IDTracker: no X-IETF-IDTracker: 6.82.0 Auto-Submitted: auto-generated Precedence: bulk Cc: Luigi Iannone , lisp-chairs@ietf.org, iesg-secretary@ietf.org, lisp@ietf.org, ggx@gigix.net Message-ID: <153255020544.15259.9464302577088340776.idtracker@ietfa.amsl.com> Date: Wed, 25 Jul 2018 13:23:25 -0700 Archived-At: Subject: [lisp] Publication has been requested for draft-ietf-lisp-gpe-04 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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: Wed, 25 Jul 2018 20:23:26 -0000 Luigi Iannone has requested publication of draft-ietf-lisp-gpe-04 as Proposed Standard on behalf of the LISP working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-lisp-gpe/ From nobody Wed Jul 25 13:32:41 2018 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 8988F130EF9; Wed, 25 Jul 2018 13:32:29 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Luigi Iannone To: X-Test-IDTracker: no X-IETF-IDTracker: 6.82.0 Auto-Submitted: auto-generated Precedence: bulk Cc: Luigi Iannone , lisp-chairs@ietf.org, iesg-secretary@ietf.org, lisp@ietf.org, ggx@gigix.net Message-ID: <153255074955.15437.4564178940335529729.idtracker@ietfa.amsl.com> Date: Wed, 25 Jul 2018 13:32:29 -0700 Archived-At: Subject: [lisp] Publication has been requested for draft-ietf-lisp-rfc6830bis-14 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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: Wed, 25 Jul 2018 20:32:37 -0000 Luigi Iannone has requested publication of draft-ietf-lisp-rfc6830bis-14 as Proposed Standard on behalf of the LISP working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6830bis/ From nobody Thu Jul 26 16:47:37 2018 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 41428130DF0; Thu, 26 Jul 2018 16:47:28 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: Cc: lisp@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.83.0 Auto-Submitted: auto-generated Precedence: bulk Reply-To: lisp@ietf.org Message-ID: <153264884821.24798.1081006899896767963@ietfa.amsl.com> Date: Thu, 26 Jul 2018 16:47:28 -0700 Archived-At: Subject: [lisp] I-D Action: draft-ietf-lisp-rfc6833bis-12.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 26 Jul 2018 23:47:29 -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 WG of the IETF. Title : Locator/ID Separation Protocol (LISP) Control-Plane Authors : Vince Fuller Dino Farinacci Albert Cabellos Filename : draft-ietf-lisp-rfc6833bis-12.txt Pages : 48 Date : 2018-07-26 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 modularity with different database designs. Since these devices implement the "edge" of the LISP Control-Plane infrastructure, connect directly to LISP-capable Internet end sites, and comprising the bulk of LISP-speaking devices, reducing their implementation and operational complexity should also reduce the overall cost and effort of deploying LISP. This document obsoletes RFC 6833. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6833bis/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-lisp-rfc6833bis-12 https://datatracker.ietf.org/doc/html/draft-ietf-lisp-rfc6833bis-12 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-rfc6833bis-12 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 Fri Jul 27 12:45:53 2018 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 A69E6130DCD; Fri, 27 Jul 2018 12:45:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.768 X-Spam-Level: X-Spam-Status: No, score=-0.768 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 4sKcHlpuxSxd; Fri, 27 Jul 2018 12:45:32 -0700 (PDT) Received: from mail-wm0-x22a.google.com (mail-wm0-x22a.google.com [IPv6:2a00:1450:400c:c09::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 E6615130DCA; Fri, 27 Jul 2018 12:45:31 -0700 (PDT) Received: by mail-wm0-x22a.google.com with SMTP id o18-v6so6711233wmc.0; Fri, 27 Jul 2018 12:45:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:from:date:message-id:subject:to:cc; bh=YU/en7owh81aieivR5b29psZ7v0c290n84w9nYunaWs=; b=n27YkrC+DTcEFp/66HcCugjz1S5sLqjVtj8AScxyJyUBWFtOoJREQyyWnh/40olPho 15bTXZscCVNyyAXeMkNGQyaJfjV40NbrlUTCk2sKntpHh3ghBUmSbWCrox/iamedHWCc WgSXh3tKkL+gI9c2OwKpEjG67aH53zsWrt32T4RiYnrkRJryBB1UDKRTbAiMyJDfFQXi bOW39J1etdokxAaCJajD0S/pShR9P4Fgq8hHkoIDweTC1SFJjzqE1CYmygwDyUSApdbU Qyw4LeiryGqYpC56/bNvttftLjSFBUvpv9l5EUaX/g4pLiFrXHZ7mPeP4jTx37pmvugG u04w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:from:date:message-id :subject:to:cc; bh=YU/en7owh81aieivR5b29psZ7v0c290n84w9nYunaWs=; b=uR3bIFfXvlRak4zzsGztghtPwxTG7AZlauGYhackGDdsW4UrMjLH1CHyz4jRBjrbmy NcpnHgviRJWxM5q6VNSKW047UYHaKkzGttgS7B4cksGYYZ9Pa14McOcl30DLg4Zs2Y5h a15i9m5gh5y+PtEsKYosPKxyZ3WbcKmj+T8p/zsNiuG3mAkTJxT2xvbm05fqjqjNLyV1 gIVvx3RCdgACOA+6M/hnkWOuBbbFeDR8EtCITqmJQjz00u2U9FD9OXpOm7UQDBDJzePQ dIqQU1ytN7bY1j3cR/Pxr0W53/e8IQF2X37Mhx4zuHC4pZmVfTaHBGXdzvsAtVaFU5fz nD6g== X-Gm-Message-State: AOUpUlFJImasXDFtnpgGUq1X4Fp9TZXhHh7wQjEzZVmpP2ffHAWmZoPR 6M1sYmNJaQzEVgjnM4Qo4Pue24wDLoTfbm+RFvny+aSK X-Google-Smtp-Source: AAOMgpeOLocT8NWXim01gLUSg6OWf4gX0SazEUBYMQCrg2jHcdJff3edpgoYMTfXRyq3wuZKt7QGkURUAHQldsiJTdQ= X-Received: by 2002:a1c:1745:: with SMTP id 66-v6mr5292380wmx.38.1532720730213; Fri, 27 Jul 2018 12:45:30 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:adf:ef8f:0:0:0:0:0 with HTTP; Fri, 27 Jul 2018 12:45:29 -0700 (PDT) Reply-To: sarikaya@ieee.org From: Behcet Sarikaya Date: Fri, 27 Jul 2018 14:45:29 -0500 Message-ID: To: 5GANGIP <5gangip@ietf.org> Cc: "lisp@ietf.org list" , dmm , ila@ietf.org Content-Type: multipart/alternative; boundary="000000000000aa14370572005a65" Archived-At: Subject: [lisp] New Mailing List for draft-nordmark-id-loc-privacy-00.txt X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 27 Jul 2018 19:45:34 -0000 --000000000000aa14370572005a65 Content-Type: text/plain; charset="UTF-8" Hi all, A new mailing list to discuss Privacy and Security issues with Identifier/Locator (Id-Loc) separation protocols in the Internet called PIdLoc has been created. You can subscribe to the list at: https://www.ietf.org/mailman/listinfo/pidloc 5gangip list will continue to host the discussions on 5G issues such as deployment, operations and so on. For all Id-Loc discussions including the discussions on draft-nordmark-id-loc-privacy, the new address is pidloc@ietf.org. Many thanks to Security Area ADs, Eric Rescorla and Ben Kaduk for their help and encouragements. So we are in security area! Regards, Behcet also for Dirk --000000000000aa14370572005a65 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,

A new mailing list to discu= ss Privacy and Security issues with Identifier/Locator (Id-Loc) separation = protocols in the Internet=C2=A0
called=C2=A0
PIdLoc

has bee= n created.

You=C2=A0can subscribe to the list at:

=

5gangip list will continue to host the discussions on 5G issues such= as deployment, operations and so on.
For all Id-Loc discussions including = =C2=A0the discussions on draft-nordmark-id-loc-privacy, the new address is= =C2=A0

Many thanks to Security Area ADs, Eric Rescorla and Ben= Kaduk for their help and encouragements.
So we are in security area!=C2=A0

Regards,
Behcet also for Dirk<= /font>
--000000000000aa14370572005a65-- From nobody Fri Jul 27 13:50:36 2018 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 40001129385; Fri, 27 Jul 2018 13:50:34 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: Luigi Iannone To: X-Test-IDTracker: no X-IETF-IDTracker: 6.83.0 Auto-Submitted: auto-generated Precedence: bulk Cc: Luigi Iannone , lisp-chairs@ietf.org, iesg-secretary@ietf.org, lisp@ietf.org, ggx@gigix.net Message-ID: <153272463425.417.10291688720679777149.idtracker@ietfa.amsl.com> Date: Fri, 27 Jul 2018 13:50:34 -0700 Archived-At: Subject: [lisp] Publication has been requested for draft-ietf-lisp-rfc6833bis-12 X-BeenThere: lisp@ietf.org X-Mailman-Version: 2.1.27 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, 27 Jul 2018 20:50:34 -0000 Luigi Iannone has requested publication of draft-ietf-lisp-rfc6833bis-12 as Proposed Standard on behalf of the LISP working group. Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6833bis/