[6lo] The 6LO WG has placed draft-lijo-6lo-expiration-time in state "Call For Adoption By WG Issued"

IETF Secretariat <ietf-secretariat-reply@ietf.org> Tue, 24 October 2017 00:36 UTC

Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: 6lo@ietf.org
Delivered-To: 6lo@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7870713AF75; Mon, 23 Oct 2017 17:36:51 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
To: 6lo-chairs@ietf.org, draft-lijo-6lo-expiration-time@ietf.org, 6lo@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.63.2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150880541148.25287.9852723437120050510.idtracker@ietfa.amsl.com>
Date: Mon, 23 Oct 2017 17:36:51 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/1V2T2euUGCVlGgmRaz4RlRuOjRw>
Subject: [6lo] The 6LO WG has placed draft-lijo-6lo-expiration-time in state "Call For Adoption By WG Issued"
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.22
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Oct 2017 00:36:51 -0000

The 6LO WG has placed draft-lijo-6lo-expiration-time in state
Call For Adoption By WG Issued (entered by Gabriel Montenegro)

The document is available at
https://datatracker.ietf.org/doc/draft-lijo-6lo-expiration-time/

Comment:
This document has been discussed at face to face meetings as well as on the
list. There is some reasonable interest and an implementation in OpenWSN. Per
the last meeting, after a revision we would issue a call for adoption, and
are pursuing now.