Hi Seil,
On 27.07.2012 11:58, Seil Jeon wrote:
As you pointed it out, multicast mobility routing optimization needs to be
addressed well. In Vancouver meeting, that would be discussed.
And regarding on your answer to my question,
if you are intending to present all the possible ways including
optimization, don't you think this needs to go along with
draft-ietf-multimob-pmipv6-ropt, even though it is informational?
No problem with informational ... and as I wrote previously: it does go
along with the deployment options of draft-ietf-multimob-pmipv6-ropt (up
to the point where this is specific) - the corresponding pointers are
already in the draft.
Cheers,
Thomas
-----Original Message-----
From: Thomas C. Schmidt [mailto:[email protected]]
Sent: Thursday, July 26, 2012 1:01 AM
To: Seil Jeon
Cc: [email protected]
Subject: Re: [multimob] Fwd: New Version Notification for
draft-ietf-multimob-pmipv6-source-01.txt
Hi Seil,
draft-ietf-multimob-pmipv6-source addresses (and is intended to address) the
solution space for multicast source mobility in PMIP. You're right in
pointing at compatibility to listener solutions.
According to listener mobility, we explicitly included the basic scenarios
yet, i.e.,
* Base solution (RFC 6224)
* Single proxy upstream (as subject of draft-ietf-multimob-pmipv6-ropt)
* Direct multicast routing (as subject of draft-ietf-multimob-pmipv6-ropt)
We should address additional aspects, if arising.
In the context of draft-ietf-multimob-pmipv6-ropt, there are several issues:
1. As you mention, draft-ietf-multimob-pmipv6-ropt contains initial trials
to route optimization, which it shouldn't. This was approved as an
informational document explaining simply the deployment cases mentioned
above.
2. draft-ietf-multimob-pmipv6-ropt is neither complete, nor concise ... I
would like to point at my earlier review of March 6th which are still
unaddressed.
Cheers,
Thomas
On 25.07.2012 23:51, Seil Jeon wrote:
Hi Thomas,
I have simple question on this draft.
How do you think solution scope and objective?
- Listing all possible ways of supporting source mobility including
optimization?
- If so, which level do you think should be considered for extension?
- Wouldn't it be focused on base source mobility deployment option
without optimization?
Now, we have been working on multicast listener solutions separately;
base deployment option [RFC6224] without any modification and
extension of existing standard protocols and multicast mobility
routing optimization [ietf-multimob-pmipv6-ropt].
This draft includes several cases of source mobility support including
optimization. I think listener and source solutions need to be
compatible each other. Are you considering that? And routing
optimization for listener is now being progressed but not finished yet.
Regards,
Seil
-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Thomas C. Schmidt
Sent: Monday, July 16, 2012 9:37 PM
To: [email protected]
Subject: [multimob] Fwd: New Version Notification for
draft-ietf-multimob-pmipv6-source-01.txt
Hi all,
we've prepared and uploaded a new version of the source mobility draft.
The document has been largely extended with the following new
contributions:
1. Direct routing with PIM-SM and PIM-SSM has been added.
2. PMIP synchronization with PIM added for improved handover.
3. Direct routing with BIDIR-PIM has been added.
4. MLD Proxy extensions requirements added.
5. Peering of MLD Proxies added.
6. First sketch of multiple upstream proxy added.
7. Editorial improvements.
8. Updated references.
Comments, feedback & reviews welcome!
See you in Vancouver,
Thomas
-------- Original Message --------
Subject: New Version Notification for
draft-ietf-multimob-pmipv6-source-01.txt
Date: Mon, 16 Jul 2012 13:32:17 -0700
From: [email protected]
To: [email protected]
CC: [email protected], [email protected], [email protected]
A new version of I-D, draft-ietf-multimob-pmipv6-source-01.txt
has been successfully submitted by Thomas C. Schmidt and posted to the
IETF repository.
Filename: draft-ietf-multimob-pmipv6-source
Revision: 01
Title: Mobile Multicast Sender Support in Proxy Mobile
IPv6
(PMIPv6)
Domains
Creation date: 2012-07-16
WG ID: multimob
Number of pages: 24
URL:
http://www.ietf.org/internet-drafts/draft-ietf-multimob-pmipv6-source-
01.txt
Status:
http://datatracker.ietf.org/doc/draft-ietf-multimob-pmipv6-source
Htmlized:
http://tools.ietf.org/html/draft-ietf-multimob-pmipv6-source-01
Diff:
http://tools.ietf.org/rfcdiff?url2=draft-ietf-multimob-pmipv6-source-0
1
Abstract:
Multicast communication can be enabled in Proxy Mobile IPv6 domains
via the Local Mobility Anchors by deploying MLD Proxy functions at
Mobile Access Gateways, via a direct traffic distribution within an
ISP's access network, or by selective route optimization schemes.
This document describes the support of mobile multicast senders in
Proxy Mobile IPv6 domains for all three scenarios. Protocol
optimizations for synchronizing PMIPv6 with PIM, as well as extended
MLD Proxy functions are presented. Mobile sources always remain
agnostic of multicast mobility operations.
The IETF Secretariat
_______________________________________________
multimob mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/multimob
_______________________________________________
multimob mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/multimob
_______________________________________________
multimob mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/multimob
