IETF Logo Mail Archive

Re: [lisp] RFC 8112

Joel Halpern Direct <jmh.direct@joelhalpern.com> Fri, 23 February 2018 18:28 UTC

Return-Path: <jmh.direct@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 1CF6112D7E5 for <lisp@ietfa.amsl.com>; Fri, 23 Feb 2018 10:28:55 -0800 (PST)
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 AKOjzgwuhDE5 for <lisp@ietfa.amsl.com>; Fri, 23 Feb 2018 10:28:53 -0800 (PST)
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 A86DC126C2F for <lisp@ietf.org>; Fri, 23 Feb 2018 10:28:53 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 946AD5E4309; Fri, 23 Feb 2018 10:28:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1519410533; bh=aixPcYGU15gDB2P3ylNien3Zie0KIRX1lnzsrhqRWog=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=YzyBN+xiP6D5y+hRyfPR3DDk+0dsPPhajQgpyRte1ObtTcHwB5G3e4iytFogRlIhY rbFKHaikWnbXkYihE+hG8oBtAFWl3OBeGUeZBcsK8vqB89vTcorRbJIMnKSZX5FmMU oxEU3pl0U2keqb8Q+ZMC+37p9V1iXl3k+nBFMsC8=
X-Virus-Scanned: Debian amavisd-new at b2.tigertech.net
Received: from Joels-MacBook-Pro.local (unknown [50.225.209.67]) (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 046B91C0691; Fri, 23 Feb 2018 10:28:52 -0800 (PST)
To: Dino Farinacci <farinacci@gmail.com>
Cc: Luigi Iannone <ggx@gigix.net>, "lisp@ietf.org list" <lisp@ietf.org>
References: <B249D16F-6B18-4311-BCF8-A0C270D462D1@gmail.com> <2a1f8a88-eed5-a433-9d53-ae9c8483bf6c@joelhalpern.com> <9FA74C96-C079-42A5-B56C-B7718647CF5C@gmail.com>
From: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Message-ID: <8f186ad4-3804-036a-6ff2-8bfd1fd86809@joelhalpern.com>
Date: Fri, 23 Feb 2018 13:28:52 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <9FA74C96-C079-42A5-B56C-B7718647CF5C@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/iEZMIR5AQlxb0dgtT9tk3lhc3z0>
Subject: Re: [lisp] RFC 8112
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: Fri, 23 Feb 2018 18:28:55 -0000

No, I do not think it is appropriate to put it in the list (not sure if 
I can).

LIG was produced as an Informational RFC by the LISP working group.  it 
is a WG product.

RFC 8112 was NOT produced by the LISP working group.  It had been on our 
plate, and then was taken for publication to the Independent Stream. 
Which is fine.  (Luigi and I were asked if this was a problem.)  But 
that means it was not a working group product, did not go through IETF 
last call, and was not approved by the IESG.  Formally, it is a product 
of the listed authors.

Yours,
Joel

On 2/23/18 1:11 PM, Dino Farinacci wrote:
> I don’t understand why its different than lig. Can you put it in the list?
> 
> Dino
> 
>> On Feb 23, 2018, at 9:55 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>>
>> It is not listed because it is not a working group product.  It is an Independent Stream document from the authors.  (I agree it is a useful document, but that is not whta that list is about.)
>>
>> Yours,
>> Joel
>>
>> On 2/23/18 12:34 PM, Dino Farinacci wrote:
>>> Chairs, can you check why RFC 8112 is not listed in the RFC list in https://datatracker.ietf.org/wg/lisp/documents/?
>>> Thanks,
>>> Dino
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lisp
>

v2.23.0 | Report a Bug | By Email