IETF Logo Mail Archive

Re: RFC3484 destination address selection rule 2 is buggy

Sebastien Roy <Sebastien.Roy@Sun.COM> Mon, 17 March 2008 16:16 UTC

Return-Path: <ipv6-bounces@ietf.org>
X-Original-To: ietfarch-ipv6-archive@core3.amsl.com
Delivered-To: ietfarch-ipv6-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 598D328C464; Mon, 17 Mar 2008 09:16:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.439
X-Spam-Level:
X-Spam-Status: No, score=-100.439 tagged_above=-999 required=5 tests=[AWL=-0.002, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SCOeCGoyAuPH; Mon, 17 Mar 2008 09:16:29 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B548428C429; Mon, 17 Mar 2008 09:16:28 -0700 (PDT)
X-Original-To: ipv6@core3.amsl.com
Delivered-To: ipv6@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 490903A683E for <ipv6@core3.amsl.com>; Mon, 17 Mar 2008 09:16:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-kHVhCYaNPe for <ipv6@core3.amsl.com>; Mon, 17 Mar 2008 09:16:27 -0700 (PDT)
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by core3.amsl.com (Postfix) with ESMTP id E625A28C405 for <ipv6@ietf.org>; Mon, 17 Mar 2008 09:16:04 -0700 (PDT)
Received: from fe-amer-09.sun.com ([192.18.109.79]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id m2HGDmRN000517 for <ipv6@ietf.org>; Mon, 17 Mar 2008 16:13:48 GMT
Received: from conversion-daemon.mail-amer.sun.com by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JXV00J01SZ6L100@mail-amer.sun.com> (original mail from Sebastien.Roy@Sun.COM) for ipv6@ietf.org; Mon, 17 Mar 2008 10:13:48 -0600 (MDT)
Received: from [192.168.1.3] ([71.174.191.147]) by mail-amer.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JXV009Y6UENDY50@mail-amer.sun.com>; Mon, 17 Mar 2008 10:13:36 -0600 (MDT)
Date: Mon, 17 Mar 2008 12:13:35 -0400
From: Sebastien Roy <Sebastien.Roy@Sun.COM>
Subject: Re: RFC3484 destination address selection rule 2 is buggy
In-reply-to: <200803132244.m2DMiBxE048560@givry.fdupont.fr>
To: Francis Dupont <Francis.Dupont@fdupont.fr>
Message-id: <47DE98AF.1010802@sun.com>
MIME-version: 1.0
References: <200803132244.m2DMiBxE048560@givry.fdupont.fr>
User-Agent: Thunderbird 2.0.0.9 (X11/20080128)
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org, Pekka Savola <pekkas@netcore.fi>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ipv6-bounces@ietf.org
Errors-To: ipv6-bounces@ietf.org

Francis Dupont wrote:
> Perhaps some of us didn't remember but:
>  - I predicted the RFC 3484 will be always at least a phase back from
>   what we want.
>  - I predicted too it would take a not reasonable amount of time to
>   get the document published or updated.
> Unfortunately both predictions were right so again I propose to make
> this a BCP and *not* a standard track document.

I'd agree with making it a BCP, or even of an Informational RFC.  It 
just doesn't fit the mold of a standards track document.  There are no 
two "interoperable" implementations, for example, as there is no 
interaction between two address selection algorithms on two sides of 
IPv6 communication.

-Seb
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

v2.23.0 | Report a Bug | By Email