Dear administrators, Just wanted to raise the issue on the MAP-T standardization. Reliance JIO is a new service provider in India and is about to launch the 4G services along with FTTX. We are banking upon getting MAP-T as our deployment mode as measure to avoid CGNAT. Already we are in the process of testing MAP-T CPE devices and MAP-BR on our Gateways.
I request all concerned to put this on standardization track and get the RFC as quickly as possible so that we can drive all the eco-system like DHCP /ACS / Gateways, etc., towards the deployment scenario. With regards, B.Nagaraj Cabin 3, 2A, 2nd floor, RCP complex, Thane Belapur Road Ghonsoli, Navi Mumbai-400701 Phone: Work: +912244773047 Mobile: +919867564147 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Rajiv Asati (rajiva) Sent: Tuesday, April 09, 2013 3:24 AM To: Tom Taylor; Softwires Subject: Re: [Softwires] MAP-E question -- first prefix Hi Tom, Good catch. We also caught this last week and started formulating the revised text. We may strive to rewrite this section a bit, time permitting. > Question: does the second sentence say anything different from the > first one? Not really. :) > Question: if the MAP node is configured differently, how will other > nodes be able to synthesize its MAP IPv6 address from the FMR? You mean, BMR ! Cheers, Rajiv -----Original Message----- From: Tom Taylor <[email protected]> Date: Monday, April 8, 2013 5:20 PM To: Softwires-wg list <[email protected]> Subject: [Softwires] MAP-E question -- first prefix >In Section 5.2 of -map-05, there is the paragraph: > >The MAP subnet ID is defined to be the first subnet (all bits set to > zero). Unless configured differently, a MAP node MUST reserve the > first IPv6 prefix in an End-user IPv6 prefix for the purpose of MAP. > >Question: does the second sentence say anything different from the >first one? > >Question: if the MAP node is configured differently, how will other >nodes be able to synthesize its MAP IPv6 address from the FMR? > >Tom Taylor >_______________________________________________ >Softwires mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/softwires _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires "Confidentiality Warning: This message and any attachments are intended only for the use of the intended recipient(s). are confidential and may be privileged. If you are not the intended recipient. you are hereby notified that any review. re-transmission. conversion to hard copy. copying. circulation or other use of this message and any attachments is strictly prohibited. If you are not the intended recipient. please notify the sender immediately by return email. and delete this message and any attachments from your system. Virus Warning: Although the company has taken reasonable precautions to ensure no viruses are present in this email. The company cannot accept responsibility for any loss or damage arising from the use of this email or attachment." _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
