[lisp] Way forward on 6830bis

"Joel M. Halpern" <jmh@joelhalpern.com> Mon, 26 October 2015 16:25 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E68531B4CF3 for <lisp@ietfa.amsl.com>; Mon, 26 Oct 2015 09:25:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.703
X-Spam-Level:
X-Spam-Status: No, score=-0.703 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 STtz8eW6lyxX for <lisp@ietfa.amsl.com>; Mon, 26 Oct 2015 09:25:20 -0700 (PDT)
Received: from mailb2.tigertech.net (mailb2.tigertech.net [208.80.4.154]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F7AC1B4BAB for <lisp@ietf.org>; Mon, 26 Oct 2015 09:25:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailb2.tigertech.net (Postfix) with ESMTP id 8947B288CA3 for <lisp@ietf.org>; Mon, 26 Oct 2015 09:25:20 -0700 (PDT)
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 44BE0288C8A for <lisp@ietf.org>; Mon, 26 Oct 2015 09:25:20 -0700 (PDT)
To: "lisp@ietf.org" <lisp@ietf.org>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <562E53EF.9070707@joelhalpern.com>
Date: Mon, 26 Oct 2015 12:25:19 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/p2OX9a-MtLgQKDr32B-kIM11wAU>
Subject: [lisp] Way forward on 6830bis
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 26 Oct 2015 16:25:22 -0000

It seemed to us that there was likely some confusiona bout how we expect 
to handle the revision of RCC 6830.  The following is what we currently 
expect.

Once we have a new charter approved, the chairs will appoint an editor 
for the revision of rfc6830.  That may be one of the existing authors, 
or a new person.  We will ask for volunteers.

Once we have an author, they will submit a starting ID called 
draft-ietf-lisp-rfc6830bis-00 which will be identical in content to the 
existing RFC.  That may require assistance from the RFC Editor to ensure 
that we get all the changes they made during final edit.

At that point, we will use the trouble ticket system to record issues 
that people bring up.  We will also discuss on the list what changes we 
wish to make according to the charter.  Things will tehn proceed in the 
usual fashion, using the trouble ticket system to help make sure we do 
not drop any of the issues.

Yours,
Joel & Luigi