Re: [lisp] Call fo adoption of draft-boucadair-lisp-rfc8113bis-01.txt

<mohamed.boucadair@orange.com> Tue, 25 September 2018 09:17 UTC

Return-Path: <mohamed.boucadair@orange.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 2D542130F24; Tue, 25 Sep 2018 02:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 FziAKth8eZd4; Tue, 25 Sep 2018 02:17:02 -0700 (PDT)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7E0AD13114A; Tue, 25 Sep 2018 02:17:01 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 42KFnl1Rvqz5wHB; Tue, 25 Sep 2018 11:16:59 +0200 (CEST)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.18]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 42KFnk6p0ZzDq7d; Tue, 25 Sep 2018 11:16:58 +0200 (CEST)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM34.corporate.adroot.infra.ftgroup ([fe80::cba:56d0:a732:ef5a%19]) with mapi id 14.03.0415.000; Tue, 25 Sep 2018 11:16:58 +0200
From: <mohamed.boucadair@orange.com>
To: Alvaro Retana <aretana.ietf@gmail.com>, Luigi Iannone <ggx@gigix.net>, "lisp@ietf.org list" <lisp@ietf.org>
CC: "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>
Thread-Topic: [lisp] Call fo adoption of draft-boucadair-lisp-rfc8113bis-01.txt
Thread-Index: AQHUVBu1moTCOM5Es0a8FTro+WqDZqUAt5zA
Date: Tue, 25 Sep 2018 09:16:57 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302DFE6578@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <153736857165.21461.18166105234850504507@ietfa.amsl.com> <1B5FAB89-DA76-4F0D-92BA-FD0E6E5A5A77@gigix.net> <CAMMESsz1rmsOXPqKHdRX9RvVXKuAWhwsEWnOpQ5Ec54fv7kyjA@mail.gmail.com>
In-Reply-To: <CAMMESsz1rmsOXPqKHdRX9RvVXKuAWhwsEWnOpQ5Ec54fv7kyjA@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.4]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93302DFE6578OPEXCLILMA3corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/CwEt2UgwCoSRwPVjM6mqZeUonKs>
Subject: Re: [lisp] Call fo adoption of draft-boucadair-lisp-rfc8113bis-01.txt
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 25 Sep 2018 09:17:04 -0000

Hi Alvaro,

The draft says the following:

   IANA is requested to replace the reference to RFC8113<https://tools.ietf.org/html/rfc8113> with the RFC
   number to be assigned to this document.

Which seems reasonable to keep track on the document that created the registry while being aligned with obsoleted RFCs.

Cheers,
Med

De : lisp [mailto:lisp-bounces@ietf.org] De la part de Alvaro Retana
Envoyé : lundi 24 septembre 2018 17:31
À : Luigi Iannone; lisp@ietf.org list
Cc : lisp-chairs@ietf.org
Objet : Re: [lisp] Call fo adoption of draft-boucadair-lisp-rfc8113bis-01.txt

[Speaking as a WG participant.]

Hi!

I don’t object to the adoption.

The main change with respect to rfc8113, that doesn’t seem right to me, is that rfc8113 defined the LISP Packet Types registry, but this document only adds to it.  In the weird world of Updating and Obsoleting RFCs, I think this means that we’re left with no document being the originator of the registry.

Note that rfc6833bis, which requests that the references from the registry point to it *and* to rfc8113, also doesn’t define the registry (which is the correct thing to do)..

My 2c.

Alvaro.


On September 19, 2018 at 11:05:05 AM, Luigi Iannone (ggx@gigix.net<mailto:ggx@gigix.net>) wrote:
Folks,

here is another piece of the work done in our WG that needs to be moved to PS.

It is the updated version of RFC 8113, nothing changed just updated coherently with the current status of the other documents.

Because this documents is really really short we will have just one week adoption call followed be one week WG Last Call.

This email officially starts the one week call for adoption.

Please spend 10 minutes having a look at the document and send an email on whether you agree or not to adopt it.

Thanks

Ciao

Luigi


Begin forwarded message:

From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
Subject: I-D Action: draft-boucadair-lisp-rfc8113bis-01.txt
Date: 19 September 2018 at 16:49:31 CEST
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Reply-To: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>


A New Internet-Draft is available from the on-line Internet-Drafts directories.


       Title           : Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
       Authors         : Mohamed Boucadair
                         Christian Jacquenet
Filename        : draft-boucadair-lisp-rfc8113bis-01.txt
Pages           : 5
Date            : 2018-09-19

Abstract:
  This document specifies a Locator/ID Separation Protocol (LISP)
  shared message type for defining future extensions and conducting
  experiments without consuming a LISP packet type codepoint for each
  extension.

  This document obsoletes RFC 8113.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-boucadair-lisp-rfc8113bis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-boucadair-lisp-rfc8113bis-01
https://datatracker.ietf.org/doc/html/draft-boucadair-lisp-rfc8113bis-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-boucadair-lisp-rfc8113bis-01


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<http://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<mailto: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<mailto:lisp@ietf.org>
https://www.ietf..org/mailman/listinfo/lisp<https://www.ietf.org/mailman/listinfo/lisp>