Re: [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01

[Dhananjay Patki (dhpatki)]

Hi Siel,

Please see inline.
--
Regards,
Dhananjay

-Original Message-



From: dmm  on behalf of Seil Jeon 
Date: Tuesday, 21 June 2016 at 2:38 PM
To: "dmm@ietf.org" 
Cc: '成 鹏' , "dmm@ietf.org" 
Subject: Re: [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01

>Hi,
>
>I have read this draft and some questions come to my mind. Let me know my
>understanding is correct or not first.
>
>Actually, this draft comes to a proposed container option to be delivered by
>a PBA message, enabling the LMA to put various parameters related to the MAG
>enforcement, not doing it individually for less signaling overhead(?)

[Dhananjay] By ‘doing it individually’ do you mean separate options (instead of 
sub-options) for Binding Update Control and Heartbeat Control? The idea is to 
keep all such LMA controlled parameters grouped into a single container option.


>
>And when I saw following sentence
>
>"Configuring aggressive values of parameters such as re-registration timeout
>and heartbeat interval can potentially create considerable signaling load on
>the LMA."
>
>I was expecting you would take care of it in terms of efficient transmission
>perspective as well. Is it out-of-scope, right?

[Dhananjay] This extension is only to communicate the values enforced by the 
LMA to the MAG. Tuning of the value for efficient transmission is out of scope 
of this extension. The above sentence is only to state a caution which is 
applicable even without using this extension.

>
>
>
>Two minor typos are,
>
>In Introduction, aggresive -> aggressive
>
>in 5.2, reveived -> received(?)

[Dhananjay] Thanks for pointing these out. I am correcting these in the next 
version.

Regards,
Dhananjay

>
>
>Regards,
>Seil Jeon
>
>
>
>-Original Message-
>From: dmm [mailto:dmm-boun...@ietf.org] On Behalf Of Jouni Korhonen
>Sent: Wednesday, June 08, 2016 2:14 AM
>To: dmm@ietf.org; Jouni; 成 鹏
>Subject: [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01
>
>Folks,
>
>This email starts the WGLC #2 for
>draft-ietf-dmm-lma-controlled-mag-params-01. Post your comment to the
>mailing list and also add your issues/correction requests/concerns etc into
>the Issue Tracker.
>
> WGLC #2 Starts: 6/7/2016
> WGLC #2 Ends: 6/21/2016 EOB PDT
>
>Regards,
> Jouni & Dapeng
>
>___
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm
>
>___
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm
___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

Re: [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01

[Dhananjay Patki (dhpatki)]

Hi Yan,

1) in the Introduction Section, "have tens of thousands of MAGs" is too 
specific here to describe the scenario.
[Dhananjay] This extension becomes necessary when there is a large scale of 
MAGs and the above wording is only to realize that. But of course, it can be 
used even at smaller scale.

2) this extension focuses on Refresh and Heartbeat control, is it necessary to 
leave space for additional use cases?
[Dhananjay] Space of additional use cases is left for extensibility of the 
option.
--
Regards,
Dhananjay


From: dmm > on behalf of 
"Z.W. Yan" >
Date: Sunday, 12 June 2016 at 6:42 AM
To: "jouni.nospam" >, 
"dmm@ietf.org" >, 
"jouni.nospam" >, 成 鹏 
>
Subject: Re: [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01

Hi, all,
This draft reads good and I support it to be moved forward.
Two comments are :
1) in the Introduction Section, "have tens of thousands of MAGs" is too 
specific here to describe the scenario.
2) this extension focuses on Refresh and Heartbeat control, is it necessary to 
leave space for additional use cases?

BR,

2016-06-12

Z.W. Yan

发件人： Jouni Korhonen
发送时间： 2016-06-08  01:13:58
收件人： dmm@ietf.org; Jouni; 成 鹏
抄送：
主题： [DMM] WGLC #2 for draft-ietf-dmm-lma-controlled-mag-params-01
Folks,
This email starts the WGLC #2 for
draft-ietf-dmm-lma-controlled-mag-params-01. Post your comment to the
mailing list and also add your issues/correction requests/concerns etc
into the Issue Tracker.
 WGLC #2 Starts: 6/7/2016
 WGLC #2 Ends: 6/21/2016 EOB PDT
Regards,
 Jouni & Dapeng
___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm
___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

Re: [DMM] New version of the OnDemand Mobility draft

[Seil Jeon]

Hi Jouni,

The concern was clearly addressed in the -06 version.
I support the I-D.

Regards,
Seil Jeon


-Original Message-
From: dmm [mailto:dmm-boun...@ietf.org] On Behalf Of Jouni Korhonen
Sent: Friday, July 01, 2016 2:06 AM
To: Seil Jeon; Alexandre Petrescu
Cc: dmm@ietf.org
Subject: Re: [DMM] New version of the OnDemand Mobility draft

Seil, Alex,

Have your concerns been addressed in the -06 revision?

- Jouni

6/30/2016, 2:20 AM, Moses, Danny kirjoitti:
>
> Hi,
>
> I have posted a new version of the OnDemand Mobility draft:
> _draft-ietf-dmm-ondemand-mobility-06_
> .
> This new version includes some text editing according to the comments 
> from Seil and change of classification from the Standard track to 
> Informational.
>
> Please support it (those who have not cast their support yet).
>
> Thanks,
> /Danny
>
>
> -
> A member of the Intel Corporation group of companies
>
> This e-mail and any attachments may contain confidential material for 
> the sole use of the intended recipient(s). Any review or distribution 
> by others is strictly prohibited. If you are not the intended 
> recipient, please contact the sender and delete all copies.
>
>
>
> ___
> dmm mailing list
> dmm@ietf.org
> https://www.ietf.org/mailman/listinfo/dmm
>

___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

Re: [DMM] New version of the OnDemand Mobility draft

[Jouni Korhonen]

Seil, Alex,

Have your concerns been addressed in the -06 revision?

- Jouni

6/30/2016, 2:20 AM, Moses, Danny kirjoitti:


Hi,

I have posted a new version of the OnDemand Mobility draft:
_draft-ietf-dmm-ondemand-mobility-06_
.
This new version includes some text editing according to the comments
from Seil and change of classification from the Standard track to
Informational.

Please support it (those who have not cast their support yet).

Thanks,
/Danny


-
A member of the Intel Corporation group of companies

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.



___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm



___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

Re: [DMM] draft-ietf-dmm-ondemand-mobility-05

[Behcet Sarikaya]

On Wed, Jun 29, 2016 at 4:04 PM, Jouni Korhonen  wrote:
> 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
>
> To me it is there..
>
>   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.
>
> And again here.
>
> If apps or mobile node need to be able to select appropriate address I find
> it ok to describe it.. call it api or not in the charter.
>
> - Jouni
>

Not to me.

I don't see any API. The API RFC 5014 was done in 6man. mif WG used to
do API. mif WG had clear items on API in its charter.






Regards,

Behcet
>
>
>
> 6/29/2016, 1:12 PM, Behcet Sarikaya kirjoitti:
>>
>> On Wed, Jun 29, 2016 at 3:03 PM, Jouni Korhonen 
>> wrote:
>>>
>>> Lo and behold your cry for intended status change will happen!
>>>
>>
>>
>> Lo I just now checked it.
>> I could not see any API development in dmm charter.
>>
>> Aren't you responsible for this?
>>
>> Regards,
>>
>> Behcet
>>>
>>> Actually, this came up earlier because 1) the I-D makes a normative
>>> referecence to an informational RFC5014 and 2) API documents are
>>> informational in general. It just did not make to the latest revision..
>>>
>>
>>
>>> - JOuni
>>>
>>>
>>> 6/29/2016, 9:07 AM, Behcet Sarikaya kirjoitti:


  Hi all,

 I quickly looked at this draft.
 It seems like the authors or Danny changed "sustained IP address" to
 "session lasting IP address". It sounds a bit better.
 However, my concerns about sustained IP address remain the same on the
 session lasting IP address because semantically they mean the same
 thing, the session lasting is just a more flashy name.

 I really don't understand how in the world this draft became a WG
 draft in the first place. Given that, my suggestion is to finish up
 this work by changing it to Informational. I don't believe it is
 implementable.

 This draft is also not the type of draft dmm should be working on, dmm
 I think is a continuation of MIP related mobility WGs and this draft
 has nothing to do with this.

 Make it Informational, folks.

 Behcet

 ___
 dmm mailing list
 dmm@ietf.org
 https://www.ietf.org/mailman/listinfo/dmm

>>>
>

___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm

[DMM] I-D Action: draft-ietf-dmm-ondemand-mobility-06.txt

[internet-drafts]

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Distributed Mobility Management of the IETF.

Title   : On Demand Mobility Management
Authors : Alper Yegin
  Danny Moses
  Kisuk Kweon
  Jinsung Lee
  Jungshin Park
Filename: draft-ietf-dmm-ondemand-mobility-06.txt
Pages   : 12
Date: 2016-06-30

Abstract:
   Applications differ with respect to whether they need IP session
   continuity and/or IP address reachability.  The network providing the
   same type of service to any mobile host and any application running
   on the host yields inefficiencies.  This document describes a
   solution for taking the application needs into account in selectively
   providing IP session continuity and IP address reachability on a per-
   socket basis.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-ondemand-mobility/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-dmm-ondemand-mobility-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-ondemand-mobility-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

___
dmm mailing list
dmm@ietf.org
https://www.ietf.org/mailman/listinfo/dmm