Re: [v6ops] new draft: draft-ma-v6ops-ipv6-address-assignment
"Mukom Akong T." <mukom.tamon@gmail.com> Sat, 17 August 2013 18:38 UTC
Return-Path: <mukom.tamon@gmail.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 DA56A11E81EA for <v6ops@ietfa.amsl.com>; Sat, 17 Aug 2013 11:38:06 -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=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, NO_RELAYS=-0.001]
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 LvxV9c9lNLSY for <v6ops@ietfa.amsl.com>; Sat, 17 Aug 2013 11:38:06 -0700 (PDT)
Received: from mail-qa0-x234.google.com (mail-qa0-x234.google.com [IPv6:2607:f8b0:400d:c00::234]) by ietfa.amsl.com (Postfix) with ESMTP id D972C11E81E3 for <v6ops@ietf.org>; Sat, 17 Aug 2013 11:38:05 -0700 (PDT)
Received: by mail-qa0-f52.google.com with SMTP id bq6so1120196qab.11 for <v6ops@ietf.org>; Sat, 17 Aug 2013 11:38:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=kJMogBAE3Ap7TJlttGxtbN+ZjDOW6EXuF/ozAsU/DNc=; b=PBrVHE2tj41TDv+XMmmGR94akFWMvo4BzP/y4H81cxM4w6LjHMmqli5zvE6q3eNjP7 VvsD2kvpBjfU9rH0901nj9txyOcIAvSP8EF6OU6aIJdZhTVMgq7ijSRiomJFGgghsgdU gYoOvIYlVfBoSzikSQQI2d0Jjobhyktp+9jau1mEUckRXzd5LbnwFvV5Pk551o0PQsU7 mrP6LcB9qsitk/eoTNYvnoQkWEYJz5rFaIID6LVR9H/IHe2wJ6NbSO+MPw3MNw383EYp TmBAP6zSgg3EOK4vnPWQN/lIFidhQgBDv4bhgpfl2xWrrvEuEri8ZvXgSCW9UQUvFXe/ vGqQ==
X-Received: by 10.224.156.197 with SMTP id y5mr2399648qaw.83.1376764684272; Sat, 17 Aug 2013 11:38:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.49.47.82 with HTTP; Sat, 17 Aug 2013 11:37:24 -0700 (PDT)
In-Reply-To: <201308131245.r7DCj0k27831@ftpeng-update.cisco.com>
References: <201308131245.r7DCj0k27831@ftpeng-update.cisco.com>
From: "Mukom Akong T." <mukom.tamon@gmail.com>
Date: Sat, 17 Aug 2013 22:37:24 +0400
Message-ID: <CAHDzDLAb1zZgNb_KAzYAiPranMzrOQNWGYmA84pDD6ho8tORqQ@mail.gmail.com>
To: draft-ma-v6ops-ipv6-address-assignment@tools.ietf.org, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="089e01537592f20df904e4290165"
Subject: Re: [v6ops] new draft: draft-ma-v6ops-ipv6-address-assignment
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, 17 Aug 2013 18:38:07 -0000
Hello all, I am a total newbie to posting here so please forgive any lapses in protocol. I've got some comments In section 3 (2) it is mentioned "....MiFi should receive a /60 prefix for downstream interface, can address 2^4 hosts" I believe the author meant to say 2^4 subnets (each being of size /64). Same mistake is made for 3 (3) which should be On second thoughts, a typical MiFI (apart from the 3G or 4G wireless WAN interface) typically only has one subnet behind it. In this case I believe a single /64 (received through DHCPv6-PD) will suffice. In section 3 (4), while a broad recommendation of "one or more /48s" might serve as a default recommendation, I'd rather go with "A single /48 but it is highly recommended that proper address planning be done to estimate exactly how many /48s are required" ... or something similar. I'd rather also use the term "End site" rather than user so as to avoid confusion. 1 million users on a GGSN is not necessarily need 1 million /64s. In 4 (4) the authors says "Each CPE need a / 64 LAN interface address and a /56 WAN interface address,". I am curious, why a /56 on a WAN interface? Regards On Tue, Aug 13, 2013 at 4:45 PM, <fred@cisco.com> wrote: > > A new draft has been posted, at > http://tools.ietf.org/html/draft-ma-v6ops-ipv6-address-assignment. Please > take a look at it and comment. > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops > -- Mukom Akong T. http://about.me/perfexcellence | twitter: @perfexcellent ------------------------------------------------------------------------------------------------------------------------------------------ “When you work, you are the FLUTE through whose lungs the whispering of the hours turns to MUSIC" - Kahlil Gibran -------------------------------------------------------------------------------------------------------------------------------------------
- [v6ops] new draft: draft-ma-v6ops-ipv6-address-as… fred
- Re: [v6ops] new draft: draft-ma-v6ops-ipv6-addres… Arturo Servin
- Re: [v6ops] new draft: draft-ma-v6ops-ipv6-addres… Arturo Servin
- Re: [v6ops] new draft: draft-ma-v6ops-ipv6-addres… Arturo Servin
- Re: [v6ops] new draft: draft-ma-v6ops-ipv6-addres… Owen DeLong
- [v6ops] new draft: draft-ma-v6ops-ipv6-address-as… fred
- Re: [v6ops] new draft: draft-ma-v6ops-ipv6-addres… Mukom Akong T.