Re: AW: [nemo] WG: new I-D on HA filtering
Ryuji Wakikawa<[email protected]> Wed, 23 Jul 2003 23:34:44 +0900
| Newsgroups | gmane.ietf.mobileip |
|---|---|
| Organization | Keio University |
| Message-ID | <[email protected]> |
Hi > > > -----Ursprüngliche Nachricht----- > > Von: [email protected] [mailto:owner-mobile- > > [email protected]] Im Auftrag von Ryuji Wakikawa > > Gesendet: Dienstag, 22. Juli 2003 12:18 > > An: [email protected] > > Cc: [email protected]; [email protected]; mobile- > > [email protected] > > Betreff: Re: [nemo] WG: [mobile-ip] new I-D on HA filtering > > > > Hello, > > > > At Wed, 23 Jul 2003 15:11:36 +0200, > > Thomas Noel wrote: > > > > > > Hi Koojana, All, > > > > > > > > Perhaps, we should initiate a discussion in mobile-ip or nemo WG to > > discuss > > > > > > > > about this topic. > > > > > > > I Agree with you, we have now several drafts and it will be interesting > > > to converge towards an unique solution to solve this issue. > > > > Can we discuss filters/policies and multipleCoAs registration separately? > > IMHO, Multiple CoAs and Flow Distributions should be discussed together. The > reason is because once multiple CoAs are available, the natural requirement > that follows would be to use these points of attachments efficiently. I understand there is a way to manage filters at the IP level, but there are also other ways to manage them. If a user wants to manage filters information statically, does she/he still need to support filters management at IP layer? regards ryuji > > > > Most of draft needs multiple CoAs registrations, but some of systems > > do not want to support filters/policies on the IP layer. > > > > Our draft(multiplecoa) deals with only multiple CoAs registration. > > > > > Perhaps, Nemo is the ideal WG to discuss about this topic. > > > > It might be better to keep discussing it in MIP6/MIPSHOP WG, because > > NEMO is based on Mobile IPv6. Once MIP supports multiplecoa, filters > > whatever, NEMO can have the same feature. > > As Hesham suggested, I too believe that mip6 or mipshop would be the best > place to discuss as it should be a extension to the MIPv6 base > specification, which is not considered simultaneous bindings as in the MIPv4 > RFC. > > Kind Regards > Koojana > > > If NEMO still needs further operations, then NEMO becomes the ideal WG. > > > > best regards, > > ryuji > > > > > > > > Regards > > > > > > Thomas Noel > > > LSIIT > > > > > > > > > > > Kind regards > > > > > > > > Koojana > > > > > > > > -----Ursprüngliche Nachricht----- > > > > Von: [email protected] > > > > [mailto:[email protected]] Im Auftrag von Nicolas > > > > Montavont > > > > Gesendet: Mittwoch, 23. Juli 2003 09:55 > > > > An: mobileip > > > > Betreff: [mobile-ip] new I-D on HA filtering > > > > > > > > Hi all, > > > > > > > > We just submitted a new I-D on Home Agent Filtering for Mobile IPv6, > > > > available at > > > > > > > > http://www-r2.u-strasbg.fr/~montavont/draft-montavont-mobileip-ha- > > filtering- > > > > v6-00.txt > > > > > > > > It will be soon available in the IETF repertories. > > > > > > > > This I-D proposes a solution for the MN to set filters on its home > > > > agent. Filters can be used to spread flows on different CoAs (and > > > > potentially several network interfaces), and to forbid the redirection > > > > of certain flows from the home agent. > > > > > > > > Here is the abstract: > > > > > > > > Mobile IPv6 allows a MN to receive incoming packets to its home > > address > > > > while it is away from its home network. In a heterogeneous > > environment, > > > > a MN may have multiple interfaces, each with different > > characteristics. > > > > While a MN is in a visited network, due to the performance of the > > > > interfaces or to the user preferences, the MN may want to forbid the > > > > redirection from its home agent of a kind of flow, or to indicate a > > > > target CoA for a kind of flow. > > > > In this draft, we propose new mobility options that allow a MN to > > > > advertise filters to its home agent. A filter is associated with a > > CoA, > > > > in such a way that the MN can register several CoA and can register > > > > several filters for one CoA. A filter may indicate that a flow which > > map > > > > to a filter must be dropped or must be redirected to the indicated > > CoA. > > > > > > > > Regards, > > > > Nicolas > > > > > > > > > > > > > > > > > > > > > >