Re: WGLC for draft-ietf-dmm-ondemand-mobility-08

Firstly, I agree that the only two examples of ‘resource’ type that may result with a creation of a source IP address are (i) an IP address and (ii) an IP prefix. I cannot think of any other magic, but perhaps some else can…

I am trying to avoid the term ‘prefix’ because it is not directly related to the Socket interface and I am trying to separate the definitions related to the Socket interface from the definitions related to the interaction between the MN and network.

If I mention prefixes, I will have to explain that the network may allocate IP addresses or IP sockets and that in cellular networks the recommended mechanism is to allocate /64 prefixes… I do not want to get into these details because they are not helpful for Socket API users.

However, I do intend to get into these details (and refer to the recommendation of RFC 7934) in the drafts that describe the extensions required to convey the IP service type between the IP stack in the MN and the network.

From: Lorenzo Colitti [mailto:[email protected]]
Sent: Tuesday, December 06, 2016 13:43
To: Moses, Danny <[email protected]>
Cc: Peter McCann <[email protected]>; jouni.nospam <[email protected]>; [email protected]; [email protected]
Subject: Re: [DMM] WGLC for draft-ietf-dmm-ondemand-mobility-08

On Mon, Dec 5, 2016 at 9:50 AM, Moses, Danny <[email protected]<mailto:[email protected]>> wrote:
I think it is important to describe that application developer can influence the type of service the IP session is receiving, while being vague about the mechanism of address allocation. Since you are concern with the draft using the term ‘address’ and I am concern with using the term ‘prefix’, I tried using the term ‘network resources’. Yes, it is vague, but that is the intention.

Ok, but what other type of resource can result in the MN being able to use an IP address? It seems to me that only an IP address or a prefix will qualify. And if allocating address on request is recommended, then that only leaves a prefix.

If there are other types of resource that I'm missing, then "resource" might be OK, as long as it has appropriate examples. But if the only two options are "address" and "prefix" and "address" is not recommended, then saying "resource" is at best unhelpful and at worst misleading.

Can you explain why you are concerned with using the term "prefix"?
---------------------------------------------------------------------
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
[email protected]
https://www.ietf.org/mailman/listinfo/dmm