Re: [v6ops] new draft: draft-colitti-v6ops-host-addr-availability

Yury Shefer <shefys@gmail.com> Tue, 07 July 2015 05:57 UTC

Return-Path: <shefys@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7432A1A9006 for <v6ops@ietfa.amsl.com>; Mon, 6 Jul 2015 22:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 VP2S6p_tN7-Q for <v6ops@ietfa.amsl.com>; Mon, 6 Jul 2015 22:57:10 -0700 (PDT)
Received: from mail-ie0-x22e.google.com (mail-ie0-x22e.google.com [IPv6:2607:f8b0:4001:c03::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72E351A9004 for <v6ops@ietf.org>; Mon, 6 Jul 2015 22:57:10 -0700 (PDT)
Received: by iebmu5 with SMTP id mu5so127531582ieb.1 for <v6ops@ietf.org>; Mon, 06 Jul 2015 22:57:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rsMEI5KQmsdaH6+TcKgLrSC+v0/ae82vpIZ3cppDeLg=; b=hIx2l+wGSSjii04WZBN55I6tZPrQRcWthqnhtQB/TRo/0j/8wlvq1Ldwik6ZjLQDYg 3CSm93N02uZFHxztyYoE14DVRCXwvXP5KgIF2+n5foKd0rPd7V5nkQOtPNlhxnvT+hFC kZrzBWvaVl7sV1NWfRklrV1Lt5JZZREq3ElnTzo1mcXhpm/JbJ5gJQgVhOgRA6JeCG1L 4Un0viarS9bPg37Gfjt0HVJlZaVM1jCvDiJV9Ww7UT+S7ohiJkdtKwlrRSgreWrS1FxE GaJGEdVwja2vaNz6ICOyXGFGnmOTKrcjgG57VpEw/4LKsgxS/ctJeDUhvty0lvgOrzwU d5Iw==
MIME-Version: 1.0
X-Received: by 10.107.33.146 with SMTP id h140mr3752689ioh.1.1436248629872; Mon, 06 Jul 2015 22:57:09 -0700 (PDT)
Received: by 10.107.47.14 with HTTP; Mon, 6 Jul 2015 22:57:09 -0700 (PDT)
In-Reply-To: <201507061147.t66Bl1AE028312@irp-lnx1.cisco.com>
References: <201507061147.t66Bl1AE028312@irp-lnx1.cisco.com>
Date: Mon, 6 Jul 2015 22:57:09 -0700
Message-ID: <CAJ_FkAM7iHRqpbPjijXDDH21BdBbVnx2uo0Xg2v9HHQH-XEjHg@mail.gmail.com>
From: Yury Shefer <shefys@gmail.com>
To: fred@cisco.com
Content-Type: multipart/alternative; boundary=001a1140a3c0649795051a42b115
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/tKOiVTC8K7cKHmaRK5FLK3a3nHs>
Cc: v6ops@ietf.org, draft-colitti-v6ops-host-addr-availability@tools.ietf.org
Subject: Re: [v6ops] new draft: draft-colitti-v6ops-host-addr-availability
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 07 Jul 2015 05:57:12 -0000

Hello authors,

+1 and thanks for the draft!

Since you mentioned 3GPP, maybe it would be useful to mention Broadband
Forum (BBF) as well? BBF End-to-End Architecture technical reports
recommend the following:

1. TR-177 - IPv6 in the context of TR-101 (Nov 2010)
1.1 - Addressing recommendations - paragraph 4.2:
"From  a  routed  RG  perspective,  the  following  IPv6  addresses  may
be  provided  by  the  Service
Provider’s network:
- A /64 prefix for the WAN link GUA (optional, only done in the case of the
numbered WAN
model)
- A  delegated  prefix  for  use  within  the  home  network  (mandatory).
The  Broadband  Forum
suggests  a  size  for  the  delegated  prefix  of  at  least  a  /60  for
home  network  or  SOHO
environments,  with  a  recommended  prefix  length  of  /56.  The
delegated  prefix  may  be
extended to a /48 for larger organizations."

1.2 - IPv6 Prefix Delegation (DHCPv6-PD) - paragraph 4.2.1:
"A different prefix (with a maximum length of 64 bits, and a recommended
length of 56 bits) is
delegated per access loop".


2. TR-187 issue 2 - IPv6 for PPP Broadband Access (Feb 2013)
DHCPv6-PD is a mandatory requirement and it must be supported together with
DHCPv6 /128 WAN address assignment. Here is a few BNG requirements -
chapter 9.1:
"R-22    The BNG, when acting as DHCPv6 Server, MUST be able to assign a
single IPv6 /128
    address to the WAN interface of the RG when using DHCPv6 for address
assignment.
R-23    The  BNG MUST  be  able  to  support  DHCPv6-Prefix  Delegation,
RFC  3633 [16],
    to delegate a prefix to the RG."

On Mon, Jul 6, 2015 at 4:47 AM, <fred@cisco.com>; wrote:

> A new draft has been posted, at
> http://tools.ietf.org/html/draft-colitti-v6ops-host-addr-availability.
> Please take a look at it and comment.
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>



-- 
Best regards,
Yury.