[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MEXT] Review of draft-ietf-mext-flow-binding-01
I should like to understand the motivation for N-cast. Which application
will have a need, when sending packets to a specific mobile node, for
having its packets replicated and sent over N different links
to a mobile node?
Christian
--- Den man 9/3/09 skrev Giaretta, Gerardo <gerardog at qualcomm.com>:
> Fra: Giaretta, Gerardo <gerardog at qualcomm.com>
> Emne: [MEXT] Review of draft-ietf-mext-flow-binding-01
> Til: "mext at ietf.org" <mext at ietf.org>
> Dato: mandag 9. marts 2009 23.37
>
>
> - Section 6.1.1:
>
>
>
> o If the Action
> field is set to
> indicate N-cast, the Binding
>
>
> Reference sub-option must
> be present and it must contain one or
>
> more
> BIDs. If the
> Binding Update sub-option includes only one
>
> BID,
> it must be pointing
> to a care-of address other than the one
>
>
> included in the binding
> update.
>
>
>
> Based on this, the n-cast would be
> done between the CoA
> in the BID and the CoA in the source address of the packet.
> I think it would be
> much cleaner to always include all BIDs for which n-casting
> is requested. The
> source address of the packet is not processed as CoA when a
> BID is present
> based on the MCoA draft (similarly to what happens in case
> the Alt-CoA option
> is used). This comment applies also to the fourth bullet of
> section 8.1
>
>
>
Find din nye laptop på kelkoo.dk. Se de gode tilbud her - http://dk.yahoo.com/r/pat/mm