RE: [16NG] RE: Last Call: draft-ietf-16ng-ps-goals (IP over 802.16Problem Statement and Goals) to Informational RFC
<rana.sircar@wipro.com> Fri, 14 December 2007 05:44 UTC
Return-path: <16ng-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1J33La-0006aX-SJ; Fri, 14 Dec 2007 00:44:30 -0500
Received: from 16ng by megatron.ietf.org with local (Exim 4.43) id 1J33LZ-0006W8-Hf for 16ng-confirm+ok@megatron.ietf.org; Fri, 14 Dec 2007 00:44:29 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1J33LZ-0006Vz-6Q; Fri, 14 Dec 2007 00:44:29 -0500
Received: from wip-cdc-wd.wipro.com ([203.91.201.26]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1J33LW-0004eK-2p; Fri, 14 Dec 2007 00:44:27 -0500
Received: from wip-cdc-wd.wipro.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id D1FA918065; Fri, 14 Dec 2007 11:14:22 +0530 (IST)
Received: from blr-ec-bh02.wipro.com (blr-ec-bh02.wipro.com [10.201.50.92]) by wip-cdc-wd.wipro.com (Postfix) with ESMTP id C047E18061; Fri, 14 Dec 2007 11:14:22 +0530 (IST)
Received: from DEL-GGN-MBX01.wipro.com ([10.105.51.182]) by blr-ec-bh02.wipro.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 14 Dec 2007 11:14:23 +0530
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [16NG] RE: Last Call: draft-ietf-16ng-ps-goals (IP over 802.16Problem Statement and Goals) to Informational RFC
Date: Fri, 14 Dec 2007 11:14:22 +0530
Message-ID: <9FF78FB380ACF749B94BE267F6E3663B0218DA8B@DEL-GGN-MBX01.wipro.com>
In-Reply-To: <f7c7d76e0712131957k117b0440o9ec005d0ac6779fc@mail.gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [16NG] RE: Last Call: draft-ietf-16ng-ps-goals (IP over 802.16Problem Statement and Goals) to Informational RFC
thread-index: Acg+BalNr7ySTGuGSqK/8Yaaqrcs6AAAjdZg
From: rana.sircar@wipro.com
To: soohongp@gmail.com, dromasca@avaya.com
X-OriginalArrivalTime: 14 Dec 2007 05:44:23.0599 (UTC) FILETIME=[617E3BF0:01C83E14]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 67c1ea29f88502ef6a32ccec927970f0
Cc: ietf@ietf.org, 16ng@ietf.org
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Errors-To: 16ng-bounces@ietf.org
Dear Daniel, I have a few qyeries - 1. It is mentioned in the introduction that Broadband Wireless Access networks addresses the inadequacies of low Bandwidth wireless communication. It mentions "Wide coverage" as a requirement (which is true).However, Wide coverage is not due to broadband wireless properties. 2. I do agree that Network Management and Policy Management (and possibly Device Management) should be handled separately. Network management does not only talk of MIBs, but a larger architecture and requirements. This apart, there are important policy and device management requirements that need to be covered. Thus, a separate draft is useful. However, as you have mentioned, a single line in the current draft would be helpful 3. In introduction and later, it talks of point-to-point links (802.16d) only. Are we not considering 802.16e (and later standards)? Best Regards, Rana -----Original Message----- From: Daniel Park [mailto:soohongp@gmail.com] Sent: Friday, December 14, 2007 9:27 AM To: Romascanu, Dan (Dan) Cc: ietf@ietf.org; 16ng@ietf.org Subject: Re: [16NG] RE: Last Call: draft-ietf-16ng-ps-goals (IP over 802.16Problem Statement and Goals) to Informational RFC Dan, Sorry for the loooong delay. That's an interesting issue. As a part of goal of 16ng, it seems to be valuable work. First, let me double check what's going on in IEEE 802.16 and WiMAX forum in terms of management method, then get back to you with further clarification. I think network management method can be addressed in a separated draft if necessary later. Now, just adding a simple sentence into PS and Goal document is doable to move it forward... For example: Goal # X: Clarification the network management method of IP over IEEE 802.16 for IP and/or Ethernet CS. What do you think ? Daniel Park Co-chair, 16NG Working Group On 12/11/07, Romascanu, Dan (Dan) <dromasca@avaya.com> wrote: > > The current version of the document completely lacks any information > regarding manageability of networks that run IP over IEEE 802.16. At a > minimum I would expect a short discussion about the interfaces model of > an IP over 802.16 or have the definition of such a model as well as of a > standard management interface mentioned as goals in Section 4.4. > > Dan > > > > > > -----Original Message----- > > From: The IESG [mailto:iesg-secretary@ietf.org] > > Sent: Monday, November 19, 2007 5:41 PM > > To: IETF-Announce > > Cc: 16ng@ietf.org > > Subject: Last Call: draft-ietf-16ng-ps-goals (IP over 802.16 > > Problem Statement and Goals) to Informational RFC > > > > The IESG has received a request from the IP over IEEE 802.16 > > Networks WG > > (16ng) to consider the following document: > > > > - 'IP over 802.16 Problem Statement and Goals ' > > <draft-ietf-16ng-ps-goals-03.txt> as an Informational RFC > > > > The IESG plans to make a decision in the next few weeks, and > > solicits final comments on this action. Please send > > substantive comments to the ietf@ietf.org mailing lists by > > 2007-12-10. Exceptionally, comments may be sent to > > iesg@ietf.org instead. In either case, please retain the > > beginning of the Subject line to allow automated sorting. > > > > The file can be obtained via > > http://www.ietf.org/internet-drafts/draft-ietf-16ng-ps-goals-03.txt > > > > > > IESG discussion can be tracked via > > https://datatracker.ietf.org/public/pidtracker.cgi?command=vie > > w_id&dTag=15284&rfc_flag=0 > > > > > > _______________________________________________ > > IETF-Announce mailing list > > IETF-Announce@ietf.org > > https://www1.ietf.org/mailman/listinfo/ietf-announce > > > > > _______________________________________________ > 16NG mailing list > 16NG@ietf.org > https://www1.ietf.org/mailman/listinfo/16ng > _______________________________________________ 16NG mailing list 16NG@ietf.org https://www1.ietf.org/mailman/listinfo/16ng _______________________________________________ 16NG mailing list 16NG@ietf.org https://www1.ietf.org/mailman/listinfo/16ng
- [16NG] Last Call: draft-ietf-16ng-ps-goals (IP ov… The IESG
- [16NG] RE: Last Call: draft-ietf-16ng-ps-goals (I… Romascanu, Dan (Dan)
- Re: [16NG] RE: Last Call: draft-ietf-16ng-ps-goal… Daniel Park
- Re: [16NG] RE: Last Call: draft-ietf-16ng-ps-goal… Junghoon Jee
- Re: [16NG] RE: Last Call: draft-ietf-16ng-ps-goal… Junghoon Jee
- RE: [16NG] RE: Last Call: draft-ietf-16ng-ps-goal… rana.sircar