Dear Anthony and Alex, I believe Anthony has pointed out that, maintaining IP session continuity is just "an example" of maintaining upper layer transparency. It should be fundamental to maintain the upper layer transparency even though upper layer may be able to cope with changing IP address, e.g. maintaining the QoS performance or location context for the service layer. Hence, the clause of the "Otherwise" portion is not very clear as Alex has pointed out.
Hence, I would like to suggest a friendly amendment to Anthony's latest proposal as follows: >>>>> The DMM solutions MUST provide transparency above the IP layer when needed. Such transparency is needed, for example, upon change of point of attachment to the Internet for the application flows that cannot cope with a change of IP address may trigger the application to decline the handover request. >>>>> Would this be acceptable to both of you? Thanks. Tricci h chan <[email protected]> Sent by: [email protected] 08/03/2012 10:07 AM To Alexandru Petrescu <[email protected]> cc "[email protected]" <[email protected]> Subject Re: [DMM] Comment on Req2 transparency for DMM How about the following: The DMM solutions MUST provide transparency above the IP layer when needed. Such transparency is needed, for example, upon change of point of attachment to the Internet for the application flows that cannot cope with a change of IP address. Otherwise the support to maintain a stable home IP address or prefix during handover may be declined. Or The DMM solutions MUST enable transparency above the IP layer. Such transparency is needed, for example, upon change of point of attachment to the Internet for the application flows that cannot cope with a change of IP address. Otherwise the support to maintain a stable home IP address or prefix during handover may be declined. H Anthony Chan -----Original Message----- From: Alexandru Petrescu [mailto:[email protected]] Sent: Thursday, August 02, 2012 11:39 AM To: h chan Cc: [email protected] Subject: Re: [DMM] Comment on Req2 transparency for DMM H Anthony, Yes, this reflects Sri's and my suggestion about removal of MN/MR qualifier. I agree with the idea of the new text as you put it. Then, if I re-read just like that, there still seems to be some difficulty to my brain to understand: Le 01/08/2012 23:35, h chan a écrit : > The DMM solutions MUST provide transparency above the IP layer when > needed, such as upon change of point of attachment to the Internet, > for the application flows that cannot cope with a change of IP > address. Otherwise the support to maintain a stable home IP address > or prefix during handover may be declined. I don't understand the last phrase - the 'otherwise' relates to the first MUST? Or to the latter 'cannot'? But this may be just nitpicking on the use of language. I agree with the direction of the idea and thank you for having provided the modification. Alex _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s). If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited. If you have received this mail in error, please delete it and notify us immediately.
_______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
