IETF Logo Mail Archive

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

Alexandre Petrescu <alexandre.petrescu@gmail.com> Tue, 19 September 2017 19:37 UTC

Return-Path: <alexandre.petrescu@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 74C8B134389 for <v6ops@ietfa.amsl.com>; Tue, 19 Sep 2017 12:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.633
X-Spam-Level:
X-Spam-Status: No, score=-2.633 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665] autolearn=ham autolearn_force=no
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 Bal2XXnm3Fyf for <v6ops@ietfa.amsl.com>; Tue, 19 Sep 2017 12:37:43 -0700 (PDT)
Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E494134373 for <v6ops@ietf.org>; Tue, 19 Sep 2017 12:37:43 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id v8JJbeBq011134; Tue, 19 Sep 2017 21:37:40 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 8D42E20E79A; Tue, 19 Sep 2017 21:37:40 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 6A80720E30D; Tue, 19 Sep 2017 21:37:40 +0200 (CEST)
Received: from [132.166.84.160] ([132.166.84.160]) by muguet2.intra.cea.fr (8.15.2/8.15.2/CEAnet-Intranet-out-1.4) with ESMTP id v8JJbd3k021382; Tue, 19 Sep 2017 21:37:40 +0200
To: Ted Lemon <mellon@fugue.com>
Cc: v6ops@ietf.org
References: <C1017FAF-91C3-4CA3-89C2-B64FF5100E41@consulintel.es> <85d934b3-ae06-c0ea-3519-4069c8387f0a@gmail.com> <0CD21368-3E62-4CBA-9EC5-C02C7850FCE7@fugue.com>
From: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Message-ID: <6619c568-a43d-d78a-8953-896ed5156c65@gmail.com>
Date: Tue, 19 Sep 2017 21:37:39 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <0CD21368-3E62-4CBA-9EC5-C02C7850FCE7@fugue.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Language: fr
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/shJlCLz5IS0ORH3hoInLVFwApqE>
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: Tue, 19 Sep 2017 19:37:45 -0000


Le 19/09/2017 à 18:55, Ted Lemon a écrit :
> On Sep 19, 2017, at 12:23 PM, Alexandre Petrescu 
> <alexandre.petrescu@gmail.com <mailto:alexandre.petrescu@gmail.com>> wrote:
>> My little IoT IPv6 cellular device does not run 464xlat and neither 
>> IPv4.  If 464xlat becomes Stds Track does it mean that it MUST run 
>> 464xlat?  I would disagree with that.
> 
> Um, when does standards track ever mean this, Alex?

Right, and I agree with your XMPP comment.

But is 464xlat some software feature that only Android implements?  I 
did not see it on yocto.

>   The answer is 
> never.   What it means for a document to be standards track is that it 
> has IETF consensus as a standard,

consensus and?

Alex

  not that you are required to implement
> it.   Does your little IoT device implement XMPP?   That's a standard...
> 
> :)
>

v2.23.0 | Report a Bug | By Email