[Mentoring-coordinators] Fw: [v6ops] Review: draft-ietf-v6ops-unique-ipv6-prefix-per-host

<nalini.elkins@insidethestack.com> Mon, 23 May 2016 15:38 UTC

Return-Path: <nalini.elkins@insidethestack.com>
X-Original-To: mentoring-coordinators@ietfa.amsl.com
Delivered-To: mentoring-coordinators@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7430C12B030 for <mentoring-coordinators@ietfa.amsl.com>; Mon, 23 May 2016 08:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=yahoo.com
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 BnjeT6J71aod for <mentoring-coordinators@ietfa.amsl.com>; Mon, 23 May 2016 08:38:16 -0700 (PDT)
Received: from nm34-vm2.bullet.mail.ne1.yahoo.com (nm34-vm2.bullet.mail.ne1.yahoo.com [98.138.229.82]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF4C912D999 for <mentoring-coordinators@ietf.org>; Mon, 23 May 2016 08:38:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s2048; t=1464017895; bh=+6DzFXBCfnDxLEk3gOnkQdXuuqfZ6J7RazccGn9jWV4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:From:Subject; b=uimD5Cvpe27c35EUNQTLjTqRLfgrNgBUeKW6f4/K7oHW0cCZl/K/aozHwAuF/2XTTaD+yTgRahSBc5cJhOuC7IIAEZyYGCeICZ52v8hLRyTw+EK7KeecZHLZDc0Kq7AbpjhlhZ7da5Bb6Yx+rftWpoX4rdDm1qrste3gMNrqTPlt1lDJwxD+aj0FcanrUc5MgNSo6kSdqini1/mtuPb8Lrh6irtlrCb5Y8RcnGYY/zyCZKDdKVQ82iVn6x77gsZrcNBHBnjGUijRxrAiGWruxYfqff6U+3VaWaiMnvbfnEuNdSEf3Hm/b8BEoxQB57ZB+9Ajcs4/QOxGQZDhgEjHfQ==
Received: from [127.0.0.1] by nm34.bullet.mail.ne1.yahoo.com with NNFMP; 23 May 2016 15:38:15 -0000
Received: from [98.138.100.102] by nm34.bullet.mail.ne1.yahoo.com with NNFMP; 23 May 2016 15:35:23 -0000
Received: from [98.138.87.3] by tm101.bullet.mail.ne1.yahoo.com with NNFMP; 23 May 2016 15:35:23 -0000
Received: from [127.0.0.1] by omp1003.mail.ne1.yahoo.com with NNFMP; 23 May 2016 15:35:23 -0000
X-Yahoo-Newman-Property: ymail-4
X-Yahoo-Newman-Id: 303726.4515.bm@omp1003.mail.ne1.yahoo.com
X-YMail-OSG: 0X_Ot1kVM1k56vf1dNU73l8KieKMreSqrg13eQb36RJLn67B2HE2ejsutLBt7qg 8uDzQpmJkPFghQFpSPG.oWvbmzm.kR0JeH.v26c70znXBLyiyFDMPQNiElh8gLXD31ngqewP_nIb EFvcOc87d.gvbUtgBdyMyUZwLBMcmTxR29S2LYp85WjIKzq52JrJaGfk6bsFxGSTAq_XKZqAA0wH CDAd4S0dnJWzuXn_nZLjYO9iy.ZA_utRVUBUUekGE3Pa78xU_ZnDTRVeQpJNQr_CRzu2C5paKrrL P1o6GYHt51_LIaNDW4DUxWS1TwXsiPC_6Ke_ijn8Actv8nkV_EfmHAjVJeZ7FzT6XDZFPlq8oP.l sK1KjYi_NCpSmnMu7FLGhoRBriD2GPL5wcIaQiBPm2L6ABE0mPaL5MRpXto_DVpaoOe1ERDmNHyf .lgTCF6aTiUCu6pk8JKjZPDxwng1O44sbXH6hn8rGFfLvlWlpJWvc7FVuH3sis4U6qjc111XZS.Y yVWTx46oTHSdXET3_NI.eT2K1L8DNAmm1lK0_ZH0wTQm7p4NVnes3vZwIkVS2DSxIb.cubGNPtw--
Received: from jws100263.mail.ne1.yahoo.com by sendmailws108.mail.ne1.yahoo.com; Mon, 23 May 2016 15:35:22 +0000; 1464017722.814
Date: Mon, 23 May 2016 15:35:22 +0000
From: nalini.elkins@insidethestack.com
To: "edwinsc@gmail.com" <edwinsc@gmail.com>, Ricardo Pelaez Negro <ricardo.pelaez@unibague.edu.co>
Message-ID: <766483200.872818.1464017722463.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <CAERpkxDjzb1Q5fFjA2bVTQoMG+CXGzAizGD_xtRaavS5bSnCUA@mail.gmail.com>
References: <CAERpkxDjzb1Q5fFjA2bVTQoMG+CXGzAizGD_xtRaavS5bSnCUA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_872817_831974363.1464017722454"
Archived-At: <http://mailarchive.ietf.org/arch/msg/mentoring-coordinators/uk1M7CFnFj8Vb6IHZkzX4JNdYLY>
Cc: "mentoring-coordinators@ietf.org" <mentoring-coordinators@ietf.org>
Subject: [Mentoring-coordinators] Fw: [v6ops] Review: draft-ietf-v6ops-unique-ipv6-prefix-per-host
X-BeenThere: mentoring-coordinators@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: nalini.elkins@insidethestack.com
List-Id: IETF Mentoring Coordinators <mentoring-coordinators.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mentoring-coordinators>, <mailto:mentoring-coordinators-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mentoring-coordinators/>
List-Post: <mailto:mentoring-coordinators@ietf.org>
List-Help: <mailto:mentoring-coordinators-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mentoring-coordinators>, <mailto:mentoring-coordinators-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 May 2016 15:38:18 -0000

Guys,
Excellent work! Thanks,
Nalini ElkinsInside Products, Inc.www.insidethestack.com(831) 659-8360

     
----- Forwarded Message -----
 From: Edwin Cordeiro <edwinsc@gmail.com>
 To: IPv6 Ops WG <v6ops@ietf.org> 
 Sent: Monday, May 23, 2016 8:24 AM
 Subject: [v6ops] Review: draft-ietf-v6ops-unique-ipv6-prefix-per-host
   
Hello all,
Below is the first review from the Internet Draft Review Team that I'm mentoring.
Document: draft-ietf-v6ops-unique-ipv6-prefix-per-host-00
Reviewers: Ricardo Pelaez-Negro, Edwin Cordeiro
Review Date: May 23th 2016
Summary: It is a good suggestion for a BCP, but it needs to add DHCP-PD to it
Comments: The draft proposes the use of an unique /64 for each user equipment connected to a WLAN gateway. The proposal highlights the benefit of such approach but fails to analyse possible consequences. I would support this draft to move forward if these issues are addressed.
Major Issues: - The DHCPv6-PD is mentioned for the first time only in section 4.3.1 and later at the "Future Work" session. From my understanding DHCPv6-PD is capable of implementing the network as desired in this BCP. Considering the intended status is BCP, I think that DCHPv6-PD should be added as valid implementation alternative.- The draft doesn't mention possible issues of giving one /64 for each UE, for example, a public WIFI with support for 512 users will need a /55 instead of a single /64.
Minor Issues and Nits: The document has some Nits problems as detailed in: https://tools.ietf.org/idnits?url=https://tools.ietf.org/id/draft-jjmb-v6ops-unique-ipv6-prefix-per-host-00.txt
Questions:- Should this document address the best way to logging the prefix assign to the UE/subscriber?- Assigning the same unique prefix if the UE/subscriber reconnect to the same AP, is something that should be considered or avoided?
Best regards,
Edwin Cordeiro
_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops