[Softwires] 答复: Review of draft-sun-softwire-yang-02

Qin Wu <bill.wu@huawei.com> Mon, 16 March 2015 02:54 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: softwires@ietfa.amsl.com
Delivered-To: softwires@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 445FB1A0BE8 for <softwires@ietfa.amsl.com>; Sun, 15 Mar 2015 19:54:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level:
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vuPxLc_qVAFI for <softwires@ietfa.amsl.com>; Sun, 15 Mar 2015 19:54:52 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C5E51A0AC8 for <softwires@ietf.org>; Sun, 15 Mar 2015 19:54:51 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BTR22174; Mon, 16 Mar 2015 02:54:50 +0000 (GMT)
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 16 Mar 2015 02:54:49 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.244]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Mon, 16 Mar 2015 10:54:45 +0800
From: Qin Wu <bill.wu@huawei.com>
To: Ian Farrer <ianfarrer@gmx.com>
Thread-Topic: [Softwires] Review of draft-sun-softwire-yang-02
Thread-Index: AQHQXJmkDQ/qp1WJBEiN/EMW+LGWxJ0YkEAAgAXd4YA=
Date: Mon, 16 Mar 2015 02:54:44 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA846F54FC@nkgeml501-mbs.china.huawei.com>
References: <B8F9A780D330094D99AF023C5877DABA846E1199@nkgeml501-mbs.china.huawei.com> <951513FB-D0C2-4E72-96DD-222F9CDB4B58@gmx.com>
In-Reply-To: <951513FB-D0C2-4E72-96DD-222F9CDB4B58@gmx.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.180]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA846F54FCnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/softwires/cN1SR3CdBTSETt6V5Ght5D9bUJ4>
Cc: "softwires@ietf.org" <softwires@ietf.org>
Subject: [Softwires] 答复: Review of draft-sun-softwire-yang-02
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/softwires/>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Mar 2015 02:54:57 -0000

发件人: Ian Farrer [mailto:ianfarrer@gmx.com]
发送时间: 2015年3月13日 1:13
收件人: Qin Wu
抄送: softwires@ietf.org
主题: Re: [Softwires] Review of draft-sun-softwire-yang-02

Hi Qin,

Thanks for your comments. Please see inline.

Cheers,
Ian

On 12 Mar 2015, at 08:53, Qin Wu <bill.wu@huawei.com<mailto:bill.wu@huawei.com>> wrote:

Dear all,
I have read this document and think the softwire yang model is needed for the configuration and management of Softwire BRs and CPEs.
A few comments below:
In section 3.2, why the binding-ipv6-addr and binding-ipv6-prefix are both contained in the binding-table?

[if] The intention here is to allow for the binding table to be specified in one of two ways, either with an explicit /128 or a /64 with the IID automatically constructed from the IPv4 address and port set.

Looking at the model again, the way that it is currently defined is wrong. Here’s an updated section of the model that should achieve the above:


   |     +--rw (binding-v6info)

   |     |  +—:(ipv6addr)

   |     |  |  +--rw binding-ipv6-addr    inet:ipv6-address

   |     |  +—:(ipv6pref)

   |     |     +--rw binding-ipv6-prefix  inet:ipv6-prefix

[Qin]: Based on the above clarification, I think binding-ipv6-addr and binding-ipv6-prefix can not coexist at the same time, both binding-ipv6-addr and binding-ipv6-prefix should be optional leaf or choice, right?

   |     +--rw (binding-v6info)?

   |     |  +—:(ipv6addr)

   |     |  |  +--rw binding-ipv6-addr?    inet:ipv6-address

   |     |  +—:(ipv6pref)

   |     |     +--rw binding-ipv6-prefix?  inet:ipv6-prefix