Re: [lisp] Jari Arkko's No Objection on charter-ietf-lisp-03-01: (with COMMENT)

Dino Farinacci <farinacci@gmail.com> Wed, 06 April 2016 16:57 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 379A912D64D; Wed, 6 Apr 2016 09:57:11 -0700 (PDT)
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 7SBAsuFHP5uQ; Wed, 6 Apr 2016 09:57:09 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (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 3506012D66E; Wed, 6 Apr 2016 09:57:09 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id r184so20056634qkc.1; Wed, 06 Apr 2016 09:57:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gJfZ5zuJSPAHpBFO2a77rLomhsZ3wa3uTOnnBq8oq9Y=; b=FnuXL4ykqKmtMQ5EzvSREKrah6LyHHlaZluZXKIYeWLj0aVuW1aRWm0EVSo8vHjMej vvuroonWm4NZSqDYMRzLqaYxaXu0ADp9ezXSt1YGoRjufwKV6MdLMynIxXn6+IL1nxEM wQ0T/fBsCZEaMZm8naYIXGugWrRVKynoJpuZ1AncOmyHLSQdSDQ4WkCXdyAg4Vgf4Ute V46ZUSBA+GyHpb0A1trQfEpnduV//HwoM7qse+9/dQYwvuIOUMu64Dt5XBQU3wn68EK/ 1F8o5Di23IANKAPFhFxuYwDPCpT9oWPo5b4Yc9VGtTawPjxTgYbS/4ThFn7yli5SzyVr xBrQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gJfZ5zuJSPAHpBFO2a77rLomhsZ3wa3uTOnnBq8oq9Y=; b=AaHlqRYlsZ00U57cUPrloRyxZScn9o8BQKbS/w8+RcpRB/i48lQl4JRQiw6aTIDX0Z UQJRP2SSefnClmw78lYhiH6kJGG4jSnlb/zKRZXXc23XPTsYJnrtgm9JF0b56OmteUlK fq9XrLNVm/RuvXVAU0ay1T9AiH1P737WYPVi1HrXkXgQHVOVEucRBu9Rc8B1nhhu/5dU GeajuDYAv/XuEqTk0P2R8eiDu06O8f07hS+jMez1ia8RuUcjm8dXLvPk0sMmLtv17nZG qBedqUmagnFWhNR0cv/v6AP+vTU/j3jfEoCjhjO0uiaGAZoQyulWeiIr8pqgotmKS273 6QBQ==
X-Gm-Message-State: AD7BkJJ2r7JW0lb4iVLO/LNQ1Y5lMbjWhuUnVgFmAKfWAl5D7/JY2RMWJi+UzMdFfmrkpA==
X-Received: by 10.55.74.140 with SMTP id x134mr3678833qka.19.1459961826786; Wed, 06 Apr 2016 09:57:06 -0700 (PDT)
Received: from ?IPv6:2001:67c:370:136:ccda:8dd3:dfa2:b5d0? ([2001:67c:370:136:ccda:8dd3:dfa2:b5d0]) by smtp.gmail.com with ESMTPSA id x189sm1609177qhb.43.2016.04.06.09.57.03 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 06 Apr 2016 09:57:05 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <20160406161552.25042.2486.idtracker@ietfa.amsl.com>
Date: Wed, 06 Apr 2016 09:57:02 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <69307B00-99CA-46BC-82DE-B5D4D20745BD@gmail.com>
References: <20160406161552.25042.2486.idtracker@ietfa.amsl.com>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.3112)
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/sscwbpgnSgfJ4980oYomwGB5_T4>
Cc: lisp-chairs@ietf.org, The IESG <iesg@ietf.org>, lisp@ietf.org
Subject: Re: [lisp] Jari Arkko's No Objection on charter-ietf-lisp-03-01: (with COMMENT)
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: Wed, 06 Apr 2016 16:57:11 -0000

If we should start a list of what items should be standards track, I think this is a decent start and is a practical base:

RFC 6830 (main spec)
RFC 6831 (multicast spec) but decide if draft-ietf-lisp-signal-free should go instead or in addition
RFC 6832 (Interworking)
RFC 6833 (Map-Server (aka the mapping system control-plane))
draft-ietf-lisp-ddt

And note these specs have been in use for at least 5 years.

Dino

On Apr 6, 2016, at 9:15 AM, Jari Arkko <jari.arkko@piuha.net> wrote:
> 
> Jari Arkko has entered the following ballot position for
> charter-ietf-lisp-03-01: 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.)
> 
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-lisp/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> I had asked a clarification on which parts of the work of the WG will be
> going standards track and which parts experimental. The answer and
> suggested edits to the charter have made it clearer. Thank you.
> 
> For what it is worth, I believe the working group should not put the
> entire list of work items (9 previous RFCs to be re-worked plus 7 new
> ones) targeting standards track. The new charter text has language that
> the situation will be evaluated for the new charter items, but at least
> my read of it gives a default answer of "standards track".  In my view
> there are work items that would benefit from being targeted for an
> experimental round before made standards, and I thought the charter
> should have said that. 
> 
> There was pushback for my suggestion to do that, however. I do not plan
> to stand in the way of the working group making this charter update, but
> I wanted to be on record that the I didn't think this was a good idea.
> 
> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp