IETF Logo Mail Archive

Re: [v6ops] reclassify 464XLAT as standard instead of info

JORDI PALET MARTINEZ <jordi.palet@consulintel.es> Thu, 21 September 2017 16:03 UTC

Return-Path: <prvs=14370a98a6=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 01C56134217 for <v6ops@ietfa.amsl.com>; Thu, 21 Sep 2017 09:03:25 -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 lEniHxZZzlFo for <v6ops@ietfa.amsl.com>; Thu, 21 Sep 2017 09:03:22 -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 D0FB1132125 for <v6ops@ietf.org>; Thu, 21 Sep 2017 09:03:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1506009799; x=1506614599; q=dns/txt; h=DomainKey-Signature: Received:User-Agent:Date:Subject:From:To:Message-ID:Thread-Topic: Mime-version:Content-type:Content-transfer-encoding:Reply-To; bh=5CtrJ9b0wvOVJ9Pbj26GmAQKmwCBPrjQhfsFQ8oOrX4=; b=qkg/D+93VL+be XKczDa2B4JhL7oVPvjm3eXyxoocfYb8qbhig9AfzR520b2JTxXNgDear6ua4U0dn vQdFIzOTEHIlRtYbNlxDIwv67Bck76zVlzwk0724sXRNzBB7SZIXV7qpZOcwFUsJ YRqxvoWuyr4EIp+Vuq+s/R3gBeg1pQ=
DomainKey-Signature: a=rsa-sha1; s=MDaemon; d=consulintel.es; c=simple; q=dns; h=from:message-id; b=IY63bE7etPkFbzxj7Tie491H8NPpUi62zEI9qTyEL2hepTRHGPN/BMPa6sbM fee/Z7Bt5WSCOxCbchVuJ3/d2FsPtFZ9YHDoeKDAEcWdRaDJXNnvgAADa TppYNRcvNk2xcuudyhczFpFH59Uj7OGsdi+i/SCx6fqWnxazyMWCzY=;
X-MDAV-Processed: mail.consulintel.es, Thu, 21 Sep 2017 18:03:19 +0200
X-Spam-Processed: mail.consulintel.es, Thu, 21 Sep 2017 18:03:16 +0200
Received: from [45.6.251.164] by mail.consulintel.es (MDaemon PRO v11.0.3) with ESMTP id md50005562332.msg for <v6ops@ietf.org>; Thu, 21 Sep 2017 18:03:15 +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:170921:md50005562332::UeVTCOSHJ72nhY5I:00000DKS
X-MDRemoteIP: 45.6.251.164
X-Return-Path: prvs=14370a98a6=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
X-MDaemon-Deliver-To: v6ops@ietf.org
User-Agent: Microsoft-MacOutlook/f.26.0.170902
Date: Thu, 21 Sep 2017 13:03:09 -0300
From: JORDI PALET MARTINEZ <jordi.palet@consulintel.es>
To: v6ops@ietf.org
Message-ID: <9AE0D6C9-56DC-4B52-8F29-C4B3991D0D1A@consulintel.es>
Thread-Topic: reclassify 464XLAT as standard instead of info
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/vX7TmN7B6rzLdAMgDecoDk71Rqw>
Subject: Re: [v6ops] reclassify 464XLAT as standard instead of info
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: Thu, 21 Sep 2017 16:03:25 -0000

And I can confirm it works, tested many times in different networks, many different devices.

Saludos,
Jordi
 

-----Mensaje original-----
De: v6ops <v6ops-bounces@ietf.org> en nombre de Ca By <cb.list6@gmail.com>
Responder a: <cb.list6@gmail.com>
Fecha: jueves, 21 de septiembre de 2017, 12:21
Para: Alexandre Petrescu <alexandre.petrescu@gmail.com>, Owen DeLong <owen@delong.com>
CC: <v6ops@ietf.org>
Asunto: Re: [v6ops] [*SPAM* Score/Req: 3.9/3.3] Re: [*SPAM* Score/Req: 3.9/3.3] Re: reclassify 464XLAT as standard instead of info

    
    On Thu, Sep 21, 2017 at 8:04 AM Alexandre Petrescu <alexandre.petrescu@gmail.com> wrote:
    
    
    Le 21/09/2017 à 16:49, Owen DeLong a écrit :
    [...]
    > CLAT and DHCP can co-exist on the same network.
    
    This is not shown anywhere.
    
    I tell you they dont, and they will not.
    
    Alex
    
    
    OpenWrt / LEDE supports both CLAT and dhcpv6-pd
    
    https://forum.openwrt.org/viewtopic.php?id=59528
    
    
    
    
    
    
    
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
    
    
    
    
    _______________________________________________
    v6ops mailing list
    v6ops@ietf.org
    https://www.ietf.org/mailman/listinfo/v6ops
    



**********************************************
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 exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.

v2.23.0 | Report a Bug | By Email