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

John Curran <jcurran@istaff.org> Fri, 07 June 2013 04:57 UTC

Return-Path: <jcurran@istaff.org>
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 7B4C921F8EB1; Thu, 6 Jun 2013 21:57:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 vHxVGRGfbi2j; Thu, 6 Jun 2013 21:57:10 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) by ietfa.amsl.com (Postfix) with ESMTP id B1DAF21F8EB2; Thu, 6 Jun 2013 21:57:07 -0700 (PDT)
Received: from pool-71-191-247-90.washdc.fios.verizon.net ([71.191.247.90] helo=diamond.istaff.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1Ukojb-0000ap-0x; Fri, 07 Jun 2013 04:57:07 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 71.191.247.90
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX18lEof+JM8JjxrVPMaWBmrI
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AC9D3A2@nkgeml512-mbx.china.huawei.com>
Date: Fri, 07 Jun 2013 00:57:05 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F9F072A-2047-4A53-B21E-6FF8F8C8FEDA@istaff.org>
References: <5D36713D8A4E7348A7E10DF7437A4B923AC98DAE@nkgeml512-mbx.china.huawei.com> <03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <8E492087-390E-4F8E-8078-1D0E63849243@delong.com> <EMEW3|f3c1b4957f182cbee8e02a76a09ead4dp4Y7Ye03tjc|ecs.soton.ac.uk|03680813-07D9-459B-A229-FA974C9A4B9E@ecs.soton.ac.uk> <CAKD1Yr0E5OUsphjhEaaMTjVarSGNdPEx6e1RyKDs5A=bkHGvBg@mail.gmail.com> <51A7A5B1.3050709@bogus.com> <5D36713D8A4E7348A7E10DF7437A4B923AC99B56@nkgeml512-mbx.china.huawei.com> <15AAD527-9221-4D59-BDC8-12CF3116FCE2@istaff.org> <5D36713D8A4E7348A7E10DF7437A4B923AC9D3A2@nkgeml512-mbx.china.huawei.com>
To: Sheng Jiang <jiangsheng@huawei.com>
X-Mailer: Apple Mail (2.1503)
Cc: "<v6ops@ietf.org>" <v6ops@ietf.org>, "draft-jiang-v6ops-semantic-prefix@tools.ietf.org" <draft-jiang-v6ops-semantic-prefix@tools.ietf.org>, "ipv6@ietf.org" <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: Fri, 07 Jun 2013 04:57:46 -0000

On Jun 6, 2013, at 11:44 PM, Sheng Jiang <jiangsheng@huawei.com> wrote:

> Hi, John,
> 
> Thanks for your message. Yes, I will add lower address utility rate as one of the major pitfalls. However, I don't want to make an absolute statement of "cannot". As a neutral analysis, it is better to just make observation, such as "there is risk that they may not". We do not want to influence the RIR policy either way, which would be quite controversial. It is better we do not touch this.

Sheng - 
 
  Yes, I see your point that "cannot get more addresses because they use 
  their block for semantic" would be considered an absolute directive. On 
  the other hand, we do want to be clear about the high possibility that 
  they will not be able to obtain additional address based on semantic use, 
  so a simple warning that incorporates both lower utility rate and the risk
  of being potentially unable to obtain more address should suffice.  Such 
  a statement in the draft would let the discussion continue focused on the
  technical aspects of semantic prefixes, provides a fair warning to anyone 
  adopting the technology, and yet keeps open the possibility of any outcome 
  from future RIR discussions of this technology.

Thanks!
/John

Disclaimers: My views alone. No semantics are encoded in my underlying 
             network packets (I already have enough work keeping useful 
             semantic meaning at the application layer... :-)