Re: [netlmm] Closing NETLMM WG?

<Dirk.von-Hugo@telekom.de> Tue, 14 September 2010 12:04 UTC

Return-Path: <Dirk.von-Hugo@telekom.de>
X-Original-To: netlmm@core3.amsl.com
Delivered-To: netlmm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5CF6E3A695D for <netlmm@core3.amsl.com>; Tue, 14 Sep 2010 05:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZrQo3UTKQdR for <netlmm@core3.amsl.com>; Tue, 14 Sep 2010 05:04:52 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by core3.amsl.com (Postfix) with ESMTP id E0DA73A6954 for <netlmm@ietf.org>; Tue, 14 Sep 2010 05:04:51 -0700 (PDT)
Received: from s4de8psaanq.blf.telekom.de (HELO S4DE8PSAANQ.mitte.t-com.de) ([10.151.180.166]) by tcmail31.telekom.de with ESMTP; 14 Sep 2010 14:05:06 +0200
Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by S4DE8PSAANQ.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675); Tue, 14 Sep 2010 14:05:06 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 14 Sep 2010 14:05:04 +0200
Message-ID: <643B0A1D1A13AB498304E0BBC8027848028EC4BE@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <4C87492D.60108@piuha.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [netlmm] Closing NETLMM WG?
Thread-Index: ActPMNNp8OaIHzErTDmS3blQK+qI9wEx+R+Q
References: <4C87492D.60108@piuha.net>
From: <Dirk.von-Hugo@telekom.de>
To: <gerardog@qualcomm.com>
X-OriginalArrivalTime: 14 Sep 2010 12:05:06.0455 (UTC) FILETIME=[120C3270:01CB5405]
Cc: netlmm@ietf.org
Subject: Re: [netlmm] Closing NETLMM WG?
X-BeenThere: netlmm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETLMM working group discussion list <netlmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netlmm>
List-Post: <mailto:netlmm@ietf.org>
List-Help: <mailto:netlmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netlmm>, <mailto:netlmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Sep 2010 12:04:53 -0000

Dear Jari, Gerardo,
Once the open IESG discussion issues are clarified for 'mip-interactions' I suggest (in addition to the already proposed changes e.g. w.r.t. security, terminology, and figure references) to consider following nits for draft-ietf-netlmm-mip-interactions-06:

Generally there seems to be no logical or technical difference between LMA/HA and HA/LMA so I would opt for using HA/LMA consistently.

S.1.
s/have implications of how/have implications for how/

S.4.2.
s/the the binding cache entry of the HA/the binding cache entry of the HA/
s/packet are encapsualted/packet is encapsulated/
s/there is valid binding cache for/there is a valid binding cache entry for/

S.9.1.
[boot-integrated]
              Chowdhury, K., Ed., "MIP6-bootstrapping for the Integrated
              Scenario", draft-ietf-mip6-bootstrapping-integrated-06.txt, 2008
(isn't this an informative reference?)

Thanks!
Best regards
Dirk 

BTW, I also agree on "sucessful WG completion" :-)

-----Urspr√ľngliche Nachricht-----
Von: netlmm-bounces@ietf.org [mailto:netlmm-bounces@ietf.org] Im Auftrag von Jari Arkko
Gesendet: Mittwoch, 8. September 2010 10:28
An: netlmm@ietf.org
Betreff: [netlmm] Closing NETLMM WG?

All,

I am looking at the work that the group is doing, and two of its 
documents are hopefully soon approved as RFCs:

- mip-interactions (waiting on 2 ADs to clear their discusses)
- pmipv6-mib (going to MIB doctor review)

Seven other documents have already been published as RFCs, including the 
key base specifications. There is one more document that the group is 
working on, lma-discovery, but progress on that seems slow. I was 
wondering if it would be time to declare success and close the working 
group. The remaining document could either die if there's no interest, 
be AD sponsored to an RFC, or moved to NETEXT WG which is already 
working on similar topics.

Thoughts? Comments?

Jari (who is having a WG cleanup day)

_______________________________________________
netlmm mailing list
netlmm@ietf.org
https://www.ietf.org/mailman/listinfo/netlmm