Re: RFC3484 destination address selection rule 2 is buggy
Alain Durand <alain_durand@cable.comcast.com> Thu, 13 March 2008 22:51 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 E717A28C2E8; Thu, 13 Mar 2008 15:51:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.373
X-Spam-Level:
X-Spam-Status: No, score=-98.373 tagged_above=-999 required=5 tests=[AWL=-0.003, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RCVD_NUMERIC_HELO=2.067, 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 yakOpj4qSvZr; Thu, 13 Mar 2008 15:51:42 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F339C3A688C; Thu, 13 Mar 2008 15:51:41 -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 CAF9D28C15D for <ipv6@core3.amsl.com>; Thu, 13 Mar 2008 15:51:40 -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 uVZi9xHICzhB for <ipv6@core3.amsl.com>; Thu, 13 Mar 2008 15:51:40 -0700 (PDT)
Received: from pacdcimo01.cable.comcast.com (PacdcIMO01.cable.comcast.com [24.40.8.145]) by core3.amsl.com (Postfix) with ESMTP id DB54A3A6C2D for <ipv6@ietf.org>; Thu, 13 Mar 2008 15:51:39 -0700 (PDT)
Received: from ([10.52.116.31]) by pacdcimo01.cable.comcast.com with ESMTP id KP-BXT38.14396906; Thu, 13 Mar 2008 18:49:09 -0400
Received: from PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) by PAOAKEXCSMTP02.cable.comcast.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 13 Mar 2008 18:49:09 -0400
Received: from 130.129.253.71 ([130.129.253.71]) by PACDCEXCMB06.cable.comcast.com ([24.40.15.22]) via Exchange Front-End Server webmail.comcast.com ([24.40.8.153]) with Microsoft Exchange Server HTTP-DAV ; Thu, 13 Mar 2008 22:49:09 +0000
User-Agent: Microsoft-Entourage/12.0.0.071130
Date: Thu, 13 Mar 2008 18:49:08 -0400
Subject: Re: RFC3484 destination address selection rule 2 is buggy
From: Alain Durand <alain_durand@cable.comcast.com>
To: Francis Dupont <Francis.Dupont@fdupont.fr>, Pekka Savola <pekkas@netcore.fi>
Message-ID: <C3FF27A4.CFF9%alain_durand@cable.comcast.com>
Thread-Topic: RFC3484 destination address selection rule 2 is buggy
Thread-Index: AciFW9UrnfB6jSj5RHKqHNDkezTHngAAJ0Nr
In-Reply-To: <200803132244.m2DMiBxE048560@givry.fdupont.fr>
Mime-version: 1.0
X-OriginalArrivalTime: 13 Mar 2008 22:49:09.0693 (UTC) FILETIME=[733D1ED0:01C8855C]
Cc: Iljitsch van Beijnum <iljitsch@muada.com>, ipv6@ietf.org
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
+1 On 3/13/08 6:44 PM, "Francis Dupont" <Francis.Dupont@fdupont.fr> 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. > > Francis.Dupont@fdupont.fr > > PS: I did this at the iterim meeting in Redmond, WA, in 2001... > (I also suggested to pick up DHCPv6 as the right way to perform > prefix delegation, a proposal which was strongly rejected at this time :-) > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@ietf.org > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
- RFC3484 destination address selection rule 2 is b… Pekka Savola
- Re: RFC3484 destination address selection rule 2 … Francis Dupont
- Re: RFC3484 destination address selection rule 2 … Alain Durand
- Re: RFC3484 destination address selection rule 2 … Rémi Denis-Courmont
- Re: RFC3484 destination address selection rule 2 … Pekka Savola
- Re: RFC3484 destination address selection rule 2 … Francis Dupont
- Re: RFC3484 destination address selection rule 2 … Mohacsi Janos
- Re: RFC3484 destination address selection rule 2 … Rémi Denis-Courmont
- Re: RFC3484 destination address selection rule 2 … Sebastien Roy
- Re: RFC3484 destination address selection rule 2 … Gabi Nakibly
- Re: RFC3484 destination address selection rule 2 … Sebastien Roy
- Re: RFC3484 destination address selection rule 2 … Fred Baker
- Re: RFC3484 destination address selection rule 2 … Sebastien Roy
- Re: RFC3484 destination address selection rule 2 … Gabi Nakibly
- Re: RFC3484 destination address selection rule 2 … Sebastien Roy
- Re: RFC3484 destination address selection rule 2 … Brian E Carpenter
- Re: RFC3484 destination address selection rule 2 … JINMEI Tatuya / 神明達哉
- Re: RFC3484 destination address selection rule 2 … JINMEI Tatuya / 神明達哉
- Re: RFC3484 destination address selection rule 2 … Pekka Savola
- RE: RFC3484 destination address selection rule 2 … Hemant Singh (shemant)
- Re: RFC3484 destination address selection rule 2 … Pekka Savola
- Re: RFC3484 destination address selection rule 2 … Fred Baker
- Re: RFC3484 destination address selection rule 2 … Bob Hinden
- RE: RFC3484 destination address selection rule 2 … Hemant Singh (shemant)
- Re: RFC3484 destination address selection rule 2 … Fred Baker
- Re: RFC3484 destination address selection rule 2 … Brian E Carpenter
- Re: RFC3484 destination address selection rule 2 … Bob Hinden
- Re: RFC3484 destination address selection rule 2 … Fred Baker