Re: [16NG] Request for review of draft-ietf-16ng-ip-over-ethernet-over-802-dot-16 from a DSL perspective

Frank Xia <xiayangsong@huawei.com> Wed, 10 December 2008 16:47 UTC

Return-Path: <16ng-bounces@ietf.org>
X-Original-To: 16ng-archive@optimus.ietf.org
Delivered-To: ietfarch-16ng-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D090D3A6969; Wed, 10 Dec 2008 08:47:36 -0800 (PST)
X-Original-To: 16ng@core3.amsl.com
Delivered-To: 16ng@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F0CAB3A6969 for <16ng@core3.amsl.com>; Wed, 10 Dec 2008 08:47:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.109
X-Spam-Level:
X-Spam-Status: No, score=-1.109 tagged_above=-999 required=5 tests=[BAYES_05=-1.11, STOX_REPLY_TYPE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VvBkDbc+ezpa for <16ng@core3.amsl.com>; Wed, 10 Dec 2008 08:47:35 -0800 (PST)
Received: from usaga04-in.huawei.com (usaga04-in.huawei.com [206.16.17.180]) by core3.amsl.com (Postfix) with ESMTP id 1D95C3A63EC for <16ng@ietf.org>; Wed, 10 Dec 2008 08:47:35 -0800 (PST)
Received: from huawei.com (usaga04-in [172.18.4.101]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KBO00EPP6N2VV@usaga04-in.huawei.com> for 16ng@ietf.org; Wed, 10 Dec 2008 10:47:27 -0600 (CST)
Received: from X24512z ([10.124.12.66]) by usaga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KBO00GDE6N0AG@usaga04-in.huawei.com> for 16ng@ietf.org; Wed, 10 Dec 2008 10:47:26 -0600 (CST)
Date: Wed, 10 Dec 2008 10:47:23 -0600
From: Frank Xia <xiayangsong@huawei.com>
To: g_e_montenegro@yahoo.com, Mark Townsley <townsley@cisco.com>
Message-id: <00aa01c95ae6$fb48cd00$420c7c0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-Priority: 3
X-MSMail-priority: Normal
References: <817000.84300.qm@web81901.mail.mud.yahoo.com>
Cc: draft-ietf-16ng-ip-over-ethernet-over-802-dot-16@tools.ietf.org, 16ng@ietf.org
Subject: Re: [16NG] Request for review of draft-ietf-16ng-ip-over-ethernet-over-802-dot-16 from a DSL perspective
X-BeenThere: 16ng@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: 16ng working group discussion list <16ng.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/16ng>
List-Post: <mailto:16ng@ietf.org>
List-Help: <mailto:16ng-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/16ng>, <mailto:16ng-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: 16ng-bounces@ietf.org
Errors-To: 16ng-bounces@ietf.org

Hi Folks

General comments include:
1)removing public access recommendation part.
  We can have an informational draft on
  "IPoEo802.16 access in Broadband Network".
2)re-considering distributed bridging funcionalities.
  It is hard to implement when a centralized database needed.

Please check the detailed comments:
1) Section 8
  "Therefore, the AR in the  public access link model
   SHOULD assign common IPv6 prefixes to all SSs
   served by the AR"
  IP addresing is still under discussion in Broadband Forum.
  However, IMO, these is almost a consensus that each
  SS uses a unique IPv6 prefixe.

2)Section 7.3.
 When a network-side bridge receives an ARP request
  from a host behind subsriber-side bridge, the network
  side bridge should discard the request if the destination
  host is also behind the same subscriber-side switch.

3)Appendix B.
  I propose that the edge network-side switchs
  are responsible for host database maitenance, and
  responsing ARP request as a proxy.
  No centralized database is needed.

4)Section 7.2
   It is better to remove TR101 stuff from this section.

BR
Frank


----- Original Message ----- 
From: <g_e_montenegro@yahoo.com>
To: "Mark Townsley" <townsley@cisco.com>; "Frank Xia" 
<xiayangsong@huawei.com>
Cc: "Jari Arkko" <jari.arkko@piuha.net>; "Soohong Daniel Park" 
<soohongp@gmail.com>; 
<draft-ietf-16ng-ip-over-ethernet-over-802-dot-16@tools.ietf.org>; 
<16ng@ietf.org>
Sent: Tuesday, November 18, 2008 6:01 PM
Subject: Request for review of 
draft-ietf-16ng-ip-over-ethernet-over-802-dot-16 from a DSL perspective


> Hi Mark and Frank,
>
> Your names have been offered as people who are familiar with DSL network 
> deployments.
>
> We would like to request your review of a 16ng draft that may have some 
> similarities with those deployments:
>
> http://tools.ietf.org/html/draft-ietf-16ng-ip-over-ethernet-over-802-dot-16-07
>
> This draft is in AD review, and Jari asked the WG to close the loop on 
> this draft with DSL-savvy folks. The idea is not that they should match, 
> but that DSL deployments have some similarities, hence you might have good 
> insight and feedback on this draft.
>
> Please feel free to forward to other DSL experts you may be aware of. If 
> at all possible, we would like to get some feedback by December 12, 2008.
>
> Thanks in advance,
>
> Gabriel and Daniel, 16ng co-chairs
>
> 


_______________________________________________
16NG mailing list
16NG@ietf.org
https://www.ietf.org/mailman/listinfo/16ng