Maoke - Section 7.3 page 19: A MAP-E CE provisioned with only a Default Mapping Rule, as in the 1:1 case, and with no IPv4 address and port range configured by other means, MUST disable its NAT44 functionality. Question #8: what is the consequence of disabling the NAT44 functionality on CE when a subscriber having a PSID of a share IPv4 address is running behind that CE as a 1:1 mode domain?
Supposed the draft is talking about the backward compatibility with DS-lite. When CE provisioned with only a Default Mapping Rule and the CE disable its NAT44 functionality, the CE turns to be B4 of DS-lite, the BR will turns to be stateful AFTR of DS-lite. But the question on the text of "as in the 1:1 case" seems still be there, because '1:1' continuous to puzzles us before it is defined. I don't think the "as in the 1:1 case" is necessary here in the context of this paragraph. Best Regards, Leaf -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Satoru Matsushima Sent: Thursday, June 28, 2012 2:32 PM To: Maoke Cc: Softwires-wg Subject: Re: [Softwires] map-00: review on the mode 1:1 Remark, Confusion of current 'draft-ietf-softwire-map-00' version of MAP about 1:1 is that independence between the ipv6 and ipv4 addressing could be represented as bellow: 1). ea-len equal to zero within a BMR/FMR for MAP-CE provisioning 2). only DMR provisioning for MAP-CE So in the 1), it doesn't mean NAT44 disabled on MAP CE. In the 2), it does require MAP CE to disable NAT44 for compatibility of MAP-CE(-E) be as DS-Lite B4, and MAP-CE(-T) to be compatible with stateless NAT64. cheers, --satoru On 2012/06/28, at 10:53, Maoke wrote: > Question #8.4: if there is no IPv4 address nor IPv4 stack, where do we need > to *disable* the NAT44? i agree with you that "NAT44 is disabled" here is > obvious but i see it is too obvious to cost a "MUST" in the specification. > "MUST disable" means WE, the HUMAN, MUST make an action according to the > specification. question clarified? please confirm that the editor/author of > this text refers the same thing as you interpreted. > _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
