Re: [v6ops] new draft: draft-shishio-v6ops-dpvt

Owen DeLong <owen@delong.com> Fri, 22 February 2013 09:31 UTC

Return-Path: <owen@delong.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 CA04321F8DFF for <v6ops@ietfa.amsl.com>; Fri, 22 Feb 2013 01:31:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.848
X-Spam-Level:
X-Spam-Status: No, score=-0.848 tagged_above=-999 required=5 tests=[AWL=0.551, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, J_CHICKENPOX_34=0.6]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5795TImFKhOa for <v6ops@ietfa.amsl.com>; Fri, 22 Feb 2013 01:30:56 -0800 (PST)
Received: from owen.delong.com (owen.delong.com [IPv6:2620:0:930::200:2]) by ietfa.amsl.com (Postfix) with ESMTP id 0B6B821F8DFD for <v6ops@ietf.org>; Fri, 22 Feb 2013 01:30:55 -0800 (PST)
Received: from dhcp50-95-223-141.hil-laxahhh.lax.wayport.net (dhcp50-95-223-141.hil-laxahhh.lax.wayport.net [50.95.223.141]) (authenticated bits=0) by owen.delong.com (8.14.2/8.14.1) with ESMTP id r1M9Rh1S032431 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Fri, 22 Feb 2013 01:27:44 -0800
X-DKIM: Sendmail DKIM Filter v2.8.3 owen.delong.com r1M9Rh1S032431
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=delong.com; s=mail; t=1361525265; bh=YHQmvpIRPd2iMnBqu9v4ddI/2SA=; h=Content-Type:Mime-Version:Subject:From:In-Reply-To:Date:Cc: Content-Transfer-Encoding:Message-Id:References:To; b=gOKQCp4hUW9odPCZ7OsmG0gSZX8BBnJKHFQNzVl7cf8JFA0qRtyM55cRuJ1SeqmVh UW/7vYF5Pln5yq80NL+QkRLjAij/b/QnWCzmHjsbQ/LgoeHtGOUJV4LcCmXlcNTBG+ qN8TDhRIh3hqQY+eaKioy6KAZ1W8EqSSgffhRih8=
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Owen DeLong <owen@delong.com>
In-Reply-To: <5126BA74.5080508@cisco.com>
Date: Fri, 22 Feb 2013 01:27:35 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B823D57C-F630-42D6-B4DF-BCFF60ACBB21@delong.com>
References: <201302181345.r1IDj0J04495@ftpeng-update.cisco.com> <1808340F7EC362469DDFFB112B37E2FCC6CFB3BC8A@SRVHKE02.rdm.cz> <51239D09.10305@cisco.com> <1808340F7EC362469DDFFB112B37E2FCC6CFB3BF8F@SRVHKE02.rdm.cz> <5126BA74.5080508@cisco.com>
To: Shishio Tsuchiya <shtsuchi@cisco.com>
X-Mailer: Apple Mail (2.1499)
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0rc1 (owen.delong.com [192.159.10.2]); Fri, 22 Feb 2013 01:27:45 -0800 (PST)
Cc: "v6ops@ietf.org" <v6ops@ietf.org>, "draft-shishio-v6ops-dpvt@tools.ietf.org" <draft-shishio-v6ops-dpvt@tools.ietf.org>
Subject: Re: [v6ops] new draft: draft-shishio-v6ops-dpvt
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, 22 Feb 2013 09:31:07 -0000

>> 
>> Let's take the DHCP-PD case, I assume that the IP resource planning goes hand in hand
>> with the number of subscribers the ISP is expecting to serve. The operator needs to decide
>> on the prefix-length to be delegated down to the subscriber and that's it, so they can
>> plan enough prefixes per access area. The operator does not need to know if/how I am using
>> my delegated prefix. They should be happy to give/sell me another prefix if needed.
>> 
>> Can you please clarify what's the benefit from Operator's point of view?
> 
> Yes,this is ideal planning.

We can agree to disagree on your use of the term "ideal" in this context.

> And RIR also has published guide line of IPv6 assignment for enduser.
> http://www.apnic.net/publications/media-library/documents/resource-guidelines/ipv6-guidelines

I'm not a particular fan of this document and have given APNIC feedback on it.

> RFC6177 was published as BCP.
> http://tools.ietf.org/html/rfc6177
> 

True. I wasn't participating actively in IETF at the time 6177 was written. IMHO, it is a travesty of v4 thinking being brought forward into IPv6 and should be considered harmful rather than BCP. It is neither common, nor best practice in my experience so far in the IPv6 world.

I will point out that no RIR provides any policy penalty for sticking with /48s and several of them actually provide benefits if you do so. Notably, ARIN policy is now based on the smallest prefix you assign to end users, so if you assign some end-users /64s and some /48s, you have to justify 65,536 /64s for each of your /48s assigned. OTOH, if you just give everyone a /48, you can just count up the number of /48s you assigned and each end user getting
a /48 is considered completely legitimate.

> Most of ISP used be provided /48 by dhcp-pd and when after RFC3177 obsoleted, they changed it to /56 and more shorter.

I believe you mean and longer. This is an unfortunate change that we can hopefully reverse before it becomes too entrenched and does too much harm.

> If the policy would be changed ,then operator should understand how delegated prefix are using.
> This is reason of the feature could provide to operators benefit ,I thought.
> 

There is no policy that prevents assigning /48s. Only a BCP that was poorly conceived.

Owen

> Thanks for your feedback.
> 
> Regards,
> -Shishio
> 
> 
> 
>> 
>>> So I thought these technologies need small oam tools.
>>> 
>>> -confirm only interface configuration from ISP side
>>> -confirm reachability not use end to end
>>> 
>>> I would appreciate any comment.
>>> 
>>> Regards,
>>> -Shishio
>> 
>> Cheers,
>> Ales
>> 
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops