From jari.arkko@piuha.net Thu Dec 5 05:51:07 2013 Return-Path: X-Original-To: multimob@ietfa.amsl.com Delivered-To: multimob@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 905261ADEB7; Thu, 5 Dec 2013 05:51:07 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 nTlTnxdZyMxK; Thu, 5 Dec 2013 05:51:05 -0800 (PST) Received: from p130.piuha.net (p130.piuha.net [193.234.218.130]) by ietfa.amsl.com (Postfix) with ESMTP id 7C51D1ADF10; Thu, 5 Dec 2013 05:51:05 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id D05C22CCBF; Thu, 5 Dec 2013 15:51:01 +0200 (EET) X-Virus-Scanned: amavisd-new at piuha.net Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kmw_jxiAaVMp; Thu, 5 Dec 2013 15:51:01 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id E22CC2CC6B; Thu, 5 Dec 2013 15:51:00 +0200 (EET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Jari Arkko In-Reply-To: Date: Thu, 5 Dec 2013 14:51:01 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <10F40DA1-121D-4D4A-A79D-20AEB820B1A9@piuha.net> References: To: Scott Brim X-Mailer: Apple Mail (2.1510) Cc: gen-art , multimob@ietf.org, draft-ietf-multimob-handover-optimization.all@tools.ietf.org Subject: Re: [multimob] [Gen-art] GEN-ART telechat review of draft-ietf-multimob-handover-optimization X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 13:51:07 -0000 Thank you for your review, Scott! I have placed a no-obj position for = this document in today's IESG telechat. Jari From internet-drafts@ietf.org Fri Dec 13 15:37:00 2013 Return-Path: X-Original-To: multimob@ietfa.amsl.com Delivered-To: multimob@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6EE81AE209; Fri, 13 Dec 2013 15:37:00 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 JqhXXMkgkgjW; Fri, 13 Dec 2013 15:36:58 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 32CC71AE179; Fri, 13 Dec 2013 15:36:58 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.83.p1 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131213233657.26822.89739.idtracker@ietfa.amsl.com> Date: Fri, 13 Dec 2013 15:36:57 -0800 Cc: multimob@ietf.org Subject: [multimob] I-D Action: draft-ietf-multimob-fmipv6-pfmipv6-multicast-02.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.15 List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Dec 2013 23:37:01 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Multicast Mobility Working Group of the I= ETF. Title : Multicast Listener Extensions for MIPv6 and PMIPv6 Fast = Handovers Author(s) : Thomas C. Schmidt Matthias Waehlisch Rajeev Koodli Godred Fairhurst Dapeng Liu Filename : draft-ietf-multimob-fmipv6-pfmipv6-multicast-02.txt Pages : 27 Date : 2013-12-13 Abstract: Fast handover protocols for MIPv6 and PMIPv6 define mobility management procedures that support unicast communication at reduced handover latency. Fast handover base operations do not affect multicast communication, and hence do not accelerate handover management for native multicast listeners. Many multicast applications like IPTV or conferencing, though, are comprised of delay-sensitive real-time traffic and will benefit from fast handover execution. This document specifies extension of the Mobile IPv6 Fast Handovers (FMIPv6) and the Fast Handovers for Proxy Mobile IPv6 (PFMIPv6) protocols to include multicast traffic management in fast handover operations. This multicast support is provided first at the control plane by a management of rapid context transfer between access routers, second at the data plane by an optional fast traffic forwarding that may include buffering. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-multimob-fmipv6-pfmipv6-multica= st There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-multimob-fmipv6-pfmipv6-multicast-02 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-multimob-fmipv6-pfmipv6-multi= cast-02 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From sarikaya2012@gmail.com Mon Dec 16 09:56:47 2013 Return-Path: X-Original-To: multimob@ietfa.amsl.com Delivered-To: multimob@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF38D1ADFD8 for ; Mon, 16 Dec 2013 09:56:47 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.749 X-Spam-Level: X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 asmpUgAVG4yM for ; Mon, 16 Dec 2013 09:56:46 -0800 (PST) Received: from mail-la0-x232.google.com (mail-la0-x232.google.com [IPv6:2a00:1450:4010:c03::232]) by ietfa.amsl.com (Postfix) with ESMTP id 8381C1ADF9B for ; Mon, 16 Dec 2013 09:56:45 -0800 (PST) Received: by mail-la0-f50.google.com with SMTP id el20so2789348lab.37 for ; Mon, 16 Dec 2013 09:56:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=XOGQelFeoNTvjruO+AduWOrc/gQisQanWSGSjqOnI7Y=; b=qiweSRHEQzMoOzSiNswqc7kbHXcNKb9+nWMKVVzM6PxEL85AbEXquEf/cKG7PMFpNK RNYl2fR0ZijKps0tkVyMn9BNd4ATJDUMyN8Ia53AzMgAtrFrxrSXOzBoKyw7FxQM1JvO NtDy6udP5Cj3V2wjZ8aCaG2ZN1f2eTGaa+sAX9CsRMYxeIskOegGh7avelMsO7mfzeuj xWw5o5cSZ9VcQtYgCju0YafaJbVWcD70RwGAF5x5BTyA+O4kYWIDXOkoCAOisAPG971v BaEEdJ3zrI/1xVtsVBr8lp/WpX3kzLWLJW7pAk8lsYybNWun6NlmsKxBUPMGJgOE51U8 VD4Q== MIME-Version: 1.0 X-Received: by 10.152.120.231 with SMTP id lf7mr7322454lab.36.1387216603756; Mon, 16 Dec 2013 09:56:43 -0800 (PST) Received: by 10.115.4.165 with HTTP; Mon, 16 Dec 2013 09:56:43 -0800 (PST) In-Reply-To: <20131213233657.26822.89739.idtracker@ietfa.amsl.com> References: <20131213233657.26822.89739.idtracker@ietfa.amsl.com> Date: Mon, 16 Dec 2013 11:56:43 -0600 Message-ID: From: Behcet Sarikaya To: "multimob@ietf.org" Content-Type: multipart/alternative; boundary=089e0122aefee4bb7404edaa8884 Subject: Re: [multimob] I-D Action: draft-ietf-multimob-fmipv6-pfmipv6-multicast-02.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 17:56:47 -0000 --089e0122aefee4bb7404edaa8884 Content-Type: text/plain; charset=ISO-8859-1 Folks, The authors have finally submitted the revision of PFMIPv6 handover draft. Please read it and comment. On Fri, Dec 13, 2013 at 5:36 PM, wrote: > > 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 : Multicast Listener Extensions for MIPv6 and > PMIPv6 Fast Handovers > Author(s) : Thomas C. Schmidt > Matthias Waehlisch > Rajeev Koodli > Godred Fairhurst > Dapeng Liu > Filename : > draft-ietf-multimob-fmipv6-pfmipv6-multicast-02.txt > Pages : 27 > Date : 2013-12-13 > > Abstract: > Fast handover protocols for MIPv6 and PMIPv6 define mobility > management procedures that support unicast communication at reduced > handover latency. Fast handover base operations do not affect > multicast communication, and hence do not accelerate handover > management for native multicast listeners. Many multicast > applications like IPTV or conferencing, though, are comprised of > delay-sensitive real-time traffic and will benefit from fast handover > execution. This document specifies extension of the Mobile IPv6 Fast > Handovers (FMIPv6) and the Fast Handovers for Proxy Mobile IPv6 > (PFMIPv6) protocols to include multicast traffic management in fast > handover operations. This multicast support is provided first at the > control plane by a management of rapid context transfer between > access routers, second at the data plane by an optional fast traffic > forwarding that may include buffering. > > > The IETF datatracker status page for this draft is: > > https://datatracker.ietf.org/doc/draft-ietf-multimob-fmipv6-pfmipv6-multicast > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-multimob-fmipv6-pfmipv6-multicast-02 > > A diff from the previous version is available at: > > http://www.ietf.org/rfcdiff?url2=draft-ietf-multimob-fmipv6-pfmipv6-multicast-02 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org. > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob > --089e0122aefee4bb7404edaa8884 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Folks,

The authors have = finally submitted the revision of PFMIPv6 handover draft.

Please read it and comment.

On Fri, Dec 13, 2013 at 5:36 PM, <= internet-drafts@ietf.org> wrote:

A New Internet-Draft is available from the on-line Internet-Drafts director= ies.
=A0This draft is a work item of the Multicast Mobility Working Group of the= IETF.

=A0 =A0 =A0 =A0 Title =A0 =A0 =A0 =A0 =A0 : Multicast Listener Extensions f= or MIPv6 and PMIPv6 Fast Handovers
=A0 =A0 =A0 =A0 Author(s) =A0 =A0 =A0 : Thomas C. Schmidt
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Matthias Waehlisch
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Rajeev Koodli
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Godred Fairhurst
=A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Dapeng Liu
=A0 =A0 =A0 =A0 Filename =A0 =A0 =A0 =A0: draft-ietf-multimob-fmipv6-pfmipv= 6-multicast-02.txt
=A0 =A0 =A0 =A0 Pages =A0 =A0 =A0 =A0 =A0 : 27
=A0 =A0 =A0 =A0 Date =A0 =A0 =A0 =A0 =A0 =A0: 2013-12-13

Abstract:
=A0 =A0Fast handover protocols for MIPv6 and PMIPv6 define mobility
=A0 =A0management procedures that support unicast communication at reduced<= br> =A0 =A0handover latency. =A0Fast handover base operations do not affect
=A0 =A0multicast communication, and hence do not accelerate handover
=A0 =A0management for native multicast listeners. =A0Many multicast
=A0 =A0applications like IPTV or conferencing, though, are comprised of
=A0 =A0delay-sensitive real-time traffic and will benefit from fast handove= r
=A0 =A0execution. =A0This document specifies extension of the Mobile IPv6 F= ast
=A0 =A0Handovers (FMIPv6) and the Fast Handovers for Proxy Mobile IPv6
=A0 =A0(PFMIPv6) protocols to include multicast traffic management in fast<= br> =A0 =A0handover operations. =A0This multicast support is provided first at = the
=A0 =A0control plane by a management of rapid context transfer between
=A0 =A0access routers, second at the data plane by an optional fast traffic=
=A0 =A0forwarding that may include buffering.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-iet= f-multimob-fmipv6-pfmipv6-multicast

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-multimo= b-fmipv6-pfmipv6-multicast-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddr= aft-ietf-multimob-fmipv6-pfmipv6-multicast-02


Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp= .ietf.org/internet-drafts/

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

--089e0122aefee4bb7404edaa8884-- From schmidt@fhtw-berlin.de Mon Dec 16 10:18:09 2013 Return-Path: X-Original-To: multimob@ietfa.amsl.com Delivered-To: multimob@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA0F91A9313 for ; Mon, 16 Dec 2013 10:18:09 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.85 X-Spam-Level: X-Spam-Status: No, score=-3.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-2.3] 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 iQw1FJpiMdCJ for ; Mon, 16 Dec 2013 10:18:07 -0800 (PST) Received: from mail2.rz.htw-berlin.de (mail2.rz.htw-berlin.de [141.45.10.102]) by ietfa.amsl.com (Postfix) with ESMTP id 1A1E81AE0C3 for ; Mon, 16 Dec 2013 10:18:06 -0800 (PST) Envelope-to: multimob@ietf.org Received: from e178063238.adsl.alicedsl.de ([85.178.63.238] helo=[192.168.178.33]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from ) id 1Vsck1-000PTx-BN; Mon, 16 Dec 2013 19:18:05 +0100 Message-ID: <52AF43DB.7090800@fhtw-berlin.de> Date: Mon, 16 Dec 2013 19:18:03 +0100 From: "Thomas C. Schmidt" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: sarikaya@ieee.org, "multimob@ietf.org" References: <20131213233657.26822.89739.idtracker@ietfa.amsl.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de) X-HTW-DELIVERED-TO: multimob@ietf.org Subject: Re: [multimob] I-D Action: draft-ietf-multimob-fmipv6-pfmipv6-multicast-02.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 18:18:10 -0000 Hi Behcet, all, sorry, this is still work in progress and does not address all comments received so far. Due to strong overload, we must delay a complete update to the Christmas period ... So please wait a few days before you complain that your comment was not addressed satisfactory ;) Best regards, Thomas On 16.12.2013 18:56, Behcet Sarikaya wrote: > Folks, > > The authors have finally submitted the revision of PFMIPv6 handover draft. > > Please read it and comment. > > On Fri, Dec 13, 2013 at 5:36 PM, > wrote: > > > 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 : Multicast Listener Extensions for MIPv6 > and PMIPv6 Fast Handovers > Author(s) : Thomas C. Schmidt > Matthias Waehlisch > Rajeev Koodli > Godred Fairhurst > Dapeng Liu > Filename : > draft-ietf-multimob-fmipv6-pfmipv6-multicast-02.txt > Pages : 27 > Date : 2013-12-13 > > Abstract: > Fast handover protocols for MIPv6 and PMIPv6 define mobility > management procedures that support unicast communication at reduced > handover latency. Fast handover base operations do not affect > multicast communication, and hence do not accelerate handover > management for native multicast listeners. Many multicast > applications like IPTV or conferencing, though, are comprised of > delay-sensitive real-time traffic and will benefit from fast > handover > execution. This document specifies extension of the Mobile IPv6 > Fast > Handovers (FMIPv6) and the Fast Handovers for Proxy Mobile IPv6 > (PFMIPv6) protocols to include multicast traffic management in fast > handover operations. This multicast support is provided first > at the > control plane by a management of rapid context transfer between > access routers, second at the data plane by an optional fast traffic > forwarding that may include buffering. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-multimob-fmipv6-pfmipv6-multicast > > There's also a htmlized version available at: > http://tools.ietf.org/html/draft-ietf-multimob-fmipv6-pfmipv6-multicast-02 > > A diff from the previous version is available at: > http://www.ietf.org/rfcdiff?url2=draft-ietf-multimob-fmipv6-pfmipv6-multicast-02 > > > Please note that it may take a couple of minutes from the time of > submission > until the htmlized version and diff are available at tools.ietf.org > . > > Internet-Drafts are also available by anonymous FTP at: > ftp://ftp.ietf.org/internet-drafts/ > > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob > > > > > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob > From E.K.Jaff@student.bradford.ac.uk Tue Dec 17 06:42:52 2013 Return-Path: X-Original-To: multimob@ietfa.amsl.com Delivered-To: multimob@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CABD11AE1E5 for ; Tue, 17 Dec 2013 06:42:52 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.626 X-Spam-Level: X-Spam-Status: No, score=-0.626 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no 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 GX8xe1nYWLf2 for ; Tue, 17 Dec 2013 06:42:51 -0800 (PST) Received: from emea01-am1-obe.outbound.protection.outlook.com (mail-am1lp0012.outbound.protection.outlook.com [213.199.154.12]) by ietfa.amsl.com (Postfix) with ESMTP id 587D51AE1E1 for ; Tue, 17 Dec 2013 06:42:51 -0800 (PST) Received: from AM3PR03MB449.eurprd03.prod.outlook.com (10.242.111.15) by AM3PR03MB563.eurprd03.prod.outlook.com (10.242.111.154) with Microsoft SMTP Server (TLS) id 15.0.842.7; Tue, 17 Dec 2013 14:42:49 +0000 Received: from AM3PR03MB450.eurprd03.prod.outlook.com (10.242.111.20) by AM3PR03MB449.eurprd03.prod.outlook.com (10.242.111.15) with Microsoft SMTP Server (TLS) id 15.0.842.7; Tue, 17 Dec 2013 14:42:48 +0000 Received: from AM3PR03MB450.eurprd03.prod.outlook.com ([10.242.111.20]) by AM3PR03MB450.eurprd03.prod.outlook.com ([10.242.111.20]) with mapi id 15.00.0842.003; Tue, 17 Dec 2013 14:42:48 +0000 From: EK Jaff To: "multimob@ietf.org" Thread-Topic: How is the HNP of a MN maintained in different MAGs within PMIPv6 domain? Thread-Index: AQHO+zX8wzJOwD3N2kyWTFVmxWwrN5pYdcyV Date: Tue, 17 Dec 2013 14:42:47 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-GB X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [143.53.36.10] x-forefront-prvs: 006339698F x-forefront-antispam-report: SFV:NSPM; SFS:(10019001)(199002)(189002)(74316001)(85306002)(83072002)(74366001)(81342001)(80022001)(79102001)(66066001)(63696002)(2656002)(87266001)(76796001)(76786001)(59766001)(76576001)(77982001)(56776001)(54316002)(49866001)(50986001)(47976001)(81686001)(81816001)(47736001)(85852003)(65816001)(81542001)(80976001)(33646001)(90146001)(76482001)(4396001)(69226001)(16236675002)(74876001)(46102001)(87936001)(83322001)(53806001)(54356001)(74706001)(51856001)(47446002)(74482001)(74662001)(74502001)(31966008)(56816005)(24736002); DIR:OUT; SFP:1102; SCL:1; SRVR:AM3PR03MB449; H:AM3PR03MB450.eurprd03.prod.outlook.com; CLIP:143.53.36.10; FPR:; RD:InfoNoRecords; A:0; MX:1; LANG:en; Content-Type: multipart/alternative; boundary="_000_c4c634366a6f4ffeae5e3a84f8442444AM3PR03MB450eurprd03pro_" MIME-Version: 1.0 X-OriginatorOrg: student.bradford.ac.uk X-Mailman-Approved-At: Tue, 17 Dec 2013 08:24:36 -0800 Subject: [multimob] How is the HNP of a MN maintained in different MAGs within PMIPv6 domain? X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 14:47:49 -0000 --_000_c4c634366a6f4ffeae5e3a84f8442444AM3PR03MB450eurprd03pro_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable ________________________________ Dear Sir, I have been going through RFC 6224 and RFC 5213 and looking forward to th= e details of how the mobile node's (MN) Home Network Prefix (HNP) is mainta= ined within the PMIPv6 domain as the MN moves from one mobility access gate= way (MAG) to another. When I read the following statement on page 43 of RFC 5213, I was left wond= ering how this could be achieved. "The specific details on how the network maintains this association between= the prefix set and the interfaces, specially during the mobility session h= andoff between interfaces, is outside the scope of this document." Please, can somebody explain to me or direct me to the document which gives= detail explanation of how the network maintains the MN's HNP as the MN mo= ves from one MAG to another within the PMIPv6 domain? Thanks. Esua Jaff --_000_c4c634366a6f4ffeae5e3a84f8442444AM3PR03MB450eurprd03pro_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 
Dear Sir,
 
 I have been going= through RFC 6224 and RFC 5213 and  looking forward to the details of = how the mobile node's (MN) Home Network Prefix (HNP) is maintained wit= hin the PMIPv6 domain as the MN moves from one mobility access gateway (MAG) to another. 
 
When I read the followi= ng statement on page 43 of RFC 5213, I was left wondering how this could be= achieved.
 
"The specific details on how the network maintains= this association between the prefix = set and the interfaces, specially during the mobility session handoff betwe= en interfaces, is outside the scope of this documen= t."
 
Please,= can somebody explain to me or direct me to the document which gives detail= explanation of how the  network maintains the MN's HNP as t= he MN moves from one MAG to another within the PMIPv6 domain?
 
Thanks.
 
Esua Jaff
--_000_c4c634366a6f4ffeae5e3a84f8442444AM3PR03MB450eurprd03pro_-- From sebastian.woelke@posteo.de Wed Dec 18 05:42:26 2013 Return-Path: X-Original-To: multimob@ietfa.amsl.com Delivered-To: multimob@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 624B01AE401 for ; Wed, 18 Dec 2013 05:42:26 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.688 X-Spam-Level: X-Spam-Status: No, score=-0.688 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.538] 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 iHDJIM1-TKmJ for ; Wed, 18 Dec 2013 05:42:24 -0800 (PST) Received: from mx02a.posteo.de (mx02a.posteo.de [89.146.194.168]) by ietfa.amsl.com (Postfix) with ESMTP id 4D3081AE400 for ; Wed, 18 Dec 2013 05:42:24 -0800 (PST) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.posteo.de (Postfix) with ESMTP id 1DCB3298A16F for ; Wed, 18 Dec 2013 13:42:22 +0000 (UTC) X-Virus-Scanned: amavisd-new at posteo.de Received: from posteo.de ([10.125.125.134]) by localhost (amavis1.posteo.de [10.125.125.165]) (amavisd-new, port 10026) with ESMTP id J-HUmKY2HGea for ; Wed, 18 Dec 2013 14:42:13 +0100 (CET) Received: from mail.posteo.de (localhost [127.0.0.1]) by mail.posteo.de (Postfix) with ESMTPSA id 58DCF2040423A for ; Wed, 18 Dec 2013 14:42:13 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 18 Dec 2013 14:42:13 +0100 From: Sebastian Woelke To: Multimob Message-ID: <13b34fafb5a5495dfec1a0e9c137c36d@posteo.de> X-Sender: sebastian.woelke@posteo.de User-Agent: Posteo Webmail Subject: [multimob] release of a igmp/mld proxy X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 13:42:26 -0000 Hi, I would like to announce a new version of the mcproxy. It can be downloaded from our project page (http://mcproxy.realmv6.org/). The mcproxy complies the IGMP/MLD proxy standard (RFC 4605) and supports the group membership protocols IGMPv3 and MLDv2 as well. In additional it meets the requirements of the multicast source and listener support in proxy mobile IPv6 (draft-ietf-multimob-pmipv6-source-06 and RFC 6224). Key features: - supports IPv4 (IGMPv3) - supports IPv6 (MLDv2) - can be instantiated multiple times - dynamically configurable at runtime - can be configured to peer data between its instances - supports multiple upstreams For further questions and comments don't hesitate to contact me. Kind regards, Sebastian From sarikaya2012@gmail.com Wed Dec 18 08:40:56 2013 Return-Path: X-Original-To: multimob@ietfa.amsl.com Delivered-To: multimob@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F026C1AE1BA for ; Wed, 18 Dec 2013 08:40:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.224 X-Spam-Level: X-Spam-Status: No, score=0.224 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DEAR_SOMETHING=1.973, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no 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 2ir4HZ_nHaYo for ; Wed, 18 Dec 2013 08:40:54 -0800 (PST) Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 302421AD6BF for ; Wed, 18 Dec 2013 08:40:53 -0800 (PST) Received: by mail-la0-f42.google.com with SMTP id ec20so4005831lab.15 for ; Wed, 18 Dec 2013 08:40:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=H/M57O+jJ9iaROW/ZWq+0qAjV57yjx8whrfxv4faoyk=; b=FgvPP3z201h3caYKscdhqjM8FdNBqtXgjqMao6vMWNu61Z++wSMw6bg1gqIGYFaW2O zLmXyMbK6GaYsjzc2lS3oTx8nB4zC3oPeLeseVok0hhYKDwqWGx4n6cHtQdrx5C3rPsB ZtpX4m1ScglTc1dFlLqEesR6OoLvhF97eOicAHWyjisykICFwn4RWUHKvJBVJxPNEQ+/ rsocJXugUWtz5hORn0ageAkN3G3Ltb4hu8q9claYiROIEz9+I+fTAWhTs1WnPDRy2/2G +mU/p1fKtQ/2vEVLekYpn5SHNUTk+4Usyjrcmdw3Uqj+bk7ECHErlLTyQKSuzzwu7ouA WISQ== MIME-Version: 1.0 X-Received: by 10.112.16.137 with SMTP id g9mr1887770lbd.1.1387384851942; Wed, 18 Dec 2013 08:40:51 -0800 (PST) Received: by 10.115.4.165 with HTTP; Wed, 18 Dec 2013 08:40:51 -0800 (PST) In-Reply-To: References: Date: Wed, 18 Dec 2013 10:40:51 -0600 Message-ID: From: Behcet Sarikaya To: EK Jaff Content-Type: multipart/alternative; boundary=001a11c3dba644537204edd1b5ec Cc: "multimob@ietf.org" Subject: Re: [multimob] How is the HNP of a MN maintained in different MAGs within PMIPv6 domain? X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Dec 2013 16:40:56 -0000 --001a11c3dba644537204edd1b5ec Content-Type: text/plain; charset=ISO-8859-1 Hi all, Can anyone please help Esua? Sri? Thomas? Regards, Behcet On Tue, Dec 17, 2013 at 8:42 AM, EK Jaff wrote: > ------------------------------ > > Dear Sir, > > I have been going through RFC 6224 and RFC 5213 and looking forward to > the details of how the mobile node's (MN) Home Network Prefix (HNP) is > maintained within the PMIPv6 domain as the MN moves from one mobility > access gateway (MAG) to another. > > When I read the following statement on page 43 of RFC 5213, I was left > wondering how this could be achieved. > > "The specific details on how the network maintains this association > between the prefix set and the interfaces, specially during the mobility > session handoff between interfaces, is outside the scope of this > document." > > Please, can somebody explain to me or direct me to the document which > gives detail explanation of how the network maintains the MN's HNP > as the MN moves from one MAG to another within the PMIPv6 domain? > > Thanks. > > Esua Jaff > > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob > > --001a11c3dba644537204edd1b5ec Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,

Can anyone p= lease help Esua?

Sri?

Thomas?

Regard= s,

Behcet


On Tue, Dec 17, 2013 at 8:42 AM, EK Jaff <E.K.Jaff@student.b= radford.ac.uk> wrote:

=A0
Dear Sir,
=A0
=A0I have been going throug= h RFC 6224 and RFC 5213 and=A0 looking forward to the details of how the=A0= mobile node's (MN) Home Network Prefix (HNP) is maintained within the P= MIPv6 domain as=A0the MN=A0moves from one mobility access gateway (MAG) to another.=A0
=A0
When I read the following s= tatement on page 43 of RFC 5213, I was left wondering how this could be ach= ieved.
=A0
"The specific details on how the network maintains= this association between the prefix = set and the interfaces, specially during the mobility session handoff betwe= en interfaces, is outside the scope of this documen= t."
=A0
Please,= can somebody explain to me or direct me to the document which gives detail= explanation of how the=A0 network maintains the MN's=A0HNP as=A0the=A0= MN=A0moves from one MAG to another within the PMIPv6 domain?<= /div>
=A0
Thanks.
=A0
Esua Jaff

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


--001a11c3dba644537204edd1b5ec-- From internet-drafts@ietf.org Thu Dec 26 14:16:32 2013 Return-Path: X-Original-To: multimob@ietfa.amsl.com Delivered-To: multimob@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F8031AE080; Thu, 26 Dec 2013 14:16:32 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 lVFXYSOM_NYj; Thu, 26 Dec 2013 14:16:29 -0800 (PST) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 928361AE075; Thu, 26 Dec 2013 14:16:29 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: internet-drafts@ietf.org To: i-d-announce@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 4.90 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20131226221629.30388.58266.idtracker@ietfa.amsl.com> Date: Thu, 26 Dec 2013 14:16:29 -0800 Cc: multimob@ietf.org Subject: [multimob] I-D Action: draft-ietf-multimob-handover-optimization-07.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.15 List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Dec 2013 22:16:32 -0000 A New Internet-Draft is available from the on-line Internet-Drafts director= ies. This draft is a work item of the Multicast Mobility Working Group of the I= ETF. Title : PMIPv6 multicast handover optimization by the Sub= scription Information Acquisition through the LMA (SIAL) Authors : Luis M. Contreras Carlos J. Bernardos Ignacio Soto Filename : draft-ietf-multimob-handover-optimization-07.txt Pages : 36 Date : 2013-12-26 Abstract: This document specifies an experimental multicast handover optimization mechanism for Proxy Mobile IPv6 to accelerate the delivery of multicast traffic to mobile nodes after handovers. The mechanism is based on speeding up the acquisition of mobile nodes' multicast context by the mobile access gateways. To do that, extensions to the current Proxy Mobile IPv6 protocol are proposed. These extensions are not only applicable to the base solution for multicast support in Proxy Mobile IPv6, but they can also be applied to other solutions developed to avoid the tunnel convergence problem. Furthermore, these extensions are also independent of the role played by the mobile access gateway within the multicast network (either acting as multicast listener discovery proxy or multicast router). The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-multimob-handover-optimization/ There's also a htmlized version available at: http://tools.ietf.org/html/draft-ietf-multimob-handover-optimization-07 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-multimob-handover-optimizatio= n-07 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/