Re: [DMM] WG Review: Distributed Mobility Management (dmm)

Alexandru Petrescu <alexandru.petrescu@gmail.com> Wed, 08 October 2014 14:24 UTC

Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC6B61A1B1F; Wed, 8 Oct 2014 07:24:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level:
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] 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 9smYH5Le1elG; Wed, 8 Oct 2014 07:24:06 -0700 (PDT)
Received: from sainfoin-out.extra.cea.fr (sainfoin-out.extra.cea.fr [132.167.192.145]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F88A1A1B2B; Wed, 8 Oct 2014 07:23:59 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by sainfoin.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s98ENvZa002842; Wed, 8 Oct 2014 16:23:57 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 586A9209004; Wed, 8 Oct 2014 16:25:02 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 3FE1D208F71; Wed, 8 Oct 2014 16:25:02 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s98ENq6e009544; Wed, 8 Oct 2014 16:23:57 +0200
Message-ID: <543548F8.7060403@gmail.com>
Date: Wed, 08 Oct 2014 16:23:52 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Jouni <jouni.nospam@gmail.com>
References: <20141003193829.9669.13386.idtracker@ietfa.amsl.com> <54352235.7070304@gmail.com> <5BBFF707-2F25-4D30-9871-B5F17B9AF0B4@gmail.com>
In-Reply-To: <5BBFF707-2F25-4D30-9871-B5F17B9AF0B4@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/rPQos0SpZhJIkOxCBCPQm2vCevw
Cc: "iesg@ietf.org" <iesg@ietf.org>, dmm WG <dmm@ietf.org>
Subject: Re: [DMM] WG Review: Distributed Mobility Management (dmm)
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm/>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Oct 2014 14:24:09 -0000

Jouni,

Thank you for the message.

Here are the modifications:

Where the Charter mentions "Mobile IPv6 protocol family (RFC x, y, z)" 
it should also mention RFC 3963 and RFC 5177.

(these RFCs were mentioned in past versions but disappeared somehow).

Where the Charter says "The working group may decide to extend the 
current milestones based on the new information and knowledge gained 
during working on other documents listed in the initial milestones. 
Possible new documents and milestones must still fit into the overall 
DMM charter scope as outlined above. Milestones:[empty]"

Please clarify that "initial milestones" is "RFC 4888, RFC 4889, 
draft-ietf-dmm-best-practices-gap-analysis-08").

Alex


Le 08/10/2014 15:00, Jouni a écrit :
> Alex,
>
> Do you have a specific change to the text in mind? The charter text
> uses systematically "mobile host/router" to make sure mobile routers
> are not forgotten. However, charter also allows solutions that are
> not specifically tailored to mobile routers.
>
> Jouni
>