IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Tue, 19 September 2017 16:55 UTC

Return-Path: <mellon@fugue.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 4486313307D for <v6ops@ietfa.amsl.com>; Tue, 19 Sep 2017 09:55:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 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_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.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 6Pj5xQDt1uS0 for <v6ops@ietfa.amsl.com>; Tue, 19 Sep 2017 09:55:54 -0700 (PDT)
Received: from mail-pf0-x234.google.com (mail-pf0-x234.google.com [IPv6:2607:f8b0:400e:c00::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C43E9124207 for <v6ops@ietf.org>; Tue, 19 Sep 2017 09:55:54 -0700 (PDT)
Received: by mail-pf0-x234.google.com with SMTP id b70so110057pfl.8 for <v6ops@ietf.org>; Tue, 19 Sep 2017 09:55:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=V6R7xaCyEZNK/B+rlS1+kHVAO8azN4K/wV5eGTEA5C8=; b=hoDtn3momnGvWGGw7sRgqU/a1FUUYWdKg/ZsFHa5ysglxIjg/Lyog+xYqJFPYSjs8k h4tQyZhkJ4CeugsB2edMDSdIjnpqHoiZYmwX8gCZZiajFzqfQvKvz6C0bNWxrrbjQuOY vqYrBV86l4+pnhGEY5/nZPr0nQPQHx7uUJZIf4f49ytyhwa9EM33FGlabS+p8aITlUXA z7uLLn88tPO7WWyNXdS4iimwu72LRYOJrc/vTxZgw1dQ1m7ntyCNo4X/ChhQ8zgNDPz9 hriJORQjsd3XhbKlOL16Ul/kpNu7Pr4i60Z6Tm4k6s1Ni1XW1oPs1tUqqanL3sVAgpoQ OycQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=V6R7xaCyEZNK/B+rlS1+kHVAO8azN4K/wV5eGTEA5C8=; b=gUC/Q8ErbS8q0hQzYm6O7wVfJmPhZBa7GuHm7HGiUyZvnbusuDYoWj+zO7q0dgS5n7 VXnyvP6tFUNxdU9cuXMIg9tjp2ObQ70OWQX7ZEfcUNhK96Hu+L+2PN8cp1babzAMltJP wmfaKodCFtIjnibNbja2SF27/4E9d8WlB2f9oa+AWY5BjJcqLqu8UooKOzbazooufWpi YPbFeOB/67btI15PDXCIHt21DZmACn5outvpnBpMz+123qdtcJ7ZYs4Aea9UOrIy//Ea n5r6vu/B4Zg2vCe9YpPNXiGwTJ5Z8U/0TyV35n/iSn4dUSG73mq8qN1FojJOomujREgJ ieNg==
X-Gm-Message-State: AHPjjUis3a6SKCsiNKmgQxbbp82oJamAhO0KZUCV9aIllhp6JiWktwkS EbPkd+fjmiwl0q1jDei6pH2nPQ==
X-Google-Smtp-Source: AOwi7QDPIGkbdk5FuGo3YzRzqsWnN+Kp9xjW1yB2JMfeu/01F83AVAP4Tc/nhtvCBgnnCmR153iFlg==
X-Received: by 10.98.159.137 with SMTP id v9mr1846120pfk.49.1505840154304; Tue, 19 Sep 2017 09:55:54 -0700 (PDT)
Received: from [10.1.60.111] (c-24-60-163-103.hsd1.ma.comcast.net. [24.60.163.103]) by smtp.gmail.com with ESMTPSA id z187sm5540983pfb.60.2017.09.19.09.55.53 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Sep 2017 09:55:53 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <0CD21368-3E62-4CBA-9EC5-C02C7850FCE7@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5EEA1300-DABA-42E5-9AC3-99599C6CAB06"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Tue, 19 Sep 2017 12:55:51 -0400
In-Reply-To: <85d934b3-ae06-c0ea-3519-4069c8387f0a@gmail.com>
Cc: v6ops@ietf.org
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
References: <C1017FAF-91C3-4CA3-89C2-B64FF5100E41@consulintel.es> <85d934b3-ae06-c0ea-3519-4069c8387f0a@gmail.com>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Da4xFDlrChCBATufhG-ED4_zfws>
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 16:55:56 -0000

On Sep 19, 2017, at 12:23 PM, Alexandre Petrescu <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?   The answer is never.   What it means for a document to be standards track is that it has IETF consensus as a standard, 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