Re: IAB Response to Appeal from [...]

"JFC (Jefsey) Morfin" <jefsey@jefsey.com> Wed, 01 February 2006 04:47 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F49ts-0004Ge-NU; Tue, 31 Jan 2006 23:47:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F49tn-0004FH-PU for ietf@megatron.ietf.org; Tue, 31 Jan 2006 23:47:23 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA06534 for <ietf@ietf.org>; Tue, 31 Jan 2006 23:45:36 -0500 (EST)
Received: from montage.altserver.com ([63.247.74.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F4A4l-00056K-Lp for ietf@ietf.org; Tue, 31 Jan 2006 23:58:40 -0500
Received: from ver78-2-82-241-91-24.fbx.proxad.net ([82.241.91.24] helo=JFCM.afrac.org) by montage.altserver.com with esmtpa (Exim 4.52) id 1F49tI-0002Q6-VR; Tue, 31 Jan 2006 20:46:49 -0800
Message-Id: <6.2.3.4.2.20060201053803.06713c10@mail.jefsey.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4
Date: Wed, 01 Feb 2006 05:46:28 +0100
To: Frank Ellermann <nobody@xyzzy.claranet.de>, ietf@ietf.org
From: "JFC (Jefsey) Morfin" <jefsey@jefsey.com>
In-Reply-To: <43E02BFD.778E@xyzzy.claranet.de>
References: <43DFAC4B.1070309@thinkingcat.com> <6.2.3.4.2.20060201011759.06605eb0@mail.jefsey.com> <43E02BFD.778E@xyzzy.claranet.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"; x-avg-checked="avg-ok-3C527EA4"
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - montage.altserver.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - jefsey.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc:
Subject: Re: IAB Response to Appeal from [...]
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

Dear Frank,
RFC 3066 bis is now a local low interest issue, under IESG appeal, 
mainly for security considerations.
IRT your so called debate, I do not think that "leaving the things as 
they are" is an innovative solution. Now someone has to do the work.
jfc


At 04:33 01/02/2006, Frank Ellermann wrote:

>JFC (Jefsey) Morfin wrote:
>
> > I hope this list will soon be a IANA managed mailing list,
> > or that the IESG requires the WG-ltru to gives it a more
> > precise status through RFC 3066 bis (a debate I proposed
> > and I was denied).
>
>That's of course not the case, it was debated for quite some
>time in "the making of 30066bis":
>
><http://mid.gmane.org/42B0A3A6.7694@xyzzy.claranet.de>
><http://mid.gmane.org/42B32C25.1466@xyzzy.claranet.de>
>
>Just two examples grepping for "3934" in an LTRU archive.
>
> > I consider that Harald and I are both only trying to do our
> > best to clarify a complex issue to the benefit of the users
> > and of the IETF. I genuinely hope the IAB decision will help
> > us to openly discuss it, taking the necessary time.
>
>Whatever it takes.  I like a new IAB draft published recently:
><http://tools.ietf.org/id/draft-iab-idn-nextsteps-02>
>--
>Frank
>
>
>
>_______________________________________________
>Ietf mailing list
>Ietf@ietf.org
>https://www1.ietf.org/mailman/listinfo/ietf


_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf