Re: [lisp] Fwd: I-D Action: draft-iannone-6834bis-00.txt

"Joel M. Halpern" <jmh@joelhalpern.com> Sun, 20 May 2018 18:23 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4FF8112D7FC for <lisp@ietfa.amsl.com>; Sun, 20 May 2018 11:23:06 -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 ze7e1ZzL2P53 for <lisp@ietfa.amsl.com>; Sun, 20 May 2018 11:23:04 -0700 (PDT)
Received: from maila1.tigertech.net (maila1.tigertech.net [208.80.4.151]) (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 7866412D7F6 for <lisp@ietf.org>; Sun, 20 May 2018 11:23:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila1.tigertech.net (Postfix) with ESMTP id 631CD360C72; Sun, 20 May 2018 11:23:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1526840584; bh=BTC5e5l93RHWDLrc9KdRu8VDxqtwpbYBev1WbH0gGiQ=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=Ev3rNeg96cGefHzioJYAWgevMmuh/qx75dhCb8LS0xaEAy7Wgkx4pmIjoPiVYAjVh NIFti9+/KWkeBoDr8iUqGKBpwgZXhg2tBqmhUGX/qhQbfcke4OhGEzfIcBMamLNxnL p2LKWIQNZtRbAo2MKxi0dxoB5Lka5uVYnY2qj0JU=
X-Virus-Scanned: Debian amavisd-new at maila1.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 maila1.tigertech.net (Postfix) with ESMTPSA id E4BD8360C46; Sun, 20 May 2018 11:23:03 -0700 (PDT)
To: Dino Farinacci <farinacci@gmail.com>
Cc: "lisp@ietf.org" <lisp@ietf.org>
References: <152683978087.2752.5378419126377849283@ietfa.amsl.com> <e59cebd4-df4b-28a0-85ad-13f68f65f013@joelhalpern.com> <C35D210B-E715-4B3C-90D3-753BCE92C4B2@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <b78dc28d-f3c6-16ea-f079-8d91143f1c59@joelhalpern.com>
Date: Sun, 20 May 2018 14:23:03 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <C35D210B-E715-4B3C-90D3-753BCE92C4B2@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/To95HOujK-fguyncQboPnuiu7lA>
Subject: Re: [lisp] Fwd: I-D Action: draft-iannone-6834bis-00.txt
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2018 18:23:06 -0000

Yeah, if we wanted to take longer we could put in a filename change. 
But it doesn't actually matter.  (usually, we need the name right so 
folks can find the document.  I don't think that is a problem in this 
case.)  I will do what is needed to attach it to the LISP WG page.

Yours,
Joel

On 5/20/18 2:21 PM, Dino Farinacci wrote:
> Note the name of the WG document should be draft-ietf-lisp-rfc6834bis-00 (note “rfc” added).
> 
> Cheers,
> Dino
> 
>> On May 20, 2018, at 11:17 AM, Joel Halpern <jmh@joelhalpern.com> wrote:
>>
>> This starts a 4 week implicit adoption call and explicit last call for the LISP Map Versioning draft revision with the purpose of moving this work onto the standards track.
>>
>> Please read the draft.
>> And then speak up as to whether you agree or disagree with us sending this document to our AD for IETF LC and IESG review as a Proposed Standard RFC.
>>
>> We will allow 4 weeks for this call, ending on Sunday, June 17.
>>
>> Thank you,
>> Joel
>>
>> PS: I will try to find a way to mark this suitably in the data tracker, but I suspect it does not have a state to reflect this.
>>
>>
>> -------- Forwarded Message --------
>> Subject: I-D Action: draft-iannone-6834bis-00.txt
>> Date: Sun, 20 May 2018 11:09:40 -0700
>> From: internet-drafts@ietf.org
>> Reply-To: internet-drafts@ietf.org
>> To: i-d-announce@ietf.org
>>
>>
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>
>>
>>         Title           : Locator/ID Separation Protocol (LISP) Map-Versioning
>>         Authors         : Luigi Iannone
>>                           Damien Saucez
>>                           Olivier Bonaventure
>>     Filename        : draft-iannone-6834bis-00.txt
>>     Pages           : 19
>>     Date            : 2018-05-20
>>
>> 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.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-iannone-6834bis/
>>
>> There are also htmlized versions available at:
>> https://tools.ietf.org/html/draft-iannone-6834bis-00
>> https://datatracker.ietf.org/doc/html/draft-iannone-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/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp