[Softwires] 答复: 4rd Address Mapping - version-01

[Leaf yeh <[e-mail]>]

Jacni - It is used to route packets to the unique CE, but the CE index in the CE IPv6 address is derived from, for example, the IPv4 destination address + Port.

I thought the CE index (the fixed part of the rule), not the max CE index (which includes the dynamic part), could derived from the IPv4 destination address + Port in the received IPv4 packets at BR.



Best Regards,

Leaf







________________________________
发件人: Jacni Qin [[e-mail]]
发送时间: 2011年9月26日 7:17
到: Leaf yeh
Cc: Rémi Després; Softwires-wg
主题: Re: [Softwires] 4rd Address Mapping - version-01



On 9/24/2011 7:01 PM, Leaf yeh wrote:

The following is my quick comments & questions on the new updated draft.



https://datatracker.ietf.org/doc/draft-despres-softwire-4rd-addmapping/?include_text=1



Section 6



   …Its CE IPv6 prefix, Rule IPv6 prefix, and Rule

   IPv4 prefix, are supposed to be respectively 2001:db4:4444:4000::/52,

   2001:db0::/28, and 192.32../12 (i.e. 0x602). …



C1. The 1st 3 hex of the Rule IPv4 prefix, 0x602, should turn to be 96.32.0.0/12, right?



Section 7



Item                        Hexadecimal Value        Nb of bits



   - IPv4 port          :            8488                      16

   - Derived

      Max Port-set ID   :             488                      12

   - IPv4 address       :      60244444                        32

   - Rule IPv4 prefix

      that matches this

      IPv4 address      :      602                             12

   - Resulting CE index :         44444488                     32

   - Rule IPv6 prefix

      of the Rule       :  20010DB                             28

   - Padding to 64 bits :                 0                     4

   - Resulting

      CE IPv6 address   :  20010DB44444488002005EFE00000000   128

   - Prefix routed

      to the CE         :  20010DB444444                       52
-------------------------------------------------


C2. I supposed the CE IPv6 address is associated with the CE index (including part of IPv4 address delegated & masked by the Rule IPv4 prefix + the fixed PSID) to identify the unique CE device, not associated the dynamic part of the IPv4 layer-4 port. Otherwise, there will be a bunch of IPv6 address associated with one CE.

It is used to route packets to the unique CE, but the CE index in the CE IPv6 address is derived from, for example, the IPv4 destination address + Port.




Q1. Any more words for the understanding on the case definition of double-translation?



Please refer to the 4rd-T draft or other translation based approaches.


Cheers,
Jacni




Best Regards,

Leaf





-----Original Message-----
From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of Rémi Després
Sent: Thursday, September 22, 2011 7:18 PM
To: Softwires-wg
Subject: [Softwires] 4rd Address Mapping - version-01



Alain, all,



We have just posted a new version of our I-D on the proposed 4rd Address Mapping.

It is available at

www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt<http://www.ietf.org/id/draft-despres-softwire-4rd-addmapping-01.txt>



Our presentation will be based on THIS version, technically simpler than version -00.

Major differences and their justifications will be briefly explained.



Regards,

RD

_______________________________________________

Softwires mailing list

[e-mail]<mailto:[e-mail]>

https://www.ietf.org/mailman/listinfo/softwires



_______________________________________________
Softwires mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/softwires