[Gen-art] Re: Gen-ART Review of draft-ietf-16ng-ps-goals-03

Ben Campbell <ben@estacado.net> Tue, 11 December 2007 03:23 UTC

Return-path: <gen-art-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J1vi6-00072F-3T; Mon, 10 Dec 2007 22:23:06 -0500
Received: from gen-art by megatron.ietf.org with local (Exim 4.43) id 1J1vi4-0006zI-Qo for gen-art-confirm+ok@megatron.ietf.org; Mon, 10 Dec 2007 22:23:04 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J1vi4-0006xn-Ea for gen-art@ietf.org; Mon, 10 Dec 2007 22:23:04 -0500
Received: from dsl001-129-069.dfw1.dsl.speakeasy.net ([72.1.129.69] helo=estacado.net) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J1vi3-0000FO-Og for gen-art@ietf.org; Mon, 10 Dec 2007 22:23:04 -0500
Received: from [10.0.1.197] (adsl-68-94-61-48.dsl.rcsntx.swbell.net [68.94.61.48]) (authenticated bits=0) by estacado.net (8.14.1/8.14.1) with ESMTP id lBB3MnhR071889 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Mon, 10 Dec 2007 21:22:54 -0600 (CST) (envelope-from ben@estacado.net)
From: Ben Campbell <ben@estacado.net>
To: Junghoon Jee <jhjee@etri.re.kr>
In-Reply-To: <000b01c83b9c$f8d625a0$6b70fe81@etriabcb8a0047>
X-Priority: 3
References: <3EAF1D63-CC84-4BE6-ACA5-554E27E0290E@estacado.net> <000b01c83b9c$f8d625a0$6b70fe81@etriabcb8a0047>
Message-Id: <0E6708AB-3829-43E1-AA37-05B87138FED7@estacado.net>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v915)
Date: Mon, 10 Dec 2007 21:22:49 -0600
X-Mailer: Apple Mail (2.915)
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: smadanapalli@gmail.com, soohong.park@samsung.com, General Area Review Team <gen-art@ietf.org>, maximilian.riegel@nsn.com, gabriel_montenegro_2000@yahoo.com, jeff@streetwaves-networks.com, townsley@cisco.com, jari.arkko@piuha.net
Subject: [Gen-art] Re: Gen-ART Review of draft-ietf-16ng-ps-goals-03
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Errors-To: gen-art-bounces@ietf.org

Thanks for the quick response!

I think that the changes you propose will address my comments.

Thanks!

Ben.


On Dec 10, 2007, at 8:24 PM, Junghoon Jee wrote:

> Dear Ben Campbell,
> Thank you for carefully reviewing the draft.
> Please find inline replies.
>
> ----- Original Message -----
> From: "Ben Campbell" <ben@estacado.net>
> To: "General Area Review Team" <gen-art@ietf.org>
> Cc: <jari.arkko@piuha.net>; <maximilian.riegel@nsn.com>; <soohong.park@samsung.com 
> >; <gabriel_montenegro_2000@yahoo.com>; <jeff@streetwaves- 
> networks.com>; <smadanapalli@gmail.com>; <jhjee@etri.re.kr>; <townsley@cisco.com 
> >
> Sent: Tuesday, December 11, 2007 2:31 AM
> Subject: Gen-ART Review of draft-ietf-16ng-ps-goals-03
>
>
>>
>> I have been selected as the General Area Review Team (Gen-ART)
>> reviewer for this draft (for background on Gen-ART, please see
>> http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html).
>>
>> Please resolve these comments along with any other Last Call comments
>> you may receive.
>>
>>
>> Document: draft-ietf-16ng-ps-goals-03
>> Reviewer: Ben Campbell
>> Review Date:  10 December 2007
>> IETF LC End Date:  10 December 2007
>> IESG Telechat date: (if known)
>>
>> Summary:
>>
>> This document is almost ready for publication as an informational  
>> RFC.
>> There are some editorial nits that should be addressed prior to
>> publication.
>>
>> Comments:
>>
>> General: There are many occurrences of missing articles ("a", "an",  
>> or
>> "the") or the occasional use of an article where it does not belong.
>> While I assume that the RFC editors will fix these, it would same  
>> them
>> some work if you did an additional proofreading pass for this sort of
>> thing.
>
> Yes, additional proofreading will be done ASAP and the next revision  
> will apply the correction.
>
>>
>> Terminology Section, Definition of "Ethernet CS":
>>
>> It would be helpful to have a reference for 802.16 STD.
>
> That part will be amended that part like below:
> Ethernet CS: It means 802.3/Ethernet CS specific part of the Packet  
> CS defined in [IEEE802.16].
>
> IP CS terminology will also reference [IEEE802.16].
>
>>
>> Section 4.1, paragraph 7: "In the first point-to-point link model..."
>>
>> I think you mean to refer to the first model in the preceding list,
>> which is the point-to-point link model. The wording sounds like you
>> mean the first of a set of point-to-point link models, which is
>> incorrect. I suggest just dropping the word "first".
>
> Right!
> Let me drop that word.
>
>> A similar issue occurs in paragraph 9 ("In the second Ethernet like
>> link model...") and 11 ("The last shared IPv6 prefix link model")
>
> Let me drop the 'second' and 'last' in them.
>
>> Section 4.1, paragraph 9: "There needs mechanisms ..."
>>
>> It looks like some words are missing from this sentence.
>
> Let me try to apply the following change:
> - From: There needs mechanisms like IEEE 802.1D to realize multicast  
> and broadcast for Ethernet CS.
> - To: Therefore, we need a mechanism like 802.1D to realize  
> multicast and broadcast.
>
>>
>>
>> Section 4.1, paragraph 10, starting with "Moreover, the frequent IP
>> multicast..."
>>
>> I had trouble parsing this paragraph in general. Also, Is "IP subnet
>> like ethernet" the same as "Ethernet like link model"?
>
> Let me try to apply the following change:
> - From: Moreover, the frequent IP multicast and broadcast signaling  
> within the IP subnet like Ethernet needs to be avoided not to wake  
> up sleep/idle [IEEE802.16e] SSs.
> - To: Moreover, the frequent IP multicast and broadcast signaling  
> should be avoided not to wake up sleep/idle [IEEE802.16e] SSs.
>
>
>>
>> Section 4.1, last paragraph:
>>
>> "According to the point-to-point feature of 802.16's MAC, the Point-
>>   to-Point link model is the feasible IP Subnet model for IP CS under
>>   considering the multilink subnet problems. "
>>
>> I cannot parse this sentence--please rephrase.
>
> Let me try to apply the following change:
> - From: According to the point-to-point feature of 802.16's MAC, the  
> Point-to-Point link model is the feasible IP Subnet model for IP CS  
> under considering the multilink subnet problems.
> - To: According to the point-to-point feature of 802.16's MAC, the  
> Point-to-Point link model is the feasible IP Subnet model in case of  
> the IP CS.
>
>> Thanks!
>>
>> Ben Campbell.
>>
>
> Best Regards,
> Junghoon



_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art