From monami6-bounces@ietf.org Thu Feb 08 10:06:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HFAqI-0001tT-Ms; Thu, 08 Feb 2007 10:05:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HFAqH-0001tA-Ud
	for monami6@ietf.org; Thu, 08 Feb 2007 10:05:45 -0500
Received: from smtp03out.vivodinet.gr ([83.171.203.3] helo=smtp.vivodinet.gr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HFApj-0007eD-7w
	for monami6@ietf.org; Thu, 08 Feb 2007 10:05:45 -0500
Received: from [10.107.10.69] (dsl-88-218-0-117.customers.vivodi.gr
	[88.218.0.117])
	by smtp.vivodinet.gr (8.12.10/8.12.10) with ESMTP id l18FAe3m011979
	for <monami6@ietf.org>; Thu, 8 Feb 2007 17:10:40 +0200
Message-ID: <45CB3D37.7010605@ieee.org>
Date: Thu, 08 Feb 2007 17:09:43 +0200
From: "Niko A. Fikouras" <n.a.fikouras@ieee.org>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
	rv:1.7.13) Gecko/20060414
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] draft-soliman-monami6-flow-binding-03 implementation
References: <20070123145103.8ffkq5cmpn6s8wso@www.comnets.uni-bremen.de>
In-Reply-To: <20070123145103.8ffkq5cmpn6s8wso@www.comnets.uni-bremen.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV 0.88.7/2533/Wed Feb 7 16:20:47 2007 on
	smtp01.vivodinet.gr
X-Virus-Status: Clean
X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on smtp01.vivodinet.gr
X-LdapVfrom: From Address UnVerifiable
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Umar,

I have heard from Asanga that you have completed the implementation. 
Congratulations on your good work.
Have you been able to implement options 3 & 4 from section 4 (Protocol 
operations):

   Option 3: Source Port - Min, Source Port - Max

   Option 4: Source Port - Min, Source Port - Max, Dst Port - Min, Dst
   Port - Max

To be more precise. Is it possible to define a filter using ports 
without the presence of the protocol type.

Thanks in advance
niko

umr@comnets.uni-bremen.de wrote:

>Hello everybody at Monami6,
>
>I am implementing Flow Management support in nemo-mcoa following the
>draft-soliman-monami6-flow-binding-03 draft. I am using nemo-0.2-mcoa from
>Nautilus as a basis for my implementation. I have succeeded in implementing a
>basic flow management support in nemo-0.2-mcoa. I will continue sharing my
>experiences in this list.
>
>One of the issues to report is that in the PRO field in fid mobility option. It
>is said in the draft that it is a 4 bit field (section 3.1) and hence can carry
>unsigned integers from 0 to 15. However the draft also says value 255 should be
>put to PRO field in order to "Remove a flow binding". Since 255 can not be
>accomodated in a 4 bit PRO field I have used 15 (the maximum 4 bit number)
>currently in my implementation and it's working fine.
>
>   Regards,
>   Umar Toseef
>
>
>
>----------------------------------------------------------------
>This message was sent using IMP, the Internet Messaging Program.
>
>_______________________________________________
>Monami6 mailing list
>Monami6@ietf.org
>https://www1.ietf.org/mailman/listinfo/monami6
>
>  
>


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Mon Feb 12 06:05:27 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGYzQ-0001fV-Js; Mon, 12 Feb 2007 06:04:56 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGYzO-0001fK-RH
	for monami6@ietf.org; Mon, 12 Feb 2007 06:04:54 -0500
Received: from bugs.comnets.uni-bremen.de ([134.102.186.10]
	helo=mario.comnets.uni-bremen.de)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGYzN-0000g9-9w
	for monami6@ietf.org; Mon, 12 Feb 2007 06:04:54 -0500
Received: by mario.comnets.uni-bremen.de (Postfix, from userid 33)
	id 2754913ED5; Mon, 12 Feb 2007 12:04:52 +0100 (CET)
Received: from 134.102.155.201 ([134.102.155.201]) by
	www.comnets.uni-bremen.de (Horde MIME library) with HTTP for
	<umr@www.comnets.uni-bremen.de>; Mon, 12 Feb 2007 12:04:51 +0100
Message-ID: <20070212120451.pil4zn17xfk0kc4o@www.comnets.uni-bremen.de>
Date: Mon, 12 Feb 2007 12:04:51 +0100
From: umr@comnets.uni-bremen.de
To: monami6@ietf.org
Subject: Re: Re: [Monami6] draft-soliman-monami6-flow-binding-03 implementation
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.2)
X-Spam-Score: 0.2 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Niko,
        Thanks for the compliments! As far as the current implementation is
concerned we have not implemented Option:3 and Option:4 which means specifying
Source/Destination port range without mentioning protocol is not yet supported.
Actually we are using  ip6tables's marking functionality to mark ip6 packets.
And ip6tables does not allow specifying port range without defining protocol!

        On the other hand if we consider it conceptually, some protocols work
with ports like tcp,udp etc but others do not require any ports e.g. ICMPv6. So
it seems logical to have protocol mentioned when you want filter traffic on some
ports.

        What do you think about this ?

        Regards,
        Umar Toseef


-----------------------------------------------
Hi Umar,


I have heard from Asanga that you have completed the implementation.
Congratulations on your good work.
Have you been able to implement options 3 & 4 from section 4 (Protocol
operations):

  Option 3: Source Port - Min, Source Port - Max


  Option 4: Source Port - Min, Source Port - Max, Dst Port - Min, Dst
  Port - Max


To be more precise. Is it possible to define a filter using ports without the
presence of the protocol type.

Thanks in advance
niko


umr at comnets.uni-bremen.de wrote:


    Hello everybody at Monami6,


    I am implementing Flow Management support in nemo-mcoa following the
    draft-soliman-monami6-flow-binding-03 draft. I am using nemo-0.2-mcoa from
    Nautilus as a basis for my implementation. I have succeeded in implementing
a
    basic flow management support in nemo-0.2-mcoa. I will continue sharing my
    experiences in this list.


    One of the issues to report is that in the PRO field in fid mobility option.
It
    is said in the draft that it is a 4 bit field (section 3.1) and hence can
carry
    unsigned integers from 0 to 15. However the draft also says value 255 should
be
    put to PRO field in order to "Remove a flow binding". Since 255 can not be
    accomodated in a 4 bit PRO field I have used 15 (the maximum 4 bit number)
    currently in my implementation and it's working fine.


      Regards,
      Umar Toseef




    ----------------------------------------------------------------




----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Mon Feb 12 10:57:16 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HGdXt-0003Zj-9i; Mon, 12 Feb 2007 10:56:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HGdXr-0003YW-Ox
	for monami6@ietf.org; Mon, 12 Feb 2007 10:56:47 -0500
Received: from mailgw4.ericsson.se ([193.180.251.62])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HGdXg-0004OW-7Q
	for monami6@ietf.org; Mon, 12 Feb 2007 10:56:47 -0500
Received: from mailgw4.ericsson.se (unknown [127.0.0.1])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	457522100C; Mon, 12 Feb 2007 16:56:20 +0100 (CET)
X-AuditID: c1b4fb3e-b06d4bb0000007e1-53-45d08e243629 
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.124])
	by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id
	1EC8E2100B; Mon, 12 Feb 2007 16:56:20 +0100 (CET)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by
	esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 16:56:19 +0100
Received: from [147.214.237.61] ([147.214.237.61]) by
	esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Mon, 12 Feb 2007 16:56:19 +0100
Message-ID: <45D08E23.6090109@levkowetz.com>
Date: Mon, 12 Feb 2007 16:56:19 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>
X-Enigmail-Version: 0.94.1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 12 Feb 2007 15:56:19.0339 (UTC)
	FILETIME=[55C9CDB0:01C74EBE]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: aec2475b197ed9c8908117d8fbf9ee2e
Cc: monami6-chairs@tools.ietf.org
Subject: [Monami6] Review of draft-ietf-monami6-mipv6-analysis-01.txt
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

I've reviewed draft-ietf-monami6-mipv6-analysis-01.txt .  The details
of the review are available below, and also on the web, inlined in the
full document text and colour-coded:
http://tools.ietf.org/rfcmarkup?url=http://levkowetz.com/ietf/reviews/review-ietf-monami6-mipv6-analysis-01.txt&comments=HENRIK

  General: 
    The document gives a comprehensive analysis of multihoming
    in the context of MIPv6, and in this regard, it is fairly complete.
    There are however a lot of editorial work and corner cases which
    I believe need some cleaning up.

  Nits: 
  * I believe it would be easier to read the document if the
    references were either given by name and reference number, or by
    symbolic references: "... RFC 3753 [4] ..." or "... [RFC3753] ..."
  * The language is too often a bit too formal, as if it was part
    of a patent application or legal document.  Less indirect language
    and a less formal style would be good in many places.


  Details:  

INTRODUCTION, paragraph 13:

>    The use of multiple interfaces is foreseen to provide ubiquitous,
>    permanent and fault-tolerant access to the Internet, particularly on
>    mobile nodes which are more prone to failure or sudden lack of
>    connectivity.  However, Mobile IPv6 currently lacks support for such
>    multihomed nodes.  The purpose of this document is to detail all the
>    issues arising through the operation of Mobile IPv6 on multihomed
>    mobile nodes.  A taxonmy is used to describe the different situations
>    where a mobile node is multihomed.  Issues are explained for each
>    multihomed configuration (number of interfaces, number of Home
>    Addresses or number of Care-of Addresses), and classified into
>    general IPv6 issues, issues pertaining to the specification of Mobile
>    IPv6, and issues related to the implementation of Mobile IPv6.  It is
>    not the intention of this document to imply that all issues must be
>    solved in the short term.

  The abstract starts out very abrupt, assuming that the reader already
  knows the context (IP mobility).  It would be better if this was
  established explicitly at the outset.  On the other hand, there
  are too many details at the end of the abstract to easily grasp on
  a once-through read to see if the docment is of interest to one --
  it would be better to cut out some of these details.

  s/taxonmy/taxonomy/


Section 1., paragraph 1:

>    The use of multiple addresses (allocated to either a single interface
>    or multiple interfaces) is foreseen to provide ubiquitous, permanent
>    and fault-tolerant access to the Internet, particularly on mobile
>    nodes which are prone to failure or sudden lack of connectivity.
>    Mobile IPv6 [1],[2] is designed to allow a mobile node to maintain
>    its IPv6 communications while moving between IPv6 subnets.  However,
>    the current specification of Mobile IPv6 lacks support for mobile
>    nodes with multiple addresses used simultaneously, i.e. multihomed
>    mobile nodes.  These addresses would be assigned to a single
>    interface or to multiple interfaces, which poses a number of issues.

  Same initial issue as for the abstract -- there's an assumption
  here about IP mobility which would be better state explicitly.


Section 1., paragraph 2:

>    Individual solutions have been proposed to extend Mobile IPv6 for
>    multihomed mobile nodes, but all issues have not been addressed in a
>    single document.  The purpose of the present document is thus to fill
>    up this gap by listing such issues, raising the discussion at the
>    IETF, and placing some requirements in order to propose comprehensive
>    solutions in forthcoming standards.

  This document doesn't really *address* the issues, as much as
  discuss them.  So it would probably to do s/been addressed in/been
  discussed in/.  Also: s/fill up this gap/fill this gap/.  The part
  about raising discussion within the IETF was relevant at the outset,
  but isn't really as relevant when being published as an RFC, so maybe
  take that out.  Also, with the next paragraph specifying two goals,
  it would probably be better to remove the last part completely,
  from 'The purpose..."


Section 1., paragraph 3:

>    This document has two goals.  The first goal of this document is to
>    define the requirements from the point of view of multihomed mobile
>    nodes operating Mobile IPv6.  The second goal of this document is to
>    define the issues arising when we attempt to fulfill these
>    requirements.  The definition of the potentially needed solutions is
>    out of scope of the analysis document.  These should be defined in a
>    separate document once the IETF community agrees on which issues
>    should be solved.

  s/The first goal of this document/The first goal/ s/The second goal
  of this document/The second goal/ I assume this document *is* the
  analysis document; in that case simply s/the analysis document/this
  document/ .  s/once the IETF community agrees on which issues should
  be solved//


Section 1., paragraph 4:

>    In order to reach the goals of this document, we define a taxonomy
>    which is used to describe the different situations where a mobile
>    node is multihomed.  For each case, we show the configuration a
>    multihomed node may have (number of Home Addresses or number of
>    Care-of Addresses).  We also illustrate each scenario.

  s/(number/(the number/ s/ or/, and the/ s/each scenario./each
  scenario with example diagrams./


Section 1., paragraph 5:

>    To understand the foundation of this document, the reader must read
>    our companion document [3] which outlines the motivations, the goals
>    and the benefits of multihoming for both fixed and mobile nodes (i.e.
>    generic IPv6 nodes).  Real-life scenarios as illustrated in that
>    document are the base motivations of the present study.  The reader
>    must also understand the operation of the Mobile IPv6 protocol ([1]).

  s/must read our/should read the/ s/must also/should also/


Section 1., paragraph 6:

>    The document is organized as follows: in Section 2, we introduce the
>    terminology related to multihoming and used in this document.  In
>    Section 3, we discuss what is required on the mobile nodes to fully
>    benefit from a multihomed configuration.  Then we propose in
>    Section 4 a taxonomy to classify the different cases where mobile
>    nodes are multihomed.  Thereafter the taxonomy is used in Section 5
>    to describe a number of multihomed configuration specific to Mobile
>    IPv6.  Finally we discuss in Section 6 and Section 6.3 all issues
>    related to a multihomed mobile node and we identify what is missing
>    to reach the goals outlined in [3].  These issues are classified into
>    IPv6 issues, Mobile IPv6-specific issues, and advices to
>    implementers.

  s/missing to/missing in order to/


Section 2., paragraph 14:

>       In [3], a node is said to be multihomed when it has multiple IPv6
>       addresses, either because multiple prefixes are advertised on the
>       link(s) the node is attached to, or because the node has multiple
>       interfaces (see the entire definition).  For a mobile node
>       operating MIPv6, this may translate into the following definition:

  s/operating/using/


Section 2., paragraph 15:

>       A MN (as defined above) is said multihomed when it has i) multiple
>       addresses which are used as source address (regardless of HoA/CoA)
>       or ii) multiple tunnels to transmit packets.  A MN may have
>       multiple HoAs/CoAs in the following cases:

  s/has i)/has either i)/ s/as source address/as source addresses/
  s/packets./packets, or both./ It is not obvious what is meant
  by "multiple addresses used as source addresses (regardless
  of HoA/CoA)".  The immediate thought is that ''..multiple source
  addresses would mean either multiple HoA or multiple CoA, so what is
  really meant here... Hmm...''.  Could this be written in a different
  and clearer way?  Or maybe just remove the "(regardless of HoA/CoA)"
  which could be more confusing than helpful?


Section 2., paragraph 21:

>       This indicates a scenario where the MN has the ability to use any
>       of the said multiple addresses at the same time.  This implies
>       that a packet with the destination field set to one of the said
>       multiple addresses will reach the MN, either directly from a CN to
>       the MN or through a tunnel with one of the MN's HAs.  This also
>       implies that any of the said multiple addresses can be used as
>       source address above the MIPv6 layer.

  This paragraph is maybe a bit too formal to be easily read
  and grasped.  Could you eliminate 'said' and re-write in a more
  direct manner?  Also, what do you mean by 'above the MIPv6 layer'?
  Inner tunnel address?  If so, I'm not sure whether this is correct
  in all cases...


Section 2., paragraph 23:

>       This indicates a scenario when there is at least one valid address
>       named for each of the said multiple interfaces, and that the MN is
>       able to simultaneously use these addresses.

  As above, loose the 'said' and re-write more straightforward.


Section 6., paragraph 4:

>    This can translate into the following enumeration of requirements:

  s/can translate/translates/ s/enumeration of
  requirements/requirements/ _or_ s/enumeration of requirements/list
  of potential requirements/

  It is somewhat disturbing that it isn't clear which of the goals
  are associated with the following requirements -- will fulfilment of
  these requirements result in achieving all of the goals?  Will none
  of the goals be fulfilled if a single one of the requirements are not
  fulfilled?  Or ... ??  It might be better to re-write this section as
  a list of capabilities which can be combined to achieve the goals,
  rather than expressing them as _requirements_.  Or alternatively,
  couple each requirement to one or more of the goals, explicitly.


Section 3., paragraph 0:

>    3.  A MN should be able to share its traffic load among its
>        interfaces, when several interfaces are activated and configured
>        with valid addresses.

  s/, when/ when/


Section 6., paragraph 0:

>    6.  If multiple HAs are available, the MN should be able to use
>        multiple HAs simultaneously for a given Home Address.

  Hmm.  Are you talking redundant HAs on the same link here, with
  VRRP switchover or similar, or are you talking multiple HAs in
  separate networks which both announce (BGP) the same prefix, or
  something else?  This should be clearer -- it's hard to be certain
  of what you really mean by 6. currently...


Section 7., paragraph 1:

>    One has to consider whether these goals can be achieved with
>    transparency or without transparency.  Transparency is achieved when
>    switching between interfaces does not cause the disruption of on-
>    going sessions.  To be achieved with transparency, a necessary (may
>    or may not be sufficient) condition is for the end-point addresses at
>    the transport/application layer to remain unchanged.  This is in view
>    of the large amount of Internet traffic currently carried by TCP,
>    which unlike SCTP, cannot handle multiple end-point address pairs.

  Ooops - now it reads as if the requirements above are goals,
  not requirements -- not sure if you mean to refer to 1-6 at the
  beginning of the section, or 1-7 just above. (And it probably would
  be good to use 1-7 and a-g instead...)

  s/To be achieved with transparency/to achieve transparency/
  s/SCTP,/SCTP/


Section 7., paragraph 2:

>    In the future, when a Shim6 protocol [5] is designed and deployed,
>    upper layer transparency may be maintained even if end-point
>    addresses are changed.  However, as Shim6 is in its early design
>    phase as of the writing of this memo, we will continue to assume that
>    an end-point address change would cause a transport layer disruption
>    throughout this document.

  I guess this is correct, but note that from an upper layer
  viewpoint, this is maybe not a particularly enlightening way of
  looking at SHIM6.  From that viewpoint, SHIM6 provides a mobility
  protocol with different characteristics than MIPv6, and both can let
  the upper layers see stable endpoint identifiers even if underlying
  locators change; it's just that it's done with different mechanisms.

  I suggest you remove this paragraph.


Section 4., paragraph 1:

>    In order to examine the issues preventing a MIPv6 mobile node to meet
>    the requirements listed in Section 3 we use in the present document
>    the following taxonomy (x,y) where:

  Here we come to what has been my greatest reservation with this
  taxonomy: This is formally clear and succinct, but a single tuple
  is hard to understand and remember the implications of if you
  haven't recently read this document.  I'd prefer almost any kind
  of alternative notation which made it easier to grasp, without
  remembering the order, which indicator belonged to the HoAs and
  which belong to the CoAs.  Some possibilities:

  (Hx,Cy) - e.g., (H1,Cn), (H*,C1), (H1,C1) hx/cy h1/cN, h*/c1,
  h1/c1 HxCy H1Cn, H*C1, H1C1

  This would make it possible to see from the notation whether it
  was the first or second indicator which belonged to the HoA, etc.
  I don't care particularly exactly which notation is used, as long
  as it is clearly more self-explanatory than (n,1) or (1,*) etc.


Section 4., paragraph 10:

>    Figure 1: Illustration of the Taxonomy

  The exact meaning of the '::=' symbol isn't self-evident.  Maybe use
  words, or add an explanation?


Section 4., paragraph 13:

>    The configurations denoted by these parameters will have an impact on
>    the way multihoming is supported.  According to the number of HoAs
>    and CoAs, different policies will be needed, such as "which CoA has
>    to be mapped with which HoA", "must all the CoAs be mapped with all
>    the HoAs", etc.

  s/According to/Depending on/ s/mapped with/mapped to/g


Section 5.1., paragraph 2:

>    When the node in the same configuration has several interfaces, it
>    may lead to a special situation where a node is connected to both its
>    home link and a foreign link.  The MN is multihomed since it would be
>    able to use both interfaces.  The Home Address might be directly used
>    on the interface which is connected to the home link, and a Care-of
>    Address is configured on the other interface which is connected to a
>    foreign link.  There cannot be more than two interfaces, otherwise
>    the mobile node would either have (A) multiple interfaces on the home
>    link, or (B) multiple interfaces on foreign links.  For (A), there
>    would be multiple HoAs.  For (B) there would be multiple CoAs.  These
>    two cases would fall in another scenario, either (n,*) (see
>    Section 5.2, Section 5.4 and Section 5.5) or (*,n) (see Section 5.3
>    and Section 5.4).

  "There cannot be more than two interfaces, ..." -- This is not
  trivially true.  What is true is that there cannot be more than one
  interface used to connect to the home network, and one interface
  used to establish a CoA.  There can be any number of interfaces
  which are left inactive because of policy decision, user preference
  or MIP software limitations.


Section 5.1., paragraph 3:

>    Achievable goals (when the node has multiple interfaces): Ubiquitous
>    Access, Reliability, Load Sharing, Load Balancing, Aggregated
>    Bandwidth, Preference Settings.

  It's not obvious to me that this statement is correct; I'd for
  instance say that you can't achieve Ubiquitous Access, and only
  limite Reliability.

  Also, in para. 2 above, you have explained how you only cna have
  two interfaces used by the MN simultaneously, and only one at a time
  as HoA and one at a time as CoA.  However, you still say "multiple
  interfaces" here and below.  Either there is something fundamental
  I don't understand here, or you should change this to something else
  (1 HoA, 1 CoA) or qualify "multiple interfaces" in some other manner.


Section 5.1., paragraph 8:

>       Reliability can be achieved through bicasting since the MN has two
>       addresses and should be able to request any CN to duplicate
>       traffic to both of them.  However, MIPv6 does not allow the MN to
>       request bicasting on the CN (see Section 6.2.2).

  s/Reliability can/Reliability could/


Section 5.2., paragraph 1:

>    The MN is multihomed, since it has several HoAs.  This case may
>    happen when a node is getting access to the Internet through
>    different HAs (possibly distinct operators) and each offers a Mobile
>    IPv6 service to the node.  That way, the node will have a HoA per HA.
>    Alternatively, a single home network may be multihomed to the
>    Internet, leading to having multiple prefixes on the home link.  Thus
>    the MN would have multiple HoAs for a single home link.  Either case,
>    the node would need to configure a single CoA on the visited IPv6
>    subnet, and bind that single CoA to all the HoAs it owns.  If the MN
>    has multiple interfaces, only one interface is connected to a foreign
>    network.  The other interfaces are connected to their home links.

  s/ Either case/ In either case/ s/their home links./their home links,
  or are inactive./


Section 5.2., paragraph 2:

>    Achievable goals: Ubiquitous Access, Reliability, Load Sharing, Load
>    Balancing and Aggregated Bandwidth (if the MN has more than one
>    interface) and Preference Settings.

  I'd not say Ubiquietous Access, and I'd say Limited Reliability,
  Limited Load Sharing, Limited Aggregated bandwidth.  There are
  restrictions on each of these, so just saying that they are
  achievable in this configuration is misleading.


Section 5.2., paragraph 10:

>       In Bidirectional Tunnel (BT) mode, preference settings and load
>       sharing only affect the path between the CN and the HA(s), and not
>       the path between the MN and the HA(s), as long as the CoA does not
>       change.  In RO mode, the path between the MN and the CN does not
>       change if the CoA does not change.  As an entry in the binding
>       cache is identified by a HoA, the MN can register the same CoA
>       with all HoAs, on any distant node.  A mechanism would then be
>       needed for the MN to select which HoA should be used when a new
>       communication flow is initiated.  A similar mechanism is needed on
>       the CN side if it knows that multiple HoAs are assigned to the
>       same MN.  With such mechanisms, it would be possible to use
>       multiple HoAs at the same time, and load sharing could be
>       performed.  See in Section 6.1.1 where such path selection issues
>       are discussed.  It is also possible that the MN register one HoA
>       as a CoA for another HoA (see discussions in Section 6.3.1).

  Since it is likely in many (most?) scenarios of practical interest
  that it is the first hop from CoA towards HA which is most bandwidth
  constrained, this load sharing may be of limited value or interest.
  You probably should mention something about this.


Section 5.2., paragraph 11:

>    o  Load Balancing and Aggregated Bandwidth
>       Load balancing and aggregated bandwidth are achievable when the MN
>       has several interfaces.  In this case, the MN is attached to one
>       foreign link via one of its interfaces, and it is attached to home
>       link(s) with its other interface(s).  In this case, the MN can
>       spread flows over its interfaces.  Note that if a CN initiates a
>       communication, the interface that it will use on the MN would
>       depend on the information it has about this MN.

  As above, this load balancing and bandwidth aggregation may be of
  limited value or interest, and you probably should mention something
  about this, too.


Section 5.3., paragraph 1:

>    The MN is multihomed since it has several CoAs.  This case may for
>    instance occur when the interface of the node is connected to a link
>    where multiple IPv6 prefixes are available.  One possible reason for
>    this is that the visited network is multihomed and because of that,
>    multiple prefixes are available in it, one per provider.  Note that
>    one of the interfaces of the MN may be connected to its home link.

  I'm surprised that you mention the (at least to me) less interesting
  scenario of multiple CoAs on the same link, and don't mention the
  more interesting scenario of multiple independent interfaces who
  are not on the same link.  Fix?


Section 5.3., paragraph 2:

>    Achievable goals: Reliability, Load Sharing, Preference Settings,
>    Load Balancing and Aggregated Bandwidth (if the MN is equipped with
>    several interfaces)

  I'd split this in one CoA interface vs. multiple CoA interfaces.
  The extent to which the goals can be achieved differ between these
  cases.  In particular, in the case where you don't have any interface
  connected to the home network, the conclusion for all of the goals
  differ between the one-interface and the multi-interface case.


Section 5.3., paragraph 4:

>    o  Ubiquitous Access, Reliabiility

  s/Reliabiility/Reliability/


Section 5.5., paragraph 4:

>    Current situation with MIPv6

  The discussion here feels strange to me - I don't see how this case
  differs from any other non-mobility multihoming case, as long as
  you're in n HoA, 0 CoA situation.  I'd prefer to simply say so,
  OR if there is any point on which this situation differs from that
  case, specifically point out such points, rather than keep to the
  format of the previous 5.x sections...


Section 6.1.1., paragraph 7:

>       This choice would be made at the time of a new communication flow
>       set up.  Usual IPv6 mechanisms for source and destination address
>       selection, such as "Default Address Selection for IPv6" [7] could
>       be used.

  Possibly you should also mention the use of DNS SRV records, and
  which address(es) to announce for the DNS A / AAAA records.


Section 6.1.1., paragraph 10:

>       When multiple CoAs are available, the MN and its communicating
>       peers (HA and CNs) must be able to select the appropriate CoA to
>       be used for a particular packet or flow.  The MN may use its
>       internal policies to (i) distribute its flow, and (ii) distribute
>       policies on distant nodes to allow them to select the preferred
>       CoA.  Solutions like flow binding [6] may be used.

  Humm.  How/when would *ever* a CN *choose* a CoA (as opposed to
  a HoA, which might result in RO to a CoA chosen by the MN) to
  communicate with?  If this statement is correct, some more text,
  maybe an example, would be good.


Section 6.1.1., paragraph 11:

>    Another related aspect of path selection is the concern of ingress
>    filtering.  This is detailed in Section 6.1.2.

  s/detailed/covered below/


Section 2, paragraph 0:

>    Currently, IPv6 has not clearly defined mechanism for failure
>    detection.  A failure in the path between two nodes can be located at
>    many different places: the media of one of the node is broken (i.e.,
>    loss of connectivity), the path between the MN and the HA is broken,
>    the home link is disconnected from the Internet, etc.  By now, MIPv6
>    only relies on the ability or the inability to receive Router
>    Advertisements within a stipulated period to detect the availibility
>    or loss of media (local failure).  Current effort [11] in the DNA
>    Working Group aims to address this, such as through the use of layer
>    2 triggers [12].  Movement detection might be extended to include
>    other triggers such as the loss of connectivity on one interface.
>    Further mechanisms would be needed to detect a failure in the path
>    between a MN and its CN(s), as well as between the MN and its HA(s),
>    between the MN and CN(s), or between the HA and CN(s).

  s/availibility/availability/


Section 6.2.1., paragraph 3:

>    To counter this issue, solutions like [13] may be used.

  This would be more readable if you would give the title, draft name,
  or other indication of what you're referring to...


Section 6.2.2., paragraph 1:

>    Rule 4 of RFC3484 specifies that a HoA will always be preferred to a
>    CoA.  While this rule allows to choose which address to use, it does
>    not allow MN to benefit from being multihomed in some cases.  When a
>    MN is multihomed, it may have one of its interfaces directly
>    connected to a home link.  This may have an impact on the way
>    multihoming is managed, since addresses from other interfaces cannot
>    be registered as CoAs for the HoA associated to the home link the
>    mobile node is connected on.

  s/allows to choose/allows the host to choose/ s/allow MN to
  benefit/allow the MN to benefit/


Section 6.3.1., paragraph 5:

>    In order to benefit from any multihoming configuration, a MN must be
>    able to register whatever address it owns with any of its HoA, as
>    long as the above statement is verified.

  s/verified/observed/


Section 6.3.2., paragraph 2:

>    With no such mechanism, the MN may be confused and may bind this CoA
>    to a possibly wrong HoA.  The result might be to bind the CoA to the
>    same HoA the previous CoA was bound to or to another one, depending
>    on the implementation.  It would indeed be better to specify the
>    behavior so that all implementations are compliant.

  It's not obvious to me how an HA can be 'wrong' in this respect.
  Surely, it would be possible, when aquiring a new CoA, to bind it
  to all of the HAs, (except possibly HAs on the same link as the CoA)?


Section 6.3.4., paragraph 1:

>    Internet connectivity is guaranteed for a MN as long as at least one
>    path is maintained between the MN and its CN.  When an alternative
>    path must be found to substitute for another one, the loss of one
>    path to the Internet may result in broken sessions.  In this case,
>    new transport sessions would have to be established over the
>    alternate path if no mechanism is provided to redirect flow
>    transparently at layers above layer 3.  The need for flow redirection
>    is given in Appendix A.

  Unclear language: "when an alternative path must be found to
  substitute for another one, ..."

  I'm not sure what you mean to say here.


Section 6.3.4., paragraph 3:

>    The second category is when the HoA changes: if one of the MN's HoA
>    needs to be changed, it influences the path between the CN and the
>    HoA.  In (n,*) cases, the MN has multiple HoAs.  If one fails,
>    established sessions on the failed HoA would break if no support
>    mechanism is used to redirect flows from a failed HoA to another,
>    unless the transport session has multihoming capabilities, such as
>    SCTP, to allow dynamic changing of addresses used.

  Again, it is not easy to understand what is meant here.  I think
  one of the problem is when you say 'needs to be changed', without
  qualifying with _where_ or _in which respect_ the need for change
  exists.


Section 7., paragraph 3:

>    Mention about relation with Shim6.

  This could be important, yes.

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Feb 15 22:06:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHtPv-00050C-9Q; Thu, 15 Feb 2007 22:05:47 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHtPt-0004qH-KM; Thu, 15 Feb 2007 22:05:45 -0500
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HHtPr-0006fF-VA; Thu, 15 Feb 2007 22:05:45 -0500
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/kings) with ESMTP id
	l1G35gqO026759; Fri, 16 Feb 2007 12:05:42 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx3) with ESMTP id
	l1G35hT18528; Fri, 16 Feb 2007 12:05:43 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/redsox) with ESMTP id
	l1G35f706090; Fri, 16 Feb 2007 12:05:42 +0900 (JST)
Received: from Sephiroth ([10.81.113.103]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Fri, 16 Feb 2007 11:05:40 +0800
From: "Benjamin Lim" <benjamin.limck@sg.panasonic.com>
To: <int-area@ietf.org>
References: <45D307BE.4060903@piuha.net>
In-Reply-To: <45D307BE.4060903@piuha.net>
Date: Fri, 16 Feb 2007 11:05:33 +0800
Organization: Panasonic Singapore Laboratories Pte Ltd
Message-ID: <00be01c75177$52aebd50$f80c37f0$@limck@sg.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcdQOEB7yFyx3cbiQJ20oJdfFjTo/gBOhQWA
Content-Language: en-us
X-OriginalArrivalTime: 16 Feb 2007 03:05:40.0911 (UTC)
	FILETIME=[57309BF0:01C75177]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976
Cc: 'Monami6 WG' <monami6@ietf.org>
Subject: [Monami6] RE: [Int-area] Lifting up a filter discussion from Monami6
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: benjamin.limck@sg.panasonic.com, Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

Since Jari brought up this discussion, I would like to put forth an issue
about interworking Monami6 with NEMO. In Monami6, a mobile node knows the
traffic condition over its multiple links. Thus, the mobile node is able to
inform its home agent how to route the flow to the mobile node (through the
various filter rules setting methods proposed in the WG).

The mobile node now associates with a mobile router with multiple egress
paths (roaming into NEMO). However, the mobile node has no way of knowing
the existence of multiple paths (and their network characteristics) to
continue on with flow filtering. On the other hand, the mobile router cannot
perform efficient flow filtering since the mobile router has no way to know
the traffic requirements of the mobile node's flow. 

The fact is that the tunnel ends at the mobile router whereas the traffic
ends at mobile node cause such a problem with flow filtering. 

Any thoughts on how such issue can be solved?

Regards,
Benjamin Lim

> -----Original Message-----
> From: Jari Arkko [mailto:jari.arkko@piuha.net]
> Sent: Wednesday, February 14, 2007 9:00 PM
> To: Internet Area
> Cc: monami6-chairs@tools.ietf.org
> Subject: [Int-area] Lifting up a filter discussion from Monami6
> 
> 
> I would like to lift up one issue from the Monami6 WG
> to a more general discussion. Monami6 is developing an
> extension to Mobile IPv6 / Nemo so that a mobile node could
> register its presence in multiple locations simultaneously.
> One of things that they expect to be able to do is to control
> what traffic goes to what care-of address; this flow to this
> address, and the other flow to that other address. Mobile nodes
> can obviously decide by themselves what outgoing interface to use.
> However, in order for a home agent to deal with return traffic
> properly, the mobile node has to tell it what policy to
> employ.
> 
> The working group has debated between a number of different
> approaches for doing this. In one approach, draft-soliman-
> monami6-flow-binding the mobile node adds a filter to a Mobile
> IPv6 Binding Update to tell what traffic should use this binding.
> Another approach, draft-larsson-monami6-filter-rules, decouples
> the policy exchange from the mobility protocol. The policies are
> exchanged at a different time (typically earlier) and carried by a
> different protocol (in this case over UDP). Yet another draft,
> draft-mitsuya-monami6-flow-distribution-policy also separates
> the mobility protocol and policy transfer, and carries
> the policies in HTTP.
> 
> Monami6 should of course decide how they want to design this.
> But this may be an interesting debate from a more generic point
> of view. Do we have input for them? For instance, are there needs
> in HIP/Shim6/Mobike space for similar functionality? Should the
> designs be tailored for each of these situations? Is there some
> advantage or disadvantage in looking at a generic solution?
> Would a generic solution be doable?
> 
> Without going into too much detail about the specific proposals
> it seems that there are actually a number of different topics here:
> - carrier protocol choice
> - policy container format
> - timing of the policy exchange
> - securing the transfer
> - etc
> 
> Thoughts?
> 
> Jari
> 
> _______________________________________________
> Int-area mailing list
> Int-area@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/int-area



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Feb 16 00:10:58 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHvMy-0000ZV-BN; Fri, 16 Feb 2007 00:10:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HHvMw-0000Wi-P0; Fri, 16 Feb 2007 00:10:50 -0500
Received: from av12-1-sn2.hy.skanova.net ([81.228.8.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HHvMu-0004n4-Kg; Fri, 16 Feb 2007 00:10:50 -0500
Received: by av12-1-sn2.hy.skanova.net (Postfix, from userid 502)
	id 8C9D7384EA; Fri, 16 Feb 2007 06:10:43 +0100 (CET)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92]) by av12-1-sn2.hy.skanova.net (Postfix) with ESMTP
	id 6E38F38026; Fri, 16 Feb 2007 06:10:43 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id 0ACA037E48;
	Fri, 16 Feb 2007 06:10:41 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1HHvMm-0005BK-V4; Fri, 16 Feb 2007 06:10:41 +0100
Message-ID: <45D53CCF.5010607@levkowetz.com>
Date: Fri, 16 Feb 2007 06:10:39 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: benjamin.limck@sg.panasonic.com, Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] RE: [Int-area] Lifting up a filter discussion from
	Monami6
References: <45D307BE.4060903@piuha.net>
	<00be01c75177$52aebd50$f80c37f0$@limck@sg.panasonic.com>
In-Reply-To: <00be01c75177$52aebd50$f80c37f0$@limck@sg.panasonic.com>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: benjamin.limck@sg.panasonic.com, monami6@ietf.org,
	int-area@ietf.org, henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: int-area@ietf.org
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Benjamin,

on 2007-02-16 04:05 Benjamin Lim said the following:
> Hi,
> 
> Since Jari brought up this discussion, I would like to put forth an issue
> about interworking Monami6 with NEMO. In Monami6, a mobile node knows the
> traffic condition over its multiple links. Thus, the mobile node is able to
> inform its home agent how to route the flow to the mobile node (through the
> various filter rules setting methods proposed in the WG).
> 
> The mobile node now associates with a mobile router with multiple egress
> paths (roaming into NEMO). However, the mobile node has no way of knowing
> the existence of multiple paths (and their network characteristics) to
> continue on with flow filtering. On the other hand, the mobile router cannot
> perform efficient flow filtering since the mobile router has no way to know
> the traffic requirements of the mobile node's flow. 
> 
> The fact is that the tunnel ends at the mobile router whereas the traffic
> ends at mobile node cause such a problem with flow filtering. 
> 
> Any thoughts on how such issue can be solved?

While the proposals discussed in monami6 so far has been geared to transfer
of filter rules, this seems to call for transfer not of filter rules, but
of a subset of policy declarations (some sort of preferences for quality
and cost of service) between the Mobile Router and the Node attaching to the
Mobile Network (the MNN).

I think that as a general problem, this may be less well understood, and
possibly more complex, than expressing filter rules.  The filter rules I
see needed by for instance monami6 appear to be a subset of filter rules
that can be expressed for firewalls today, using well-defined languages; but
I'm not aware of mature languages for expressing cost/latency/bandwidth/
/reliability/security/etc. preferences, and how to weigh them against each
other.

I know that some work has been done in SHIM6 on expressing and communicating
policy, but don't know that work well enough to know whether it would be
applicable to this case.


	Henrik

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Feb 16 09:28:08 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI43p-0000Dh-HQ; Fri, 16 Feb 2007 09:27:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI43n-00008s-M2; Fri, 16 Feb 2007 09:27:39 -0500
Received: from concorde.inria.fr ([192.93.2.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HI43j-0003ES-7V; Fri, 16 Feb 2007 09:27:39 -0500
Received: from dhcp-rocq-244.inria.fr (dhcp-rocq-244.inria.fr [128.93.62.244])
	by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id l1GERVa1002977
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 16 Feb 2007 15:27:32 +0100
Date: Fri, 16 Feb 2007 15:27:51 +0100
From: Thierry Ernst <thierry.ernst@inria.fr>
To: Monami6 WG <monami6@ietf.org>
Subject: Re: [Monami6] RE: [Int-area] Lifting up a filter discussion from
	Monami6
Message-Id: <20070216152751.ec384ad0.thierry.ernst@inria.fr>
In-Reply-To: <45D53CCF.5010607@levkowetz.com>
References: <45D307BE.4060903@piuha.net>
	<00be01c75177$52aebd50$f80c37f0$@limck@sg.panasonic.com>
	<45D53CCF.5010607@levkowetz.com>
Organization: INRIA
X-Mailer: Sylpheed version 2.2.3 (GTK+ 2.10.6; powerpc-apple-darwin8.8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Miltered: at concorde with ID 45D5BF53.000 by Joe's j-chkmail
	(http://j-chkmail . ensmp . fr)!
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
Cc: int-area@ietf.org, henrik@levkowetz.com
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


Hi,

Do we need to keep ccing int-area (at the same time of Monami6) ?

The term "Mobile Node" is missleading. What Benjamin is talking about
is a Mobile Network Node (MNN).

So, the issue raised by Benjamin is known for a long time, even before
the set up of Monami6. The issue is discussed in
http://www.ietf.org/internet-drafts/draft-ietf-nemo-multihoming-issues-07.txt
section 4.10, and the conclusion (section 5 same draft) is that the
issue is not specific to mobility at all (but is more important to be
solved in mobility scenarios). This is why it is not brought up to the attention of the Monami6 working group. 

However, since it is more important to be solved for Monami6 use case,
we could contemplate to solve it within Monami6, if interest arises. Of
course, the solution should not be specific to mobility since the
mobility protocol doesn't intervene between MR and MNN.

This issue is also worked out by the automotive industry, within ISO
TC204 WG16 (they have their own solution using SNMPv3).

Thierry.




On Fri, 16 Feb 2007 06:10:39 +0100
Henrik Levkowetz <henrik@levkowetz.com> wrote:

>Hi Benjamin,
>
>on 2007-02-16 04:05 Benjamin Lim said the following:
>> Hi,
>> 
>> Since Jari brought up this discussion, I would like to put forth an issue
>> about interworking Monami6 with NEMO. In Monami6, a mobile node knows the
>> traffic condition over its multiple links. Thus, the mobile node is able to
>> inform its home agent how to route the flow to the mobile node (through the
>> various filter rules setting methods proposed in the WG).
>> 
>> The mobile node now associates with a mobile router with multiple egress
>> paths (roaming into NEMO). However, the mobile node has no way of knowing
>> the existence of multiple paths (and their network characteristics) to
>> continue on with flow filtering. On the other hand, the mobile router cannot
>> perform efficient flow filtering since the mobile router has no way to know
>> the traffic requirements of the mobile node's flow. 
>> 
>> The fact is that the tunnel ends at the mobile router whereas the traffic
>> ends at mobile node cause such a problem with flow filtering. 
>> 
>> Any thoughts on how such issue can be solved?
>
>While the proposals discussed in monami6 so far has been geared to transfer
>of filter rules, this seems to call for transfer not of filter rules, but
>of a subset of policy declarations (some sort of preferences for quality
>and cost of service) between the Mobile Router and the Node attaching to the
>Mobile Network (the MNN).
>
>I think that as a general problem, this may be less well understood, and
>possibly more complex, than expressing filter rules.  The filter rules I
>see needed by for instance monami6 appear to be a subset of filter rules
>that can be expressed for firewalls today, using well-defined languages; but
>I'm not aware of mature languages for expressing cost/latency/bandwidth/
>/reliability/security/etc. preferences, and how to weigh them against each
>other.
>
>I know that some work has been done in SHIM6 on expressing and communicating
>policy, but don't know that work well enough to know whether it would be
>applicable to this case.
>
>
>	Henrik
>
>_______________________________________________
>Monami6 mailing list
>Monami6@ietf.org
>https://www1.ietf.org/mailman/listinfo/monami6
>


-- 
Thierry ERNST, PhD 
INRIA Rocquencourt France Project-Team IMARA / JRU LARA
http://www.lara.prd.fr +33 1 39 63 59 30 (office)


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Feb 16 10:17:20 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI4pX-00010U-4m; Fri, 16 Feb 2007 10:16:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI4pV-00010G-NO; Fri, 16 Feb 2007 10:16:57 -0500
Received: from av8-1-sn3.vrr.skanova.net ([81.228.9.183])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HI4pT-000760-5o; Fri, 16 Feb 2007 10:16:57 -0500
Received: by av8-1-sn3.vrr.skanova.net (Postfix, from userid 502)
	id 5650637F13; Fri, 16 Feb 2007 16:16:52 +0100 (CET)
Received: from smtp3-1-sn3.vrr.skanova.net (smtp3-1-sn3.vrr.skanova.net
	[81.228.9.101]) by av8-1-sn3.vrr.skanova.net (Postfix) with ESMTP
	id 3B2FB37E53; Fri, 16 Feb 2007 16:16:52 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp3-1-sn3.vrr.skanova.net (Postfix) with ESMTP id 78F1037E42;
	Fri, 16 Feb 2007 16:16:50 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1HI4pN-0005Ie-Ny; Fri, 16 Feb 2007 16:16:49 +0100
Message-ID: <45D5CAE0.4070809@levkowetz.com>
Date: Fri, 16 Feb 2007 16:16:48 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: Thierry Ernst <thierry.ernst@inria.fr>
Subject: Re: [Monami6] RE: [Int-area] Lifting up a filter discussion from
	Monami6
References: <45D307BE.4060903@piuha.net>	<00be01c75177$52aebd50$f80c37f0$@limck@sg.panasonic.com>	<45D53CCF.5010607@levkowetz.com>
	<20070216152751.ec384ad0.thierry.ernst@inria.fr>
In-Reply-To: <20070216152751.ec384ad0.thierry.ernst@inria.fr>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: thierry.ernst@inria.fr, monami6@ietf.org,
	benjamin.limck@sg.panasonic.com, int-area@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4
Cc: int-area@ietf.org, Monami6 WG <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Thierry,

Since you're top posting, I'm not sure if you're responding to
Benjamin or me.

on 2007-02-16 15:27 Thierry Ernst said the following:
> Hi,
> 
> Do we need to keep ccing int-area (at the same time of Monami6) ?

Depends on how general the issue is, I guess.

> The term "Mobile Node" is missleading. What Benjamin is talking about
> is a Mobile Network Node (MNN).

Yes, and so am I, using that exact term, if you look again at my response
to Benjamin.

> So, the issue raised by Benjamin is known for a long time, even before
> the set up of Monami6. The issue is discussed in
> http://www.ietf.org/internet-drafts/draft-ietf-nemo-multihoming-issues-07.txt
> section 4.10, and the conclusion (section 5 same draft) is that the
> issue is not specific to mobility at all (but is more important to be
> solved in mobility scenarios). This is why it is not brought up to the
> attention of the Monami6 working group. 

Yes, it's covered in 4.10 of this document, to about the same level of
details as done in this thread so far.  However, the distinction between
filter rules and policies/preferences, which I believe is important in
this context, isn't covered there.

> However, since it is more important to be solved for Monami6 use case,
> we could contemplate to solve it within Monami6, if interest arises. Of
> course, the solution should not be specific to mobility since the
> mobility protocol doesn't intervene between MR and MNN.
> 
> This issue is also worked out by the automotive industry, within ISO
> TC204 WG16 (they have their own solution using SNMPv3).

Do you have more details about this, maybe a pointer to available documents?


	Henrik



> Thierry.
> 
> 
> 
> 
> On Fri, 16 Feb 2007 06:10:39 +0100
> Henrik Levkowetz <henrik@levkowetz.com> wrote:
> 
>>Hi Benjamin,
>>
>>on 2007-02-16 04:05 Benjamin Lim said the following:
>>> Hi,
>>> 
>>> Since Jari brought up this discussion, I would like to put forth an issue
>>> about interworking Monami6 with NEMO. In Monami6, a mobile node knows the
>>> traffic condition over its multiple links. Thus, the mobile node is able to
>>> inform its home agent how to route the flow to the mobile node (through the
>>> various filter rules setting methods proposed in the WG).
>>> 
>>> The mobile node now associates with a mobile router with multiple egress
>>> paths (roaming into NEMO). However, the mobile node has no way of knowing
>>> the existence of multiple paths (and their network characteristics) to
>>> continue on with flow filtering. On the other hand, the mobile router cannot
>>> perform efficient flow filtering since the mobile router has no way to know
>>> the traffic requirements of the mobile node's flow. 
>>> 
>>> The fact is that the tunnel ends at the mobile router whereas the traffic
>>> ends at mobile node cause such a problem with flow filtering. 
>>> 
>>> Any thoughts on how such issue can be solved?
>>
>>While the proposals discussed in monami6 so far has been geared to transfer
>>of filter rules, this seems to call for transfer not of filter rules, but
>>of a subset of policy declarations (some sort of preferences for quality
>>and cost of service) between the Mobile Router and the Node attaching to the
>>Mobile Network (the MNN).
>>
>>I think that as a general problem, this may be less well understood, and
>>possibly more complex, than expressing filter rules.  The filter rules I
>>see needed by for instance monami6 appear to be a subset of filter rules
>>that can be expressed for firewalls today, using well-defined languages; but
>>I'm not aware of mature languages for expressing cost/latency/bandwidth/
>>/reliability/security/etc. preferences, and how to weigh them against each
>>other.
>>
>>I know that some work has been done in SHIM6 on expressing and communicating
>>policy, but don't know that work well enough to know whether it would be
>>applicable to this case.
>>
>>
>>	Henrik
>>
>>_______________________________________________
>>Monami6 mailing list
>>Monami6@ietf.org
>>https://www1.ietf.org/mailman/listinfo/monami6
>>
> 
> 

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Feb 16 11:30:45 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI5yU-0005jI-Aa; Fri, 16 Feb 2007 11:30:18 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI5yS-0005it-PJ; Fri, 16 Feb 2007 11:30:16 -0500
Received: from concorde.inria.fr ([192.93.2.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HI5yO-0004Xj-9F; Fri, 16 Feb 2007 11:30:16 -0500
Received: from dhcp-rocq-244.inria.fr (dhcp-rocq-244.inria.fr [128.93.62.244])
	by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id l1GGU4uX007785
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Fri, 16 Feb 2007 17:30:05 +0100
Date: Fri, 16 Feb 2007 17:30:25 +0100
From: Thierry Ernst <thierry.ernst@inria.fr>
To: ml-ietf-monami6 <monami6@ietf.org>, int-area@ietf.org
Subject: Re: [Monami6] RE: [Int-area] Lifting up a filter discussion from
	Monami6
Message-Id: <20070216173025.43c16d96.thierry.ernst@inria.fr>
In-Reply-To: <45D5CAE0.4070809@levkowetz.com>
References: <45D307BE.4060903@piuha.net>
	<00be01c75177$52aebd50$f80c37f0$@limck@sg.panasonic.com>
	<45D53CCF.5010607@levkowetz.com>
	<20070216152751.ec384ad0.thierry.ernst@inria.fr>
	<45D5CAE0.4070809@levkowetz.com>
Organization: INRIA
X-Mailer: Sylpheed version 2.2.3 (GTK+ 2.10.6; powerpc-apple-darwin8.8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Miltered: at concorde with ID 45D5DC0C.001 by Joe's j-chkmail
	(http://j-chkmail . ensmp . fr)!
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: 
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org



>Since you're top posting, I'm not sure if you're responding to
>Benjamin or me.

Actually, I was replying to Benjamin, but replying back using the last
mail on the thread ;-)

>on 2007-02-16 15:27 Thierry Ernst said the following:
>> Hi,
>> 
>> Do we need to keep ccing int-area (at the same time of Monami6) ?
>
>Depends on how general the issue is, I guess.
>
>> The term "Mobile Node" is missleading. What Benjamin is talking about
>> is a Mobile Network Node (MNN).
>
>Yes, and so am I, using that exact term, if you look again at my response
>to Benjamin.
>
>> So, the issue raised by Benjamin is known for a long time, even before
>> the set up of Monami6. The issue is discussed in
>> http://www.ietf.org/internet-drafts/draft-ietf-nemo-multihoming-issues-07.txt
>> section 4.10, and the conclusion (section 5 same draft) is that the
>> issue is not specific to mobility at all (but is more important to be
>> solved in mobility scenarios). This is why it is not brought up to the
>> attention of the Monami6 working group. 
>
>Yes, it's covered in 4.10 of this document, to about the same level of
>details as done in this thread so far.  However, the distinction between
>filter rules and policies/preferences, which I believe is important in
>this context, isn't covered there.

I don't know how important the distinction is, and so far I've only
heard and dealt with policies and preferences. They could be probably
be specified in whatever language (including proprietary) as long as
there is a transport to convey them between the two nodes. How this is
used at the MR is all internal and is not of interest from an IETF
standardization point of view. 

>> However, since it is more important to be solved for Monami6 use case,
>> we could contemplate to solve it within Monami6, if interest arises. Of
>> course, the solution should not be specific to mobility since the
>> mobility protocol doesn't intervene between MR and MNN.
>> 
>> This issue is also worked out by the automotive industry, within ISO
>> TC204 WG16 (they have their own solution using SNMPv3).
>
>Do you have more details about this, maybe a pointer to available documents?

Nop, the documents are not public. But here is their public website:
http://www.calm.hu/

Thierry.


>>>Hi Benjamin,
>>>
>>>on 2007-02-16 04:05 Benjamin Lim said the following:
>>>> Hi,
>>>> 
>>>> Since Jari brought up this discussion, I would like to put forth an issue
>>>> about interworking Monami6 with NEMO. In Monami6, a mobile node knows the
>>>> traffic condition over its multiple links. Thus, the mobile node is able to
>>>> inform its home agent how to route the flow to the mobile node (through the
>>>> various filter rules setting methods proposed in the WG).
>>>> 
>>>> The mobile node now associates with a mobile router with multiple egress
>>>> paths (roaming into NEMO). However, the mobile node has no way of knowing
>>>> the existence of multiple paths (and their network characteristics) to
>>>> continue on with flow filtering. On the other hand, the mobile router cannot
>>>> perform efficient flow filtering since the mobile router has no way to know
>>>> the traffic requirements of the mobile node's flow. 
>>>> 
>>>> The fact is that the tunnel ends at the mobile router whereas the traffic
>>>> ends at mobile node cause such a problem with flow filtering. 
>>>> 
>>>> Any thoughts on how such issue can be solved?
>>>
>>>While the proposals discussed in monami6 so far has been geared to transfer
>>>of filter rules, this seems to call for transfer not of filter rules, but
>>>of a subset of policy declarations (some sort of preferences for quality
>>>and cost of service) between the Mobile Router and the Node attaching to the
>>>Mobile Network (the MNN).
>>>
>>>I think that as a general problem, this may be less well understood, and
>>>possibly more complex, than expressing filter rules.  The filter rules I
>>>see needed by for instance monami6 appear to be a subset of filter rules
>>>that can be expressed for firewalls today, using well-defined languages; but
>>>I'm not aware of mature languages for expressing cost/latency/bandwidth/
>>>/reliability/security/etc. preferences, and how to weigh them against each
>>>other.
>>>
>>>I know that some work has been done in SHIM6 on expressing and communicating
>>>policy, but don't know that work well enough to know whether it would be
>>>applicable to this case.
>>>
>>>
>>>	Henrik
>>>
>>>_______________________________________________
>>>Monami6 mailing list
>>>Monami6@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/monami6
>>>
>> 
>> 
>


-- 
Thierry ERNST, PhD 
INRIA Rocquencourt France Project-Team IMARA / JRU LARA
http://www.lara.prd.fr +33 1 39 63 59 30 (office)


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Fri Feb 16 14:14:25 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI8Wm-0005ED-Rl; Fri, 16 Feb 2007 14:13:52 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HI8Wl-0005E0-9p; Fri, 16 Feb 2007 14:13:51 -0500
Received: from av11-2-sn2.hy.skanova.net ([81.228.8.184])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HI8Wg-00058K-Vo; Fri, 16 Feb 2007 14:13:51 -0500
Received: by av11-2-sn2.hy.skanova.net (Postfix, from userid 502)
	id 58B5C37F74; Fri, 16 Feb 2007 20:13:46 +0100 (CET)
Received: from smtp4-1-sn2.hy.skanova.net (smtp4-1-sn2.hy.skanova.net
	[81.228.8.92]) by av11-2-sn2.hy.skanova.net (Postfix) with ESMTP
	id 0E07737F23; Fri, 16 Feb 2007 20:13:43 +0100 (CET)
Received: from shiraz.levkowetz.com (81-232-110-214-no16.tbcn.telia.com
	[81.232.110.214])
	by smtp4-1-sn2.hy.skanova.net (Postfix) with ESMTP id DE31337E42;
	Fri, 16 Feb 2007 20:13:43 +0100 (CET)
Received: from localhost ([127.0.0.1])
	by shiraz.levkowetz.com with esmtp (Exim 4.63)
	(envelope-from <henrik@levkowetz.com>)
	id 1HI8Wc-00059d-VV; Fri, 16 Feb 2007 20:13:43 +0100
Message-ID: <45D60266.80606@levkowetz.com>
Date: Fri, 16 Feb 2007 20:13:42 +0100
From: Henrik Levkowetz <henrik@levkowetz.com>
User-Agent: Thunderbird 1.5.0.9 (Macintosh/20061207)
MIME-Version: 1.0
To: Thierry Ernst <thierry.ernst@inria.fr>
Subject: Re: [Monami6] RE: [Int-area] Lifting up a filter discussion from
	Monami6
References: <45D307BE.4060903@piuha.net>	<00be01c75177$52aebd50$f80c37f0$@limck@sg.panasonic.com>	<45D53CCF.5010607@levkowetz.com>	<20070216152751.ec384ad0.thierry.ernst@inria.fr>	<45D5CAE0.4070809@levkowetz.com>
	<20070216173025.43c16d96.thierry.ernst@inria.fr>
In-Reply-To: <20070216173025.43c16d96.thierry.ernst@inria.fr>
X-Enigmail-Version: 0.94.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: thierry.ernst@inria.fr, monami6@ietf.org, int-area@ietf.org,
	henrik-sent@levkowetz.com
X-SA-Exim-Mail-From: henrik@levkowetz.com
X-SA-Exim-Scanned: No (on shiraz.levkowetz.com);
	SAEximRunCond expanded to false
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: int-area@ietf.org, ml-ietf-monami6 <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Thierry,

on 2007-02-16 17:30 Thierry Ernst said the following:
> 
>>Since you're top posting, I'm not sure if you're responding to
>>Benjamin or me.
> 
> Actually, I was replying to Benjamin, but replying back using the last
> mail on the thread ;-)

Ah. Ok.

...
>>> This issue is also worked out by the automotive industry, within ISO
>>> TC204 WG16 (they have their own solution using SNMPv3).
>>
>>Do you have more details about this, maybe a pointer to available documents?
> 
> Nop, the documents are not public. But here is their public website:
> http://www.calm.hu/

Ok, thanks!  It does indeed look as if they are considering distribution
of preference policies within the system, but it doesn't look as if the
architecture requires a standardized protocol for transfer of preferences.
Hard to tell for certain, though, based on the information available on
the website.


	Henrik


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Mon Feb 19 06:51:19 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJ72j-0005gN-FR; Mon, 19 Feb 2007 06:50:53 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJ72h-0005g1-Ju; Mon, 19 Feb 2007 06:50:51 -0500
Received: from discorde.inria.fr ([192.93.2.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HJ72d-0003H8-7B; Mon, 19 Feb 2007 06:50:51 -0500
Received: from dhcp-rocq-244.inria.fr (dhcp-rocq-244.inria.fr [128.93.62.244])
	by discorde.inria.fr (8.13.6/8.13.6) with ESMTP id l1JBofKH016542
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Mon, 19 Feb 2007 12:50:42 +0100
Date: Mon, 19 Feb 2007 12:50:43 +0100
From: Thierry Ernst <thierry.ernst@inria.fr>
To: Henrik Levkowetz <henrik@levkowetz.com>
Subject: Re: [Monami6] RE: [Int-area] Lifting up a filter discussion from
	Monami6
Message-Id: <20070219125043.4be7a77c.thierry.ernst@inria.fr>
In-Reply-To: <45D60266.80606@levkowetz.com>
References: <45D307BE.4060903@piuha.net>
	<00be01c75177$52aebd50$f80c37f0$@limck@sg.panasonic.com>
	<45D53CCF.5010607@levkowetz.com>
	<20070216152751.ec384ad0.thierry.ernst@inria.fr>
	<45D5CAE0.4070809@levkowetz.com>
	<20070216173025.43c16d96.thierry.ernst@inria.fr>
	<45D60266.80606@levkowetz.com>
Organization: INRIA
X-Mailer: Sylpheed version 2.2.3 (GTK+ 2.10.6; powerpc-apple-darwin8.8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-j-chkmail-Score: MSGID : 45D98F11.000 on discorde : j-chkmail score : XX :
	5/20 0 0.000 -> 2
X-Miltered: at discorde with ID 45D98F11.000 by Joe's j-chkmail
	(http://j-chkmail . ensmp . fr)!
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: int-area@ietf.org, monami6@ietf.org
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


Hi Henrik,

>>>> This issue is also worked out by the automotive industry, within ISO
>>>> TC204 WG16 (they have their own solution using SNMPv3).
>>>
>>>Do you have more details about this, maybe a pointer to available documents?
>> 
>> Nop, the documents are not public. But here is their public website:
>> http://www.calm.hu/
>
>Ok, thanks!  It does indeed look as if they are considering distribution
>of preference policies within the system, but it doesn't look as if the
>architecture requires a standardized protocol for transfer of preferences.
>Hard to tell for certain, though, based on the information available on
>the website.

What I can tell you is that they have their own solution, and this
solution is part of the CALM standard which is supposed to be deployed
in vehicles. So, this would be the standard solution within the vehicles
for ITS applications. They dot not necessarily need an IETF standard,
and don't even try, though they do reuse some of the existing standards
like NEMO Basic Support, etc. 

Thierry.








_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Mon Feb 19 12:50:19 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJCeF-0002fA-JW; Mon, 19 Feb 2007 12:49:59 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJCeE-0002f5-AQ
	for monami6@ietf.org; Mon, 19 Feb 2007 12:49:58 -0500
Received: from omta04ps.mx.bigpond.com ([144.140.83.156])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJCeC-0007lz-Gd
	for monami6@ietf.org; Mon, 19 Feb 2007 12:49:58 -0500
Received: from oaamta04ps.mx.bigpond.com ([124.191.178.123])
	by omta04ps.mx.bigpond.com with ESMTP id
	<20070219174950.NHKB295.omta04ps.mx.bigpond.com@oaamta04ps.mx.bigpond.com>
	for <monami6@ietf.org>; Mon, 19 Feb 2007 17:49:50 +0000
Received: from PC20005 ([124.191.178.123]) by oaamta04ps.mx.bigpond.com
	with ESMTP
	id <20070219174950.NTPK14659.oaamta04ps.mx.bigpond.com@PC20005>
	for <monami6@ietf.org>; Mon, 19 Feb 2007 17:49:50 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Monami6 WG'" <monami6@ietf.org>
Date: Tue, 20 Feb 2007 04:49:44 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcdQOEM/3BT+Cf7TQISxxJ+V2EFZGwEElqkwAADsJNA=
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-Id: <20070219174950.NTPK14659.oaamta04ps.mx.bigpond.com@PC20005>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 2086112c730e13d5955355df27e3074b
Subject: [Monami6] FW: [Int-area] Lifting up a filter discussion from Monami6
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

FYI 

-----Original Message-----
From: Hesham Soliman [mailto:Hesham@elevatemobile.com] 
Sent: Tuesday, February 20, 2007 4:44 AM
To: 'Jari Arkko'; 'Internet Area'
Cc: monami6-chairs@tools.ietf.org
Subject: RE: [Int-area] Lifting up a filter discussion from Monami6

Hi Jari, all,

After reading this email and reading all the responses I think a few
comments are in order.
Generally speaking, I would think that when given a choice between a "one
size fits all" solution versus one solution per protocol, most people would
choose the former. However, I don't think the choice is so simple as some of
the responses seemed to imply. 

I think it is ill-advised to take a decision on this without understanding
the scenarios, and the resulting requirements from those scenarios.
Additionally, we need to consider how each of the protocols using the
solution actually work. I'll list the scenarios we (authors of one of the
solutions) had in mind and let others comment or add their own scenarios.

Regardless of the approach, the solution we had in mind would transfer flow
descriptions and binding information between the flow in question and one or
more of the mobile node's addresses. The sender of this information is the
mobile node. The receiver is either a correspondent node or another
intermediate node. If we use the terms HA/MAP then we're implying the use of
MIPv6. So I'll stick to generic language. 

Now, each of the protocols you mention below (HIP, Mobike, SHIM6 ...etc)
have their own way of identifying the sending node to the receiver of the
signalling. This identity is obviously essential for securing the
signalling. Furthermore, they're all different in this regard. So I don't
think having one solution that fits all is a simple task. Even within one
protocol, the security requirements are different depending on the node
receiving the signalling. MIPv6 is the perfect example for this case. Can we
just assume that IPsec or AAA will work with a CN? I don't see how. Also,
some entities don't exist in all protocols, e.g. the HA/MAP.

So even if we go with "one solution" it would have to incorporate several
modes of operation (at least from the security perspective) to work for all
the different protocols. 

Another question to ask here is what is the real benefit of having one
solution? I'm not talking about saving documents, I mean a real benefit to
an implementer. If the flow descriptors need to have the same format then
that's easily done and reusable for implementers. But that doesn't require
one transport protocol. 

On the other hand, there are examples of protocols that incorporated the
same function without having to coordinate one protocol across the board. A
recent example is the use of IPv4 and IPv6 addresses in mobility protocols,
which was done in MIPv6, MIPv4 and I think shim6 without having to come up
with a single solution. 

Regardless of the outcome of this discussion, I hope we can get specific
with the comments that highlight the benefits of having one Vs several
solutions. I urge people to look at the bullets at the end of Jari's
original email and consider them when they make up their mind for one
approach Vs another. 

Hesham


 > I would like to lift up one issue from the Monami6 WG
 > to a more general discussion. Monami6 is developing an
 > extension to Mobile IPv6 / Nemo so that a mobile node could
 > register its presence in multiple locations simultaneously.
 > One of things that they expect to be able to do is to control
 > what traffic goes to what care-of address; this flow to this
 > address, and the other flow to that other address. Mobile nodes
 > can obviously decide by themselves what outgoing interface to use.
 > However, in order for a home agent to deal with return traffic
 > properly, the mobile node has to tell it what policy to
 > employ.
 > 
 > The working group has debated between a number of different
 > approaches for doing this. In one approach, draft-soliman-
 > monami6-flow-binding the mobile node adds a filter to a Mobile
 > IPv6 Binding Update to tell what traffic should use this binding.
 > Another approach, draft-larsson-monami6-filter-rules, decouples
 > the policy exchange from the mobility protocol. The policies are
 > exchanged at a different time (typically earlier) and carried by a
 > different protocol (in this case over UDP). Yet another draft,
 > draft-mitsuya-monami6-flow-distribution-policy also separates
 > the mobility protocol and policy transfer, and carries
 > the policies in HTTP.
 > 
 > Monami6 should of course decide how they want to design this.
 > But this may be an interesting debate from a more generic point
 > of view. Do we have input for them? For instance, are there needs
 > in HIP/Shim6/Mobike space for similar functionality? Should the
 > designs be tailored for each of these situations? Is there some
 > advantage or disadvantage in looking at a generic solution?
 > Would a generic solution be doable?
 > 
 > Without going into too much detail about the specific proposals
 > it seems that there are actually a number of different topics here:
 > - carrier protocol choice
 > - policy container format
 > - timing of the policy exchange
 > - securing the transfer
 > - etc
 > 
 > Thoughts?
 > 
 > Jari
 > 
 > _______________________________________________
 > Int-area mailing list
 > Int-area@lists.ietf.org
 > https://www1.ietf.org/mailman/listinfo/int-area
 > 



_______________________________________________
Int-area mailing list
Int-area@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/int-area



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Feb 20 02:43:11 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJPeS-0004zY-2Y; Tue, 20 Feb 2007 02:43:04 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJPeP-0004z9-QQ; Tue, 20 Feb 2007 02:43:01 -0500
Received: from n2.nomadiclab.com ([193.234.219.2])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HJPeO-0006XK-DB; Tue, 20 Feb 2007 02:43:01 -0500
Received: from n2.nomadiclab.com (localhost [127.0.0.1])
	by n2.nomadiclab.com (Postfix) with ESMTP id E8AF8212D38;
	Tue, 20 Feb 2007 09:42:56 +0200 (EET)
Received: from [193.234.219.43] (n43.nomadiclab.com [193.234.219.43])
	by n2.nomadiclab.com (Postfix) with ESMTP id B267A212D34;
	Tue, 20 Feb 2007 09:42:56 +0200 (EET)
Message-ID: <45DAA612.6010201@nomadiclab.com>
Date: Tue, 20 Feb 2007 09:41:06 +0200
From: Heikki Mahkonen <heikki@nomadiclab.com>
User-Agent: Thunderbird 1.5.0.9 (X11/20061222)
MIME-Version: 1.0
To: Monami6 WG <monami6@ietf.org>,  int-area@ietf.org
Subject: Re: [Monami6] FW: [Int-area] Lifting up a filter discussion from
	Monami6
References: <20070219174950.NTPK14659.oaamta04ps.mx.bigpond.com@PC20005>
In-Reply-To: <20070219174950.NTPK14659.oaamta04ps.mx.bigpond.com@PC20005>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: 
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Hesham,

Hesham Soliman wrote:
> Regardless of the approach, the solution we had in mind would transfer flow
> descriptions and binding information between the flow in question and one or
> more of the mobile node's addresses. The sender of this information is the
> mobile node. The receiver is either a correspondent node or another
> intermediate node. If we use the terms HA/MAP then we're implying the use of
> MIPv6. So I'll stick to generic language.

==> I think that the solution you describe in your draft for flow 
bindings might be enough for MIPv6 but it is not sufficient for instance 
in NEMO case (or other non MIPv6 intermediate node case). In the flow 
binding draft it is mandatory for the intermediate node to be able to 
receive a BU message, right?

In NEMO the MNN cannot send a BU message to the MR so the MNN. Because 
of this you would need to write another draft (which would resemble I 
think the one or both of the alternative solutions). Or change the NEMO 
so the MNN can send BU to the MR?

Just as an example. In NEMO the MNN might have a need to set the 
preferred routes for it's traffic into the MR. For instance, think of a 
case where the MNN is a laptop and the user uses a cellular phone with 
multiple interfaces as a MR. In this scenario the user most certainly 
would expect some control over the application flows from the laptop 
trough the phone.

Best regards,

Heikki Mahkonen




_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Feb 20 06:30:07 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJTBl-0001NO-UP; Tue, 20 Feb 2007 06:29:41 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJTBk-0001N0-FA; Tue, 20 Feb 2007 06:29:40 -0500
Received: from omta02ps.mx.bigpond.com ([144.140.83.154])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HJTBi-0000Ux-W3; Tue, 20 Feb 2007 06:29:40 -0500
Received: from oaamta02ps.mx.bigpond.com ([124.191.178.123])
	by omta02ps.mx.bigpond.com with ESMTP id
	<20070220112931.KQZQ24597.omta02ps.mx.bigpond.com@oaamta02ps.mx.bigpond.com>;
	Tue, 20 Feb 2007 11:29:31 +0000
Received: from PC20005 ([124.191.178.123]) by oaamta02ps.mx.bigpond.com
	with ESMTP
	id <20070220112931.KUDX17816.oaamta02ps.mx.bigpond.com@PC20005>;
	Tue, 20 Feb 2007 11:29:31 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Monami6 WG'" <monami6@ietf.org>,
	<int-area@ietf.org>
Subject: RE: [Monami6] FW: [Int-area] Lifting up a filter discussion
	fromMonami6
Date: Tue, 20 Feb 2007 22:29:25 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <45DAA612.6010201@nomadiclab.com>
Thread-Index: AcdUwtlV8hasbXlQQkSp09/+uQPycAAH14fA
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-Id: <20070220112931.KUDX17816.oaamta02ps.mx.bigpond.com@PC20005>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: 
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Heikki, 

I don't think we need to discuss this on the INT area mailing list so I'll
respond to you on the monami list. I think your analysis is off target but
I'll explain it on monami. 

Hesham 

 > -----Original Message-----
 > From: Heikki Mahkonen [mailto:heikki@nomadiclab.com] 
 > Sent: Tuesday, February 20, 2007 6:41 PM
 > To: Monami6 WG; int-area@ietf.org
 > Subject: Re: [Monami6] FW: [Int-area] Lifting up a filter 
 > discussion fromMonami6
 > 
 > Hi Hesham,
 > 
 > Hesham Soliman wrote:
 > > Regardless of the approach, the solution we had in mind 
 > would transfer flow
 > > descriptions and binding information between the flow in 
 > question and one or
 > > more of the mobile node's addresses. The sender of this 
 > information is the
 > > mobile node. The receiver is either a correspondent node or another
 > > intermediate node. If we use the terms HA/MAP then we're 
 > implying the use of
 > > MIPv6. So I'll stick to generic language.
 > 
 > ==> I think that the solution you describe in your draft for flow 
 > bindings might be enough for MIPv6 but it is not sufficient 
 > for instance 
 > in NEMO case (or other non MIPv6 intermediate node case). In 
 > the flow 
 > binding draft it is mandatory for the intermediate node to 
 > be able to 
 > receive a BU message, right?
 > 
 > In NEMO the MNN cannot send a BU message to the MR so the 
 > MNN. Because 
 > of this you would need to write another draft (which would 
 > resemble I 
 > think the one or both of the alternative solutions). Or 
 > change the NEMO 
 > so the MNN can send BU to the MR?
 > 
 > Just as an example. In NEMO the MNN might have a need to set the 
 > preferred routes for it's traffic into the MR. For instance, 
 > think of a 
 > case where the MNN is a laptop and the user uses a cellular 
 > phone with 
 > multiple interfaces as a MR. In this scenario the user most 
 > certainly 
 > would expect some control over the application flows from the laptop 
 > trough the phone.
 > 
 > Best regards,
 > 
 > Heikki Mahkonen
 > 
 > 
 > 
 > 
 > _______________________________________________
 > Monami6 mailing list
 > Monami6@ietf.org
 > https://www1.ietf.org/mailman/listinfo/monami6
 > 



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Feb 20 10:49:54 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJXEx-0006D5-Ce; Tue, 20 Feb 2007 10:49:15 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HJXEw-0006Cl-PU
	for monami6@ietf.org; Tue, 20 Feb 2007 10:49:14 -0500
Received: from [2001:660:7301:3192:211:43ff:fea3:7e4b]
	(helo=laposte.rennes.enst-bretagne.fr)
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HJXEs-0000WG-SE
	for monami6@ietf.org; Tue, 20 Feb 2007 10:49:14 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by laposte.rennes.enst-bretagne.fr (8.13.7/8.13.7/2006.08.14) with
	ESMTP id l1KFmpdd024960; Tue, 20 Feb 2007 16:48:51 +0100
Received: from l2.rennes.enst-bretagne.fr (l2.rennes.enst-bretagne.fr
	[192.44.77.4])
	by laposte.rennes.enst-bretagne.fr (8.13.7/8.13.7/2006.08.14) with
	ESMTP id l1KFmlU6024952; Tue, 20 Feb 2007 16:48:47 +0100
Received: from [192.44.77.188] (dhcpe188.rennes.enst-bretagne.fr
	[192.44.77.188]) (authenticated bits=0)
	by l2.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	l1KFmkmW014245
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO);
	Tue, 20 Feb 2007 16:48:46 +0100
In-Reply-To: <45D08E23.6090109@levkowetz.com>
References: <45D08E23.6090109@levkowetz.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <2E9C6D71-9D7D-41AF-919B-8E415E5B85C3@enst-bretagne.fr>
Content-Transfer-Encoding: 7bit
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
Date: Tue, 20 Feb 2007 16:48:45 +0100
To: Henrik Levkowetz <henrik@levkowetz.com>
X-Mailer: Apple Mail (2.752.3)
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: -2.8 (--)
X-Scan-Signature: b84f8c8fba0e1389e5eb998b64078964
Cc: monami6-chairs@tools.ietf.org, Monami6 WG <monami6@ietf.org>
Subject: [Monami6] Re: Review of draft-ietf-monami6-mipv6-analysis-01.txt
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Henrik and all,

First, I would like to thank you very much for this deep review.
I tried to address all your comments. Please check the new version here:

http://www.rennes.enst-bretagne.fr/~montavont/ietf/draft-ietf-monami6- 
mipv6-analysis-02.txt

and the diff from 01 here :

http://www.rennes.enst-bretagne.fr/~montavont/ietf/diff-02-from-01.html

Anyone is welcome to discuss how I addressed Henrik's comments.  
Please do not hesitate to provide any feedback.

I would also like to draw your attention on section 3, which section  
I changed from Requirements to Nodes capabilties.

I just have few comments on which I have questions / comments. Please  
find them inline.

On Feb 12, 2007, at 4:56 PM, Henrik Levkowetz wrote:

[SKIP]

>
> Section 5.1., paragraph 3:
>
>>    Achievable goals (when the node has multiple interfaces):  
>> Ubiquitous
>>    Access, Reliability, Load Sharing, Load Balancing, Aggregated
>>    Bandwidth, Preference Settings.
>
>   It's not obvious to me that this statement is correct; I'd for
>   instance say that you can't achieve Ubiquitous Access, and only
>   limite Reliability.
	
NICOLAS: The achievable goals are not mobile IP dependant: it is
	dependant of the topology of the configuration. Normally, when
	you have multiple interfaces, you should be able to achieve
	these goals. See introduction of section 5.
	I have added: Achievable goals (when the MN has a
	single interface).

>
>   Also, in para. 2 above, you have explained how you only cna have
>   two interfaces used by the MN simultaneously, and only one at a time
>   as HoA and one at a time as CoA.  However, you still say "multiple
>   interfaces" here and below.  Either there is something fundamental
>   I don't understand here, or you should change this to something else
>   (1 HoA, 1 CoA) or qualify "multiple interfaces" in some other  
> manner.
>
>
>
[SKIP]
>
>
> Section 5.2., paragraph 2:
>
>>    Achievable goals: Ubiquitous Access, Reliability, Load Sharing,  
>> Load
>>    Balancing and Aggregated Bandwidth (if the MN has more than one
>>    interface) and Preference Settings.
>
>   I'd not say Ubiquietous Access, and I'd say Limited Reliability,
>   Limited Load Sharing, Limited Aggregated bandwidth.  There are
>   restrictions on each of these, so just saying that they are
>   achievable in this configuration is misleading.

NICOLAS: same comment as before: does the introduction of section 5 is
	clear enough? => these goals are only achievable if mechanisms
	are provided in addition to MIPv6.

>
>
> Section 5.2., paragraph 10:
>
>>       In Bidirectional Tunnel (BT) mode, preference settings and load
>>       sharing only affect the path between the CN and the HA(s),  
>> and not
>>       the path between the MN and the HA(s), as long as the CoA  
>> does not
>>       change.  In RO mode, the path between the MN and the CN does  
>> not
>>       change if the CoA does not change.  As an entry in the binding
>>       cache is identified by a HoA, the MN can register the same CoA
>>       with all HoAs, on any distant node.  A mechanism would then be
>>       needed for the MN to select which HoA should be used when a new
>>       communication flow is initiated.  A similar mechanism is  
>> needed on
>>       the CN side if it knows that multiple HoAs are assigned to the
>>       same MN.  With such mechanisms, it would be possible to use
>>       multiple HoAs at the same time, and load sharing could be
>>       performed.  See in Section 6.1.1 where such path selection  
>> issues
>>       are discussed.  It is also possible that the MN register one  
>> HoA
>>       as a CoA for another HoA (see discussions in Section 6.3.1).
>
>   Since it is likely in many (most?) scenarios of practical interest
>   that it is the first hop from CoA towards HA which is most bandwidth
>   constrained, this load sharing may be of limited value or interest.
>   You probably should mention something about this.

NICOLAS: agree. I have updated the text.
>
>
> Section 5.2., paragraph 11:
>
>>    o  Load Balancing and Aggregated Bandwidth
>>       Load balancing and aggregated bandwidth are achievable when  
>> the MN
>>       has several interfaces.  In this case, the MN is attached to  
>> one
>>       foreign link via one of its interfaces, and it is attached  
>> to home
>>       link(s) with its other interface(s).  In this case, the MN can
>>       spread flows over its interfaces.  Note that if a CN  
>> initiates a
>>       communication, the interface that it will use on the MN would
>>       depend on the information it has about this MN.
>
>   As above, this load balancing and bandwidth aggregation may be of
>   limited value or interest, and you probably should mention something
>   about this, too.

NICOLAS: I don't think it is a limited interest: the MN has the choice
	to use any of its interfaces, and the first hop at the MN may
	be the bottleneck

>
>
> Section 5.3., paragraph 1:
>
>>    The MN is multihomed since it has several CoAs.  This case may for
>>    instance occur when the interface of the node is connected to a  
>> link
>>    where multiple IPv6 prefixes are available.  One possible  
>> reason for
>>    this is that the visited network is multihomed and because of  
>> that,
>>    multiple prefixes are available in it, one per provider.  Note  
>> that
>>    one of the interfaces of the MN may be connected to its home link.
>
>   I'm surprised that you mention the (at least to me) less interesting
>   scenario of multiple CoAs on the same link, and don't mention the
>   more interesting scenario of multiple independent interfaces who
>   are not on the same link.  Fix?
>
>
> Section 5.3., paragraph 2:
>
>>    Achievable goals: Reliability, Load Sharing, Preference Settings,
>>    Load Balancing and Aggregated Bandwidth (if the MN is equipped  
>> with
>>    several interfaces)
>
>   I'd split this in one CoA interface vs. multiple CoA interfaces.
>   The extent to which the goals can be achieved differ between these
>   cases.  In particular, in the case where you don't have any  
> interface
>   connected to the home network, the conclusion for all of the goals
>   differ between the one-interface and the multi-interface case.

NICOLAS: but this paragraph describes the achievable goals, and not
	how to achieve these. I don't think there is a difference in
	the achievable goals (exept for the aggregated bandwidth,
	which is specified)

[SKIP]

>
> Section 5.5., paragraph 4:
>
>>    Current situation with MIPv6
>
>   The discussion here feels strange to me - I don't see how this case
>   differs from any other non-mobility multihoming case, as long as
>   you're in n HoA, 0 CoA situation.  I'd prefer to simply say so,
>   OR if there is any point on which this situation differs from that
>   case, specifically point out such points, rather than keep to the
>   format of the previous 5.x sections...

NICOLAS: Added the sentence : "This situation is quite similar to a
	non-mobile node which is multihomed." The based configuration
	is the same as a fixed node, exept that here the node IS
	mobile, this is why I would prefer to keep the same format for
	this section

>
>
> Section 6.1.1., paragraph 7:
>
>>       This choice would be made at the time of a new communication  
>> flow
>>       set up.  Usual IPv6 mechanisms for source and destination  
>> address
>>       selection, such as "Default Address Selection for IPv6" [7]  
>> could
>>       be used.
>
>   Possibly you should also mention the use of DNS SRV records, and
>   which address(es) to announce for the DNS A / AAAA records.
>
>
> Section 6.1.1., paragraph 10:
>
>>       When multiple CoAs are available, the MN and its communicating
>>       peers (HA and CNs) must be able to select the appropriate  
>> CoA to
>>       be used for a particular packet or flow.  The MN may use its
>>       internal policies to (i) distribute its flow, and (ii)  
>> distribute
>>       policies on distant nodes to allow them to select the preferred
>>       CoA.  Solutions like flow binding [6] may be used.
>
>   Humm.  How/when would *ever* a CN *choose* a CoA (as opposed to
>   a HoA, which might result in RO to a CoA chosen by the MN) to
>   communicate with?  If this statement is correct, some more text,
>   maybe an example, would be good.

NICOLAS: Here we refer to a mechanism where the MN can advertise its
	multiple CoAs to HA/CN and possibly associated rules. Don't
	you think that the text already say that, and that the
	reference can be used to clarify such a mechanism?

>
[SKIP]

Nicolas

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Feb 20 15:49:58 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJbvy-0004gc-L0; Tue, 20 Feb 2007 15:49:58 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJbvx-0004gJ-1a; Tue, 20 Feb 2007 15:49:57 -0500
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HJbvv-00007p-PT; Tue, 20 Feb 2007 15:49:57 -0500
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 33073198776;
	Tue, 20 Feb 2007 22:49:55 +0200 (EET)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id DD67A1986E2;
	Tue, 20 Feb 2007 22:49:54 +0200 (EET)
Message-ID: <45DB5EF3.5030608@piuha.net>
Date: Tue, 20 Feb 2007 22:49:55 +0200
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.9 (X11/20070104)
MIME-Version: 1.0
To: int-area@ietf.org
Subject: Re: [Monami6] FW: [Int-area] Lifting up a filter
	discussion	fromMonami6
References: <20070220112931.KUDX17816.oaamta02ps.mx.bigpond.com@PC20005>
In-Reply-To: <20070220112931.KUDX17816.oaamta02ps.mx.bigpond.com@PC20005>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Cc: 'Monami6 WG' <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

There were a couple of questions about what list to
use for this discussion -- Lets keep the general
discussion on the int-area list. I thought the topic
deserved a wider audience, and that's still the case.
But if there was some detail about current proposals,
monami6 list works for that better. The question
of what nodes to involve, including hosts under an
MR, did seem important though in terms of thinking
what architecture works for this function.

Jari



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Feb 21 03:35:56 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJmx2-0007dH-Ac; Wed, 21 Feb 2007 03:35:48 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJmx0-0007cy-Eo; Wed, 21 Feb 2007 03:35:46 -0500
Received: from omta05ps.mx.bigpond.com ([144.140.83.195])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HJmwx-0007yz-Vk; Wed, 21 Feb 2007 03:35:46 -0500
Received: from PC20005 ([124.191.178.123]) by omta05ps.mx.bigpond.com
	with ESMTP
	id <20070221083536.MDTJ19269.omta05ps.mx.bigpond.com@PC20005>;
	Wed, 21 Feb 2007 08:35:36 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Monami6 WG'" <monami6@ietf.org>,
	<int-area@ietf.org>
Subject: RE: [Monami6] FW: [Int-area] Lifting up a filter discussion
	fromMonami6
Date: Wed, 21 Feb 2007 19:35:29 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <45DAA612.6010201@nomadiclab.com>
Thread-Index: AcdUwtlV8hasbXlQQkSp09/+uQPycAAz0Q4g
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-Id: <20070221083536.MDTJ19269.omta05ps.mx.bigpond.com@PC20005>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: 
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi Heikki, 

I guess Jari wants us to continue this point on the int-area list so I'll
respond to both.
See below.

 > Hesham Soliman wrote:
 > > Regardless of the approach, the solution we had in mind 
 > would transfer flow
 > > descriptions and binding information between the flow in 
 > question and one or
 > > more of the mobile node's addresses. The sender of this 
 > information is the
 > > mobile node. The receiver is either a correspondent node or another
 > > intermediate node. If we use the terms HA/MAP then we're 
 > implying the use of
 > > MIPv6. So I'll stick to generic language.
 > 
 > ==> I think that the solution you describe in your draft for flow 
 > bindings might be enough for MIPv6 but it is not sufficient 
 > for instance 
 > in NEMO case (or other non MIPv6 intermediate node case). In 
 > the flow 
 > binding draft it is mandatory for the intermediate node to 
 > be able to 
 > receive a BU message, right?
 > 
 > In NEMO the MNN cannot send a BU message to the MR so the 
 > MNN. Because 
 > of this you would need to write another draft (which would 
 > resemble I 
 > think the one or both of the alternative solutions). Or 
 > change the NEMO 
 > so the MNN can send BU to the MR?

=> No no no :). You've skipped a lot of steps here. First of all, the
current solution does support nemo because the signalling can be sent from
the MR to the HA/MAP. As you probably know nemo does not allow the MR to
send BUs to a CN, so this fully supports nemo. Now, your second point is
about an MNN sending a BU. First, lets be clear that the MNN does not send
BUs to the MR in any spec defined today, so the BU would have to be sent
from the MNN to a CN/HA/MAP. I don't see why this can't be done in
draft-soliman. If you mean that the MNN (more likely a VMN) needs to know
what properties correspond to which prefix advertised by the MR then this
goes back to a separate issue of how the MR informs MNNs of the properties
associated with advertised prefixes. This issue was raised many years ago
(when nemo was a bof) and was recently referred to by Thierry in his
response to a query about this point. Thierry's response was on this thread
so feel free to take a look. 

So the bottom line is the MIPv6 solution does support this case. 

 > 
 > Just as an example. In NEMO the MNN might have a need to set the 
 > preferred routes for it's traffic into the MR. For instance, 
 > think of a 
 > case where the MNN is a laptop and the user uses a cellular 
 > phone with 
 > multiple interfaces as a MR. In this scenario the user most 
 > certainly 
 > would expect some control over the application flows from the laptop 
 > trough the phone.

=> Of course, so if it gets the prefixes from the MR and associated
properties with each one it can make that choice. I don't see the
relationship between this issue and the current discussion on this thread. 

Hesham



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Feb 21 06:18:24 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJpU7-0007Fu-5x; Wed, 21 Feb 2007 06:18:07 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJpU5-0007FV-FP; Wed, 21 Feb 2007 06:18:05 -0500
Received: from mail128.messagelabs.com ([216.82.250.131])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HJpU4-0001e4-2Q; Wed, 21 Feb 2007 06:18:05 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-4.tower-128.messagelabs.com!1172056683!15982036!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [129.188.136.10]
Received: (qmail 25366 invoked from network); 21 Feb 2007 11:18:02 -0000
Received: from motgate6.mot.com (HELO motgate.mot.com) (129.188.136.10)
	by server-4.tower-128.messagelabs.com with SMTP;
	21 Feb 2007 11:18:02 -0000
Received: from az33exr01.mot.com (az33exr01.mot.com [10.64.251.231])
	by motgate.mot.com (8.12.11/Motorola) with ESMTP id l1LBMnl8011941;
	Wed, 21 Feb 2007 04:22:54 -0700 (MST)
Received: from az10vts01 (az10vts01.mot.com [10.64.251.242])
	by az33exr01.mot.com (8.13.1/Vontu) with SMTP id l1LBECPi014032;
	Wed, 21 Feb 2007 05:14:13 -0600 (CST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr01.mot.com (8.13.1/8.13.0) with ESMTP id l1LBEAUg014009;
	Wed, 21 Feb 2007 05:14:11 -0600 (CST)
Message-ID: <45DC2981.9060002@motorola.com>
Date: Wed, 21 Feb 2007 12:14:09 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: [Monami6] FW: [Int-area] Lifting up a filter
	discussion	fromMonami6
References: <20070221083536.MDTJ19269.omta05ps.mx.bigpond.com@PC20005>
In-Reply-To: <20070221083536.MDTJ19269.omta05ps.mx.bigpond.com@PC20005>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Vontu: Pass
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
Cc: int-area@ietf.org, 'Monami6 WG' <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hesham Soliman wrote:
> Hi Heikki,
> 
> I guess Jari wants us to continue this point on the int-area list so
>  I'll respond to both. See below.
> 
>> Hesham Soliman wrote:
>>> Regardless of the approach, the solution we had in mind
>> would transfer flow
>>> descriptions and binding information between the flow in
>> question and one or
>>> more of the mobile node's addresses. The sender of this
>> information is the
>>> mobile node. The receiver is either a correspondent node or 
>>> another intermediate node. If we use the terms HA/MAP then we're
>>> 
>> implying the use of
>>> MIPv6. So I'll stick to generic language.
>> 
>> ==> I think that the solution you describe in your draft for flow 
>> bindings might be enough for MIPv6 but it is not sufficient for 
>> instance in NEMO case (or other non MIPv6 intermediate node case).
>>  In the flow binding draft it is mandatory for the intermediate
>> node to be able to receive a BU message, right?
>> 
>> In NEMO the MNN cannot send a BU message to the MR so the MNN. 
>> Because of this you would need to write another draft (which would
>>  resemble I think the one or both of the alternative solutions). Or
>>  change the NEMO so the MNN can send BU to the MR?
> 
> => No no no :). You've skipped a lot of steps here. First of all, the
>  current solution does support nemo because the signalling can be 
> sent from the MR to the HA/MAP. As you probably know nemo does not 
> allow the MR to send BUs to a CN, so this fully supports nemo.

Yes both Hesham and Heikki: MNN doesn't send NEMO BU and MR doesn't send
BU toCN.

(terminology: MNN as defined  by terminology documents is a Mobile
  Network Node, thus a Mobile Node, which can be a Mobile Router; but I
  assume the intent was to say a MH (not a MR) that is connected to a
  moving network doesn't send BU to MR - I agree with this).

> Now, your second point is about an MNN sending a BU. First, lets be 
> clear that the MNN does not send BUs to the MR in any spec defined 
> today, so the BU would have to be sent from the MNN to a CN/HA/MAP. I
>  don't see why this can't be done in draft-soliman. If you mean that 
> the MNN (more likely a VMN) needs to know what properties correspond 
> to which prefix advertised by the MR then this goes back to a 
> separate issue of how the MR informs MNNs of the properties 
> associated with advertised prefixes. This issue was raised many years
>  ago (when nemo was a bof) and was recently referred to by Thierry in
>  his response to a query about this point. Thierry's response was on 
> this thread so feel free to take a look.

Regardlessof Thierry mentioning it, it's still unsolved.

It's still true that an LFN/MH has certain preferences for application,
preferences that aren't currently communicated to MR.  So when MR makes
monami decisions on which interface to use it's monami-relevant only for
that MR, not for LFN.

In this sense, monami filters at MR are irrelevant to LFN.  In which
case one can easily say that monami filters are only for MR.  Which is
easy to say that is relevant only for the MH part of that MR.

My reasoning is.  But let me turn it into a question:

What's the effect of MR monami filters on the LFN application?

> So the bottom line is the MIPv6 solution does support this case.
> 
>> 
>> Just as an example. In NEMO the MNN might have a need to set the 
>> preferred routes for it's traffic into the MR. For instance, think
>>  of a case where the MNN is a laptop and the user uses a cellular 
>> phone with multiple interfaces as a MR. In this scenario the user 
>> most certainly would expect some control over the application flows
>>  from the laptop trough the phone.
> 
> => Of course, so if it gets the prefixes from the MR and associated 
> properties with each one it can make that choice. I don't see the 
> relationship between this issue and the current discussion on this 
> thread.

I agree with you with the first part.  But I see a strong relationship
of MR making monami decisions and its effects on LFN.  If this
relationship is not defined then one simply can't say Monami is for 
NEMO.  End-to-end arguments can be made about this.

I also think a clear distinction should be made here, that I wanted to
say since long but things were too hectic at that time.

When monami6 was formed there network mobility was an important topic
discussed in many places.  Monami6 has a goal to work in the NEMO
context, so it helped building it up.  This can be understood in two ways:

-simplest: NEMO is an extension to MIP, so a HA doing NEMO can be
  extended to do monami (mcoa) and it will continue to do NEMO no
  problem.  But that doesn't mean NEMO protocol was extended.  It more
  means that that HA will continue to use UDP as before, or HTTP or NEMO.
-more complex: have monami flow bindings to have a meaning _through_ the
  MR, to LFN and have a NEMO sense.  That is a more relevant means to say
  that the MONAMI6 WG does NEMO.  OTherwise monami6 does NEMO as much as
  it does UDP.

Alex


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Feb 21 12:53:36 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJveU-00053y-Ad; Wed, 21 Feb 2007 12:53:14 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJvdg-0004wF-J1; Wed, 21 Feb 2007 12:52:24 -0500
Received: from omta03ps.mx.bigpond.com ([144.140.82.155])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HJvPL-00019z-4y; Wed, 21 Feb 2007 12:37:36 -0500
Received: from oaamta03ps.mx.bigpond.com ([124.191.178.123])
	by omta03ps.mx.bigpond.com with ESMTP id
	<20070221173727.ZEBI24030.omta03ps.mx.bigpond.com@oaamta03ps.mx.bigpond.com>;
	Wed, 21 Feb 2007 17:37:27 +0000
Received: from PC20005 ([124.191.178.123]) by oaamta03ps.mx.bigpond.com
	with ESMTP
	id <20070221173727.PNT14761.oaamta03ps.mx.bigpond.com@PC20005>;
	Wed, 21 Feb 2007 17:37:27 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Alexandru Petrescu'" <alexandru.petrescu@motorola.com>
Subject: RE: [Monami6] FW: [Int-area] Lifting up a filter
	discussion	fromMonami6
Date: Thu, 22 Feb 2007 04:37:20 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <45DC2981.9060002@motorola.com>
Thread-Index: AcdVqfmsUUFKFTZqTE+vrdlx7gy/VAANHe5Q
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-Id: <20070221173727.PNT14761.oaamta03ps.mx.bigpond.com@PC20005>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: int-area@ietf.org, 'Monami6 WG' <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Alex,  

 > In this sense, monami filters at MR are irrelevant to LFN.  In which
 > case one can easily say that monami filters are only for MR. 
 >  Which is
 > easy to say that is relevant only for the MH part of that MR.
 > 
 > My reasoning is.  But let me turn it into a question:
 > 
 > What's the effect of MR monami filters on the LFN application?

=> See below.

 > >> Just as an example. In NEMO the MNN might have a need to set the 
 > >> preferred routes for it's traffic into the MR. For instance, think
 > >>  of a case where the MNN is a laptop and the user uses a cellular 
 > >> phone with multiple interfaces as a MR. In this scenario the user 
 > >> most certainly would expect some control over the 
 > application flows
 > >>  from the laptop trough the phone.
 > > 
 > > => Of course, so if it gets the prefixes from the MR and 
 > associated 
 > > properties with each one it can make that choice. I don't see the 
 > > relationship between this issue and the current discussion on this 
 > > thread.
 > 
 > I agree with you with the first part.  But I see a strong 
 > relationship
 > of MR making monami decisions and its effects on LFN.  If this
 > relationship is not defined then one simply can't say Monami is for 
 > NEMO.  End-to-end arguments can be made about this.

=> This is not different from a router in the fixed network that
load-balances traffic without informing end hosts. This happens all the time
today and no one is making e2e arguments about that. Routers are given the
authority to route traffic in the most optimum manner, as they see it. 

Hesham




_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Feb 21 13:10:47 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJvvP-0007r2-9w; Wed, 21 Feb 2007 13:10:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJvvN-0007qt-SI; Wed, 21 Feb 2007 13:10:41 -0500
Received: from mail119.messagelabs.com ([216.82.241.179])
	by ietf-mx.ietf.org with smtp (Exim 4.43)
	id 1HJvvM-0000v0-JT; Wed, 21 Feb 2007 13:10:41 -0500
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@motorola.com
X-Msg-Ref: server-14.tower-119.messagelabs.com!1172081439!20671923!1
X-StarScan-Version: 5.5.10.7.1; banners=-,-,-
X-Originating-IP: [144.189.100.102]
Received: (qmail 20619 invoked from network); 21 Feb 2007 18:10:39 -0000
Received: from motgate4.mot.com (HELO motgate4.mot.com) (144.189.100.102)
	by server-14.tower-119.messagelabs.com with SMTP;
	21 Feb 2007 18:10:39 -0000
Received: from az33exr03.mot.com (az33exr03.mot.com [10.64.251.233])
	by motgate4.mot.com (8.12.11/Motorola) with ESMTP id l1LIAdro006008;
	Wed, 21 Feb 2007 11:10:39 -0700 (MST)
Received: from [10.161.201.117] (zfr01-2117.crm.mot.com [10.161.201.117])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id l1LIAbEn008615;
	Wed, 21 Feb 2007 12:10:37 -0600 (CST)
Message-ID: <45DC8B1C.1090804@motorola.com>
Date: Wed, 21 Feb 2007 19:10:36 +0100
From: Alexandru Petrescu <alexandru.petrescu@motorola.com>
User-Agent: Thunderbird 1.5.0.8 (Windows/20061025)
MIME-Version: 1.0
To: Hesham Soliman <Hesham@elevatemobile.com>
Subject: Re: network decisions for endnode (was: [Monami6] FW: [Int-area]
	Lifting up a filter discussion from Monami6)
References: <20070221173727.PNT14761.oaamta03ps.mx.bigpond.com@PC20005>
In-Reply-To: <20070221173727.PNT14761.oaamta03ps.mx.bigpond.com@PC20005>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Cc: int-area@ietf.org, 'Monami6 WG' <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

[lifting up monmami6 WG from CC]

Hesham Soliman wrote:
>>>> Just as an example. In NEMO the MNN might have a need to set 
>>>> the preferred routes for it's traffic into the MR. For 
>>>> instance, think of a case where the MNN is a laptop and the 
>>>> user uses a cellular phone with multiple interfaces as a MR. In
>>>>  this scenario the user most certainly would expect some 
>>>> control over the
>> application flows
>>>> from the laptop trough the phone.
>>> 
>>> => Of course, so if it gets the prefixes from the MR and
>> associated
>>> properties with each one it can make that choice. I don't see the
>>>  relationship between this issue and the current discussion on 
>>> this thread.
>> 
>> I agree with you with the first part.  But I see a strong 
>> relationship of MR making monami decisions and its effects on LFN.
>>  If this relationship is not defined then one simply can't say 
>> Monami is for NEMO.  End-to-end arguments can be made about this.
> 
> => This is not different from a router in the fixed network that 
> load-balances traffic without informing end hosts. This happens all 
> the time today and no one is making e2e arguments about that.

Hi HEsham, I'm not sure how it's thought routers in the fixed network
load-balance traffic without informing end-hosts.  IETF has some nice
qos reservation mechanisms that are triggered by end-node after which
routers in the middle look at packet markings and load-balance
accordingly.  COPS, RSVP, Traffic Class, Diffserv are keywords for
search.  It's the end-node who tags the packets anyways.

It's even true for a MIP6 HA: HA copies the traffic class from inner to
outer header, so what's decided by MN is respected by HA.  (there's an
option with pre-configured Traffic Class at HA , but optional that is).

So I think flow bindings for NEMO _would_ be different than
COPS/RSVP/Traffic Class, because MR would make decisions irrespective of
the LFN will, what do you think?

Alex


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Wed Feb 21 13:21:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJw5S-00011H-2a; Wed, 21 Feb 2007 13:21:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HJw5Q-00010l-4H; Wed, 21 Feb 2007 13:21:04 -0500
Received: from omta02ps.mx.bigpond.com ([144.140.83.154])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HJw5O-0003OA-4Z; Wed, 21 Feb 2007 13:21:04 -0500
Received: from oaamta02ps.mx.bigpond.com ([124.191.178.123])
	by omta02ps.mx.bigpond.com with ESMTP id
	<20070221182050.FYLK24597.omta02ps.mx.bigpond.com@oaamta02ps.mx.bigpond.com>;
	Wed, 21 Feb 2007 18:20:50 +0000
Received: from PC20005 ([124.191.178.123]) by oaamta02ps.mx.bigpond.com
	with ESMTP
	id <20070221182049.FJAV17816.oaamta02ps.mx.bigpond.com@PC20005>;
	Wed, 21 Feb 2007 18:20:49 +0000
From: "Hesham Soliman" <Hesham@elevatemobile.com>
To: "'Alexandru Petrescu'" <alexandru.petrescu@motorola.com>
Subject: RE: network decisions for endnode (was: [Monami6] FW: [Int-area]
	Lifting up a filter discussion from Monami6)
Date: Thu, 22 Feb 2007 05:20:42 +1100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <45DC8B1C.1090804@motorola.com>
Thread-Index: AcdV46nqMBhquK7+QgihFwj5IDZr4QAAFOPg
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
Message-Id: <20070221182049.FJAV17816.oaamta02ps.mx.bigpond.com@PC20005>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: int-area@ietf.org, 'Monami6 WG' <monami6@ietf.org>
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org


 > Hi HEsham, I'm not sure how it's thought routers in the fixed network
 > load-balance traffic without informing end-hosts.  IETF has some nice
 > qos reservation mechanisms that are triggered by end-node after which
 > routers in the middle look at packet markings and load-balance
 > accordingly.  COPS, RSVP, Traffic Class, Diffserv are keywords for
 > search.  It's the end-node who tags the packets anyways.

=> This is not related to reality in deployed networks. End hosts don't use
RSVP and hosts hardly ever mark TOS fields. Anyway, your response is not
related to what I said earlier, routers do split flows to different links
all the time (of course one flow is expected to take the same path in the
network under normal circumstances). This is a fact and I don't see why an
end host has to know which specific links its traffic goes through on every
hop. That makes no sense. 

 > 
 > It's even true for a MIP6 HA: HA copies the traffic class 
 > from inner to
 > outer header, so what's decided by MN is respected by HA.  
 > (there's an
 > option with pre-configured Traffic Class at HA , but 
 > optional that is).

=> Again, this is not related to my comment or this thread in general.

Hesham



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Thu Feb 22 00:55:11 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HK6uj-0007lv-7B; Thu, 22 Feb 2007 00:54:45 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HK6uh-0007kh-WC
	for monami6@ietf.org; Thu, 22 Feb 2007 00:54:44 -0500
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HK6ug-0007u5-DA
	for monami6@ietf.org; Thu, 22 Feb 2007 00:54:43 -0500
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/kings) with ESMTP id
	l1M5sen4020999
	for <monami6@ietf.org>; Thu, 22 Feb 2007 14:54:41 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx2) with ESMTP id
	l1M5se120431
	for <monami6@ietf.org>; Thu, 22 Feb 2007 14:54:40 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/mariners) with ESMTP id
	l1M5se817025
	for <monami6@ietf.org>; Thu, 22 Feb 2007 14:54:40 +0900 (JST)
Received: from Sephiroth ([10.81.113.103]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Feb 2007 13:54:36 +0800
From: "Benjamin Lim" <benjamin.limck@sg.panasonic.com>
To: "'Monami6 WG'" <monami6@ietf.org>
References: <45D307BE.4060903@piuha.net>	<00be01c75177$52aebd50$f80c37f0$@limck@sg.panasonic.com>	<45D53CCF.5010607@levkowetz.com>
	<20070216152751.ec384ad0.thierry.ernst@inria.fr>
In-Reply-To: <20070216152751.ec384ad0.thierry.ernst@inria.fr>
Subject: RE: [Monami6] RE: [Int-area] Lifting up a filter discussion from
	Monami6
Date: Thu, 22 Feb 2007 13:54:27 +0800
Organization: Panasonic Singapore Laboratories Pte Ltd
Message-ID: <015b01c75645$e9ec0600$bdc41200$@limck@sg.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcdR1qjJS3W9tcNhSs+tF3CcxuyB4QEXstgg
Content-Language: en-us
X-OriginalArrivalTime: 22 Feb 2007 05:54:36.0610 (UTC)
	FILETIME=[EF040A20:01C75645]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: benjamin.limck@sg.panasonic.com, Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

Hi,

Sorry for the late response. I have no access to my mail client for the past
few days. 
Response inline from snip parts of various mails.

>From Thierry;
[snip]
> However, since it is more important to be solved for Monami6 use case,
> we could contemplate to solve it within Monami6, if interest arises. Of
> course, the solution should not be specific to mobility since the
> mobility protocol doesn't intervene between MR and MNN.
[/snip]

[Ben] Exactly what I feel. Based on the mails I have read on this
discussion, I feel that monami6 draft(s) on flow bindings should consider
such use case of preference settings of MNN being attached to a MR. This is
inline with monami6 being supportive of NEMO.

>From Hesham;
[snip]
>>Just as an example. In NEMO the MNN might have a need to set the preferred

>>routes for it's traffic into the MR. For instance, think of a case where
the MNN is a 
>>laptop and the user uses a cellular phone with multiple interfaces as a
MR. In this 
>>scenario the user most certainly would expect some control over the
application 
>>flows from the laptop trough the phone.
>
> => Of course, so if it gets the prefixes from the MR and associated 
> properties with each one it can make that choice. I don't see the 
> relationship between this issue and the current discussion on this 
> thread.
[/snip]

[Ben] From what Hesham mentioned on prefix and associated properties, this
could be a possible solution to the problem in which the MNN in NEMO has no
way of knowing the existence of multiple paths (and their network
characteristics). Since there is mention on applicability on flow bindings
to HMIPv6, why not mention applicability for MNN in NEMO in the draft and
include this point? This is just my suggestion.

Regards,
Benjamin Lim



_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6



From monami6-bounces@ietf.org Tue Feb 27 18:50:56 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMC5a-0002tz-2W; Tue, 27 Feb 2007 18:50:34 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HMC55-00013f-O8; Tue, 27 Feb 2007 18:50:03 -0500
Received: from ns1.neustar.com ([2001:503:c779:1a::9c9a:108a])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1HMC55-0003hw-8b; Tue, 27 Feb 2007 18:50:03 -0500
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns1.neustar.com (Postfix) with ESMTP id 0F26526ED8;
	Tue, 27 Feb 2007 23:50:03 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1HMC54-0007am-GF; Tue, 27 Feb 2007 18:50:02 -0500
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Message-Id: <E1HMC54-0007am-GF@stiedprstage1.ietf.org>
Date: Tue, 27 Feb 2007 18:50:02 -0500
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: monami6@ietf.org
Subject: [Monami6] I-D ACTION:draft-ietf-monami6-mipv6-analysis-02.txt 
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>,
	<mailto:monami6-request@ietf.org?subject=subscribe>
Errors-To: monami6-bounces@ietf.org

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts 
directories.
This draft is a work item of the Mobile Nodes and Multiple Interfaces in IPv6 Working Group of the IETF.

	Title		: Analysis of Multihoming in Mobile IPv6
	Author(s)	: N. Montavont, et al.
	Filename	: draft-ietf-monami6-mipv6-analysis-02.txt
	Pages		: 35
	Date		: 2007-2-27
	
Mobile IPv6 as specified in RFC3775 [1] allows a mobile node to
   maintain its IPv6 communications while moving between subnets.  This
   document investigates configurations where a mobile node running
   Mobile IPv6 is multihomed.  The use of multiple addresses is foreseen
   to provide ubiquitous, permanent and fault-tolerant access to the
   Internet, particularly on mobile nodes which are more prone to
   failure or sudden lack of connectivity.  However, Mobile IPv6
   currently lacks support for such multihomed nodes.  The purpose of
   this document is to detail all the issues arising through the
   operation of Mobile IPv6 on multihomed mobile nodes.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-monami6-mipv6-analysis-02.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of 
the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.

Internet-Drafts are also available by anonymous FTP. Login with the 
username "anonymous" and a password of your e-mail address. After 
logging in, type "cd internet-drafts" and then 
"get draft-ietf-monami6-mipv6-analysis-02.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-monami6-mipv6-analysis-02.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2007-2-27154247.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-monami6-mipv6-analysis-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-monami6-mipv6-analysis-02.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2007-2-27154247.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6

--NextPart--




