IETF Logo Mail Archive

Re: [lisp] I-D Action: draft-ietf-lisp-type-iana-05.txt

<mohamed.boucadair@orange.com> Fri, 03 February 2017 06:25 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 ECE351293EE for <lisp@ietfa.amsl.com>; Thu, 2 Feb 2017 22:25:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.816
X-Spam-Level:
X-Spam-Status: No, score=-5.816 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-3.199, 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 9UZ1285jnQMk for <lisp@ietfa.amsl.com>; Thu, 2 Feb 2017 22:25:08 -0800 (PST)
Received: from relais-inet.orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B019B1293DC for <lisp@ietf.org>; Thu, 2 Feb 2017 22:25:07 -0800 (PST)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id F1633120CD2; Fri, 3 Feb 2017 07:25:05 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.34]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id C840380062; Fri, 3 Feb 2017 07:25:05 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM6F.corporate.adroot.infra.ftgroup ([fe80::bd00:88f8:8552:3349%17]) with mapi id 14.03.0319.002; Fri, 3 Feb 2017 07:25:05 +0100
From: mohamed.boucadair@orange.com
To: Dino Farinacci <farinacci@gmail.com>
Thread-Topic: [lisp] I-D Action: draft-ietf-lisp-type-iana-05.txt
Thread-Index: AQHSfYF5WZ3SGGGkXU6GRFUGycUmlaFW0C7w
Date: Fri, 03 Feb 2017 06:25:04 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B933009DF8EBE@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <148602047542.18619.11155947305350239971.idtracker@ietfa.amsl.com> <92251959-8AE6-4629-827D-CFDD7761C06B@gmail.com>
In-Reply-To: <92251959-8AE6-4629-827D-CFDD7761C06B@gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.3]
Content-Type: multipart/related; boundary="_004_787AE7BB302AE849A7480A190F8B933009DF8EBEOPEXCLILMA3corp_"; type="multipart/alternative"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/GmOXwbJeKmeXHiwKZ_pdWq_jKUA>
Cc: "lisp@ietf.org" <lisp@ietf.org>
Subject: Re: [lisp] I-D Action: draft-ietf-lisp-type-iana-05.txt
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <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: Fri, 03 Feb 2017 06:25:10 -0000

Hi Dino, all,

I do think the NEW text in -06 is clear about the update:


   This document updates RFC6830 by defining a registry for LISP Packet

   Types assignments.

RFC6833bis will need to point to the registry to define new control messages. No need to add a reference to RFC6833bis, IMHO.

Cheers,
Med

De : lisp [mailto:lisp-bounces@ietf.org] De la part de Dino Farinacci
Envoyé : jeudi 2 février 2017 19:23
À : internet-drafts@ietf.org
Cc : lisp@ietf.org; i-d-announce@ietf.org
Objet : Re: [lisp] I-D Action: draft-ietf-lisp-type-iana-05.txt

Mohamed, the statement “This document updates RFC6830.” is too broad and easily open to misinterpretation. See my suggestion below.

[cid:image002.png@01D27DEE.A3131170]
I suggest this wording (and possibly not in the abstract):

This document introduces a new LISP message type so extenstions to the protocol may be experimented with. The code point is defined in RFC6833bis in which this document references as well as describes how the sub-types for the code point are used.

Dino


On Feb 1, 2017, at 11:27 PM, internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> wrote:


A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Locator/ID Separation Protocol of the IETF.

       Title           : LISP Shared Extension Message & IANA Registry for LISP Packet Type Allocations
       Authors         : Mohamed Boucadair
                         Christian Jacquenet
          Filename        : draft-ietf-lisp-type-iana-05.txt
          Pages           : 6
          Date            : 2017-02-01

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

  This document updates RFC6830.



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

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-lisp-type-iana-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-lisp-type-iana-05


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/

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

v2.23.0 | Report a Bug | By Email