[netext] Conclusion of consensus call to adopt I-D draft-krishnan-netext-update-notifications

Basavaraj Patil <bpatil1@gmail.com> Thu, 29 November 2012 20:58 UTC

Return-Path: <bpatil1@gmail.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id B5E5521F8C38 for <netext@ietfa.amsl.com>; Thu, 29 Nov 2012 12:58:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.598
X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id t7Y97ZmPqtgp for <netext@ietfa.amsl.com>; Thu, 29 Nov 2012 12:58:20 -0800 (PST)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com []) by ietfa.amsl.com (Postfix) with ESMTP id 225EC21F8B9A for <netext@ietf.org>; Thu, 29 Nov 2012 12:58:19 -0800 (PST)
Received: by mail-ie0-f172.google.com with SMTP id c13so16621843ieb.31 for <netext@ietf.org>; Thu, 29 Nov 2012 12:58:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=WtwBObHzYLc4llD1wWmYlFYKdIttMhz7WJ4lalj5SQI=; b=Om9w3Oh4/ZA8ZOYsZSpN4iO/1VV/ylGwkX7+K/UK6fhzX+cGmxfTOJ47dBVSpQdvDF N6FI+QnLsQDbtOFqEQUz7Ty1LQotVY0i5XZOwrwPoU/ammNWSbFe8EBhN/0is8WV/xiw sJVUk9tk9gtQF/xg8hIVY3H9dzQAQI35tIK4TildPKllPej/GKe5qK1tVLAAXbcNsuXs 8v6hX/HcUUbml/bjk+jC/smX95l4l2+UqDfIO87UnZ/RJ7tECOz92bn+xjcKSFARFO/C yP9mj7f4JC6dfhhpWjTr7VkhKIuPodN0vg+SwKPbQO1qj7lyGgCbaQG4MfJa7SD5lhFW 8Emg==
MIME-Version: 1.0
Received: by with SMTP id h10mr26964838igc.55.1354222699590; Thu, 29 Nov 2012 12:58:19 -0800 (PST)
Received: by with HTTP; Thu, 29 Nov 2012 12:58:19 -0800 (PST)
Date: Thu, 29 Nov 2012 14:58:19 -0600
Message-ID: <CAA5F1T2dWR6XSMPY_iKjy7PnFv3ubs7xV6RG3_7ScQwt4vFi=A@mail.gmail.com>
From: Basavaraj Patil <bpatil1@gmail.com>
To: netext@ietf.org
Content-Type: multipart/alternative; boundary="f46d044468e3f4b39004cfa88a7c"
Cc: draft-krishnan-netext-update-notifications@tools.ietf.org
Subject: [netext] Conclusion of consensus call to adopt I-D draft-krishnan-netext-update-notifications
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Nov 2012 20:58:20 -0000

The WG members are supportive of adopting the I-D
draft-krishnan-netext-update-notifiactions as a WG document and progressing
it along the standards track route.

Consensus is strong. I have not seen any dissenting emails for adopting
this I-D.

Authors: Please go ahead and submit the I-D as a Netext WG document.


On Mon, Nov 12, 2012 at 9:11 PM, Basavaraj Patil <bpatil1@gmail.com> wrote:

> The I-D : Update Notifications for Proxy Mobile IPv6
> <draft-krishnan-netext-update-notifications> was presented at the WG
> meeting at IETF85 (Atlanta).
> There was consensus in the room to adopt this I-D as a WG document (11 in
> favor of, None against).
> Please treat this as a consensus call for adopting this I-D as a WG
> document.
> Question: Should the Netext WG adopt I-D:
> draft-krishnan-netext-update-notifications as a working group document?
> Yes:  [  ]
> No :  [  ]
> Some background info: The 3GPP liaison to the IETF has indicated the
> relevance of this I-D to their specifications and is awaiting feedback from
> the AD and the chairs about its status.
> Abstract
>    Proxy Mobile IPv6 (PMIPv6) is a network based mobility management
>    protocol that enables IP mobility for a host without requiring its
>    participation in any mobility-related signaling.  This document
>    proposes a mechanism for the Local Mobility Anchor to asynchronously
>    notify the Mobile Access Gateway about changes related to the
>    mobility session.
> This consensus call will expire on November 26th, 2012.
> -Chairs

Basavaraj Patil