IETF Logo Mail Archive

Re: [v6ops] Prep for v6ops IETF 84 agenda

Rémi Després <despres.remi@laposte.net> Thu, 28 June 2012 16:37 UTC

Return-Path: <despres.remi@laposte.net>
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 C726521F8516 for <v6ops@ietfa.amsl.com>; Thu, 28 Jun 2012 09:37:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.526
X-Spam-Level:
X-Spam-Status: No, score=-1.526 tagged_above=-999 required=5 tests=[AWL=-0.177, BAYES_00=-2.599, HELO_EQ_FR=0.35, J_CHICKENPOX_13=0.6, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xBJ43xDfGUSb for <v6ops@ietfa.amsl.com>; Thu, 28 Jun 2012 09:37:58 -0700 (PDT)
Received: from smtp23.services.sfr.fr (smtp23.services.sfr.fr [93.17.128.20]) by ietfa.amsl.com (Postfix) with ESMTP id 2EB1A21F850D for <v6ops@ietf.org>; Thu, 28 Jun 2012 09:37:57 -0700 (PDT)
Received: from filter.sfr.fr (localhost [127.0.0.1]) by msfrf2308.sfr.fr (SMTP Server) with ESMTP id 2D9A870000A3; Thu, 28 Jun 2012 18:37:57 +0200 (CEST)
Received: from [192.168.0.21] (per92-10-88-166-221-144.fbx.proxad.net [88.166.221.144]) by msfrf2308.sfr.fr (SMTP Server) with ESMTP id BF12570000F6; Thu, 28 Jun 2012 18:37:56 +0200 (CEST)
X-SFR-UUID: 20120628163756782.BF12570000F6@msfrf2308.sfr.fr
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="iso-8859-1"
From: Rémi Després <despres.remi@laposte.net>
X-Priority: 3
In-Reply-To: <00b401cd53b0$88115840$4001a8c0@gateway.2wire.net>
Date: Thu, 28 Jun 2012 18:37:56 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <152970C3-BBA5-4399-B913-4D86907C6742@laposte.net>
References: <017901cd538a$e9af8980$4001a8c0@gateway.2wire.net> <20120626235550kawashimam@mail.jp.nec.com> <00b401cd53b0$88115840$4001a8c0@gateway.2wire.net>
To: "t.petch" <ietfc@btconnect.com>
X-Mailer: Apple Mail (2.1084)
Cc: v6ops@ietf.org
Subject: Re: [v6ops] Prep for v6ops IETF 84 agenda
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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, 28 Jun 2012 16:37:58 -0000

Hi, Tom,

2012-06-26 à 17:28, t.petch:
...
> So I will read -04 and hope that everyone else who had comments will do
> likewise, after which, I hope that the chairs will initiate WGLC.

FYI, after previous comments I had made on previous versions, I commented -04 in /www.ietf.org/mail-archive/web/v6ops/current/msg13314.html, to say:


<< I have to confirm, no surprise, that I object to its BCP status because:
- it proposes more than just a combination of existing RFCs
- it has close relationship with subjects discussed in Softwires such as MAP and 4rd, without serious examination of this relationship.

OTOH, I also confirm that I would be pleased to support it if its status is changed back to Informational (its original status) because:
- It deals with a subject not covered by existing RFCs
- It is based on ideas that have been, at least in part, tested in the field.
- Issues raised in the WG (other than the RFC status) have been dealt with. >>

Regards,
RD

v2.23.0 | Report a Bug | By Email