From monami6-bounces@ietf.org Thu Jun 14 08:57:13 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hyosy-0000IK-BL; Thu, 14 Jun 2007 08:57:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hyosw-0000IA-Jr
	for monami6@ietf.org; Thu, 14 Jun 2007 08:57:10 -0400
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hyosv-0001S4-Pk
	for monami6@ietf.org; Thu, 14 Jun 2007 08:57:10 -0400
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
	l5ECv6SX024156
	for <monami6@ietf.org>; Thu, 14 Jun 2007 21:57:06 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx1) with ESMTP id
	l5ECv7D17758
	for <monami6@ietf.org>; Thu, 14 Jun 2007 21:57:07 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/indians) with ESMTP id
	l5ECv5912728
	for <monami6@ietf.org>; Thu, 14 Jun 2007 21:57:05 +0900 (JST)
Received: from [127.0.0.1] ([10.238.16.137]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Thu, 14 Jun 2007 20:55:43 +0800
Message-ID: <46713B1C.9010209@sg.panasonic.com>
Date: Thu, 14 Jun 2007 20:57:00 +0800
From: Benjamin Koh Tien-Ming <benjamin.kohtm@sg.panasonic.com>
User-Agent: Thunderbird 1.5.0.7 (Windows/20060909)
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: 14 Jun 2007 12:55:43.0877 (UTC)
	FILETIME=[51BF0350:01C7AE83]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d9238570526f12788af3d33c67f37625
Subject: [Monami6] MCoA Issue: Simultaneous Usage of Home and Away interfaces
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 had posted an email to the Monami6 mailing list proposing the adoption
of Section 7 of draft-wakikawa-mip6-no-ndp-00 as a working solution to
resolve the issue of simultaneous usage of home and away interfaces.

See:-
 http://www1.ietf.org/mail-archive/web/monami6/current/msg01051.html

A month has passed and there has been no negative responses. Some small
amount of support has also been expressed.  As such, I'm submitting the
following suggested changes to draft-ietf-monami6-multiplecoa-02.txt for
discussion and action.  The actual text has been heavily plagiarized
from draft-wakikawa-mip6-no-ndp-00.txt. (Apologies to authors)    ;-)

Changes:-

3.3.  Returning Home
"
   In the above two cases, a mobile node cannot use interfaces attached
   to both home and foreign links simultaneously.
<cut>
   If this is what a
   mobile node wants, a home agent can set up another link other than
   home link and uses the link for the mobile node to return virtually
   to home network.  Even though packets from and to the mobile node are
   routed via the home agent, the hop count is kept in one.  The
   overhead should be negligible since it is only for an additional IPv6
   header and processing tunnel (encapsulation and decapsulation) per
   packets.  The detail can be found in Figure 7
</cut>

<paste>
   This restriction is
   related to the Proxy NDP operation on a Home Agent.  The Home Agent
   needs to defend a mobile node's home address by the proxy NDP for
   packet interception, while the mobile node defends its home address
   by regular NDP to send and receive packets at the interface attached
   to the home link.  Two nodes, Home Agent and Mobile Node, compete ND
   state.  This will causes address duplication problem at the end.

   This document recommends not to use the Proxy NDP for this scenario.
   When one of the Mobile Node's interface is attached to the home link
   and the other is attached to the foreign link and it decides to
   utilize both interfaces, it notifies the Home Agent using the H flag
   which means the Mobile Node is attached to the home link. If the
   proxy NDP is disabled, the main problem can be solved.  In the
   Multiple Care-of Address Registration case, the elimination of Proxy
   NDP enable that Mobile Node and Home Agent maintain multiple
   bindings, one of the Mobile Node's interface is attached to the home
   link and the other is attached to the foreign link.
</paste>
"

4.2.1.  Binding Unique Identifier sub-option
"
<replace>
                      1                   2                   3
        0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
                                       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
                                       |   Type = TBD  |     Length    |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
       |     Binding Unique ID (BID)   |Priority/Status|C|O|H|Reserved |
       +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-------------------------------+
       +                                                               +
       +                    care-of address (CoA)                      +
       +                                                               +
       +---------------------------------------------------------------+
</replace>

<paste>
   Home Binding (H) flag
      When this flag is set, a home agent stores a Home Address in the
      Care-of Address field of the binding cache entry.  This flag must
      be used only for binding de-registration.  This flag is not used
      in the bulk registration mode.
</paste>

   Reserved

<replace>
      5 bits Reserved field.  Reserved field must be set with all 0.
</replace>
"

5.6.  Returning Home
"
   no longer receives packets at the interface attached to the home
   link.  All packets are routed to other interfaces attached to a
   foreign link.

<paste>
   Alternatively, the Mobile Node may choose to activate both the
   interfaces attached to the home link and the foreign link, and
   communicates with all of the interfaces.  The Mobile Node notifies
   the Home Agent using the H flag which means the Mobile Node is
   attached to the home link. The Home Agent then no longer
   uses Proxy Neighbor Advertisement to intercept packets and the Mobile
   Node can utilize both of interfaces attached to the home link and the
   foreign link simultaneously.  The Home Agent can intercept packets by
   IP routing, but not by proxy Neighbor Discovery.

   When the Mobile Node returns home, it de-registers a binding for the
   interface.  While the bindings for the interfaces attached to the
   foreign link are still active.  Intercepting packets, the Home Agent
   can decide whether it tunnels to the foreign interface or routes to
   the home interface of the Mobile Node.  To do so, the Home Agent must
   know that the Mobile Node is back to the home link.  However, if the
   binding is deleted according to [2], there is no way for the Home
   Agent to know that the Mobile Node is at the home, too.  The Home
   Agent SHOULD invalidate the binding for the interface attached to the
   home link and MAY NOT delete it.  It can alternatively mark that the
   Mobile Node is at the home link, too.  As an
   example, the Home Agent inserts the Home Address of the Mobile Node
   in the Care-of Address field of the Mobile Node.  The binding is
   named "Home Binding" in this doc.  The Home Agent MAY manage this
   home binding as same as the other binding entry in terms of lifetime
   validation, etc.  The Mobile Node MAY send multiple binding de-
   registration to keep this home binding active.  Alternatively, the
   Home Agent can use infinity lifetime for the lifetime of the home
   binding.  When the Mobile Node leaves the Home Link, it can update
   the home binding to the normal binding.  Before that, the Home Agent
   believes the Mobile Node is at the home and may route packets for the
   Mobile Node to the Home Link.
</paste>
"

6.3.  Processing Binding Update
"
   o  If the Lifetime field of the Binding Update is zero, the receiver
      node deletes the binding entry which BID is same as BID sent by
      the Binding Unique Identifier sub-option.  If the receiver node
      does not have appropriate binding which BID is matched with the
      Binding Update, it MUST reject this de-registration Binding
      Update.  If the receiver is a Home Agent, it SHOULD also return a
      Binding Acknowledgment to the mobile node, in which the Status
      field is set to [not Home Agent for this mobile node, 133].  If O
      flag is set in the deregistering Binding Update, the receiver can
      ignore this flag for deregistration.
<paste>
      If the H flag is set, the home agent stores a Home Address in the
      Care-of Address field of the binding cache entry.  The home agent
      no longer performs proxy NDP for this mobile node until this
      entry is deleted.
</paste>
"

Appendix A.  Example Configurations
"
<cut>
   Figure 7 depicts the scenario where interfaces of MN are attached to
   the foreign links.  One of foreign link is managed by the home agent.
   The HA and CN have the binding entries listed in Figure 7 in their
   binding cache database.  The home agent advertises a prefix which is
   other than home prefix.  The mobile node will generate a care-of
   address from the prefix and registers it to the home agent.  Even if
   the mobile node attaches to a foreign link, the link is managed by
   its home agent.  It will tunnel the packets to the home agent, but
   the home agent is one-hop neighbor.  The cost of tunnel is
   negligible.  If the mobile node wants to utilize not only an
   interface attached to home but also interfaces attached to foreign
   link, it can use this foreign link of the home agent to return a one
   hop foreign link on behalf of a home link.  This is different from
   the general returning home, but this enable the capability of using
   interfaces attached to both home and foreign link without any
   modifications to Mobile IPv6 and NEMO basic support.

                    +----+
                    | CN |
                    +--+-+
                       |
                   +---+------+          +----+
            +------+ Internet |----------+ HA |
            |      +----+-----+          ++-+-+
        CoA2|           |                 | |   Home Link
         +--+--+        |             ----|-+------
         |  MN +========+                 |
         +--+--+ CoA1                ---+-+------
       CoA3 |                           |  Foreign Link
            +---------------------------+

     Binding Cache Database:
        home agent's binding (Proxy neighbor advertisement is active)
              binding [a:b:c:d::EUI  care-of address1  BID1]
              binding [a:b:c:d::EUI  care-of address2  BID2]
              binding [a:b:c:d::EUI  care-of address3  BID3]
        correspondent node's binding
              binding [a:b:c:d::EUI  care-of address1  BID1]
              binding [a:b:c:d::EUI  care-of address2  BID2]
              binding [a:b:c:d::EUI  care-of address3  BID3]


    Figure 7: Emulating to Utilize Interfaces Attached to both Home and
                               Foreign Links
</cut>
"

Regards,
Ben


-- 


/<<<<<<<<<<<<<<<<<<<<++>>>>>>>>>>>>>>>>>>>>\
| Benjamin Koh Tien-Ming                   |
| R & D Engineer                           |
| Panasonic Singapore Laboratories Pte Ltd |
| Tel: (65)6550 5481 Fax: (65)6550 5459    |
| E-mail: benjamin.kohtm@sg.panasonic.com  |
\>>>>>>>>>>>>>>>>>>>>--<<<<<<<<<<<<<<<<<<<</


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



From monami6-bounces@ietf.org Thu Jun 14 21:34:47 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1Hz0i3-0007ry-6v; Thu, 14 Jun 2007 21:34:43 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1Hz0i2-0007rt-Dv
	for monami6@ietf.org; Thu, 14 Jun 2007 21:34:42 -0400
Received: from wa-out-1112.google.com ([209.85.146.180])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hz0i1-00059B-Bc
	for monami6@ietf.org; Thu, 14 Jun 2007 21:34:42 -0400
Received: by wa-out-1112.google.com with SMTP id j5so1056573wah
	for <monami6@ietf.org>; Thu, 14 Jun 2007 18:34:40 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta;
	h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=AbRozdyr1j5cFR9yW6gWYavdg3QXyPMopXloxw4+0hrcMEqPa6Gk9UmmF6V4vF3+QroaoJgabABrQlZSe+piVNsYIZx24m3dAT5vB1XV4COSmGfLIG3tv0nfMJSql/5jhD2nbtfoMv9lKpcqQSo+wFkwXMt2+LnL/EAeR07wxvs=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:in-reply-to:references:mime-version:content-type:message-id:content-transfer-encoding:from:subject:date:to:x-mailer;
	b=L2YC2gt3ffBNdFePC9kTHQYLjeESrrbCpgX3E+FdH9GnT5aL+MUfyTlwWqSRi/8rJ2pmhYvXEcEtDpS8ND1aYMK0FlebAJCwBW9mIXy7MqcCoXB4CurGu3bjy0dfZAj0UYWScRmSEx7i9CnPc0g+DkVz737vl2BXjdipKT+l+TA=
Received: by 10.115.54.1 with SMTP id g1mr2401596wak.1181871280551;
	Thu, 14 Jun 2007 18:34:40 -0700 (PDT)
Received: from ?121.134.255.188? ( [121.134.255.188])
	by mx.google.com with ESMTP id d20sm3385505waa.2007.06.14.18.34.38
	(version=TLSv1/SSLv3 cipher=OTHER);
	Thu, 14 Jun 2007 18:34:39 -0700 (PDT)
In-Reply-To: <46713B1C.9010209@sg.panasonic.com>
References: <46713B1C.9010209@sg.panasonic.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0EDE1EFB-892E-4F75-9A6D-7D31CAC2A475@gmail.com>
Content-Transfer-Encoding: 7bit
From: RYUJI WAKIKAWA <ryuji.wakikawa@gmail.com>
Subject: Re: [Monami6] MCoA Issue: Simultaneous Usage of Home and Away
	interfaces
Date: Fri, 15 Jun 2007 10:34:34 +0900
To: Monami6 WG <monami6@ietf.org>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d2fdecab7a7fa796e06e001d026c91
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 All,

Thanks for Benjamin.
I am revising the MCoA draft for the IETF Chicago now.
It looks there is no objection on this changes, i plan to include  
this option.

regards,
ryuji



On 2007/06/14, at 21:57, Benjamin Koh Tien-Ming wrote:

> Hi!
>
> I had posted an email to the Monami6 mailing list proposing the  
> adoption
> of Section 7 of draft-wakikawa-mip6-no-ndp-00 as a working solution to
> resolve the issue of simultaneous usage of home and away interfaces.
>
> See:-
>  http://www1.ietf.org/mail-archive/web/monami6/current/msg01051.html
>
> A month has passed and there has been no negative responses. Some  
> small
> amount of support has also been expressed.  As such, I'm submitting  
> the
> following suggested changes to draft-ietf-monami6- 
> multiplecoa-02.txt for
> discussion and action.  The actual text has been heavily plagiarized
> from draft-wakikawa-mip6-no-ndp-00.txt. (Apologies to authors)    ;-)
>
> Changes:-
>
> 3.3.  Returning Home
> "
>    In the above two cases, a mobile node cannot use interfaces  
> attached
>    to both home and foreign links simultaneously.
> <cut>
>    If this is what a
>    mobile node wants, a home agent can set up another link other than
>    home link and uses the link for the mobile node to return virtually
>    to home network.  Even though packets from and to the mobile  
> node are
>    routed via the home agent, the hop count is kept in one.  The
>    overhead should be negligible since it is only for an additional  
> IPv6
>    header and processing tunnel (encapsulation and decapsulation) per
>    packets.  The detail can be found in Figure 7
> </cut>
>
> <paste>
>    This restriction is
>    related to the Proxy NDP operation on a Home Agent.  The Home Agent
>    needs to defend a mobile node's home address by the proxy NDP for
>    packet interception, while the mobile node defends its home address
>    by regular NDP to send and receive packets at the interface  
> attached
>    to the home link.  Two nodes, Home Agent and Mobile Node,  
> compete ND
>    state.  This will causes address duplication problem at the end.
>
>    This document recommends not to use the Proxy NDP for this  
> scenario.
>    When one of the Mobile Node's interface is attached to the home  
> link
>    and the other is attached to the foreign link and it decides to
>    utilize both interfaces, it notifies the Home Agent using the H  
> flag
>    which means the Mobile Node is attached to the home link. If the
>    proxy NDP is disabled, the main problem can be solved.  In the
>    Multiple Care-of Address Registration case, the elimination of  
> Proxy
>    NDP enable that Mobile Node and Home Agent maintain multiple
>    bindings, one of the Mobile Node's interface is attached to the  
> home
>    link and the other is attached to the foreign link.
> </paste>
> "
>
> 4.2.1.  Binding Unique Identifier sub-option
> "
> <replace>
>                       1                   2                   3
>         0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9  
> 0 1
>                                        +-+-+-+-+-+-+-+-+-+-+-+-+-+- 
> +-+-+
>                                        |   Type = TBD  |      
> Length    |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 
> +-+-+
>        |     Binding Unique ID (BID)   |Priority/Status|C|O|H| 
> Reserved |
>        +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 
> +-------------------------------+
>         
> +                                                               +
>        +                    care-of address  
> (CoA)                      +
>         
> +                                                               +
>         
> +---------------------------------------------------------------+
> </replace>
>
> <paste>
>    Home Binding (H) flag
>       When this flag is set, a home agent stores a Home Address in the
>       Care-of Address field of the binding cache entry.  This flag  
> must
>       be used only for binding de-registration.  This flag is not used
>       in the bulk registration mode.
> </paste>
>
>    Reserved
>
> <replace>
>       5 bits Reserved field.  Reserved field must be set with all 0.
> </replace>
> "
>
> 5.6.  Returning Home
> "
>    no longer receives packets at the interface attached to the home
>    link.  All packets are routed to other interfaces attached to a
>    foreign link.
>
> <paste>
>    Alternatively, the Mobile Node may choose to activate both the
>    interfaces attached to the home link and the foreign link, and
>    communicates with all of the interfaces.  The Mobile Node notifies
>    the Home Agent using the H flag which means the Mobile Node is
>    attached to the home link. The Home Agent then no longer
>    uses Proxy Neighbor Advertisement to intercept packets and the  
> Mobile
>    Node can utilize both of interfaces attached to the home link  
> and the
>    foreign link simultaneously.  The Home Agent can intercept  
> packets by
>    IP routing, but not by proxy Neighbor Discovery.
>
>    When the Mobile Node returns home, it de-registers a binding for  
> the
>    interface.  While the bindings for the interfaces attached to the
>    foreign link are still active.  Intercepting packets, the Home  
> Agent
>    can decide whether it tunnels to the foreign interface or routes to
>    the home interface of the Mobile Node.  To do so, the Home Agent  
> must
>    know that the Mobile Node is back to the home link.  However, if  
> the
>    binding is deleted according to [2], there is no way for the Home
>    Agent to know that the Mobile Node is at the home, too.  The Home
>    Agent SHOULD invalidate the binding for the interface attached  
> to the
>    home link and MAY NOT delete it.  It can alternatively mark that  
> the
>    Mobile Node is at the home link, too.  As an
>    example, the Home Agent inserts the Home Address of the Mobile Node
>    in the Care-of Address field of the Mobile Node.  The binding is
>    named "Home Binding" in this doc.  The Home Agent MAY manage this
>    home binding as same as the other binding entry in terms of  
> lifetime
>    validation, etc.  The Mobile Node MAY send multiple binding de-
>    registration to keep this home binding active.  Alternatively, the
>    Home Agent can use infinity lifetime for the lifetime of the home
>    binding.  When the Mobile Node leaves the Home Link, it can update
>    the home binding to the normal binding.  Before that, the Home  
> Agent
>    believes the Mobile Node is at the home and may route packets  
> for the
>    Mobile Node to the Home Link.
> </paste>
> "
>
> 6.3.  Processing Binding Update
> "
>    o  If the Lifetime field of the Binding Update is zero, the  
> receiver
>       node deletes the binding entry which BID is same as BID sent by
>       the Binding Unique Identifier sub-option.  If the receiver node
>       does not have appropriate binding which BID is matched with the
>       Binding Update, it MUST reject this de-registration Binding
>       Update.  If the receiver is a Home Agent, it SHOULD also  
> return a
>       Binding Acknowledgment to the mobile node, in which the Status
>       field is set to [not Home Agent for this mobile node, 133].   
> If O
>       flag is set in the deregistering Binding Update, the receiver  
> can
>       ignore this flag for deregistration.
> <paste>
>       If the H flag is set, the home agent stores a Home Address in  
> the
>       Care-of Address field of the binding cache entry.  The home  
> agent
>       no longer performs proxy NDP for this mobile node until this
>       entry is deleted.
> </paste>
> "
>
> Appendix A.  Example Configurations
> "
> <cut>
>    Figure 7 depicts the scenario where interfaces of MN are  
> attached to
>    the foreign links.  One of foreign link is managed by the home  
> agent.
>    The HA and CN have the binding entries listed in Figure 7 in their
>    binding cache database.  The home agent advertises a prefix  
> which is
>    other than home prefix.  The mobile node will generate a care-of
>    address from the prefix and registers it to the home agent.   
> Even if
>    the mobile node attaches to a foreign link, the link is managed by
>    its home agent.  It will tunnel the packets to the home agent, but
>    the home agent is one-hop neighbor.  The cost of tunnel is
>    negligible.  If the mobile node wants to utilize not only an
>    interface attached to home but also interfaces attached to foreign
>    link, it can use this foreign link of the home agent to return a  
> one
>    hop foreign link on behalf of a home link.  This is different from
>    the general returning home, but this enable the capability of using
>    interfaces attached to both home and foreign link without any
>    modifications to Mobile IPv6 and NEMO basic support.
>
>                     +----+
>                     | CN |
>                     +--+-+
>                        |
>                    +---+------+          +----+
>             +------+ Internet |----------+ HA |
>             |      +----+-----+          ++-+-+
>         CoA2|           |                 | |   Home Link
>          +--+--+        |             ----|-+------
>          |  MN +========+                 |
>          +--+--+ CoA1                ---+-+------
>        CoA3 |                           |  Foreign Link
>             +---------------------------+
>
>      Binding Cache Database:
>         home agent's binding (Proxy neighbor advertisement is active)
>               binding [a:b:c:d::EUI  care-of address1  BID1]
>               binding [a:b:c:d::EUI  care-of address2  BID2]
>               binding [a:b:c:d::EUI  care-of address3  BID3]
>         correspondent node's binding
>               binding [a:b:c:d::EUI  care-of address1  BID1]
>               binding [a:b:c:d::EUI  care-of address2  BID2]
>               binding [a:b:c:d::EUI  care-of address3  BID3]
>
>
>     Figure 7: Emulating to Utilize Interfaces Attached to both Home  
> and
>                                Foreign Links
> </cut>
> "
>
> Regards,
> Ben
>
>
> -- 
>
>
> /<<<<<<<<<<<<<<<<<<<<++>>>>>>>>>>>>>>>>>>>>\
> | Benjamin Koh Tien-Ming                   |
> | R & D Engineer                           |
> | Panasonic Singapore Laboratories Pte Ltd |
> | Tel: (65)6550 5481 Fax: (65)6550 5459    |
> | E-mail: benjamin.kohtm@sg.panasonic.com  |
> \>>>>>>>>>>>>>>>>>>>>--<<<<<<<<<<<<<<<<<<<</
>
>
> _______________________________________________
> 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 Jun 18 18:02:34 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0PIv-00028j-70; Mon, 18 Jun 2007 18:02:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0PIs-00028R-FL; Mon, 18 Jun 2007 18:02:30 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I0PIp-00081z-Iv; Mon, 18 Jun 2007 18:02:30 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id B829D1986A7;
	Tue, 19 Jun 2007 01:02:26 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 4A34F1986A6;
	Tue, 19 Jun 2007 01:02:26 +0300 (EEST)
Message-ID: <467700F2.4060204@piuha.net>
Date: Tue, 19 Jun 2007 01:02:26 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Mobile IPv6 Mailing List <mip6@ietf.org>, IETF NEMO WG <nemo@ietf.org>,
	Monami6 WG <monami6@ietf.org>
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: 5fb88b8381f3896aeacc5a021513237b
Cc: 
Subject: [Monami6] Merged WG charter
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Mobile IPv6 Mailing List <mip6@ietf.org>,
	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 all,

Please find below the first draft charter for the merged
WG. Comments appreciated.

Note that the charter has changed only in terms of merging
material from the three working groups into one, shortening
the text here and there, and removing completed items. I've
taken bootstrapping away as a completed item even if we are
still a few weeks away from sending the last document (the
option) to the IESG.

Replies set to mip6 list.

Jari

----

Mobility EXTensions for IPv6 (MEXT)

Chair(s):
TBD

Internet Area Director(s):
Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Mailing Lists:
TBD

Description of Working Group:

Mobile IPv6 specifies routing support which permits an IPv6 host to
continue using its home address as it moves around the Internet,
enabling continuity of sessions. Mobile IPv6 supports transparency
above the IP layer, including maintenance of active transport level
sessions. In addition, NEMO network mobility mechanisms built on top
of Mobile IPv6 allow managing the mobility of an entire network, as it
changes its point of attachment to the Internet. The base
specifications consist of:

o RFC 3775
o RFC 3776
o RFC 3963

The primary goal of the MEXT working group will be to enhance base
IPv6 mobility by continuing work on developments that are required for
wide-scale deployments and specific deployment scenarios
(A). Additionally the working group will ensure that any issues
identified by implementation and interoperability experience are
addressed, and that the base specifications are maintained (B). The
group will also produce informational documentation, such as design
rationale documents or description of specific issues within the
protocol (C).

Deployment considerations call for solutions to enable
dual-stack operation (A.1), allow the use of multiple interfaces in
mobile nodes (A.2), mechanisms to support high-availabity home agents
(A.3), and ways to employ Mobile IPv6 in the presence of firewalls
(A.4). In addition, there are specific needs of the automotive and
aviation communities with regards to route optimization of network
mobility (A.5).

Work items related to large scale deployment include:

(A.1) A Solution for MIP6 session continuity for dual stack hosts which
      attach to IPv4 access networks. Additionally provide a mechanism
      for carrying IPv4 packets via the Home agent for MIP6 capable
      dual-stack hosts.

(A.2) A protocol based solution for enhancing the reliability of home
      agents and a method to force a host to switch home agents.

      A mechanism to force an MN to switch the HA that is currently
      serving it. This is required in deployments where the HA may need to
      be taken offline for maintenance.

(A.3) Use of multiple interfaces.
    
      The protocols do not today provide support for simultaneous
      differentiated use of multiple access technologies, although
      several proposals exist for such support, and some of them have
      been implemented and tested.
    
      When a mobile host/router uses multiple network interfaces
      simultaneously, or when multiple prefixes are available on a
      single network interface, the mobile host/router would end up
      with multiple Care-of Addresses (CoAs). In addition, the Home
      Agent might be attached to multiple network interfaces, or to a
      single network interface with multiple prefixes, hence resulting
      in the option to use multiple IP addresses for the Home
      Agent. This could result in the possibility of using a multitude
      of bi-directional tunnels between pairs of {Home Agent address,
      CoA} and a number of associated issues: establishment, selection
      and modification of multiple simultaneous tunnels.
    
      The objective of the WG is to produce a clear problem statement
      and to produce standard track specifications to the problems
      associated with the simultaneous use of multiple addresses for
      either mobile hosts using Mobile IPv6 or mobile routers using
      NEMO Basic Support and their variants (FMIPv6, HMIPv6,
      etc). Where the effects of having multiple prefixes on a single
      interface is identical to the effects of having multiple
      interfaces each with a single prefix, the WG will consider a
      generalized approach to cater for multiple prefixes available to
      a mobile host/router.
    
      The WG does not plan to define a tunnel selection mechanism, but
      may document how to use existing mechanisms based upon
      preferences or policies. In particular, the WG will consider
      that a tunnel is alive as long as packets can be exchanged with
      the corresponding peer. In addition, local information, such as
      interface up/down events, or other failure detection mechanisms
      can be used to quickly detect failure of tunnel(s).
    
      Deliverables related to this include
    
      - A document explaining the motivations for a node using multiple
        interfaces and the scenarios where it may end up with multiple
        global addresses on its interfaces [Informational]
    
      - An analysis document explaining what are the limitations for
        mobile hosts using multiple simultaneous Care-of Addresses and Home
        Agent addresses using Mobile IPv6, whether issues are specific to
        Mobile IPv6 or not [Informational].
    
      - A protocol extension to support the registration of multiple
        Care-of Addresses at a given Home Agent address [Standard
        Track].
    
      - A "Flow/binding policies exchange" solution for an exchange of
        policies from the mobile host/router to the Home Agent and from the
        Home Agent to the mobile host/router influencing the choice of the
        Care-of Address and Home Agent address [Standard Track].

(A.4) Work on solutions to deal with firewalls and the problems that
      firewalls cause as identified in RFC 4487.

(A.5) Route optimization of network mobility.

      Three use cases have been identified for this. These are called
      the Aviation case, the Automotive case, and the Personal Mobile
      Router (consumer electronics) case, though the actual technical
      problems are characterized by the type of movements and
      environments more than by the specific industry using the
      technology. The group will explore these cases to gather
      requirements and proceed with solving the open issues.
    
      (1) Airline and spacecraft community, who are deploying NEMO for
      control systems, as well as Internet connectivity and
      entertainment systems. This use case is characterized by fast (~
      1000 km/h) moving objects over large distances (across
      continents). The main technical problem is that tunneling-based
      solutions imply a roundtrip to another continent and that BGP
      based solutions imply significant churn in the global Internet
      routing table.
    
      (2) Automotive industry who are deploying NEMO for in-car
      communication, entertainment, and data gathering, possible
      control systems use, and communication to roadside devices. This
      use case is characterized by moderately fast (~ 100-300 km/h)
      moving objects that employ local or cellular networks for
      connectivity.
    
      (3) Personal Mobile Routers, which are consumer devices that
      allow the user to bring a NEMO network with the user while
      mobile, and communicate with peer NEMO networks/MNNs.
    
      After gathering the requirements for these types of deployments,
      the working group will evaluate what type of route optimization
      needs to be performed (if any), and formulate a solution to
      those problems.
    
      If no requirements for those scenarios can be collected by the
      deadline, it will be assumed that the work is premature, and
      that type of deployment will be dropped from the WG.
    
      The group will only consider airline and spacecraft solutions
      that combine tunneling solutions for small movements with either
      federated tunnel servers or slowly changing end host prefixes.
      The group will only consider personal mobile router requirements
      about optimized routes to another mobile router belonging to the
      same operator. The group will only consider automotive industry
      requirements to allow MR-attached hosts to directly access the
      network where MR has attached to. Work on automotive and
      personal mobile router solutions requires rechartering.
    
      The WG will not consider routing issues inside the mobile
      network. Existing routing protocols (including MANET protocols)
      can be used to solve these problems. The group will also not
      consider general route optimization, multihoming, or other
      problems that are not related to the deployment and maintenance
      of NEMO networks. Similarly, the group will not consider or rely
      on the results of general routing architecture, Internet
      architecture, or identifier-locator split issues that are
      discussed in separate, long term efforts elsewhere in the
      IETF. Finally, the group will not consider solutions that
      require changes from correspondent nodes in the general Internet


Work items related to base specification maintenance include:

(B.1) Create and maintain issue lists that are generated on the basis
      of implementation and interoperability experience. Address
      specific issues with specific updates or revisions of the base
      specification. One specific area of concern that should be
      analyzed and addressed relates to multilink subnets.

      This work item relates only to corrections and
      clarifications. The working group shall not revisit design
      decisions or change the protocol.

(B.2) Update the IANA considerations of RFC 3775 to allow extensions for
      experimental purposes as well passing of optional vendor-specific
      information.

(B.3) Finish working group documents that are currently in process, and
      submit for RFC. This includes prefix delegation protocol mechanism
      for network mobility, and a MIB for NEMO Basic Support.


Work items related to informational documentation include:

(C.1) Produce a design rationale that documents the historical
      thinking behind the introduction of an alternative security
      mechanism, the Authentication Protocol (RFC 4285).


Goals and Milestones:


Jul 2007	Submit -00 draft on Route Optimization Needs for Aircraft and Spacecraft Deployments
Jul 2007	Submit -00 draft on Route Optimization Needs for Automobile and Highway Deployments
Jul 2007	Submit -00 draft on Route Optimization needs for Personal Mobile Router
Aug 2007	Submit Multiple CoA Registration to IESG
Aug 2007	Submit I-D 'Motivation for Authentication I-D' to IESG for publication as Informational.
Aug 2007	Submit I-D 'Goals for AAA HA Interface' to IESG for publication as Informational.
Sep 2007	Submit I-D 'Mobility Header Home Agent Switch Message' to IESG for publication as a Proposed Standard.
Sep 2007	Submit Analysis of the use of Multiple Simultaneous Care-of Addresses and Home Agent addresses in Mobile IPv6
Sep 2007	Submit -00 draft for solution to aircraft/spacecraft problem
Sep 2007	Submit I-D 'Home agent reliability' to IESG for publication as a Proposed Standard.
Sep 2007	Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for publication as a Proposed Standard.
Oct 2007	Submit Multiple Interfaces Motivations and Scenario to IESG, for Informational
Oct 2007	Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for publication as a Proposed Standard
Nov 2007	Submit final doc on Route Optimization Needs for Aircraft and Spacecraft Deployments, for Informational
Nov 2007	Submit final doc on Route Optimization Needs for Automobile and Highway Deployments, for Informational
Nov 2007	Submit final doc on Route Optimization needs for Personal Mobile Router, for Informational
Dec 2007	Determine how to proceed with remaining automotive/Personal Mobile Router solutions
Dec 2007	Recharter to work on the remaining automotive/Personal Mobile Router solutions
Dec 2007	Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG for publication as a Proposed Standard.
Dec 2007	Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for publication as a proposed standard.
Dec 2007	Submit the final doc on MIB for NEMO Basic Support to the IESG, for Proposed Standard
Dec 2007	Submit the final doc on Prefix Delegation for NEMO to the IESG, for Proposed Standard
Feb 2008	Submit final doc for solution to aircraft/spacecraft problem to the IESG, for Proposed Standard
Feb 2008	Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG for publication as Informational.
Feb 2008	Submit I-D(s) related to specific updates and corrections of RFC 3775 to IESG for publication as Proposed Standard. 
Mar 2008	Submit Flow/binding policies exchange to IESG



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



From monami6-bounces@ietf.org Mon Jun 18 22:34:24 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0TXz-0002Lq-PD; Mon, 18 Jun 2007 22:34:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I0TXy-0002LZ-3Y; Mon, 18 Jun 2007 22:34:22 -0400
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I0TXw-0004JV-Gr; Mon, 18 Jun 2007 22:34:22 -0400
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
	l5J2YHS1016634; Tue, 19 Jun 2007 11:34:17 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx2) with ESMTP id
	l5J2YIt19206; Tue, 19 Jun 2007 11:34:18 +0900 (JST)
Received: from pslexc01.psl.local (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/indians) with ESMTP id
	l5J2YE710011; Tue, 19 Jun 2007 11:34:15 +0900 (JST)
Received: from NW-Sephiroth ([10.81.113.103]) by pslexc01.psl.local with
	Microsoft SMTPSVC(6.0.3790.1830); Tue, 19 Jun 2007 10:32:48 +0800
Received: from NWSephiroth by NW-Sephiroth (PGP Universal service);
	Tue, 19 Jun 2007 10:32:44 +0800
X-PGP-Universal: processed; by NW-Sephiroth on Tue, 19 Jun 2007 10:32:44 +0800
From: "Benjamin Lim" <benjamin.limck@sg.panasonic.com>
To: "'Mobile IPv6 Mailing List'" <mip6@ietf.org>,
	"'Monami6 WG'" <monami6@ietf.org>, "'IETF NEMO WG'" <nemo@ietf.org>
References: <467700F2.4060204@piuha.net>
In-Reply-To: <467700F2.4060204@piuha.net>
Subject: RE: [Monami6] Merged WG charter
Date: Tue, 19 Jun 2007 10:32:38 +0800
Organization: Panasonic Singapore Labs Pte Ltd
Message-ID: <010b01c7b21a$1a7111a0$4f5334e0$@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: Acex9DFDjINqk7bUQdmMFdjiMw6ajwAIZsHw
Content-Language: en-us
X-OriginalArrivalTime: 19 Jun 2007 02:32:48.0111 (UTC)
	FILETIME=[201E77F0:01C7B21A]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: 
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,

I snip points for comments.

[snip] from (A.3) Use of multiple interfaces.
>
>       The objective of the WG is to produce a clear problem statement
>       and to produce standard track specifications to the problems
>       associated with the simultaneous use of multiple addresses for
>       either mobile hosts using Mobile IPv6 or mobile routers using
>       NEMO Basic Support and their variants (FMIPv6, HMIPv6,
>       etc). Where the effects of having multiple prefixes on a single
>       interface is identical to the effects of having multiple
>       interfaces each with a single prefix, the WG will consider a
>       generalized approach to cater for multiple prefixes available to
>       a mobile host/router.
[/snip]

[snip] from (A.5) Route optimization of network mobility.
>
>       The WG will not consider routing issues inside the mobile
>       network. Existing routing protocols (including MANET protocols)
>       can be used to solve these problems. The group will also not
>       consider general route optimization, multihoming, or other
>       problems that are not related to the deployment and maintenance
>       of NEMO networks....
[/snip]

I feel that there is a conflict between A.3 and A.5. From my interpretation,
A.3 mentions that the WG will consider multi-homing w.r.t multiple
interfaces for mobile host/routers. However, in A.5, it is said that WG will
NOT consider multi-homing that are not related to NEMO. Suggest removing the
restriction of multi-homing consideration from A.5.

Regards,
Benjamin Lim



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



From monami6-bounces@ietf.org Wed Jun 20 14:17:38 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I14kM-0000Gc-6B; Wed, 20 Jun 2007 14:17:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I14kK-0000Fw-FD; Wed, 20 Jun 2007 14:17:36 -0400
Received: from ndjsbar01.ndc.nasa.gov ([198.120.25.38])
	by ietf-mx.ietf.org with esmtp (Exim 4.43)
	id 1I14kI-00062o-OO; Wed, 20 Jun 2007 14:17:36 -0400
Received: from ndjsxgw02.ndc.nasa.gov (ndjsxgw02.ndc.nasa.gov [129.166.32.112])
	by ndjsbar01.ndc.nasa.gov (Spam Firewall) with ESMTP
	id 84D77375298; Wed, 20 Jun 2007 13:17:33 -0500 (CDT)
Received: from NDJSEVS23A.ndc.nasa.gov ([129.166.32.223]) by
	ndjsxgw02.ndc.nasa.gov with Microsoft SMTPSVC(6.0.3790.1830); 
	Wed, 20 Jun 2007 13:17:33 -0500
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Monami6] Merged WG charter
Date: Wed, 20 Jun 2007 13:17:01 -0500
Message-ID: <A3A356E39B867E4380966B0EB600C28F21CB72@NDJSEVS23A.ndc.nasa.gov>
In-Reply-To: <010b01c7b21a$1a7111a0$4f5334e0$@limck@sg.panasonic.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Monami6] Merged WG charter
Thread-Index: Acex9DFDjINqk7bUQdmMFdjiMw6ajwAIZsHwAFP7PJA=
References: <467700F2.4060204@piuha.net>
	<010b01c7b21a$1a7111a0$4f5334e0$@limck@sg.panasonic.com>
From: "Ivancic, William D. (GRC-RCN0)" <william.d.ivancic@nasa.gov>
To: <benjamin.limck@sg.panasonic.com>, "Monami6 WG" <monami6@ietf.org>,
	"Mobile IPv6 Mailing List" <mip6@ietf.org>, "IETF NEMO WG" <nemo@ietf.org>
X-OriginalArrivalTime: 20 Jun 2007 18:17:33.0389 (UTC)
	FILETIME=[459737D0:01C7B367]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
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

I agree with Benjamin.  I think I understand what is implied by A.5 in
that we only should be addressing NEMO specific items.  Perhaps is
should read as:


"The WG will not consider routing issues inside the mobile network.
Existing routing protocols (including MANET protocols)can be used to
solve these problems. The group will also not consider problems that are
not directly related to the deployment and maintenance of NEMO
networks...."

Or=20

"The WG will not consider routing issues inside the mobile network.
Existing routing protocols (including MANET protocols)can be used to
solve these problems. The group will also not consider general route
optimization, site multihoming, or other problems that are not directly
related to the deployment and  maintenance of NEMO networks...."

Here, "site multihoming" is meant to mean items associated with shim6.

I am assuming that monami6 issues related to multihoming are withing the
bounds of the MEXT working group. =20


Regards,


Will Ivancic
NASA=20



> -----Original Message-----
> From: Benjamin Lim [mailto:benjamin.limck@sg.panasonic.com]=20
> Sent: Monday, June 18, 2007 10:33 PM
> To: 'Mobile IPv6 Mailing List'; 'Monami6 WG'; 'IETF NEMO WG'
> Subject: RE: [Monami6] Merged WG charter
>=20
> Hi,
>=20
> I snip points for comments.
>=20
> [snip] from (A.3) Use of multiple interfaces.
> >
> >       The objective of the WG is to produce a clear problem=20
> statement
> >       and to produce standard track specifications to the problems
> >       associated with the simultaneous use of multiple addresses for
> >       either mobile hosts using Mobile IPv6 or mobile routers using
> >       NEMO Basic Support and their variants (FMIPv6, HMIPv6,
> >       etc). Where the effects of having multiple prefixes=20
> on a single
> >       interface is identical to the effects of having multiple
> >       interfaces each with a single prefix, the WG will consider a
> >       generalized approach to cater for multiple prefixes=20
> available to
> >       a mobile host/router.
> [/snip]
>=20
> [snip] from (A.5) Route optimization of network mobility.
> >
> >       The WG will not consider routing issues inside the mobile
> >       network. Existing routing protocols (including MANET=20
> protocols)
> >       can be used to solve these problems. The group will also not
> >       consider general route optimization, multihoming, or other
> >       problems that are not related to the deployment and=20
> maintenance
> >       of NEMO networks....
> [/snip]
>=20
> I feel that there is a conflict between A.3 and A.5. From my=20
> interpretation,
> A.3 mentions that the WG will consider multi-homing w.r.t=20
> multiple interfaces for mobile host/routers. However, in A.5,=20
> it is said that WG will NOT consider multi-homing that are=20
> not related to NEMO. Suggest removing the restriction of=20
> multi-homing consideration from A.5.
>=20
> Regards,
> Benjamin Lim
>=20
>=20
>=20
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6
>=20

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



From monami6-bounces@ietf.org Fri Jun 22 08:10:01 2007
Return-path: <monami6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I1hxd-0005Ox-TG; Fri, 22 Jun 2007 08:09:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I1hxc-0005Os-Gw
	for monami6@ietf.org; Fri, 22 Jun 2007 08:09:56 -0400
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 1I1hxa-0002yT-Ot
	for monami6@ietf.org; Fri, 22 Jun 2007 08:09:56 -0400
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 l5MC9n81006498
	for <monami6@ietf.org>; Fri, 22 Jun 2007 14:09:49 +0200
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/2007.03.20) with
	ESMTP id l5MC9kZw006483
	for <monami6@ietf.org>; Fri, 22 Jun 2007 14:09:46 +0200
Received: from [10.76.158.56] ([213.223.93.185]) (authenticated bits=0)
	by l2.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id
	l5MC9Ydg009468
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <monami6@ietf.org>; Fri, 22 Jun 2007 14:09:43 +0200
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Transfer-Encoding: 7bit
Message-Id: <330CD69F-254F-40A0-A225-0FA085D01476@enst-bretagne.fr>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
To: Monami6 WG <monami6@ietf.org>
From: Nicolas Montavont <nicolas.montavont@enst-bretagne.fr>
Date: Fri, 22 Jun 2007 14:08:39 +0200
X-Mailer: Apple Mail (2.752.3)
X-Virus-Scanned: amavisd-new at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Subject: [Monami6] timeslot at IETF 69
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

Dear all,

We have reserved a 1.5 hours slot at the next IETF.
In order to prepare the Monami6 agenda for IETF 69, if you want to  
present your work, can you please send us an email with the following  
details :

1. I-D name
2. How does it fit in the scope of the Monami6 charter
3. Time requested

Regards,
Nicolas

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



From mext-bounces@ietf.org Mon Jun 25 08:48:46 2007
Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I2nzf-0002E1-Pr; Mon, 25 Jun 2007 08:48:35 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I2nze-0002Dw-5f
	for mext@ietf.org; Mon, 25 Jun 2007 08:48:34 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I2nzb-0000ay-GS
	for mext@ietf.org; Mon, 25 Jun 2007 08:48:34 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id AB9551986A6
	for <mext@ietf.org>; Mon, 25 Jun 2007 15:48:30 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 5E7A219868B
	for <mext@ietf.org>; Mon, 25 Jun 2007 15:48:30 +0300 (EEST)
Message-ID: <467FB99E.3000105@piuha.net>
Date: Mon, 25 Jun 2007 15:48:30 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: mext@ietf.org
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: 9e5c23589e6cce06555030c0194c9e2b
Subject: [MEXT] new charter version
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org

Testing the new list... this list should have all the subscribers
of the existing three lists. For now, please continue your
technical discussions in the existing lists, except for charter
discussion which we can move here. In general, you do not
need to take any action with regards to list changes, once
we are ready to move complete away from the old lists we
can deal with the from the secretariat. Here's a pointer
to the list page:

   https://www1.ietf.org/mailman/listinfo/mext

Here's the new charter, revised according to comments
from many of you (thanks!) and the rest of the IESG.

The charter will go out soon for public IETF review.

------

Mobility EXTensions for IPv6 (MEXT)

Chair(s):
TBD

Internet Area Director(s):
Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Mailing Lists:
https://www1.ietf.org/mailman/listinfo/mext
http://www1.ietf.org/mail-archive/web/mext/current/index.html


Description of Working Group:

Mobile IPv6 specifies routing support which permits an IPv6 host to
continue using its home address as it moves around the Internet,
enabling continuity of sessions. Mobile IPv6 supports transparency
above the IP layer, including maintenance of active transport level
sessions. In addition, NEMO network mobility mechanisms built on top
of Mobile IPv6 allow managing the mobility of an entire network, as it
changes its point of attachment to the Internet. The base
specifications consist of:

o RFC 3775
o RFC 3963
o RFC 4877

The MEXT Working Group continues the work of the MIP6, NEMO, and
MONAMI6 Working Groups.

The primary goal of MEXT will be to (A) enhance base IPv6 mobility by
continuing work on developments that are required for wide-scale
deployments and specific deployment scenarios.  Additionally, (B) the
working group will ensure that any issues identified by implementation
and interoperability experience are addressed, and that the base
specifications are maintained. (C) The group will also produce
informational documentation, such as design rationale documents or
description of specific issues within the protocol.

Deployment considerations call for (A.1) solutions to enable
dual-stack operation, (A.2) allowing the use of multiple interfaces in
mobile nodes, (A.3) mechanisms to support high-availability home
agents, (A.4) ways to employ Mobile IPv6 in the presence of firewalls,
(A.5) address the specific needs of automotive and aviation
communities for route optimisation in network mobility, and (A.6)
support for AAA is needed as a continuation of earlier work on
bootstrapping.

Work items related to large scale deployment include:

(A.1) A Solution for MIP6 session continuity for dual stack hosts which
      attach to IPv4 access networks. Additionally provide a mechanism
      for carrying IPv4 packets via the Home agent for MIP6 capable
      dual-stack hosts.

(A.2) A protocol based solution for enhancing the reliability of home
      agents and a method to force a host to switch home agents.

      A mechanism to force an MN to switch the HA that is currently
      serving it. This is required in deployments where the HA needs to
      be taken offline for maintenance.

(A.3) Use of multiple interfaces.

      Today, the protocols do not provide suppport for simultaneous
      differentiated use of multiple access technologies. Several
      proposals exist for such support, and some of them have been
      implemented and tested.
   
      When a mobile host/router uses multiple network interfaces
      simultaneously, or when multiple prefixes are available on a
      single network interface, the mobile host/router would end up
      with multiple Care-of Addresses (CoAs). In addition, the Home
      Agent might be attached to multiple network interfaces, or to a
      single network interface with multiple prefixes, hence resulting
      in the option to use multiple IP addresses for the Home
      Agent. This could result in the possibility of using a multitude
      of bi-directional tunnels between pairs of {Home Agent address,
      CoA} and a number of associated issues: establishment, selection
      and modification of multiple simultaneous tunnels.
   
      The objective of the WG is to produce a clear problem statement
      and to produce standard track specifications to the problems
      associated with the simultaneous use of multiple addresses for
      either mobile hosts using Mobile IPv6 or mobile routers using
      NEMO Basic Support and their variants (FMIPv6, HMIPv6,
      etc). Where the effects of having multiple prefixes on a single
      interface is identical to the effects of having multiple
      interfaces each with a single prefix, the WG will consider a
      generalized approach to cater for multiple prefixes available to
      a mobile host/router.

      The WG uses existing tunneling mechanisms defined for Mobile
      IPv6. The involved nodes need to select which tunnel instance
      to use when multiple ones are available due to multiple
      addresses on either end. But the WG does not plan to define a
      new mechanism for this, but rather document how to use existing
      mechanisms based upon preferences or policies. In particular,
      the WG will consider that a tunnel is alive as long as packets
      can be exchanged with the corresponding peer. In addition, local
      information, such as interface up/down events, or other failure
      detection mechanisms can be used to quickly detect failure of
      tunnel(s).
   
      Deliverables related to this include
   
      - A document explaining the motivations for a node using multiple
        interfaces and the scenarios where it may end up with multiple
        global addresses on its interfaces [Informational]
   
      - An analysis document explaining what are the limitations for
        mobile hosts using multiple simultaneous Care-of Addresses and Home
        Agent addresses using Mobile IPv6, whether issues are specific to
        Mobile IPv6 or not [Informational].
   
      - A protocol extension to support the registration of multiple
        Care-of Addresses at a given Home Agent address [Standard
        Track].
   
      - A "Flow/binding policies exchange" solution for an exchange of
        policies from the mobile host/router to the Home Agent and from the
        Home Agent to the mobile host/router influencing the choice of the
        Care-of Address and Home Agent address. The solution involves two
        specifications, one for the policy format and another for its
        transport [both Standard Track].
      
(A.4) Work on solutions to deal with firewalls and the problems that
      firewalls cause as identified in RFC 4487.

(A.5) Route optimization of network mobility.

      Three use cases have been identified for this. These are called
      the Aviation case, the Automotive case, and the Personal Mobile
      Router (consumer electronics) case, though the actual technical
      problems are characterized by the type of movements and
      environments more than by the specific industry using the
      technology. The group will explore these cases to gather
      requirements and proceed with solving the open issues.
   
      (1) Airline and spacecraft community, who are deploying NEMO for
      control systems, as well as Internet connectivity and
      entertainment systems. This use case is characterized by fast (~
      1000 km/h) moving objects over large distances (across
      continents). The main technical problem is that tunneling-based
      solutions imply a roundtrip to another continent and that BGP
      based solutions imply significant churn in the global Internet
      routing table.
   
      (2) Automotive industry who are deploying NEMO for in-car
      communication, entertainment, and data gathering, possible
      control systems use, and communication to roadside devices. This
      use case is characterized by moderately fast (~ 100-300 km/h)
      moving objects that employ local or cellular networks for
      connectivity.
   
      (3) Personal Mobile Routers, which are consumer devices that
      allow the user to bring a NEMO network with the user while
      mobile, and communicate with peer NEMO Basic Support nodes
      and nodes served by them.
   
      After gathering the requirements for these types of deployments,
      the working group will evaluate what type of route optimization
      needs to be performed (if any), and formulate a solution to
      those problems.
   
      If no requirements for those scenarios can be collected by the
      deadline, it will be assumed that the work is premature, and
      that type of deployment will be dropped from the WG.
   
      The group will only consider airline and spacecraft solutions
      that combine tunneling solutions for small movements with either
      federated tunnel servers or slowly changing end host prefixes.
      The group will only consider personal mobile router requirements
      about optimized routes to another mobile router belonging to the
      same operator. The group will only consider automotive industry
      requirements to allow MR-attached hosts to directly access the
      network where MR has attached to. Work on automotive and
      personal mobile router solutions requires rechartering.

      The WG will not consider extensions to routing protocols. The
      group will not consider general multi-homing problems that are
      not related to the deployment and maintenance of Mobile IPv6 or
      NEMO Basic Support protocols. The group will also not consider
      general route optimization, or other problems that are not
      related to the deployment and maintenance of NEMO Basic Support
      protocols. Similarly, the group will not consider or rely on the
      results of general routing architecture, Internet architecture,
      or identifier-locator split issues that are discussed in
      separate, long term efforts elsewhere in the IETF. Finally, the
      group will not consider solutions that require changes from
      correspondent nodes in the general Internet

(A.6) Bootstrapping mechanisms developed earlier in the MIP6 WG
      require AAA support for Mobile IPv6. Part of this work is
      already being done in the DIME WG, but the MEXT WG is chartered
      to complete a design for RADIUS.


Work items related to base specification maintenance include:

(B.1) Create and maintain issue lists that are generated on the basis
      of implementation and interoperability experience. Address
      specific issues with specific updates or revisions of the base
      specification. One specific area of concern that should be
      analyzed and addressed relates to multilink subnets.

      This work item relates only to corrections and
      clarifications. The working group shall not revisit design
      decisions or change the protocol.

(B.2) Update the IANA considerations of RFC 3775 to allow extensions for
      experimental purposes as well passing of optional vendor-specific
      information.

(B.3) Finish working group documents that are currently in process, and
      submit for RFC. This includes prefix delegation protocol mechanism
      for network mobility, and a MIB for NEMO Basic Support.


Work items related to informational documentation include:

(C.1) Produce a design rationale that documents the historical
      thinking behind the introduction of an alternative security
      mechanism, the Authentication Protocol (RFC 4285).


Goals and Milestones:

Aug 2007    Submit -00 draft on Route Optimization Needs for Aircraft
and Spacecraft Deployments
Aug 2007    Submit -00 draft on Route Optimization Needs for Automobile
and Highway Deployments
Aug 2007    Submit Multiple CoA Registration to IESG

Sep 2007    Submit I-D 'Motivation for Authentication I-D' to IESG for
publication as Informational.
Sep 2007    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
publication as a Proposed Standard.

Oct 2007    Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for
publication as a Proposed Standard
Oct 2007    Submit -00 draft on Route Optimization needs for Personal
Mobile Router

Nov 2007    Submit final doc on Route Optimization Needs for Aircraft
and Spacecraft Deployments, for Informational
Nov 2007    Submit I-D 'Goals for AAA HA Interface' to IESG for
publication as Informational.

Dec 2007    Submit -00 draft for solution to aircraft/spacecraft problem
Dec 2007    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG
for publication as a Proposed Standard.
Dec 2007    Submit the final doc on Prefix Delegation for NEMO to the
IESG, for Proposed Standard

Jan 2007    Submit final doc on Route Optimization Needs for Automobile
and Highway Deployments, for Informational
Jan 2007    Submit final doc on Route Optimization needs for Personal
Mobile Router, for Informational

Feb 2008    Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
publication as a proposed standard.
Feb 2008    Determine how to proceed with remaining automotive/Personal
Mobile Router solutions

Mar 2008    Submit the final doc on MIB for NEMO Basic Support to the
IESG, for Proposed Standard
Mar 2008    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
for publication as Informational.

Apr 2008    Submit Flow/binding policy format to IESG, for Proposed Standard
Apr 2008    Submit Flow/binding policy transport to IESG, for Proposed
Standard
Apr 2007    Submit I-D 'Mobility Header Home Agent Switch Message' to
IESG for publication as a Proposed Standard.

May 2008    Submit final doc for solution to aircraft/spacecraft problem
to the IESG, for Proposed Standard
May 2008    Recharter to work on the remaining automotive/Personal
Mobile Router solutions

Jul 2007    Submit Multiple Interfaces Motivations and Scenario to IESG,
for Informational
Jul 2007    Submit Analysis of the use of Multiple Simultaneous Care-of
Addresses and Home Agent addresses, for Informational

Aug 2008    Submit I-D(s) related to specific updates and corrections of
RFC 3775 to IESG for publication as Proposed Standard.
Aug 2008    Submit I-D 'Home agent reliability' to IESG for publication
as a Proposed Standard.


_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext



From mext-bounces@ietf.org Tue Jun 26 17:05:51 2007
Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3IEC-0003As-C0; Tue, 26 Jun 2007 17:05:36 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3HDE-0005Hq-LX; Tue, 26 Jun 2007 16:00:32 -0400
Received: from ns3.neustar.com ([156.154.24.138])
	by chiedprmail1.ietf.org with esmtp (Exim 4.43)
	id 1I3HDE-000743-6r; Tue, 26 Jun 2007 16:00:32 -0400
Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com
	[10.31.47.10]) by ns3.neustar.com (Postfix) with ESMTP id D608A175CA;
	Tue, 26 Jun 2007 20:00:01 +0000 (GMT)
Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43)
	id 1I3HCj-0006C0-Ex; Tue, 26 Jun 2007 16:00:01 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
To: ietf-announce@ietf.org
From: IESG Secretary <iesg-secretary@ietf.org>
Message-Id: <E1I3HCj-0006C0-Ex@stiedprstage1.ietf.org>
Date: Tue, 26 Jun 2007 16:00:01 -0400
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f5932bfc8385127f631fc458a872feb1
X-Mailman-Approved-At: Tue, 26 Jun 2007 17:05:35 -0400
Cc: mext@ietf.org
Subject: [MEXT] WG Review: Mobility EXTensions for IPv6 (mext) 
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: iesg@ietf.org
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org

A new IETF working group has been proposed in the Internet Area.  
The IESG has not made any determination as yet. The following draft
charter was submitted, and is provided for informational purposes only.
Please send your comments to the IESG mailing list (iesg@ietf.org) by 
July 2.

+++

Mobility EXTensions for IPv6 (MEXT)

Chair(s):
TBD

Internet Area Director(s):
Jari Arkko <jari.arkko@piuha.net>
Mark Townsley <townsley@cisco.com>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Mailing Lists: mext@ietf.org 
https://www1.ietf.org/mailman/listinfo/mext
http://www1.ietf.org/mail-archive/web/mext/current/index.html


Description of Working Group:

Mobile IPv6 specifies routing support which permits an IPv6 host to
continue using its home address as it moves around the Internet,
enabling continuity of sessions. Mobile IPv6 supports transparency
above the IP layer, including maintenance of active transport level
sessions. In addition, NEMO network mobility mechanisms built on top
of Mobile IPv6 allow managing the mobility of an entire network, as it
changes its point of attachment to the Internet. The base
specifications consist of:

o RFC 3775
o RFC 3963
o RFC 4877

The MEXT Working Group continues the work of the MIP6,
NEMO, and MONAMI6 Working Groups.

The primary goal of MEXT will be to (A) enhance base IPv6
mobility by continuing work on developments that are required for
wide-scale deployments and specific deployment scenarios.
Additionally, (B) the working group will ensure that any issues
identified by implementation and interoperability experience are
addressed, and that the base specifications are maintained. (C) The
group will also produce informational documentation, such as design
rationale documents or description of specific issues within the
protocol.

Deployment considerations call for (A.1) solutions to enable
dual-stack operation, (A.2) allowing the use of multiple interfaces in
mobile nodes, (A.3) mechanisms to support high-availability home
agents, (A.4) ways to employ Mobile IPv6 in the presence of firewalls,
(A.5) address the specific needs of automotive and aviation
communities for route optimisation in network mobility, and (A.6)
support for AAA is needed as a continuation of earlier work on
bootstrapping.

Work items related to large scale deployment include:

(A.1) A Solution for MIP6 session continuity for dual stack hosts which
attach to IPv4 access networks. Additionally provide a mechanism
for carrying IPv4 packets via the Home agent for MIP6 capable
dual-stack hosts.

(A.2) A protocol based solution for enhancing the reliability of home
agents and a method to force a host to switch home agents.

A mechanism to force an MN to switch the HA that is currently
serving it. This is required in deployments where the HA needs to
be taken offline for maintenance.

(A.3) Use of multiple interfaces.

Today, the protocols do not provide suppport for simultaneous
differentiated use of multiple access technologies. Several
proposals exist for such support, and some of them have been
implemented and tested.

When a mobile host/router uses multiple network interfaces
simultaneously, or when multiple prefixes are available on a
single network interface, the mobile host/router would end up
with multiple Care-of Addresses (CoAs). In addition, the Home
Agent might be attached to multiple network interfaces, or to a
single network interface with multiple prefixes, hence resulting
in the option to use multiple IP addresses for the Home
Agent. This could result in the possibility of using a multitude
of bi-directional tunnels between pairs of {Home Agent address,
CoA} and a number of associated issues: establishment, selection
and modification of multiple simultaneous tunnels.

The objective of the WG is to produce a clear problem statement
and to produce standard track specifications to the problems
associated with the simultaneous use of multiple addresses for
either mobile hosts using Mobile IPv6 or mobile routers using
NEMO Basic Support and their variants (FMIPv6, HMIPv6,
etc). Where the effects of having multiple prefixes on a single
interface is identical to the effects of having multiple
interfaces each with a single prefix, the WG will consider a
generalized approach to cater for multiple prefixes available to
a mobile host/router.

The WG uses existing tunneling mechanisms defined for Mobile
IPv6. The involved nodes need to select which tunnel instance
to use when multiple ones are available due to multiple
addresses on either end. But the WG does not plan to define a
new mechanism for this, but rather document how to use existing
mechanisms based upon preferences or policies. In particular,
the WG will consider that a tunnel is alive as long as packets
can be exchanged with the corresponding peer. In addition, local
information, such as interface up/down events, or other failure
detection mechanisms can be used to quickly detect failure of
tunnel(s).

Deliverables related to this include

- A document explaining the motivations for a node using multiple
interfaces and the scenarios where it may end up with multiple
global addresses on its interfaces [Informational]

- An analysis document explaining what are the limitations for
mobile hosts using multiple simultaneous Care-of Addresses and Home
Agent addresses using Mobile IPv6, whether issues are specific to
Mobile IPv6 or not [Informational].

- A protocol extension to support the registration of multiple
Care-of Addresses at a given Home Agent address [Standard
Track].

- A "Flow/binding policies exchange" solution for an exchange of
policies from the mobile host/router to the Home Agent and from the
Home Agent to the mobile host/router influencing the choice of the
Care-of Address and Home Agent address. The solution involves two
specifications, one for the policy format and another for its
transport [both Standard Track].

(A.4) Work on solutions to deal with firewalls and the problems that
firewalls cause as identified in RFC 4487.

(A.5) Route optimization of network mobility.

Three use cases have been identified for this. These are called
the Aviation case, the Automotive case, and the Personal Mobile
Router (consumer electronics) case, though the actual technical
problems are characterized by the type of movements and
environments more than by the specific industry using the
technology. The group will explore these cases to gather
requirements and proceed with solving the open issues.

(1) Airline and spacecraft community, who are deploying NEMO for
control systems, as well as Internet connectivity and
entertainment systems. This use case is characterized by fast (~
1000 km/h) moving objects over large distances (across
continents). The main technical problem is that tunneling-based
solutions imply a roundtrip to another continent and that BGP
based solutions imply significant churn in the global Internet
routing table.

(2) Automotive industry who are deploying NEMO for in-car
communication, entertainment, and data gathering, possible
control systems use, and communication to roadside devices. This
use case is characterized by moderately fast (~ 100-300 km/h)
moving objects that employ local or cellular networks for
connectivity.

(3) Personal Mobile Routers, which are consumer devices that
allow the user to bring a NEMO network with the user while
mobile, and communicate with peer NEMO Basic Support nodes
and nodes served by them.

After gathering the requirements for these types of deployments,
the working group will evaluate what type of route optimization
needs to be performed (if any), and formulate a solution to
those problems.

If no requirements for those scenarios can be collected by the
deadline, it will be assumed that the work is premature, and
that type of deployment will be dropped from the WG.

The group will only consider airline and spacecraft solutions
that combine tunneling solutions for small movements with either
federated tunnel servers or slowly changing end host prefixes.
The group will only consider personal mobile router requirements
about optimized routes to another mobile router belonging to the
same operator. The group will only consider automotive industry
requirements to allow MR-attached hosts to directly access the
network where MR has attached to. Work on automotive and
personal mobile router solutions requires rechartering.

The WG will not consider extensions to routing protocols. The
group will not consider general multi-homing problems that are
not related to the deployment and maintenance of Mobile IPv6 or
NEMO Basic Support protocols. The group will also not consider
general route optimization, or other problems that are not
related to the deployment and maintenance of NEMO Basic Support
protocols. Similarly, the group will not consider or rely on the
results of general routing architecture, Internet architecture,
or identifier-locator split issues that are discussed in
separate, long term efforts elsewhere in the IETF. Finally, the
group will not consider solutions that require changes from
correspondent nodes in the general Internet

(A.6) Bootstrapping mechanisms developed earlier in the MIP6 WG
require AAA support for Mobile IPv6. Part of this work is
already being done in the DIME WG, but the MEXT WG is chartered
to complete a design for RADIUS.


Work items related to base specification maintenance include:

(B.1) Create and maintain issue lists that are generated on the basis
of implementation and interoperability experience. Address
specific issues with specific updates or revisions of the base
specification. One specific area of concern that should be
analyzed and addressed relates to multilink subnets.

This work item relates only to corrections and
clarifications. The working group shall not revisit design
decisions or change the protocol.

(B.2) Update the IANA considerations of RFC 3775 to allow extensions for
experimental purposes as well passing of optional vendor-specific
information.

(B.3) Finish working group documents that are currently in process, and
submit for RFC. This includes prefix delegation protocol mechanism
for network mobility, and a MIB for NEMO Basic Support.


Work items related to informational documentation include:

(C.1) Produce a design rationale that documents the historical
thinking behind the introduction of an alternative security
mechanism, the Authentication Protocol (RFC 4285).


Goals and Milestones:

Aug 2007 Submit -00 draft on Route Optimization Needs for Aircraft
and Spacecraft Deployments
Aug 2007 Submit -00 draft on Route Optimization Needs for Automobile
and Highway Deployments
Aug 2007 Submit Multiple CoA Registration to IESG

Sep 2007 Submit I-D 'Motivation for Authentication I-D' to IESG for
publication as Informational.
Sep 2007 Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
publication as a Proposed Standard.

Oct 2007 Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for
publication as a Proposed Standard
Oct 2007 Submit -00 draft on Route Optimization needs for Personal
Mobile Router

Nov 2007 Submit final doc on Route Optimization Needs for Aircraft
and Spacecraft Deployments, for Informational
Nov 2007 Submit I-D 'Goals for AAA HA Interface' to IESG for
publication as Informational.

Dec 2007 Submit -00 draft for solution to aircraft/spacecraft problem
Dec 2007 Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG
for publication as a Proposed Standard.
Dec 2007 Submit the final doc on Prefix Delegation for NEMO to the
IESG, for Proposed Standard

Jan 2007 Submit final doc on Route Optimization Needs for Automobile
and Highway Deployments, for Informational
Jan 2007 Submit final doc on Route Optimization needs for Personal
Mobile Router, for Informational

Feb 2008 Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
publication as a proposed standard.
Feb 2008 Determine how to proceed with remaining automotive/Personal
Mobile Router solutions

Mar 2008 Submit the final doc on MIB for NEMO Basic Support to the
IESG, for Proposed Standard
Mar 2008 Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
for publication as Informational.

Apr 2008 Submit Flow/binding policy format to IESG, for Proposed Standard
Apr 2008 Submit Flow/binding policy transport to IESG, for Proposed
Standard
Apr 2007 Submit I-D 'Mobility Header Home Agent Switch Message' to
IESG for publication as a Proposed Standard.

May 2008 Submit final doc for solution to aircraft/spacecraft problem
to the IESG, for Proposed Standard
May 2008 Recharter to work on the remaining automotive/Personal
Mobile Router solutions

Jul 2007 Submit Multiple Interfaces Motivations and Scenario to IESG,
for Informational
Jul 2007 Submit Analysis of the use of Multiple Simultaneous Care-of
Addresses and Home Agent addresses, for Informational

Aug 2008 Submit I-D(s) related to specific updates and corrections of
RFC 3775 to IESG for publication as Proposed Standard.
Aug 2008 Submit I-D 'Home agent reliability' to IESG for publication
as a Proposed Standard.

_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext



From mext-bounces@ietf.org Wed Jun 27 06:08:09 2007
Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3URQ-0002WZ-Gd; Wed, 27 Jun 2007 06:08:04 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3URE-00022q-GJ
	for mext@ietf.org; Wed, 27 Jun 2007 06:07:52 -0400
Received: from mail153.messagelabs.com ([216.82.253.51])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I3UQJ-0005O9-N7
	for mext@ietf.org; Wed, 27 Jun 2007 06:07:52 -0400
X-VirusChecked: Checked
X-Env-Sender: alexandru.petrescu@gmail.com
X-Msg-Ref: server-7.tower-153.messagelabs.com!1182938811!2338471!1
X-StarScan-Version: 5.5.12.11; banners=.,-,-
X-Originating-IP: [129.188.136.9]
Received: (qmail 6441 invoked from network); 27 Jun 2007 10:06:52 -0000
Received: from ftpbox.mot.com (HELO ftpbox.mot.com) (129.188.136.9)
	by server-7.tower-153.messagelabs.com with SMTP;
	27 Jun 2007 10:06:52 -0000
Received: from az33exr03.mot.com ([10.64.251.233])
	by ftpbox.mot.com (8.12.11/Motorola) with ESMTP id l5RA6pn7027274
	for <mext@ietf.org>; Wed, 27 Jun 2007 05:06:51 -0500 (CDT)
Received: from az10vts04 (az10vts04.mot.com [10.64.251.245])
	by az33exr03.mot.com (8.13.1/Vontu) with SMTP id l5RA6ow8011429
	for <mext@ietf.org>; Wed, 27 Jun 2007 05:06:50 -0500 (CDT)
Received: from zuk35exm62.ds.mot.com (zuk35exm62.ea.mot.com [10.178.1.41])
	by az33exr03.mot.com (8.13.1/8.13.0) with ESMTP id l5RA6nGV011410
	for <mext@ietf.org>; Wed, 27 Jun 2007 05:06:49 -0500 (CDT)
Received: from [127.0.0.1] ([10.161.201.117]) by zuk35exm62.ds.mot.com with
	Microsoft SMTPSVC(6.0.3790.2709); Wed, 27 Jun 2007 11:06:47 +0100
Message-ID: <468236AE.8060805@gmail.com>
Date: Wed, 27 Jun 2007 12:06:38 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Thunderbird 2.0.0.0 (Windows/20070326)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: some dates (was: [MEXT] new charter version)
References: <467FB99E.3000105@piuha.net>
In-Reply-To: <467FB99E.3000105@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 000752-1, 26/06/2007), Outbound message
X-Antivirus-Status: Clean
X-OriginalArrivalTime: 27 Jun 2007 10:06:47.0881 (UTC)
	FILETIME=[DF978390:01C7B8A2]
X-Vontu: Pass
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Cc: mext@ietf.org
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org

Just to say some dates should be updated to 2008 instead of 2007.

Jari Arkko wrote:
[...]
> Dec 2007    Submit -00 draft for solution to aircraft/spacecraft problem
> Dec 2007    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG
> for publication as a Proposed Standard.
> Dec 2007    Submit the final doc on Prefix Delegation for NEMO to the
> IESG, for Proposed Standard
> 
> Jan 2007    Submit final doc on Route Optimization Needs for Automobile
> and Highway Deployments, for Informational
> Jan 2007    Submit final doc on Route Optimization needs for Personal
> Mobile Router, for Informational

^here.

> Feb 2008    Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
> publication as a proposed standard.
> Feb 2008    Determine how to proceed with remaining automotive/Personal
> Mobile Router solutions

Alex

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext



From mext-bounces@ietf.org Wed Jun 27 06:27:41 2007
Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I3UkM-0008NK-CI; Wed, 27 Jun 2007 06:27:38 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I3UkH-0008Db-F5
	for mext@ietf.org; Wed, 27 Jun 2007 06:27:33 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I3Ujd-0002nW-I3
	for mext@ietf.org; Wed, 27 Jun 2007 06:27:33 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 54A331986A6;
	Wed, 27 Jun 2007 13:26:52 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 0E526198691;
	Wed, 27 Jun 2007 13:26:52 +0300 (EEST)
Message-ID: <46823B6B.9020600@piuha.net>
Date: Wed, 27 Jun 2007 13:26:51 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
References: <467FB99E.3000105@piuha.net> <468236AE.8060805@gmail.com>
In-Reply-To: <468236AE.8060805@gmail.com>
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: 52e1467c2184c31006318542db5614d5
Cc: mext@ietf.org
Subject: [MEXT] Re: some dates
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org

Ah, of course. Thanks for catching this.

Jari

Alexandru Petrescu kirjoitti:
> Just to say some dates should be updated to 2008 instead of 2007.
>
> Jari Arkko wrote:
> [...]
>> Dec 2007    Submit -00 draft for solution to aircraft/spacecraft problem
>> Dec 2007    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG
>> for publication as a Proposed Standard.
>> Dec 2007    Submit the final doc on Prefix Delegation for NEMO to the
>> IESG, for Proposed Standard
>>
>> Jan 2007    Submit final doc on Route Optimization Needs for Automobile
>> and Highway Deployments, for Informational
>> Jan 2007    Submit final doc on Route Optimization needs for Personal
>> Mobile Router, for Informational
>
> ^here.
>
>> Feb 2008    Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
>> publication as a proposed standard.
>> Feb 2008    Determine how to proceed with remaining automotive/Personal
>> Mobile Router solutions
>
> Alex
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
>


_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext



From mext-bounces@ietf.org Fri Jun 29 17:29:23 2007
Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4O1e-0004n0-Vo; Fri, 29 Jun 2007 17:29:11 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4O1d-0004hb-Ee
	for mext@ietf.org; Fri, 29 Jun 2007 17:29:09 -0400
Received: from imr1.ericy.com ([198.24.6.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4O0j-0004Xn-Uq
	for mext@ietf.org; Fri, 29 Jun 2007 17:29:09 -0400
Received: from eusrcmw751.eamcs.ericsson.se (eusrcmw751.exu.ericsson.se
	[138.85.77.51])
	by imr1.ericy.com (8.13.1/8.13.1) with ESMTP id l5TLVjTL026544;
	Fri, 29 Jun 2007 16:31:45 -0500
Received: from eusrcmw751.eamcs.ericsson.se ([138.85.77.56]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 16:28:12 -0500
Received: from [142.133.10.140] ([142.133.10.140]) by
	eusrcmw751.eamcs.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); 
	Fri, 29 Jun 2007 16:28:12 -0500
Message-ID: <46857923.3080302@ericsson.com>
Date: Fri, 29 Jun 2007 17:26:59 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
User-Agent: Thunderbird 1.5 (X11/20060313)
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [MEXT] new charter version
References: <467FB99E.3000105@piuha.net>
In-Reply-To: <467FB99E.3000105@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 29 Jun 2007 21:28:12.0270 (UTC)
	FILETIME=[6569B0E0:01C7BA94]
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6b519fb0ef66258f34533f52ff46aedf
Cc: mext@ietf.org
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org

Hi Jari,
   The items A.2 and A.3 are reversed in the following descriptive text

"Deployment considerations call for (A.1) solutions to enable
dual-stack operation, (A.2) allowing the use of multiple interfaces in
mobile nodes, (A.3) mechanisms to support high-availability home
agents,..."

whereas in the following bulleted list A.2 talks about HA reliability 
and A.3 talks about multiple interfaces in MNs.

Cheers
Suresh

Jari Arkko wrote:
> Testing the new list... this list should have all the subscribers
> of the existing three lists. For now, please continue your
> technical discussions in the existing lists, except for charter
> discussion which we can move here. In general, you do not
> need to take any action with regards to list changes, once
> we are ready to move complete away from the old lists we
> can deal with the from the secretariat. Here's a pointer
> to the list page:
> 
>    https://www1.ietf.org/mailman/listinfo/mext
> 
> Here's the new charter, revised according to comments
> from many of you (thanks!) and the rest of the IESG.
> 
> The charter will go out soon for public IETF review.
> 
> ------
> 
> Mobility EXTensions for IPv6 (MEXT)
> 
> Chair(s):
> TBD
> 
> Internet Area Director(s):
> Jari Arkko <jari.arkko@piuha.net>
> Mark Townsley <townsley@cisco.com>
> 
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
> 
> Mailing Lists:
> https://www1.ietf.org/mailman/listinfo/mext
> http://www1.ietf.org/mail-archive/web/mext/current/index.html
> 
> 
> Description of Working Group:
> 
> Mobile IPv6 specifies routing support which permits an IPv6 host to
> continue using its home address as it moves around the Internet,
> enabling continuity of sessions. Mobile IPv6 supports transparency
> above the IP layer, including maintenance of active transport level
> sessions. In addition, NEMO network mobility mechanisms built on top
> of Mobile IPv6 allow managing the mobility of an entire network, as it
> changes its point of attachment to the Internet. The base
> specifications consist of:
> 
> o RFC 3775
> o RFC 3963
> o RFC 4877
> 
> The MEXT Working Group continues the work of the MIP6, NEMO, and
> MONAMI6 Working Groups.
> 
> The primary goal of MEXT will be to (A) enhance base IPv6 mobility by
> continuing work on developments that are required for wide-scale
> deployments and specific deployment scenarios.  Additionally, (B) the
> working group will ensure that any issues identified by implementation
> and interoperability experience are addressed, and that the base
> specifications are maintained. (C) The group will also produce
> informational documentation, such as design rationale documents or
> description of specific issues within the protocol.
> 
> Deployment considerations call for (A.1) solutions to enable
> dual-stack operation, (A.2) allowing the use of multiple interfaces in
> mobile nodes, (A.3) mechanisms to support high-availability home
> agents, (A.4) ways to employ Mobile IPv6 in the presence of firewalls,
> (A.5) address the specific needs of automotive and aviation
> communities for route optimisation in network mobility, and (A.6)
> support for AAA is needed as a continuation of earlier work on
> bootstrapping.
> 
> Work items related to large scale deployment include:
> 
> (A.1) A Solution for MIP6 session continuity for dual stack hosts which
>       attach to IPv4 access networks. Additionally provide a mechanism
>       for carrying IPv4 packets via the Home agent for MIP6 capable
>       dual-stack hosts.
> 
> (A.2) A protocol based solution for enhancing the reliability of home
>       agents and a method to force a host to switch home agents.
> 
>       A mechanism to force an MN to switch the HA that is currently
>       serving it. This is required in deployments where the HA needs to
>       be taken offline for maintenance.
> 
> (A.3) Use of multiple interfaces.
> 
>       Today, the protocols do not provide suppport for simultaneous
>       differentiated use of multiple access technologies. Several
>       proposals exist for such support, and some of them have been
>       implemented and tested.
>    
>       When a mobile host/router uses multiple network interfaces
>       simultaneously, or when multiple prefixes are available on a
>       single network interface, the mobile host/router would end up
>       with multiple Care-of Addresses (CoAs). In addition, the Home
>       Agent might be attached to multiple network interfaces, or to a
>       single network interface with multiple prefixes, hence resulting
>       in the option to use multiple IP addresses for the Home
>       Agent. This could result in the possibility of using a multitude
>       of bi-directional tunnels between pairs of {Home Agent address,
>       CoA} and a number of associated issues: establishment, selection
>       and modification of multiple simultaneous tunnels.
>    
>       The objective of the WG is to produce a clear problem statement
>       and to produce standard track specifications to the problems
>       associated with the simultaneous use of multiple addresses for
>       either mobile hosts using Mobile IPv6 or mobile routers using
>       NEMO Basic Support and their variants (FMIPv6, HMIPv6,
>       etc). Where the effects of having multiple prefixes on a single
>       interface is identical to the effects of having multiple
>       interfaces each with a single prefix, the WG will consider a
>       generalized approach to cater for multiple prefixes available to
>       a mobile host/router.
> 
>       The WG uses existing tunneling mechanisms defined for Mobile
>       IPv6. The involved nodes need to select which tunnel instance
>       to use when multiple ones are available due to multiple
>       addresses on either end. But the WG does not plan to define a
>       new mechanism for this, but rather document how to use existing
>       mechanisms based upon preferences or policies. In particular,
>       the WG will consider that a tunnel is alive as long as packets
>       can be exchanged with the corresponding peer. In addition, local
>       information, such as interface up/down events, or other failure
>       detection mechanisms can be used to quickly detect failure of
>       tunnel(s).
>    
>       Deliverables related to this include
>    
>       - A document explaining the motivations for a node using multiple
>         interfaces and the scenarios where it may end up with multiple
>         global addresses on its interfaces [Informational]
>    
>       - An analysis document explaining what are the limitations for
>         mobile hosts using multiple simultaneous Care-of Addresses and Home
>         Agent addresses using Mobile IPv6, whether issues are specific to
>         Mobile IPv6 or not [Informational].
>    
>       - A protocol extension to support the registration of multiple
>         Care-of Addresses at a given Home Agent address [Standard
>         Track].
>    
>       - A "Flow/binding policies exchange" solution for an exchange of
>         policies from the mobile host/router to the Home Agent and from the
>         Home Agent to the mobile host/router influencing the choice of the
>         Care-of Address and Home Agent address. The solution involves two
>         specifications, one for the policy format and another for its
>         transport [both Standard Track].
>       
> (A.4) Work on solutions to deal with firewalls and the problems that
>       firewalls cause as identified in RFC 4487.
> 
> (A.5) Route optimization of network mobility.
> 
>       Three use cases have been identified for this. These are called
>       the Aviation case, the Automotive case, and the Personal Mobile
>       Router (consumer electronics) case, though the actual technical
>       problems are characterized by the type of movements and
>       environments more than by the specific industry using the
>       technology. The group will explore these cases to gather
>       requirements and proceed with solving the open issues.
>    
>       (1) Airline and spacecraft community, who are deploying NEMO for
>       control systems, as well as Internet connectivity and
>       entertainment systems. This use case is characterized by fast (~
>       1000 km/h) moving objects over large distances (across
>       continents). The main technical problem is that tunneling-based
>       solutions imply a roundtrip to another continent and that BGP
>       based solutions imply significant churn in the global Internet
>       routing table.
>    
>       (2) Automotive industry who are deploying NEMO for in-car
>       communication, entertainment, and data gathering, possible
>       control systems use, and communication to roadside devices. This
>       use case is characterized by moderately fast (~ 100-300 km/h)
>       moving objects that employ local or cellular networks for
>       connectivity.
>    
>       (3) Personal Mobile Routers, which are consumer devices that
>       allow the user to bring a NEMO network with the user while
>       mobile, and communicate with peer NEMO Basic Support nodes
>       and nodes served by them.
>    
>       After gathering the requirements for these types of deployments,
>       the working group will evaluate what type of route optimization
>       needs to be performed (if any), and formulate a solution to
>       those problems.
>    
>       If no requirements for those scenarios can be collected by the
>       deadline, it will be assumed that the work is premature, and
>       that type of deployment will be dropped from the WG.
>    
>       The group will only consider airline and spacecraft solutions
>       that combine tunneling solutions for small movements with either
>       federated tunnel servers or slowly changing end host prefixes.
>       The group will only consider personal mobile router requirements
>       about optimized routes to another mobile router belonging to the
>       same operator. The group will only consider automotive industry
>       requirements to allow MR-attached hosts to directly access the
>       network where MR has attached to. Work on automotive and
>       personal mobile router solutions requires rechartering.
> 
>       The WG will not consider extensions to routing protocols. The
>       group will not consider general multi-homing problems that are
>       not related to the deployment and maintenance of Mobile IPv6 or
>       NEMO Basic Support protocols. The group will also not consider
>       general route optimization, or other problems that are not
>       related to the deployment and maintenance of NEMO Basic Support
>       protocols. Similarly, the group will not consider or rely on the
>       results of general routing architecture, Internet architecture,
>       or identifier-locator split issues that are discussed in
>       separate, long term efforts elsewhere in the IETF. Finally, the
>       group will not consider solutions that require changes from
>       correspondent nodes in the general Internet
> 
> (A.6) Bootstrapping mechanisms developed earlier in the MIP6 WG
>       require AAA support for Mobile IPv6. Part of this work is
>       already being done in the DIME WG, but the MEXT WG is chartered
>       to complete a design for RADIUS.
> 
> 
> Work items related to base specification maintenance include:
> 
> (B.1) Create and maintain issue lists that are generated on the basis
>       of implementation and interoperability experience. Address
>       specific issues with specific updates or revisions of the base
>       specification. One specific area of concern that should be
>       analyzed and addressed relates to multilink subnets.
> 
>       This work item relates only to corrections and
>       clarifications. The working group shall not revisit design
>       decisions or change the protocol.
> 
> (B.2) Update the IANA considerations of RFC 3775 to allow extensions for
>       experimental purposes as well passing of optional vendor-specific
>       information.
> 
> (B.3) Finish working group documents that are currently in process, and
>       submit for RFC. This includes prefix delegation protocol mechanism
>       for network mobility, and a MIB for NEMO Basic Support.
> 
> 
> Work items related to informational documentation include:
> 
> (C.1) Produce a design rationale that documents the historical
>       thinking behind the introduction of an alternative security
>       mechanism, the Authentication Protocol (RFC 4285).
> 
> 
> Goals and Milestones:
> 
> Aug 2007    Submit -00 draft on Route Optimization Needs for Aircraft
> and Spacecraft Deployments
> Aug 2007    Submit -00 draft on Route Optimization Needs for Automobile
> and Highway Deployments
> Aug 2007    Submit Multiple CoA Registration to IESG
> 
> Sep 2007    Submit I-D 'Motivation for Authentication I-D' to IESG for
> publication as Informational.
> Sep 2007    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
> publication as a Proposed Standard.
> 
> Oct 2007    Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for
> publication as a Proposed Standard
> Oct 2007    Submit -00 draft on Route Optimization needs for Personal
> Mobile Router
> 
> Nov 2007    Submit final doc on Route Optimization Needs for Aircraft
> and Spacecraft Deployments, for Informational
> Nov 2007    Submit I-D 'Goals for AAA HA Interface' to IESG for
> publication as Informational.
> 
> Dec 2007    Submit -00 draft for solution to aircraft/spacecraft problem
> Dec 2007    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG
> for publication as a Proposed Standard.
> Dec 2007    Submit the final doc on Prefix Delegation for NEMO to the
> IESG, for Proposed Standard
> 
> Jan 2007    Submit final doc on Route Optimization Needs for Automobile
> and Highway Deployments, for Informational
> Jan 2007    Submit final doc on Route Optimization needs for Personal
> Mobile Router, for Informational
> 
> Feb 2008    Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
> publication as a proposed standard.
> Feb 2008    Determine how to proceed with remaining automotive/Personal
> Mobile Router solutions
> 
> Mar 2008    Submit the final doc on MIB for NEMO Basic Support to the
> IESG, for Proposed Standard
> Mar 2008    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
> for publication as Informational.
> 
> Apr 2008    Submit Flow/binding policy format to IESG, for Proposed Standard
> Apr 2008    Submit Flow/binding policy transport to IESG, for Proposed
> Standard
> Apr 2007    Submit I-D 'Mobility Header Home Agent Switch Message' to
> IESG for publication as a Proposed Standard.
> 
> May 2008    Submit final doc for solution to aircraft/spacecraft problem
> to the IESG, for Proposed Standard
> May 2008    Recharter to work on the remaining automotive/Personal
> Mobile Router solutions
> 
> Jul 2007    Submit Multiple Interfaces Motivations and Scenario to IESG,
> for Informational
> Jul 2007    Submit Analysis of the use of Multiple Simultaneous Care-of
> Addresses and Home Agent addresses, for Informational
> 
> Aug 2008    Submit I-D(s) related to specific updates and corrections of
> RFC 3775 to IESG for publication as Proposed Standard.
> Aug 2008    Submit I-D 'Home agent reliability' to IESG for publication
> as a Proposed Standard.
> 
> 
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www1.ietf.org/mailman/listinfo/mext


_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext



From mext-bounces@ietf.org Fri Jun 29 18:34:48 2007
Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4P31-0005Y7-TT; Fri, 29 Jun 2007 18:34:39 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4P30-0005Xc-IL
	for mext@ietf.org; Fri, 29 Jun 2007 18:34:38 -0400
Received: from web84106.mail.mud.yahoo.com ([68.142.206.193])
	by ietf-mx.ietf.org with smtp (Exim 4.43) id 1I4P2u-0004To-Kx
	for mext@ietf.org; Fri, 29 Jun 2007 18:34:38 -0400
Received: (qmail 44804 invoked by uid 60001); 29 Jun 2007 22:34:32 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com;
	h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:MIME-Version:Content-Type:Message-ID;
	b=ymMdslFbjk2WgYIVQpqTM2wvozSG9Oa1E+vWdFSCsPaimUjJBvTx/IwkjtLZQU3UzZd1vtpnJKEmlDiQum14CuoQTo3ODRTsUklbsrZ463zgGtr+hN3D6neLH4k9pT3S6455mw8120U8Nnm2XxfAN5zQQTZSF7ILa00pfibCgck=;
X-YMail-OSG: DZWOWDEVM1m1TSRnjz.7zH0hyQPweR_nrJzLGQBjkXD997R7boesSbJtUBP.UK9S5Y_Tsy_Ce9WOFqYh.D1vi89YLDPv34mXrgsrZenAxLVp61TXUew-
Received: from [206.16.17.212] by web84106.mail.mud.yahoo.com via HTTP;
	Fri, 29 Jun 2007 15:34:32 PDT
X-Mailer: YahooMailRC/651.38 YahooMailWebService/0.7.41.16
Date: Fri, 29 Jun 2007 15:34:32 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: Re: [MEXT] new charter version
To: Jari Arkko <jari.arkko@piuha.net>
MIME-Version: 1.0
Message-ID: <84929.44768.qm@web84106.mail.mud.yahoo.com>
X-Spam-Score: 0.1 (/)
X-Scan-Signature: cd000eda3d43531d5b01b5d305410e3c
Cc: mext@ietf.org
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0222891421=="
Errors-To: mext-bounces@ietf.org

--===============0222891421==
Content-Type: multipart/alternative; boundary="0-1884647686-1183156472=:44768"

--0-1884647686-1183156472=:44768
Content-Type: text/plain; charset=ascii

Hi Jari,
  In fact HA reliability work is almost over. I think the current draft is expected to go for WGLC soon and the subteam is almost closed. I don't think it would take Aug 08 to complete this work. HA reliability could be completely removed from this charter.

Kind regards,

Behcet



----- Original Message ----
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Jari Arkko <jari.arkko@piuha.net>
Cc: mext@ietf.org
Sent: Friday, June 29, 2007 4:26:59 PM
Subject: Re: [MEXT] new charter version

Hi Jari,
   The items A.2 and A.3 are reversed in the following descriptive text

"Deployment considerations call for (A.1) solutions to enable
dual-stack operation, (A.2) allowing the use of multiple interfaces in
mobile nodes, (A.3) mechanisms to support high-availability home
agents,..."

whereas in the following bulleted list A.2 talks about HA reliability 
and A.3 talks about multiple interfaces in MNs.

Cheers
Suresh

Jari Arkko wrote:
> Testing the new list... this list should have all the subscribers
> of the existing three lists. For now, please continue your
> technical discussions in the existing lists, except for charter
> discussion which we can move here. In general, you do not
> need to take any action with regards to list changes, once
> we are ready to move complete away from the old lists we
> can deal with the from the secretariat. Here's a pointer
> to the list page:
> 
>    https://www1.ietf.org/mailman/listinfo/mext
> 
> Here's the new charter, revised according to comments
> from many of you (thanks!) and the rest of the IESG.
> 
> The charter will go out soon for public IETF review.
> 
> ------
> 
> Mobility EXTensions for IPv6 (MEXT)
> 
> Chair(s):
> TBD
> 
> Internet Area Director(s):
> Jari Arkko <jari.arkko@piuha.net>
> Mark Townsley <townsley@cisco.com>
> 
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
> 
> Mailing Lists:
> https://www1.ietf.org/mailman/listinfo/mext
> http://www1.ietf.org/mail-archive/web/mext/current/index.html
> 
> 
> Description of Working Group:
> 
> Mobile IPv6 specifies routing support which permits an IPv6 host to
> continue using its home address as it moves around the Internet,
> enabling continuity of sessions. Mobile IPv6 supports transparency
> above the IP layer, including maintenance of active transport level
> sessions. In addition, NEMO network mobility mechanisms built on top
> of Mobile IPv6 allow managing the mobility of an entire network, as it
> changes its point of attachment to the Internet. The base
> specifications consist of:
> 
> o RFC 3775
> o RFC 3963
> o RFC 4877
> 
> The MEXT Working Group continues the work of the MIP6, NEMO, and
> MONAMI6 Working Groups.
> 
> The primary goal of MEXT will be to (A) enhance base IPv6 mobility by
> continuing work on developments that are required for wide-scale
> deployments and specific deployment scenarios.  Additionally, (B) the
> working group will ensure that any issues identified by implementation
> and interoperability experience are addressed, and that the base
> specifications are maintained. (C) The group will also produce
> informational documentation, such as design rationale documents or
> description of specific issues within the protocol.
> 
> Deployment considerations call for (A.1) solutions to enable
> dual-stack operation, (A.2) allowing the use of multiple interfaces in
> mobile nodes, (A.3) mechanisms to support high-availability home
> agents, (A.4) ways to employ Mobile IPv6 in the presence of firewalls,
> (A.5) address the specific needs of automotive and aviation
> communities for route optimisation in network mobility, and (A.6)
> support for AAA is needed as a continuation of earlier work on
> bootstrapping.
> 
> Work items related to large scale deployment include:
> 
> (A.1) A Solution for MIP6 session continuity for dual stack hosts which
>       attach to IPv4 access networks. Additionally provide a mechanism
>       for carrying IPv4 packets via the Home agent for MIP6 capable
>       dual-stack hosts.
> 
> (A.2) A protocol based solution for enhancing the reliability of home
>       agents and a method to force a host to switch home agents.
> 
>       A mechanism to force an MN to switch the HA that is currently
>       serving it. This is required in deployments where the HA needs to
>       be taken offline for maintenance.
> 
> (A.3) Use of multiple interfaces.
> 
>       Today, the protocols do not provide suppport for simultaneous
>       differentiated use of multiple access technologies. Several
>       proposals exist for such support, and some of them have been
>       implemented and tested.
>    
>       When a mobile host/router uses multiple network interfaces
>       simultaneously, or when multiple prefixes are available on a
>       single network interface, the mobile host/router would end up
>       with multiple Care-of Addresses (CoAs). In addition, the Home
>       Agent might be attached to multiple network interfaces, or to a
>       single network interface with multiple prefixes, hence resulting
>       in the option to use multiple IP addresses for the Home
>       Agent. This could result in the possibility of using a multitude
>       of bi-directional tunnels between pairs of {Home Agent address,
>       CoA} and a number of associated issues: establishment, selection
>       and modification of multiple simultaneous tunnels.
>    
>       The objective of the WG is to produce a clear problem statement
>       and to produce standard track specifications to the problems
>       associated with the simultaneous use of multiple addresses for
>       either mobile hosts using Mobile IPv6 or mobile routers using
>       NEMO Basic Support and their variants (FMIPv6, HMIPv6,
>       etc). Where the effects of having multiple prefixes on a single
>       interface is identical to the effects of having multiple
>       interfaces each with a single prefix, the WG will consider a
>       generalized approach to cater for multiple prefixes available to
>       a mobile host/router.
> 
>       The WG uses existing tunneling mechanisms defined for Mobile
>       IPv6. The involved nodes need to select which tunnel instance
>       to use when multiple ones are available due to multiple
>       addresses on either end. But the WG does not plan to define a
>       new mechanism for this, but rather document how to use existing
>       mechanisms based upon preferences or policies. In particular,
>       the WG will consider that a tunnel is alive as long as packets
>       can be exchanged with the corresponding peer. In addition, local
>       information, such as interface up/down events, or other failure
>       detection mechanisms can be used to quickly detect failure of
>       tunnel(s).
>    
>       Deliverables related to this include
>    
>       - A document explaining the motivations for a node using multiple
>         interfaces and the scenarios where it may end up with multiple
>         global addresses on its interfaces [Informational]
>    
>       - An analysis document explaining what are the limitations for
>         mobile hosts using multiple simultaneous Care-of Addresses and Home
>         Agent addresses using Mobile IPv6, whether issues are specific to
>         Mobile IPv6 or not [Informational].
>    
>       - A protocol extension to support the registration of multiple
>         Care-of Addresses at a given Home Agent address [Standard
>         Track].
>    
>       - A "Flow/binding policies exchange" solution for an exchange of
>         policies from the mobile host/router to the Home Agent and from the
>         Home Agent to the mobile host/router influencing the choice of the
>         Care-of Address and Home Agent address. The solution involves two
>         specifications, one for the policy format and another for its
>         transport [both Standard Track].
>       
> (A.4) Work on solutions to deal with firewalls and the problems that
>       firewalls cause as identified in RFC 4487.
> 
> (A.5) Route optimization of network mobility.
> 
>       Three use cases have been identified for this. These are called
>       the Aviation case, the Automotive case, and the Personal Mobile
>       Router (consumer electronics) case, though the actual technical
>       problems are characterized by the type of movements and
>       environments more than by the specific industry using the
>       technology. The group will explore these cases to gather
>       requirements and proceed with solving the open issues.
>    
>       (1) Airline and spacecraft community, who are deploying NEMO for
>       control systems, as well as Internet connectivity and
>       entertainment systems. This use case is characterized by fast (~
>       1000 km/h) moving objects over large distances (across
>       continents). The main technical problem is that tunneling-based
>       solutions imply a roundtrip to another continent and that BGP
>       based solutions imply significant churn in the global Internet
>       routing table.
>    
>       (2) Automotive industry who are deploying NEMO for in-car
>       communication, entertainment, and data gathering, possible
>       control systems use, and communication to roadside devices. This
>       use case is characterized by moderately fast (~ 100-300 km/h)
>       moving objects that employ local or cellular networks for
>       connectivity.
>    
>       (3) Personal Mobile Routers, which are consumer devices that
>       allow the user to bring a NEMO network with the user while
>       mobile, and communicate with peer NEMO Basic Support nodes
>       and nodes served by them.
>    
>       After gathering the requirements for these types of deployments,
>       the working group will evaluate what type of route optimization
>       needs to be performed (if any), and formulate a solution to
>       those problems.
>    
>       If no requirements for those scenarios can be collected by the
>       deadline, it will be assumed that the work is premature, and
>       that type of deployment will be dropped from the WG.
>    
>       The group will only consider airline and spacecraft solutions
>       that combine tunneling solutions for small movements with either
>       federated tunnel servers or slowly changing end host prefixes.
>       The group will only consider personal mobile router requirements
>       about optimized routes to another mobile router belonging to the
>       same operator. The group will only consider automotive industry
>       requirements to allow MR-attached hosts to directly access the
>       network where MR has attached to. Work on automotive and
>       personal mobile router solutions requires rechartering.
> 
>       The WG will not consider extensions to routing protocols. The
>       group will not consider general multi-homing problems that are
>       not related to the deployment and maintenance of Mobile IPv6 or
>       NEMO Basic Support protocols. The group will also not consider
>       general route optimization, or other problems that are not
>       related to the deployment and maintenance of NEMO Basic Support
>       protocols. Similarly, the group will not consider or rely on the
>       results of general routing architecture, Internet architecture,
>       or identifier-locator split issues that are discussed in
>       separate, long term efforts elsewhere in the IETF. Finally, the
>       group will not consider solutions that require changes from
>       correspondent nodes in the general Internet
> 
> (A.6) Bootstrapping mechanisms developed earlier in the MIP6 WG
>       require AAA support for Mobile IPv6. Part of this work is
>       already being done in the DIME WG, but the MEXT WG is chartered
>       to complete a design for RADIUS.
> 
> 
> Work items related to base specification maintenance include:
> 
> (B.1) Create and maintain issue lists that are generated on the basis
>       of implementation and interoperability experience. Address
>       specific issues with specific updates or revisions of the base
>       specification. One specific area of concern that should be
>       analyzed and addressed relates to multilink subnets.
> 
>       This work item relates only to corrections and
>       clarifications. The working group shall not revisit design
>       decisions or change the protocol.
> 
> (B.2) Update the IANA considerations of RFC 3775 to allow extensions for
>       experimental purposes as well passing of optional vendor-specific
>       information.
> 
> (B.3) Finish working group documents that are currently in process, and
>       submit for RFC. This includes prefix delegation protocol mechanism
>       for network mobility, and a MIB for NEMO Basic Support.
> 
> 
> Work items related to informational documentation include:
> 
> (C.1) Produce a design rationale that documents the historical
>       thinking behind the introduction of an alternative security
>       mechanism, the Authentication Protocol (RFC 4285).
> 
> 
> Goals and Milestones:
> 
> Aug 2007    Submit -00 draft on Route Optimization Needs for Aircraft
> and Spacecraft Deployments
> Aug 2007    Submit -00 draft on Route Optimization Needs for Automobile
> and Highway Deployments
> Aug 2007    Submit Multiple CoA Registration to IESG
> 
> Sep 2007    Submit I-D 'Motivation for Authentication I-D' to IESG for
> publication as Informational.
> Sep 2007    Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for
> publication as a Proposed Standard.
> 
> Oct 2007    Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for
> publication as a Proposed Standard
> Oct 2007    Submit -00 draft on Route Optimization needs for Personal
> Mobile Router
> 
> Nov 2007    Submit final doc on Route Optimization Needs for Aircraft
> and Spacecraft Deployments, for Informational
> Nov 2007    Submit I-D 'Goals for AAA HA Interface' to IESG for
> publication as Informational.
> 
> Dec 2007    Submit -00 draft for solution to aircraft/spacecraft problem
> Dec 2007    Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG
> for publication as a Proposed Standard.
> Dec 2007    Submit the final doc on Prefix Delegation for NEMO to the
> IESG, for Proposed Standard
> 
> Jan 2007    Submit final doc on Route Optimization Needs for Automobile
> and Highway Deployments, for Informational
> Jan 2007    Submit final doc on Route Optimization needs for Personal
> Mobile Router, for Informational
> 
> Feb 2008    Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for
> publication as a proposed standard.
> Feb 2008    Determine how to proceed with remaining automotive/Personal
> Mobile Router solutions
> 
> Mar 2008    Submit the final doc on MIB for NEMO Basic Support to the
> IESG, for Proposed Standard
> Mar 2008    Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG
> for publication as Informational.
> 
> Apr 2008    Submit Flow/binding policy format to IESG, for Proposed Standard
> Apr 2008    Submit Flow/binding policy transport to IESG, for Proposed
> Standard
> Apr 2007    Submit I-D 'Mobility Header Home Agent Switch Message' to
> IESG for publication as a Proposed Standard.
> 
> May 2008    Submit final doc for solution to aircraft/spacecraft problem
> to the IESG, for Proposed Standard
> May 2008    Recharter to work on the remaining automotive/Personal
> Mobile Router solutions
> 
> Jul 2007    Submit Multiple Interfaces Motivations and Scenario to IESG,
> for Informational
> Jul 2007    Submit Analysis of the use of Multiple Simultaneous Care-of
> Addresses and Home Agent addresses, for Informational
> 
> Aug 2008    Submit I-D(s) related to specific updates and corrections of
> RFC 3775 to IESG for publication as Proposed Standard.
> Aug 2008    Submit I-D 'Home agent reliability' to IESG for publication
> as a Proposed Standard.
> 
> 
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www1.ietf.org/mailman/listinfo/mext


_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext





--0-1884647686-1183156472=:44768
Content-Type: text/html; charset=ascii

<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:14pt"><div style="font-family: times new roman,new york,times,serif; font-size: 14pt;">Hi Jari,<br>&nbsp; In fact HA reliability work is almost over. I think the current draft is expected to go for WGLC soon and the subteam is almost closed. I don't think it would take Aug 08 to complete this work. HA reliability could be completely removed from this charter.<br><br>Kind regards,<br><br>Behcet<br><br><br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Suresh Krishnan &lt;suresh.krishnan@ericsson.com&gt;<br>To: Jari Arkko &lt;jari.arkko@piuha.net&gt;<br>Cc: mext@ietf.org<br>Sent: Friday, June 29, 2007 4:26:59 PM<br>Subject: Re: [MEXT] new charter version<br><br><div>Hi Jari,<br>&nbsp;&nbsp; The items A.2 and A.3 are reversed in the following
 descriptive text<br><br>"Deployment considerations call for (A.1) solutions to enable<br>dual-stack operation, (A.2) allowing the use of multiple interfaces in<br>mobile nodes, (A.3) mechanisms to support high-availability home<br>agents,..."<br><br>whereas in the following bulleted list A.2 talks about HA reliability <br>and A.3 talks about multiple interfaces in MNs.<br><br>Cheers<br>Suresh<br><br>Jari Arkko wrote:<br>&gt; Testing the new list... this list should have all the subscribers<br>&gt; of the existing three lists. For now, please continue your<br>&gt; technical discussions in the existing lists, except for charter<br>&gt; discussion which we can move here. In general, you do not<br>&gt; need to take any action with regards to list changes, once<br>&gt; we are ready to move complete away from the old lists we<br>&gt; can deal with the from the secretariat. Here's a pointer<br>&gt; to the list page:<br>&gt; <br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<a target="_blank"
 href="https://www1.ietf.org/mailman/listinfo/mext">https://www1.ietf.org/mailman/listinfo/mext</a><br>&gt; <br>&gt; Here's the new charter, revised according to comments<br>&gt; from many of you (thanks!) and the rest of the IESG.<br>&gt; <br>&gt; The charter will go out soon for public IETF review.<br>&gt; <br>&gt; ------<br>&gt; <br>&gt; Mobility EXTensions for IPv6 (MEXT)<br>&gt; <br>&gt; Chair(s):<br>&gt; TBD<br>&gt; <br>&gt; Internet Area Director(s):<br>&gt; Jari Arkko &lt;jari.arkko@piuha.net&gt;<br>&gt; Mark Townsley &lt;townsley@cisco.com&gt;<br>&gt; <br>&gt; Internet Area Advisor:<br>&gt; Jari Arkko &lt;jari.arkko@piuha.net&gt;<br>&gt; <br>&gt; Mailing Lists:<br>&gt; <a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mext">https://www1.ietf.org/mailman/listinfo/mext</a><br>&gt; <a target="_blank" href="http://www1.ietf.org/mail-archive/web/mext/current/index.html">http://www1.ietf.org/mail-archive/web/mext/current/index.html</a><br>&gt; <br>&gt;
 <br>&gt; Description of Working Group:<br>&gt; <br>&gt; Mobile IPv6 specifies routing support which permits an IPv6 host to<br>&gt; continue using its home address as it moves around the Internet,<br>&gt; enabling continuity of sessions. Mobile IPv6 supports transparency<br>&gt; above the IP layer, including maintenance of active transport level<br>&gt; sessions. In addition, NEMO network mobility mechanisms built on top<br>&gt; of Mobile IPv6 allow managing the mobility of an entire network, as it<br>&gt; changes its point of attachment to the Internet. The base<br>&gt; specifications consist of:<br>&gt; <br>&gt; o RFC 3775<br>&gt; o RFC 3963<br>&gt; o RFC 4877<br>&gt; <br>&gt; The MEXT Working Group continues the work of the MIP6, NEMO, and<br>&gt; MONAMI6 Working Groups.<br>&gt; <br>&gt; The primary goal of MEXT will be to (A) enhance base IPv6 mobility by<br>&gt; continuing work on developments that are required for wide-scale<br>&gt; deployments and specific
 deployment scenarios.&nbsp;&nbsp;Additionally, (B) the<br>&gt; working group will ensure that any issues identified by implementation<br>&gt; and interoperability experience are addressed, and that the base<br>&gt; specifications are maintained. (C) The group will also produce<br>&gt; informational documentation, such as design rationale documents or<br>&gt; description of specific issues within the protocol.<br>&gt; <br>&gt; Deployment considerations call for (A.1) solutions to enable<br>&gt; dual-stack operation, (A.2) allowing the use of multiple interfaces in<br>&gt; mobile nodes, (A.3) mechanisms to support high-availability home<br>&gt; agents, (A.4) ways to employ Mobile IPv6 in the presence of firewalls,<br>&gt; (A.5) address the specific needs of automotive and aviation<br>&gt; communities for route optimisation in network mobility, and (A.6)<br>&gt; support for AAA is needed as a continuation of earlier work on<br>&gt; bootstrapping.<br>&gt; <br>&gt; Work items
 related to large scale deployment include:<br>&gt; <br>&gt; (A.1) A Solution for MIP6 session continuity for dual stack hosts which<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; attach to IPv4 access networks. Additionally provide a mechanism<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for carrying IPv4 packets via the Home agent for MIP6 capable<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; dual-stack hosts.<br>&gt; <br>&gt; (A.2) A protocol based solution for enhancing the reliability of home<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; agents and a method to force a host to switch home agents.<br>&gt; <br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; A mechanism to force an MN to switch the HA that is currently<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; serving it. This is required in deployments where the HA needs to<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; be taken offline for maintenance.<br>&gt; <br>&gt; (A.3) Use of multiple interfaces.<br>&gt;
 <br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Today, the protocols do not provide suppport for simultaneous<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; differentiated use of multiple access technologies. Several<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; proposals exist for such support, and some of them have been<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; implemented and tested.<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; When a mobile host/router uses multiple network interfaces<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; simultaneously, or when multiple prefixes are available on a<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; single network interface, the mobile host/router would end up<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; with multiple Care-of Addresses (CoAs). In addition, the Home<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Agent might be attached to multiple network interfaces, or to a<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 single network interface with multiple prefixes, hence resulting<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; in the option to use multiple IP addresses for the Home<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Agent. This could result in the possibility of using a multitude<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of bi-directional tunnels between pairs of {Home Agent address,<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; CoA} and a number of associated issues: establishment, selection<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and modification of multiple simultaneous tunnels.<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The objective of the WG is to produce a clear problem statement<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and to produce standard track specifications to the problems<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; associated with the simultaneous use of multiple addresses for<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
 either mobile hosts using Mobile IPv6 or mobile routers using<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEMO Basic Support and their variants (FMIPv6, HMIPv6,<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; etc). Where the effects of having multiple prefixes on a single<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interface is identical to the effects of having multiple<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interfaces each with a single prefix, the WG will consider a<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; generalized approach to cater for multiple prefixes available to<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; a mobile host/router.<br>&gt; <br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The WG uses existing tunneling mechanisms defined for Mobile<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; IPv6. The involved nodes need to select which tunnel instance<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to use when multiple ones are available due to
 multiple<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; addresses on either end. But the WG does not plan to define a<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; new mechanism for this, but rather document how to use existing<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mechanisms based upon preferences or policies. In particular,<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the WG will consider that a tunnel is alive as long as packets<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; can be exchanged with the corresponding peer. In addition, local<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information, such as interface up/down events, or other failure<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; detection mechanisms can be used to quickly detect failure of<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; tunnel(s).<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Deliverables related to this
 include<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - A document explaining the motivations for a node using multiple<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; interfaces and the scenarios where it may end up with multiple<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; global addresses on its interfaces [Informational]<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - An analysis document explaining what are the limitations for<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mobile hosts using multiple simultaneous Care-of Addresses and Home<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Agent addresses using Mobile IPv6, whether issues are specific to<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Mobile IPv6 or not [Informational].<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - A protocol extension to support the registration of
 multiple<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Care-of Addresses at a given Home Agent address [Standard<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Track].<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; - A "Flow/binding policies exchange" solution for an exchange of<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; policies from the mobile host/router to the Home Agent and from the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Home Agent to the mobile host/router influencing the choice of the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Care-of Address and Home Agent address. The solution involves two<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; specifications, one for the policy format and another for its<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; transport [both Standard Track].<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <br>&gt; (A.4) Work on solutions to
 deal with firewalls and the problems that<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; firewalls cause as identified in RFC 4487.<br>&gt; <br>&gt; (A.5) Route optimization of network mobility.<br>&gt; <br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Three use cases have been identified for this. These are called<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the Aviation case, the Automotive case, and the Personal Mobile<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Router (consumer electronics) case, though the actual technical<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; problems are characterized by the type of movements and<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; environments more than by the specific industry using the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; technology. The group will explore these cases to gather<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; requirements and proceed with solving the open
 issues.<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (1) Airline and spacecraft community, who are deploying NEMO for<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control systems, as well as Internet connectivity and<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; entertainment systems. This use case is characterized by fast (~<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1000 km/h) moving objects over large distances (across<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; continents). The main technical problem is that tunneling-based<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; solutions imply a roundtrip to another continent and that BGP<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; based solutions imply significant churn in the global Internet<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; routing table.<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (2) Automotive industry who are deploying NEMO for
 in-car<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; communication, entertainment, and data gathering, possible<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; control systems use, and communication to roadside devices. This<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; use case is characterized by moderately fast (~ 100-300 km/h)<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; moving objects that employ local or cellular networks for<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; connectivity.<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; (3) Personal Mobile Routers, which are consumer devices that<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; allow the user to bring a NEMO network with the user while<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mobile, and communicate with peer NEMO Basic Support nodes<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; and nodes served by them.<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; After
 gathering the requirements for these types of deployments,<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; the working group will evaluate what type of route optimization<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; needs to be performed (if any), and formulate a solution to<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; those problems.<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; If no requirements for those scenarios can be collected by the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; deadline, it will be assumed that the work is premature, and<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that type of deployment will be dropped from the WG.<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The group will only consider airline and spacecraft solutions<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; that combine tunneling solutions for small movements with either<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; federated tunnel servers
 or slowly changing end host prefixes.<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The group will only consider personal mobile router requirements<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; about optimized routes to another mobile router belonging to the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; same operator. The group will only consider automotive industry<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; requirements to allow MR-attached hosts to directly access the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; network where MR has attached to. Work on automotive and<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; personal mobile router solutions requires rechartering.<br>&gt; <br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; The WG will not consider extensions to routing protocols. The<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group will not consider general multi-homing problems that are<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; not related to the deployment and maintenance of
 Mobile IPv6 or<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; NEMO Basic Support protocols. The group will also not consider<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; general route optimization, or other problems that are not<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; related to the deployment and maintenance of NEMO Basic Support<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; protocols. Similarly, the group will not consider or rely on the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; results of general routing architecture, Internet architecture,<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; or identifier-locator split issues that are discussed in<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; separate, long term efforts elsewhere in the IETF. Finally, the<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; group will not consider solutions that require changes from<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; correspondent nodes in the general Internet<br>&gt; <br>&gt; (A.6) Bootstrapping
 mechanisms developed earlier in the MIP6 WG<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; require AAA support for Mobile IPv6. Part of this work is<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; already being done in the DIME WG, but the MEXT WG is chartered<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; to complete a design for RADIUS.<br>&gt; <br>&gt; <br>&gt; Work items related to base specification maintenance include:<br>&gt; <br>&gt; (B.1) Create and maintain issue lists that are generated on the basis<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; of implementation and interoperability experience. Address<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; specific issues with specific updates or revisions of the base<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; specification. One specific area of concern that should be<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; analyzed and addressed relates to multilink subnets.<br>&gt; <br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; This work item
 relates only to corrections and<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; clarifications. The working group shall not revisit design<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; decisions or change the protocol.<br>&gt; <br>&gt; (B.2) Update the IANA considerations of RFC 3775 to allow extensions for<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; experimental purposes as well passing of optional vendor-specific<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; information.<br>&gt; <br>&gt; (B.3) Finish working group documents that are currently in process, and<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; submit for RFC. This includes prefix delegation protocol mechanism<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; for network mobility, and a MIB for NEMO Basic Support.<br>&gt; <br>&gt; <br>&gt; Work items related to informational documentation include:<br>&gt; <br>&gt; (C.1) Produce a design rationale that documents the historical<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; thinking
 behind the introduction of an alternative security<br>&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; mechanism, the Authentication Protocol (RFC 4285).<br>&gt; <br>&gt; <br>&gt; Goals and Milestones:<br>&gt; <br>&gt; Aug 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit -00 draft on Route Optimization Needs for Aircraft<br>&gt; and Spacecraft Deployments<br>&gt; Aug 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit -00 draft on Route Optimization Needs for Automobile<br>&gt; and Highway Deployments<br>&gt; Aug 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit Multiple CoA Registration to IESG<br>&gt; <br>&gt; Sep 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit I-D 'Motivation for Authentication I-D' to IESG for<br>&gt; publication as Informational.<br>&gt; Sep 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit I-D 'Mobile IPv6 Dual-Stack Operation' to IESG for<br>&gt; publication as a Proposed Standard.<br>&gt; <br>&gt; Oct 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit I-D 'Mobile IPv6 Vendor Specific Option' to IESG for<br>&gt; publication as a Proposed
 Standard<br>&gt; Oct 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit -00 draft on Route Optimization needs for Personal<br>&gt; Mobile Router<br>&gt; <br>&gt; Nov 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit final doc on Route Optimization Needs for Aircraft<br>&gt; and Spacecraft Deployments, for Informational<br>&gt; Nov 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit I-D 'Goals for AAA HA Interface' to IESG for<br>&gt; publication as Informational.<br>&gt; <br>&gt; Dec 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit -00 draft for solution to aircraft/spacecraft problem<br>&gt; Dec 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit I-D 'Mobile IPv6 Experimental Allocations' to IESG<br>&gt; for publication as a Proposed Standard.<br>&gt; Dec 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit the final doc on Prefix Delegation for NEMO to the<br>&gt; IESG, for Proposed Standard<br>&gt; <br>&gt; Jan 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit final doc on Route Optimization Needs for Automobile<br>&gt; and Highway Deployments, for Informational<br>&gt; Jan
 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit final doc on Route Optimization needs for Personal<br>&gt; Mobile Router, for Informational<br>&gt; <br>&gt; Feb 2008&nbsp;&nbsp;&nbsp;&nbsp;Submit the I-D 'RADIUS Mobile IPv6 Support' to IESG for<br>&gt; publication as a proposed standard.<br>&gt; Feb 2008&nbsp;&nbsp;&nbsp;&nbsp;Determine how to proceed with remaining automotive/Personal<br>&gt; Mobile Router solutions<br>&gt; <br>&gt; Mar 2008&nbsp;&nbsp;&nbsp;&nbsp;Submit the final doc on MIB for NEMO Basic Support to the<br>&gt; IESG, for Proposed Standard<br>&gt; Mar 2008&nbsp;&nbsp;&nbsp;&nbsp;Submit I-D 'Mobile IPv6 Operation with Firewalls' to IESG<br>&gt; for publication as Informational.<br>&gt; <br>&gt; Apr 2008&nbsp;&nbsp;&nbsp;&nbsp;Submit Flow/binding policy format to IESG, for Proposed Standard<br>&gt; Apr 2008&nbsp;&nbsp;&nbsp;&nbsp;Submit Flow/binding policy transport to IESG, for Proposed<br>&gt; Standard<br>&gt; Apr 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit I-D 'Mobility
 Header Home Agent Switch Message' to<br>&gt; IESG for publication as a Proposed Standard.<br>&gt; <br>&gt; May 2008&nbsp;&nbsp;&nbsp;&nbsp;Submit final doc for solution to aircraft/spacecraft problem<br>&gt; to the IESG, for Proposed Standard<br>&gt; May 2008&nbsp;&nbsp;&nbsp;&nbsp;Recharter to work on the remaining automotive/Personal<br>&gt; Mobile Router solutions<br>&gt; <br>&gt; Jul 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit Multiple Interfaces Motivations and Scenario to IESG,<br>&gt; for Informational<br>&gt; Jul 2007&nbsp;&nbsp;&nbsp;&nbsp;Submit Analysis of the use of Multiple Simultaneous Care-of<br>&gt; Addresses and Home Agent addresses, for Informational<br>&gt; <br>&gt; Aug 2008&nbsp;&nbsp;&nbsp;&nbsp;Submit I-D(s) related to specific updates and corrections of<br>&gt; RFC 3775 to IESG for publication as Proposed Standard.<br>&gt; Aug 2008&nbsp;&nbsp;&nbsp;&nbsp;Submit I-D 'Home agent reliability' to IESG for publication<br>&gt; as a Proposed Standard.<br>&gt;
 <br>&gt; <br>&gt; _______________________________________________<br>&gt; MEXT mailing list<br>&gt; MEXT@ietf.org<br>&gt; <a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mext">https://www1.ietf.org/mailman/listinfo/mext</a><br><br><br>_______________________________________________<br>MEXT mailing list<br>MEXT@ietf.org<br><a target="_blank" href="https://www1.ietf.org/mailman/listinfo/mext">https://www1.ietf.org/mailman/listinfo/mext</a><br></div></div><br></div></div></body></html>
--0-1884647686-1183156472=:44768--


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

_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext

--===============0222891421==--




From mext-bounces@ietf.org Sat Jun 30 13:10:49 2007
Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1I4gSh-0008GV-Ma; Sat, 30 Jun 2007 13:10:19 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1I4gSg-0008GN-S7
	for mext@ietf.org; Sat, 30 Jun 2007 13:10:18 -0400
Received: from p130.piuha.net ([193.234.218.130])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1I4gSZ-0001Wn-Vf
	for mext@ietf.org; Sat, 30 Jun 2007 13:10:18 -0400
Received: from p130.piuha.net (localhost [127.0.0.1])
	by p130.piuha.net (Postfix) with ESMTP id 61E561986A7
	for <mext@ietf.org>; Sat, 30 Jun 2007 20:10:11 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130])
	by p130.piuha.net (Postfix) with ESMTP id 1E6D119866D
	for <mext@ietf.org>; Sat, 30 Jun 2007 20:10:11 +0300 (EEST)
Message-ID: <46868E73.3080705@piuha.net>
Date: Sat, 30 Jun 2007 20:10:11 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.12 (X11/20070604)
MIME-Version: 1.0
To: mext@ietf.org
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: 2870a44b67ee17965ce5ad0177e150f4
Subject: [MEXT] test
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>,
	<mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org

Testing a list problem, please ignore.

Jari


_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext



