IETF Logo Mail Archive

Re: [lisp] Fwd: Alvaro Retana's No Objection on draft-ietf-lisp-rfc6830bis-16: (with COMMENT)

"Joel M. Halpern" <jmh@joelhalpern.com> Tue, 11 September 2018 13:50 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 7AB8C130DF5 for <lisp@ietfa.amsl.com>; Tue, 11 Sep 2018 06:50:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 uodYZJJ_6Bzk for <lisp@ietfa.amsl.com>; Tue, 11 Sep 2018 06:50:17 -0700 (PDT)
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 C5035130DF2 for <lisp@ietf.org>; Tue, 11 Sep 2018 06:50:15 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id A4BF5660131; Tue, 11 Sep 2018 06:50:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1536673815; bh=obQ0GcKV3oQxt1r+dEHbsmoC0tm8ZjUxnCWQg4GnrUk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=ay1nhZ1FSpmH8lzaw9/ZcnfKb8vuhUaVigr64a4/F9pmoapsJfftoXegB5hnhH1ll /Y5WPcuSTHURlBg1UuS+0FLzklXHCEciAEqmy5UpSuhrrBw9xgE5bgjS8kweS35iS1 zhT8Q62jO84dHcOH33l8okF5kbCsJIoctC1n4vPw=
X-Virus-Scanned: Debian amavisd-new at b2.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 mailb2.tigertech.net (Postfix) with ESMTPSA id E22C46600FA; Tue, 11 Sep 2018 06:50:14 -0700 (PDT)
To: Dino Farinacci <farinacci@gmail.com>, Luigi Iannone <ggx@gigix.net>
Cc: db3546@att.com, "lisp@ietf.org" <lisp@ietf.org>
References: <153661454107.16021.14181238567935017697.idtracker@ietfa.amsl.com> <82C0DF7A-E661-48DF-ABCE-7C830E875E70@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <f51f97af-5b4c-ac7f-b239-bc39088a263a@joelhalpern.com>
Date: Tue, 11 Sep 2018 09:50:13 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <82C0DF7A-E661-48DF-ABCE-7C830E875E70@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/Aa1a0va30Acxdy1fWQmBQL3zHKk>
Subject: Re: [lisp] Fwd: Alvaro Retana's No Objection on draft-ietf-lisp-rfc6830bis-16: (with COMMENT)
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, 11 Sep 2018 13:50:19 -0000

Any change to lisp-intro should be done by discussion with the RFC 
Editor, as it is in the RFC Editor queue (pending reference completion).
If the working group considers it acceptable, we could easily ask them 
to change the references to 6830 and 6833 to the bis documents (after 
all, it is alreay blocked by documents which depend upon those.)

Yours,
Joel

On 9/10/18 11:27 PM, Dino Farinacci wrote:
> If you guys have source for the intro doc, I could point it to bis 
> documents?
> 
> Dino
> 
> 
> Begin forwarded message:
> 
>> *Resent-From:* <alias-bounces@ietf.org <mailto:alias-bounces@ietf.org>>
>> *From:* Alvaro Retana <aretana.ietf@gmail.com 
>> <mailto:aretana.ietf@gmail.com>>
>> *Date:* September 10, 2018 at 2:22:21 PM PDT
>> *Resent-To:* farinacci@gmail.com <mailto:farinacci@gmail.com>, 
>> vince.fuller@gmail.com <mailto:vince.fuller@gmail.com>, dmm@1-4-5.net 
>> <mailto:dmm@1-4-5.net>, darlewis@cisco.com 
>> <mailto:darlewis@cisco.com>, acabello@ac.upc.edu 
>> <mailto:acabello@ac.upc.edu>
>> *To:* "The IESG" <iesg@ietf.org <mailto:iesg@ietf.org>>
>> *Cc:* draft-ietf-lisp-rfc6830bis@ietf.org 
>> <mailto:draft-ietf-lisp-rfc6830bis@ietf.org>, Luigi Iannone 
>> <ggx@gigix.net <mailto:ggx@gigix.net>>, lisp-chairs@ietf.org 
>> <mailto:lisp-chairs@ietf.org>, lisp@ietf.org <mailto:lisp@ietf.org>
>> *Subject:* *Alvaro Retana's No Objection on 
>> draft-ietf-lisp-rfc6830bis-16: (with COMMENT)*
>>
>> Alvaro Retana has entered the following ballot position for
>> draft-ietf-lisp-rfc6830bis-16: No Objection
>>
>> When responding, please keep the subject line intact and reply to all
>> email addresses included in the To and CC lines. (Feel free to cut this
>> introductory paragraph, however.)
>>
>>
>> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>> for more information about IESG DISCUSS and COMMENT positions.
>>
>>
>> The document, along with other ballot positions, can be found here:
>> https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6830bis/
>>
>>
>>
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>>
>> Thanks for the work on this document!
>>
>> I have some relatively minor comments/nits:
>>
>> (1) §18: s/RFC8060/RFC8061
>>
>> (2) §1: "Finally, [I-D.ietf-lisp-introduction] describes the LISP
>> architecture."  First of all, it would seem to me that the 
>> Architecture should
>> be a Normative reference...but I-D.ietf-lisp-introduction says that it 
>> "is used
>> for introductory purposes, more details can be found in RFC6830, the 
>> protocol
>> specification."  This document obsoletes rfc6830...so it seems to me 
>> that there
>> is a failed circular dependency.
>>
>> (3) References to rfc2119/rfc8174 and rfc8126 should be Normative.
>>
>>

v2.23.0 | Report a Bug | By Email