RE: TSVDIR review of draft-ietf-mif-current-practices-10
Songhaibin <haibin.song@huawei.com> Tue, 03 May 2011 06:30 UTC
Return-Path: <haibin.song@huawei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4260AE073E; Mon, 2 May 2011 23:30:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MmVnv6898b6D; Mon, 2 May 2011 23:30:38 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 7EA51E06E1; Mon, 2 May 2011 23:30:38 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKL00BYDWQW39@szxga03-in.huawei.com>; Tue, 03 May 2011 14:30:32 +0800 (CST)
Received: from szxeml208-edg.china.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LKL003OUWQT02@szxga03-in.huawei.com>; Tue, 03 May 2011 14:30:32 +0800 (CST)
Received: from SZXEML401-HUB.china.huawei.com (10.82.67.31) by szxeml208-edg.china.huawei.com (172.24.2.60) with Microsoft SMTP Server (TLS) id 14.1.270.1; Tue, 03 May 2011 14:30:25 +0800
Received: from SZXEML505-MBS.china.huawei.com ([169.254.1.24]) by SZXEML401-HUB.china.huawei.com ([10.82.67.31]) with mapi id 14.01.0270.001; Tue, 03 May 2011 14:30:27 +0800
Date: Tue, 03 May 2011 06:30:26 +0000
From: Songhaibin <haibin.song@huawei.com>
Subject: RE: TSVDIR review of draft-ietf-mif-current-practices-10
In-reply-to: <843DA8228A1BA74CA31FB4E111A5C46201A8ECC4@ftrdmel0.rd.francetelecom.fr>
X-Originating-IP: [10.138.41.119]
To: "pierrick.seite@orange-ftgroup.com" <pierrick.seite@orange-ftgroup.com>, "tsv-dir@ietf.org" <tsv-dir@ietf.org>
Message-id: <E33E01DFD5BEA24B9F3F18671078951F10C1C8@SZXEML505-MBS.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="iso-8859-1"
Content-language: zh-CN
Content-transfer-encoding: quoted-printable
Accept-Language: en-US, zh-CN
Thread-topic: TSVDIR review of draft-ietf-mif-current-practices-10
Thread-index: AcwEjT94f5cFrLDDQnmx/e6koQnb/wAIoiCAASrnTyA=
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
References: <E33E01DFD5BEA24B9F3F18671078951F10B727@SZXEML505-MBS.china.huawei.com> <843DA8228A1BA74CA31FB4E111A5C46201A8ECC4@ftrdmel0.rd.francetelecom.fr>
X-Mailman-Approved-At: Tue, 03 May 2011 08:47:22 -0700
Cc: "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "draft-ietf-mif-current-practices@tools.ietf.org" <draft-ietf-mif-current-practices@tools.ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 May 2011 06:30:39 -0000
Hi Pierrick, Thank you very much for adopting the comments. Now I'm very satisfied with the document. BR, Haibin > -----Original Message----- > From: pierrick.seite@orange-ftgroup.com > [mailto:pierrick.seite@orange-ftgroup.com] > Sent: Wednesday, April 27, 2011 3:58 PM > To: Songhaibin; tsv-dir@ietf.org > Cc: tsv-ads@tools.ietf.org; ietf@ietf.org; > draft-ietf-mif-current-practices@tools.ietf.org > Subject: RE: TSVDIR review of draft-ietf-mif-current-practices-10 > > Hi Haibin, > > Thanks for the review. The draft has been updated accordingly. Please see > inline for more details. > > Br, > Pierrick > > > -----Message d'origine----- > > De : Songhaibin [mailto:haibin.song@huawei.com] > > Envoyé : mercredi 27 avril 2011 05:43 > > À : tsv-dir@ietf.org > > Cc : tsv-ads@tools.ietf.org; ietf@ietf.org; draft-ietf-mif-current- > > practices@tools.ietf.org > > Objet : TSVDIR review of draft-ietf-mif-current-practices-10 > > > > Hi, all, > > > > I've reviewed this document as part of the transport area directorate's > > ongoing effort to review key IETF documents. These comments were written > > primarily for the transport area directors, but are copied to the > > document's authors for their information and to allow them to address any > > issues raised. The authors should consider this review together with any > > other last-call comments they receive. Please always CC tsv-dir@ietf.org > > if you reply to or forward this review. > > > > The document describes how the current practices cope with challenges > > raised by multiple interfaces. This draft is very good to read. And the > > content is complete in my opinion. But I also have one main comment and > > two minor comments. > > -------- > > The main comment: > > > > Section 3.3. Focus on access network selection > > This section describes the current practices about how to select the > > access network/points, especially how connection manager deal with the > > list of preferred SSID and how does it select the access point for > > attachment. I think this is out of the scope of MIF WG, which is aimed to > > address the problems raised by multiple interfaces, instead of attachment > > network/point selection for one interface. And the charter explicitly > > says: " Network discovery and selection on lower layers as defined by RFC > > 5113 is out of scope." > > > > ok, section 3.3 is removed. > > > ------- > > Two minor comments: > > > > 3.1.1 Nokia S60 3rd Edition, Feature Pack 2 > > > > Paragraph " When SNAPs are used, it is possibly for the operating system > > to notify applications when a preferred IAP, leading to the same > > destination, becomes available...." > > > > Rewording: > > When SNAPs are used, the operating system can notify applications when a > preferred IAP, leading to the same destination, becomes available (for example, > when a user comes within range of his home WLAN access point), or when the > currently used IAP is no longer available. If so, applications have to reconnect > via another IAP (for example, when a user goes out of range of his home WLAN > and must move to the cellular network). > > > When the word "possibly" is used here, I am a little confused. I guess the > > authors mean the operating system provides the capability to notify the > > applications, but the applications may/may not use it. Or does it mean the > > operating system can decide whether to notify the applications? > > > > Section 3.3.1 and 3.3.2 > > > > These two sections describe the access network selection for Android/HTC > > Magic and RIM BlackBerry. But they use the similar method and most of the > > text are the same. So it is possible to merge these two sections. But my > > this comment is useless if the main comment is accepted. > > > > n/a since section is removed. > > > By the way, in Section 3.1.3 line 2, delete duplicate "can use". > > > > Done. > > > I hope this feedback will be useful to the authors. > > > > Yes, thanks. > > > -Haibin
- TSVDIR review of draft-ietf-mif-current-practices… Songhaibin
- RE: TSVDIR review of draft-ietf-mif-current-pract… pierrick.seite
- RE: TSVDIR review of draft-ietf-mif-current-pract… Songhaibin