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

Sheng Jiang <jiangsheng@huawei.com> Fri, 07 June 2013 02:42 UTC

Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E490511E80A4; Thu, 6 Jun 2013 19:42:55 -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 1rd5lVVIxNfk; Thu, 6 Jun 2013 19:42:50 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7295A21F8FCB; Thu, 6 Jun 2013 19:42:49 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id ATQ47496; Fri, 07 Jun 2013 02:42:47 +0000 (GMT)
Received: from LHREML404-HUB.china.huawei.com (10.201.5.218) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 7 Jun 2013 03:41:53 +0100
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.1.323.7; Fri, 7 Jun 2013 10:42:44 +0800
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.3]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.01.0323.007; Fri, 7 Jun 2013 10:42:40 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Owen DeLong <owen@delong.com>, Sheng Jiang <shengjiang@gmail.com>
Subject: RE: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Topic: [v6ops] Could IPv6 address be more than locator?//draft-jiang-v6ops-semantic-prefix-03
Thread-Index: AQHOYqIreYB7EHmXR0+A7JbK0DaUI5kof3AAgAEHRrA=
Date: Fri, 07 Jun 2013 02:42:39 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AC9D21B@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>
In-Reply-To: <CEC831E4-719F-40ED-A71D-56433B8CAB37@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: "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>, Ted Lemon <Ted.Lemon@nominum.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Jun 2013 02:42:56 -0000

>> Yes, this discussion has become far way from my original motivation of
>analysing semantic prefix mechanism. I am going to stop replying to the
>discuss regarding to the avaibilities of bits. In the future version, I will add the
>bits consumption as one of the pitfalls.
>>
>> 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.

Hi, Owen,

I take this as much more useful discussion than bit availability. I share your opinion that ISPs should be much more carefully as their will be consequences for downstream customers, comparing to enterprise. These will be included into the future version. :)

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.

Best regards,

Sheng


>Owen