Re: [multimob] I-D Action:draft-ietf-multimob-pmipv6-base-solution-05.txt
<Dirk.von-Hugo@telekom.de> Mon, 18 October 2010 11:00 UTC
Return-Path: <Dirk.von-Hugo@telekom.de>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D46613A6D97 for <multimob@core3.amsl.com>; Mon, 18 Oct 2010 04:00:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.705
X-Spam-Level:
X-Spam-Status: No, score=-2.705 tagged_above=-999 required=5 tests=[AWL=0.544, 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 rQc5O5AbcSQY for <multimob@core3.amsl.com>; Mon, 18 Oct 2010 04:00:08 -0700 (PDT)
Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by core3.amsl.com (Postfix) with ESMTP id 3C0ED3A6D94 for <multimob@ietf.org>; Mon, 18 Oct 2010 04:00:04 -0700 (PDT)
Received: from s4de8psaans.blf.telekom.de (HELO s4de8psaans.mitte.t-com.de) ([10.151.180.168]) by tcmail71.telekom.de with ESMTP; 18 Oct 2010 13:01:20 +0200
Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675); Mon, 18 Oct 2010 13:01:18 +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: Mon, 18 Oct 2010 13:01:17 +0200
Message-ID: <643B0A1D1A13AB498304E0BBC802784802B3B6FE@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <4CB85BB9.5080500@informatik.haw-hamburg.de>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [multimob]I-D Action:draft-ietf-multimob-pmipv6-base-solution-05.txt
Thread-Index: Actsb8pviNaNbA9BRNCHQsjW7SAk9ACQAW+A
References: <160000.78662.qm@web111409.mail.gq1.yahoo.com> <4CB85BB9.5080500@informatik.haw-hamburg.de>
From: Dirk.von-Hugo@telekom.de
To: schmidt@informatik.haw-hamburg.de, sarikaya@ieee.org
X-OriginalArrivalTime: 18 Oct 2010 11:01:18.0576 (UTC) FILETIME=[CA7FB700:01CB6EB3]
Cc: behcetsarikaya@yahoo.com, multimob@ietf.org
Subject: Re: [multimob] I-D Action:draft-ietf-multimob-pmipv6-base-solution-05.txt
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Oct 2010 11:00:09 -0000
Dear all, Regarding the PMIP WG draft of Multimob 'officially' there are (see http://trac.tools.ietf.org/wg/multimob/trac/report/1) still two 'major' tickets pending on sect 5.1. and 5.2 regarding the addressing. Isn't this now solved with the references to RFC 2710 and 3810 in place? Perhaps one could add an exlanatory sentence in sect. 5 mentioning something like 'Destination addresses for MLD/MGMP messages shall be in accordance with those specified in sect. 8. (Message Destiantions) of RFC 2710 for MLDv1 and sect. 5.1.15. (Destination Addresses for Queries) and sect. 5.2.14. (Destination Addresses for Reports) of RFC 3810 for MLDv2, respectively' Any disagreement? About the other (minor) tickets I am not sure whether the reporter, the owner, the authors or who else can declare them as resolved in order to proceed? >From my point of view the document then should be ready for IESG ... Thanks! Best regards Dirk -----Ursprüngliche Nachricht----- Von: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] Im Auftrag von Thomas C. Schmidt Gesendet: Freitag, 15. Oktober 2010 15:49 An: Behcet Sarikaya Cc: Behcet Sarikaya; multimob@ietf.org Betreff: Re: [multimob]I-D Action:draft-ietf-multimob-pmipv6-base-solution-05.txt Hi Behcet, I'm not sure to understand correctly: If you ask about the 'readiness' of draft-ietf-multimob-pmipv6-base-solution-05.txt, the status is as follows: We have included all feedback from the group & mailing list in the last update and are waiting for the draft to move forward. So the current believe is that the activity token is not at our side. Please let us know if we are wrong / should take any action. Best regards, Thomas On 13.10.2010 23:33, Behcet Sarikaya wrote: > Folks, > We need to make progress on the current charter items so that we can > recharter. > > > It's been long time this revision has been posted. > Considering all the issues raised so far, please state if this draft is ready to > be moved to IESG as soon as possible. > > Also regarding MLD/IGMP tuning charter item, the authors of > draft-asaeda-multimob-igmp-mld-optimization-03 and > draft-wu-multimob-igmp-mld-tuning-02 > > please make sure to submit revisions as soon as possible. > > > > > > ----- Forwarded Message ---- >> From: "Internet-Drafts@ietf.org"<Internet-Drafts@ietf.org> >> To: i-d-announce@ietf.org >> Cc: multimob@ietf.org >> Sent: Thu, July 29, 2010 11:30:07 AM >> Subject: [multimob] I-D Action:draft-ietf-multimob-pmipv6-base-solution-05.txt >> >> A New Internet-Draft is available from the on-line Internet-Drafts >> directories. >> This draft is a work item of the Multicast Mobility Working Group of the > IETF. >> >> >> Title : Base Deployment for Multicast Listener Support in PMIPv6 >> Domains >> Author(s) : T. Schmidt, et al. >> Filename : draft-ietf-multimob-pmipv6-base-solution-05.txt >> Pages : 21 >> Date : 2010-07-29 >> >> This document describes deployment options for activating multicast >> listener functions in Proxy Mobile IPv6 domains without modifying >> mobility and multicast protocol standards. Similar to Home Agents in >> Mobile IPv6, Local Mobility Anchors of Proxy Mobile IPv6 serve as >> multicast subscription anchor points, while Mobile Access Gateways >> provide MLD proxy functions. In this scenario, Mobile Nodes remain >> agnostic of multicast mobility operations. A support for mobile >> multicast senders is outside the scope of this document. >> >> A URL for this Internet-Draft is: >> http://www.ietf.org/internet-drafts/draft-ietf-multimob-pmipv6-base-solution-05.txt >> t >> >> Internet-Drafts are also available by anonymous FTP at: >> ftp://ftp.ietf.org/internet-drafts/ >> >> Below is the data which will enable a MIME compliant mail reader >> implementation to automatically retrieve the ASCII version of the >> Internet-Draft. >> > > > > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob -- Prof. Dr. Thomas C. Schmidt ° Hamburg University of Applied Sciences Berliner Tor 7 ° ° Dept. Informatik, Internet Technologies Group 20099 Hamburg, Germany ° ° http://www.haw-hamburg.de/inet Fon: +49-40-42875-8452 ° ° http://www.informatik.haw-hamburg.de/~schmidt Fax: +49-40-42875-8409 ° _______________________________________________ multimob mailing list multimob@ietf.org https://www.ietf.org/mailman/listinfo/multimob
- [multimob] I-D Action:draft-ietf-multimob-pmipv6-… Internet-Drafts
- [multimob] I-D Action:draft-ietf-multimob-pmipv6-… Behcet Sarikaya
- Re: [multimob] I-D Action:draft-ietf-multimob-pmi… Thomas C. Schmidt
- Re: [multimob] I-D Action:draft-ietf-multimob-pmi… Dirk.von-Hugo
- Re: [multimob] I-D Action:draft-ietf-multimob-pmi… Thomas C. Schmidt