RE: [Mip6] Comments on draft-chen-mip6-gprs-02.txt
"CHEN, Xiaobao" <xiaobao.chen@orange.co.uk> Wed, 03 November 2004 11:36 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26862 for <mip6-web-archive@ietf.org>; Wed, 3 Nov 2004 06:36:32 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CPJgb-0001iT-EQ for mip6-web-archive@ietf.org; Wed, 03 Nov 2004 06:52:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPJMV-0005Sq-Uk; Wed, 03 Nov 2004 06:31:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CPJBf-0002BN-J5 for mip6@megatron.ietf.org; Wed, 03 Nov 2004 06:20:25 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA24655 for <mip6@ietf.org>; Wed, 3 Nov 2004 06:20:19 -0500 (EST)
Received: from mail32.messagelabs.com ([62.173.108.211]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1CPJQm-00018Q-LK for mip6@ietf.org; Wed, 03 Nov 2004 06:36:11 -0500
X-VirusChecked: Checked
X-Env-Sender: xiaobao.chen@orange.co.uk
X-Msg-Ref: server-6.tower-32.messagelabs.com!1099480555!23426794!1
X-StarScan-Version: 5.4.2; banners=orange.co.uk,-,-
X-Originating-IP: [193.35.135.133]
Received: (qmail 11021 invoked from network); 3 Nov 2004 11:15:55 -0000
Received: from unknown (HELO hagrid.orange.co.uk) (193.35.135.133) by server-6.tower-32.messagelabs.com with SMTP; 3 Nov 2004 11:15:55 -0000
Received: from bit.orange.co.uk (bit.orange.co.uk) by hagrid.orange.co.uk (Content Technologies SMTPRS 4.3.10) with ESMTP id <T6d0a8db7dec12387855b8@hagrid.orange.co.uk>; Wed, 3 Nov 2004 11:14:55 +0000
Received: from ukexbrismtp02.uk.orangegad.com (ukexbrismtp02.orange.co.uk [172.16.131.106]) by bit.orange.co.uk with SMTP id iA3BEsD04557; Wed, 3 Nov 2004 11:14:54 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Mip6] Comments on draft-chen-mip6-gprs-02.txt
Date: Wed, 03 Nov 2004 11:14:53 -0000
Message-ID: <8C8F0E870815804FAC506E74B8A6F7B401C3AC0A@UKEXBRIMBX001.uk.orangegad.com>
Thread-Topic: [Mip6] Comments on draft-chen-mip6-gprs-02.txt
Thread-Index: AcTBGbU0IVZ6h74VRnqlqCxK4VMrCgAdcFdH
From: "CHEN, Xiaobao" <xiaobao.chen@orange.co.uk>
To: Samita Chakrabarti <Samita.Chakrabarti@eng.sun.com>, mip6@ietf.org
X-OriginalArrivalTime: 03 Nov 2004 11:14:54.0193 (UTC) FILETIME=[582EBE10:01C4C196]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a92270ba83d7ead10c5001bb42ec3221
Content-Transfer-Encoding: quoted-printable
Cc: samita.chakrabarti@sun.com
X-BeenThere: mip6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mip6.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip6@ietf.org>
List-Help: <mailto:mip6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip6>, <mailto:mip6-request@ietf.org?subject=subscribe>
Sender: mip6-bounces@ietf.org
Errors-To: mip6-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31b28e25e9d13a22020d8b7aedc9832c
Content-Transfer-Encoding: quoted-printable
Samita, Many thanks for the comments. My response is in line. Regards, Xiaobao -----Original Message----- From: mip6-bounces@ietf.org on behalf of Samita Chakrabarti Sent: Tue 02/11/2004 19:54 To: mip6@ietf.org Cc: samita.chakrabarti@sun.com Subject: [Mip6] Comments on draft-chen-mip6-gprs-02.txt I understand from the authors that this document is targeting for individual RFC submission. I only have some editorial comments. minor nits: In my copy, I was getting blank pages off and on. Please check if it still happens in the latest version. [xc] Yes, will check it again and make sure it won't happen in the next revised version. General comment: Since this document describes issues with GPRS services and IMS services, it might be better to organize the issues under each of those services; for example: 3.1 GPRS Services 3.1.1 Mobile Terminal defined packet filtering 3.1.2 Network Service Defined packet filtering 3.2 IMS Services : : [xc] Good point. This is certainly one of the ways for organising the structure for the problems descriptions that we considered before. After comparing this with the current structure of the descriptions, i.e. the GPRS node being either the correspondent node or the mobile node, we found it perhaps easier and clearer for some readers who may not be very familiar with the 3GPP networks to understand the descriptions by describing the problems in a style close to the way that Mobile IP works. But I will discuss this again with other co-authors to see what is the best way for describing the problems clearly. In section 3.1 "The TFT only applies...with it" is not very clear, please re-word the senstence. [xc] Yes, will provide clarifications in the next revised version. 4.1.1.2 "As a result, two possible decisions can be made by the GGSN... to B" Is this indicating possible solutions or today GGSN is capable of handling the Route optimization this way? [xc] In current 3GPP standard specifications, the GGSN allows one PDP without TFT at maximum. And it is also possible that all PDP contexts have TFT's. The sentense you mentiond in the draft indicates that the GGSN, when having a PDP without the TFT, may choose to use this PDP to deliver the IP datagrams that fail to match any TFT's. But the problem with this is that the IP datagrams will not receive the correct QoS. And this won't work for the cases when all PDP's have TFT'. This sentense does not intend to indicate any solution but further describe problems still exist even if one TFT-free PDP is possible. section 4.2.1.2 "If tunnelled packets ....PDP Context to B" - may be this part of text is redundant since we are describing the issues. [xc] We will consider to delete the sentence. section 5. At the end of the page, it made reference to [14] which is non-existent. [xc] Yes, it will be corrected. As discussed before on the private list that "home agent tunneling" is due to the issue of GGSN's handling of IP-in-IP tunnel - it is not a MIP6 specific issue - it should be mentioned in the document to clarify that. [xc] Agreed. -Samita _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6 ******************************************************************** Important. Confidentiality: This communication is intended for the above-named person and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of the company. If it has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender immediately. Monitoring/Viruses. Orange may monitor all incoming and outgoing emails in line with current legislation. Although we have taken steps to ensure that this email and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. Orange PCS Limited is a subsidiary of Orange SA and is registered in England No 2178917, with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ. ******************************************************************** _______________________________________________ Mip6 mailing list Mip6@ietf.org https://www1.ietf.org/mailman/listinfo/mip6
- [Mip6] Comments on draft-chen-mip6-gprs-02.txt Samita Chakrabarti
- RE: [Mip6] Comments on draft-chen-mip6-gprs-02.txt CHEN, Xiaobao