Hi Behect and Frank, Thanks for putting this draft together. I have few comments/questions:
- Introduction, 5th paragraph. Mention the MAG is the ds-lite softwire initiator and CGN collocates with LMA (HA). - Does the ds-lite CGN and LMAA use the same IPv6 address? - For client Mobile IPv6, I agree that the ds-lite CGN should collocate with HA. - It should recommend to use public ipv4 addresses for the CGN pool. This can greatly reduce the complexity to avoid double-NAT. - Discuss DNS proxy placement for IPv4 client as such DNS traffic won't run over ds-lite softwire. - 3.1 Step 2. Since multiple MNs may use the same MAG to go to the same destination, the LMA can't search only the binding cache for the dst IPv4 address (128.0.0.1). Instead, the LMA must search the <MAG-IPv6-addr, MN-IPv4-addr, src-port, transport-protocol, dst-IPv4-addr, dst-port, transport-protocol> tuple. - 3.2 mentions about GRE. It is worth to mention if GRE is used, the MAG will run GRE-in-IPv6 instead of IPv4-in-IPv6. Either case, only one tunnel protocol is used rather than tunnel-in-tunnel. - Section 4 is really puzzling me. Why does MN need to get the IPv4 home address from HA? Can it request only the IPv6 home address and use the IANA assigned ds-list IPv4 address (e.g. a.b.c.d)? Then the MN will source all IPv4 datagram with this well-known address. - Section 4.2. This is not true. The well-known IPv4 address is unique to the client because the binding table will index the client by both the IPv6 Home address and the well-known address. As such, all the ports are available to the client. * There is cost for client MIPv6 . The MIPv6 client must send keepalive to maintain the NAT binding in the HA. This is less than ideal in battery sensitive mobile device. So a combination of A+P and > ds-lite may be a better fit in this model. Thanks, Yiu On 7/14/09 11:01 AM, "Behcet Sarikaya" <[email protected]> wrote: > > > Hi all, > We submitted this draft, please send your comments to the list. > > Regards, > > Behcet > > > > ----- Forwarded Message ---- >> > From: IETF I-D Submission Tool <[email protected]> >> > To: [email protected] >> > Cc: [email protected] >> > Sent: Monday, July 6, 2009 10:28:32 AM >> > Subject: New Version Notification for >> draft-sarikaya-softwire-dslitemobility-00 >> > >> > >> > A new version of I-D, draft-sarikaya-softwire-dslitemobility-00.txt has >> been >> > successfuly submitted by Behcet Sarikaya and posted to the IETF repository. >> > >> > Filename: draft-sarikaya-softwire-dslitemobility >> > Revision: 00 >> > Title: Dual-stack Lite Mobility Solutions >> > Creation_date: 2009-07-06 >> > WG ID: Independent Submission >> > Number_of_pages: 12 >> > >> > Abstract: >> > Two solutions are presented to show how to use Dual-Stack Lite >> > transition technique in mobile networks: one for Proxy Mobile IPv6 >> > and the other for Dual-Stack Mobile IPv6. Proxy Mobile IPv6 allows >> > IPv4 nodes to receive mobility services using an IPv4 home address. >> > Mobile node can have IPv4 only operation by sending IPv4 datagrams >> > which are encapsulated by the Mobile Access Gateway (MAG) at the DS- >> > lite home router and and tunneled to Local Mobility Anchor (LMA) >> > which is also DS-lite carrier-grade Network Address Translator (NAT). >> > In case of client based mobility using DSMIPv6, mobile node is a >> > dual-stack node and it can receive an IPv4 home address from the home >> > agent which is co-located with DS-lite carrier-grade NAT. Mobile >> > node (MN) encapsulates IPv4 datagrams in IPv6 which are decapsulated >> > at the home agent (HA). Mobile network could be WiMAX network or >> > 3GPP Long Term Evolution network. >> > >> >> > >> > >> > >> > The IETF Secretariat. > > > > > > _______________________________________________ > Softwires mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/softwires >
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
