[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: proposed text for charter
Catching up on some back mail, I'd like to comment that IMO, the charter
> o The solution must not cause problems for mobility. That is, it
> should be possible to continue using Mobile IPv6 even when using
> shim6 simultaneously. However, any optimizations or advanced
> configurations are out of scope for shim6.
> I would suggest to write "should be possile to continue using mobility
> support protocols such as Mobile IPv6 land NEMO Basic Support"
> An additional item such as the following one would be useful:
> - The WG will ensure that various mechanisms defined within other IETF
> WGs will continue to work when using shmi6 simultaneously. To achieve
> this, the Shim6 WG will interact with other WGs when needed, and may
> place requirements on the protocols developed by those WGs.
I disagree with this addtion, as it is not clear to me how shim6 would interact
with these solutions, or what deployment models folks have in their mind. I
agree with Erik's general scetch of shim6 - mip6 interaction, but I am not sure
if everyone has come to agreement. I could think of many possible interactions -
running MIPv6 over SHIM6, for example. What would it mean to run shim6 with fmip
or hmip? With respect to NEMO, are the multiple prefixes advertised over the NEMO
link or would there be both a nemo-aware interface active and another non-NEMO
interface. All of these questions are secondary in nature, and I think we should
actually get some of the basic shim6 work done before opening these boxes.
Finally, Brian says:
> Well, I'd want to see a walkthrough to be sure that there aren't tricky
> cases where the change of locators forced by shim6 would cause perverse
> routing due to MIP6, or where a change of c/o address due to MIP6 would
> confuse shim6. (Incidentally there are similar questions if we try to run
> SCTP over shim6.) I just don't want charter language that later proves
> to be mathematically impossible to meet. It goes without saying that
> interworking is highly desirable.
Which I basically agree with. I think we have to have a stable understanding
of how SHIM6 works before going onto these topics.