Re: [v6ops] question about draft-ietf-v6ops-unique-ipv6-prefix-per-host-06 (was draft-jjmb-v6ops-unique-ipv6-prefix-per-host)

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Mon, 03 July 2017 08:06 UTC

Return-Path: <prvs=1357fe33c6=jordi.palet@consulintel.es>
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 B79DF12EB4A for <v6ops@ietfa.amsl.com>; Mon, 3 Jul 2017 01:06:54 -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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=consulintel.es; domainkeys=pass (1024-bit key) header.from=jordi.palet@consulintel.es header.d=consulintel.es
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 lMKli-x3M16v for <v6ops@ietfa.amsl.com>; Mon, 3 Jul 2017 01:06:53 -0700 (PDT)
Received: from mail.consulintel.es (mail.consulintel.es [217.126.185.215]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02CFB126B7F for <v6ops@ietf.org>; Mon, 3 Jul 2017 01:06:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1499069211; x=1499674011; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: References:In-Reply-To:Mime-version:Content-type: Content-transfer-encoding:Reply-To; bh=C9+wqPMVsQ8X4ld0zts8zPRWW m286TVTpH4ZNXgLpZI=; b=YKWZ7yP3tZYbwRDJeGwaMecKwWunLzR11Cejf2qjg vxwWe9dXnmiFrtxulxIn55PcQYavRdr55BrZV7/AqI1qU8GviwJzbchjIqisigs+ Zn9AARNrA5GlVWqbz5upu78Cpr4TVucyRx7bvacJwUC9CCcWhZB9+b1SuYxs/KSH X8=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=gI3gXHIHfuYx2MsyISlK1NYq2GfOIjtPD6NZj7NDOCbuMJh0cJUWsIqH7Gr5 FBq9ZHArWVzEHkb9vIH/unADwUFrvmDD/ltBkKP2EHMpc95vJwpBA/gtz Tx1+bbZ+JKD77C3SjD9uVx0877EYKVYKZmqe5mhfCUsUDUuOwwI8lk=;
X-MDAV-Processed: mail.consulintel.es, Mon, 03 Jul 2017 10:06:51 +0200
X-Spam-Processed: mail.consulintel.es, Mon, 03 Jul 2017 10:06:50 +0200
Received: from [10.10.10.99] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005464041.msg for <v6ops@ietf.org>; Mon, 03 Jul 2017 10:06:50 +0200
X-MDOP-RefID: re=0.000,fgs=0 (_st=1 _vt=0 _iwf=0)
X-Authenticated-Sender: jordi.palet@consulintel.es
X-HashCash: 1:20:170703:md50005464041::ObW98kxpAInGtibf:00000MNJ
X-Return-Path: prvs=1357fe33c6=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/f.21.0.170409
Date: Mon, 03 Jul 2017 10:06:47 +0200
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>
Message-ID: <BF079711-4016-4C5A-A8D8-C082BBA6DDEC@consulintel.es>
Thread-Topic: [v6ops] question about draft-ietf-v6ops-unique-ipv6-prefix-per-host-06 (was draft-jjmb-v6ops-unique-ipv6-prefix-per-host)
References: <F0CF1BE8-52C8-4A0E-A35D-47814476DC1E@consulintel.es> <CAKD1Yr3E+FUAJSSehMbn1nDuKbqQB8+MywYzoUMYL2UR7dbbvQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr3E+FUAJSSehMbn1nDuKbqQB8+MywYzoUMYL2UR7dbbvQ@mail.gmail.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Reply-To: jordi.palet@consulintel.es
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/CLjV4YRzoaGpSquEtUCpFX5UVHU>
Subject: Re: [v6ops] question about draft-ietf-v6ops-unique-ipv6-prefix-per-host-06 (was draft-jjmb-v6ops-unique-ipv6-prefix-per-host)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 03 Jul 2017 08:06:55 -0000

I guess I’m not good describing what I want to say …

What I mean is that a host can be connected to multiple networks, and it may need to use a single prefix (from each network, not the same prefix in different ones).

Regards,
Jordi
 

-----Mensaje original-----
De: Lorenzo Colitti <lorenzo@google.com>
Responder a: <lorenzo@google.com>
Fecha: lunes, 3 de julio de 2017, 10:03
Para: Jordi Palet Martinez <jordi.palet@consulintel.es>
CC: "v6ops@ietf.org WG" <v6ops@ietf.org>
Asunto: Re: [v6ops] question about draft-ietf-v6ops-unique-ipv6-prefix-per-host-06 (was draft-jjmb-v6ops-unique-ipv6-prefix-per-host)

    On Mon, Jul 3, 2017 at 4:56 PM, JORDI PALET MARTINEZ <jordi.palet@consulintel.es> wrote:
    
    What I mean is that, reading the document a “new” reader may understand that only hosts with a single link may use this, and I think the original goal is that a unique IPv6 prefix can be used by a host and not just in one interface, but in any of the interfaces.
    
    
    
    I don't think using the same prefix on multiple interfaces is necessarily a goal The goal is to route an entire prefix to a host, such that different hosts are guaranteed to have different prefixes.
     
    
    Some possible text improvements for that:
    
    New p., at the end of the abstract:
    This approach may be used also in several interfaces of a single host.
    
    
    
    That is true of *any* IP addressing mechanism. All existing mechanisms for IP address assignment (SLAAC, manual configuration, DHCPv6, ...) can be used on multiple interfaces simultaneously.
    
    
    
    



**********************************************
IPv4 is over
Are you ready for the new Internet ?
http://www.consulintel.es
The IPv6 Company

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.