[Lwip] The LWIG WG has placed draft-jadhav-lwig-nbr-mgmt-policy in state "Call For Adoption By WG Issued"

IETF Secretariat <ietf-secretariat-reply@ietf.org> Fri, 11 August 2017 09:49 UTC

Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: lwip@ietf.org
Delivered-To: lwip@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3EAD2132545; Fri, 11 Aug 2017 02:49:47 -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: lwip@ietf.org, draft-jadhav-lwig-nbr-mgmt-policy@ietf.org, lwig-chairs@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150244498721.24449.2354648181399468637.idtracker@ietfa.amsl.com>
Date: Fri, 11 Aug 2017 02:49:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lwip/_qNm1pcnC_QJWiiF1WuImz8Fm_4>
Subject: [Lwip] The LWIG WG has placed draft-jadhav-lwig-nbr-mgmt-policy in state "Call For Adoption By WG Issued"
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Lightweight IP stack <lwip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lwip>, <mailto:lwip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lwip/>
List-Post: <mailto:lwip@ietf.org>
List-Help: <mailto:lwip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lwip>, <mailto:lwip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 Aug 2017 09:49:47 -0000

The LWIG WG has placed draft-jadhav-lwig-nbr-mgmt-policy in state
Call For Adoption By WG Issued (entered by Zhen Cao)

The document is available at
https://datatracker.ietf.org/doc/draft-jadhav-lwig-nbr-mgmt-policy/

Comment:
This document has been presented at IETF98 and IETF99.  The adoption poll was
conducted at IETF99, Prague, where the consensus was quite clear.   This call
would like to confirm the consensus at the meeting.   (Note: minutes of
IETF99 have indicated that the proactive neighbor management which
necessitates protocol changes will be not discussed in this document).