[Roll] WRT adopting draft-rahul-roll-rpl-observations as WG document

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 30 July 2018 19:59 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE7B012F1AB for <roll@ietfa.amsl.com>; Mon, 30 Jul 2018 12:59:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 Eahy2ZV5wk9a for <roll@ietfa.amsl.com>; Mon, 30 Jul 2018 12:59:03 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE10F124D68 for <roll@ietf.org>; Mon, 30 Jul 2018 12:59:03 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 08D492008C for <roll@ietf.org>; Mon, 30 Jul 2018 16:15:33 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id A27F81826; Mon, 30 Jul 2018 15:59:02 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9EE511821 for <roll@ietf.org>; Mon, 30 Jul 2018 15:59:02 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: roll@ietf.org
X-Attribution: mcr
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha1"; protocol="application/pgp-signature"
Date: Mon, 30 Jul 2018 15:59:02 -0400
Message-ID: <30663.1532980742@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/xHZkvK3mEbam4hGdd97jDIlmivM>
Subject: [Roll] WRT adopting draft-rahul-roll-rpl-observations as WG document
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2018 19:59:06 -0000

{been watching the youtube video of the ROLL session}

1) I think that the work in roll-rpl-observations is really important.
   -> that's why we should adopt the document so that it can have priority
      over other non-WG documents in the agenda.
   As our AD pointed out, we don't have to publish it.

2) Starting rfc6550bis or rfc6550updates is very important!!!
   We have some options on how to do this, one of which is to publish a bunch
   of very small updates.  That's probably the lowest latency way, but it
   does cause more IESG and RFC-EDITOR work.
   So I think that we will be forced to publish a ~60-page update document
   that collects all sorts of things.

3) I'd like to move to obsolete (mark as "historical") storing mode in favour
   of dao-projection mode.  I think that this is mostly orthogonal to the updates work, but
   if we agree that we are going in that direction, there might be updates
   that we don't need to do.

4) We need a new node capabilities mechanism.  It could be quite
   controversial as there are a lot of design choices here.  maybe we should 
   probably encourage implementations, and then experimental RFCs.

-- 
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-