From nobody Fri Aug 1 03:24:18 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CC8F1A0654 for ; Fri, 1 Aug 2014 03:24:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wqlpXrXSMZlJ for ; Fri, 1 Aug 2014 03:24:15 -0700 (PDT) Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E4BE1A0648 for ; Fri, 1 Aug 2014 03:24:14 -0700 (PDT) Received: by mail-la0-f46.google.com with SMTP id b8so3068584lan.33 for ; Fri, 01 Aug 2014 03:24:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=vagnLs+lf5aENSwY4GrbWNpVGGa7d0K0ORGxo/wV3I4=; b=gZOgtz5ftAc/DCpYu+rt7QK9t+ux5DVQr7+JERt0f7feqVGNEClxm77NnmcPEKeB2C Acn6A3lWATLIOPXUK6LESRBc8B8h18UGFBPsq6wmfvaOScyytnpPmP/mO/TapjA4G2yL jNERkHLWZkhFtXpJmGnYF0rCQpBF3X0F/GO16/n4WyD8rYYF/vUKsMQj0N8K9j/gI3w3 dpKP5CL44SGCNuvXbmHinuPVI24hfLOX2kZadrPnzFxT94Skvf4CHYV+aWZu/bBmX1Uw RDW99WBDaoQ6AxSqX6nNLro7PgmjbCa11wrbQZGkEYh/7lBd2qMD8qqJ4chO64kE0iA5 jLjw== X-Received: by 10.112.225.229 with SMTP id rn5mr4217940lbc.48.1406888653263; Fri, 01 Aug 2014 03:24:13 -0700 (PDT) Received: from [10.17.0.21] ([83.150.126.201]) by mx.google.com with ESMTPSA id rd5sm4492002lac.42.2014.08.01.03.24.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 01 Aug 2014 03:24:12 -0700 (PDT) Message-ID: <53DB6ACA.6000205@gmail.com> Date: Fri, 01 Aug 2014 13:24:10 +0300 From: Jouni Korhonen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "dmm@ietf.org" References: <53D8AED8.4060705@gmail.com> In-Reply-To: <53D8AED8.4060705@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/GLtEOHDnE6aFix-jX_EapjZ9GN4 Subject: Re: [DMM] interims i.e. teleconferences.. X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2014 10:24:17 -0000 Folks, To our surprise we seem not to be in that hurry after all.. The next IESG window is now closed for rechartering, which means postponing the completion of the rechartering at least by two weeks. Regarding telcos we could resume around September. I myself have some vacations left in August. - Jouni & Dapeng 7/30/2014 11:37 AM, Jouni Korhonen kirjoitti: > Folks, > > 14th or 15th Aug are the next possible dates for an interim telco (1-2h > duration). To accommodate east and west, I think 16:00 CET+1 is doable > (late in Japan, early in US). Next time we'll shift the time to be less > convenient for Europeans. > > Speak up now if the date does not fit and you think your presense is > required. > > Agenda is rather simple. If we are still working on the charter, then > we'll work on that. If the charter has been shipped already, we > concentrate srtucturing the work as discussed in Toronto. > > - Jouni & Dapeng From nobody Mon Aug 4 23:59:33 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CEBE1B291D for ; Mon, 4 Aug 2014 23:59:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VDgELk1wY_NO for ; Mon, 4 Aug 2014 23:59:29 -0700 (PDT) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28D2E1B2919 for ; Mon, 4 Aug 2014 23:59:28 -0700 (PDT) Received: by mail-la0-f47.google.com with SMTP id mc6so364573lab.20 for ; Mon, 04 Aug 2014 23:59:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=reL55lyPteYxr/cYDodLMWm2EsFUeRRrzS7XTSQTaIg=; b=I8xaNEhoJ/tZYe/8R7cvt7uQZg5KzyLNrKILIiMCw9UBvNrAeyYjvz97+aqh+qNdx5 8zTJoqJiJi7YgP7XgQ3xn6HwohURuSVTXpScc/Q45Z3UacCsByn5Mtd2r20eXswTd0RX 4NrBjm5kTa61QBasRK21DXhxBLbN6YqaSzz2FwfjUwci1A3qxualSx1z0KxTj2pnFR1M R+JCVuRU/FmGYnTWyBsw8TqQ/o5xHZmAz8KFqzCF2fjm/QEYQVnRf73Fxefwg34fLswl 2Wv4UlByh+g53a9PjRElXtiwn6w3IyxcxfDwBk+q1jTapaFndGpQ23ukpHDivFtyOLRU BToA== X-Received: by 10.152.87.229 with SMTP id bb5mr1672170lab.75.1407221967322; Mon, 04 Aug 2014 23:59:27 -0700 (PDT) Received: from [188.117.15.107] ([188.117.15.107]) by mx.google.com with ESMTPSA id f2sm1390406lbo.2.2014.08.04.23.59.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 04 Aug 2014 23:59:26 -0700 (PDT) Message-ID: <53E080CC.10209@gmail.com> Date: Tue, 05 Aug 2014 09:59:24 +0300 From: Jouni Korhonen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "dmm@ietf.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/xzPXw4ZX4CbbCaMCsD4EEP8pxrQ Subject: [DMM] ietf90 meeting minutes uploaded X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2014 06:59:31 -0000 Folks, Just to inform that the combined Thu+Fri meeting minutes have been uploaded. Thanks to Danny & John for taking excellent notes. Go to http://tools.ietf.org/wg/dmm/minutes - Jouni From nobody Tue Aug 5 01:43:58 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C474D1B296C for ; Tue, 5 Aug 2014 01:43:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VkiIi2IDeV5f for ; Tue, 5 Aug 2014 01:43:52 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 705501B28F9 for ; Tue, 5 Aug 2014 01:43:52 -0700 (PDT) Received: from [192.168.1.6] (88.244.101.116.dynamic.ttnet.com.tr [88.244.101.116]) by mrelay.perfora.net (node=mreueus002) with ESMTP (Nemesis) id 0Mg5dj-1X2ocx47xF-00NTBr; Tue, 05 Aug 2014 10:43:50 +0200 Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: text/plain; charset=us-ascii From: Alper Yegin In-Reply-To: <53D8AAE0.4040301@gmail.com> Date: Tue, 5 Aug 2014 11:43:46 +0300 Content-Transfer-Encoding: quoted-printable Message-Id: <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> References: <53D17F75.3030207@gmail.com> <53D7A012.2050700@gmail.com> <53D8AAE0.4040301@gmail.com> To: Jouni Korhonen X-Mailer: Apple Mail (2.1283) X-Provags-ID: V02:K0:CLMO87zjRobDYagrcV5bP1uofcxf7liTUrRHN3eApU0 Gh8vcsznF0bm471vH3S/PAAI+ID4Zq+xP5Yg2TMxWYbhtHjavO anIjrgCx7sDfixruoy3MPKgbvAwNKJHNWB9Vnua9aM9L0l+XO/ rbQbD6ISP7+K5ff6zfmOlRSq8eheNDAAk5Cd2q24pFApl38RbM iwiG4GghohoYu7nPS1wKSnm8gJYQcCQR1pAJxhgBNZWVPUjOLP y3OyzUiS0iwSvhMItbHTG7ApOPVELBTDmHD+qfFGkbi5gqfFyz NAqt55selvC2BA9FqL/RUSQHvV76sYE6Ofw1Wu2Jkx4yJJwst2 zCzUW8DfA2Ws6TmV25jF0tAnAvKVvU2nlXY8fZe1EXqWfZ+mPz xQVxruWC+++7Q== Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/QnhZtpnL9oKKM8NKSQMZoEu9vK8 Cc: "dmm@ietf.org" Subject: Re: [DMM] regarding the re-chartering.. X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2014 08:43:56 -0000 Hello, Thank you Kostas for this rewrite. The charter reads better now. Please see below for few comments. On Jul 30, 2014, at 11:20 AM, Jouni Korhonen wrote: > Folks, >=20 > A major rewrite of the charter is in github (and below). Thanks to = Kostas providing excellent feedbask on the text. Comments are welcome. >=20 > -------------------------------------------------------------------- >=20 > Description of Working Group: >=20 > Mobility management solutions lie at the center of the wireless = Internet > and enable mobile devices to partake in IP networks anytime and > anywhere. The IETF Distributed Mobility Management (DMM) working group > (WG) specifies solutions for IP networks so that traffic can be > expedited between mobile and correspondent nodes. DMM solutions aim = for > transparency above the IP layer, including maintenance of active > transport level sessions when mobile hosts or mobile networks change > their point of attachment to the Internet. >=20 > Wireless network deployments have traditionally relied on hierarchical > schemes that often lead to centralized deployment models, where a = small > number of mobility anchors manage both mobility and reachability for a > mobile node. The DMM WG will consider the latest developments in = mobile > networking research and operational practice (i.e. flat network > architectures, the impact of virtualization, new deployment needs as > wireless access technologies evolve in the coming years) and will > describe how distributed mobility management addresses the new needs = in > this area better than previously standardized solutions. >=20 > A topic of particular focus will be mobility anchoring in this new > context, and the DMM working group is chartered to work on > maintenance-oriented extensions of the Mobile IPv6 protocol family = (RFC > 5213, RFC 5844, RFC 5555, RFC 5568, and RFC 6275) as well as new > approaches which capitalize on other protocols specified by the IETF. > When extending protocols that are not based on Mobile IP, DMM = solutions > will be have to be reviewed by the corresponding WGs. >=20 > IPv6 is assumed to be present in both the mobile host/router and the > access networks. DMM solutions are primarily targeted at IPv6 > deployments and are not required to support IPv4, in particular for = the > case where private IPv4 addresses and/or NATs are used. DMM solutions > must maintain backward compatibility: If the network or the mobile > host/router does not support the distributed mobility management > protocol that should not prevent the mobile host/router gaining basic > access (i.e., nomadic) to the network. >=20 > Contrary to earlier IP mobility protocols, mobility management = signaling > paths and end-user traffic forwarding paths may differ. Further, > mobility-related functions may be located in separate network nodes. > DMM > solutions should not distinguish between physical or virtualized > networking functions. Whenever applicable, clarifications and = additional > features/capabilities for specific networking function deployment > models, e.g. in virtualized environments, are in-scope and encouraged. > Solutions may also specify the selection between the care-of addresses > and home address(es)/prefix(es) for different application use cases. >=20 > Work items related to distributed mobility management include: >=20 > o Distributed mobility management deployment models and = scenarios: > describe the target high-level network architectures and > deployment models where distributed mobility management > protocol solutions could apply. >=20 Can someone elaborate on what kind of information will go into such a = document? > o Enhanced mobility anchoring: define protocol solutions for a > gateway and mobility anchor assignment and mid-session mobility > anchor switching that go beyond what has been specified, for > example, in RFC 6097, 6463, and 5142. Traffic steering > associated with the anchor switch is also in-scope if deemed > appropriate. >=20 > o Forwarding path and signaling management: the function > that handles mobility management signaling interacts with the > DMM network elements for managing the forwarding state > associated with a mobile node's IP traffic. These two functions > may or may not be collocated. Furthermore, the forwarding state > may also be distributed into multiple network elements instead > of a single network element (e.g., anchor). Protocol extensions > or new protocols will be specified to allow the above mentioned > forwarding path and signalling management. >=20 I cannot separate "mobility anchoring" from "fwding path and signaling = management". Wherever you want to set your anchor or move your anchor to, you'd need = signaling and setting up data path. The two are inseparable. Having said that, I'm OK to keep the current work item descriptions and = finalize rechartering. Once we have detailed discussions about the = breakdown of the work, we can come back and refine the goals and = milestones (as already stated below [*]). > o Exposing mobility state to mobile nodes and network nodes: > define solutions that allow, for example, mobile nodes to = select > either a care-of address or a home address depending on an > application' mobility needs. In order to enable this > functionality, the network-side control functions and other > networking nodes must also be able to exchange appropriate > control information, as well as to the mobile nodes and their > applications. >=20 > The working group may decide to extend the current milestones based on > the new information and knowledge gained during working on other > documents listed in the initial milestones. [*] Cheers, Alper > Possible new documents and > milestones must still fit into the overall DMM charter scope as = outlined > above. >=20 > Goals and Milestones: >=20 > Feb 2015 - Submit 'The deployment models and scenarios' as a working > group document(s). To be Informational RFC. >=20 > Feb 2015 - Submit 'Enhanced mobility anchoring' as a working group > document. To be Proposed Standard. >=20 > Feb 2015 - Submit 'Forwarding path and signaling management' as a > working group document. To be Proposed Standard. >=20 > May 2015 - Submit 'Exposing mobility state to mobile nodes and = network > nodes' as a working group document(s). To be Proposed > Standard. >=20 >=20 > May 2015 - Submit 'The deployment models and scenarios' submitted to > the IESG. To be Informational RFC. >=20 > Jun 2015 - Submit 'Enhanced mobility anchoring' submitted to the = IESG. > To be Proposed Standard. >=20 > Jun 2015 - Submit 'Forwarding path and signaling management' = submitted > to the IESG. To be Proposed Standard. >=20 > Oct 2015 - Submit 'Exposing mobility state to mobile nodes and = network > nodes' submitted to the IESG. To be Proposed Standard. >=20 >=20 >=20 > 7/29/2014 4:22 PM, Jouni Korhonen kirjoitti: >> The webex sessions have been cancelled in accordance of better IETF >> process compliancy. New dates will be announced rougghly two weeks = ahead >> of tomorrow. >>=20 >> You can (and should) still actively send edits to the list and I'll >> update the text accordingly. Maybe we manage to get ready even = without a >> call! >>=20 >> - Jouni & Dapeng >>=20 >> 7/25/2014 12:49 AM, Jouni Korhonen kirjoitti: >>> Folks, >>>=20 >>> The latest charter draft can be found here: >>> = https://github.com/jounikor/dmm-re-charter/blob/master/recharter_draft.txt= >>>=20 >>>=20 >>> The deadline for the text chnges are 31st July. I'll setup a call = for >>> next week so that those who want to dial in and have verbal = commenting >>> can do that. In a meanwhile, email works as usual for updates and >>> comments on the text. The actual milestone dates are to be done last = but >>> suggestions are more than welcome. >>>=20 >>> - Jouni & Dapeng >=20 > _______________________________________________ > dmm mailing list > dmm@ietf.org > https://www.ietf.org/mailman/listinfo/dmm From nobody Thu Aug 7 23:49:30 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F8FD1A035F for ; Thu, 7 Aug 2014 23:48:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.191 X-Spam-Level: X-Spam-Status: No, score=-6.191 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id shKk6qOeakSf for ; Thu, 7 Aug 2014 23:47:59 -0700 (PDT) Received: from worker1.doodle.com (worker1.doodle.com [188.92.145.81]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98A761A0350 for ; Thu, 7 Aug 2014 23:47:59 -0700 (PDT) Received: from worker1.doodle.com (localhost [127.0.0.1]) by worker1.doodle.com (Postfix) with ESMTP id 67939104E093 for ; Fri, 8 Aug 2014 08:47:56 +0200 (CEST) Date: Fri, 8 Aug 2014 08:47:56 +0200 (CEST) From: "Jouni Korhonen (via Doodle)" To: Message-ID: <1746163051.894049.1407480476421.POLL_INVITECONTACT_PARTICIPANT_INVITATION.doodle@worker1> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_894048_1552420122.1407480476420" Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/2ntCJurrmbZV6WCzkLqpk2m_rk0 X-Mailman-Approved-At: Thu, 07 Aug 2014 23:49:28 -0700 Subject: [DMM] DMM interin X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Jouni Korhonen List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2014 06:48:02 -0000 ------=_Part_894048_1552420122.1407480476420 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi there, Jouni Korhonen (jounikor@gmail.com) invites you to participate in the Doodle poll "DMM interin". Jouni Korhonen says: Folks, =20 Lets start preparing for the DMM Interim Telco. Select your preferred times by 12th Aug. The interim will last 2h.=20 =20 - Jouni & Dapeng Participate now https://doodle.com/bn78u9ck57agk8v6?tmail=3Dpoll_invitecontact_participant_= invitation&tlink=3Dpollbtn What is Doodle? Doodle is a web service that helps Jouni Korhonen to find a suitable date for meeting with a group of people. Learn more about how Doodle works. (https://doodle.com/main.html?tlink=3DcheckOutLink&tmail=3Dpoll_inviteconta= ct_participant_invitation) ---------------------------------------------------------------------- You have received this e-mail because "Jouni Korhonen" has invited you to participate in the Doodle poll "DMM interin." ---- Doodle AG, Werdstrasse 21, 8021 Z=C3=BCrich ------=_Part_894048_1552420122.1407480476420 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =
=09
Jouni Korhonen invites you = to participate in the Doodle poll "DMM interin."
=09
=09 =09 =09
=09 =09=09 =09=09 =09=09=09=09=09=09=09 =09=09 =09=09=09=09=09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09
=09=09 =09=09=09 =09=09 =09 =09=09 =09=09 =09=09 =09 =09=09 =09=09=09 =09=09 =09=09 =09=09 =09=09 =09 =09=09 =09=09
=09=09 =09 =09=09 =09 =09=09=09 =09 =09=09=09
=09
=09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09
=09=09=09=09=09=09
=09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09 =09=09
=09=09=09=09=09=09
=09=09 =09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09 =09=09
=09=09=09=09=09=09
"DMM interin= ". =09=09=09=09=09=09
=09=09=09=09=09
=09=09 =09
=09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09 =09=09
=09=09=09=09=09=09
=09=09=09=09=09=09=09Jouni Korhonen says: =09=09=09=09=09=09
=09=09=09=09=09=09
=09=09=09=09=09=09=09Folks,

Lets start preparing for the DMM Inter= im Telco. Select your preferred times by 12th Aug. The interim will last 2h= .

- Jouni & Dapeng =09=09=09=09=09=09
=09=09=09=09=09
=20 =09
=09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09 =09=09
=
=09=09=09=09=09=09 =09=09=09=09=09=09 =09=09=09=09=09=09 =09=09=09=09=09=09=09 =09=09=09=09=09=09 =09=09=09=09=09=09 =09=09=09=09=09=09 =09=09=09=09=09
=09=09=09=09=09=09=09=09Participate now =09=09=09=09=09=09=09
=09=09=09=09=09
=
=09
=09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09 =09=09
=09=09=09=09=09=09 =09=09=09=09=09 =09=09=09=09=09=09
=20 =09=09=09=09=09=09=09 What is Doodle? Doodle is a web service that helps Jouni Korhonen to find a suitable dat= e for meeting with a group of people. Learn more about how Doodle works.
=20 =09=09=09=09=09=09
=09=09=09=09=09
=09
=09=09 =09=09 =09 =09=09 =09=09 =09=09 =09 =09=09 =09 =09=09 =09 =09=09 =09 =09=09 =09=09 =09=09 =09 =09=09 =09=09 =20 =09=09
=09=09 =09You have received this e-mail because "Jouni Korhonen= " has invited you to participate in the Doodle poll "DMM interin.= " =09=09
=09
=09 =09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09
=09=09=09=09=09=09
To: Message-ID: <1147036039.34861.1407501135945.POLL_INVITECONTACT_PARTICIPANT_INVITATION.doodle@worker1> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_34860_882597524.1407501135944" Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/YFtiDcV8bcPMWIOsj0B2D4Ji9rU X-Mailman-Approved-At: Fri, 08 Aug 2014 05:32:55 -0700 Subject: [DMM] DMM interim 2 X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Jouni Korhonen List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Aug 2014 12:32:21 -0000 ------=_Part_34860_882597524.1407501135944 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi there, Jouni Korhonen (jounikor@gmail.com) invites you to participate in the Doodle poll "DMM interim 2". Jouni Korhonen says: Folks, =20 The DMM Interim Telco #2. Select your preferred times by 13th Aug. The interim will last max 2h. =20 - Jouni & Dapeng Participate now https://doodle.com/pge8b2renhtu8dgc?tmail=3Dpoll_invitecontact_participant_= invitation&tlink=3Dpollbtn What is Doodle? Doodle is a web service that helps Jouni Korhonen to find a suitable date for meeting with a group of people. Learn more about how Doodle works. (https://doodle.com/main.html?tlink=3DcheckOutLink&tmail=3Dpoll_inviteconta= ct_participant_invitation) ---------------------------------------------------------------------- You have received this e-mail because "Jouni Korhonen" has invited you to participate in the Doodle poll "DMM interim 2." ---- Doodle AG, Werdstrasse 21, 8021 Z=C3=BCrich ------=_Part_34860_882597524.1407501135944 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable =
=09
Jouni Korhonen invites you = to participate in the Doodle poll "DMM interim 2."
=09
=09 =09 =09
=09 =09=09 =09=09 =09=09=09=09=09=09=09 =09=09 =09=09=09=09=09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09
=09=09 =09=09=09 =09=09 =09 =09=09 =09=09 =09=09 =09 =09=09 =09=09=09 =09=09 =09=09 =09=09 =09=09 =09 =09=09 =09=09
=09=09 =09 =09=09 =09 =09=09=09 =09 =09=09=09
=09
=09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09
=09=09=09=09=09=09
=09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09=09=09=09=09=09=09 =09=09=09=09=09=09=09=09 =09 =09 =09=09
=09=09=09=09=09=09
=09=09 =09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09 =09=09
=09=09=09=09=09=09
"DMM interim= 2". =09=09=09=09=09=09
=09=09=09=09=09
=09=09 =09
=09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09 =09=09
=09=09=09=09=09=09
=09=09=09=09=09=09=09Jouni Korhonen says: =09=09=09=09=09=09
=09=09=09=09=09=09
=09=09=09=09=09=09=09Folks,

The DMM Interim Telco #2. Select your = preferred times by 13th Aug. The interim will last max 2h.

- Jouni= & Dapeng =09=09=09=09=09=09
=09=09=09=09=09
=20 =09
=09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09 =09=09
=
=09=09=09=09=09=09 =09=09=09=09=09=09 =09=09=09=09=09=09 =09=09=09=09=09=09=09 =09=09=09=09=09=09 =09=09=09=09=09=09 =09=09=09=09=09=09 =09=09=09=09=09
=09=09=09=09=09=09=09=09Participate now =09=09=09=09=09=09=09
=09=09=09=09=09
=
=09
=09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09 =09=09=09=09=09 =09=09=09=09 =09=09=09 =09=09
=09=09=09=09=09=09 =09=09=09=09=09 =09=09=09=09=09=09
=20 =09=09=09=09=09=09=09 What is Doodle? Doodle is a web service that helps Jouni Korhonen to find a suitable dat= e for meeting with a group of people. Learn more about how Doodle works.
=20 =09=09=09=09=09=09
=09=09=09=09=09
=09
=09=09 =09=09 =09 =09=09 =09=09 =09=09 =09 =09=09 =09 =09=09 =09 =09=09 =09 =09=09 =09=09 =09=09 =09 =09=09 =09=09 =20 =09=09
=09=09 =09You have received this e-mail because "Jouni Korhonen= " has invited you to participate in the Doodle poll "DMM interim = 2." =09=09
=09
=09 =09=09 =09=09=09 =09=09=09=09 =09=09=09=09=09
=09=09=09=09=09=09
Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/QuBdpWHCClr0Embw3yCtEnVd9A8 Subject: [DMM] DMM interim calls X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 07:59:23 -0000 Folks, Based on the doodle 2nd Sep and 16th Sep are the days for the interim calls. I'll initiate the formal invitation soon. - Jouni & Dapeng From nobody Wed Aug 13 04:42:16 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9E9E1A8707 for ; Wed, 13 Aug 2014 04:42:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id a1WoCPW1AAWq for ; Wed, 13 Aug 2014 04:42:13 -0700 (PDT) Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 09E271A085C for ; Wed, 13 Aug 2014 04:42:12 -0700 (PDT) Received: by mail-lb0-f178.google.com with SMTP id c11so8251631lbj.9 for ; Wed, 13 Aug 2014 04:42:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=GP3JLZ3P5JmkgqTt5ftrjjcne1MhFqhmnzDLl38r3UA=; b=FedsXO7F7YfxHTOZDzYM+Z5p0ePA2kbvLXN5QEd8ua6es/AeJXJ2TE+7wA0OB0wYDB VYFMF3ha30bt+7l/PPMCD7Q19dMlK5aMhcXISGWjSzDg4NRcbuz7pqUX2MectAp//p2M 1DNwsmXxObCvQ9byrM8gAxmwd+T6c7bs7PM2O6VHvoaP3EVD8VyY+Qk6MFWXxMboISGR dNAKlGBXss8b+QnrGFgCj9nzPBLojrRKq6/hCWUiZP5aaEOl5yweqP7fw4ScN14J4e8S kDyxQBsgD/CQ5aQBcaz5REBhaorEeQ8/bzeSkfFZ/LWGCizY2hOvmSVo2o6LfNq4p0vb UmbQ== X-Received: by 10.152.10.169 with SMTP id j9mr4014685lab.69.1407930131312; Wed, 13 Aug 2014 04:42:11 -0700 (PDT) Received: from [10.17.0.23] ([83.150.126.201]) by mx.google.com with ESMTPSA id l4sm1061943lam.2.2014.08.13.04.42.09 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Aug 2014 04:42:10 -0700 (PDT) Message-ID: <53EB4F10.1040502@gmail.com> Date: Wed, 13 Aug 2014 14:42:08 +0300 From: Jouni Korhonen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Alper Yegin References: <53D17F75.3030207@gmail.com> <53D7A012.2050700@gmail.com> <53D8AAE0.4040301@gmail.com> <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> In-Reply-To: <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/e4nTQdfOQ8T3yM0-fA8zQVHjC4A Cc: "dmm@ietf.org" Subject: Re: [DMM] regarding the re-chartering.. X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 11:42:16 -0000 Alper, all, 8/5/2014 11:43 AM, Alper Yegin kirjoitti: > Hello, > > Thank you Kostas for this rewrite. The charter reads better now. > > Please see below for few comments. > > > On Jul 30, 2014, at 11:20 AM, Jouni Korhonen wrote: > >> Folks, >> >> A major rewrite of the charter is in github (and below). Thanks to Kostas providing excellent feedbask on the text. Comments are welcome. >> >> -------------------------------------------------------------------- >> >> Description of Working Group: >> >> Mobility management solutions lie at the center of the wireless Internet >> and enable mobile devices to partake in IP networks anytime and >> anywhere. The IETF Distributed Mobility Management (DMM) working group >> (WG) specifies solutions for IP networks so that traffic can be >> expedited between mobile and correspondent nodes. DMM solutions aim for >> transparency above the IP layer, including maintenance of active >> transport level sessions when mobile hosts or mobile networks change >> their point of attachment to the Internet. >> >> Wireless network deployments have traditionally relied on hierarchical >> schemes that often lead to centralized deployment models, where a small >> number of mobility anchors manage both mobility and reachability for a >> mobile node. The DMM WG will consider the latest developments in mobile >> networking research and operational practice (i.e. flat network >> architectures, the impact of virtualization, new deployment needs as >> wireless access technologies evolve in the coming years) and will >> describe how distributed mobility management addresses the new needs in >> this area better than previously standardized solutions. >> >> A topic of particular focus will be mobility anchoring in this new >> context, and the DMM working group is chartered to work on >> maintenance-oriented extensions of the Mobile IPv6 protocol family (RFC >> 5213, RFC 5844, RFC 5555, RFC 5568, and RFC 6275) as well as new >> approaches which capitalize on other protocols specified by the IETF. >> When extending protocols that are not based on Mobile IP, DMM solutions >> will be have to be reviewed by the corresponding WGs. >> >> IPv6 is assumed to be present in both the mobile host/router and the >> access networks. DMM solutions are primarily targeted at IPv6 >> deployments and are not required to support IPv4, in particular for the >> case where private IPv4 addresses and/or NATs are used. DMM solutions >> must maintain backward compatibility: If the network or the mobile >> host/router does not support the distributed mobility management >> protocol that should not prevent the mobile host/router gaining basic >> access (i.e., nomadic) to the network. >> >> Contrary to earlier IP mobility protocols, mobility management signaling >> paths and end-user traffic forwarding paths may differ. Further, >> mobility-related functions may be located in separate network nodes. >> DMM >> solutions should not distinguish between physical or virtualized >> networking functions. Whenever applicable, clarifications and additional >> features/capabilities for specific networking function deployment >> models, e.g. in virtualized environments, are in-scope and encouraged. >> Solutions may also specify the selection between the care-of addresses >> and home address(es)/prefix(es) for different application use cases. >> >> Work items related to distributed mobility management include: >> >> o Distributed mobility management deployment models and scenarios: >> describe the target high-level network architectures and >> deployment models where distributed mobility management >> protocol solutions could apply. >> > > > Can someone elaborate on what kind of information will go into such a document? See the reply to Brian: http://www.ietf.org/mail-archive/web/dmm/current/msg01406.html >> o Enhanced mobility anchoring: define protocol solutions for a >> gateway and mobility anchor assignment and mid-session mobility >> anchor switching that go beyond what has been specified, for >> example, in RFC 6097, 6463, and 5142. Traffic steering >> associated with the anchor switch is also in-scope if deemed >> appropriate. >> >> o Forwarding path and signaling management: the function >> that handles mobility management signaling interacts with the >> DMM network elements for managing the forwarding state >> associated with a mobile node's IP traffic. These two functions >> may or may not be collocated. Furthermore, the forwarding state >> may also be distributed into multiple network elements instead >> of a single network element (e.g., anchor). Protocol extensions >> or new protocols will be specified to allow the above mentioned >> forwarding path and signalling management. >> > > I cannot separate "mobility anchoring" from "fwding path and signaling management". > Wherever you want to set your anchor or move your anchor to, you'd need signaling > and setting up data path. The two are inseparable. > Having said that, I'm OK to keep the current work item descriptions and finalize > rechartering. Once we have detailed discussions about the breakdown of the work, we > can come back and refine the goals and milestones (as already stated below [*]). The enhanced mobility anchoring above is/was rather MIP type solutions influenced with "anchors" like we understand today, while the "forwarding path and signaling management" was meant for more future oriented solutions where the forwarding path does not necessarily have anything mobility specific etc. Any other opinions on collapsing these two? - Jouni >> o Exposing mobility state to mobile nodes and network nodes: >> define solutions that allow, for example, mobile nodes to select >> either a care-of address or a home address depending on an >> application' mobility needs. In order to enable this >> functionality, the network-side control functions and other >> networking nodes must also be able to exchange appropriate >> control information, as well as to the mobile nodes and their >> applications. >> >> The working group may decide to extend the current milestones based on >> the new information and knowledge gained during working on other >> documents listed in the initial milestones. [*] > > > Cheers, > > Alper > > > > >> Possible new documents and >> milestones must still fit into the overall DMM charter scope as outlined >> above. >> >> Goals and Milestones: >> >> Feb 2015 - Submit 'The deployment models and scenarios' as a working >> group document(s). To be Informational RFC. >> >> Feb 2015 - Submit 'Enhanced mobility anchoring' as a working group >> document. To be Proposed Standard. >> >> Feb 2015 - Submit 'Forwarding path and signaling management' as a >> working group document. To be Proposed Standard. >> >> May 2015 - Submit 'Exposing mobility state to mobile nodes and network >> nodes' as a working group document(s). To be Proposed >> Standard. >> >> >> May 2015 - Submit 'The deployment models and scenarios' submitted to >> the IESG. To be Informational RFC. >> >> Jun 2015 - Submit 'Enhanced mobility anchoring' submitted to the IESG. >> To be Proposed Standard. >> >> Jun 2015 - Submit 'Forwarding path and signaling management' submitted >> to the IESG. To be Proposed Standard. >> >> Oct 2015 - Submit 'Exposing mobility state to mobile nodes and network >> nodes' submitted to the IESG. To be Proposed Standard. >> >> >> >> 7/29/2014 4:22 PM, Jouni Korhonen kirjoitti: >>> The webex sessions have been cancelled in accordance of better IETF >>> process compliancy. New dates will be announced rougghly two weeks ahead >>> of tomorrow. >>> >>> You can (and should) still actively send edits to the list and I'll >>> update the text accordingly. Maybe we manage to get ready even without a >>> call! >>> >>> - Jouni & Dapeng >>> >>> 7/25/2014 12:49 AM, Jouni Korhonen kirjoitti: >>>> Folks, >>>> >>>> The latest charter draft can be found here: >>>> https://github.com/jounikor/dmm-re-charter/blob/master/recharter_draft.txt >>>> >>>> >>>> The deadline for the text chnges are 31st July. I'll setup a call for >>>> next week so that those who want to dial in and have verbal commenting >>>> can do that. In a meanwhile, email works as usual for updates and >>>> comments on the text. The actual milestone dates are to be done last but >>>> suggestions are more than welcome. >>>> >>>> - Jouni & Dapeng >> >> _______________________________________________ >> dmm mailing list >> dmm@ietf.org >> https://www.ietf.org/mailman/listinfo/dmm > From nobody Wed Aug 13 05:36:10 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0CC81A870D for ; Wed, 13 Aug 2014 05:36:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id iTIkgR0w9geg for ; Wed, 13 Aug 2014 05:36:04 -0700 (PDT) Received: from mout.perfora.net (mout.perfora.net [74.208.4.194]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54C821A8706 for ; Wed, 13 Aug 2014 05:36:04 -0700 (PDT) Received: from [192.168.1.4] (88.244.81.189.dynamic.ttnet.com.tr [88.244.81.189]) by mrelay.perfora.net (node=mreueus001) with ESMTP (Nemesis) id 0LmdF7-1WhefN0AYV-00aH5L; Wed, 13 Aug 2014 14:36:02 +0200 Mime-Version: 1.0 (Apple Message framework v1283) Content-Type: multipart/alternative; boundary="Apple-Mail=_383CDF49-3635-419C-8CC3-6CD858E5EE66" From: Alper Yegin In-Reply-To: <53EB4F10.1040502@gmail.com> Date: Wed, 13 Aug 2014 15:35:56 +0300 Message-Id: References: <53D17F75.3030207@gmail.com> <53D7A012.2050700@gmail.com> <53D8AAE0.4040301@gmail.com> <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> <53EB4F10.1040502@gmail.com> To: Jouni Korhonen X-Mailer: Apple Mail (2.1283) X-Provags-ID: V02:K0:KfVLZsHms5VbBE0Udwt/R96GmEy5gWJgR8qi9e3055Q IDzd14vdUqzxbuHaav2EWOGK3R8IHqdHEpC5CDZM4nHB/nrN20 yHWL3MjUxTAXfyKKRIBZbm0+n9jT14U/ER1A/RYy0D3neDx0Ii WpKqXI3ku6cNJqsxPszuubZexCynrqLgJqHeaDIFwSH+11q2uA XmMekBrzGsahfSGiYSgmmV7pg1dAZZ6/KwIaLjEOYaetCjyW7/ o2AT4X1aINzO1UvuiS5aET/7pRmNnKlNMDyH9xWPfCpHgACOCs +TFHM+MQX1fKK9W7JW26lHO0V7ogL2FdxQuTrzLFlciP2whqje HJXQ+8adPzWA+qpAPnA1YrjI1rpU49Tlb6pIPigk9QUZdop2Vu geUC9zOWcNDkA== X-UI-Out-Filterresults: notjunk:1; Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/3nNC8PSw4QJ-W2xlu6pXcYn6tnk Cc: "dmm@ietf.org" Subject: Re: [DMM] regarding the re-chartering.. X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 12:36:07 -0000 --Apple-Mail=_383CDF49-3635-419C-8CC3-6CD858E5EE66 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Hi Jouni, >>>=20 >>>=20 >>> o Distributed mobility management deployment models and = scenarios: >>> describe the target high-level network architectures and >>> deployment models where distributed mobility management >>> protocol solutions could apply. >>>=20 >>=20 >>=20 >> Can someone elaborate on what kind of information will go into such a = document? >=20 > See the reply to Brian: > http://www.ietf.org/mail-archive/web/dmm/current/msg01406.html >=20 Yes, I had read that. But even that does not really clarify it for me. = Brian had said and you had agreed that: I interpreted the the charter text as describing deployment models like: - Wi-Fi-based mobility management - Cellular (e.g., 3GPP) mobility management - Mixed technology mobility management But, what exactly would go into, say, 3GPP mobility management? Are we = going to describe how 3GPP system works?=20 Would that be simply documenting 3GPP mobility in an IETF draft? >>> o Enhanced mobility anchoring: define protocol solutions for a >>> gateway and mobility anchor assignment and mid-session = mobility >>> anchor switching that go beyond what has been specified, for >>> example, in RFC 6097, 6463, and 5142. Traffic steering >>> associated with the anchor switch is also in-scope if deemed >>> appropriate. >>>=20 >>> o Forwarding path and signaling management: the function >>> that handles mobility management signaling interacts with the >>> DMM network elements for managing the forwarding state >>> associated with a mobile node's IP traffic. These two = functions >>> may or may not be collocated. Furthermore, the forwarding = state >>> may also be distributed into multiple network elements = instead >>> of a single network element (e.g., anchor). Protocol = extensions >>> or new protocols will be specified to allow the above = mentioned >>> forwarding path and signalling management. >>>=20 >>=20 >> I cannot separate "mobility anchoring" from "fwding path and = signaling management". >> Wherever you want to set your anchor or move your anchor to, you'd = need signaling > > and setting up data path. The two are inseparable. >> Having said that, I'm OK to keep the current work item descriptions = and finalize > > rechartering. Once we have detailed discussions about the breakdown = of the work, we > > can come back and refine the goals and milestones (as already stated = below [*]). >=20 > The enhanced mobility anchoring above is/was rather MIP type solutions = influenced with "anchors" like we understand today, while the = "forwarding path and signaling management" was meant for more future = oriented solutions where the forwarding path does not necessarily have = anything mobility specific etc. >=20 (Just FYI: It's not possible to gather what you are saying from reading = the charter. Different people reading the charter may not have the same = understanding. But like I said, this is just FYI, I can live with this = text until we come back and refine it later). Thanks. Alper > Any other opinions on collapsing these two? >=20 > - Jouni >=20 >>> o Exposing mobility state to mobile nodes and network nodes: >>> define solutions that allow, for example, mobile nodes to = select >>> either a care-of address or a home address depending on an >>> application' mobility needs. In order to enable this >>> functionality, the network-side control functions and other >>> networking nodes must also be able to exchange appropriate >>> control information, as well as to the mobile nodes and their >>> applications. >>>=20 >>> The working group may decide to extend the current milestones based = on >>> the new information and knowledge gained during working on other >>> documents listed in the initial milestones. [*] >>=20 >>=20 >> Cheers, >>=20 >> Alper >>=20 >>=20 >>=20 >>=20 >>> Possible new documents and >>> milestones must still fit into the overall DMM charter scope as = outlined >>> above. >>>=20 >>> Goals and Milestones: >>>=20 >>> Feb 2015 - Submit 'The deployment models and scenarios' as a = working >>> group document(s). To be Informational RFC. >>>=20 >>> Feb 2015 - Submit 'Enhanced mobility anchoring' as a working group >>> document. To be Proposed Standard. >>>=20 >>> Feb 2015 - Submit 'Forwarding path and signaling management' as a >>> working group document. To be Proposed Standard. >>>=20 >>> May 2015 - Submit 'Exposing mobility state to mobile nodes and = network >>> nodes' as a working group document(s). To be Proposed >>> Standard. >>>=20 >>>=20 >>> May 2015 - Submit 'The deployment models and scenarios' submitted = to >>> the IESG. To be Informational RFC. >>>=20 >>> Jun 2015 - Submit 'Enhanced mobility anchoring' submitted to the = IESG. >>> To be Proposed Standard. >>>=20 >>> Jun 2015 - Submit 'Forwarding path and signaling management' = submitted >>> to the IESG. To be Proposed Standard. >>>=20 >>> Oct 2015 - Submit 'Exposing mobility state to mobile nodes and = network >>> nodes' submitted to the IESG. To be Proposed Standard. >>>=20 >>>=20 >>>=20 >>> 7/29/2014 4:22 PM, Jouni Korhonen kirjoitti: >>>> The webex sessions have been cancelled in accordance of better IETF >>>> process compliancy. New dates will be announced rougghly two weeks = ahead >>>> of tomorrow. >>>>=20 >>>> You can (and should) still actively send edits to the list and I'll >>>> update the text accordingly. Maybe we manage to get ready even = without a >>>> call! >>>>=20 >>>> - Jouni & Dapeng >>>>=20 >>>> 7/25/2014 12:49 AM, Jouni Korhonen kirjoitti: >>>>> Folks, >>>>>=20 >>>>> The latest charter draft can be found here: >>>>> = https://github.com/jounikor/dmm-re-charter/blob/master/recharter_draft.txt= >>>>>=20 >>>>>=20 >>>>> The deadline for the text chnges are 31st July. I'll setup a call = for >>>>> next week so that those who want to dial in and have verbal = commenting >>>>> can do that. In a meanwhile, email works as usual for updates and >>>>> comments on the text. The actual milestone dates are to be done = last but >>>>> suggestions are more than welcome. >>>>>=20 >>>>> - Jouni & Dapeng >>>=20 >>> _______________________________________________ >>> dmm mailing list >>> dmm@ietf.org >>> https://www.ietf.org/mailman/listinfo/dmm >>=20 --Apple-Mail=_383CDF49-3635-419C-8CC3-6CD858E5EE66 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Hi = Jouni,




     o = Distributed mobility management deployment models and = scenarios:
=        describe the target high-level = network architectures and
=        deployment models where = distributed mobility management
=        protocol solutions could = apply.



Can someone = elaborate on what kind of information will go into such a = document?

See the reply to Brian:
ht= tp://www.ietf.org/mail-archive/web/dmm/current/msg01406.html


Yes, I had read that. But even that = does not really clarify it for me. Brian had said and you had agreed = that:

I =
interpreted the the charter text as describing
deployment models like:

- Wi-Fi-based mobility management

- Cellular (e.g., 3GPP) mobility management

- Mixed technology mobility management
=




But= , what exactly would go into, say, 3GPP mobility management? Are we = going to describe how 3GPP system works? 
Would that be = simply documenting 3GPP mobility in an IETF = draft?




     o Enhanced mobility = anchoring: define protocol solutions for = a
       gateway and = mobility anchor assignment and mid-session = mobility
=        anchor switching that go = beyond what has been specified, = for
       example, in RFC = 6097, 6463, and 5142. Traffic = steering
=        associated with the anchor = switch is also in-scope if = deemed
=        appropriate.

     o = Forwarding path and signaling management: the = function
=        that handles mobility = management signaling interacts with = the
       DMM network = elements for managing the forwarding = state
       associated with = a mobile node's IP traffic. These two = functions
=        may or may not be collocated. = Furthermore, the forwarding = state
       may also be = distributed into multiple network elements = instead
       of a single = network element (e.g., anchor). Protocol = extensions
=        or new protocols will be = specified to allow the above = mentioned
=        forwarding path and signalling = management.


I cannot = separate "mobility anchoring" from "fwding path and signaling = management".
Wherever you want = to set your anchor or move your anchor to, you'd need = signaling
> and setting up data path. The two are = inseparable.
Having said that, I'm OK to = keep the current work item descriptions and = finalize
> rechartering. Once we have detailed = discussions about the breakdown of the work, we
> can come back = and refine the goals and milestones (as already stated below = [*]).

The enhanced mobility anchoring above is/was rather MIP = type solutions influenced with "anchors" like we understand today, while = the "forwarding path and signaling management" was meant for more future = oriented solutions where the forwarding path does not necessarily have = anything mobility specific = etc.


(Just FYI: It's not = possible to gather what you are saying from reading the charter. = Different people reading the charter may not have the same = understanding. But like I said, this is just FYI, I can live with this = text until we come back and refine it = later).

Thanks.

Alper




Any other opinions on collapsing these two?

- = Jouni

=      o Exposing mobility state to mobile nodes = and network nodes:
=        define solutions that allow, = for example, mobile nodes to = select
       either a = care-of address or a home address depending on = an
       application' = mobility needs. In order to enable = this
       functionality, = the network-side control functions and = other
       networking = nodes must also be able to exchange = appropriate
=        control information, as well = as to the mobile nodes and = their
=        applications.

The working group may decide to = extend the current milestones based = on
the new information and knowledge gained during working on = other
documents listed in the initial milestones. = [*]


Cheers,

Alper




Possible new documents = and
milestones must still fit into the overall DMM charter = scope as outlined
above.

Goals and = Milestones:

 Feb 2015 - Submit 'The = deployment models and scenarios' as a = working
=             gr= oup document(s). To be Informational = RFC.

 Feb 2015 - Submit = 'Enhanced mobility anchoring' as a working = group
=             do= cument. To be Proposed = Standard.

 Feb 2015 - Submit = 'Forwarding path and signaling management' as = a
=             wo= rking group document. To be Proposed = Standard.

 May 2015 - Submit = 'Exposing mobility state to mobile nodes and = network
=             no= des' as a working group document(s). To be = Proposed
=             St= andard.


 May 2015 - Submit 'The = deployment models and scenarios' submitted = to
=             th= e IESG. To be Informational = RFC.

 Jun 2015 - Submit = 'Enhanced mobility anchoring' submitted to the = IESG.
=             To= be Proposed Standard.

 Jun 2015 - Submit = 'Forwarding path and signaling management' = submitted
=             to= the IESG. To be Proposed = Standard.

 Oct 2015 - Submit = 'Exposing mobility state to mobile nodes and = network
=             no= des' submitted to the IESG. To be Proposed = Standard.



7/29/2014 4:22 PM, Jouni = Korhonen kirjoitti:
The = webex sessions have been cancelled in accordance of better = IETF
process = compliancy. New dates will be announced rougghly two weeks = ahead
of = tomorrow.

You = can (and should) still actively send edits to the list and = I'll
update = the text accordingly. Maybe we manage to get ready even without = a
call!

- = Jouni & Dapeng

7/25/2014 12:49 AM, Jouni Korhonen = kirjoitti:
Folks,

The latest charter draft can be = found = here:
https://github.com/jounikor/dmm-re-charter/blob/master/recharter= _draft.txt


The deadline for the text chnges = are 31st July. I'll setup a call = for
next week so that those who want = to dial in and have verbal = commenting
can do that. In a meanwhile, = email works as usual for updates = and
comments on the text. The actual = milestone dates are to be done last = but
suggestions are more than = welcome.

- Jouni & = Dapeng

_______________________________________________
dmm = mailing list
dmm@ietf.org
https://www.ietf.org/ma= ilman/listinfo/dmm


<= /html>= --Apple-Mail=_383CDF49-3635-419C-8CC3-6CD858E5EE66-- From nobody Wed Aug 13 10:10:58 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36BAF1A02A2; Wed, 13 Aug 2014 10:10:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.99 X-Spam-Level: X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HMNAnwMtX5A1; Wed, 13 Aug 2014 10:10:48 -0700 (PDT) Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7BA571A01E7; Wed, 13 Aug 2014 10:10:47 -0700 (PDT) Received: by mail-la0-f46.google.com with SMTP id b8so30268lan.33 for ; Wed, 13 Aug 2014 10:10:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; bh=i87uMKDWExs1vKhBHal4UpnzvJYU3mmfbuefbz1YMX8=; b=tMT0SE3mRms4LwJ6g8WuyI/daDEUMrpbya8PG9TDBwV6jFR5+JCm4oLNwC7xvNEd0q w155k1XsD8mgVFAwdS8h0/wTQ7Kx4iQRIY18GfrhDkeeuOSVqLnfpkbCnQwpTbOc6W8j e+kxhCVneb2MgDlCbqGBXIfx1Gk12qyX3TWVAULCUvdrD4DlZenpaZp85UilWy806Hrh ewi+y3i39Cz6If3zekTWTZ0Xt5TLSgLuxCR5HrvFMuwwQHwPoidpoTtiWbHNHXF76Qiw Oel2MkZbJWXV7J3FguWD0ZxppjzsecFP2szXYnpaq/obvT81MjGjVROuuCt3WqErrhtC KitQ== X-Received: by 10.112.166.2 with SMTP id zc2mr4291977lbb.98.1407949845787; Wed, 13 Aug 2014 10:10:45 -0700 (PDT) Received: from [188.117.15.109] ([188.117.15.109]) by mx.google.com with ESMTPSA id m1sm1527065laj.6.2014.08.13.10.10.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Aug 2014 10:10:45 -0700 (PDT) From: Jouni Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 13 Aug 2014 20:10:42 +0300 Message-Id: <5267E928-E431-4D90-9D23-F29250979C50@gmail.com> To: DraftTracker Mail System , dmm@ietf.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/2Jgm0L7_x2N96NcTPlWQh3psu_c Cc: dmm-chairs@tools.ietf.org Subject: [DMM] DMM interim conference call #1 X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 17:10:55 -0000 The DMM WG will hold two interim conference calls during September: The first one is scheduled 2nd September, 5PM (Helsinki time, EEST) The conference call lasts max 2 hours. The detailed agenda will be available later but it is around progressing the new work we are pursuing. -------------------------------------------------------=20 WebEx details: ------------------------------------------------------- Topic: DMM Interim=20 Date: Tuesday 2 September 2014=20 Time: 17:00, Northern Europe Summer Time (Helsinki, GMT+03:00)=20 Meeting Number: 649 544 518=20 Meeting Password: dmm1911=20 -------------------------------------------------------=20 To join the online meeting (Now from mobile devices!)=20 -------------------------------------------------------=20 1. Go to = https://ietf.webex.com/ietf/j.php?MTID=3Dmca9a04110816785817b6761d7c8a819d= =20 2. If requested, enter your name and email address.=20 3. If a password is required, enter the meeting password: dmm1911=20 4. Click "Join".=20 To view in other time zones or languages, please click the link:=20 https://ietf.webex.com/ietf/j.php?MTID=3Dm7268c494bff4d3b707b957004edf094b= =20 -------------------------------------------------------=20 To join the audio conference only=20 -------------------------------------------------------=20 Call-in toll number (US/Canada): 1-650-479-3208=20 Access code:649 544 518=20 -------------------------------------------------------=20 For assistance=20 -------------------------------------------------------=20 1. Go to https://ietf.webex.com/ietf/mc=20 2. On the left navigation bar, click "Support".=20 You can contact me at:=20 dmm-chairs@tools.ietf.org=20 To add this meeting to your calendar program (for example Microsoft = Outlook), click this link:=20 https://ietf.webex.com/ietf/j.php?MTID=3Dm107845f7d771bffa2fe00c733181615d= =20 The playback of UCF (Universal Communications Format) rich media files = requires appropriate players. To view this type of rich media files in = the meeting, please check whether you have the players installed on your = computer by going to https://ietf.webex.com/ietf/systemdiagnosis.php.=20 Sign up for a free trial of WebEx=20 http://www.webex.com/go/mcemfreetrial=20 http://www.webex.com=20 CCP:+16504793208x649544518#=20 IMPORTANT NOTICE: This WebEx service includes a feature that allows = audio and any documents and other materials exchanged or viewed during = the session to be recorded. By joining this session, you automatically = consent to such recordings. If you do not consent to the recording, = discuss your concerns with the meeting host prior to the start of the = recording or do not join the session. Please note that any such = recordings may be subject to discovery in the event of litigation.=20 From nobody Wed Aug 13 10:11:02 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E020C1A00CD; Wed, 13 Aug 2014 10:10:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.99 X-Spam-Level: X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vx_DvkPSGOCX; Wed, 13 Aug 2014 10:10:51 -0700 (PDT) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54F1B1A0243; Wed, 13 Aug 2014 10:10:51 -0700 (PDT) Received: by mail-la0-f41.google.com with SMTP id s18so34425lam.14 for ; Wed, 13 Aug 2014 10:10:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:date:message-id :cc:to:mime-version; bh=24hx8vgfpP3pEnH4/BSPuZ/J2QLV9o0SCC73uJxhZEQ=; b=yuUrvfpEcV0iwD6zCTNYxMz0QUiIdNG68hvBfNHTDTskXy2IEHGkBnELX/gKxFwqsj qNnmXQlDnCF4JI44ciLUA5olTAMlhEMKhKKxaIDmSvZkFkcVe8jE7Yq1vl2t7L1k4x7r JhEV4BevgXJhJivAFkM+PQDV9TMkowanQ9HjbGUrVA99S9OC8bqcpPmEXcmZ86n5T7cp l/IF+fenoLYJ7CogRS0eMXAd+CS8CI8zFe8tAzANEvKZvImdX4UQXAmlFvL+S4y/zFbs IswNnadDHtZUsAYosdhTnTWn13wGTJWAv054usbL+HMc1mj0sAFvT26xkoDwTGlOSPbT 3H/w== X-Received: by 10.112.225.7 with SMTP id rg7mr5526165lbc.52.1407949849644; Wed, 13 Aug 2014 10:10:49 -0700 (PDT) Received: from [188.117.15.109] ([188.117.15.109]) by mx.google.com with ESMTPSA id m1sm1527065laj.6.2014.08.13.10.10.48 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Aug 2014 10:10:48 -0700 (PDT) From: Jouni Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 13 Aug 2014 20:10:44 +0300 Message-Id: To: DraftTracker Mail System , dmm@ietf.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/aRcQVwXwLQ6aJZxSenGJW_UwmW4 Cc: dmm-chairs@tools.ietf.org Subject: [DMM] DMM interim conference call #2 X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 17:10:56 -0000 The DMM WG will hold two interim conference calls during September: The second one is scheduled 16th September, 8AM (Helsinki time, EEST) The conference call lasts max 2 hours. The detailed agenda will be available later but it is around progressing the new work we are pursuing. -------------------------------------------------------=20 WebEx details: ------------------------------------------------------- Topic: DMM Interim=20 Date: Tuesday 16 September 2014=20 Time: 8:00, Northern Europe Summer Time (Helsinki, GMT+03:00)=20 Meeting Number: 646 119 560=20 Meeting Password: dmm1911=20 -------------------------------------------------------=20 To join the online meeting (Now from mobile devices!)=20 -------------------------------------------------------=20 1. Go to = https://ietf.webex.com/ietf/j.php?MTID=3Dm00fbce3768311acb9c2071e291254755= =20 2. If requested, enter your name and email address.=20 3. If a password is required, enter the meeting password: dmm1911=20 4. Click "Join".=20 To view in other time zones or languages, please click the link:=20 https://ietf.webex.com/ietf/j.php?MTID=3Dmb1760d3b557aea6ae1761ea3feea10c0= =20 -------------------------------------------------------=20 To join the audio conference only=20 -------------------------------------------------------=20 Call-in toll number (US/Canada): 1-650-479-3208=20 Access code:646 119 560=20 -------------------------------------------------------=20 For assistance=20 -------------------------------------------------------=20 1. Go to https://ietf.webex.com/ietf/mc=20 2. On the left navigation bar, click "Support".=20 You can contact me at:=20 dmm-chairs@tools.ietf.org=20 To add this meeting to your calendar program (for example Microsoft = Outlook), click this link:=20 https://ietf.webex.com/ietf/j.php?MTID=3Dm556846cd8ca9b22f82b4e6ccf9bc2612= =20 The playback of UCF (Universal Communications Format) rich media files = requires appropriate players. To view this type of rich media files in = the meeting, please check whether you have the players installed on your = computer by going to https://ietf.webex.com/ietf/systemdiagnosis.php.=20 Sign up for a free trial of WebEx=20 http://www.webex.com/go/mcemfreetrial=20 http://www.webex.com=20 CCP:+16504793208x646119560#=20 IMPORTANT NOTICE: This WebEx service includes a feature that allows = audio and any documents and other materials exchanged or viewed during = the session to be recorded. By joining this session, you automatically = consent to such recordings. If you do not consent to the recording, = discuss your concerns with the meeting host prior to the start of the = recording or do not join the session. Please note that any such = recordings may be subject to discovery in the event of litigation.=20= From nobody Wed Aug 13 14:06:01 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6CC0C1A06D2; Wed, 13 Aug 2014 14:05:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RsmqclEK6t9p; Wed, 13 Aug 2014 14:05:54 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3409C1A06B2; Wed, 13 Aug 2014 14:05:54 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IESG Secretary To: IETF Announcement List X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p5 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140813210554.5396.18876.idtracker@ietfa.amsl.com> Date: Wed, 13 Aug 2014 14:05:54 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/711DZGUxOFNcd0OdutOw49-4NkE Cc: dmm@ietf.org Subject: [DMM] DMM WG Virtual Interim Meeting, September 2, 2014 X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Reply-To: dmm@ietf.org List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 21:05:59 -0000 The DMM WG will hold two interim conference calls during September: The first one is scheduled 2nd September, 5PM (Helsinki time, EEST) The conference call lasts max 2 hours. The detailed agenda will be available later but it is around progressing the new work we are pursuing. ------------------------------------------------------- WebEx details: ------------------------------------------------------- Topic: DMM Interim Date: Tuesday 2 September 2014 Time: 17:00, Northern Europe Summer Time (Helsinki, GMT+03:00) Meeting Number: 649 544 518 Meeting Password: dmm1911 ------------------------------------------------------- To join the online meeting (Now from mobile devices!) ------------------------------------------------------- 1. Go to https://ietf.webex.com/ietf/j.php?MTID=mca9a04110816785817b6761d7c8a819d 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: dmm1911 4. Click "Join". To view in other time zones or languages, please click the link: https://ietf.webex.com/ietf/j.php?MTID=m7268c494bff4d3b707b957004edf094b ------------------------------------------------------- To join the audio conference only ------------------------------------------------------- Call-in toll number (US/Canada): 1-650-479-3208 Access code:649 544 518 ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://ietf.webex.com/ietf/mc 2. On the left navigation bar, click "Support". You can contact me at: dmm-chairs@tools.ietf.org To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://ietf.webex.com/ietf/j.php?MTID=m107845f7d771bffa2fe00c733181615d The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://ietf.webex.com/ietf/systemdiagnosis.php. Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com CCP:+16504793208x649544518# IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. From nobody Wed Aug 13 14:09:08 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12AB41A06B2; Wed, 13 Aug 2014 14:09:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TYTO5m1Rb-Qf; Wed, 13 Aug 2014 14:09:00 -0700 (PDT) Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B0411A024C; Wed, 13 Aug 2014 14:09:00 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IESG Secretary To: IETF Announcement List X-Test-IDTracker: no X-IETF-IDTracker: 5.6.2.p5 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <20140813210900.6850.51621.idtracker@ietfa.amsl.com> Date: Wed, 13 Aug 2014 14:09:00 -0700 Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/bbzELPPBVcDe6LDdcCEAx1Ipr2I Cc: dmm@ietf.org Subject: [DMM] DMM WG Virtual Interim Meeting, September 16, 2014 X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Reply-To: dmm@ietf.org List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 21:09:02 -0000 The DMM WG will hold two interim conference calls during September: The second one is scheduled 16th September, 8AM (Helsinki time, EEST) The conference call lasts max 2 hours. The detailed agenda will be available later but it is around progressing the new work we are pursuing. ------------------------------------------------------- WebEx details: ------------------------------------------------------- Topic: DMM Interim Date: Tuesday 16 September 2014 Time: 8:00, Northern Europe Summer Time (Helsinki, GMT+03:00) Meeting Number: 646 119 560 Meeting Password: dmm1911 ------------------------------------------------------- To join the online meeting (Now from mobile devices!) ------------------------------------------------------- 1. Go to https://ietf.webex.com/ietf/j.php?MTID=m00fbce3768311acb9c2071e291254755 2. If requested, enter your name and email address. 3. If a password is required, enter the meeting password: dmm1911 4. Click "Join". To view in other time zones or languages, please click the link: https://ietf.webex.com/ietf/j.php?MTID=mb1760d3b557aea6ae1761ea3feea10c0 ------------------------------------------------------- To join the audio conference only ------------------------------------------------------- Call-in toll number (US/Canada): 1-650-479-3208 Access code:646 119 560 ------------------------------------------------------- For assistance ------------------------------------------------------- 1. Go to https://ietf.webex.com/ietf/mc 2. On the left navigation bar, click "Support". You can contact me at: dmm-chairs@tools.ietf.org To add this meeting to your calendar program (for example Microsoft Outlook), click this link: https://ietf.webex.com/ietf/j.php?MTID=m556846cd8ca9b22f82b4e6ccf9bc2612 The playback of UCF (Universal Communications Format) rich media files requires appropriate players. To view this type of rich media files in the meeting, please check whether you have the players installed on your computer by going to https://ietf.webex.com/ietf/systemdiagnosis.php. Sign up for a free trial of WebEx http://www.webex.com/go/mcemfreetrial http://www.webex.com CCP:+16504793208x646119560# IMPORTANT NOTICE: This WebEx service includes a feature that allows audio and any documents and other materials exchanged or viewed during the session to be recorded. By joining this session, you automatically consent to such recordings. If you do not consent to the recording, discuss your concerns with the meeting host prior to the start of the recording or do not join the session. Please note that any such recordings may be subject to discovery in the event of litigation. From nobody Wed Aug 13 15:44:27 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB5BC1A0107 for ; Wed, 13 Aug 2014 15:44:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.869 X-Spam-Level: X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u5VrtiSbuGa3 for ; Wed, 13 Aug 2014 15:44:23 -0700 (PDT) Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 867BC1A0197 for ; Wed, 13 Aug 2014 15:44:23 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s7DMiMw2021159; Wed, 13 Aug 2014 17:44:22 -0500 Received: from XCH-PHX-312.sw.nos.boeing.com (xch-phx-312.sw.nos.boeing.com [130.247.25.173]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s7DMiFKa020669 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 13 Aug 2014 17:44:16 -0500 Received: from XCH-BLV-207.nw.nos.boeing.com (10.57.37.63) by XCH-PHX-312.sw.nos.boeing.com (130.247.25.173) with Microsoft SMTP Server (TLS) id 14.3.181.6; Wed, 13 Aug 2014 15:44:15 -0700 Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.6]) by XCH-BLV-207.nw.nos.boeing.com ([169.254.7.29]) with mapi id 14.03.0181.006; Wed, 13 Aug 2014 15:44:14 -0700 From: "Templin, Fred L" To: Jouni Korhonen Thread-Topic: [DMM] regarding the re-chartering.. Thread-Index: AQHPtuunsgqLUKZ3D0eUvh98F1yPB5vPIgHw Date: Wed, 13 Aug 2014 22:44:14 +0000 Message-ID: <2134F8430051B64F815C691A62D9831832CF0CC0@XCH-BLV-504.nw.nos.boeing.com> References: <53D17F75.3030207@gmail.com> <53D7A012.2050700@gmail.com> <53D8AAE0.4040301@gmail.com> <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> <53EB4F10.1040502@gmail.com> In-Reply-To: <53EB4F10.1040502@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [130.247.104.6] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-MML: disable Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/u7z9OP6QwT--Vh1Ri2tOSByTOOo Cc: "dmm@ietf.org" Subject: Re: [DMM] regarding the re-chartering.. X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Aug 2014 22:44:25 -0000 Hi Jouni, Is the draft charter under some sort of version control, or are the previous versions gone for good? Thanks - Fred fred.l.templin@boeing.com From nobody Wed Aug 13 22:38:37 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CAB71A0776 for ; Wed, 13 Aug 2014 22:38:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CopTzjx3RUK0 for ; Wed, 13 Aug 2014 22:38:28 -0700 (PDT) Received: from mail-la0-x229.google.com (mail-la0-x229.google.com [IPv6:2a00:1450:4010:c03::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 30AB31A0774 for ; Wed, 13 Aug 2014 22:38:28 -0700 (PDT) Received: by mail-la0-f41.google.com with SMTP id s18so583472lam.14 for ; Wed, 13 Aug 2014 22:38:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=BDuAH1LGOiRDXtkZZXgXwr+0a8oElJtTdJ5tTjwjwAo=; b=Qhmf/nhlJ4iK37gtOWzmt7ObUyn6geAUEQHiBTnCKYijRogNTTTsuo9/N0FvjzUKrI GvCl9uSFBepJCbVHSWNhNYGnlOfwtTRAFcBIfh0DfERxW3NXahXpOQRJAukwORRFXnK0 SPIG9ANpujSHTy5olwBTfI1dEmuY8fILz+soaft1unBdUQjMuV7XJ+SsN8Jon1M3w6yF G1ziLtfJ+amum2G6OoX6xRWosMJt2obDNmcTc9GTELjJ/HWFG2z5rkhtayw1TLnoH6Zu Ijwjdc+o5nnmaaX5qthxnJGz8WYsmHVmdOwXsjC3PxVoUcQEq2yG8ah+5V3Q+J7cD8zm lP9A== X-Received: by 10.152.30.100 with SMTP id r4mr766187lah.87.1407994706372; Wed, 13 Aug 2014 22:38:26 -0700 (PDT) Received: from [192.168.250.201] ([194.100.71.98]) by mx.google.com with ESMTPSA id mi10sm6320658lbc.19.2014.08.13.22.38.24 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 13 Aug 2014 22:38:25 -0700 (PDT) Message-ID: <53EC4B4F.9070006@gmail.com> Date: Thu, 14 Aug 2014 08:38:23 +0300 From: Jouni Korhonen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "Templin, Fred L" References: <53D17F75.3030207@gmail.com> <53D7A012.2050700@gmail.com> <53D8AAE0.4040301@gmail.com> <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> <53EB4F10.1040502@gmail.com> <2134F8430051B64F815C691A62D9831832CF0CC0@XCH-BLV-504.nw.nos.boeing.com> In-Reply-To: <2134F8430051B64F815C691A62D9831832CF0CC0@XCH-BLV-504.nw.nos.boeing.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/75-GyvAo1N2IGAT-HNWN3DqOy0A Cc: "dmm@ietf.org" Subject: Re: [DMM] regarding the re-chartering.. X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2014 05:38:33 -0000 https://github.com/jounikor/dmm-re-charter 8/14/2014 1:44 AM, Templin, Fred L kirjoitti: > Hi Jouni, > > Is the draft charter under some sort of version control, or are > the previous versions gone for good? > > Thanks - Fred > fred.l.templin@boeing.com > > From nobody Thu Aug 14 07:37:48 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD1AC1A024E for ; Thu, 14 Aug 2014 07:37:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.869 X-Spam-Level: X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ck-jheihpvNo for ; Thu, 14 Aug 2014 07:37:45 -0700 (PDT) Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D1A51A019C for ; Thu, 14 Aug 2014 07:37:45 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s7EEbioW013723; Thu, 14 Aug 2014 09:37:44 -0500 Received: from XCH-PHX-313.sw.nos.boeing.com (xch-phx-313.sw.nos.boeing.com [130.247.25.175]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s7EEbg64013709 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 14 Aug 2014 09:37:43 -0500 Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.6]) by XCH-PHX-313.sw.nos.boeing.com ([169.254.13.70]) with mapi id 14.03.0181.006; Thu, 14 Aug 2014 07:37:42 -0700 From: "Templin, Fred L" To: Jouni Korhonen Thread-Topic: [DMM] regarding the re-chartering.. Thread-Index: AQHPtuunsgqLUKZ3D0eUvh98F1yPB5vPIgHwgADpbYCAACFJcA== Date: Thu, 14 Aug 2014 14:37:41 +0000 Message-ID: <2134F8430051B64F815C691A62D9831832CF1236@XCH-BLV-504.nw.nos.boeing.com> References: <53D17F75.3030207@gmail.com> <53D7A012.2050700@gmail.com> <53D8AAE0.4040301@gmail.com> <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> <53EB4F10.1040502@gmail.com> <2134F8430051B64F815C691A62D9831832CF0CC0@XCH-BLV-504.nw.nos.boeing.com> <53EC4B4F.9070006@gmail.com> In-Reply-To: <53EC4B4F.9070006@gmail.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [130.247.104.6] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-MML: disable Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/DViZKpZHHgr_hgJN0GubFisiYgI Cc: "dmm@ietf.org" Subject: Re: [DMM] regarding the re-chartering.. X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2014 14:37:46 -0000 OK, I see it now. thanks. Fred > -----Original Message----- > From: Jouni Korhonen [mailto:jouni.nospam@gmail.com] > Sent: Wednesday, August 13, 2014 10:38 PM > To: Templin, Fred L > Cc: dmm@ietf.org > Subject: Re: [DMM] regarding the re-chartering.. >=20 > https://github.com/jounikor/dmm-re-charter >=20 > 8/14/2014 1:44 AM, Templin, Fred L kirjoitti: > > Hi Jouni, > > > > Is the draft charter under some sort of version control, or are > > the previous versions gone for good? > > > > Thanks - Fred > > fred.l.templin@boeing.com > > > > From nobody Thu Aug 14 08:39:32 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B965E1A6F3C for ; Thu, 14 Aug 2014 08:39:31 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.869 X-Spam-Level: X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jZyk5QnfqZVC for ; Thu, 14 Aug 2014 08:39:25 -0700 (PDT) Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E06BA1A6F3A for ; Thu, 14 Aug 2014 08:39:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s7EFdIFv015420; Thu, 14 Aug 2014 08:39:18 -0700 Received: from XCH-BLV-503.nw.nos.boeing.com (xch-blv-503.nw.nos.boeing.com [130.247.25.192]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s7EFdDow015389 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Thu, 14 Aug 2014 08:39:14 -0700 Received: from XCH-BLV-305.nw.nos.boeing.com (2002:82f7:19d9::82f7:19d9) by XCH-BLV-503.nw.nos.boeing.com (2002:82f7:19c0::82f7:19c0) with Microsoft SMTP Server (TLS) id 14.3.181.6; Thu, 14 Aug 2014 08:39:13 -0700 Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.6]) by XCH-BLV-305.nw.nos.boeing.com ([169.254.5.203]) with mapi id 14.03.0181.006; Thu, 14 Aug 2014 08:39:13 -0700 From: "Templin, Fred L" To: Jouni Korhonen Thread-Topic: [DMM] regarding the re-chartering.. Thread-Index: AQHPtuunsgqLUKZ3D0eUvh98F1yPB5vPIgHwgADpbYCAACFJcIAAD2/Q Date: Thu, 14 Aug 2014 15:39:12 +0000 Message-ID: <2134F8430051B64F815C691A62D9831832CF130C@XCH-BLV-504.nw.nos.boeing.com> References: <53D17F75.3030207@gmail.com> <53D7A012.2050700@gmail.com> <53D8AAE0.4040301@gmail.com> <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> <53EB4F10.1040502@gmail.com> <2134F8430051B64F815C691A62D9831832CF0CC0@XCH-BLV-504.nw.nos.boeing.com> <53EC4B4F.9070006@gmail.com> <2134F8430051B64F815C691A62D9831832CF1236@XCH-BLV-504.nw.nos.boeing.com> In-Reply-To: <2134F8430051B64F815C691A62D9831832CF1236@XCH-BLV-504.nw.nos.boeing.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [130.247.104.6] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-MML: disable Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/iNL4D7NW8bvZn-9WoVzoLos35yw Cc: "dmm@ietf.org" Subject: Re: [DMM] regarding the re-chartering.. X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Aug 2014 15:39:31 -0000 So, in lines 27-30 of the current draft charter, it says:=20 > 5213, RFC 5844, RFC 5555, RFC 5568, and RFC 6275) as well as new=20 > approaches which capitalize on other protocols specified by the IETF. > When extending protocols that are not based on Mobile IP, DMM solutions=20 > will be have to be reviewed by the corresponding WGs. That text has changed considerably from earlier versions but I am still thinking that AERO can be considered a "new approach which capitalizes on other protocols specified by the IETF". Am I right that AERO could be a candidate for such a "new approach"? If so, then my only concern is that AERO doesn't currently have a working group home, and I was sort of thinking dmm could become the home working group. Is that wishful thinking? Thanks - Fred fred.l.templin@boeing.com From nobody Tue Aug 19 07:12:29 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38EB91A8906 for ; Tue, 19 Aug 2014 07:12:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WI7kKIrDqByz for ; Tue, 19 Aug 2014 07:12:26 -0700 (PDT) Received: from mail-lb0-x232.google.com (mail-lb0-x232.google.com [IPv6:2a00:1450:4010:c04::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6DD51A0382 for ; Tue, 19 Aug 2014 07:12:25 -0700 (PDT) Received: by mail-lb0-f178.google.com with SMTP id c11so5486037lbj.23 for ; Tue, 19 Aug 2014 07:12:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=kngizVkiPx1IsxQdSYOFD3J7JdjZSD+pvPj3VYrnhVs=; b=Btkg/Il1zKOAyT29WOiqeniOxoe3FuldsX8RI+bGCN25YRT96/qRpgDu0XEqGc5zmO pvs25cA3RWLqnZv5ohuAGJVlUdzH5BhFBTjtEsOtW/jFqKukVjTiQrtAYx4ganBu9VS6 87jzyMFTEDZgIrb48lHne1VabGGUmR5vbMF1QHExM+8eXpl/QY6G2kCmA9s8fft6lj0M M7l+t6Ns6eUY9Uz6rRfdwdV0KNllWaAjXPUKN5VOxRzadZcIW4v4oGesJ62yEXiIPZpQ c4e+6Si9TPf0nffEjK+Pb+fq0d6o7eb7aBl+uHrxMaSB670lafeZVlaq88HmY3Z3y88m hiXQ== X-Received: by 10.152.19.167 with SMTP id g7mr4568611lae.46.1408457543744; Tue, 19 Aug 2014 07:12:23 -0700 (PDT) Received: from [10.17.0.23] ([83.150.126.201]) by mx.google.com with ESMTPSA id c3sm5460272lab.15.2014.08.19.07.12.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 19 Aug 2014 07:12:21 -0700 (PDT) Message-ID: <53F35B44.1090808@gmail.com> Date: Tue, 19 Aug 2014 17:12:20 +0300 From: Jouni Korhonen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: Alper Yegin References: <53D17F75.3030207@gmail.com> <53D7A012.2050700@gmail.com> <53D8AAE0.4040301@gmail.com> <2E9AF0DF-8B1A-475B-B5FB-ED5E419F0085@yegin.org> <53EB4F10.1040502@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/FhqejI_fvgbY783ys2kKA8nV-l8 Cc: "dmm@ietf.org" Subject: Re: [DMM] regarding the re-chartering.. X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Aug 2014 14:12:28 -0000 Alper, 8/13/2014 3:35 PM, Alper Yegin kirjoitti: > Hi Jouni, > > >>>> >>>> >>>> o Distributed mobility management deployment models and scenarios: >>>> describe the target high-level network architectures and >>>> deployment models where distributed mobility management >>>> protocol solutions could apply. >>>> >>> >>> >>> Can someone elaborate on what kind of information will go into such a >>> document? >> >> See the reply to Brian: >> http://www.ietf.org/mail-archive/web/dmm/current/msg01406.html >> > > Yes, I had read that. But even that does not really clarify it for me. > Brian had said and you had agreed that: > > I interpreted the the charter text as describing > deployment models like: > > - Wi-Fi-based mobility management > - Cellular (e.g., 3GPP) mobility management > - Mixed technology mobility management > > > But, what exactly would go into, say, 3GPP mobility management? Are we > going to describe how 3GPP system works? > Would that be simply documenting 3GPP mobility in an IETF draft? Okay, we are not going to define how the existing 3FPP system works - that knowledge is assumed. What I thought goes into the document, for example, in the case of 3GPP system would be identifying the architecture changes or modifications needed. If the deployment model assumes all network functions are virtualized, the document states that and lays out the architecture based on that. Satoru's & Ryuji's vEPC deployment model (based on their solution) is IMHO a good example of what could be documented. The similar applies for other system architectures such as SP Wi-Fi etc. >>>> o Enhanced mobility anchoring: define protocol solutions for a >>>> gateway and mobility anchor assignment and mid-session mobility >>>> anchor switching that go beyond what has been specified, for >>>> example, in RFC 6097, 6463, and 5142. Traffic steering >>>> associated with the anchor switch is also in-scope if deemed >>>> appropriate. >>>> >>>> o Forwarding path and signaling management: the function >>>> that handles mobility management signaling interacts with the >>>> DMM network elements for managing the forwarding state >>>> associated with a mobile node's IP traffic. These two functions >>>> may or may not be collocated. Furthermore, the forwarding state >>>> may also be distributed into multiple network elements instead >>>> of a single network element (e.g., anchor). Protocol extensions >>>> or new protocols will be specified to allow the above mentioned >>>> forwarding path and signalling management. >>>> >>> >>> I cannot separate "mobility anchoring" from "fwding path and >>> signaling management". >>> Wherever you want to set your anchor or move your anchor to, you'd >>> need signaling >> > and setting up data path. The two are inseparable. >>> Having said that, I'm OK to keep the current work item descriptions >>> and finalize >> > rechartering. Once we have detailed discussions about the breakdown >> of the work, we >> > can come back and refine the goals and milestones (as already stated >> below [*]). >> >> The enhanced mobility anchoring above is/was rather MIP type solutions >> influenced with "anchors" like we understand today, while the >> "forwarding path and signaling management" was meant for more future >> oriented solutions where the forwarding path does not necessarily have >> anything mobility specific etc. >> > > (Just FYI: It's not possible to gather what you are saying from reading > the charter. Different people reading the charter may not have the same > understanding. But like I said, this is just FYI, I can live with this > text until we come back and refine it later). Ok. I'll try to clarify the point the text tries to make. - Jouni > > Thanks. > > Alper > > > > >> Any other opinions on collapsing these two? >> >> - Jouni >> >>>> o Exposing mobility state to mobile nodes and network nodes: >>>> define solutions that allow, for example, mobile nodes to select >>>> either a care-of address or a home address depending on an >>>> application' mobility needs. In order to enable this >>>> functionality, the network-side control functions and other >>>> networking nodes must also be able to exchange appropriate >>>> control information, as well as to the mobile nodes and their >>>> applications. >>>> >>>> The working group may decide to extend the current milestones based on >>>> the new information and knowledge gained during working on other >>>> documents listed in the initial milestones. [*] >>> >>> >>> Cheers, >>> >>> Alper >>> >>> >>> >>> >>>> Possible new documents and >>>> milestones must still fit into the overall DMM charter scope as outlined >>>> above. >>>> >>>> Goals and Milestones: >>>> >>>> Feb 2015 - Submit 'The deployment models and scenarios' as a working >>>> group document(s). To be Informational RFC. >>>> >>>> Feb 2015 - Submit 'Enhanced mobility anchoring' as a working group >>>> document. To be Proposed Standard. >>>> >>>> Feb 2015 - Submit 'Forwarding path and signaling management' as a >>>> working group document. To be Proposed Standard. >>>> >>>> May 2015 - Submit 'Exposing mobility state to mobile nodes and network >>>> nodes' as a working group document(s). To be Proposed >>>> Standard. >>>> >>>> >>>> May 2015 - Submit 'The deployment models and scenarios' submitted to >>>> the IESG. To be Informational RFC. >>>> >>>> Jun 2015 - Submit 'Enhanced mobility anchoring' submitted to the IESG. >>>> To be Proposed Standard. >>>> >>>> Jun 2015 - Submit 'Forwarding path and signaling management' submitted >>>> to the IESG. To be Proposed Standard. >>>> >>>> Oct 2015 - Submit 'Exposing mobility state to mobile nodes and network >>>> nodes' submitted to the IESG. To be Proposed Standard. >>>> >>>> >>>> >>>> 7/29/2014 4:22 PM, Jouni Korhonen kirjoitti: >>>>> The webex sessions have been cancelled in accordance of better IETF >>>>> process compliancy. New dates will be announced rougghly two weeks >>>>> ahead >>>>> of tomorrow. >>>>> >>>>> You can (and should) still actively send edits to the list and I'll >>>>> update the text accordingly. Maybe we manage to get ready even >>>>> without a >>>>> call! >>>>> >>>>> - Jouni & Dapeng >>>>> >>>>> 7/25/2014 12:49 AM, Jouni Korhonen kirjoitti: >>>>>> Folks, >>>>>> >>>>>> The latest charter draft can be found here: >>>>>> https://github.com/jounikor/dmm-re-charter/blob/master/recharter_draft.txt >>>>>> >>>>>> >>>>>> The deadline for the text chnges are 31st July. I'll setup a call for >>>>>> next week so that those who want to dial in and have verbal commenting >>>>>> can do that. In a meanwhile, email works as usual for updates and >>>>>> comments on the text. The actual milestone dates are to be done >>>>>> last but >>>>>> suggestions are more than welcome. >>>>>> >>>>>> - Jouni & Dapeng >>>> >>>> _______________________________________________ >>>> dmm mailing list >>>> dmm@ietf.org >>>> https://www.ietf.org/mailman/listinfo/dmm >>> > From nobody Thu Aug 21 00:21:44 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 948201A0476 for ; Thu, 21 Aug 2014 00:21:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OXhZM5_S_O_7 for ; Thu, 21 Aug 2014 00:21:39 -0700 (PDT) Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D93F1A03A4 for ; Thu, 21 Aug 2014 00:21:39 -0700 (PDT) Received: by mail-la0-f53.google.com with SMTP id gl10so8331485lab.12 for ; Thu, 21 Aug 2014 00:21:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=5JJAHFI9XmTOaIbiMJqHLBL0dqdxYjrTFR2FqcfA9qM=; b=czaLmyjKEtF0ZHWFp7jU1xSTk9u3btG1h+HaOhs7ntx+pdiYveB2i9K6PmbfIQPuo/ YvjkkRvZ8TWDgW5X4XQXUPY9Sq1aiSTMrjXiAH17h2vZVDnPW/BVY7a+EjE6LKJvkUT0 CCHK8TnJ5r/7AW2xjSqqhClTnJekoMnJtqOYS6AEenYZK9awsmCdpwOMZt7LBzUi375O Ew+pyk0fdKxSp7rbB8ERHFOWKRTWN9GHSJYAUE7ofVaRS/eukzWWdHGFNoCkkqJLjlEM EpRLlB6DMKY6gGm1LQns3mAo+3/kNPhzGKNv4trq5eTkde2Zv43Y23mrKibjhTlJYmGE 7O/w== X-Received: by 10.112.52.225 with SMTP id w1mr45450149lbo.44.1408605697468; Thu, 21 Aug 2014 00:21:37 -0700 (PDT) Received: from [10.17.0.23] ([83.150.126.201]) by mx.google.com with ESMTPSA id du2sm5044846lac.25.2014.08.21.00.21.35 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 21 Aug 2014 00:21:35 -0700 (PDT) Message-ID: <53F59DFD.9000006@gmail.com> Date: Thu, 21 Aug 2014 10:21:33 +0300 From: Jouni Korhonen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "dmm@ietf.org" References: <20140821014017.97252180090@rfc-editor.org> In-Reply-To: <20140821014017.97252180090@rfc-editor.org> X-Forwarded-Message-Id: <20140821014017.97252180090@rfc-editor.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/1-kJeCTTiPpSBa3AzovK2w76jMU Subject: [DMM] Fwd: RFC 7333 on Requirements for Distributed Mobility Management X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2014 07:21:41 -0000 Congrats to the authors and to the WG. We have our first RFC published ! -------- Alkuperäinen viesti / Orig.Msg. -------- Aihe: RFC 7333 on Requirements for Distributed Mobility Management Päiväys: Wed, 20 Aug 2014 18:40:17 -0700 (PDT) Lähettäjä: rfc-editor@rfc-editor.org Vastausosoite: ietf@ietf.org Vastaanottaja: ietf-announce@ietf.org, rfc-dist@rfc-editor.org CC: rfc-editor@rfc-editor.org A new Request for Comments is now available in online RFC libraries. RFC 7333 Title: Requirements for Distributed Mobility Management Author: H. Chan, Ed., D. Liu, P. Seite, H. Yokota, J. Korhonen Status: Informational Stream: IETF Date: August 2014 Mailbox: h.a.chan@ieee.org, liudapeng@chinamobile.com, pierrick.seite@orange.com, hidetoshi.yokota@landisgyr.com, jouni.nospam@gmail.com Pages: 24 Characters: 50110 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-dmm-requirements-17.txt URL: https://www.rfc-editor.org/rfc/rfc7333.txt This document defines the requirements for Distributed Mobility Management (DMM) at the network layer. The hierarchical structure in traditional wireless networks has led primarily to centrally deployed mobility anchors. As some wireless networks are evolving away from the hierarchical structure, it can be useful to have a distributed model for mobility management in which traffic does not need to traverse centrally deployed mobility anchors far from the optimal route. The motivation and the problems addressed by each requirement are also described. This document is a product of the Distributed Mobility Management Working Group of the IETF. From nobody Thu Aug 21 10:18:40 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C58B51A0453 for ; Thu, 21 Aug 2014 10:18:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.869 X-Spam-Level: X-Spam-Status: No, score=-4.869 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L3pgHyqpayIv for ; Thu, 21 Aug 2014 10:18:36 -0700 (PDT) Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77C1B1A03C8 for ; Thu, 21 Aug 2014 10:18:36 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id s7LHIaZC013665; Thu, 21 Aug 2014 10:18:36 -0700 Received: from XCH-PHX-411.sw.nos.boeing.com (xch-phx-411.sw.nos.boeing.com [10.57.37.42]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s7LHIZii013647 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for ; Thu, 21 Aug 2014 10:18:35 -0700 Received: from XCH-BLV-106.nw.nos.boeing.com (130.247.25.122) by XCH-PHX-411.sw.nos.boeing.com (10.57.37.42) with Microsoft SMTP Server (TLS) id 14.3.181.6; Thu, 21 Aug 2014 10:18:34 -0700 Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.6]) by XCH-BLV-106.nw.nos.boeing.com ([169.254.6.188]) with mapi id 14.03.0181.006; Thu, 21 Aug 2014 10:18:34 -0700 From: "Templin, Fred L" To: "dmm@ietf.org" Thread-Topic: Recharter text request Thread-Index: Ac+9Y++ZxLpH/gpmTc6xqyEq0UCX0g== Date: Thu, 21 Aug 2014 17:18:33 +0000 Message-ID: <2134F8430051B64F815C691A62D9831832CF7C98@XCH-BLV-504.nw.nos.boeing.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [130.247.104.6] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-TM-AS-MML: disable Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/la8tDFRSpVja45MTiomF4vmM66c Subject: [DMM] Recharter text request X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Aug 2014 17:18:38 -0000 Hi, Back on June 11, the following text was dropped from the draft charter: "However, mobility management in a limited area, such as within an autonomous system, is not strictly limited to mentioned IP mobility protocols but can be any existing or a new protocol solution enabling the movement of a mobile node such as routing protocols." I would like to see this text brought back into the charter, because "within an autonomous system" brings distributed mobility management for enterprise networks into focus. Thanks - Fred fred.l.templin@boeing.com From nobody Mon Aug 25 04:10:18 2014 Return-Path: X-Original-To: dmm@ietfa.amsl.com Delivered-To: dmm@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02F641A9030 for ; Mon, 25 Aug 2014 04:10:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fqsguGzwKhuK for ; Mon, 25 Aug 2014 04:10:13 -0700 (PDT) Received: from mail-la0-x236.google.com (mail-la0-x236.google.com [IPv6:2a00:1450:4010:c03::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B444B1A902D for ; Mon, 25 Aug 2014 04:10:12 -0700 (PDT) Received: by mail-la0-f54.google.com with SMTP id hz20so12683928lab.13 for ; Mon, 25 Aug 2014 04:10:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=42+oCNznLl3dr1lpPNLpCfozkrfDPL6xqF74Vrg4dqk=; b=lAeXU0V27yB3M8SjlgfUYeYMORC9y1c5waG5ss/LnW42JXONvX94tdJCIC7c7eRXYH VJgVVnOGQnrRLg7c9fN4++mBoa+p6tLNQJiCOwpe0Nsm/CKA5a0tVpUJJaDUT87YxDs1 QdOGEW5W7LkOtyBGdpiJC+O9zU3Ih8YfihqRhgFhddg45mTI6mvcIK3eIPD6HNbUTIJS qqeAricj83ydIBFCfpUDlpkZuA5xPrFaZYNKSGaskU4teqJoyIwi67zpAsOOjUVf4e1c 9luJg3JvV/PdIFzjSvdyKo1oQ8mEOi80KY+5YnELlbL8Czl6k681lNefiIufd5fkWLK/ ilrA== X-Received: by 10.112.28.41 with SMTP id y9mr19413033lbg.67.1408965011043; Mon, 25 Aug 2014 04:10:11 -0700 (PDT) Received: from [192.168.250.224] ([194.100.71.98]) by mx.google.com with ESMTPSA id f9sm62212954lbd.46.2014.08.25.04.10.09 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 25 Aug 2014 04:10:09 -0700 (PDT) Message-ID: <53FB1990.1080809@gmail.com> Date: Mon, 25 Aug 2014 14:10:08 +0300 From: Jouni Korhonen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: "dmm@ietf.org" Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/g5t1VI-GwQglM5I1TJCBt7MmqSo Subject: [DMM] DMM Interim call #1 agenda X-BeenThere: dmm@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Distributed Mobility Management Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Aug 2014 11:10:15 -0000 Folks, The agenda for the Interim call #1 is simple: o Preliminaries (10 min) Note well Note takers Agenda bash Row call o Finalize the re-charter text (80 min) Review new implemented comments recevied prior the call. Editing based on online comments The aim is that after this call we can ship the text to AD and IESG more or less as-is. I would encourage WG to provide (in addition to what Alper and Fred already did) comments on the charter text _prior_ the meeting. - Jouni & Dapeng