Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03

Sheng Jiang <jiangsheng@huawei.com> Sat, 08 June 2013 01:58 UTC

Return-Path: <jiangsheng@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 411CA21F99FE; Fri, 7 Jun 2013 18:58:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 8OTpWlz0nUfA; Fri, 7 Jun 2013 18:58:13 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id F16E121F9A00; Fri, 7 Jun 2013 18:58:08 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ASF25813; Sat, 08 Jun 2013 01:58:06 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.1.323.7; Sat, 8 Jun 2013 02:57:05 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.1.323.7; Sat, 8 Jun 2013 02:58:03 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.01.0323.007; Sat, 8 Jun 2013 09:57:59 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Owen DeLong <owen@delong.com>
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOYqIreYB7EHmXR0+A7JbK0DaUI5kof3AAgAEHRrCAAMYyAIAAwFmQ
Date: Sat, 08 Jun 2013 01:57:58 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC9DC3C@nkgeml512-mbx.china.huawei.com>
References: <05DB0BDC-9B6D-4852-B878-5320ABC14D67@steffann.nl> <8D23D4052ABE7A4490E77B1A012B6307751C5A63@mbx-01.win.nominum.com> <021E64FECA7E5A4699562F4E6671648103DE44@XCH-PHX-503.sw.nos.boeing.com> <8D23D4052ABE7A4490E77B1A012B6307751C62A3@mbx-01.win.nominum.com> <CAL6Yo0+Bfn0URBTaZmEk_X1NCoBo3QBJNn3FZqG0pLkA+3FgkA@mail.gmail.com> <CEC831E4-719F-40ED-A71D-56433B8CAB37@delong.com> <5D36713D8A4E7348A7E10DF7437A4B923AC9D21B@nkgeml512-mbx.china.huawei.com> <6E92D779-70BD-488B-B81C-95681AA26F4C@delong.com>
In-Reply-To: <6E92D779-70BD-488B-B81C-95681AA26F4C@delong.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, "v6ops@ietf.org WG" <v6ops@ietf.org>, "<draft-jiang-v6ops-semantic-prefix@tools.ietf.org>" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org 6man-wg" <ipv6@ietf.org>
Subject: Re: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
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: Sat, 08 Jun 2013 01:58:18 -0000

>>>> By the way, ISPs are only one kind of network operators who are
>interesting
>>> in semantic prefix. Enterprise network operators are another group of
>>> network operators who can benefit from embedded semantics. And the
>>> enterprises do not have subscribers who potentially need extra bits.
>>>
>>> Your use of the word "benefit" here is questionable at best. It is an
>example of
>>> language that seems to encourage this use rather than evaluate it in an
>>> unbiased manner.
>>>
>>> "Enterprise operators are another group of network operators which may
>>> succumb to this nasty pitfall of embedded semantics" would be  an
>equally
>>> biased statement in the opposite direction.
>>>
>>> I suggest that neutral would require something more along the lines of:
>>>
>>> "Enterprise operators are another group of network operators which may
>>> choose to embed semantics in their address prefixes."
>>>
>>> Now, in terms of arguing the merits, there are significant differences
>between
>>> these two. In the case of an enterprise operator, their choice to embed
>>> semantics in the address has a limited scope of harm. It can only negatively
>>> impact said enterprise.
>>>
>>> In the case of an ISP, this can have significant consequences not only for
>the
>>> ISP, but also for their downstream customers.
>>
>> As a neutral analysis, it is fine to say there are benefits and pitfalls. All good
>things come with costs. I will make sure we document both sides in the draft.
>>
>
>Yes. However, when you talk about classes of users that may use a technology,
>there are multiple ways to express that potential use.
>
>"Those that may benefit…" is a positive way.
>"The world will end if…" is a negative way.
>"The following groups may use…" is neutral.
>
>When you are talking about how something can be implemented or the
>relative merits of doing so, then it is appropriate to discuss the benefits and
>pitfalls (ideally in as neutral a fashion as possible).

Hi, Owen,

Thanks for your neutral suggestion. I agree on this, and will try my best to use the neutral language in the future version. To clarify myself, I think "the X groups may get Y benefit with Z cost" is a neutral analysis.

Cheers,

Sheng

>I hope that clarifies what I was attempting to express above.
>
>Owen