Remi, [...]
>>> 5. >>> Of course, the suffix parameter can be added to MAP if decided (no problem >>> with that), but the feature comparison table remains based on existing >>> drafts. >> >> not, needed. the MAP subnet-id is defined to be 0. > > AFAIK, this statement makes sense only if you assume that the 4-bit NTT > suffix is set to 0 in all customer sites. > If this is assumed, it is a great simplification of the problem. > It deserves to be clearly stated. MAP specifies a subnet-id of 0. those are the bits between the End-user IPv6 prefix length and the interface-id. e.g. if a /56 is delegated there will be 8 bits of 0. we have discussed if this needs to be configurable. > With this assumption, the suffix parameter is indeed no longer needed (not > more for 4rd-U than for MAP). regardless of what the suffix parameter is. 0xF or 0x0. it has to be the same across the domain. in the 3rd party CPE use case, which prefixes are available to the 3rd party CPE may be outside of your control. the 3rd party model has the following issues: - how to get routing for the MAP prefix - how does prefix assignment work at all (general IPv6 problem) - how is the mechanism provisioned? there is no DHCPv6 path, unless the 3rd party CPE has a tunnel "home" cheers, Ole _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
