Re: [v6ops] "RE: goals of draft-zhang-v6ops-ipv6oa-iwf-00.txt "

"Will Liu (Shucheng)" <liushucheng@huawei.com> Wed, 25 July 2012 03:55 UTC

Return-Path: <liushucheng@huawei.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB7F911E8080 for <v6ops@ietfa.amsl.com>; Tue, 24 Jul 2012 20:55:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.032
X-Spam-Level:
X-Spam-Status: No, score=-5.032 tagged_above=-999 required=5 tests=[AWL=-1.386, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_32=0.6, MIME_BASE64_TEXT=1.753, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s5C2V2QgC0qW for <v6ops@ietfa.amsl.com>; Tue, 24 Jul 2012 20:55:11 -0700 (PDT)
Received: from dfwrgout.huawei.com (dfwrgout.huawei.com [206.16.17.72]) by ietfa.amsl.com (Postfix) with ESMTP id 101F111E807F for <v6ops@ietf.org>; Tue, 24 Jul 2012 20:55:11 -0700 (PDT)
Received: from 172.18.9.243 (EHLO dfweml201-edg.china.huawei.com) ([172.18.9.243]) by dfwrg01-dlp.huawei.com (MOS 4.2.3-GA FastPath) with ESMTP id AIH93370; Tue, 24 Jul 2012 23:55:10 -0400 (EDT)
Received: from DFWEML404-HUB.china.huawei.com (10.193.5.203) by dfweml201-edg.china.huawei.com (172.18.9.107) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 24 Jul 2012 20:52:37 -0700
Received: from SZXEML423-HUB.china.huawei.com (10.82.67.162) by dfweml404-hub.china.huawei.com (10.193.5.203) with Microsoft SMTP Server (TLS) id 14.1.323.3; Tue, 24 Jul 2012 20:52:40 -0700
Received: from SZXEML546-MBX.china.huawei.com ([169.254.3.75]) by szxeml423-hub.china.huawei.com ([10.82.67.162]) with mapi id 14.01.0323.003; Wed, 25 Jul 2012 11:52:35 +0800
From: "Will Liu (Shucheng)" <liushucheng@huawei.com>
To: "wang.cui1@zte.com.cn" <wang.cui1@zte.com.cn>
Thread-Topic: [v6ops] "RE: goals of draft-zhang-v6ops-ipv6oa-iwf-00.txt "
Thread-Index: AQHNagaLJtbkYYoO8kagl+XtfL/+sZc5Wfdw
Date: Wed, 25 Jul 2012 03:52:34 +0000
Message-ID: <C9B5F12337F6F841B35C404CF0554ACB2B9494F0@szxeml546-mbx.china.huawei.com>
References: <OFD22200D9.689DC01C-ON48257A45.00299C89-48257A45.002A9310@zte.com.cn> <CAPu_Ac4Crr7y_WUxS7iZ9yTTg=tTEvaxsjXYXdR0qTZqDn5LgQ@mail.gmail.com> <CAPu_Ac5pB=Z03x+2RN2GAN7k+pFJBT6C9YF78g7iKs3AQ4WUNg@mail.gmail.com>
In-Reply-To: <CAPu_Ac5pB=Z03x+2RN2GAN7k+pFJBT6C9YF78g7iKs3AQ4WUNg@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.66.79.130]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] "RE: goals of draft-zhang-v6ops-ipv6oa-iwf-00.txt "
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 Jul 2012 03:55:12 -0000

Let me add one point. In fact the IPv6oA interworking is sort of an ND and IND proxy. It makes changes to ND and IND messages. However, it does not initiate the ND message. More details were written in the last but two paragraphs in chapter 4.2.

“When IPv6oA IWF sends Inverse Neighbor Discovery Message, it can
        change the Neighbor Solicitation Message from BNG to Inverse Neighbor
        Discovery Solicitation message or change the Inverse Neighbor
        Discovery Advertisements message from CPE to Neighbor Advertisements
        message since IND protocol is just the extension to the IPv6 Neighbor
        Discovery.”

Did this answer the question, or do you have other questions regarding the responsibilities of IWF?

Regards,
Will


> -----Original Message-----
> From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
> Jiexin Zhang
> Sent: Wednesday, July 25, 2012 9:41 AM
> To: wang.cui1@zte.com.cn
> Cc: v6ops@ietf.org
> Subject: Re: [v6ops] "RE: goals of draft-zhang-v6ops-ipv6oa-iwf-00.txt "
> 
> 2012/7/25, Jiexin Zhang <estrellazhang2012@gmail.com>:
> > Thanks for the comments from Miss Wang.  Actually,I think IWF means it
> can perform both layer2 and IP function. Therefore, IWF can be
> performed in a layer 2 node, such as an ATM switch, which works like
> the IPv4oA IWF in ATM switch usually.  And it can also be performed
> in a layer 3 node, BRAS as an example. In this draft, we just defined
> IWF is in a layer 2 node.
> >
> ~~JX
> >
> > 2012/7/24, wang.cui1@zte.com.cn <wang.cui1@zte.com.cn>:
> >> Hi,
> >>
> >> I have throughly read this draft and the discussions on the mailing list,
> >> the previous questions from fred and J.S help my understanding about this
> >> draft,
> >> and this solution seems more economical which just need updates the
> >> version of
> >> the ATM nodes than buying extra equipments to replace the located ATM
> >> nodes or ATM network;
> >>
> >> But here I have a comment:
> >>
> >>     1) You said the "Interworking Function" is a layer 2 node, but in
> >> section 4.2,what the IPv6oA IWF do seems like a
> >>         layer 3 node because this node has to deal with IP address. What
> >> do you think ?
> >>
> >> Thanks~
> >> Cui Wang
> >>
> >>
> >> --------------------------------------------------------
> >> ZTE Information Security Notice: The information contained in this mail
> >> (and
> >> any attachment transmitted herewith) is privileged and confidential and
> >> is
> >> intended for the exclusive use of the addressee(s).  If you are not an
> >> intended recipient, any disclosure, reproduction, distribution or other
> >> dissemination or use of the information contained is strictly prohibited.
> >> If you have received this mail in error, please delete it and notify us
> >> immediately.
> >>
> >>
> >
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops