Well, actually on this topic I think it may make sense at least from a terminology consistency perspective to go back to calling out the Default Mapping Rule (DMR) and, just like the BMR, marking it as mandatory. That's what actually is already in the DHCP draft.
Regards, Woj. On 12 February 2013 15:22, Ole Troan <[email protected]> wrote: > Tom, > > > Thanks. What about the assertions in the bullets? > > sorry, may be my short term memory... what do you mean? > > cheers, > Ole > > > > > > On 12/02/2013 3:27 AM, Ole Troan wrote: > >> Tom, > >> > >>> I'm still hoping to see a response to this. > >>> > >>> On 06/02/2013 8:42 AM, Tom Taylor wrote: > >>>> Section 5 of the latest version of MAP has the following: > >>>> > >>>> 1. Basic Mapping Rule (BMR) - mandatory, used for IPv4 prefix, > >>>> address or port set assignment. There can only be one Basic > >>>> Mapping Rule per End-user IPv6 prefix. The Basic Mapping Rule > is > >>>> used to configure the MAP IPv6 address or prefix. > >>>> > >>>> 2. Forwarding Mapping Rule (FMR) - optional, used for forwarding. > >>>> The Basic Mapping Rule is also a Forwarding Mapping Rule. Each > >>>> Forwarding Mapping Rule will result in an entry in the Rules > >>>> table for the Rule IPv4 prefix. > >>>> > >>>> Question: there will always be a BMR. In the absence of additional > >>>> rules, how does a CE know whether it can use the BMR for forwarding or > >>>> must always use the default rule? > >> > >> the answer to that is in section 7, last bullet. > >> > >> that is, the MAP CE must be configured to be in hub and spoke mode or > mesh mode. > >> which mode it is in decided if the BMR is used for forwarding or not. > >> > >> cheers, > >> Ole > >> > >> > > _______________________________________________ > Softwires mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/softwires >
_______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
