I think this charter requires some clarifications. Since this is about extensions to NETLMM protocols, it should clarify what principles it inherits from the NETLMM charter. For instance, one major thing that stands out is about no changes to the mobile node - I believe NETLMM's main value was seen as providing mobility without MN involvement and I don't believe we have consensus to allow any changes to the MN. I think this charter should explicitly clarify that. Other points worth clarifying are that the protocols that may be specified need to remain link layer agnostic and independent of a global mobility management mechanism that may be used with it. Cheers, Vidya > -----Original Message----- > From: ietf-announce-bounces@xxxxxxxx [mailto:ietf-announce- > bounces@xxxxxxxx] On Behalf Of IESG Secretary > Sent: Tuesday, April 14, 2009 1:00 PM > To: ietf-announce@xxxxxxxx > Cc: netext@xxxxxxxxxxxxxxxx > Subject: WG Review: Network-Based Mobility Extensions (netext) > > 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@xxxxxxxx) by Tuesday, > April > 21, 2009. > > Network-Based Mobility Extensions (netext) > ------------------------------------------------------------- > > Last Modified: 2009-04-03 > > Current Status: Proposed Working Group > > Chair(s): > TBD > > Internet Area Director(s): > Ralph Droms <rdroms@xxxxxxxxx> > Jari Arkko <jari.arkko@xxxxxxxxx> > > Internet Area Advisor: > TBD > > Mailing Lists: > http://www.mobileip.jp/mailman/listinfo/netext > > Description of Working Group: > > Proxy Mobile IPv6, specified in RFC 5213, is a network-based mobility > protocol. It uses a Mobile Access Gateway (MAG) and a Local Mobility > Anchor (LMA) to allow hosts to move around within a domain while > keeping > their address or address prefix stable. Proxy Mobile IPv6 has been > incorporated into a number of products and deployments are starting. > Certain deployment considerations, including localized routing and bulk > refresh of lifetime are already emerging. > > The working group will focus on the following topics relevant for > network-based mobility: > > Localized Routing: a specification for routing traffic between the > MAG(s) without involving the LMA. That is, allow the MAGs to route > traffic between hosts from one MAG to another, without being tunneled > all the way to the LMA. This reduces latency and backhaul load. > Applications such as voice can benefit from the reduced latency. Hosts > are not affected, as they still send and receive their packets via the > MAG. > > Bulk Refresh: a specification of improving the signaling load for > binding lifetime refresh. The current specifications call for the > handling of each mobility session independent of each other. When a > large number of hosts are served by a single MAG, a periodic refresh of > the binding lifetimes can lead to a signaling storm. The purpose of the > Bulk Refresh feature is to construct a protocol feature that allows > such > refreshes to occur on a per-MAG basis. > > LMA Redirection: a specification for allowing an LMA to redirect a MAG > to another LMA. This is primarily needed as a way to perform load > balancing, and is complementary to the initial LMA discovery work in > the > NETLMM WG. > > The proposed activity will be complementary to the existing IETF > Working > Groups, notably the NETLMM and MEXT WGs. The NETEXT working group will > also act as the primary forum where new extensions on top of the Proxy > Mobile IPv6 protocol can be developed. The addition of such new > extensions to the working group involves addition of the extension to > this charter through the normal rechartering process. > > Milestones > > May 2009 WG chartered > July 2009 Initial WG draft on Bulk Refresh > September 2009 Initial WG draft on LMA Redirection > November 2009 Initial WG draft on Route Optimization > December 2009 Submit Bulk Refresh to IESG for publication as a > Proposed Standard RFC > January 2009 Submit LMA Redirection to IESG for publication as a > Proposed Standard RFC > April 2010 Submit Route Optimization to IESG for publication > as a Proposed Standard RFC > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf-announce _______________________________________________ Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf