IETF Logo Mail Archive

Re: [lisp] One comment to draft-ietf-lisp-type-iana-05.txt

Dino Farinacci <farinacci@gmail.com> Thu, 02 February 2017 18:58 UTC

Return-Path: <farinacci@gmail.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 4FCFD12952E for <lisp@ietfa.amsl.com>; Thu, 2 Feb 2017 10:58:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZZVcH_domxvy for <lisp@ietfa.amsl.com>; Thu, 2 Feb 2017 10:58:29 -0800 (PST)
Received: from mail-pf0-x231.google.com (mail-pf0-x231.google.com [IPv6:2607:f8b0:400e:c00::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 D6580129511 for <lisp@ietf.org>; Thu, 2 Feb 2017 10:58:29 -0800 (PST)
Received: by mail-pf0-x231.google.com with SMTP id y143so7188549pfb.0 for <lisp@ietf.org>; Thu, 02 Feb 2017 10:58:29 -0800 (PST)
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=EmA4tzU75pS6rsIwAPuvmPh5Z73DwvZLhGA/9idQ1HU=; b=nJar3iZWq/zAeZHJgwYnvAbGzco6TP5x3dbNJXDA8Q3w6x8culYKc7Dp/N4vZtzjT2 1jfKrXC4N/2xnQnKPbmfJYoI5SGkklvVy/KcHKGQ7oT0VG+0P4XVMxBxXNTGgCA82Ouy 0f6MkcFgD+Tbp3ascH/qTEvYSZoO8UzPuipnEEr6UMoG4ISyLZu/j4hwKxzdez5lK4P8 4JrR42A4vAVJTRxH426jL4U2Qd3s9Rza5WyGPUBSIyNhg+SJACi4e39f/LAT8/4bmznE M8VsqT2M97Ok0crBu3CPrHiClcEs52U6bQwsRrckc3OPAD0qkj0ISJoguZgAMJBetwlC byoQ==
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=EmA4tzU75pS6rsIwAPuvmPh5Z73DwvZLhGA/9idQ1HU=; b=RQTuOrpmyI7NnvJlmryOcmXN0bNw67yentsE/GqFBuTED+EQzpJh5HS0EA2ep0sT0b k3XMKPYgax0KsKIVv2OD1f9cCI24aost/6BxXud9Pwamjsh5jWBKAME8pSBVdDAXzb9+ bD+pZtQXuhOHM6VPKtuX1M7wUyg/44pM2UKyUUhJdgCqK9RHdwbx6wC14UAsWDbNY1Iv tvy6rSq+8fUnSM31npAcW6a9V3hub0rXHgsdhsNXo0haxcPSY/hw3pANsJzEiyH4/uY9 Kc71OhA6wuygHxQGtHwEHhmYHfibJK7DkvxYFD1/F/03HJKK0E9lwu/69Ub1Z0WducnJ PzPA==
X-Gm-Message-State: AIkVDXKWVu3rZLoSGMmKcaBUaxHvSODnhzHs4vMxp9EMoiCY2rkqAWT5U8aPKzn5Fii/Yg==
X-Received: by 10.99.140.77 with SMTP id q13mr12292467pgn.179.1486061909480; Thu, 02 Feb 2017 10:58:29 -0800 (PST)
Received: from [10.197.31.157] (173-11-119-245-SFBA.hfc.comcastbusiness.net. [173.11.119.245]) by smtp.gmail.com with ESMTPSA id r74sm60399399pfb.67.2017.02.02.10.58.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Feb 2017 10:58:28 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <8a09a5a2-b252-1d25-cb26-a04be2b9b824@joelhalpern.com>
Date: Thu, 02 Feb 2017 10:58:27 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <6C4A0552-F74C-4BE7-886D-F8C09B3A098E@gmail.com>
References: <mailman.3778.1486059811.4842.i-d-announce@ietf.org> <E29F9348-438C-4551-B383-ECE62118C585@gmail.com> <8a09a5a2-b252-1d25-cb26-a04be2b9b824@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/cr3A2MgA04F7-jqsdZpWxJ72hn0>
Cc: LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] One comment to 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: Thu, 02 Feb 2017 18:58:31 -0000

Did we? Why can’t it all be independent? 

Dino

> On Feb 2, 2017, at 10:44 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
> 
> I had not realized we intended to defer creation of the registry until we publish 6833bis.
> 
> Yours,
> Joel
> 
> On 2/2/17 1:26 PM, Dino Farinacci wrote:
>> Mohamed, the statement “This document updates RFC6830.” is too broad and
>> easily open to misinterpretation. See my suggestion below.
>> 
>> 
>> 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
>> 
>> 
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
>>

v2.23.0 | Report a Bug | By Email