IETF Logo Mail Archive

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

Ole Troan <otroan@employees.org> Wed, 20 September 2017 21:44 UTC

Return-Path: <otroan@employees.org>
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 6A7AE13422B for <v6ops@ietfa.amsl.com>; Wed, 20 Sep 2017 14:44:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001] 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 YGXhCPUpCNw6 for <v6ops@ietfa.amsl.com>; Wed, 20 Sep 2017 14:44:44 -0700 (PDT)
Received: from accordion.employees.org (accordion.employees.org [198.137.202.74]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 339D812421A for <v6ops@ietf.org>; Wed, 20 Sep 2017 14:44:44 -0700 (PDT)
Received: from h.hanazo.no (96.51-175-103.customer.lyse.net [51.175.103.96]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by accordion.employees.org (Postfix) with ESMTPSA id D05A02D5060; Wed, 20 Sep 2017 21:44:43 +0000 (UTC)
Received: from [IPv6:::1] (localhost [IPv6:::1]) by h.hanazo.no (Postfix) with ESMTP id B2F1110B8A61C; Wed, 20 Sep 2017 23:44:41 +0200 (CEST)
From: Ole Troan <otroan@employees.org>
Message-Id: <30557544-8312-4361-8CD4-E819E8C97814@employees.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_4961FD43-FD71-4729-A25C-86241DE1844A"; protocol="application/pgp-signature"; micalg="pgp-sha512"
Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\))
Date: Wed, 20 Sep 2017 23:44:41 +0200
In-Reply-To: <D5E8043B.86B21%lee@asgard.org>
Cc: jordi.palet@consulintel.es, v6ops@ietf.org
To: Lee Howard <Lee@asgard.org>
References: <D5E8043B.86B21%lee@asgard.org>
X-Mailer: Apple Mail (2.3273)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/zA99yjSvxnbaBn03P0gTn86pZyg>
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: Wed, 20 Sep 2017 21:44:45 -0000

>> RFC6877 (464XLAT) is an informational document.
>> ...
>> 
>> Can we even consider moving it to STD?
> 
> 
> I don’t think v6ops can promote it to Standard, or Standards Track. Our
> charter doesn’t explicitly say we’re not allowed to do standards work, but
> I would want to hear from our AD and check with 6man before promoting it.

6man doesn't do IPv4.

> Generally, the two tests are rough consensus and multiple interoperable
> implementations.

Ole

v2.23.0 | Report a Bug | By Email