Re: [MEXT] One issue about RFC 5142(Mobility Header Home Agent Switch Message)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MEXT] One issue about RFC 5142(Mobility Header Home Agent Switch Message)



Hi Robert,

Robert Yang wrote:
> Hi, Brian, Vijay and all
> In section 6.1 of RFC 5142 it says that: it (MN) MUST send a Binding Error
> message with the Status field set to 2 (unrecognized MH Type value) if it
> does not support the message type.
> But my Question is that: 
> (1)Binding error message is sent from CN instead of MN as described in
> rfc3775;

Yes, this is something Hui pointed-out too, and I know that what 
entities are allowed to send Binding Errors is under revision for 
3775-bis, so I'll suggest that text be relaxed further than just 
allowing CNs and HAs to send it.  After all, a MN is going to pretty 
much implement all of the CN functionality, so it's not a stretch to 
allow it to send a Binding Error.

> (2) HA switch message is a new message for entities such as MN, HA in
> rfc3775, so MN as well as HA should be updated to support this message;

Yes, updating the Linux implementation is on my to-do list, I can't 
speak for any other vendors.

Thanks for the feedback,

-Brian
_______________________________________________
MEXT mailing list
MEXT at ietf.org
http://www.ietf.org/mailman/listinfo/mext



Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.