[STDS-802-16] Fwd: [802SEC] FW: [New-work] WG Review: Multihoming and Mobile Nodes in IPv6 (monami6)
FYI. This mentions 802.16. It is most closely related to 802.21.
Roger
>802 Task Group Chairs,
>
>The following announcement of new work in the IETF may be of interest to
>your Task Group member. Please forward as appropriate.
>
>Paul
>
>-----Original Message-----
>From: new-work-bounces@ietf.org [mailto:new-work-bounces@ietf.org] On
>Behalf Of The IESG
>Sent: Wednesday, September 21, 2005 8:23 AM
>To: new-work@ietf.org
>Subject: [New-work] WG Review: Multihoming and Mobile Nodes in IPv6
>(monami6)
>
>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 September
>28.
>
>+++
>
>Multihoming and Mobile Nodes in IPv6 (monami6)
>==============================================
>
>Current Status: Proposed Working Group
>
>Chairs:
>TBD
>
>Responsible AD:
>Margaret Wasserman <margaret@thingmagic.com>
>
>Mailing Lists:
>List: monami6@ietf.org
>Subscribe: https://www1.ietf.org/mailman/listinfo/monami6
>HTTP Archives:
>http://www.ietf.org/mail-archive/web/monami6/current/index.html
>FTP Archives: ftp://ftp.ietf.org/ietf-mail-archive/monami6
>
>Additional Web Page:
>http://www.nautilus6.org/ietf/
>
>Description:
>
>There is currently rapid development in the area of new wireless
>standards (802.11*, 802.16, 802.20, UMTS, Bluetooth and others). At the
>same time, terminals which have radio and protocol support for two,
>three or even more standards are appearing. This opens the possibility
>of using multiple access types simultaneously, with each access used to
>transport the traffic for which it is most appropriate. For instance, an
>intermittent, but high-bandwidth access type might be used for file
>transfers (e.g., music download) while a low-bandwidth, high reliability
>access might simultaneously be used for a voice call.
>
>In the meantime, IP-level mobility support protocols such as Mobile
>IPv6 (RFC 3775) and NEMO Basic Support (RFC 3963) have been conceived by
>the IETF to support handoffs for IPv6 mobile hosts and routers,
>respectively.
>
>However, these protocols do not today provide standardised 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. Some of the issues are very specific to mobility and are
>generally applicable to both mobile hosts and mobile routers using
>Mobile IPv6 and NEMO Basic Support respectively. Some of these issues
>can be resolved with relatively small and straight-forward changes to
>Mobile IPv6 and NEMO Basic Support (e.g. multiple CoAs registration).
>
>The objective of the Monami6 WG is to produce a clear problem statement
>and to produce standard track specifications to the straight-forward
>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, Monami6
>will consider a generalized approach to cater for multiple prefixes
>available to a mobile host/router. Once this is done, the WG might
>re-charter in order to work on more generic issues that prevent to take
>advantage of the multiple CoAs and HoAs available to mobile nodes and
>routers.
>
>The WG will not work on tunnel selection based on dynamic discovery of
>tunnel characteristics, but will assume that it is given by policy or
>other mechanisms external to the Monami6 work. In particular, the WG
>will consider that a tunnel is alive as long as BU/BACK can be exchanged
>with the corresponding peer. In addition, local information, such as an
>interface went down, can be used to quickly detect failure of tunnel(s).
>
>WG Deliverables:
>
>- A document explaining the needs and the design goals for mobile hosts
>and mobile routers using multiple global addresses on its interface(s).
>[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 "MCoA" solution to register multiple Care-of Addresses for a given
>home 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 interface
>[Standard Track].
>
>
>Goals and Milestones:
>
>APR 06 Submit Motivations and Goals to IESG APR 06 Submit Analysis of
>the use of Multiple Simultaneous Care-of Addresses and Home Agents in
>Mobile IPv6 APR 06 Submit Multiple CoA Registration to IESG DEC 06
>Submit Flow/binding policies exchange to IESG
>
>
>
>_______________________________________________
>New-work mailing list
>New-work@ietf.org
>https://www1.ietf.org/mailman/listinfo/new-work
>