Re: CARD issue#29: more text on use of "Context-ID" and"M-flag"required
Vijay Devarapalli <[email protected]>
| Newsgroups | gmane.ietf.seamoby |
|---|---|
| Message-ID | <[email protected]> |
fine with me. Marco Liebsch wrote: > > I agree. Also specific text on use of the context-id will be incorporated. > However, since we found that the L2 ID has to carry kind of status code > to indicate to the MN in a reply that AR was not able to resolve the > requested L2 ID (issue#39), we can avoid the M-flag and incorporate all > these > notifications into an 8 bit status code field within the L2 ID sub-option. > This means for example. 0x00 set by default in a CARD Request when > MN sends the L2 ID for resolution to its AR. AR can return 0x01 as an > OK indicator, 0x02 could be the indicator that L2 ID matches with a > previously > resolved CAR IP address (context-id match, replaces the M-flag), 0x03 could > indicate the error case due to the AR was not able to resolve the L2 ID... > > What do you think? > > marco