
From nobody Wed Oct  1 17:11:27 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 914791A8843; Wed,  1 Oct 2014 17:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 3DrAa0MFXI0M; Wed,  1 Oct 2014 17:11:23 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id F05281A8855; Wed,  1 Oct 2014 17:11:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-why64-06.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141002001121.22307.61553.idtracker@ietfa.amsl.com>
Date: Wed, 01 Oct 2014 17:11:21 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/aTtbES-FNu1pqTiAZ7iV5iIxWv0
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 02 Oct 2014 00:11:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Analysis of the 64-bit Boundary in IPv6 Addressing
        Authors         : Brian Carpenter
                          Tim Chown
                          Fernando Gont
                          Sheng Jiang
                          Alexandru Petrescu
                          Andrew Yourtchenko
	Filename        : draft-ietf-6man-why64-06.txt
	Pages           : 24
	Date            : 2014-10-01

Abstract:
   The IPv6 unicast addressing format includes a separation between the
   prefix used to route packets to a subnet and the interface identifier
   used to specify a given interface connected to that subnet.
   Currently the interface identifier is defined as 64 bits long for
   almost every case, leaving 64 bits for the subnet prefix.  This
   document describes the advantages of this fixed boundary and analyses
   the issues that would be involved in treating it as a variable
   boundary.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-why64/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-why64-06

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-why64-06


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Oct  1 17:14:29 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80F1E1A8843 for <ipv6@ietfa.amsl.com>; Wed,  1 Oct 2014 17:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 R5vCRVppYygq for <ipv6@ietfa.amsl.com>; Wed,  1 Oct 2014 17:14:25 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFCDC1A8845 for <ipv6@ietf.org>; Wed,  1 Oct 2014 17:14:25 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id p10so1085979pdj.1 for <ipv6@ietf.org>; Wed, 01 Oct 2014 17:14:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=k0wxeJ4RgfoKucLSYzvN0EUtrAmbZrumEE87bwhXB70=; b=aihDW6T3pEwad6X9wT/HqpVaR0Dhjx/i4pACZmkBAKXdfOzgnBoylg5yW+v1+l+NZ8 yR32iCQ43o4w2nKEhpO2+ZfrlKuVUEhY0lO4nFD5Lg9BvYjNt5beaw389OCwlfwhpQMe 6dBgNNQRxvzmKHfvq9we30JyEb677I7pmEpxipicEBWCZj4cPCq4R2mhW7oQ9aIo722q dpVCjfNl+Q6GHPtQr3KCWhvCtbP145BOfUfChcULlVMlVyz3nMUgxIft8r7+DC3MPHak p8t7iKVZvUbgKuMB1/VRe82K5A8Vq3YrKn9/KXPhRLOHXesLMVxPzAvxdVPZzoRJFCKG V5pA==
X-Received: by 10.68.136.136 with SMTP id qa8mr81986210pbb.68.1412208865577; Wed, 01 Oct 2014 17:14:25 -0700 (PDT)
Received: from [192.168.178.23] (89.199.69.111.dynamic.snap.net.nz. [111.69.199.89]) by mx.google.com with ESMTPSA id nv1sm2016016pbc.18.2014.10.01.17.14.23 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Oct 2014 17:14:24 -0700 (PDT)
Message-ID: <542C98E7.3060604@gmail.com>
Date: Thu, 02 Oct 2014 13:14:31 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-ietf-6man-why64-06.txt
References: <20141002001121.22307.61553.idtracker@ietfa.amsl.com>
In-Reply-To: <20141002001121.22307.61553.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/v_SiMXsJhyElNyXRDuQmotkEDcA
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 02 Oct 2014 00:14:27 -0000

Hi,

This update fixes two small careless phrasings about SLAAC that were
noticed during Last Call. Otherwise we received no negative comments.

   Brian


On 02/10/2014 13:11, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
> 
>         Title           : Analysis of the 64-bit Boundary in IPv6 Addressing
>         Authors         : Brian Carpenter
>                           Tim Chown
>                           Fernando Gont
>                           Sheng Jiang
>                           Alexandru Petrescu
>                           Andrew Yourtchenko
> 	Filename        : draft-ietf-6man-why64-06.txt
> 	Pages           : 24
> 	Date            : 2014-10-01
> 
> Abstract:
>    The IPv6 unicast addressing format includes a separation between the
>    prefix used to route packets to a subnet and the interface identifier
>    used to specify a given interface connected to that subnet.
>    Currently the interface identifier is defined as 64 bits long for
>    almost every case, leaving 64 bits for the subnet prefix.  This
>    document describes the advantages of this fixed boundary and analyses
>    the issues that would be involved in treating it as a variable
>    boundary.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-why64/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-why64-06
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-why64-06
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
> 


From nobody Fri Oct  3 00:24:18 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71CC71ACFB5 for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 00:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 qxrSAqTb655p for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 00:24:16 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AC3EA1ACFB2 for <ipv6@ietf.org>; Fri,  3 Oct 2014 00:24:15 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtMEANxOLlStJssW/2dsb2JhbABgg2FYgwLHbAqHTQKBHQF7hAMBAQEDAQEBARoGSwsFCwsYAgImAgInMAYTiDYIDahPlXABF4EsjkczB4J3NoEeBYYrkAWIOTuDBpEOg2U7L4JKAQEB
X-IronPort-AV: E=Sophos;i="5.04,645,1406592000"; d="scan'208";a="193371801"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 03 Oct 2014 07:24:14 +0000
Received: from dhcp-10-61-102-7.cisco.com (dhcp-10-61-102-7.cisco.com [10.61.102.7]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s937OBdd018421 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Oct 2014 07:24:13 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1988\))
Subject: Re: Adoption call of draft-halpern-6man-nd-pre-resolve-addr for 6MAN
From: Ole Troan <otroan@employees.org>
In-Reply-To: <407DEA57-2807-44A5-8936-45B20CDB87C0@employees.org>
Date: Fri, 3 Oct 2014 09:24:13 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <91F53E5E-71DB-4BF0-9081-40973F588D60@employees.org>
References: <407DEA57-2807-44A5-8936-45B20CDB87C0@employees.org>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1988)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/LEvJmPaQ5gJdxR21mtNZQuydq74
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 07:24:17 -0000

This end the adoption call for draft-halpern-6man-nd-pre-resolve-addr.
The chairs conclusion is that there is consensus in the working group to =
adopt this document.

Authors, please resubmit this draft as =
draft-ietf-6man-nd-pre-resolve-addr

Best regards,
Ole

> On 24 Sep 2014, at 9:24 , Ole Troan <otroan@employees.org> wrote:
>=20
> All,
>=20
> The authors have requested an adoption call for this document as an =
informational document.
>=20
> Please provide a view with reasons as to whether the WG should adopt =
this or not.
>=20
> This message starts a one week 6MAN Working Group call on adopting:
>=20
> 	Title           : Triggering ND Address Resolution on Receiving =
DAD-NS
> 	Author(s)    : I. Chen, J. Halpern
> 	Filename    : draft-halpern-6man-nd-pre-resolve-addr-00
> 	Pages        : 7
> 	Date          : 2014-01-10
>=20
> http://tools.ietf.org/html/draft-halpern-6man-nd-pre-resolve-addr-00
>=20
> The call ends on October 1st, 2014.
>=20
> Regards,
>=20
> Bob Hinden & Ole Tr=C3=B8an
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri Oct  3 00:28:08 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A32B1ACFCD for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 00:28:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 i2rDbgEfLWOT for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 00:28:05 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 405E11ACFB2 for <ipv6@ietf.org>; Fri,  3 Oct 2014 00:28:04 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtEEANxOLlStJssW/2dsb2JhbABgg2FYgwLHbAqHTYEfAXuEBQYBARoGSws1AiYCKTYTiD4NqE+VcAEXgSyOeoJ+NoEeBYYrkAWIOTuDBpEOg2U7L4JKAQEB
X-IronPort-AV: E=Sophos;i="5.04,645,1406592000"; d="scan'208";a="193375130"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 03 Oct 2014 07:28:03 +0000
Received: from dhcp-10-61-102-7.cisco.com (dhcp-10-61-102-7.cisco.com [10.61.102.7]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s937S2G3008034 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Oct 2014 07:28:02 GMT
From: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
Date: Fri, 3 Oct 2014 09:28:04 +0200
Message-Id: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1988\))
X-Mailer: Apple Mail (2.1988)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/GUflSFClQaF9pnyC_QT1JB9yFnw
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 07:28:06 -0000

All,

The authors have requested an adoption call for this document as a =
standards track document.

Please provide a view with reasons as to whether the WG should adopt =
this or not.

This message starts a one week 6MAN Working Group call on adopting:

	Title           : IPv6 Prefix Length Recommendation for =
Forwarding
	Author(s)    : M. Boucadair, A. Petrescu
	Filename    : draft-boucadair-6man-prefix-routing-reco-02
	Pages        : 4
	Date          : 2014-09-24

http://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02

The call ends on October 10th, 2014.

Regards,

Bob Hinden & Ole Tr=C3=B8an


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


From nobody Fri Oct  3 00:31:09 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F4371ACFD4 for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 00:31:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 f_B7lKjPxFCy for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 00:31:07 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A02B41A0143 for <ipv6@ietf.org>; Fri,  3 Oct 2014 00:31:06 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAEAMJPLlStJssW/2dsb2JhbABg012DIYEfAXuEJx00C4E+iFG+TAEXj0QRAVCEUgEEnmmDQY0Pg3+DZTuBPoE7AQEB
X-IronPort-AV: E=Sophos;i="5.04,645,1406592000"; d="scan'208";a="193345881"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 03 Oct 2014 07:31:06 +0000
Received: from dhcp-10-61-102-7.cisco.com (dhcp-10-61-102-7.cisco.com [10.61.102.7]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s937V45g014419 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 3 Oct 2014 07:31:04 GMT
From: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: 6man IETF 91 Call for agenda items
Date: Fri, 3 Oct 2014 09:31:06 +0200
Message-Id: <A2A2E2B8-D1DD-4EA3-A73E-885262303DFF@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1988\))
X-Mailer: Apple Mail (2.1988)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/xHyX9MOKbftpd8wK6w8bfTlb9X4
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 07:31:08 -0000

We have asked for a two and a half hour slot in Honolulu for the 6MAN =
working group.

If you have a draft you would like to discuss, please send your request =
for agenda time to the 6man chairs.
Please include in the request, the title and file name of the draft, the =
speakers name (and email),
and how much time you need.

We will prioritise drafts that are working group items and drafts that =
have been actively discussed on the list.

We expect at least half the presentation time to be used for open =
discussion,
please plan your presentation accordingly.

New drafts not discussed on the mailing list prior to the meeting,
or drafts that do not appear to have support from the working group are =
unlikely to get time at the meeting.

Please have agenda items to us by 2014-10-27 and also note the draft =
deadline for IETF91:
2014-10-27 (Monday): Internet Draft submission cut-off (for all drafts, =
including -00) by UTC 23:59

Regards,

Bob & Ole


From nobody Fri Oct  3 01:07:45 2014
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF2301A014C for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 01:07:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level: 
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 rmVyqMSjLk_v for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 01:07:38 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A8A31ACFF0 for <ipv6@ietf.org>; Fri,  3 Oct 2014 01:07:38 -0700 (PDT)
Received: by mail-ig0-f174.google.com with SMTP id l13so1183299iga.7 for <ipv6@ietf.org>; Fri, 03 Oct 2014 01:07:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=P75f9N/P1Un/VgAJ/crbYzA/LAnTIboeZ7U1eSY79Io=; b=R066Ld/LQHKz1+Z/GYTEFOh2dXsqbAt7UgOSCmPFf1qIpMKcyoDMMo7Qz1w+X5rRiJ za6zufDOD4NrP8IaEL4S/EbEQlpPxR3Rl2z4JTWTjS3s4w68loIqpw/4a+KkwDEs6AIc 9m2rpRLOc/nlbKkFbxfwTU7f3J+0vj5gmR371vDJNILw28SFLE2/WmdQ4DpXEpfF/Ayd ZtO/U1igUNvntG8Zc6XvzgQc5oqACC59bAzP+To6UCA8J/TbQSkbgjHjp8PaJ+HruVwl gjWN53k9TfkDwnY6JVYIdTvW4d7WVRP9gzgC/54nWdf+5nI/hzmDywglHTvLYYeeLZH7 fB5w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=P75f9N/P1Un/VgAJ/crbYzA/LAnTIboeZ7U1eSY79Io=; b=csedTwwvH4gRlypp0KOFuM/uHMlCJRl0iK3FRA7Fk03ZI9BYmGpM82a7SCtcGM1k1w egEuzN+KYJM1MA2iiUAr0leQtu10g3T6StZKA2XtBHenuV90fq4ahtFAdIBaj4s7qN9A utp/tDyCdPSiRwCjzeRmlSks+P8J22M9HBbBdhtd6y5xnHnX5XAP8tcjniJMpLUfN5Zj 9n6r/FCMDjYFnh2d27zY3/Eic1jsk7WY8kCAeEHFzAjGUfgRFOjrvV48BPcR5ibAbP9S TITcMrXYj5ZputUQFHT1ebzqtsZiK6RdKG/p2VXJXv7Mbr/etv6DPC722QwV70bAiP/H 1Oag==
X-Gm-Message-State: ALoCoQkGx+K9cuB2jucuc5VTfKg/ofX8iMOBpfSurcwAeUguHcfIsD76iuW9pj3I27k82rpNs/Fv
X-Received: by 10.42.236.19 with SMTP id ki19mr11138386icb.18.1412323657629; Fri, 03 Oct 2014 01:07:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.24.144 with HTTP; Fri, 3 Oct 2014 01:07:17 -0700 (PDT)
In-Reply-To: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 3 Oct 2014 17:07:17 +0900
Message-ID: <CAKD1Yr1_dpscgwcJF42Ov2g8AQRpXG1_gcw+P=tj3EGmvDRwPg@mail.gmail.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=20cf302446adebf1110504803910
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/CSFkI6B8Q78w7MLN_E7pGUOltwc
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 08:07:41 -0000

--20cf302446adebf1110504803910
Content-Type: text/plain; charset=UTF-8

On Fri, Oct 3, 2014 at 4:28 PM, Ole Troan <otroan@employees.org> wrote:

> Please provide a view with reasons as to whether the WG should adopt this
> or not.
>

Why does this belong in 6man? There are no protocol changes. Looks like it
should be in v6ops instead.

--20cf302446adebf1110504803910
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Oct 3, 2014 at 4:28 PM, Ole Troan <span dir=3D"ltr">&lt;<a href=3D"mail=
to:otroan@employees.org" target=3D"_blank">otroan@employees.org</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">Please provide a view with rea=
sons as to whether the WG should adopt this or not.<br></blockquote><div><b=
r></div><div>Why does this belong in 6man? There are no protocol changes. L=
ooks like it should be in v6ops instead.=C2=A0</div></div></div></div>

--20cf302446adebf1110504803910--


From nobody Fri Oct  3 03:57:35 2014
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1C921A028B for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 03:57:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.3
X-Spam-Level: 
X-Spam-Status: No, score=-1.3 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 ygrUG4QXdzcV for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 03:57:31 -0700 (PDT)
Received: from bastion.ch.unfix.org (bastion.ch.unfix.org [46.20.246.101]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 621311AD034 for <ipv6@ietf.org>; Fri,  3 Oct 2014 03:57:30 -0700 (PDT)
Received: from kami.ch.unfix.org (173-10-186-209-BusName-washingtonDC.hfc.comcastbusiness.net [173.10.186.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jeroen) by bastion.ch.unfix.org (Postfix) with ESMTPSA id BD0A110069CE3; Fri,  3 Oct 2014 10:57:25 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=massar.ch; s=DKIM2009; t=1412333846; bh=BHMWm1TYPiL7oWhteTo0SZ1HxqbQP3qnB7kesx9CzCI=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=u+b+HJEZMynGvOR6eatzaD21KyVLE26wAqmctgBksyySIYaBi4TC545xWBfuokqo/ iJBjglDy+BPSS8hNym/Sgi5AXokD5hsBSkFQCIaoavhyk78ldlaehOWDL8htD2jhhZ aOj1W5MaBas/yHY2MtvNG8lxGC06NbPuUL9ZNZwZC4VRITOMROzhxtdxui44TzpJgz OLBszSlCv8ThBEGcHr2H2AxNPe3FU3+q3/K98vnTJ6yCmIsdMmdNtgR8hy/sYX8shT M8JG7s43iMFEyKNOspAtE5SgI774HNhf9DP98E1iEG15rj9fgMSClLm1hPckBRfs3O q0055MM36Y2Yw==
Message-ID: <542E8110.5050906@massar.ch>
Date: Fri, 03 Oct 2014 06:57:20 -0400
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com>
In-Reply-To: <542E20C3.1060404@gmail.com>
X-Forwarded-Message-Id: <542E20C3.1060404@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/TF0URs5qMWsL8unyVyfc5dzsGBc
Cc: Ole Troan <ot@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 10:57:34 -0000

As some .gov agency is reminding us[1], it might be time to finally lay
6to4 to rest by making it historic.

Can we revive:
 http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05

and finally make it into a BCP, marking 6to4 historic.

That way, we can also get operators to wind down on 2002::/16 relays and
give a clear signal that folks really should have native in 2014.

Greets,
 Jeroen

[1] www.azdes.gov = 2002::cf6c:8846

-------- Forwarded Message --------
Subject: Re: 6to4 in Internet aaaa records
Date: Fri, 03 Oct 2014 17:06:27 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
CC: Jeroen Massar <jeroen@massar.ch>, IPv6 operators forum
<ipv6-ops@lists.cluenet.de>

[..]
>> and of course also:
>>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>>  (though that technically expired).

3 years ago that seemed premature. With recent progress in real IPv6,
I'm wondering whether it isn't time to revive it. If so it should be
changed to be a BCP that says "Don't do this" and also makes
the proposed standard drafts Historic.

But we do hear persistently that there are happy hobbyist and peer to peer
users of 6to4. Using it offer web service for the Arizona Department of
Economic Security is so wrong, though.


From nobody Fri Oct  3 04:55:41 2014
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7756D1A030A for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 04:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 WB9sHdeDT0hy for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 04:55:35 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 235341A0309 for <ipv6@ietf.org>; Fri,  3 Oct 2014 04:55:35 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id E076D880ED for <ipv6@ietf.org>; Fri,  3 Oct 2014 04:55:34 -0700 (PDT)
Received: from clemson.local (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id A81C313681D5 for <ipv6@ietf.org>; Fri,  3 Oct 2014 04:55:34 -0700 (PDT)
Message-ID: <542E8EB6.6050302@innovationslab.net>
Date: Fri, 03 Oct 2014 07:55:34 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch>
In-Reply-To: <542E8110.5050906@massar.ch>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="UvtUbp1kNiCtGhQrHihS77NsvN6Gq9e1h"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/hLef_N2TdmhZg4osRHOQ0lsn9Zo
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 11:55:39 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--UvtUbp1kNiCtGhQrHihS77NsvN6Gq9e1h
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

As a process point, we do not need a draft to move an RFC to Historic.
Please review this IESG statement:

http://trac.tools.ietf.org/group/iesg/trac/wiki/DesignatingAsHistoric

Regards,
Brian

On 10/3/14 6:57 AM, Jeroen Massar wrote:
> As some .gov agency is reminding us[1], it might be time to finally lay=

> 6to4 to rest by making it historic.
>=20
> Can we revive:
>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>=20
> and finally make it into a BCP, marking 6to4 historic.
>=20
> That way, we can also get operators to wind down on 2002::/16 relays an=
d
> give a clear signal that folks really should have native in 2014.
>=20
> Greets,
>  Jeroen
>=20
> [1] www.azdes.gov =3D 2002::cf6c:8846
>=20
> -------- Forwarded Message --------
> Subject: Re: 6to4 in Internet aaaa records
> Date: Fri, 03 Oct 2014 17:06:27 +1300
> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> CC: Jeroen Massar <jeroen@massar.ch>, IPv6 operators forum
> <ipv6-ops@lists.cluenet.de>
>=20
> [..]
>>> and of course also:
>>>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>>>  (though that technically expired).
>=20
> 3 years ago that seemed premature. With recent progress in real IPv6,
> I'm wondering whether it isn't time to revive it. If so it should be
> changed to be a BCP that says "Don't do this" and also makes
> the proposed standard drafts Historic.
>=20
> But we do hear persistently that there are happy hobbyist and peer to p=
eer
> users of 6to4. Using it offer web service for the Arizona Department of=

> Economic Security is so wrong, though.
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20


--UvtUbp1kNiCtGhQrHihS77NsvN6Gq9e1h
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJULo63AAoJEBOZRqCi7goqYU0IAJMdF8iogJPaBE9WKQCvXQLZ
hQAMqsUvJsDJ6CW7DlP4bumY9rZ2FiEuIXTsAVj6ioT4Fq/bzJDpcoIW+SPMwOlo
stxJcbcAbRTgYM51QAboU+LCqrG/vAWXp3KQAf8qJnoVFnG2kSGsEQx3OSOfRyhv
q3m0fdbukGLjQM5rgjqB5gQ/9r0Q2zkViWjPXqjAXh34kv5BrM+SfDS4S4lQLact
I+mr6hkTH/zA7N3+ilSeNs2w/MxzrZl2P/dLXktuDvVSoTFY9AtM9VWqagQEh0eN
K9NXoOGuDfuG6CguLqHbdSyDqsFCsw77apRA8sLNVy8B0XUztCHP5oYavs+99aU=
=ZUTY
-----END PGP SIGNATURE-----

--UvtUbp1kNiCtGhQrHihS77NsvN6Gq9e1h--


From nobody Fri Oct  3 05:33:17 2014
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 42C601A036E for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 05:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 QKfUqGtK7F5i for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 05:33:14 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 344B71A034D for <ipv6@ietf.org>; Fri,  3 Oct 2014 05:33:14 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s93CXBFd021379 for <ipv6@ietf.org>; Fri, 3 Oct 2014 14:33:11 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5E68520701B for <ipv6@ietf.org>; Fri,  3 Oct 2014 14:34:08 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 4D3AE206FE6 for <ipv6@ietf.org>; Fri,  3 Oct 2014 14:34:08 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s93CWqD9006292 for <ipv6@ietf.org>; Fri, 3 Oct 2014 14:33:10 +0200
Message-ID: <542E9774.60300@gmail.com>
Date: Fri, 03 Oct 2014 14:32:52 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <CAKD1Yr1_dpscgwcJF42Ov2g8AQRpXG1_gcw+P=tj3EGmvDRwPg@mail.gmail.com>
In-Reply-To: <CAKD1Yr1_dpscgwcJF42Ov2g8AQRpXG1_gcw+P=tj3EGmvDRwPg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/2H5s-E0EIskwQ_7oP_oA_yv8QZk
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 12:33:16 -0000

Le 03/10/2014 10:07, Lorenzo Colitti a écrit :
> On Fri, Oct 3, 2014 at 4:28 PM, Ole Troan <otroan@employees.org
> <mailto:otroan@employees.org>> wrote:
>
>     Please provide a view with reasons as to whether the WG should adopt
>     this or not.
>
>
> Why does this belong in 6man? There are no protocol changes. Looks like
> it should be in v6ops instead.

In a sense yes - there is no protocol change, because the idea of 
matching on arbitrary prefix lengths is rather an algorithm rather than 
a protocol to be operated;  like what MD5 is to IPsec.

I suppose it could be seen in v6ops as well, provided deployers care 
about it.  Or not.

Alex

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



From nobody Fri Oct  3 06:02:48 2014
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D0B41A066C for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 06:02:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 gQ0UCSwn_9h3 for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 06:02:44 -0700 (PDT)
Received: from bastion.ch.unfix.org (bastion.ch.unfix.org [46.20.246.101]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F1331A0AF1 for <ipv6@ietf.org>; Fri,  3 Oct 2014 06:02:44 -0700 (PDT)
Received: from kami.ch.unfix.org (173-10-186-209-BusName-washingtonDC.hfc.comcastbusiness.net [173.10.186.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jeroen) by bastion.ch.unfix.org (Postfix) with ESMTPSA id 8835210069CE6; Fri,  3 Oct 2014 13:02:40 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=massar.ch; s=DKIM2009; t=1412341362; bh=dTwwDbT9Dh8caKAFFgbm/j7UmrGBefGul8lz/Y4xnvw=; h=Date:From:To:Subject:References:In-Reply-To; b=tQrqYGu1hmHmOARjlTpSOFl1PpC/avB70+bvuB4BrKLH3nhDjOgP40HV7Lv5DMgCA wnla1EntjlU0y2iv5xG0CVzhxaiqliP8dq/A2WId0Og+BhTdxrgJKuZvJq8z9ZdJLw zkrud4fXJ8r2n6bLGICsHDaig8e/+1kBM7wIcvoNjvjBT0MdR0tQLKv9awq9LpAb50 igJ4Lp91kL5xMS1AK4WeMVbxLK5u7VWdR35aFgzxy9ZAbPgReMSsJR9adAtHNBrtIS MxGfedbThKcQ4aIMGPCS1DKm+OeC0HGSZgEMK5NElPLtneeuv6VewrNZpMnIHfO7is g6DrO2zKUnZdw==
Message-ID: <542E9E6C.90205@massar.ch>
Date: Fri, 03 Oct 2014 09:02:36 -0400
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Brian Haberman <brian@innovationslab.net>, ipv6@ietf.org
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542E8EB6.6050302@innovationslab.net>
In-Reply-To: <542E8EB6.6050302@innovationslab.net>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/o74VTqFo4A7-ic7WhPulkh5Tcvk
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 13:02:47 -0000

On 2014-10-03 07:55, Brian Haberman wrote:
> As a process point, we do not need a draft to move an RFC to Historic.
> Please review this IESG statement:
> 
> http://trac.tools.ietf.org/group/iesg/trac/wiki/DesignatingAsHistoric

Yes, but it is good to have a background reason for historical purposes.

The draft from back then has more than a few:

>>>> and of course also:
>>>>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>>>>  (though that technically expired).

Greets,
 Jeroen



From nobody Fri Oct  3 06:06:12 2014
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 446411A040B for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 06:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 ligmcZkgbFZs for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 06:06:07 -0700 (PDT)
Received: from bastion.ch.unfix.org (bastion.ch.unfix.org [46.20.246.101]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB0291A03AA for <ipv6@ietf.org>; Fri,  3 Oct 2014 06:06:06 -0700 (PDT)
Received: from kami.ch.unfix.org (173-10-186-209-BusName-washingtonDC.hfc.comcastbusiness.net [173.10.186.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jeroen) by bastion.ch.unfix.org (Postfix) with ESMTPSA id 3E48110069CE6; Fri,  3 Oct 2014 13:06:03 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=massar.ch; s=DKIM2009; t=1412341563; bh=tn8BIvLH8IaWWAbg14aGCyEGvrAc9GDvMlRUU+X2UuQ=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=gwBkCjLN56QQwtfsynw5DUQS4bMPIwrcLrbE1bN0xX76V5gm+pF7fN3cLWJUsFuS8 eB8MsSRL/91+Xh6CJej5vGj4pI8mZNF05wmcQvEsfSgTHeoiVaq2Um/sJjUMzgJJ6j pLm93C7QDNJScsnsi1Zozsn8USg3WEy2568GpsEAhL2o6IqRrmVI8ZC9ourkJEPzE6 bzpThNcLXEAER2BbOnK7VHpFwJETjAPP8n0Rsd0UknZpG5ZPGwNnIKnSz0r/VnIIRr uskpCH+KtXLB2kwz+OCY4cZzk7srMrdc6fvvGaGenHK1cOg0VIonk2HOIpbkt+T/VN CoMm3O35jVYSA==
Message-ID: <542E9F38.7050000@massar.ch>
Date: Fri, 03 Oct 2014 09:06:00 -0400
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Erik Kline <ek@google.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <CAAedzxqxtV7UK4MNUoDLbEogFH3TVUpWy+rRX_uvsOLJ3oergw@mail.gmail.com>
In-Reply-To: <CAAedzxqxtV7UK4MNUoDLbEogFH3TVUpWy+rRX_uvsOLJ3oergw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/Nk777Cz1uBNaqWAqc-e9CGOCLVI
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 13:06:09 -0000

On 2014-10-03 07:05, Erik Kline wrote:
> One concern I remember from one of the most vocal opponents at that time
> was that deprecation might cause code to get deleted from codebases

Why would that be bad?

Code that is not used and could possibly provide a path to some kind of
exploit/abuse/unknown use is good to disappear.

One of the many things that the LibreSSL folks are doing to OpenSSL.

> or at the very least bitrot (with various patches rejected sited IETF
> deprecation).

The only acceptable patch is in those cases a patch that
removes/deprecates the support.

> I believe this person either had or knew of one or more
> private uses of 6to4 that would therefore likely suffer.

"Private" means "local", thus do not require anything on the rest of the
Internet. Also it means that they can set up 6in4 based tunnels or use
ISATAP.

Unless that "person" provides a lot more details and reasoning, does it
matter?

Greets,
 Jeroen



From nobody Fri Oct  3 06:08:56 2014
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DB8CC1A040B for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 06:08:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 uAhKR3q2qZHC for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 06:08:51 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2971B1A03AA for <ipv6@ietf.org>; Fri,  3 Oct 2014 06:08:51 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 0A0D5880E1; Fri,  3 Oct 2014 06:08:51 -0700 (PDT)
Received: from clemson.local (clairseach.fuaim.com [206.197.161.141]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 90C4513681DB; Fri,  3 Oct 2014 06:08:50 -0700 (PDT)
Message-ID: <542E9FDB.3050607@innovationslab.net>
Date: Fri, 03 Oct 2014 09:08:43 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Jeroen Massar <jeroen@massar.ch>, ipv6@ietf.org
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542E8EB6.6050302@innovationslab.net> <542E9E6C.90205@massar.ch>
In-Reply-To: <542E9E6C.90205@massar.ch>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="0euLnPA5vaCAcbjiLkiFw3tH0sLaSBwGo"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/YM2fBHhBkaIMwTk83dw8kH0iG-k
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 13:08:53 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--0euLnPA5vaCAcbjiLkiFw3tH0sLaSBwGo
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Jeroen,

On 10/3/14 9:02 AM, Jeroen Massar wrote:
> On 2014-10-03 07:55, Brian Haberman wrote:
>> As a process point, we do not need a draft to move an RFC to Historic.=

>> Please review this IESG statement:
>>
>> http://trac.tools.ietf.org/group/iesg/trac/wiki/DesignatingAsHistoric
>=20
> Yes, but it is good to have a background reason for historical purposes=
=2E

Sure.  And that is what the status-change documents do.  They are not as
verbose as another RFC, but that is usually a good thing.

Take a look at some examples...

https://datatracker.ietf.org/doc/rfc-status-changes/

>=20
> The draft from back then has more than a few:
>=20
>>>>> and of course also:
>>>>>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05

Yeah, the content of section 3 of that draft can very easily be put in a
status-change document for historical purposes.

Regards,
Brian



--0euLnPA5vaCAcbjiLkiFw3tH0sLaSBwGo
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJULp/hAAoJEBOZRqCi7goqp/QH/j4K4mXwgGYrr7v6kVh2EtMR
AvzKXPXxZmXAwMUT7AM1uEBoLYQ4LRYLGfkjlRqe1ZpKDp6GsvC+HR57f6OQvAeU
DKvAssohPQSN7a1jUkOSvVc6mDtihF74+QHgWEVTZ8RVE11mqIkztMSW0YgaDftv
wZ7G1TW4tKjvCY8CFJ0pBXBUw7mEy1n2XY3uS1IVZlcZ6y00L7LJaGQAXk3ExQ9z
dynha4sVFFgs8Q+5X8pSoudtIa2klcB1km6v7GSG6IpB+fsh+oj9K7p95CjSZOas
qozBalHyQMB28YxNeIWbpO9I+IBIPcNO/rvEZ6SRSi2AkwtUhhiUOud8OeenqwQ=
=JTz2
-----END PGP SIGNATURE-----

--0euLnPA5vaCAcbjiLkiFw3tH0sLaSBwGo--


From nobody Fri Oct  3 06:13:42 2014
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38C401AD03D for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 04:05:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level: 
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 FP4aWPUgeslB for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 04:05:22 -0700 (PDT)
Received: from mail-qg0-x231.google.com (mail-qg0-x231.google.com [IPv6:2607:f8b0:400d:c04::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E84721AD038 for <ipv6@ietf.org>; Fri,  3 Oct 2014 04:05:21 -0700 (PDT)
Received: by mail-qg0-f49.google.com with SMTP id a108so737796qge.8 for <ipv6@ietf.org>; Fri, 03 Oct 2014 04:05:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=pjWLu3hbiErZIoUzpUmsU2tRQq9Gqaqm7g+u+0W0RyQ=; b=PstsKJPQFkX+EXnpcO6Gv6CP6Ca4qMlhlaBHVRhmtw62K4kxsSQQuuGpcUeIL0pLcB /v0Oao3Ayf84QnDoJyzCpTcZa+exeKWkLh3vgrbVdAf8X5gpUxx8TlabhvMw1OYJTwcU ULJ1EFIymOYxz4Y8VlN95gMWvOCxsDYIWjBQcgTfb8WQS6jWfGiytpiaFEUA3DXD1TQ0 7xz4+NKJk4PiBi6JrksD24aa2uLi/+3LHXta3GjhJZowLAD/28jdX8nZlYeauDp8yXCp I9EOLT3laOO/nsEj12D2/jgrznRhCFKBM2gTcfBoHR6UUKsJPEAwEbpLsq5S1P0eYXPI Md5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=pjWLu3hbiErZIoUzpUmsU2tRQq9Gqaqm7g+u+0W0RyQ=; b=N/8qbudLr/C4shEXWBTlNwa0dJoae9MRqCtXFuagAzEtnOKtvX6FLeQQHFE93VQIYF dPo346FHbNTxKUq/3Xx8cvIsFCx0/AbLGtvOZd4WJmlO15s+BnS16XilJG/2S8qH1nzO bV5DlHMb7fOYp1LWux5GGq4kI5nIpXPbJwIR7naQFwoRg6o9Abt3DGKTHP2VjxZVNoNb mPn0OetYZUHrS63ps6IiRa0WH4zUshu2/pm4ToRG19sC61KSzN4xtHk+YJWWYt4heNql pVo81a5/rgRwMbF9Y0YGxRXjyTn7+L2DuHjCtuG/ff16qJ0jBCgpmFt2QyuCNgpT3SOT ruQQ==
X-Gm-Message-State: ALoCoQkPZDRM9EgsYFjFT1rk8u/n7PNqBvKpjaFeaZV+MSb8TOgl1wjZQunuCVef9Bj1P7Llza1B
X-Received: by 10.140.37.9 with SMTP id q9mr4326473qgq.40.1412334321126; Fri, 03 Oct 2014 04:05:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.80.65 with HTTP; Fri, 3 Oct 2014 04:05:01 -0700 (PDT)
In-Reply-To: <542E8110.5050906@massar.ch>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch>
From: Erik Kline <ek@google.com>
Date: Fri, 3 Oct 2014 20:05:01 +0900
Message-ID: <CAAedzxqxtV7UK4MNUoDLbEogFH3TVUpWy+rRX_uvsOLJ3oergw@mail.gmail.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
To: Jeroen Massar <jeroen@massar.ch>
Content-Type: multipart/alternative; boundary=001a11c1358a83ee53050482b537
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/u5_p_adR21zT9QUmhfZOJC0QyKQ
X-Mailman-Approved-At: Fri, 03 Oct 2014 06:13:40 -0700
Cc: Ole Troan <ot@cisco.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 11:05:24 -0000

--001a11c1358a83ee53050482b537
Content-Type: text/plain; charset=UTF-8

One concern I remember from one of the most vocal opponents at that time
was that deprecation might cause code to get deleted from codebases, or at
the very least bitrot (with various patches rejected sited IETF
deprecation).  I believe this person either had or knew of one or more
private uses of 6to4 that would therefore likely suffer.

I was in favor of deprecation at that time, but I could understand the
point being made.

On Fri, Oct 3, 2014 at 7:57 PM, Jeroen Massar <jeroen@massar.ch> wrote:

> As some .gov agency is reminding us[1], it might be time to finally lay
> 6to4 to rest by making it historic.
>
> Can we revive:
>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>
> and finally make it into a BCP, marking 6to4 historic.
>
> That way, we can also get operators to wind down on 2002::/16 relays and
> give a clear signal that folks really should have native in 2014.
>
> Greets,
>  Jeroen
>
> [1] www.azdes.gov = 2002::cf6c:8846
>
> -------- Forwarded Message --------
> Subject: Re: 6to4 in Internet aaaa records
> Date: Fri, 03 Oct 2014 17:06:27 +1300
> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> CC: Jeroen Massar <jeroen@massar.ch>, IPv6 operators forum
> <ipv6-ops@lists.cluenet.de>
>
> [..]
> >> and of course also:
> >>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
> >>  (though that technically expired).
>
> 3 years ago that seemed premature. With recent progress in real IPv6,
> I'm wondering whether it isn't time to revive it. If so it should be
> changed to be a BCP that says "Don't do this" and also makes
> the proposed standard drafts Historic.
>
> But we do hear persistently that there are happy hobbyist and peer to peer
> users of 6to4. Using it offer web service for the Arizona Department of
> Economic Security is so wrong, though.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--001a11c1358a83ee53050482b537
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">One concern I remember from one of the most vocal opponent=
s at that time was that deprecation might cause code to get deleted from co=
debases, or at the very least bitrot (with various patches rejected sited I=
ETF deprecation).=C2=A0 I believe this person either had or knew of one or =
more private uses of 6to4 that would therefore likely suffer.<div><br></div=
><div>I was in favor of deprecation at that time, but I could understand th=
e point being made.</div></div><div class=3D"gmail_extra"><br><div class=3D=
"gmail_quote">On Fri, Oct 3, 2014 at 7:57 PM, Jeroen Massar <span dir=3D"lt=
r">&lt;<a href=3D"mailto:jeroen@massar.ch" target=3D"_blank">jeroen@massar.=
ch</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">As some .gov age=
ncy is reminding us[1], it might be time to finally lay<br>
6to4 to rest by making it historic.<br>
<br>
Can we revive:<br>
=C2=A0<a href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-histor=
ic-05" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-v6ops-6to4-t=
o-historic-05</a><br>
<br>
and finally make it into a BCP, marking 6to4 historic.<br>
<br>
That way, we can also get operators to wind down on 2002::/16 relays and<br=
>
give a clear signal that folks really should have native in 2014.<br>
<br>
Greets,<br>
=C2=A0Jeroen<br>
<br>
[1] <a href=3D"http://www.azdes.gov" target=3D"_blank">www.azdes.gov</a> =
=3D 2002::cf6c:8846<br>
<br>
-------- Forwarded Message --------<br>
Subject: Re: 6to4 in Internet aaaa records<br>
Date: Fri, 03 Oct 2014 17:06:27 +1300<br>
From: Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">=
brian.e.carpenter@gmail.com</a>&gt;<br>
CC: Jeroen Massar &lt;<a href=3D"mailto:jeroen@massar.ch">jeroen@massar.ch<=
/a>&gt;, IPv6 operators forum<br>
&lt;<a href=3D"mailto:ipv6-ops@lists.cluenet.de">ipv6-ops@lists.cluenet.de<=
/a>&gt;<br>
<br>
[..]<br>
&gt;&gt; and of course also:<br>
&gt;&gt;=C2=A0 <a href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-6to4-=
to-historic-05" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-v6o=
ps-6to4-to-historic-05</a><br>
&gt;&gt;=C2=A0 (though that technically expired).<br>
<br>
3 years ago that seemed premature. With recent progress in real IPv6,<br>
I&#39;m wondering whether it isn&#39;t time to revive it. If so it should b=
e<br>
changed to be a BCP that says &quot;Don&#39;t do this&quot; and also makes<=
br>
the proposed standard drafts Historic.<br>
<br>
But we do hear persistently that there are happy hobbyist and peer to peer<=
br>
users of 6to4. Using it offer web service for the Arizona Department of<br>
Economic Security is so wrong, though.<br>
<br>
--------------------------------------------------------------------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
--------------------------------------------------------------------<br>
</blockquote></div><br></div>

--001a11c1358a83ee53050482b537--


From nobody Fri Oct  3 06:23:58 2014
Return-Path: <alejandroacostaalamo@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A32D61A1A29 for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 06:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 slgn1e4xaIMQ for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 06:23:55 -0700 (PDT)
Received: from mail-qa0-x22d.google.com (mail-qa0-x22d.google.com [IPv6:2607:f8b0:400d:c00::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A72E71A1A16 for <ipv6@ietf.org>; Fri,  3 Oct 2014 06:23:55 -0700 (PDT)
Received: by mail-qa0-f45.google.com with SMTP id s7so820404qap.32 for <ipv6@ietf.org>; Fri, 03 Oct 2014 06:23:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=z3uZCvupDBVFdtqH0PtjwAQicmPZpTluMega8gv4twU=; b=RlQVZIjmqgGe/5eB82eniBaG8JqZoqgdLtCj6gyXYpJPSNYtnFm5Pc1kOm0wBRI/vm 70x/WaBbvtEkHICLBu3p//I1Pwh+psb/yEFkxeWdqr4AxydITWlW/oIbqWgQwqy5L2Wu utNXlwYSQ7vLeov9HgSXTOTEy6Re8MIQSHJkhApkM2SUd06UjYOGgGE6EbtWXPZ30Wq9 YiRpqJ7jZl4puy+tKbRw1ouEkWbbiwHlkp9do95Q0YGn455PMhwmuXNBNEGUMDd4J+ge yRueEMcU0WwNrC0gVEZauflDLELm4pMSGX8Zi+eiucZ3HkZGAVbfmkcWQVmoN7NLMONp t8FQ==
X-Received: by 10.140.22.199 with SMTP id 65mr5540091qgn.20.1412342634889; Fri, 03 Oct 2014 06:23:54 -0700 (PDT)
Received: from [172.17.50.187] ([186.2.177.4]) by mx.google.com with ESMTPSA id w8sm4776848qap.32.2014.10.03.06.23.53 for <ipv6@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 03 Oct 2014 06:23:54 -0700 (PDT)
Message-ID: <542EA35C.2080606@gmail.com>
Date: Fri, 03 Oct 2014 08:53:40 -0430
From: Alejandro Acosta <alejandroacostaalamo@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch>
In-Reply-To: <542E8110.5050906@massar.ch>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/eBS53rHGdW7qBDVdH3MLfT8511A
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 13:23:57 -0000

Hi List,
  The first time I read about this idea I did not pay attention but now
I would like to say that I agree with this.
  The reason I support this idea is that for many many years a lot of
transition mechanisms have been created generating several doubts to
service providers. Deprecating 6to4 will give direct and indirect
reasons to service providers to move to native IPv6.
 
Best regards,

Alejandro,


El 10/3/2014 a las #4, Jeroen Massar escribió:
> As some .gov agency is reminding us[1], it might be time to finally lay
> 6to4 to rest by making it historic.
>
> Can we revive:
>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>
> and finally make it into a BCP, marking 6to4 historic.
>
> That way, we can also get operators to wind down on 2002::/16 relays and
> give a clear signal that folks really should have native in 2014.
>
> Greets,
>  Jeroen
>
> [1] www.azdes.gov = 2002::cf6c:8846
>
> -------- Forwarded Message --------
> Subject: Re: 6to4 in Internet aaaa records
> Date: Fri, 03 Oct 2014 17:06:27 +1300
> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> CC: Jeroen Massar <jeroen@massar.ch>, IPv6 operators forum
> <ipv6-ops@lists.cluenet.de>
>
> [..]
>>> and of course also:
>>>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>>>  (though that technically expired).
> 3 years ago that seemed premature. With recent progress in real IPv6,
> I'm wondering whether it isn't time to revive it. If so it should be
> changed to be a BCP that says "Don't do this" and also makes
> the proposed standard drafts Historic.
>
> But we do hear persistently that there are happy hobbyist and peer to peer
> users of 6to4. Using it offer web service for the Arizona Department of
> Economic Security is so wrong, though.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri Oct  3 07:05:11 2014
Return-Path: <karsten_thomann@linfre.de>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF5AC1A1BBD for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 07:05:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.338
X-Spam-Level: 
X-Spam-Status: No, score=-2.338 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.786, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 36GjCDFKw7nc for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 07:05:05 -0700 (PDT)
Received: from linfre.de (linfre.de [83.151.26.85]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACE741A1AFF for <ipv6@ietf.org>; Fri,  3 Oct 2014 07:05:04 -0700 (PDT)
Received: from e7240.linfre (85.16.193.132) by linfreserv.linfre (Axigen) with (AES256-SHA encrypted) ESMTPSA id 058E01; Fri, 3 Oct 2014 16:04:52 +0200
From: Karsten Thomann <karsten_thomann@linfre.de>
To: ipv6@ietf.org
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
Date: Fri, 03 Oct 2014 16:04:52 +0200
Message-ID: <1545352.1EIA0Soipj@e7240.linfre>
User-Agent: KMail/4.14 (Linux/3.16.2-48.gdcee397-desktop; KDE/4.14.0; x86_64; ; )
In-Reply-To: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
X-AXIGEN-DK-Result: No records
DomainKey-Status: no signature
X-AxigenSpam-Level: 6
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/lnVVH0cXGSdFEbHE-8VoAaCQ7l8
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 14:05:09 -0000

Regardless of the discussion if this should be a 6man or v6ops document=
, I=20
don't think it needs an extra document to recommend that the routers sh=
ould be=20
able to route every prefix length, if the routing is not working for ev=
ery=20
prefix length the implementation is in a way broken that I would not ca=
ll it an=20
IPv6 implementation.

To document that there are throughput problems for longer prefixes is n=
othing I=20
would document in a standards track document.

Regards
Karsten

Am Freitag, 3. Oktober 2014, 09:28:04 schrieb Ole Troan:
> All,
>=20
> The authors have requested an adoption call for this document as a st=
andards
> track document.
>=20
> Please provide a view with reasons as to whether the WG should adopt =
this or
> not.
>=20
> This message starts a one week 6MAN Working Group call on adopting:
>=20
> =09Title           : IPv6 Prefix Length Recommendation for Forwarding=

> =09Author(s)    : M. Boucadair, A. Petrescu
> =09Filename    : draft-boucadair-6man-prefix-routing-reco-02
> =09Pages        : 4
> =09Date          : 2014-09-24
>=20
> http://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-0=
2
>=20
> The call ends on October 10th, 2014.
>=20
> Regards,
>=20
> Bob Hinden & Ole Tr=F8an
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Fri Oct  3 07:05:47 2014
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D43511A3B9E for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 07:05:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.687
X-Spam-Level: 
X-Spam-Status: No, score=-7.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 VzpAKVyXBTcG for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 07:05:29 -0700 (PDT)
Received: from mx.pao1.isc.org (mx.pao1.isc.org [149.20.64.53]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 653B21A1BF0 for <ipv6@ietf.org>; Fri,  3 Oct 2014 07:05:29 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP id 8C1073493E2; Fri,  3 Oct 2014 14:05:24 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id 50903160068; Fri,  3 Oct 2014 14:08:22 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 21285160064; Fri,  3 Oct 2014 14:08:22 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 8661420BC158; Sat,  4 Oct 2014 00:05:19 +1000 (EST)
To: Alejandro Acosta <alejandroacostaalamo@gmail.com>
From: Mark Andrews <marka@isc.org>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
In-reply-to: Your message of "Fri, 03 Oct 2014 08:53:40 -0430." <542EA35C.2080606@gmail.com>
Date: Sat, 04 Oct 2014 00:05:19 +1000
Message-Id: <20141003140519.8661420BC158@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/lyiL5FxlFyJyTbFWHBq4jZgu5bw
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 14:05:34 -0000

In message <542EA35C.2080606@gmail.com>, Alejandro Acosta writes:
> Hi List,
>   The first time I read about this idea I did not pay attention but now
> I would like to say that I agree with this.
>   The reason I support this idea is that for many many years a lot of
> transition mechanisms have been created generating several doubts to
> service providers. Deprecating 6to4 will give direct and indirect
> reasons to service providers to move to native IPv6.
>
> Best regards,
>
> Alejandro,

ISP's are already moving.  I seriously doubt that moving 6to4 to
historic will make one iota of difference.  All it will do is
make it more painful for those that rely on it.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Fri Oct  3 07:06:55 2014
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C06321A1B6B for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 07:06:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 xQBWFhwgk41P for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 07:06:48 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 806871A6F04 for <ipv6@ietf.org>; Fri,  3 Oct 2014 07:06:37 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s93E6ZkO029354 for <ipv6@ietf.org>; Fri, 3 Oct 2014 16:06:35 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 780762071F3 for <ipv6@ietf.org>; Fri,  3 Oct 2014 16:07:32 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 6E0032071F2 for <ipv6@ietf.org>; Fri,  3 Oct 2014 16:07:32 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s93E6GkI001367 for <ipv6@ietf.org>; Fri, 3 Oct 2014 16:06:34 +0200
Message-ID: <542EAD58.2060907@gmail.com>
Date: Fri, 03 Oct 2014 16:06:16 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <CAAedzxqxtV7UK4MNUoDLbEogFH3TVUpWy+rRX_uvsOLJ3oergw@mail.gmail.com> <542E9F38.7050000@massar.ch>
In-Reply-To: <542E9F38.7050000@massar.ch>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/KMeH57yz8MZN2rIHb1luxXDx5ss
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 14:06:53 -0000

Le 03/10/2014 15:06, Jeroen Massar a écrit :
> On 2014-10-03 07:05, Erik Kline wrote:
>> One concern I remember from one of the most vocal opponents at that time
>> was that deprecation might cause code to get deleted from codebases
>
> Why would that be bad?
>
> Code that is not used and could possibly provide a path to some kind of
> exploit/abuse/unknown use is good to disappear.

It would be good to document cases where that happened.

Here something along these lines happened recently with the -brand- CLI 
not specifying the IPv4 dst address, followed by "invalid memory 
action", and then by all outgoing IPv6 packets going encapsulated to 
random IPv4 addresses.  Not only  it could have been considered 
legitimately as an attack by the receivers, but had a geo-political 
dimension on it when localized on certain regions of a map.

On another hand, for whatever is worth, at my local setting IPv6 as 
'6to4' works just fine in 2014 and maybe in 2015 there would be reason 
to move to native, and even more so if 6to4 service is not maintained.

Alex

> One of the many things that the LibreSSL folks are doing to OpenSSL.
>
>> or at the very least bitrot (with various patches rejected sited IETF
>> deprecation).
>
> The only acceptable patch is in those cases a patch that
> removes/deprecates the support.
>
>> I believe this person either had or knew of one or more
>> private uses of 6to4 that would therefore likely suffer.
>
> "Private" means "local", thus do not require anything on the rest of the
> Internet. Also it means that they can set up 6in4 based tunnels or use
> ISATAP.
>
> Unless that "person" provides a lot more details and reasoning, does it
> matter?
>
> Greets,
>   Jeroen
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>



From nobody Fri Oct  3 07:22:50 2014
Return-Path: <tjc@ecs.soton.ac.uk>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B93071A0009 for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 07:22:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.007
X-Spam-Level: 
X-Spam-Status: No, score=-2.007 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.786, SPF_NEUTRAL=0.779] autolearn=ham
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 esmEjajO5C2h for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 07:22:42 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B72131A0023 for <ipv6@ietf.org>; Fri,  3 Oct 2014 07:22:34 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s93EMQwu004255; Fri, 3 Oct 2014 15:22:26 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk s93EMQwu004255
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=201304; t=1412346146; bh=H5Ub3SWXKxgyhiyTte4U2y2e/kw=; h=Mime-Version:Subject:From:In-Reply-To:Date:Cc:References:To; b=OdDg3L9Oaui04TJziMEruXNRMw+qQbkDHVHRDXSxZfu/Nlk2HGx0AOb6LkXvSgpro sG16D7vENLtsBScnVaqZN72Sh/nQJFbanj60hz2h+dMNXuK2Di09u8ocMN8YqpU9Jj JOrgPWhy1gjq/tkHA/8mlDGhs/mN+W9tGqflHgNw=
Received: from gander.ecs.soton.ac.uk (gander.ecs.soton.ac.uk [2001:630:d0:f102::25d]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102::25e]) envelope-from <tjc@ecs.soton.ac.uk> with ESMTP (valid=N/A) id q92FMQ2581309870uh ret-id none; Fri, 03 Oct 2014 15:22:26 +0100
Received: from [IPv6:2001:630:d0:ed04:1521:a4ce:b253:7cdd] ([IPv6:2001:630:d0:ed04:1521:a4ce:b253:7cdd]) (authenticated bits=0) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id s93EMMjQ028260 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 3 Oct 2014 15:22:22 +0100
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
From: Tim Chown <tjc@ecs.soton.ac.uk>
In-Reply-To: <20141003140519.8661420BC158@rock.dv.isc.org>
Date: Fri, 3 Oct 2014 15:22:22 +0100
Content-Transfer-Encoding: quoted-printable
Message-ID: <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk>
To: Mark Andrews <marka@isc.org>
X-Mailer: Apple Mail (2.1878.6)
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=q92FMP258130987000; tid=q92FMQ2581309870uh; client=relay,ipv6; mail=; rcpt=; nrcpt=3:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: s93EMQwu004255
X-ECS-MailScanner-From: tjc@ecs.soton.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/o8wFRQfebnGfN88QvrmBn80BHF4
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 14:22:46 -0000

On 3 Oct 2014, at 15:05, Mark Andrews <marka@isc.org> wrote:

> In message <542EA35C.2080606@gmail.com>, Alejandro Acosta writes:
>> Hi List,
>>  The first time I read about this idea I did not pay attention but =
now
>> I would like to say that I agree with this.
>>  The reason I support this idea is that for many many years a lot of
>> transition mechanisms have been created generating several doubts to
>> service providers. Deprecating 6to4 will give direct and indirect
>> reasons to service providers to move to native IPv6.
>>=20
>> Best regards,
>>=20
>> Alejandro,
>=20
> ISP's are already moving.  I seriously doubt that moving 6to4 to
> historic will make one iota of difference.  All it will do is
> make it more painful for those that rely on it.

A problem is we simply don=92t know who relies on it.

The Google stats have 6to4/Teredo traffic at 0.01%, and native =
approaching 5%. =20

But what I assume that Google figure doesn=92t show is 6to4 to 6to4 =
traffic, which is the mode in which it works well, rather than where it =
depends on the highly problematic relays.

Tim=


From nobody Fri Oct  3 09:06:47 2014
Return-Path: <msweet@apple.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACD061A19F1 for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 09:06:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.087
X-Spam-Level: 
X-Spam-Status: No, score=-5.087 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 ppb5Q24isZpE for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 09:06:27 -0700 (PDT)
Received: from mail-in5.apple.com (mail-out5.apple.com [17.151.62.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 69E0F1A19F6 for <ipv6@ietf.org>; Fri,  3 Oct 2014 09:06:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=apple.com; s=mailout2048s; c=relaxed/simple;  q=dns/txt; i=@apple.com; t=1412352386; x=2276265986; h=From:Sender:Reply-To:Subject:Date:Message-id:To:Cc:MIME-version:Content-type: Content-transfer-encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-reply-to:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=enRiol/11F7RpMzifkPGuuf+/XckdXhLCKSX7anOYyU=; b=fVyDnGxSWjNCJzXL7JiIZ6UL/UyPxjuSaxiGq/6Tw+G2xgP2sWKkzndQnGqxqFNJ Fs/5qRdAmZl4wQymm6aHPUXq420bUlsECCyba7IqsEzixR5EhEQWXEKoCQoZhVoo 5ZtwbhsXQo4x8Rn85Qp/szk7b2g+HE3BUiKq/aDGsTJgNn8SLqzLlrk8cdrAsqun EgFx/LH/NwNfT9K4M5CIIrcuc8AHHc5+PNsRjdt5oyuMIzaX+wTENXQ9kjUP8Ppo lci30p2IUV2q/vHV+nnkrJKpyKrQa6BC+G9ZpLVggqBlFX0QlhrjNkpLQLzNklyk LM9X8rJHNhfFmFqnTdLTLA==;
Received: from mail-out.apple.com (bramley.apple.com [17.151.62.49]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate) by mail-in5.apple.com (Apple Secure Mail Relay) with SMTP id 22.A3.24074.289CE245; Fri,  3 Oct 2014 09:06:26 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=windows-1252
Received: from relay2.apple.com ([17.128.113.67]) by local.mail-out.apple.com (Oracle Communications Messaging Server 7.0.5.30.0 64bit (built Oct 22 2013)) with ESMTP id <0NCV00CDDM15SGY0@local.mail-out.apple.com> for ipv6@ietf.org; Fri, 03 Oct 2014 09:06:26 -0700 (PDT)
X-AuditID: 11973e13-f79326d000005e0a-ee-542ec982ad79
Received: from marigold.apple.com (marigold.apple.com [17.128.115.132]) (using TLS with cipher RC4-MD5 (128/128 bits)) (Client did not present a certificate)	by relay2.apple.com (Apple SCV relay) with SMTP id E2.93.19003.E79CE245; Fri,  3 Oct 2014 09:06:23 -0700 (PDT)
Received: from [17.153.23.121] (unknown [17.153.23.121]) by marigold.apple.com (Oracle Communications Messaging Server 7.0.5.30.0 64bit (built Oct 22 2013)) with ESMTPSA id <0NCV008NCM2OC600@marigold.apple.com> for ipv6@ietf.org; Fri, 03 Oct 2014 09:06:25 -0700 (PDT)
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
From: Michael Sweet <msweet@apple.com>
In-reply-to: <542EAD58.2060907@gmail.com>
Date: Fri, 03 Oct 2014 12:06:23 -0400
Content-transfer-encoding: quoted-printable
Message-id: <AD71B0BB-B504-46C7-A275-7F16DF96B68E@apple.com>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <CAAedzxqxtV7UK4MNUoDLbEogFH3TVUpWy+rRX_uvsOLJ3oergw@mail.gmail.com> <542E9F38.7050000@massar.ch> <542EAD58.2060907@gmail.com>
To: 6man <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1988)
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrELMWRmVeSWpSXmKPExsUiON3OULfppF6IwfFmPouXZ98zOTB6LFny kymAMYrLJiU1J7MstUjfLoEr4+yeOUwFy8Urbs8UbWCcJNzFyMkhIWAisbThLjuELSZx4d56 ti5GLg4hgZlMErumtbCAJHgFBCV+TL4HZHNwMAvoSdy/qAVRM4VJ4uLC58wwg/7fPsMKkZjE JHHt5yQmCGcik8TWnQ8YQaqEBUIkbq46BzaVTUBN4vekPlYQm1NAU+LvxydsIDaLgKrEgv2/ wWxmAW2JJ+8usEJcYSOx/fIdqKEnGCVOTX3ABJIQEZCQuLboERvEGbISUxY8ZQYpkhB4zipx 4Ncd9gmMwrOQvDEL4Y1ZSHYsYGRexSiUm5iZo5uZZ6qXWFCQk6qXnJ+7iRESyMI7GE+vsjrE KMDBqMTD++GGbogQa2JZcWXuIUZpDhYlcd7W10AhgfTEktTs1NSC1KL4otKc1OJDjEwcnFIN jMHzVm55GPtU4sh6Xbb4FScCdu5w+vk0Lem96vNI7tMPO7vOLc4xElFb3LjgXrSivzBPdZP6 Z4HA/8zqX435WD7dyeW6VbtQfePt3nxRQ9vV2VrzNUxzt5wyS7ry8/bzVrNeFSdG+dSwwpse p+1ifAUFu54ku0zUraltOe34nMlV60KhkqKKEktxRqKhFnNRcSIAeVHgQEUCAAA=
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprBLMWRmVeSWpSXmKPExsUi2FDcolt/Ui/EYOVcJouXZ98zOTB6LFny kymAMYrLJiU1J7MstUjfLoEr4+yeOUwFy8Urbs8UbWCcJNzFyMkhIWAi8f/2GVYIW0ziwr31 bF2MXBxCApOYJP5+bmWHcCYySWzd+YCxi5GDg1lAT+L+RS2QBl4gc8OVr+wgtrBAiMTNVedY QGw2ATWJ35P6wIZyCmhK/P34hA3EZhFQlViw/zeYzSygLfHk3QVWiDk2Etsv32GC2HWCUeLU 1AdMIAkRAQmJa4sesUFcJysxZcFT5gmM/LMQzpiF5IxZSMYuYGRexShQlJqTWGmkl1hQkJOq l5yfu4kRHF6FzjsYjy2zOsQowMGoxMP74YZuiBBrYllxZe4hRgkOZiUR3gUr9UKEeFMSK6tS i/Lji0pzUosPMUpzsCiJ8169D1QtkJ5YkpqdmlqQWgSTZeLglGpgtI9KvBB+6tnvh/e3tv7S V/+10qC/hpH14dQn7+eesNz2/5TXLgnN3OZq5XX/5txyvc1t/t1uBZtr8UuHvW9yj//gNplg +9fbMfUdw7QWoW8P1HId3W1v8OsZBd+5b14dzS/74V98p+PLMhXZ9ovKGUu+yc9evXXbxPy3 2xpOtszLVJhoI2A1R4mlOCPRUIu5qDgRAOGGFW4rAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/apgiwI3D4GWfkUS34lBUOPOGSa8
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 16:06:36 -0000

FWIW, as an implementor I incorporated changes into CUPS to prevent the =
use of 6to4 back in October of 2005 (9 years ago), mainly because of the =
issues identified in:

    http://tools.ietf.org/html/rfc3964
    =
ftp://ftp.itojun.org/pub/paper/draft-cmetz-v6ops-v4mapped-api-harmful-01.t=
xt

> On Oct 3, 2014, at 10:06 AM, Alexandru Petrescu =
<alexandru.petrescu@gmail.com> wrote:
>=20
> Le 03/10/2014 15:06, Jeroen Massar a =E9crit :
>> On 2014-10-03 07:05, Erik Kline wrote:
>>> One concern I remember from one of the most vocal opponents at that =
time
>>> was that deprecation might cause code to get deleted from codebases
>>=20
>> Why would that be bad?
>>=20
>> Code that is not used and could possibly provide a path to some kind =
of
>> exploit/abuse/unknown use is good to disappear.
>=20
> It would be good to document cases where that happened.
>=20
> Here something along these lines happened recently with the -brand- =
CLI not specifying the IPv4 dst address, followed by "invalid memory =
action", and then by all outgoing IPv6 packets going encapsulated to =
random IPv4 addresses.  Not only  it could have been considered =
legitimately as an attack by the receivers, but had a geo-political =
dimension on it when localized on certain regions of a map.
>=20
> On another hand, for whatever is worth, at my local setting IPv6 as =
'6to4' works just fine in 2014 and maybe in 2015 there would be reason =
to move to native, and even more so if 6to4 service is not maintained.
>=20
> Alex
>=20
>> One of the many things that the LibreSSL folks are doing to OpenSSL.
>>=20
>>> or at the very least bitrot (with various patches rejected sited =
IETF
>>> deprecation).
>>=20
>> The only acceptable patch is in those cases a patch that
>> removes/deprecates the support.
>>=20
>>> I believe this person either had or knew of one or more
>>> private uses of 6to4 that would therefore likely suffer.
>>=20
>> "Private" means "local", thus do not require anything on the rest of =
the
>> Internet. Also it means that they can set up 6in4 based tunnels or =
use
>> ISATAP.
>>=20
>> Unless that "person" provides a lot more details and reasoning, does =
it
>> matter?
>>=20
>> Greets,
>>  Jeroen
>>=20
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>=20
>>=20
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair


From nobody Fri Oct  3 15:56:28 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7A791A02D4 for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 15:56:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 i-5zzQ1INZry for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 15:56:25 -0700 (PDT)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0C641A01F6 for <ipv6@ietf.org>; Fri,  3 Oct 2014 15:56:24 -0700 (PDT)
Received: by mail-pa0-f51.google.com with SMTP id lj1so2238442pab.10 for <ipv6@ietf.org>; Fri, 03 Oct 2014 15:56:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=XjHBsdxrI2ZeTMDY54uK745WlRNHCODLFo26nkBsyqA=; b=rg3aittOdK/igge331iP797L7IbIhPqntnKFVYqnTkFFkCLHrlhwOy79PbdhdlPcPz UNpHdQTOCp+U7Vq6pAf0h5ziHswyIO4UmFbmn0eFk2zJ/RLNOGzPM+Se1+y9g2/Uomhy duecrhILwjFvOJfozgyCoItbx64dh3usbcSY+7p5+wPzlUmr8N59s10VAbr6v9RtVGQi RAV2xLHs6AxjzVr+iwyM/ey9zEdyM7kF5dve5/Bw6iHLF2vuKUiLJHpil8TajDVId5ir iH70RLOrSqaxzHkWlfK8TWoNjL4ihG5z7u8VJ6j7x7ZN46tJmZJ8k6moOBiXKvoQ18Br 5SuA==
X-Received: by 10.66.236.38 with SMTP id ur6mr9976609pac.49.1412376984706; Fri, 03 Oct 2014 15:56:24 -0700 (PDT)
Received: from [192.168.178.23] (5.198.69.111.dynamic.snap.net.nz. [111.69.198.5]) by mx.google.com with ESMTPSA id ic5sm7323027pbb.3.2014.10.03.15.56.21 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 03 Oct 2014 15:56:23 -0700 (PDT)
Message-ID: <542F29A2.9090406@gmail.com>
Date: Sat, 04 Oct 2014 11:56:34 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/D0YBkuulRVmzz2PwD83zhHViPMI
Cc: ipv6@ietf.org, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 22:56:26 -0000

On 04/10/2014 03:22, Tim Chown wrote:
> On 3 Oct 2014, at 15:05, Mark Andrews <marka@isc.org> wrote:
>=20
>> In message <542EA35C.2080606@gmail.com>, Alejandro Acosta writes:
>>> Hi List,
>>>  The first time I read about this idea I did not pay attention but no=
w
>>> I would like to say that I agree with this.
>>>  The reason I support this idea is that for many many years a lot of
>>> transition mechanisms have been created generating several doubts to
>>> service providers. Deprecating 6to4 will give direct and indirect
>>> reasons to service providers to move to native IPv6.
>>>
>>> Best regards,
>>>
>>> Alejandro,
>> ISP's are already moving.  I seriously doubt that moving 6to4 to
>> historic will make one iota of difference.  All it will do is
>> make it more painful for those that rely on it.
>=20
> A problem is we simply don=E2=80=99t know who relies on it.
>=20
> The Google stats have 6to4/Teredo traffic at 0.01%, and native approach=
ing 5%. =20
>=20
> But what I assume that Google figure doesn=E2=80=99t show is 6to4 to 6t=
o4 traffic, which is the mode in which it works well, rather than where i=
t depends on the highly problematic relays.

Exactly. That's why I think we actually need a BCP (probably in v6ops)
rather than a simple s/Proposed Standard/Historic/.

The motivation here is damage prevention, and that cuts both ways.

   Brian

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


From nobody Fri Oct  3 16:07:30 2014
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC771A1AE0 for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 16:07:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=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 ti19qqCekzVZ for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 16:07:16 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D61A11A19FB for <ipv6@ietf.org>; Fri,  3 Oct 2014 16:07:15 -0700 (PDT)
Received: from [172.22.229.45] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s93N7A46009139 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 3 Oct 2014 16:07:10 -0700
Message-ID: <542F2C1E.4090909@acm.org>
Date: Fri, 03 Oct 2014 16:07:10 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>
Subject: Re: Adoption call of draft-halpern-6man-nd-pre-resolve-addr for 6MAN
References: <407DEA57-2807-44A5-8936-45B20CDB87C0@employees.org> <7DDF678F-1E09-4016-894C-6F16C2215859@employees.org>
In-Reply-To: <7DDF678F-1E09-4016-894C-6F16C2215859@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
X-Sonic-CAuth: UmFuZG9tSVYCN4J3n2AGjGiUdeQjNYzTLT0gBv/TRjtr1UniyZzRf14hLEwA27sk7qC4cUGaAkLm8f+oVgXuAtfyNxAcm9kw
X-Sonic-ID: C;7B/yAFJL5BGKmnyTE+W37Q== M;/jIEAVJL5BGKmnyTE+W37Q==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/fbVF7rUk4W5g0Alzhs6c9eau3QI
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 03 Oct 2014 23:07:18 -0000

Ole,

I missed the reference to the IPR disclosure since it wasn't in the 
actual WG last call but in a follow-up email.

I find this technique of limited utility. For instance, it does not 
describe how the entry can actually remain in the neighbor cache for 
weeks or months (the host will do DAD once, and the DOS attack can 
happen a long time after that). As indicated in RFC 6583 events like 
Spanning Tree Protocol (STP) Topology Change Notification (TCN) might 
invalidate the neighbor cache on an interface. Or a flood which results 
in NUD packets not being processed in a timely manner will result in 
loosing the NCE.

Given that *plus* the claimed IPR, I don't see why the WG needs to spend 
time on this.
It might be useful to document this behavior that Ericsson as 
implemented in an independent submission informational document.

    Erik



On 9/24/14 11:20 PM, Ole Troan wrote:
> for some additional information, here is the initial discussion of the draft back in January:
> https://mailarchive.ietf.org/arch/search/?q=draft-halpern-6man-nd-pre-resolve-addr&gbt=1
>
> and here is the IPR disclosure:
> https://datatracker.ietf.org/ipr/2300/
>
> Ole
>
>> On 24 Sep 2014, at 9:24 , Ole Troan <otroan@employees.org> wrote:
>>
>> All,
>>
>> The authors have requested an adoption call for this document as an informational document.
>>
>> Please provide a view with reasons as to whether the WG should adopt this or not.
>>
>> This message starts a one week 6MAN Working Group call on adopting:
>>
>> 	Title           : Triggering ND Address Resolution on Receiving DAD-NS
>> 	Author(s)    : I. Chen, J. Halpern
>> 	Filename    : draft-halpern-6man-nd-pre-resolve-addr-00
>> 	Pages        : 7
>> 	Date          : 2014-01-10
>>
>> http://tools.ietf.org/html/draft-halpern-6man-nd-pre-resolve-addr-00
>>
>> The call ends on October 1st, 2014.
>>
>> Regards,
>>
>> Bob Hinden & Ole TrÃ¸an
>>
>>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Sat Oct  4 02:02:35 2014
Return-Path: <tore@fud.no>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0695A1A8F48 for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 02:02:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 5JhoofesvpNB for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 02:02:32 -0700 (PDT)
Received: from greed.fud.no (greed.fud.no [IPv6:2a02:c0:1001:100::145]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 523DB1A014C for <ipv6@ietf.org>; Sat,  4 Oct 2014 02:02:32 -0700 (PDT)
Received: from [2a02:fe0:c410:3c30::1] (port=43764 helo=envy.fud.no) by greed.fud.no with esmtpsa (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <tore@fud.no>) id 1XaLEQ-0002gJ-Sv; Sat, 04 Oct 2014 11:02:26 +0200
Message-ID: <542FB7A2.6060208@fud.no>
Date: Sat, 04 Oct 2014 11:02:26 +0200
From: Tore Anderson <tore@fud.no>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.1
MIME-Version: 1.0
To: Tim Chown <tjc@ecs.soton.ac.uk>, Mark Andrews <marka@isc.org>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/ZZ1sIUU4BQmuX3z_qz9QCGZuQDI
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 04 Oct 2014 09:02:34 -0000

* Tim Chown

> A problem is we simply don’t know who relies on it.
> 
> The Google stats have 6to4/Teredo traffic at 0.01%, and native
> approaching 5%.

When we realised that the IETF wasn't ready to deprecate 6to4, we went
straight to the software vendors instead, who *did* listen and took the
necessary steps to deprecate/disable it in their products. So we
fortunately succeeded in killing it without the IETF's help.

In all likelihood, the 0.01% constitute the long trail of not upgraded
software and operating systems. They'll go away eventually; I doubt that
reviving the 6to4-to-historic draft would accelerate the process.

Marking 6to4 as historic would appropriately document current
operational reality, though. I suppose that would have some value in
itself, so I'd support doing so. That said, I doubt marking it as
historic will prevent people from doing stupid things, like the
«www.azdes.gov. IN AAAA 2002::cf6c:8846» example that started this
thread. (If you look closely, you'll see that this isn't even a valid
6to4 address.)

> But what I assume that Google figure doesn’t show is 6to4 to 6to4
> traffic, which is the mode in which it works well, rather than where
> it depends on the highly problematic relays.

I'm guessing that it would almost exclusively be BitTorrent. If I'm
right about that, I don't think it would count as «relying on it»
because of the way BitTorrent works; taking away 6to4 wouldn't break
BitTorrent in the slightest.

Tore


From nobody Sat Oct  4 02:26:25 2014
Return-Path: <jeroen@massar.ch>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A72981A90F5 for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 02:26:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
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 80IEA3C3OAGy for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 02:26:20 -0700 (PDT)
Received: from bastion.ch.unfix.org (bastion.ch.unfix.org [46.20.246.101]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D6E71A0196 for <ipv6@ietf.org>; Sat,  4 Oct 2014 02:26:20 -0700 (PDT)
Received: from kami.ch.unfix.org (84-73-144-213.dclient.hispeed.ch [84.73.144.213]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: jeroen) by bastion.ch.unfix.org (Postfix) with ESMTPSA id 460AA1006747C; Sat,  4 Oct 2014 09:26:16 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=massar.ch; s=DKIM2009; t=1412414777; bh=wIY24WK5hKvE+NqmqBKGu8aupYe8yCRtBJEI6WD+RS4=; h=Date:From:To:CC:Subject:References:In-Reply-To; b=a2LR6ZdD29a4BZOmOGHKOssp5Nufi+fS2DKrecp2V5HsprZqr9v2mau8mofOOqYrQ cWJbBhY2hpOI/P8NJQlOa3MrPtXqyAslPRcyI7I4WUzXsptVDq6Dh+9vmztvQAaUJW /q5JIlEwPJYZ4WteMq4RFn+6OI58SnbTbz9wFJe0hfy7eUvB02RwTyiJbtypwJS80Z a98swDhg9iPvBzIH/7rrqyXitUWsGFMyaGEXXLUgQswOUBycMfjfq8A356kK+9Ot6A Jc4PJ8ZsTGfukyJqIpicf0+XcZHtr/AIKqu82GFT7cfOxWOXb0nPXbUjh4kwz24NOi 1QRIXEJpEeMiQ==
Message-ID: <542FBD36.5070202@massar.ch>
Date: Sat, 04 Oct 2014 11:26:14 +0200
From: Jeroen Massar <jeroen@massar.ch>
Organization: Massar
MIME-Version: 1.0
To: Tore Anderson <tore@fud.no>, Tim Chown <tjc@ecs.soton.ac.uk>,  Mark Andrews <marka@isc.org>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no>
In-Reply-To: <542FB7A2.6060208@fud.no>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/iyMwHISZ_U4kY5sAsXXfpQju9HA
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 04 Oct 2014 09:26:22 -0000

On 2014-10-04 11:02, Tore Anderson wrote:
> * Tim Chown
> 
>> A problem is we simply don’t know who relies on it.
>>
>> The Google stats have 6to4/Teredo traffic at 0.01%, and native
>> approaching 5%.
> 
> When we realised that the IETF wasn't ready to deprecate 6to4, we went
> straight to the software vendors instead, who *did* listen and took the
> necessary steps to deprecate/disable it in their products. So we
> fortunately succeeded in killing it without the IETF's help.
> 
> In all likelihood, the 0.01% constitute the long trail of not upgraded
> software and operating systems. They'll go away eventually; I doubt that
> reviving the 6to4-to-historic draft would accelerate the process.

It would indeed not, but it would give a signal as then it is
"officially" gone, especially the .govs understand that.

> Marking 6to4 as historic would appropriately document current
> operational reality, though. I suppose that would have some value in
> itself, so I'd support doing so. That said, I doubt marking it as
> historic will prevent people from doing stupid things, like the
> «www.azdes.gov. IN AAAA 2002::cf6c:8846» example that started this
> thread. (If you look closely, you'll see that this isn't even a valid
> 6to4 address.)

(Can't fix PEBKAC :)

>> But what I assume that Google figure doesn’t show is 6to4 to 6to4
>> traffic, which is the mode in which it works well, rather than where
>> it depends on the highly problematic relays.
> 
> I'm guessing that it would almost exclusively be BitTorrent. If I'm
> right about that, I don't think it would count as «relying on it»
> because of the way BitTorrent works; taking away 6to4 wouldn't break
> BitTorrent in the slightest.

I would assume the same, especially as RFC3484 and Happy Eyeballs caused
6to4 to be used in very few circumstances.

Greets,
 Jeroen



From nobody Sat Oct  4 02:59:11 2014
Return-Path: <sander@steffann.nl>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7FE41A9108 for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 02:59:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.094
X-Spam-Level: 
X-Spam-Status: No, score=0.094 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, SPF_PASS=-0.001] autolearn=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 Ibk3g_l5LkCm for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 02:59:07 -0700 (PDT)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:9e0:803::6]) (using TLSv1.1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEBCF1A9107 for <ipv6@ietf.org>; Sat,  4 Oct 2014 02:59:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.sintact.nl (Postfix) with ESMTP id 2C1F756; Sat,  4 Oct 2014 11:59:05 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=steffann.nl; h= x-mailer:references:message-id:content-transfer-encoding:date :date:in-reply-to:from:from:subject:subject:mime-version :content-type:content-type:received:received; s=mail; t= 1412416743; bh=129xagr7MzfEUq3PW1wO1cLobSmSk0CAh3BBVaZtv1I=; b=G 6TJIYWIcpudk4L64E0cYvpqAQ/ZLsjlrhXPtBUPxQcy59HGcRDJyGxWfdGU5nriO 07bNp+NP6Mn1qCV2r/5uok6fbR+xXaaRJE616gUzwwjta3Lb6HPiimaFwYkaFKt2 GB2NT8OL8LVHDRlrvyyQod7bi4EVkoFp7V6SHquVcM=
X-Virus-Scanned: Debian amavisd-new at mail.sintact.nl
Received: from mail.sintact.nl ([127.0.0.1]) by localhost (mail.sintact.nl [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id gCqMJ1hd2jaz; Sat,  4 Oct 2014 11:59:03 +0200 (CEST)
Received: from [IPv6:2a00:8640:1::78be:d36a:7e02:1734] (unknown [IPv6:2a00:8640:1:0:78be:d36a:7e02:1734]) by mail.sintact.nl (Postfix) with ESMTPSA id 2DB1855; Sat,  4 Oct 2014 11:59:02 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1988\))
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <542FB7A2.6060208@fud.no>
Date: Sat, 4 Oct 2014 11:59:01 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no>
To: Tore Anderson <tore@fud.no>
X-Mailer: Apple Mail (2.1988)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/Thq5GV1_56HJYm4cYiEQ5eYux1I
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ipv6@ietf.org, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 04 Oct 2014 09:59:09 -0000

Hi,

> Marking 6to4 as historic would appropriately document current
> operational reality, though. I suppose that would have some value in
> itself, so I'd support doing so.

+1.

I still have people in my training classes that think 6to4 is a great =
idea. When I tell them why they shouldn't depend on 6to4 I sometimes get =
the reply: "but it's an official internet standard, we should just be =
able to use it!". And I'm sure that they're not the only ones that =
prefer 'standards' over common sense.

Good documentation of current operational reality is important.

Cheers,
Sander


From nobody Sat Oct  4 03:27:36 2014
Return-Path: <randy@psg.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 49B381A911E for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 03:27:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 9v-FXnegaQ5j for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 03:27:33 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3BA6D1A911D for <ipv6@ietf.org>; Sat,  4 Oct 2014 03:27:33 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1XaMYl-0007O1-Ov for ipv6@ietf.org; Sat, 04 Oct 2014 10:27:32 +0000
Date: Sat, 04 Oct 2014 19:27:30 +0900
Message-ID: <m21tqom8od.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: IPv6 Deployment Prevention <ipv6@ietf.org>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
In-Reply-To: <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/gv-IAY4C_wLOLwdgzFsWuA56YoE
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 04 Oct 2014 10:27:34 -0000

ok.  i am confused.  what is 6to4?  i thought we were supposed to be
going from 4 to 6.  this ietf place is pretty crazy.

randy


From nobody Sat Oct  4 11:24:35 2014
Return-Path: <nygren@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F34541A0126 for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 11:24:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 fY6Kzos0m0xR for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 11:24:32 -0700 (PDT)
Received: from mail-vc0-x22f.google.com (mail-vc0-x22f.google.com [IPv6:2607:f8b0:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA03A1A0120 for <ipv6@ietf.org>; Sat,  4 Oct 2014 11:24:31 -0700 (PDT)
Received: by mail-vc0-f175.google.com with SMTP id id10so1810897vcb.20 for <ipv6@ietf.org>; Sat, 04 Oct 2014 11:24:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tXNsKAm5KbttPxBVvzMr/oDHOyTf+bX07PGemBRc0zs=; b=ssXpTB6rJ3CZfWgG1/0fMFz6Vd8kuYfqSKq6dezFiid/iiPq7Oo7yvdRlBfsUEJ9HP v54hLkWX9AfBpq+N6WsChTWgBhUiIyxEtELMKZx6T24zXE9U6L7sf5/XQoSl9QeXVDfw /mz9nygghP6nUl+JXE/gRZiTxebrz7vL19FFYnp/UUOq89s6dulnRDs0GEFTx2a0Csj/ Zcdr510blbIIX7foYrOOf0KjNtUPm06abPSqK0fnnSBSP2z62/JGeHmPYycHhS7IGhgD VFupTGS0nDPglO1OB36JNLIaq9zOz04Ah+Tg1bS0aHCsGT1T1njUMkEi+k/2bgkQkN3M SVGw==
MIME-Version: 1.0
X-Received: by 10.220.251.13 with SMTP id mq13mr398034vcb.25.1412447070956; Sat, 04 Oct 2014 11:24:30 -0700 (PDT)
Sender: nygren@gmail.com
Received: by 10.220.12.11 with HTTP; Sat, 4 Oct 2014 11:24:30 -0700 (PDT)
In-Reply-To: <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl>
Date: Sat, 4 Oct 2014 14:24:30 -0400
X-Google-Sender-Auth: XTCwNX0a0Fnz8BhXJB1aIxm4ZHI
Message-ID: <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
From: Erik Nygren <erik+ietf@nygren.org>
To: Sander Steffann <sander@steffann.nl>
Content-Type: multipart/alternative; boundary=089e013cbf8aedb32e05049cf5e4
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/aWsNN8GLg1TNUZGCU7hRP8_I1wE
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Tore Anderson <tore@fud.no>, 6man <ipv6@ietf.org>, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 04 Oct 2014 18:24:33 -0000

--089e013cbf8aedb32e05049cf5e4
Content-Type: text/plain; charset=UTF-8

On Sat, Oct 4, 2014 at 5:59 AM, Sander Steffann <sander@steffann.nl> wrote:

> Hi,
>
> > Marking 6to4 as historic would appropriately document current
> > operational reality, though. I suppose that would have some value in
> > itself, so I'd support doing so.
>
> +1.
>
> I still have people in my training classes that think 6to4 is a great
> idea. When I tell them why they shouldn't depend on 6to4 I sometimes get
> the reply: "but it's an official internet standard, we should just be able
> to use it!". And I'm sure that they're not the only ones that prefer
> 'standards' over common sense.
>
> Good documentation of current operational reality is important.
>


+1.

I run into the same issue.

Similarly, it would be good to be able to officially confirm/communicate
to people that standing up IPv6 networks do not need to run 6to4 anycast
relays.
Given the amount of complexity introduced while we're in the dual-stack
world,
anything we can do that officially reduces that complexity is also valuable.

     Erik

--089e013cbf8aedb32e05049cf5e4
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On S=
at, Oct 4, 2014 at 5:59 AM, Sander Steffann <span dir=3D"ltr">&lt;<a href=
=3D"mailto:sander@steffann.nl" target=3D"_blank">sander@steffann.nl</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<span class=3D""><br>
&gt; Marking 6to4 as historic would appropriately document current<br>
&gt; operational reality, though. I suppose that would have some value in<b=
r>
&gt; itself, so I&#39;d support doing so.<br>
<br>
</span>+1.<br>
<br>
I still have people in my training classes that think 6to4 is a great idea.=
 When I tell them why they shouldn&#39;t depend on 6to4 I sometimes get the=
 reply: &quot;but it&#39;s an official internet standard, we should just be=
 able to use it!&quot;. And I&#39;m sure that they&#39;re not the only ones=
 that prefer &#39;standards&#39; over common sense.<br>
<br>
Good documentation of current operational reality is important.<br></blockq=
uote><div><br><br><div>+1.<br><br></div>I run into the same issue.=C2=A0 <b=
r><br></div><div>Similarly, it would be good to be able to officially confi=
rm/communicate <br>to people that standing up IPv6 networks do not need to =
run 6to4 anycast relays.<br></div><div>Given the amount of complexity intro=
duced while we&#39;re in the dual-stack world,<br>anything we can do that o=
fficially reduces that complexity is also valuable.<br><br></div><div>=C2=
=A0=C2=A0=C2=A0=C2=A0 Erik<br><br></div></div></div></div>

--089e013cbf8aedb32e05049cf5e4--


From nobody Sat Oct  4 12:17:02 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 783931A0172 for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 12:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 G61QSf8BInv6 for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 12:16:58 -0700 (PDT)
Received: from mail-pa0-x230.google.com (mail-pa0-x230.google.com [IPv6:2607:f8b0:400e:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A90151A0167 for <ipv6@ietf.org>; Sat,  4 Oct 2014 12:16:58 -0700 (PDT)
Received: by mail-pa0-f48.google.com with SMTP id eu11so3126206pac.35 for <ipv6@ietf.org>; Sat, 04 Oct 2014 12:16:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=vqbKRBL4tFgayfGRHtKhb1kAB3NetoKAqEQTQEHjBOI=; b=RR7AeEtBJ0DuL8ZM8ZYWJdJ2SKHkD5936voLaTfcpARMSn2pPkywMFQy+mLGLhIHKi 2Hlznf9v9F9Ce20fY+JoKQmS2o9gohmo27NnX5/qph5IwBYAYvxhK1Njil8F7oSvnw4L sdj3sDaYnvv/RjlhPAcamOAO9dx1VLDVbWgzvFDx2AQJwANdi/atOjrGlxOp9ldCNYIk XdcboY4OYq2Xq2bF5RyA7R3ZpQVUyPl5mLKoOo2punLQA0yX2g+eJjhcAhlsQ8MFvUWz 621nm/UTiQ4qy10cj8YZvEwot3hmlgXI0cuDjusNQyXMPjUO7X1cbkdGhjttvuMPDkya dyMg==
X-Received: by 10.66.129.199 with SMTP id ny7mr15029550pab.16.1412450218356; Sat, 04 Oct 2014 12:16:58 -0700 (PDT)
Received: from [192.168.178.23] (243.194.69.111.dynamic.snap.net.nz. [111.69.194.243]) by mx.google.com with ESMTPSA id oq6sm7186662pdb.45.2014.10.04.12.16.53 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 04 Oct 2014 12:16:57 -0700 (PDT)
Message-ID: <543047A2.8020804@gmail.com>
Date: Sun, 05 Oct 2014 08:16:50 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Erik Nygren <erik+ietf@nygren.org>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com>
In-Reply-To: <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/wtftD2sif4HMl1YZ28BY9572vas
Cc: 6man <ipv6@ietf.org>, Tim Chown <tjc@ecs.soton.ac.uk>, Tore Anderson <tore@fud.no>, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 04 Oct 2014 19:17:00 -0000

On 05/10/2014 07:24, Erik Nygren wrote:
> On Sat, Oct 4, 2014 at 5:59 AM, Sander Steffann <sander@steffann.nl> wrote:
> 
>> Hi,
>>
>>> Marking 6to4 as historic would appropriately document current
>>> operational reality, though. I suppose that would have some value in
>>> itself, so I'd support doing so.
>> +1.
>>
>> I still have people in my training classes that think 6to4 is a great
>> idea. When I tell them why they shouldn't depend on 6to4 I sometimes get
>> the reply: "but it's an official internet standard, we should just be able
>> to use it!". And I'm sure that they're not the only ones that prefer
>> 'standards' over common sense.
>>
>> Good documentation of current operational reality is important.
>>
> 
> 
> +1.
> 
> I run into the same issue.

There's another issue here that I see from time to time in under-informed
discussion forums such as www.theregister.co.uk/ :

Some people believe that anybody can get an IPv6 address by sticking
their IPv4 address after a magic prefix. ::/96 is a popular choice
for that magic prefix, and judging by the azdes.gov some people
believe that 2002::/96 is equally magic.

Killing that meme would help quite a bit.

That said, I'll repeat that I think a formal deprecation is
now reasonable, but it needs a bit more logic in it than just
declaring several RFCs Historic.

For example, it would not help anybody to switch off correctly
working return 6to4 relays (i.e. boxes that announce 2002::/96).
On the other hand, if all forward relays (boxes that announce
192.88.99.1) were switched off, Anycast 6to4 would cease working
immediately and the resulting problems would vanish.

In fact, it is really only RFC 3068 that needs deprecating,
because that is where the damage comes from. Peer to peer
6to4 doesn't hurt anybody afaik.

> Similarly, it would be good to be able to officially confirm/communicate
> to people that standing up IPv6 networks do not need to run 6to4 anycast
> relays.

s/do not need/SHOULD NOT/

   Brian

> Given the amount of complexity introduced while we're in the dual-stack
> world,
> anything we can do that officially reduces that complexity is also valuable.
> 
>      Erik
> 
> 
> 
> ------------------------------------------------------------------------
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Sat Oct  4 18:31:25 2014
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A88ED1A037C for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 18:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.451
X-Spam-Level: **
X-Spam-Status: No, score=2.451 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, HK_RANDOM_REPLYTO=0.25, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 3pCIdjFbaitX for <ipv6@ietfa.amsl.com>; Sat,  4 Oct 2014 18:31:22 -0700 (PDT)
Received: from nm50.bullet.mail.bf1.yahoo.com (nm50.bullet.mail.bf1.yahoo.com [216.109.114.67]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B174E1A0345 for <ipv6@ietf.org>; Sat,  4 Oct 2014 18:31:22 -0700 (PDT)
Received: from [98.139.212.153] by nm50.bullet.mail.bf1.yahoo.com with NNFMP;  05 Oct 2014 01:31:21 -0000
Received: from [98.139.212.214] by tm10.bullet.mail.bf1.yahoo.com with NNFMP;  05 Oct 2014 01:31:21 -0000
Received: from [127.0.0.1] by omp1023.mail.bf1.yahoo.com with NNFMP; 05 Oct 2014 01:31:21 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 82877.51808.bm@omp1023.mail.bf1.yahoo.com
Received: (qmail 83579 invoked by uid 60001); 5 Oct 2014 01:31:21 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024;  t=1412472681; bh=JboI/GeFXWMw8vjKtkqJKnZCxzz4Nk8Unpyse2GmROs=;  h=References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=CJV25ruj/Sf4ne82v2qwv04roL4FmJvK1b+wng6YwShrK5QnRvPZqSZC08hjFLhDTSBd9aqXTaMoa5eGHVjismD0KhJVWPZVjtFJXkZ2ifxQ5EYP//DI4lP+rReT+ubqS8q4CWE9U5lp46PdZik4J+3nXsEvwRDMUIadb3+ZpCI=
X-YMail-OSG: 5jmmlqMVM1lFP7z9J0rePEUkZBOR6PuXv4ZLdfNiVTO83_W HSHu7SCvgiu94kU3PwoJgvJZl8Uq1HPYm.nFdchLliaIHDXF9t3G7OUfBV8. TMjhrbog5nX3x5dzCZGrgumUM1fcAtlXvS_IVQn6jictQvu7rJA7PlezSSic 5ZTADS2IQ98Pe_zpKBt_XkqYr1i7_CoPe5WmwQ0sh3.kndQlWTsMoueNoBRA w2ny4V8GvrD4_Y6CLupVqGHNxUAD5X6R_d1oWvyobOg5kLw0EiOflGgl3N.d R8gIOYavL6Z3Z7sCJrH98wsujyKUYBUYJ_9sVmaQT7p8I7VdrnimHh9gl3XG DE_THMqXS0_0.QOni.5TRr7ZcndN0nQGX0It.odNVSt2khH6sjiJPrRBLJ77 vIGK_I2L_lV9BJ.UcYcAu3B9o6.6MY0h6fEaSgwzo3bfPvJdk47TOHfm2FGy LTdG_rfiBu3iAvaV4d5M7i3S2EarinwyP_HajF_OvLq6X7bRckMzSrvVqZBY IMVfi1rSWRlhjEg42yU7RYU3C1wQJ8J70pn3fLxWOZt7fboVAQ13yPm19TKQ -
Received: from [150.101.221.237] by web162205.mail.bf1.yahoo.com via HTTP; Sat, 04 Oct 2014 18:31:20 PDT
X-Rocket-MIMEInfo: 002.001, CgoKCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0KPiBGcm9tOiBSYW5keSBCdXNoIDxyYW5keUBwc2cuY29tPgo.IFRvOiBJUHY2IERlcGxveW1lbnQgUHJldmVudGlvbiA8aXB2NkBpZXRmLm9yZz4KPiBDYzogCj4gU2VudDogU2F0dXJkYXksIDQgT2N0b2JlciAyMDE0LCAyMDoyNwo.IFN1YmplY3Q6IFJlOiA2dG80IHRvIEhpc3RvcmljIChpcHY2LW9wc0BjbHVlbmV0IFJlOiA2dG80IGluIEludGVybmV0IGFhYWEgcmVjb3JkcykKPiAKPiBvay4gIGkgYW0gY29uZnVzZWQuICB3aGF0IGlzIDZ0bzQ_ICABMAEBAQE-
X-Mailer: YahooMailWebService/0.8.203.696
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <m21tqom8od.wl%randy@psg.com>
Message-ID: <1412472680.77308.YahooMailNeo@web162205.mail.bf1.yahoo.com>
Date: Sat, 4 Oct 2014 18:31:20 -0700
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
To: Randy Bush <randy@psg.com>, IPv6 Deployment Prevention <ipv6@ietf.org>
In-Reply-To: <m21tqom8od.wl%randy@psg.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/XrpA62xOI6-7avt_ZXzLgAbYRIw
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sun, 05 Oct 2014 01:31:23 -0000

=0A=0A=0A=0A----- Original Message -----=0A> From: Randy Bush <randy@psg.co=
m>=0A> To: IPv6 Deployment Prevention <ipv6@ietf.org>=0A> Cc: =0A> Sent: Sa=
turday, 4 October 2014, 20:27=0A> Subject: Re: 6to4 to Historic (ipv6-ops@c=
luenet Re: 6to4 in Internet aaaa records)=0A> =0A> ok.  i am confused.  wha=
t is 6to4?  i thought we were supposed to be=0A> going from 4 to 6.  this i=
etf place is pretty crazy.=0A> =0A=0AIt was a way for people like me for ma=
ny years who only had IPv4 at home could get a IPv6 prefix and IPv6 Interne=
t access without having to ask anybody. Configured HE tunnels were/are grea=
t, however they didn't provide as optimal forwarding as 6to4 did (my 6to4 r=
elay was only around 1000 miles from me here in Australia, compared to over=
seas somewhere for the HE tunnel end-point ...)=0A=0A> randy=0A> =0A> =0A> =
--------------------------------------------------------------------=0A> IE=
TF IPv6 working group mailing list=0A> ipv6@ietf.org=0A> Administrative Req=
uests: https://www.ietf.org/mailman/listinfo/ipv6=0A> ---------------------=
-----------------------------------------------=0A> 


From nobody Sun Oct  5 04:31:13 2014
Return-Path: <fw@deneb.enyo.de>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 30F001A00EF for <ipv6@ietfa.amsl.com>; Sun,  5 Oct 2014 04:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.336
X-Spam-Level: 
X-Spam-Status: No, score=-2.336 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 AZDkqWR1DCsH for <ipv6@ietfa.amsl.com>; Sun,  5 Oct 2014 04:31:08 -0700 (PDT)
Received: from albireo.enyo.de (albireo.enyo.de [46.237.207.196]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 166A61A008A for <6man@ietf.org>; Sun,  5 Oct 2014 04:31:07 -0700 (PDT)
Received: from [172.17.203.2] (helo=deneb.enyo.de) by albireo.enyo.de with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) id 1Xak1p-0002fG-2L; Sun, 05 Oct 2014 13:31:05 +0200
Received: from fw by deneb.enyo.de with local (Exim 4.80) (envelope-from <fw@deneb.enyo.de>) id 1Xak1o-0003ZY-Ro; Sun, 05 Oct 2014 13:31:04 +0200
From: Florian Weimer <fw@deneb.enyo.de>
To: Fernando Gont <fernando@gont.com.ar>
Subject: Re: Revision of the IPv6 atomic frag deprecation I-D (Fwd: New Version Notification for draft-gont-6man-deprecate-atomfrag-generation-01.txt)
References: <20140827174304.18733.67331.idtracker@ietfa.amsl.com> <53FE1D07.5060309@gont.com.ar>
Date: Sun, 05 Oct 2014 13:31:04 +0200
In-Reply-To: <53FE1D07.5060309@gont.com.ar> (Fernando Gont's message of "Wed,  27 Aug 2014 15:01:43 -0300")
Message-ID: <87vbnylpmv.fsf@mid.deneb.enyo.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/l4wII0JH3Bl5iNw6Uxp_CDBN1vw
Cc: "6man@ietf.org" <6man@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sun, 05 Oct 2014 11:31:10 -0000

* Fernando Gont:

> We have published a revision of the aforementioned document:
> <http://www.ietf.org/internet-drafts/draft-gont-6man-deprecate-atomfrag-generation-01.txt>

It would be appropriate to reference the 2012 discussion during the
preparation of RFC 6946, which already raised these issues and should
have prevented the publication of RFC 6946.


From czyborra@googlemail.com  Fri Oct  3 23:26:27 2014
Return-Path: <czyborra@googlemail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 198EC1A8F3B for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 23:26:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 XJC0fWlpjdZU for <ipv6@ietfa.amsl.com>; Fri,  3 Oct 2014 23:26:25 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B56B1A8A94 for <ipv6@ietf.org>; Fri,  3 Oct 2014 23:26:24 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id a1so2977747wgh.11 for <ipv6@ietf.org>; Fri, 03 Oct 2014 23:26:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=b0mkqsb0X503VXHIPrUh5FNwWo8zqTtTg08TB4L/2CA=; b=rqMypzcyLDEZHhSYDNY0yv1ERbQ0FIVyYSFWgr1Pn7WfiHhV1hKLRVsBejoDOVDO6w iardHx3MjFq1Qj4MAZDtmFE98z/i9r/VHpjRC1tK/72dJ7G4SdIBTEtJSLsO4r05ZiK9 QNj8JMFA2NOAoDvUhZ2daOJV9CMb8S2vJOGEkOUBx7A45jPSVvRYXtu0kMF9zr5gDcEy uwLMRLJnhW2lw0V5dstOL0ftV3AvMAstlBmmVdMHkCMHjAFzcUn/kh3zEwkHjRADdVhr iekzr4CqpjSGwJ/lGwTM93majdBR23nQ46rqSYkuxhqjC84Ln4w/bFxGfYWMU3SsTLMb hGWA==
X-Received: by 10.194.24.169 with SMTP id v9mr1688030wjf.114.1412403983110; Fri, 03 Oct 2014 23:26:23 -0700 (PDT)
MIME-Version: 1.0
Sender: czyborra@googlemail.com
Received: by 10.194.67.193 with HTTP; Fri, 3 Oct 2014 23:26:03 -0700 (PDT)
In-Reply-To: <542E8110.5050906@massar.ch>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch>
From: Roman Czyborra <roman@czyborra.com>
Date: Sat, 4 Oct 2014 08:26:03 +0200
X-Google-Sender-Auth: LK6rSIxti_TZIXsF_-1EskjNF6A
Message-ID: <CADu1F6cm=DtsOxU9=PNH+_acQimA=QsBdgZDAsKpbA84EFKydQ@mail.gmail.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
To: Jeroen Massar <jeroen@massar.ch>
Content-Type: multipart/alternative; boundary=047d7b45101ab15ac6050492ed7d
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/mPDB3WlGq7drBZZgBfLqkqNH3B4
Cc: Ole Troan <ot@cisco.com>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 04:54:28 -0000

--047d7b45101ab15ac6050492ed7d
Content-Type: text/plain; charset=UTF-8

<sarcasm>Yeah let us move all RFCs to historic that are not by default
turned on in Microsoft Excel.

One historic draft reminded us that a subset of the following techniques
are either not visible on Oettinger's desktop or generated unforeseen
insecurities to somebody and therefore obsolete.

So let us just outlaw the proposed standard technique introduced in 1998's
http://tools.ietf.org/html/rfc2460 for its fringe adoption after a decade
and the so-called internet technique introduced in 1981's
http://tools.ietf.org/html/rfc791 for its apparent social issues.

Once we detach from that 32bit|128bit stupidity to we will no longer
receive such nonsense:

Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1900:3001:11::2c])
	by new.woffs.de (8.14.4/8.14.4/Debian-4) with ESMTP id s93Avm7Q022176
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
	for <roman@czyborra.com>; Fri, 3 Oct 2014 12:57:50 +0200
Received: from bastion.ch.unfix.org (bastion.ch.unfix.org [46.20.246.101])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 621311AD034
 for <ipv6@ietf.org>; Fri,  3 Oct 2014 03:57:30 -0700 (PDT)
Received: from kami.ch.unfix.org
 (173-10-186-209-BusName-washingtonDC.hfc.comcastbusiness.net
 [173.10.186.209])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested) (Authenticated sender: jeroen)
 by bastion.ch.unfix.org (Postfix) with ESMTPSA id BD0A110069CE3;
 Fri,  3 Oct 2014 10:57:25 +0000 (UTC)
Message-ID: <542E8110.5050906@massar.ch>
Date: Fri, 03 Oct 2014 06:57:20 -0400
From: Jeroen Massar <jeroen@massar.ch>
Organization: http://www.massar.ch/net/


<real>Do the speed and security advantages of 2400:: no longer suffice to
outphase 0.0.0.0 and 2002:: so we need to actively wreck and stress
everything?  Or does 2002:: endanger out profit margins?


On Fri, Oct 3, 2014 at 12:57 PM, Jeroen Massar <jeroen@massar.ch> wrote:

> As some .gov agency is reminding us[1], it might be time to finally lay
> 6to4 to rest by making it historic.
>
> Can we revive:
>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>
> and finally make it into a BCP, marking 6to4 historic.
>
> That way, we can also get operators to wind down on 2002::/16 relays and
> give a clear signal that folks really should have native in 2014.
>
> Greets,
>  Jeroen
>
> [1] www.azdes.gov = 2002::cf6c:8846
>
> -------- Forwarded Message --------
> Subject: Re: 6to4 in Internet aaaa records
> Date: Fri, 03 Oct 2014 17:06:27 +1300
> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> CC: Jeroen Massar <jeroen@massar.ch>, IPv6 operators forum
> <ipv6-ops@lists.cluenet.de>
>
> [..]
> >> and of course also:
> >>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
> >>  (though that technically expired).
>
> 3 years ago that seemed premature. With recent progress in real IPv6,
> I'm wondering whether it isn't time to revive it. If so it should be
> changed to be a BCP that says "Don't do this" and also makes
> the proposed standard drafts Historic.
>
> But we do hear persistently that there are happy hobbyist and peer to peer
> users of 6to4. Using it offer web service for the Arizona Department of
> Economic Security is so wrong, though.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--047d7b45101ab15ac6050492ed7d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>&lt;sarcasm&gt;Yeah let us move all RFCs to historic =
that are not by default turned on in Microsoft Excel.</div><br>One historic=
 draft reminded us that a subset of the following techniques are either not=
 visible on Oettinger&#39;s desktop or generated unforeseen insecurities to=
 somebody and therefore obsolete.<br><br>So let us just outlaw the proposed=
 standard technique introduced in 1998&#39;s=C2=A0<a href=3D"http://tools.i=
etf.org/html/rfc2460">http://tools.ietf.org/html/rfc2460</a> for its fringe=
 adoption after a decade and the so-called internet technique introduced in=
 1981&#39;s <a href=3D"http://tools.ietf.org/html/rfc791">http://tools.ietf=
.org/html/rfc791</a> for its apparent social issues.<div><br></div><div>Onc=
e we detach from that 32bit|128bit stupidity to we will no longer receive s=
uch nonsense:</div><div><pre style=3D"color:rgb(0,0,0);word-wrap:break-word=
;white-space:pre-wrap">Received: from <a href=3D"http://mail.ietf.org">mail=
.ietf.org</a> (<a href=3D"http://mail.ietf.org">mail.ietf.org</a> [IPv6:200=
1:1900:3001:11::2c])
	by <a href=3D"http://new.woffs.de">new.woffs.de</a> (8.14.4/8.14.4/Debian-=
4) with ESMTP id s93Avm7Q022176
	(version=3DTLSv1/SSLv3 cipher=3DDHE-RSA-AES256-GCM-SHA384 bits=3D256 verif=
y=3DNO)
	for &lt;<a href=3D"mailto:roman@czyborra.com">roman@czyborra.com</a>&gt;; =
Fri, 3 Oct 2014 12:57:50 +0200
Received: from <a href=3D"http://bastion.ch.unfix.org">bastion.ch.unfix.org=
</a> (<a href=3D"http://bastion.ch.unfix.org">bastion.ch.unfix.org</a> [46.=
20.246.101])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by <a href=3D"http://ietfa.amsl.com">ietfa.amsl.com</a> (Postfix) with ESM=
TPS id 621311AD034
 for &lt;<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a>&gt;; Fri,  3 Oc=
t 2014 03:57:30 -0700 (PDT)
Received: from <a href=3D"http://kami.ch.unfix.org">kami.ch.unfix.org</a>
 (<a href=3D"http://173-10-186-209-BusName-washingtonDC.hfc.comcastbusiness=
.net">173-10-186-209-BusName-washingtonDC.hfc.comcastbusiness.net</a>
 [173.10.186.209])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested) (Authenticated sender: jeroen)
 by <a href=3D"http://bastion.ch.unfix.org">bastion.ch.unfix.org</a> (Postf=
ix) with ESMTPSA id BD0A110069CE3;
 Fri,  3 Oct 2014 10:57:25 +0000 (UTC)
Message-ID: &lt;<a href=3D"mailto:542E8110.5050906@massar.ch">542E8110.5050=
906@massar.ch</a>&gt;
Date: Fri, 03 Oct 2014 06:57:20 -0400
From: Jeroen Massar &lt;<a href=3D"mailto:jeroen@massar.ch">jeroen@massar.c=
h</a>&gt;
Organization: <a href=3D"http://www.massar.ch/net/">http://www.massar.ch/ne=
t/</a></pre></div><div><br></div><div>&lt;real&gt;Do the speed and security=
 advantages of 2400:: no longer suffice to outphase 0.0.0.0 and 2002:: so w=
e need to actively wreck and stress everything?=C2=A0 Or does 2002:: endang=
er out profit margins?</div><div><br></div></div><div class=3D"gmail_extra"=
><br><div class=3D"gmail_quote">On Fri, Oct 3, 2014 at 12:57 PM, Jeroen Mas=
sar <span dir=3D"ltr">&lt;<a href=3D"mailto:jeroen@massar.ch" target=3D"_bl=
ank">jeroen@massar.ch</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">As some .gov agency is reminding us[1], it might be time to finally lay<=
br>
6to4 to rest by making it historic.<br>
<br>
Can we revive:<br>
=C2=A0<a href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-histor=
ic-05" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-v6ops-6to4-t=
o-historic-05</a><br>
<br>
and finally make it into a BCP, marking 6to4 historic.<br>
<br>
That way, we can also get operators to wind down on 2002::/16 relays and<br=
>
give a clear signal that folks really should have native in 2014.<br>
<br>
Greets,<br>
=C2=A0Jeroen<br>
<br>
[1] <a href=3D"http://www.azdes.gov" target=3D"_blank">www.azdes.gov</a> =
=3D 2002::cf6c:8846<br>
<br>
-------- Forwarded Message --------<br>
Subject: Re: 6to4 in Internet aaaa records<br>
Date: Fri, 03 Oct 2014 17:06:27 +1300<br>
From: Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com">=
brian.e.carpenter@gmail.com</a>&gt;<br>
CC: Jeroen Massar &lt;<a href=3D"mailto:jeroen@massar.ch">jeroen@massar.ch<=
/a>&gt;, IPv6 operators forum<br>
&lt;<a href=3D"mailto:ipv6-ops@lists.cluenet.de">ipv6-ops@lists.cluenet.de<=
/a>&gt;<br>
<br>
[..]<br>
&gt;&gt; and of course also:<br>
&gt;&gt;=C2=A0 <a href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-6to4-=
to-historic-05" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-v6o=
ps-6to4-to-historic-05</a><br>
&gt;&gt;=C2=A0 (though that technically expired).<br>
<br>
3 years ago that seemed premature. With recent progress in real IPv6,<br>
I&#39;m wondering whether it isn&#39;t time to revive it. If so it should b=
e<br>
changed to be a BCP that says &quot;Don&#39;t do this&quot; and also makes<=
br>
the proposed standard drafts Historic.<br>
<br>
But we do hear persistently that there are happy hobbyist and peer to peer<=
br>
users of 6to4. Using it offer web service for the Arizona Department of<br>
Economic Security is so wrong, though.<br>
<br>
--------------------------------------------------------------------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
--------------------------------------------------------------------<br>
</blockquote></div><br></div>

--047d7b45101ab15ac6050492ed7d--


From nobody Sun Oct  5 23:00:16 2014
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7191A1B3E for <ipv6@ietfa.amsl.com>; Sun,  5 Oct 2014 23:00:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.65
X-Spam-Level: 
X-Spam-Status: No, score=-0.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514] autolearn=ham
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 MsIv4U9SovXa for <ipv6@ietfa.amsl.com>; Sun,  5 Oct 2014 23:00:09 -0700 (PDT)
Received: from mail-ie0-x22f.google.com (mail-ie0-x22f.google.com [IPv6:2607:f8b0:4001:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26F861A1A03 for <ipv6@ietf.org>; Sun,  5 Oct 2014 23:00:09 -0700 (PDT)
Received: by mail-ie0-f175.google.com with SMTP id x19so2663188ier.6 for <ipv6@ietf.org>; Sun, 05 Oct 2014 23:00:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=EwItVlsTIpSclbDh4pbJh94aaEeTHZA/ijTRhObL/jU=; b=n5Qzw+XLy2MdPeC2+meU+PP125Zw+PQZ3QZlxob2s7F23eO1q80P415NH4vDWqJdEE knEHWeQ7mN+l9W9Ztu6BhHJVfatD78QjLNoAKhWAYSzZsgoOaQ7xFqlAxPnbd/dO4Vy1 OEKJApsuoGIYdoCdg0bsT6+YRGicUiIH8S5WHagd+z0S+M39lQZyfMAHWVvSAHfEjELo X0+xkRZHG9BLOiDpik/dR6yoLaymXcieSOMN4OwgTItN85l4i19jwswhgcmJ1czxsQjU uQIO5seyt6iEOCsW0AOZBBOGd6lYOujDD5Uqss5IYXNQ24sjGK003RDpGp/3jf6Cavwj jOHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=EwItVlsTIpSclbDh4pbJh94aaEeTHZA/ijTRhObL/jU=; b=HOdEmMnyt8T9AEUw4nA9DEWoOtSGP8h0wjHrcyX2ManmYeoUibSZgoVB1y7PccFXNM WdHE3bspSQnyXJcbj0fUpZORDQ/GxS3SbTol0Buhm2htGCVcnyDYf9yh534NJkGDqici yT2YOvMROnCyKdOZ+gMORFQUB7JUNARBOVSX63dgpb5NHRuAf7pX2bnuHZvKd6AC2oD3 UmF8qNbjXsV3M/C40i4+bvse1/aQhJ3e0e47bzrgx4WtpDe3DwJiItI/wVc7B+4GnXkD n+x3NPVwi97sjgV1JrfTfDd33oCtuZCiJSbXBLQAzK6g6fUccpRUMMXfhOeliZ2T3sCZ iD4g==
X-Gm-Message-State: ALoCoQkZDnmGZCcbkKJEf18dCk40TUUEYRkIPAGotVHhC+sT+0XQkCifgeP5AXqvD8iH9RYbx4N9
X-Received: by 10.42.114.203 with SMTP id h11mr373085icq.86.1412575208290; Sun, 05 Oct 2014 23:00:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.24.144 with HTTP; Sun, 5 Oct 2014 22:59:48 -0700 (PDT)
In-Reply-To: <CADu1F6cm=DtsOxU9=PNH+_acQimA=QsBdgZDAsKpbA84EFKydQ@mail.gmail.com>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <CADu1F6cm=DtsOxU9=PNH+_acQimA=QsBdgZDAsKpbA84EFKydQ@mail.gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 6 Oct 2014 14:59:48 +0900
Message-ID: <CAKD1Yr0A+vPzLrGduVgfm0r5buA3r8Sb+86W_UVRT9A5MnaXwg@mail.gmail.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
To: Roman Czyborra <roman@czyborra.com>
Content-Type: multipart/alternative; boundary=20cf303ea4be825b150504bacb6d
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/-lPn4YlsdiImgmhzY0HISGuGzoQ
Cc: Ole Troan <ot@cisco.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 06:00:13 -0000

--20cf303ea4be825b150504bacb6d
Content-Type: text/plain; charset=UTF-8

Wow, I haven't seen such a negative email in quite a long time.

On Sat, Oct 4, 2014 at 3:26 PM, Roman Czyborra <roman@czyborra.com> wrote:

> <sarcasm>Yeah let us move all RFCs to historic that are not by default
> turned on in Microsoft Excel.
>
> One historic draft reminded us that a subset of the following techniques
> are either not visible on Oettinger's desktop or generated unforeseen
> insecurities to somebody and therefore obsolete.
>
> So let us just outlaw the proposed standard technique introduced in 1998's
> http://tools.ietf.org/html/rfc2460 for its fringe adoption after a decade
> and the so-called internet technique introduced in 1981's
> http://tools.ietf.org/html/rfc791 for its apparent social issues.
>
> Once we detach from that 32bit|128bit stupidity to we will no longer
> receive such nonsense:
>
> Received: from mail.ietf.org (mail.ietf.org [IPv6:2001:1900:3001:11::2c])
> 	by new.woffs.de (8.14.4/8.14.4/Debian-4) with ESMTP id s93Avm7Q022176
> 	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO)
> 	for <roman@czyborra.com>; Fri, 3 Oct 2014 12:57:50 +0200
> Received: from bastion.ch.unfix.org (bastion.ch.unfix.org [46.20.246.101])
>  (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
>  (No client certificate requested)
>  by ietfa.amsl.com (Postfix) with ESMTPS id 621311AD034
>  for <ipv6@ietf.org>; Fri,  3 Oct 2014 03:57:30 -0700 (PDT)
> Received: from kami.ch.unfix.org
>  (173-10-186-209-BusName-washingtonDC.hfc.comcastbusiness.net
>  [173.10.186.209])
>  (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
>  (No client certificate requested) (Authenticated sender: jeroen)
>  by bastion.ch.unfix.org (Postfix) with ESMTPSA id BD0A110069CE3;
>  Fri,  3 Oct 2014 10:57:25 +0000 (UTC)
> Message-ID: <542E8110.5050906@massar.ch>
> Date: Fri, 03 Oct 2014 06:57:20 -0400
> From: Jeroen Massar <jeroen@massar.ch>
> Organization: http://www.massar.ch/net/
>
>
> <real>Do the speed and security advantages of 2400:: no longer suffice to
> outphase 0.0.0.0 and 2002:: so we need to actively wreck and stress
> everything?  Or does 2002:: endanger out profit margins?
>
>
> On Fri, Oct 3, 2014 at 12:57 PM, Jeroen Massar <jeroen@massar.ch> wrote:
>
>> As some .gov agency is reminding us[1], it might be time to finally lay
>> 6to4 to rest by making it historic.
>>
>> Can we revive:
>>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>>
>> and finally make it into a BCP, marking 6to4 historic.
>>
>> That way, we can also get operators to wind down on 2002::/16 relays and
>> give a clear signal that folks really should have native in 2014.
>>
>> Greets,
>>  Jeroen
>>
>> [1] www.azdes.gov = 2002::cf6c:8846
>>
>> -------- Forwarded Message --------
>> Subject: Re: 6to4 in Internet aaaa records
>> Date: Fri, 03 Oct 2014 17:06:27 +1300
>> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
>> CC: Jeroen Massar <jeroen@massar.ch>, IPv6 operators forum
>> <ipv6-ops@lists.cluenet.de>
>>
>> [..]
>> >> and of course also:
>> >>  http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>> >>  (though that technically expired).
>>
>> 3 years ago that seemed premature. With recent progress in real IPv6,
>> I'm wondering whether it isn't time to revive it. If so it should be
>> changed to be a BCP that says "Don't do this" and also makes
>> the proposed standard drafts Historic.
>>
>> But we do hear persistently that there are happy hobbyist and peer to peer
>> users of 6to4. Using it offer web service for the Arizona Department of
>> Economic Security is so wrong, though.
>>
>> --------------------------------------------------------------------
>> 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
> --------------------------------------------------------------------
>
>

--20cf303ea4be825b150504bacb6d
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Wow, I haven&#39;t seen such a negative email in quite a l=
ong time.</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On=
 Sat, Oct 4, 2014 at 3:26 PM, Roman Czyborra <span dir=3D"ltr">&lt;<a href=
=3D"mailto:roman@czyborra.com" target=3D"_blank">roman@czyborra.com</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>&lt;=
sarcasm&gt;Yeah let us move all RFCs to historic that are not by default tu=
rned on in Microsoft Excel.</div><br>One historic draft reminded us that a =
subset of the following techniques are either not visible on Oettinger&#39;=
s desktop or generated unforeseen insecurities to somebody and therefore ob=
solete.<br><br>So let us just outlaw the proposed standard technique introd=
uced in 1998&#39;s=C2=A0<a href=3D"http://tools.ietf.org/html/rfc2460" targ=
et=3D"_blank">http://tools.ietf.org/html/rfc2460</a> for its fringe adoptio=
n after a decade and the so-called internet technique introduced in 1981&#3=
9;s <a href=3D"http://tools.ietf.org/html/rfc791" target=3D"_blank">http://=
tools.ietf.org/html/rfc791</a> for its apparent social issues.<div><br></di=
v><div>Once we detach from that 32bit|128bit stupidity to we will no longer=
 receive such nonsense:</div><div><pre style=3D"color:rgb(0,0,0);word-wrap:=
break-word;white-space:pre-wrap">Received: from <a href=3D"http://mail.ietf=
.org" target=3D"_blank">mail.ietf.org</a> (<a href=3D"http://mail.ietf.org"=
 target=3D"_blank">mail.ietf.org</a> [IPv6:2001:1900:3001:11::2c])
	by <a href=3D"http://new.woffs.de" target=3D"_blank">new.woffs.de</a> (8.1=
4.4/8.14.4/Debian-4) with ESMTP id s93Avm7Q022176
	(version=3DTLSv1/SSLv3 cipher=3DDHE-RSA-AES256-GCM-SHA384 bits=3D256 verif=
y=3DNO)
	for &lt;<a href=3D"mailto:roman@czyborra.com" target=3D"_blank">roman@czyb=
orra.com</a>&gt;; Fri, 3 Oct 2014 12:57:50 +0200
Received: from <a href=3D"http://bastion.ch.unfix.org" target=3D"_blank">ba=
stion.ch.unfix.org</a> (<a href=3D"http://bastion.ch.unfix.org" target=3D"_=
blank">bastion.ch.unfix.org</a> [46.20.246.101])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by <a href=3D"http://ietfa.amsl.com" target=3D"_blank">ietfa.amsl.com</a> =
(Postfix) with ESMTPS id 621311AD034
 for &lt;<a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">ipv6@ietf.org</=
a>&gt;; Fri,  3 Oct 2014 03:57:30 -0700 (PDT)
Received: from <a href=3D"http://kami.ch.unfix.org" target=3D"_blank">kami.=
ch.unfix.org</a>
 (<a href=3D"http://173-10-186-209-BusName-washingtonDC.hfc.comcastbusiness=
.net" target=3D"_blank">173-10-186-209-BusName-washingtonDC.hfc.comcastbusi=
ness.net</a>
 [173.10.186.209])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (No client certificate requested) (Authenticated sender: jeroen)
 by <a href=3D"http://bastion.ch.unfix.org" target=3D"_blank">bastion.ch.un=
fix.org</a> (Postfix) with ESMTPSA id BD0A110069CE3;
 Fri,  3 Oct 2014 10:57:25 +0000 (UTC)
Message-ID: &lt;<a href=3D"mailto:542E8110.5050906@massar.ch" target=3D"_bl=
ank">542E8110.5050906@massar.ch</a>&gt;
Date: Fri, 03 Oct 2014 06:57:20 -0400
From: Jeroen Massar &lt;<a href=3D"mailto:jeroen@massar.ch" target=3D"_blan=
k">jeroen@massar.ch</a>&gt;
Organization: <a href=3D"http://www.massar.ch/net/" target=3D"_blank">http:=
//www.massar.ch/net/</a></pre></div><div><br></div><div>&lt;real&gt;Do the =
speed and security advantages of 2400:: no longer suffice to outphase 0.0.0=
.0 and 2002:: so we need to actively wreck and stress everything?=C2=A0 Or =
does 2002:: endanger out profit margins?</div><div><br></div></div><div cla=
ss=3D"HOEnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Fri, Oct 3, 2014 at 12:57 PM, Jeroen Massar <span dir=
=3D"ltr">&lt;<a href=3D"mailto:jeroen@massar.ch" target=3D"_blank">jeroen@m=
assar.ch</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">As some =
.gov agency is reminding us[1], it might be time to finally lay<br>
6to4 to rest by making it historic.<br>
<br>
Can we revive:<br>
=C2=A0<a href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-histor=
ic-05" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-v6ops-6to4-t=
o-historic-05</a><br>
<br>
and finally make it into a BCP, marking 6to4 historic.<br>
<br>
That way, we can also get operators to wind down on 2002::/16 relays and<br=
>
give a clear signal that folks really should have native in 2014.<br>
<br>
Greets,<br>
=C2=A0Jeroen<br>
<br>
[1] <a href=3D"http://www.azdes.gov" target=3D"_blank">www.azdes.gov</a> =
=3D 2002::cf6c:8846<br>
<br>
-------- Forwarded Message --------<br>
Subject: Re: 6to4 in Internet aaaa records<br>
Date: Fri, 03 Oct 2014 17:06:27 +1300<br>
From: Brian E Carpenter &lt;<a href=3D"mailto:brian.e.carpenter@gmail.com" =
target=3D"_blank">brian.e.carpenter@gmail.com</a>&gt;<br>
CC: Jeroen Massar &lt;<a href=3D"mailto:jeroen@massar.ch" target=3D"_blank"=
>jeroen@massar.ch</a>&gt;, IPv6 operators forum<br>
&lt;<a href=3D"mailto:ipv6-ops@lists.cluenet.de" target=3D"_blank">ipv6-ops=
@lists.cluenet.de</a>&gt;<br>
<br>
[..]<br>
&gt;&gt; and of course also:<br>
&gt;&gt;=C2=A0 <a href=3D"http://tools.ietf.org/html/draft-ietf-v6ops-6to4-=
to-historic-05" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-v6o=
ps-6to4-to-historic-05</a><br>
&gt;&gt;=C2=A0 (though that technically expired).<br>
<br>
3 years ago that seemed premature. With recent progress in real IPv6,<br>
I&#39;m wondering whether it isn&#39;t time to revive it. If so it should b=
e<br>
changed to be a BCP that says &quot;Don&#39;t do this&quot; and also makes<=
br>
the proposed standard drafts Historic.<br>
<br>
But we do hear persistently that there are happy hobbyist and peer to peer<=
br>
users of 6to4. Using it offer web service for the Arizona Department of<br>
Economic Security is so wrong, though.<br>
<br>
--------------------------------------------------------------------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org" target=3D"_blank">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
--------------------------------------------------------------------<br>
</blockquote></div><br></div>
</div></div><br>-----------------------------------------------------------=
---------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
--------------------------------------------------------------------<br>
<br></blockquote></div><br></div>

--20cf303ea4be825b150504bacb6d--


From nobody Mon Oct  6 00:43:33 2014
Return-Path: <ek@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4ECD1A1B66 for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 00:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level: 
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 cUxSuzzGCWPB for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 00:31:07 -0700 (PDT)
Received: from mail-qg0-x22b.google.com (mail-qg0-x22b.google.com [IPv6:2607:f8b0:400d:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 493981A1B60 for <ipv6@ietf.org>; Mon,  6 Oct 2014 00:31:07 -0700 (PDT)
Received: by mail-qg0-f43.google.com with SMTP id j107so3345039qga.16 for <ipv6@ietf.org>; Mon, 06 Oct 2014 00:31:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=D4o//n+3JBHUtujDZ97cFhx0j0IFUuh5j4TVV/DmA+I=; b=e+lGKnXEzSEqd0XY9oIAuXNDFFVeeic0U/FFiPNyrFBFDgJc8+fSfb/WYihJ9bTIuk AKO/krKSpVuQi/Jqz8QyUkwmJP8Ez6c7oIzPiO3MJ/iZj36ltvk6t6Z6H+HYXtYwzy0K 1j3kNSmPs++kX08X03zD9Zm71fUxt5nim8sMsLUzCpgde7fop4NxXvQ3FrDfvhzkTk3L Ai8JYn4w1k5nC7DA5gOtbXHNyK+Ki9HatmxThLKnw8msPaCTv3Bghb7i7JbixpKQf9PW Q8vpec7lIk6ghJZ3Npa1h/X9NOnxwxJGipdlwG7352XLYUuEn/YCqx8QVhjT7Z1knmtk QfGw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=D4o//n+3JBHUtujDZ97cFhx0j0IFUuh5j4TVV/DmA+I=; b=G6m7nCvj2K9rrT75vz6uomU/YKHb/lo7TY3Le/sAnxDPvJpyTQpyKRAjm94dn2slQJ 6peZvpEtbl/h8MQoLgi3ovm4f2IT3vkgjjqMM9y5Fu27681IcLLRnG7UtJRlDAVt06wJ 1pi0Ga+j16mpYUCItm0jZNBXFlw9nLpXxZtYk6C/weCj7TCU49AgKKNziA7WF4UUMyZF 59WhILH6fw8Y0HXYKlQbwLKuZooYsBhSxXHvOCHtponBQPJGHy/2t5NMOn6zT0i4iTaN +BEuaxKEs3nRPlLo58WnfjXYFFuLfgz3ONGgOFkht37zM+vqx/9X8I7ItY6JXMyoxmBa rh6A==
X-Gm-Message-State: ALoCoQlaENXS4FuIwBlTit90Kx16stIF1ogfbmgyKFgfcuLRv11g/wv0UMQXFvoZFHjDgV7UCVBN
X-Received: by 10.140.42.138 with SMTP id c10mr25629105qga.9.1412580666414; Mon, 06 Oct 2014 00:31:06 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.80.65 with HTTP; Mon, 6 Oct 2014 00:30:46 -0700 (PDT)
In-Reply-To: <542F2C1E.4090909@acm.org>
References: <407DEA57-2807-44A5-8936-45B20CDB87C0@employees.org> <7DDF678F-1E09-4016-894C-6F16C2215859@employees.org> <542F2C1E.4090909@acm.org>
From: Erik Kline <ek@google.com>
Date: Mon, 6 Oct 2014 16:30:46 +0900
Message-ID: <CAAedzxpo-yn=4NObnZ7XbgAAQTkRozDPxHzu2Ugq4x123=tuEA@mail.gmail.com>
Subject: Re: Adoption call of draft-halpern-6man-nd-pre-resolve-addr for 6MAN
To: Erik Nordmark <nordmark@acm.org>
Content-Type: multipart/alternative; boundary=001a1139b876d6c87c0504bc10fd
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/0J6UTbwYqwydpfzUxuH5ctaK_MA
X-Mailman-Approved-At: Mon, 06 Oct 2014 00:43:30 -0700
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 07:31:13 -0000

--001a1139b876d6c87c0504bc10fd
Content-Type: text/plain; charset=UTF-8

>
>
> Given that *plus* the claimed IPR, I don't see why the WG needs to spend
> time on this.
> It might be useful to document this behavior that Ericsson as implemented
> in an independent submission informational document.
>

Agreed.

--001a1139b876d6c87c0504bc10fd
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex"><br>
Given that *plus* the claimed IPR, I don&#39;t see why the WG needs to spen=
d time on this.<br>
It might be useful to document this behavior that Ericsson as implemented i=
n an independent submission informational document.<br></blockquote><div><b=
r></div><div>Agreed.=C2=A0</div></div></div></div>

--001a1139b876d6c87c0504bc10fd--


From nobody Mon Oct  6 04:44:35 2014
Return-Path: <lear@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE51F1A1B55 for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 04:44:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -13.773
X-Spam-Level: 
X-Spam-Status: No, score=-13.773 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 mJswfE_z4PpU for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 04:44:31 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F32341A0054 for <ipv6@ietf.org>; Mon,  6 Oct 2014 04:44:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2276; q=dns/txt; s=iport; t=1412595871; x=1413805471; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=cUBM82QLj9GD2BLjtpoAnEQDsGpN1f+j/4NVxWt0xVU=; b=aLA/k0737VkJhbAGqzOlCUpgFu9sQPFYbbcoTtZ87Iwgg8ZfUZwMks6U hVmLGkRkXIG0CyDXm/61u9GnHkNvIadz8qCLHDO6S336h0+3iLUIqrONi 9CRQ4qzNwpyCLfoMjOYPsBaploKVXBdj4rfFL3y+KJ2DuciT+V67g3l0Z I=;
X-Files: signature.asc : 486
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqgEAF1/MlStJssW/2dsb2JhbABfg2FYgwLJGIdRAoEcAXuEBAEBBCMmLwEQCxgJFgsCAgkDAgECAUUGAQwBBwEBiDqrbZQ3AReQRQcJgm6BVAEEk3+BTGWHDoFohXaOIoNlOy+CSgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,663,1406592000";  d="asc'?scan'208";a="197295253"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 06 Oct 2014 11:44:29 +0000
Received: from [10.61.104.94] (dhcp-10-61-104-94.cisco.com [10.61.104.94]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s96BiST9011250; Mon, 6 Oct 2014 11:44:28 GMT
Message-ID: <5432809C.1090608@cisco.com>
Date: Mon, 06 Oct 2014 13:44:28 +0200
From: Eliot Lear <lear@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Erik Nygren <erik+ietf@nygren.org>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com> <543047A2.8020804@gmail.com>
In-Reply-To: <543047A2.8020804@gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3utiCcXt4ABVEfcBdorVvbPeGfKuGHleS"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/MOHHs3lJbaFEz96zFMgOPfkvY7o
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Tore Anderson <tore@fud.no>, 6man <ipv6@ietf.org>, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 11:44:32 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--3utiCcXt4ABVEfcBdorVvbPeGfKuGHleS
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,

On 10/4/14, 9:16 PM, Brian E Carpenter wrote:
>
>
> +1.
>
> I run into the same issue.
> There's another issue here that I see from time to time in under-inform=
ed
> discussion forums such as www.theregister.co.uk/ :
>
> Some people believe that anybody can get an IPv6 address by sticking
> their IPv4 address after a magic prefix. ::/96 is a popular choice
> for that magic prefix, and judging by the azdes.gov some people
> believe that 2002::/96 is equally magic.
>
> Killing that meme would help quite a bit.
>
> That said, I'll repeat that I think a formal deprecation is
> now reasonable, but it needs a bit more logic in it than just
> declaring several RFCs Historic.
>
> For example, it would not help anybody to switch off correctly
> working return 6to4 relays (i.e. boxes that announce 2002::/96).
> On the other hand, if all forward relays (boxes that announce
> 192.88.99.1) were switched off, Anycast 6to4 would cease working
> immediately and the resulting problems would vanish.
>
> In fact, it is really only RFC 3068 that needs deprecating,
> because that is where the damage comes from. Peer to peer
> 6to4 doesn't hurt anybody afaik.
>

Forgive me for maybe having missed it, but is there a willing draft
author?  I know Ole wrote the original referenced document...

Eliot


--3utiCcXt4ABVEfcBdorVvbPeGfKuGHleS
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)

iQEcBAEBAgAGBQJUMoCdAAoJEIe2a0bZ0nozVGgIALNOzZqWdohzDDU7w+lcX+tg
fZLewc2+J9vqDK82ZVF7mF2HWk7Vdyx8GEwREH3nSotloPPWylTMpkHCe9eTwED8
Sqznz8n5PHHUOMqoew/8yn+j4g+yNQgSLT7SyQkpf+9OQliaO31oidkSaQZK3+o1
bek9FnZuoNTOvgHhw4vfOYRvDoPodiyZ/UdrY2cC259dE2dlDoxPC8LwMCuU8SE6
Yo2Y/6Z0R+dTQCqHFKpqWNfCuW5ticO8BNBsexzsGsMJ0wCqYDChKRNrCPTSAmt7
F355uxEzWdZLGHoljD1nK6oB/t/EkNr/l+A3DNyNsjmntRI9bXLDlF96M8XA1r8=
=ETVA
-----END PGP SIGNATURE-----

--3utiCcXt4ABVEfcBdorVvbPeGfKuGHleS--


From nobody Mon Oct  6 12:24:28 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40DD91A88F9 for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 12:24:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 RFSep0NgZ9mu for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 12:24:21 -0700 (PDT)
Received: from mail-pd0-x229.google.com (mail-pd0-x229.google.com [IPv6:2607:f8b0:400e:c02::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61AA21A891F for <ipv6@ietf.org>; Mon,  6 Oct 2014 12:24:21 -0700 (PDT)
Received: by mail-pd0-f169.google.com with SMTP id w10so3751171pde.28 for <ipv6@ietf.org>; Mon, 06 Oct 2014 12:24:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=blh0SyoYMCdB32BIKUPWaM8EqqYm9k9JIyHsNO73ivs=; b=PVr81vfmBfAnHNBMZ/3tbAIYwQlFdAJjoBL1p6YWFJMsW3XVYbhs9XMaRV2nJVlHuI dJTOAqsq7YrujhjMUSkojLpY0qmHBWHc4K24TgvqqkWOrpFtxwrmI4gGh4y+s1N4fIvx x2ruhQVzL9Epb3z6vvxmQSMQMbEimIFlpQV4BqhM2DqmCIfrT1g9vFC1hULTXZO4g+dW BqYA0pKkTwW3dJCkgfxhPAeOvKkGixNvKYuojm1JJKMIf3su4IE5XonNeobzxG2/rQh0 HG2gvLH7XOzQpByvJU1ThXExCaRgTHonmpNxVHNPnDugRsCS+OcPtp+sva19F2HkFbyk 9wsA==
X-Received: by 10.70.37.165 with SMTP id z5mr20363686pdj.13.1412623461101; Mon, 06 Oct 2014 12:24:21 -0700 (PDT)
Received: from [192.168.178.23] (116.195.69.111.dynamic.snap.net.nz. [111.69.195.116]) by mx.google.com with ESMTPSA id kk10sm11818951pdb.63.2014.10.06.12.24.17 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 Oct 2014 12:24:20 -0700 (PDT)
Message-ID: <5432EC61.4060806@gmail.com>
Date: Tue, 07 Oct 2014 08:24:17 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Eliot Lear <lear@cisco.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com> <543047A2.8020804@gmail.com> <5432809C.1090608@cisco.com>
In-Reply-To: <5432809C.1090608@cisco.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/uTxLl6HdnIfL9Jo6yUdLT7hXD7E
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Tore Anderson <tore@fud.no>, 6man <ipv6@ietf.org>, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 19:24:24 -0000

On 07/10/2014 00:44, Eliot Lear wrote:
> Hi,
> 
> On 10/4/14, 9:16 PM, Brian E Carpenter wrote:
>>
>> +1.
>>
>> I run into the same issue.
>> There's another issue here that I see from time to time in under-informed
>> discussion forums such as www.theregister.co.uk/ :
>>
>> Some people believe that anybody can get an IPv6 address by sticking
>> their IPv4 address after a magic prefix. ::/96 is a popular choice
>> for that magic prefix, and judging by the azdes.gov some people
>> believe that 2002::/96 is equally magic.
>>
>> Killing that meme would help quite a bit.
>>
>> That said, I'll repeat that I think a formal deprecation is
>> now reasonable, but it needs a bit more logic in it than just
>> declaring several RFCs Historic.
>>
>> For example, it would not help anybody to switch off correctly
>> working return 6to4 relays (i.e. boxes that announce 2002::/96).
>> On the other hand, if all forward relays (boxes that announce
>> 192.88.99.1) were switched off, Anycast 6to4 would cease working
>> immediately and the resulting problems would vanish.
>>
>> In fact, it is really only RFC 3068 that needs deprecating,
>> because that is where the damage comes from. Peer to peer
>> 6to4 doesn't hurt anybody afaik.
>>
> 
> Forgive me for maybe having missed it, but is there a willing draft
> author?  I know Ole wrote the original referenced document...

I would be willing to work on this with Ole. But it would be nice
to get some actual facts about residual peer-to-peer usage. (We
already know that client-to-server usage of anycast 6to4 is
falling off.)

    Brian


From nobody Mon Oct  6 12:46:23 2014
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC0D11A1A47 for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 12:46:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.737
X-Spam-Level: 
X-Spam-Status: No, score=-4.737 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 62fbkSZ0Wjxe for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 12:46:19 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C26411A1B7F for <ipv6@ietf.org>; Mon,  6 Oct 2014 12:46:19 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 17857A1; Mon,  6 Oct 2014 21:46:18 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1412624778; bh=nYlJvS3MO0YTyrBSkZDD2U+qWZnxftKIVYi9/RHPYKw=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=SW30mkp+JW6k1mipr6Jg1ORgEEK1DrF0F1oxbRjSm/vNfB62SsM2GO4WKPFdPeXyF cvaVxUT94yoUk5v96xMjMW957u/L4MFMeiryu5UyE9bwt6IljTzqa3TzQr/+kx6pgG 2b2MgDiWA+n9dpxRmEH5KXJA7tlXJej7zEPLqCZU=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 075939F; Mon,  6 Oct 2014 21:46:18 +0200 (CEST)
Date: Mon, 6 Oct 2014 21:46:17 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
In-Reply-To: <5432EC61.4060806@gmail.com>
Message-ID: <alpine.DEB.2.02.1410062142550.14735@uplift.swm.pp.se>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com> <543047A2.8020804@gmail.com> <5432809C.1090608@cisco.com> <5432EC61.4060806@gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/xna_qoIZJKg0PL90QjmFAt15e88
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 19:46:21 -0000

On Tue, 7 Oct 2014, Brian E Carpenter wrote:

> I would be willing to work on this with Ole. But it would be nice to get 
> some actual facts about residual peer-to-peer usage. (We already know 
> that client-to-server usage of anycast 6to4 is falling off.)

My guess is that the best people here to ask would be the IX operators who 
do sFlow analysis, I don't see how else you could analyse IPv4 proto 41 
traffic and count the ratio of traffic that has both src and dst addresses 
in the 2002::/16 within them as opposed to other traffic.

Because that's what we're talking about, right?

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Oct  6 12:56:32 2014
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B4B91A8917 for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 12:56:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.437
X-Spam-Level: 
X-Spam-Status: No, score=-2.437 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 L-7iylW9OAca for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 12:56:31 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF1ED1A8940 for <ipv6@ietf.org>; Mon,  6 Oct 2014 12:56:30 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id D737AA1; Mon,  6 Oct 2014 21:56:28 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1412625388; bh=LCxybuPNs0LFhVDGuRr2raws0LzDMY57E4vkM8+UqCw=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=1wfCc7tkOp2TNIp1VeV3GfVDSDDydlpl7K49KMFCCUDLfV2/LrHgrtLHEZyKPFup4 NkixkbAe8Ktq7b9T7DDeIP75I1Kjf7QEmBITaaWtT6s29yvhIHit/ioTiJ2lEJPbd2 OoEI7wjcF4lxuugBLyg8DWzlQ3EKAtDyfNCQ1Q+w=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id CAB349F; Mon,  6 Oct 2014 21:56:28 +0200 (CEST)
Date: Mon, 6 Oct 2014 21:56:28 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
In-Reply-To: <alpine.DEB.2.02.1410062142550.14735@uplift.swm.pp.se>
Message-ID: <alpine.DEB.2.02.1410062155090.14735@uplift.swm.pp.se>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com> <543047A2.8020804@gmail.com> <5432809C.1090608@cisco.com> <5432EC61.4060806@gmail.com> <alpine.DEB.2.02.1410062142550.14735@uplift.swm.pp.se>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/EPknKj0YrbkhUEZJB7gDfWkevy4
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 19:56:32 -0000

On Mon, 6 Oct 2014, Mikael Abrahamsson wrote:

> My guess is that the best people here to ask would be the IX operators 
> who do sFlow analysis, I don't see how else you could analyse IPv4 proto 
> 41 traffic and count the ratio of traffic that has both src and dst 
> addresses in the 2002::/16 within them as opposed to other traffic.

I asked around, and at least one IX doesn't look beyond L2 headers with 
their sFlow, so that won't help.

Basically, I don't see how we can easily monitor this without some 
operators giving this to us, and that might just capture a few reagions, 
and might not give a global view.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Oct  6 13:16:36 2014
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D1341A876F for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 13:16:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 eO4__QZRwkJE for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 13:16:33 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C41E1A8953 for <ipv6@ietf.org>; Mon,  6 Oct 2014 13:16:33 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 1368F8811D for <ipv6@ietf.org>; Mon,  6 Oct 2014 13:16:33 -0700 (PDT)
Received: from clemson.local (unknown [76.21.129.88]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id C851B1368153 for <ipv6@ietf.org>; Mon,  6 Oct 2014 13:16:32 -0700 (PDT)
Message-ID: <5432F89E.8040008@innovationslab.net>
Date: Mon, 06 Oct 2014 16:16:30 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: Adoption call of draft-halpern-6man-nd-pre-resolve-addr for 6MAN
References: <407DEA57-2807-44A5-8936-45B20CDB87C0@employees.org> <7DDF678F-1E09-4016-894C-6F16C2215859@employees.org> <542F2C1E.4090909@acm.org> <CAAedzxpo-yn=4NObnZ7XbgAAQTkRozDPxHzu2Ugq4x123=tuEA@mail.gmail.com>
In-Reply-To: <CAAedzxpo-yn=4NObnZ7XbgAAQTkRozDPxHzu2Ugq4x123=tuEA@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6Dg3gmuevRrr66rH0RD8omItjUbCbWqJQ"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/SKPpHlPIi_OwE_Wuj1JAWEv3J08
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 20:16:34 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--6Dg3gmuevRrr66rH0RD8omItjUbCbWqJQ
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



On 10/6/14 3:30 AM, Erik Kline wrote:
>>
>>
>> Given that *plus* the claimed IPR, I don't see why the WG needs to spe=
nd
>> time on this.
>> It might be useful to document this behavior that Ericsson as implemen=
ted
>> in an independent submission informational document.
>>
>=20
> Agreed.
>=20

As a data point, the IESG has been encouraging the use of the ISE for
documents that describe what companies have implemented.  And since this
document is listed Informational, that approach makes more sense to me.

Regards,
Brian



--6Dg3gmuevRrr66rH0RD8omItjUbCbWqJQ
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJUMvieAAoJEBOZRqCi7goqwI4IAI/VdFuJ7VjDytj7ykHkkcfA
C09IfyAZxs8dLvU/X7bS4OhBmmtNw6B7347JU4TcTJWifOJ8qmwKaw/R0yM6lEgx
RpQW1WoFNOfIkwrG2O30lP/sE+nNLMod1QWExEc1hzPyYz8a0VpvBc5p4opc40MH
qhXr4EMJKT5bjL1vRp/4r2cnEapQKzFPZdLNlJPkw/LUgNoKt8nvVACIHKl5fT7o
bQjTZkPpy4MG9aV6mTOwrAnS64bcfMn3C4OAeoZg78An4kt1yzjIlFDA+f6bWx/O
5UZPkCDjMVfoADDdLL5L8dEsnMtY72LHHhXiI2AJ+6kUTzbK5HZknGpKPnbLkvY=
=qaOk
-----END PGP SIGNATURE-----

--6Dg3gmuevRrr66rH0RD8omItjUbCbWqJQ--


From nobody Mon Oct  6 13:39:02 2014
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9E6B1A89AE for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 13:38:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.952
X-Spam-Level: 
X-Spam-Status: No, score=0.952 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DATE_IN_PAST_24_48=1.34, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514] autolearn=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 0ydzT9hwG4j3 for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 13:38:58 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DBE01A8967 for <ipv6@ietf.org>; Mon,  6 Oct 2014 13:38:58 -0700 (PDT)
Received: from [2001:5c0:1000:a::805] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fernando@gont.com.ar>) id 1XbF3U-0000LM-2C; Mon, 06 Oct 2014 22:38:52 +0200
Message-ID: <54317DCD.90907@gont.com.ar>
Date: Sun, 05 Oct 2014 14:20:13 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>,  Erik Nygren <erik+ietf@nygren.org>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com> <543047A2.8020804@gmail.com>
In-Reply-To: <543047A2.8020804@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/gg8Dd9mbGz1dMTKEyjogQBEwJIE
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Tore Anderson <tore@fud.no>, 6man <ipv6@ietf.org>, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 20:39:00 -0000

Hi, Brian,

On 10/04/2014 04:16 PM, Brian E Carpenter wrote:
> There's another issue here that I see from time to time in under-informed
> discussion forums such as www.theregister.co.uk/ :
> 
> Some people believe that anybody can get an IPv6 address by sticking
> their IPv4 address after a magic prefix. ::/96 is a popular choice
> for that magic prefix, and judging by the azdes.gov some people
> believe that 2002::/96 is equally magic.

Question: Any ideas of what's the reasoning behind this belief?

-- FWIW, When measuring IPv6 addresses from public-facing servers, I
found many instances of these... but never got to do much
analysis/guesswork regarding where this "assumption" was coming from.

Thanks!

Best regards,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Mon Oct  6 13:44:32 2014
Return-Path: <brian@innovationslab.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61F3D1A89FA for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 13:44:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 XJoZQbEpERCw for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 13:44:27 -0700 (PDT)
Received: from uillean.fuaim.com (uillean.fuaim.com [206.197.161.140]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7BE11A89E9 for <ipv6@ietf.org>; Mon,  6 Oct 2014 13:44:27 -0700 (PDT)
Received: from clairseach.fuaim.com (clairseach-high.fuaim.com [206.197.161.158]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by uillean.fuaim.com (Postfix) with ESMTP id 9071B8811D for <ipv6@ietf.org>; Mon,  6 Oct 2014 13:44:27 -0700 (PDT)
Received: from clemson.local (unknown [76.21.129.88]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by clairseach.fuaim.com (Postfix) with ESMTP id 54C8E136816E for <ipv6@ietf.org>; Mon,  6 Oct 2014 13:44:27 -0700 (PDT)
Message-ID: <5432FF23.3090305@innovationslab.net>
Date: Mon, 06 Oct 2014 16:44:19 -0400
From: Brian Haberman <brian@innovationslab.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com> <543047A2.8020804@gmail.com> <54317DCD.90907@gont.com.ar>
In-Reply-To: <54317DCD.90907@gont.com.ar>
Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LwrUqJsHtiT0aEXHocRwv86OKQIaTS0p9"
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/SXSgSaCCvXTsMRbmwLS1bMGKZoo
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 20:44:30 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--LwrUqJsHtiT0aEXHocRwv86OKQIaTS0p9
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



On 10/5/14 1:20 PM, Fernando Gont wrote:
>=20
> Hi, Brian,
>=20
> On 10/04/2014 04:16 PM, Brian E Carpenter wrote:
>> There's another issue here that I see from time to time in under-infor=
med
>> discussion forums such as www.theregister.co.uk/ :
>>
>> Some people believe that anybody can get an IPv6 address by sticking
>> their IPv4 address after a magic prefix. ::/96 is a popular choice
>> for that magic prefix, and judging by the azdes.gov some people
>> believe that 2002::/96 is equally magic.
>=20
> Question: Any ideas of what's the reasoning behind this belief?

IPv4-compatible addresses described in RFC 1884.

>=20
> -- FWIW, When measuring IPv6 addresses from public-facing servers, I
> found many instances of these... but never got to do much
> analysis/guesswork regarding where this "assumption" was coming from.
>=20
> Thanks!
>=20
> Best regards,
>=20


--LwrUqJsHtiT0aEXHocRwv86OKQIaTS0p9
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.20 (Darwin)
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJUMv8pAAoJEBOZRqCi7goqKYEIAMQ+nlVzEDm8BJP1a+zdEElp
/bxdd8RVOUPJ36/o7rifTkD+Tmo/xHTtKNr6Fe8mSVbrzaE6d/4l4beTLPKynaJZ
vIPFRD+IXkFadUOrlVZiCixxYQHvNj8EWjUYEapzAWMcAexVZ4xYfrGauBEmoJ+Q
OCb5Yo3LLPsf6ILzrD0tmle99trn7OHUA4EUcaBcvs4Px0VaCaLZI7IK3wf64WZu
xR5XmF88kXap7b4SaBvhF73u/ja4iZvNXDz3hLW1QoORfNzp1/1vUa5pz9Yw4l4t
NkDZnn4wTZ4Yn/CgqioYrvFgPCmjMhofhC9FC39YknrmyKZfwnSfCCeEZyS88ec=
=d3h3
-----END PGP SIGNATURE-----

--LwrUqJsHtiT0aEXHocRwv86OKQIaTS0p9--


From nobody Mon Oct  6 15:08:36 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C2CD01A8ADE for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 15:08:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 Jh22GJvelv32 for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 15:08:27 -0700 (PDT)
Received: from mail-pa0-x22e.google.com (mail-pa0-x22e.google.com [IPv6:2607:f8b0:400e:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA6541A8AE6 for <ipv6@ietf.org>; Mon,  6 Oct 2014 15:08:27 -0700 (PDT)
Received: by mail-pa0-f46.google.com with SMTP id fa1so6009289pad.33 for <ipv6@ietf.org>; Mon, 06 Oct 2014 15:08:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=POo4mnqPxnVLkGjSFwhCdPtzgmImlA6kRaeLEtElH4Q=; b=nouYgEaLOCSov8gT90rwYWbpV3bCTAUeUTDaB4hU1QCJcsyaoactBqORKdY6DihRGy kxppZeFtLqI8nrI19C03CPCFza2IjHiEur5lQvzBnTvnB09ORHn1e5pY+iHXb30S7QlO JBNNsQU4TxMScR2u9GeEanzTnuUuGXkv86XiB1spJ30RX+Kg4ALGLuKL7BH/nN3iP2s8 Y2PSs2GWHqfRGU2oGPtqaAdSgOTH2kXk+4sLaTU33kSRFkLmux+cxvJ9TWeDmm40LTFf LbsvYZE0AtnZiLv1FFWjSsgLs5ti40pbmQSiNE/IEGv2wMHPbrVgjTxQFfRs8ED3Gcni +r6Q==
X-Received: by 10.70.133.65 with SMTP id pa1mr21090454pdb.71.1412633307367; Mon, 06 Oct 2014 15:08:27 -0700 (PDT)
Received: from [130.216.38.108] (sc-cs-567-laptop.cs.auckland.ac.nz. [130.216.38.108]) by mx.google.com with ESMTPSA id of9sm216144pbc.6.2014.10.06.15.08.24 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 Oct 2014 15:08:26 -0700 (PDT)
Message-ID: <543312D6.3090403@gmail.com>
Date: Tue, 07 Oct 2014 11:08:22 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com> <543047A2.8020804@gmail.com> <5432809C.1090608@cisco.com> <5432EC61.4060806@gmail.com> <alpine.DEB.2.02.1410062142550.14735@uplift.swm.pp.se> <alpine.DEB.2.02.1410062155090.14735@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1410062155090.14735@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/0ud-oUS16uQyhhWzdpY-Dnh_lXw
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 06 Oct 2014 22:08:31 -0000

On 07/10/2014 08:56, Mikael Abrahamsson wrote:
> On Mon, 6 Oct 2014, Mikael Abrahamsson wrote:
> 
>> My guess is that the best people here to ask would be the IX operators
>> who do sFlow analysis, I don't see how else you could analyse IPv4
>> proto 41 traffic and count the ratio of traffic that has both src and
>> dst addresses in the 2002::/16 within them as opposed to other traffic.
> 
> I asked around, and at least one IX doesn't look beyond L2 headers with
> their sFlow, so that won't help.
> 
> Basically, I don't see how we can easily monitor this without some
> operators giving this to us, and that might just capture a few reagions,
> and might not give a global view.

Right. We'd actually need to get a set of IPv4 pcap traces from several
IXes to do this. I will ask my local expert on traces but I'm not
too optimistic.

    Brian


From nobody Mon Oct  6 17:57:21 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1FBA1A90F3 for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 17:57:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 1Of2UVC6Vawd for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 17:57:18 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 399151A90F5 for <ipv6@ietf.org>; Mon,  6 Oct 2014 17:57:18 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id p10so4143347pdj.15 for <ipv6@ietf.org>; Mon, 06 Oct 2014 17:57:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=jAgqiCxoncPp9+GA8C6QVfemLM80dkXw3vSfBlCGpy8=; b=F/HTZF38TBYgSxp7KURKiZXrK/OHrLa3MgVPp810OMuJKJSXorlqIKdBfUfG465PoW 1y2kgNEh0Gatsw9CEwYBuePPRWtF9mJF2Q3U6uNItZ3dQE08xlonnwGlPh0u491Xrmcy tsa5DLDCFGDunmrqJiugGNgGd8naPFpTH7YuW76srVMbC0xudnwzUGXLgGnoRL66ZLG5 I108hvDjXRGCE8VFaR0C9PR93qBnQxj/pd9zYkJmofLHXGwFtPEWPs3OoPmY6GULzdL0 OnpEoqdVh8Y6YbE4vGqZrzMuVdAWlVuqZTHdu0WelLdHOH4w9DRenqXXESD3q/sMZj8k OlCg==
X-Received: by 10.70.91.39 with SMTP id cb7mr650523pdb.8.1412643437858; Mon, 06 Oct 2014 17:57:17 -0700 (PDT)
Received: from [172.24.28.140] (wireless-nat-20.auckland.ac.nz. [130.216.30.131]) by mx.google.com with ESMTPSA id m2sm45288pdf.48.2014.10.06.17.57.14 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 06 Oct 2014 17:57:16 -0700 (PDT)
Message-ID: <54333A6A.5090807@gmail.com>
Date: Tue, 07 Oct 2014 13:57:14 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: 6man <ipv6@ietf.org>
Subject: Re: I-D Action: draft-sarikaya-6man-sadr-overview-01.txt
References: <20140929200736.12989.12437.idtracker@ietfa.amsl.com>
In-Reply-To: <20140929200736.12989.12437.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/wtADLNNaRAfaFeqju_5gKvUyz5g
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 07 Oct 2014 00:57:20 -0000

Hi,

I find this draft very interesting. I didn't spot any major errors,
but I think it lacks some sort of conclusion to summarise the
open issues and missing solutions.

    Brian

On 30/09/2014 09:07, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> 
> 
>         Title           : Overview of Source Address Dependent Routing
>         Author          : Behcet Sarikaya
> 	Filename        : draft-sarikaya-6man-sadr-overview-01.txt
> 	Pages           : 11
> 	Date            : 2014-09-29
> 
> Abstract:
>    This document presents an overview of source address dependent
>    routing from the host perspective.  Multihomed hosts and hosts with
>    multiple interfaces are considered.  Different architectures are
>    introduced and with their help, why source address selection and next
>    hop resolution in view of source address dependent routing is needed
>    is explained.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-01
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-sadr-overview-01
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Mon Oct  6 23:28:43 2014
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D79B51A1B42 for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 23:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.737
X-Spam-Level: 
X-Spam-Status: No, score=-4.737 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 0AvfOxGY8Ps2 for <ipv6@ietfa.amsl.com>; Mon,  6 Oct 2014 23:28:39 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B6B891A8728 for <ipv6@ietf.org>; Mon,  6 Oct 2014 23:28:39 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 8DEDEA1; Tue,  7 Oct 2014 08:28:37 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1412663317; bh=buOtfVJ8JF0B2O6ElSFAKAC74aA2JxaZGNMogqxE9v0=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=WffM1pT/SM2golkHL4ocI8KitddNsCHtzvDD96YL1plEgLvqXlBiqsJW8w4TUNWvh a2KtXFAGrycraTRENxRSg5iuVwMpu4Sfyhx4F6z1CEx2sCRHW8ZUWwlJ9OyZkdYCbm vp77ZWZ/PpgEHV3r5MvCPX+c55tJ8Iw3xxEUcY7M=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 8054E9F; Tue,  7 Oct 2014 08:28:37 +0200 (CEST)
Date: Tue, 7 Oct 2014 08:28:37 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
In-Reply-To: <543312D6.3090403@gmail.com>
Message-ID: <alpine.DEB.2.02.1410070825550.14735@uplift.swm.pp.se>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com> <543047A2.8020804@gmail.com> <5432809C.1090608@cisco.com> <5432EC61.4060806@gmail.com> <alpine.DEB.2.02.1410062142550.14735@uplift.swm.pp.se> <alpine.DEB.2.02.1410062155090.14735@uplift.swm.pp.se> <543312D6.3090403@gmail.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/7mG2sYXkNrNj1JNWpiBJ1SSF4MU
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 07 Oct 2014 06:28:42 -0000

On Tue, 7 Oct 2014, Brian E Carpenter wrote:

> Right. We'd actually need to get a set of IPv4 pcap traces from several 
> IXes to do this. I will ask my local expert on traces but I'm not too 
> optimistic.

I agree. I also think that we should give guidance that in more and more 
NAT44(4):ed world, even p2p 6to4 doesn't work. So I see no downside in 
making 6to4 historic, at least I hope this will stop new implementations 
of 6to4 for reasons that the implementor doesn't know about 6to4 state of 
affairs on the common Internet. If they still choose to implement it, 
that's fine, but at least that'll be a more informed decision.

So can't we just revive 
https://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05 and see 
if there is consensus? It was a good idea in 2011, it's an even better 
idea in 2014.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Tue Oct  7 00:09:18 2014
Return-Path: <cfriacas@fccn.pt>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5A4B1A9139 for <ipv6@ietfa.amsl.com>; Tue,  7 Oct 2014 00:09:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.686
X-Spam-Level: 
X-Spam-Status: No, score=-2.686 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 FeAE-njWjjFc for <ipv6@ietfa.amsl.com>; Tue,  7 Oct 2014 00:09:12 -0700 (PDT)
Received: from app02.fccn.pt (app02-out.fccn.pt [IPv6:2001:690:2080:8005::1005]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F9BB1A1B39 for <ipv6@ietf.org>; Tue,  7 Oct 2014 00:09:10 -0700 (PDT)
Received: from mx.anubis.local (ste [10.1.2.2]) by outbound.anubis.local (Postfix) with ESMTP id 061C2C2E2C for <ipv6@ietf.org>; Tue,  7 Oct 2014 08:09:11 +0100 (WEST)
Received: from gauntlet-ID.corp.fccn.pt (gauntlet-ID.corp.fccn.pt [193.136.46.2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cfriacas@fccn.pt) by mx.anubis.local (Postfix) with ESMTP id E49E3C2E23; Tue,  7 Oct 2014 08:09:10 +0100 (WEST)
Date: Tue, 7 Oct 2014 08:09:04 +0100 (WEST)
From: Carlos Friacas <cfriacas@fccn.pt>
X-X-Sender: cfriacas@gauntlet.id.fccn.pt
To: ipv6@ietf.org
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
In-Reply-To: <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl>
Message-ID: <alpine.LRH.2.11.1410070804330.5160@gauntlet.id.fccn.pt>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl>
User-Agent: Alpine 2.11 (LRH 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/yQzG4BJIp20p2rKjorOdNKeyQo0
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 07 Oct 2014 07:09:18 -0000

On Sat, 4 Oct 2014, Sander Steffann wrote:

> Hi,

Hi,


>> Marking 6to4 as historic would appropriately document current
>> operational reality, though. I suppose that would have some value in
>> itself, so I'd support doing so.
>
> +1.

+1 too.

We ran a 6to4 relay at some point along the way.
It was shutdown a while ago, and nobody complained so far.

However, i still do see 27 2002::/16 objects and 32 192.88.99.0/24 objects 
at the RIPEdb...


> I still have people in my training classes that think 6to4 is a great 
> idea.

You still get people at your classes that think NAT and CGN are great 
ideas ? ;-)


> When I tell them why they shouldn't depend on 6to4 I sometimes get 
> the reply: "but it's an official internet standard, we should just be 
> able to use it!". And I'm sure that they're not the only ones that 
> prefer 'standards' over common sense.
>
> Good documentation of current operational reality is important.

Completely agree. Cleanup.

Cheers,
Carlos



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


From nobody Tue Oct  7 01:35:22 2014
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A7E131A1B5D for <ipv6@ietfa.amsl.com>; Tue,  7 Oct 2014 01:35:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 FVqzBU8qiw_n for <ipv6@ietfa.amsl.com>; Tue,  7 Oct 2014 01:35:19 -0700 (PDT)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92EBE1A1A80 for <ipv6@ietf.org>; Tue,  7 Oct 2014 01:35:18 -0700 (PDT)
Received: by mail-lb0-f171.google.com with SMTP id z12so5740820lbi.16 for <ipv6@ietf.org>; Tue, 07 Oct 2014 01:35:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=n+f4kZTjv+JmCLQEGGiVWx/03hxyMHVrOqyxUun2xsI=; b=ErsgCjQzAAVowFpJ8prgjWeuuP0cKq97/kERs++qRVQYv/HWD4J/tPGh0hG8lCa1xS 9q/glMjs/UAJV5CF7DNwWuAmHmol8MQ1eE3JpeASz+lAwFKsgMv5h3IgCs2SKmku40Ci RuTGNmDiJP0QPSxi792d5kgW3ySque9wVndRAndhQTbgrc4cS0ctLc0LYYfiZDmtgZQh l4R1OKWV23JWp54RxtIX+mdCvjgsSmQ/G0inZ2pD4S0S8HjAZYctN7Dm5sXWUQlueSiG Dzr1YuHg23TEDeIodURdtz11gYn2IfdU8gXEw1VszKph7Mc0b6uowp0oG1NpmUeClOcO 2YNQ==
X-Received: by 10.113.3.130 with SMTP id bw2mr2312818lbd.39.1412670916867; Tue, 07 Oct 2014 01:35:16 -0700 (PDT)
Received: from [10.17.0.20] ([83.150.126.201]) by mx.google.com with ESMTPSA id t6sm6492710lag.27.2014.10.07.01.35.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 01:35:15 -0700 (PDT)
Message-ID: <5433A5C9.9060203@gmail.com>
Date: Tue, 07 Oct 2014 11:35:21 +0300
From: Jouni Korhonen <jouni.nospam@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, ipv6@ietf.org
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com>
In-Reply-To: <540FBDB8.4010701@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/lsTqAWb7SR1Okp26AQrWy-O128c
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 07 Oct 2014 08:35:20 -0000

Hi,

I am somewhat late with this document. I quick question for my 
clarification. Section 4.3.1. states that RIO is not supported e.g. for 
rather recent Linuxes. What qualifies "NOT-SUP" ? The fact that it is 
experimental and not enabled by default?

- JOuni


9/10/2014 5:55 AM, Brian E Carpenter kirjoitti:
> This version just fixes a minor reference error.
>
>      Brian
>
> On 10/09/2014 14:48, internet-drafts@ietf.org wrote:
>> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>>   This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
>>
>>          Title           : Analysis of the 64-bit Boundary in IPv6 Addressing
>>          Authors         : Brian Carpenter
>>                            Tim Chown
>>                            Fernando Gont
>>                            Sheng Jiang
>>                            Alexandru Petrescu
>>                            Andrew Yourtchenko
>> 	Filename        : draft-ietf-6man-why64-04.txt
>> 	Pages           : 24
>> 	Date            : 2014-09-09
>>
>> Abstract:
>>     The IPv6 unicast addressing format includes a separation between the
>>     prefix used to route packets to a subnet and the interface identifier
>>     used to specify a given interface connected to that subnet.
>>     Currently the interface identifier is defined as 64 bits long for
>>     almost every case, leaving 64 bits for the subnet prefix.  This
>>     document describes the advantages of this fixed boundary and analyses
>>     the issues that would be involved in treating it as a variable
>>     boundary.
>>
>>
>> The IETF datatracker status page for this draft is:
>> https://datatracker.ietf.org/doc/draft-ietf-6man-why64/
>>
>> There's also a htmlized version available at:
>> http://tools.ietf.org/html/draft-ietf-6man-why64-04
>>
>> A diff from the previous version is available at:
>> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-why64-04
>>
>>
>> Please note that it may take a couple of minutes from the time of submission
>> until the htmlized version and diff are available at tools.ietf.org.
>>
>> Internet-Drafts are also available by anonymous FTP at:
>> ftp://ftp.ietf.org/internet-drafts/
>>
>> _______________________________________________
>> I-D-Announce mailing list
>> I-D-Announce@ietf.org
>> https://www.ietf.org/mailman/listinfo/i-d-announce
>> Internet-Draft directories: http://www.ietf.org/shadow.html
>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Tue Oct  7 10:53:55 2014
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E66B1A870F for <ipv6@ietfa.amsl.com>; Tue,  7 Oct 2014 10:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 huhOtg53VhWf for <ipv6@ietfa.amsl.com>; Tue,  7 Oct 2014 10:53:50 -0700 (PDT)
Received: from mail-pa0-x22d.google.com (mail-pa0-x22d.google.com [IPv6:2607:f8b0:400e:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4187F1A8708 for <ipv6@ietf.org>; Tue,  7 Oct 2014 10:53:48 -0700 (PDT)
Received: by mail-pa0-f45.google.com with SMTP id rd3so7559205pab.4 for <ipv6@ietf.org>; Tue, 07 Oct 2014 10:53:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=iIt7ebQz8v1WcSsQJNXFz/jJdWcUDO6QzauHfBnwWL4=; b=uOfLORXixyh0mXaUamGk1NpiC4CTJx7F5qfQvVZ5S9R1ahU48B54KJgOmVSRZDeJG8 paAkYgdEl3JmIrRqJv3uhSl7tJBtNWEXPocpS9MB/OUgYwpQ1k6Q2paAqnJL5mH++sNA jo2DnvaacX8MkbA6LFwCDIDHZrkgszV3uc4N28rTNYZlHEYZ5DvaxrxNb2ORxo9wAL4X 2S78XifqlzWG1SEOZqHtNXRGol+f6ruspuHK3XoYVLkHdSBxxKMKujHyhqVmtm9kzgMZ fUkER3ULOOuiDs4QpNciypjqsrCE/GtXJ4U0slNNMAQq/hpmPFX1RHJMeyronHb70wGw da4g==
X-Received: by 10.70.89.108 with SMTP id bn12mr3813835pdb.146.1412704427870; Tue, 07 Oct 2014 10:53:47 -0700 (PDT)
Received: from [172.16.224.219] ([209.97.127.34]) by mx.google.com with ESMTPSA id gw1sm16523536pbd.49.2014.10.07.10.53.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 10:53:46 -0700 (PDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_E4A518E5-BEA3-4324-AFB5-1AC28E075712"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
Subject: Re: Adoption call of draft-halpern-6man-nd-pre-resolve-addr for 6MAN
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <5432F89E.8040008@innovationslab.net>
Date: Tue, 7 Oct 2014 10:53:36 -0700
Message-Id: <EFF58F9A-062E-47D0-A237-291885D38027@gmail.com>
References: <407DEA57-2807-44A5-8936-45B20CDB87C0@employees.org> <7DDF678F-1E09-4016-894C-6F16C2215859@employees.org> <542F2C1E.4090909@acm.org> <CAAedzxpo-yn=4NObnZ7XbgAAQTkRozDPxHzu2Ugq4x123=tuEA@mail.gmail.com> <5432F89E.8040008@innovationslab.net>
To: Brian Haberman <brian@innovationslab.net>
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/x5pcQX2C2PsYfSavwbixuFwskkw
Cc: IPv6 IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 07 Oct 2014 17:53:52 -0000

--Apple-Mail=_E4A518E5-BEA3-4324-AFB5-1AC28E075712
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

Brian,

On Oct 6, 2014, at 1:16 PM, Brian Haberman <brian@innovationslab.net> =
wrote:

>=20
>=20
> On 10/6/14 3:30 AM, Erik Kline wrote:
>>>=20
>>>=20
>>> Given that *plus* the claimed IPR, I don't see why the WG needs to =
spend
>>> time on this.
>>> It might be useful to document this behavior that Ericsson as =
implemented
>>> in an independent submission informational document.
>>>=20
>>=20
>> Agreed.
>>=20
>=20
> As a data point, the IESG has been encouraging the use of the ISE for
> documents that describe what companies have implemented.  And since =
this
> document is listed Informational, that approach makes more sense to =
me.
>=20


This is a fair point.  Contrary to our earlier conclusion on adopting =
this document, we now think going the Independent Submission route is =
appropriate.  If it was intended for all nodes and making changes to =
Neighbor Discovery, then it should be adopted in 6MAN.  As it not =
intended to be implemented by all nodes and it is Informational, we =
think the ISE route is appropriate for this document.

We also think that this was intended to be implemented in all nodes, =
then it would probably need additional work and some of this overlaps =
with the Efficient ND work going on in the w.g.

Is the w.g., and especially those who were in favour of adopting this =
draft, OK with this approach?

Bob




--Apple-Mail=_E4A518E5-BEA3-4324-AFB5-1AC28E075712
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJUNCigAAoJEK7rdBF357uo2/EH/2v/bTOOiNzQRZgN89/uNbyq
LMMT5RBsdp+Rnzhq0MPYHLbYVSTKIxpskb188k8eCvOxG1zPHsBEGd/i+ypxjiSs
B/ZIjRK+4m0lx/3TyRlRcXOHcKSJGF46iO59sMCCDypcJYeQVighgZzRaaQUNsbA
d1k03uow7bZG+0FM+dh7iQbBsBsKAFYc0u0kVhzZkY63BIA+hRN/0fGbe+C9Wb3W
d0o4A4nfBakmkBNtJnBBUsI0Zp9TBPDZpH00YDT/tvoBXaBL8MkRzhw2GvjDp8OA
kvGLPM5kTtjyZ0XOcq2PfH5qZ1jY1mWuCmIdr3/1YD7B8fKVBiEcq5V1C3CPA/4=
=XTL+
-----END PGP SIGNATURE-----

--Apple-Mail=_E4A518E5-BEA3-4324-AFB5-1AC28E075712--


From nobody Tue Oct  7 12:37:54 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 475031A19EF for <ipv6@ietfa.amsl.com>; Tue,  7 Oct 2014 12:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 txMN-PEnslUD for <ipv6@ietfa.amsl.com>; Tue,  7 Oct 2014 12:37:51 -0700 (PDT)
Received: from mail-pd0-x22c.google.com (mail-pd0-x22c.google.com [IPv6:2607:f8b0:400e:c02::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD96E1A07BE for <ipv6@ietf.org>; Tue,  7 Oct 2014 12:37:51 -0700 (PDT)
Received: by mail-pd0-f172.google.com with SMTP id ft15so5567502pdb.31 for <ipv6@ietf.org>; Tue, 07 Oct 2014 12:37:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=FbXMyTrPcNcOHErandEeQyvZak+heeKOCSA9YlVeUoo=; b=GQCeqRhywtjeuoKCjUWjkPRlSAoRYpfIZkLq7BvMl7l4VUSbM7JII2G47L8x6oXY4u IDZ6z7UJJ9o6JYqONw1zi/PHdX3IrHaQYxqqyU+XZczLFyKuRS3/H13bVR2sgCSsBEsJ qswnYU2EclEbGT6KkvhYhrhDAsVaa5sxzssWGYUHcHLHa5YROKQi2UDx15AfXUC0v1p2 o3R/WRIHJXIxzMi5ocWAjc/7BFYGATyMcOHykM148UGVg8kG1TNkSqIPzzdoPHwk4UHE Eckajmb/4wnz3JYhv078P6JYTZogKRhuLbkRCLa5pmMsDlf3Hqao7wMgXtuoHOYG2GLV QzBg==
X-Received: by 10.69.27.71 with SMTP id je7mr3730389pbd.155.1412710671567; Tue, 07 Oct 2014 12:37:51 -0700 (PDT)
Received: from [192.168.178.23] (224.200.69.111.dynamic.snap.net.nz. [111.69.200.224]) by mx.google.com with ESMTPSA id rh5sm5241213pdb.4.2014.10.07.12.37.48 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 07 Oct 2014 12:37:50 -0700 (PDT)
Message-ID: <54344110.4090505@gmail.com>
Date: Wed, 08 Oct 2014 08:37:52 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com> <543047A2.8020804@gmail.com> <5432809C.1090608@cisco.com> <5432EC61.4060806@gmail.com> <alpine.DEB.2.02.1410062142550.14735@uplift.swm.pp.se> <alpine.DEB.2.02.1410062155090.14735@uplift.swm.pp.se> <543312D6.3090403@gmail.com> <alpine.DEB.2.02.1410070825550.14735@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1410070825550.14735@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/mjLkJZ_bSey8_ByahQFefqlCXxQ
Cc: 6man <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 07 Oct 2014 19:37:53 -0000

On 07/10/2014 19:28, Mikael Abrahamsson wrote:
> On Tue, 7 Oct 2014, Brian E Carpenter wrote:
> 
>> Right. We'd actually need to get a set of IPv4 pcap traces from
>> several IXes to do this. I will ask my local expert on traces but I'm
>> not too optimistic.
> 
> I agree. I also think that we should give guidance that in more and more
> NAT44(4):ed world, even p2p 6to4 doesn't work. 

This is indeed discussed in RFC 3056 to some extent, although NAT44
was quite rare then.

> So I see no downside in
> making 6to4 historic, at least I hope this will stop new implementations
> of 6to4 for reasons that the implementor doesn't know about 6to4 state
> of affairs on the common Internet. If they still choose to implement it,
> that's fine, but at least that'll be a more informed decision.

(which was already the intention of RFC 6343 of course).

> So can't we just revive
> https://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05 and see
> if there is consensus? It was a good idea in 2011, it's an even better
> idea in 2014.

I have the xml2rfc source and (with Tore's agreement of course) will
update it soon.

   Brian


From n.oje.bar@gmail.com  Wed Oct  8 06:51:39 2014
Return-Path: <n.oje.bar@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 207DF1A1AA5 for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 06:51:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 NZtg26F9mGrU for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 06:51:37 -0700 (PDT)
Received: from mail-ig0-x232.google.com (mail-ig0-x232.google.com [IPv6:2607:f8b0:4001:c05::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 277E61A1A85 for <ipv6@ietf.org>; Wed,  8 Oct 2014 06:51:37 -0700 (PDT)
Received: by mail-ig0-f178.google.com with SMTP id h3so2260527igd.5 for <ipv6@ietf.org>; Wed, 08 Oct 2014 06:51:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=96Y6mVpxJCFFBEto/49oPnp+YWC1vPNe0fo2NdGCicw=; b=Kf1V8W1mVWnPUUoW35X/s+fIfsVzka3osN3VTkEcewalTJLLLOScoLzC2Z3ZPSNNxj lvWCIvpFSZEvLWoM2M8ZOBlODCaSRMCwbgAbIAY9G/M/r8JBy/kH6CANcMSDcxrejx0I 8vdRFjGWNQb6PtmHoEbcWQbZ2J6A0nnXVScO+DV/keV5CXeFA/QYWe6wqKdVLWDimjCK vSkeSETFRgyNkqnZvLBrIfsOOwiiVWtkUEa1Ghkl7NBIHFdDSwVgsWuiPJoeTa33XgZZ R6nCshm5+9M9sVy2thNUfUdSdBR/7ZgsedsJzEgGUmYmZN3GnQaqfGrI6ew+emb7bZ7M zTNw==
MIME-Version: 1.0
X-Received: by 10.50.117.65 with SMTP id kc1mr16671440igb.34.1412776296617; Wed, 08 Oct 2014 06:51:36 -0700 (PDT)
Sender: n.oje.bar@gmail.com
Received: by 10.50.243.36 with HTTP; Wed, 8 Oct 2014 06:51:36 -0700 (PDT)
Date: Wed, 8 Oct 2014 14:51:36 +0100
X-Google-Sender-Auth: xPkBxA5rc_kj7_x4zT-0Zj5Men8
Message-ID: <CAPunWhCzfNhE5fAJAWD-_63GqcwV8DEvgjnimXh1rXJ06zvUJg@mail.gmail.com>
Subject: Question on RFC 4861, Appendix C
From: Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk>
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=089e0118271e4e9be80504e99dec
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/en7R9Kc1MOF68gya7jtyQ6axvA8
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 08 Oct 2014 13:53:40 -0000

--089e0118271e4e9be80504e99dec
Content-Type: text/plain; charset=UTF-8

Hello,

I am currently implementing ND as specified in RFC 4861. I have a question
on the state machine specified in Appendix C. There it says that on receipt
of a RA message for which there is no entry in the NC the node should
create a new entry for the router in the NC with state STALE.

I don't know how to interpret this because it implies that the RA message
comes with a 'Source link-layer address' option because that is needed to
have a STALE entry in the NC, but the 'Source link-layer address' option in
the RA message is optional (as stated in 4.2, 'Possible options'). What is
one supposed to do if there is no such option ?

Thank you very much,
Nicolas

--089e0118271e4e9be80504e99dec
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>I am currently implementing ND a=
s specified in RFC 4861. I have a question on the state machine specified i=
n Appendix C. There it says that on receipt of a RA message for which there=
 is no entry in the NC the node should create a new entry for the router in=
 the NC with state STALE.</div><div><br></div><div>I don&#39;t know how to =
interpret this because it implies that the RA message comes with a &#39;Sou=
rce link-layer address&#39; option because that is needed to have a STALE e=
ntry in the NC, but the &#39;Source link-layer address&#39; option in the R=
A message is optional (as stated in 4.2, &#39;Possible options&#39;). What =
is one supposed to do if there is no such option ?</div><div><br></div><div=
>Thank you very much,<br></div><div>Nicolas</div></div>

--089e0118271e4e9be80504e99dec--


From nobody Wed Oct  8 08:50:22 2014
Return-Path: <kauer@into6.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DB371A1B27 for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 07:36:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.001
X-Spam-Level: 
X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
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 wh0hG2d2rV00 for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 07:36:42 -0700 (PDT)
Received: from ipmail07.adl2.internode.on.net (ipmail07.adl2.internode.on.net [150.101.137.131]) by ietfa.amsl.com (Postfix) with ESMTP id EB86C1A1AE9 for <ipv6@ietf.org>; Wed,  8 Oct 2014 07:36:41 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApcBALhKNVSWZX+7/2dsb2JhbAANUoNhWIMEyAiHUQKBIAGEfwEBBCMmQAsYAgImAgJXBhMctFh4lQ0YgSyLWoNFgneBVAW1SIF9WIJKAQEB
Received: from eth4284.nsw.adsl.internode.on.net (HELO [192.168.1.196]) ([150.101.127.187]) by ipmail07.adl2.internode.on.net with ESMTP; 09 Oct 2014 01:06:40 +1030
Message-ID: <1412778981.20084.0.camel@karl>
Subject: Re: Question on RFC 4861, Appendix C
From: Karl Auer <kauer@into6.com.au>
To: IETF IPv6 <ipv6@ietf.org>
Date: Thu, 09 Oct 2014 01:36:21 +1100
In-Reply-To: <CAPunWhCzfNhE5fAJAWD-_63GqcwV8DEvgjnimXh1rXJ06zvUJg@mail.gmail.com>
References: <CAPunWhCzfNhE5fAJAWD-_63GqcwV8DEvgjnimXh1rXJ06zvUJg@mail.gmail.com>
Organization: Into6
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.10.4-0ubuntu2 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/fv0SoNVjggSm5eJ9nqdtFxN8XTA
X-Mailman-Approved-At: Wed, 08 Oct 2014 08:50:19 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 08 Oct 2014 14:36:44 -0000

On Wed, 2014-10-08 at 14:51 +0100, Nicolas Ojeda Bar wrote:
> I am currently implementing ND as specified in RFC 4861. I have a question
> on the state machine specified in Appendix C. There it says that on receipt
> of a RA message for which there is no entry in the NC the node should
> create a new entry for the router in the NC with state STALE.
> 
> I don't know how to interpret this because it implies that the RA message
> comes with a 'Source link-layer address' option because that is needed to
> have a STALE entry in the NC, but the 'Source link-layer address' option in
> the RA message is optional (as stated in 4.2, 'Possible options'). What is
> one supposed to do if there is no such option ?

I don't think the state machine is prescriptive. Looking at section
6.3.4, it's pretty clear that you SHOULD (not MUST) create an NC entry
from an RA, and in fact one of the reasons given for NOT doing so is if
there is no link-layer address in the RA.

Regards, K.

-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer                                          tel  +61-2-64957435
kauer@into6.com.au                                 mob  +61-428-957160
                                         
Into6 - IPv6 design, support, training                www.into6.com.au

GPG fingerprint: C66C AF82 E0A2 155A 5444 7897 C370 D706 3EC0 C413
Old fingerprint: D8A4 A65A EE32 286F 1E36 55A4 0901 EEAF A785 1684


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Karl Auer                                          tel  +61-2-64957435
kauer@into6.com.au                                 mob  +61-428-957160
                                         
Into6 - IPv6 design, support, training                www.into6.com.au

GPG fingerprint: C66C AF82 E0A2 155A 5444 7897 C370 D706 3EC0 C413
Old fingerprint: D8A4 A65A EE32 286F 1E36 55A4 0901 EEAF A785 1684



From nobody Wed Oct  8 09:47:02 2014
Return-Path: <SRS0=W1if=67=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D12351A9232 for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 09:46:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Vv26zdQbSKCN for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 09:46:46 -0700 (PDT)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB36B1A9218 for <ipv6@ietf.org>; Wed,  8 Oct 2014 09:46:43 -0700 (PDT)
Received: from dhcp-10-61-101-88.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 3D3091408EEE3; Wed,  8 Oct 2014 18:46:39 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <5433A5C9.9060203@gmail.com>
Date: Wed, 8 Oct 2014 18:46:41 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com>
To: Jouni Korhonen <jouni.nospam@gmail.com>
X-Mailer: Apple Mail (2.1878.6)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Wed Oct 8 18:46:40 2014 +0200 (CEST))
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/X3H58P9gf-YE4qzaN5-hJ7JZGoQ
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 08 Oct 2014 16:46:51 -0000

Hello,

+1 to Jouni=92s question.

I went through the why64 document today and also found this "NOT-SUP" =
clause quite surprising.

Linux has been supporting RIOs since a long while.
But not by default (net.ipv6.conf.eth0.accept_ra_rt_info_max_plen sets =
the maximal length for which RIOs are accepted).
According to some mailing list discusses, it is not enabled by default =
for security concerns and/or because of the way it could interact with =
VPN softwares.

- Pierre


Le 7 oct. 2014 =E0 10:35, Jouni Korhonen <jouni.nospam@gmail.com> a =
=E9crit :

>=20
> Hi,
>=20
> I am somewhat late with this document. I quick question for my =
clarification. Section 4.3.1. states that RIO is not supported e.g. for =
rather recent Linuxes. What qualifies "NOT-SUP" ? The fact that it is =
experimental and not enabled by default?
>=20
> - JOuni
>=20
>=20
> 9/10/2014 5:55 AM, Brian E Carpenter kirjoitti:
>> This version just fixes a minor reference error.
>>=20
>>     Brian
>>=20
>> On 10/09/2014 14:48, internet-drafts@ietf.org wrote:
>>> A New Internet-Draft is available from the on-line Internet-Drafts =
directories.
>>>  This draft is a work item of the IPv6 Maintenance Working Group of =
the IETF.
>>>=20
>>>         Title           : Analysis of the 64-bit Boundary in IPv6 =
Addressing
>>>         Authors         : Brian Carpenter
>>>                           Tim Chown
>>>                           Fernando Gont
>>>                           Sheng Jiang
>>>                           Alexandru Petrescu
>>>                           Andrew Yourtchenko
>>> 	Filename        : draft-ietf-6man-why64-04.txt
>>> 	Pages           : 24
>>> 	Date            : 2014-09-09
>>>=20
>>> Abstract:
>>>    The IPv6 unicast addressing format includes a separation between =
the
>>>    prefix used to route packets to a subnet and the interface =
identifier
>>>    used to specify a given interface connected to that subnet.
>>>    Currently the interface identifier is defined as 64 bits long for
>>>    almost every case, leaving 64 bits for the subnet prefix.  This
>>>    document describes the advantages of this fixed boundary and =
analyses
>>>    the issues that would be involved in treating it as a variable
>>>    boundary.
>>>=20
>>>=20
>>> The IETF datatracker status page for this draft is:
>>> https://datatracker.ietf.org/doc/draft-ietf-6man-why64/
>>>=20
>>> There's also a htmlized version available at:
>>> http://tools.ietf.org/html/draft-ietf-6man-why64-04
>>>=20
>>> A diff from the previous version is available at:
>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-why64-04
>>>=20
>>>=20
>>> Please note that it may take a couple of minutes from the time of =
submission
>>> until the htmlized version and diff are available at tools.ietf.org.
>>>=20
>>> Internet-Drafts are also available by anonymous FTP at:
>>> ftp://ftp.ietf.org/internet-drafts/
>>>=20
>>> _______________________________________________
>>> I-D-Announce mailing list
>>> I-D-Announce@ietf.org
>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>=20
>>=20
>> --------------------------------------------------------------------
>> IETF IPv6 working group mailing list
>> ipv6@ietf.org
>> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
>> --------------------------------------------------------------------
>>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Wed Oct  8 12:49:18 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 710D51A010E for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 12:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 q1qwCQViZSBP for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 12:49:14 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 990091A0147 for <ipv6@ietf.org>; Wed,  8 Oct 2014 12:49:14 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id bj1so9660476pad.1 for <ipv6@ietf.org>; Wed, 08 Oct 2014 12:49:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=12z3KngtGK2qbLgmf+O35Ap/f2eSarTzrCGR4wncOTg=; b=D/oXCl/XVjwbGHwBUfCWbh15EMGVtdIwEeRHAgfJiyIUJSRJqIR14AXMojg5j8LGtJ QpYEFReKocp7RyOR/HNrFx22BFfl8QWt5+l0PruVLqJaki2LkDL/ArFQZoQF59HT29uE +P7u65YC7Iy5ugvnArixSjbqlimlH7U9sgNSAngwAxbGneKjADgIw2wZgp2HzRQz6RG/ RBO3nU0C/PK/h5UR+68YyIksVI+WRZxZG+jFVjn9qVvWs37j/mqI/MIEu5l8kCNh4v+a CvTge+lVmVMdSTz/f6NntF6OZe1JmieayKtOZFDD5ksC3m3EKm4AD8Gsj5sefRqyhUkq d60g==
X-Received: by 10.70.129.72 with SMTP id nu8mr13622769pdb.91.1412797754247; Wed, 08 Oct 2014 12:49:14 -0700 (PDT)
Received: from [192.168.178.23] (129.195.69.111.dynamic.snap.net.nz. [111.69.195.129]) by mx.google.com with ESMTPSA id iu10sm720635pbd.57.2014.10.08.12.49.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 08 Oct 2014 12:49:12 -0700 (PDT)
Message-ID: <5435953A.7010904@gmail.com>
Date: Thu, 09 Oct 2014 08:49:14 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr>
In-Reply-To: <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/9lyoBw4D5rCTQMLqje36lcTVbUE
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 08 Oct 2014 19:49:16 -0000

Fernando - this text originally came from you, can you clarify please?
If this needs a wording change, we need to know quickly.

Regards
   Brian

On 09/10/2014 05:46, Pierre Pfister wrote:
> Hello,
>=20
> +1 to Jouni=E2=80=99s question.
>=20
> I went through the why64 document today and also found this "NOT-SUP" c=
lause quite surprising.
>=20
> Linux has been supporting RIOs since a long while.
> But not by default (net.ipv6.conf.eth0.accept_ra_rt_info_max_plen sets =
the maximal length for which RIOs are accepted).
> According to some mailing list discusses, it is not enabled by default =
for security concerns and/or because of the way it could interact with VP=
N softwares.
>=20
> - Pierre
>=20
>=20
> Le 7 oct. 2014 =C3=A0 10:35, Jouni Korhonen <jouni.nospam@gmail.com> a =
=C3=A9crit :
>=20
>> Hi,
>>
>> I am somewhat late with this document. I quick question for my clarifi=
cation. Section 4.3.1. states that RIO is not supported e.g. for rather r=
ecent Linuxes. What qualifies "NOT-SUP" ? The fact that it is experimenta=
l and not enabled by default?
>>
>> - JOuni
>>
>>
>> 9/10/2014 5:55 AM, Brian E Carpenter kirjoitti:
>>> This version just fixes a minor reference error.
>>>
>>>     Brian
>>>
>>> On 10/09/2014 14:48, internet-drafts@ietf.org wrote:
>>>> A New Internet-Draft is available from the on-line Internet-Drafts d=
irectories.
>>>>  This draft is a work item of the IPv6 Maintenance Working Group of =
the IETF.
>>>>
>>>>         Title           : Analysis of the 64-bit Boundary in IPv6 Ad=
dressing
>>>>         Authors         : Brian Carpenter
>>>>                           Tim Chown
>>>>                           Fernando Gont
>>>>                           Sheng Jiang
>>>>                           Alexandru Petrescu
>>>>                           Andrew Yourtchenko
>>>> 	Filename        : draft-ietf-6man-why64-04.txt
>>>> 	Pages           : 24
>>>> 	Date            : 2014-09-09
>>>>
>>>> Abstract:
>>>>    The IPv6 unicast addressing format includes a separation between =
the
>>>>    prefix used to route packets to a subnet and the interface identi=
fier
>>>>    used to specify a given interface connected to that subnet.
>>>>    Currently the interface identifier is defined as 64 bits long for=

>>>>    almost every case, leaving 64 bits for the subnet prefix.  This
>>>>    document describes the advantages of this fixed boundary and anal=
yses
>>>>    the issues that would be involved in treating it as a variable
>>>>    boundary.
>>>>
>>>>
>>>> The IETF datatracker status page for this draft is:
>>>> https://datatracker.ietf.org/doc/draft-ietf-6man-why64/
>>>>
>>>> There's also a htmlized version available at:
>>>> http://tools.ietf.org/html/draft-ietf-6man-why64-04
>>>>
>>>> A diff from the previous version is available at:
>>>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-why64-04
>>>>
>>>>
>>>> Please note that it may take a couple of minutes from the time of su=
bmission
>>>> until the htmlized version and diff are available at tools.ietf.org.=

>>>>
>>>> Internet-Drafts are also available by anonymous FTP at:
>>>> ftp://ftp.ietf.org/internet-drafts/
>>>>
>>>> _______________________________________________
>>>> I-D-Announce mailing list
>>>> I-D-Announce@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/i-d-announce
>>>> Internet-Draft directories: http://www.ietf.org/shadow.html
>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>>
>>> --------------------------------------------------------------------
>>> 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
>> --------------------------------------------------------------------
>=20
>=20


From nobody Wed Oct  8 13:45:58 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F02641A030A; Wed,  8 Oct 2014 13:45:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 5aWlz6JEPcHu; Wed,  8 Oct 2014 13:45:52 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BA6B1A01EF; Wed,  8 Oct 2014 13:45:52 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-default-iids-01.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141008204552.13263.38810.idtracker@ietfa.amsl.com>
Date: Wed, 08 Oct 2014 13:45:52 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/TNuPcOyHeWfnaYpSJK2JFRqmohQ
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 08 Oct 2014 20:45:54 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Recommendation on Stable IPv6 Interface Identifiers
        Authors         : Fernando Gont
                          Alissa Cooper
                          Dave Thaler
                          Will Liu
	Filename        : draft-ietf-6man-default-iids-01.txt
	Pages           : 7
	Date            : 2014-10-08

Abstract:
   The IPv6 addressing architecture defines Modified EUI-64 format
   Interface Identifiers, and the existing IPv6 over various link-layers
   specify how such identifiers are derived from the underlying link-
   layer address (e.g., an IEEE LAN MAC address) when employing IPv6
   Stateless Address Autoconfiguration (SLAAC).  The security and
   privacy implications of embedding hardware addresses in the Interface
   Identifier have been known and understood for some time now, and some
   popular IPv6 implementations have already deviated from such schemes
   to mitigate these issues.  This document changes the recommended
   default Interface Identifier generation scheme to that specified in
   RFC7217, and recommends against embedding hardware addresses in IPv6
   Interface Identifiers.  It formally updates RFC2464, RFC2467,
   RFC2470, RFC2491, RFC2492, RFC2497, RFC2590, RFC3146, RFC3572,
   RFC4291, RFC4338, RFC4391, RFC5072, and RFC5121, wihch require IPv6
   Interface Identifiers to be derived from the underlying link-layer
   address.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-default-iids/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-default-iids-01

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-default-iids-01


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Wed Oct  8 15:20:56 2014
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F2D21A1AD9 for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 15:20:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=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 rcpSPUNx3AO0 for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 15:20:52 -0700 (PDT)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 155C71A0028 for <ipv6@ietf.org>; Wed,  8 Oct 2014 15:20:50 -0700 (PDT)
Received: from [172.22.229.45] ([162.210.130.3]) (authenticated bits=0) by c.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s98MKeAl025068 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 8 Oct 2014 15:20:41 -0700
Message-ID: <5435B8B9.7080405@acm.org>
Date: Wed, 08 Oct 2014 15:20:41 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk>, ipv6@ietf.org
Subject: Re: Question on RFC 4861, Appendix C
References: <CAPunWhCzfNhE5fAJAWD-_63GqcwV8DEvgjnimXh1rXJ06zvUJg@mail.gmail.com>
In-Reply-To: <CAPunWhCzfNhE5fAJAWD-_63GqcwV8DEvgjnimXh1rXJ06zvUJg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVanpxoFNAtxpyoSQkZIqWR09K/aOjG3QLQMuEvCx9YbK/J/kf/fKuKXILFFf3zSGTYuJetKSBiH7teR49q7XpOJ
X-Sonic-ID: C;yKBoVjlP5BGi7YR6lZB5Vg== M;fhWJVjlP5BGi7YR6lZB5Vg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/Rs54Tq2uyMvEaMymjzVa7Q3xrn4
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 08 Oct 2014 22:20:53 -0000

On 10/8/14 6:51 AM, Nicolas Ojeda Bar wrote:
> Hello,
>
> I am currently implementing ND as specified in RFC 4861. I have a 
> question on the state machine specified in Appendix C. There it says 
> that on receipt of a RA message for which there is no entry in the NC 
> the node should create a new entry for the router in the NC with state 
> STALE.

I assume this is the rule at the top of the "table" on page 91 which 
also has NS etc:
    -               NS, RS, RA, Redirect    Create entry. STALE

    INCOMPLETE      NS, RS, RA, Redirect    Record link-layer STALE
                                            address. Send queued
                                            packets.


Note that the link-layer address is merely a SHOULD for unicast NS messages.
Thus the same question applies for a NS as for a RA.

And in the INCOMPLETE case one can only record a lla of the message 
contains one; the queued packets can only be sent (on link-layers which 
has addresses) once the entry has a recorded lla.

>
> I don't know how to interpret this because it implies that the RA 
> message comes with a 'Source link-layer address' option because that 
> is needed to have a STALE entry in the NC, but the 'Source link-layer 
> address' option in the RA message is optional (as stated in 4.2, 
> 'Possible options'). What is one supposed to do if there is no such 
> option ?
>
>

There is more detail in section 6.3.4:
    After extracting information from the fixed part of the Router
    Advertisement message, the advertisement is scanned for valid
    options.  If the advertisement contains a Source Link-Layer Address
    option, the link-layer address SHOULD be recorded in the Neighbor
    Cache entry for the router (creating an entry if necessary) and the
    IsRouter flag in the Neighbor Cache entry MUST be set to TRUE. If no
    Source Link-Layer Address is included, but a corresponding Neighbor
    Cache entry exists, its IsRouter flag MUST be set to TRUE.  The
    IsRouter flag is used by Neighbor Unreachability Detection to
    determine when a router changes to being a host (i.e., no longer
    capable of forwarding packets).  If a Neighbor Cache entry is created
    for the router, its reachability state MUST be set to STALE as
    specified in Section 7.3.3.  If a cache entry already exists and is
    updated with a different link-layer address, the reachability state
    MUST also be set to STALE.

Does that make it clear?

Regards,
    Erik


From nobody Wed Oct  8 16:30:37 2014
Return-Path: <n.oje.bar@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B9581A1AB3 for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 16:30:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 7OrtjLrnxus4 for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 16:30:34 -0700 (PDT)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 870731A6F49 for <ipv6@ietf.org>; Wed,  8 Oct 2014 16:30:34 -0700 (PDT)
Received: by mail-ig0-f181.google.com with SMTP id r10so811520igi.14 for <ipv6@ietf.org>; Wed, 08 Oct 2014 16:30:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=lrAvYDAbDKUO3wm/ZgepoQFLNyEmZ1UDWxh7G3bnlrE=; b=CFQsqc/o/P9M4RvFh6duWR54/sfJl13tPgXF2dvZ++QWTZBR0yuMJ75CV7WiMBorkZ FZvXd5PdEYK/JTdSCa19dtvfH3ZtRicshzZaZwNeaJC17yiJxqXk73ZJxLQ+VMJkbQT8 MzGhCe0nNzb8UUGzQuJqptNTfK9H8PfkNtp7IwsEPuG/YdcduZ9kfdpkwHYQw7uMuqFy w4sYNSvHJjPcXscY3eunx0p7kqIYp0EpJ7VHIAKCJx8/8I9CAIht8UcclvTav4nnN0U/ S8zeHWwt34E4OHpTsnugbUmqUCcMtlR5sg89j9G3gFROvLGhU7Nx1d5jTpOcsgZvlAAo sZLw==
MIME-Version: 1.0
X-Received: by 10.50.117.65 with SMTP id kc1mr1812734igb.34.1412811033906; Wed, 08 Oct 2014 16:30:33 -0700 (PDT)
Sender: n.oje.bar@gmail.com
Received: by 10.50.243.36 with HTTP; Wed, 8 Oct 2014 16:30:33 -0700 (PDT)
In-Reply-To: <5435B8B9.7080405@acm.org>
References: <CAPunWhCzfNhE5fAJAWD-_63GqcwV8DEvgjnimXh1rXJ06zvUJg@mail.gmail.com> <5435B8B9.7080405@acm.org>
Date: Thu, 9 Oct 2014 00:30:33 +0100
X-Google-Sender-Auth: VpieoNK_REmDAC7UNrPD3Fw3H5Q
Message-ID: <CAPunWhAuboVxb2sTt81w+WO9CYfyS0+MkTKcT2h-wKg8gZJeew@mail.gmail.com>
Subject: Re: Question on RFC 4861, Appendix C
From: Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk>
To: Erik Nordmark <nordmark@acm.org>
Content-Type: multipart/alternative; boundary=089e0118271ecfa9830504f1b3ef
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/woTeyGIKrLxZNsyXN4WhuQsgF6Q
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 08 Oct 2014 23:30:36 -0000

--089e0118271ecfa9830504f1b3ef
Content-Type: text/plain; charset=UTF-8

Thanks very much for all the answers! They have been very helpful.

Best wishes,
Nicolas

On Wed, Oct 8, 2014 at 11:20 PM, Erik Nordmark <nordmark@acm.org> wrote:

> On 10/8/14 6:51 AM, Nicolas Ojeda Bar wrote:
>
>> Hello,
>>
>> I am currently implementing ND as specified in RFC 4861. I have a
>> question on the state machine specified in Appendix C. There it says that
>> on receipt of a RA message for which there is no entry in the NC the node
>> should create a new entry for the router in the NC with state STALE.
>>
>
> I assume this is the rule at the top of the "table" on page 91 which also
> has NS etc:
>    -               NS, RS, RA, Redirect    Create entry. STALE
>
>    INCOMPLETE      NS, RS, RA, Redirect    Record link-layer STALE
>                                            address. Send queued
>                                            packets.
>
>
> Note that the link-layer address is merely a SHOULD for unicast NS
> messages.
> Thus the same question applies for a NS as for a RA.
>
> And in the INCOMPLETE case one can only record a lla of the message
> contains one; the queued packets can only be sent (on link-layers which has
> addresses) once the entry has a recorded lla.
>
>
>> I don't know how to interpret this because it implies that the RA message
>> comes with a 'Source link-layer address' option because that is needed to
>> have a STALE entry in the NC, but the 'Source link-layer address' option in
>> the RA message is optional (as stated in 4.2, 'Possible options'). What is
>> one supposed to do if there is no such option ?
>>
>>
>>
> There is more detail in section 6.3.4:
>    After extracting information from the fixed part of the Router
>    Advertisement message, the advertisement is scanned for valid
>    options.  If the advertisement contains a Source Link-Layer Address
>    option, the link-layer address SHOULD be recorded in the Neighbor
>    Cache entry for the router (creating an entry if necessary) and the
>    IsRouter flag in the Neighbor Cache entry MUST be set to TRUE. If no
>    Source Link-Layer Address is included, but a corresponding Neighbor
>    Cache entry exists, its IsRouter flag MUST be set to TRUE.  The
>    IsRouter flag is used by Neighbor Unreachability Detection to
>    determine when a router changes to being a host (i.e., no longer
>    capable of forwarding packets).  If a Neighbor Cache entry is created
>    for the router, its reachability state MUST be set to STALE as
>    specified in Section 7.3.3.  If a cache entry already exists and is
>    updated with a different link-layer address, the reachability state
>    MUST also be set to STALE.
>
> Does that make it clear?
>
> Regards,
>    Erik
>
>

--089e0118271ecfa9830504f1b3ef
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thanks very much for all the answers! They have been very =
helpful.<div><br></div><div>Best wishes,</div><div>Nicolas</div></div><div =
class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Oct 8, 2014 at=
 11:20 PM, Erik Nordmark <span dir=3D"ltr">&lt;<a href=3D"mailto:nordmark@a=
cm.org" target=3D"_blank">nordmark@acm.org</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex"><span class=3D"">On 10/8/14 6:51 AM, Nicolas Ojeda =
Bar wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
Hello,<br>
<br>
I am currently implementing ND as specified in RFC 4861. I have a question =
on the state machine specified in Appendix C. There it says that on receipt=
 of a RA message for which there is no entry in the NC the node should crea=
te a new entry for the router in the NC with state STALE.<br>
</blockquote>
<br></span>
I assume this is the rule at the top of the &quot;table&quot; on page 91 wh=
ich also has NS etc:<br>
=C2=A0 =C2=A0-=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0NS, RS=
, RA, Redirect=C2=A0 =C2=A0 Create entry. STALE<br>
<br>
=C2=A0 =C2=A0INCOMPLETE=C2=A0 =C2=A0 =C2=A0 NS, RS, RA, Redirect=C2=A0 =C2=
=A0 Record link-layer STALE<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0address. Send queued<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0packets.<br>
<br>
<br>
Note that the link-layer address is merely a SHOULD for unicast NS messages=
.<br>
Thus the same question applies for a NS as for a RA.<br>
<br>
And in the INCOMPLETE case one can only record a lla of the message contain=
s one; the queued packets can only be sent (on link-layers which has addres=
ses) once the entry has a recorded lla.<span class=3D""><br>
<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<br>
I don&#39;t know how to interpret this because it implies that the RA messa=
ge comes with a &#39;Source link-layer address&#39; option because that is =
needed to have a STALE entry in the NC, but the &#39;Source link-layer addr=
ess&#39; option in the RA message is optional (as stated in 4.2, &#39;Possi=
ble options&#39;). What is one supposed to do if there is no such option ?<=
br>
<br>
<br>
</blockquote>
<br></span>
There is more detail in section 6.3.4:<br>
=C2=A0 =C2=A0After extracting information from the fixed part of the Router=
<br>
=C2=A0 =C2=A0Advertisement message, the advertisement is scanned for valid<=
br>
=C2=A0 =C2=A0options.=C2=A0 If the advertisement contains a Source Link-Lay=
er Address<br>
=C2=A0 =C2=A0option, the link-layer address SHOULD be recorded in the Neigh=
bor<br>
=C2=A0 =C2=A0Cache entry for the router (creating an entry if necessary) an=
d the<br>
=C2=A0 =C2=A0IsRouter flag in the Neighbor Cache entry MUST be set to TRUE.=
 If no<br>
=C2=A0 =C2=A0Source Link-Layer Address is included, but a corresponding Nei=
ghbor<br>
=C2=A0 =C2=A0Cache entry exists, its IsRouter flag MUST be set to TRUE.=C2=
=A0 The<br>
=C2=A0 =C2=A0IsRouter flag is used by Neighbor Unreachability Detection to<=
br>
=C2=A0 =C2=A0determine when a router changes to being a host (i.e., no long=
er<br>
=C2=A0 =C2=A0capable of forwarding packets).=C2=A0 If a Neighbor Cache entr=
y is created<br>
=C2=A0 =C2=A0for the router, its reachability state MUST be set to STALE as=
<br>
=C2=A0 =C2=A0specified in Section 7.3.3.=C2=A0 If a cache entry already exi=
sts and is<br>
=C2=A0 =C2=A0updated with a different link-layer address, the reachability =
state<br>
=C2=A0 =C2=A0MUST also be set to STALE.<br>
<br>
Does that make it clear?<br>
<br>
Regards,<br>
=C2=A0 =C2=A0Erik<br>
<br>
</blockquote></div><br></div>

--089e0118271ecfa9830504f1b3ef--


From nobody Wed Oct  8 19:43:08 2014
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA8B71A8A4A for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 19:43:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level: 
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 rwak3R2i2Pqv for <ipv6@ietfa.amsl.com>; Wed,  8 Oct 2014 19:43:04 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F23941A8A49 for <ipv6@ietf.org>; Wed,  8 Oct 2014 19:43:03 -0700 (PDT)
Received: by mail-ig0-f174.google.com with SMTP id a13so4681795igq.1 for <ipv6@ietf.org>; Wed, 08 Oct 2014 19:43:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=7fgHQUnubhlpNB2gJ1Kk1ytcSCXtfRN+M45tp3CK10k=; b=LCvWG8JMnS2zp1QNhym54xZgj7AzNAGQR8meIf5LQwPhirsz0JkdJynGuRzZ2GkBjx JX2iM6BHic+/mOm8Eq1yXM5I3i1msl7Ogt4QZvXoKlpYa+inWIigCpO5or0lX5lUvPzy N8kdDx9OrQye0+ZV+JMPyRU/56REEBTGSUCsTADkpcv7/XrHNQ1UVPUeURzhu1jzEyuU owVaZR8bgIXYY2fTeeQVOnQxyZPbdCffalOnIJBFZMnxv4Szs3PcnhgpoFOTPW9+Rnt7 9yLQZcfcJIH2Sht0n8jwK8W8xFv8t402+8tZockI/aAK7ybrNZUYmo5ZiOzWv8nrShlR zEIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=7fgHQUnubhlpNB2gJ1Kk1ytcSCXtfRN+M45tp3CK10k=; b=KJ5ePhl9fcHoJTIabDyPhKF0j2HtSDb42FSzR4s7iNv0A/0yXXI6a+03id/Mn0i67p +g6fdtSkaFeD6Nzht/NmCpFKiYS0FDk/NsDNG14ALU9QILuQuZv7VCPcLDbekGqrCmQW Zzju+zuHSyRXDyK4tF06IEBtXsX/09t/HL04Hc5ULIqOhcUt8+ewqaImUnfpQx8Fuc1j fg/8i3bDEodQbL8GVm3mLO9TwQrDFmqqnDWv4N42mi7F3uO7OB32cQMS08ftMqk63k5R fmEomMGknpr9g9VFmAEW90LwMmTKVRP6CXht+ENV0B3PrQ9JdrGihRkgekSCfntK4h19 14+w==
X-Gm-Message-State: ALoCoQlCAyk/qlwYA0o3P+JazBQNw1EAZMYoZhWzw1pmQd9xNhEGHxn5xHm61EEOu6ONGyRfA8wY
X-Received: by 10.42.70.11 with SMTP id d11mr2982706icj.92.1412822583001; Wed, 08 Oct 2014 19:43:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.24.144 with HTTP; Wed, 8 Oct 2014 19:42:42 -0700 (PDT)
In-Reply-To: <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Oct 2014 11:42:42 +0900
Message-ID: <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
To: Pierre Pfister <pierre.pfister@darou.fr>
Content-Type: multipart/alternative; boundary=90e6ba2122c130edae0504f46436
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/dTdBlnsN2dB7x4ApamLKwqc0qCI
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 02:43:07 -0000

--90e6ba2122c130edae0504f46436
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Another reason why you might not want to set accept_ra_rt_info_max_plen in
the real wold is that doing so creates a DoS scenario where an attacker can
consume all your routing table slots by sending you tens of thousands of
RIOs.

The kernel has protections against configuring too many autoconf addresses
(defaults to max 16), but nothing against configuring too many routes.

I suppose an attacker who can mount such an attack can already send you RAs
from ulimited link-local addresses, so perhaps there's no additional risk
here?

On Thu, Oct 9, 2014 at 1:46 AM, Pierre Pfister <pierre.pfister@darou.fr>
wrote:

> Hello,
>
> +1 to Jouni=E2=80=99s question.
>
> I went through the why64 document today and also found this "NOT-SUP"
> clause quite surprising.
>
> Linux has been supporting RIOs since a long while.
> But not by default (net.ipv6.conf.eth0.accept_ra_rt_info_max_plen sets th=
e
> maximal length for which RIOs are accepted).
> According to some mailing list discusses, it is not enabled by default fo=
r
> security concerns and/or because of the way it could interact with VPN
> softwares.
>
> - Pierre
>
>
> Le 7 oct. 2014 =C3=A0 10:35, Jouni Korhonen <jouni.nospam@gmail.com> a =
=C3=A9crit :
>
> >
> > Hi,
> >
> > I am somewhat late with this document. I quick question for my
> clarification. Section 4.3.1. states that RIO is not supported e.g. for
> rather recent Linuxes. What qualifies "NOT-SUP" ? The fact that it is
> experimental and not enabled by default?
> >
> > - JOuni
> >
> >
> > 9/10/2014 5:55 AM, Brian E Carpenter kirjoitti:
> >> This version just fixes a minor reference error.
> >>
> >>     Brian
> >>
> >> On 10/09/2014 14:48, internet-drafts@ietf.org wrote:
> >>> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> >>>  This draft is a work item of the IPv6 Maintenance Working Group of
> the IETF.
> >>>
> >>>         Title           : Analysis of the 64-bit Boundary in IPv6
> Addressing
> >>>         Authors         : Brian Carpenter
> >>>                           Tim Chown
> >>>                           Fernando Gont
> >>>                           Sheng Jiang
> >>>                           Alexandru Petrescu
> >>>                           Andrew Yourtchenko
> >>>     Filename        : draft-ietf-6man-why64-04.txt
> >>>     Pages           : 24
> >>>     Date            : 2014-09-09
> >>>
> >>> Abstract:
> >>>    The IPv6 unicast addressing format includes a separation between t=
he
> >>>    prefix used to route packets to a subnet and the interface
> identifier
> >>>    used to specify a given interface connected to that subnet.
> >>>    Currently the interface identifier is defined as 64 bits long for
> >>>    almost every case, leaving 64 bits for the subnet prefix.  This
> >>>    document describes the advantages of this fixed boundary and
> analyses
> >>>    the issues that would be involved in treating it as a variable
> >>>    boundary.
> >>>
> >>>
> >>> The IETF datatracker status page for this draft is:
> >>> https://datatracker.ietf.org/doc/draft-ietf-6man-why64/
> >>>
> >>> There's also a htmlized version available at:
> >>> http://tools.ietf.org/html/draft-ietf-6man-why64-04
> >>>
> >>> A diff from the previous version is available at:
> >>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-why64-04
> >>>
> >>>
> >>> Please note that it may take a couple of minutes from the time of
> submission
> >>> until the htmlized version and diff are available at tools.ietf.org.
> >>>
> >>> Internet-Drafts are also available by anonymous FTP at:
> >>> ftp://ftp.ietf.org/internet-drafts/
> >>>
> >>> _______________________________________________
> >>> I-D-Announce mailing list
> >>> I-D-Announce@ietf.org
> >>> https://www.ietf.org/mailman/listinfo/i-d-announce
> >>> Internet-Draft directories: http://www.ietf.org/shadow.html
> >>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> >>>
> >>
> >> --------------------------------------------------------------------
> >> 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
> > --------------------------------------------------------------------
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

--90e6ba2122c130edae0504f46436
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Another reason why you might not want to set accept_ra_rt_=
info_max_plen in the real wold is that doing so creates a DoS scenario wher=
e an attacker can consume all your routing table slots by sending you tens =
of thousands of RIOs.<div><br></div><div>The kernel has protections against=
 configuring too many autoconf addresses (defaults to max 16), but nothing =
against configuring too many routes.</div><div><br></div><div>I suppose an =
attacker who can mount such an attack can already send you RAs from ulimite=
d link-local addresses, so perhaps there&#39;s no additional risk here?</di=
v></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, O=
ct 9, 2014 at 1:46 AM, Pierre Pfister <span dir=3D"ltr">&lt;<a href=3D"mail=
to:pierre.pfister@darou.fr" target=3D"_blank">pierre.pfister@darou.fr</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
<br>
+1 to Jouni=E2=80=99s question.<br>
<br>
I went through the why64 document today and also found this &quot;NOT-SUP&q=
uot; clause quite surprising.<br>
<br>
Linux has been supporting RIOs since a long while.<br>
But not by default (net.ipv6.conf.eth0.accept_ra_rt_info_max_plen sets the =
maximal length for which RIOs are accepted).<br>
According to some mailing list discusses, it is not enabled by default for =
security concerns and/or because of the way it could interact with VPN soft=
wares.<br>
<br>
- Pierre<br>
<br>
<br>
Le 7 oct. 2014 =C3=A0 10:35, Jouni Korhonen &lt;<a href=3D"mailto:jouni.nos=
pam@gmail.com">jouni.nospam@gmail.com</a>&gt; a =C3=A9crit :<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt;<br>
&gt; Hi,<br>
&gt;<br>
&gt; I am somewhat late with this document. I quick question for my clarifi=
cation. Section 4.3.1. states that RIO is not supported e.g. for rather rec=
ent Linuxes. What qualifies &quot;NOT-SUP&quot; ? The fact that it is exper=
imental and not enabled by default?<br>
&gt;<br>
&gt; - JOuni<br>
&gt;<br>
&gt;<br>
&gt; 9/10/2014 5:55 AM, Brian E Carpenter kirjoitti:<br>
&gt;&gt; This version just fixes a minor reference error.<br>
&gt;&gt;<br>
&gt;&gt;=C2=A0 =C2=A0 =C2=A0Brian<br>
&gt;&gt;<br>
&gt;&gt; On 10/09/2014 14:48, <a href=3D"mailto:internet-drafts@ietf.org">i=
nternet-drafts@ietf.org</a> wrote:<br>
&gt;&gt;&gt; A New Internet-Draft is available from the on-line Internet-Dr=
afts directories.<br>
&gt;&gt;&gt;=C2=A0 This draft is a work item of the IPv6 Maintenance Workin=
g Group of the IETF.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Title=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0: Analysis of the 64-bit Boundary in IPv6 Addressing<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Authors=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0: Brian Carpenter<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Tim Chown<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Fernando Gont<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Sheng Jiang<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Alexandru Petrescu<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Andrew Yourtchenko<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0Filename=C2=A0 =C2=A0 =C2=A0 =C2=A0 : draft=
-ietf-6man-why64-04.txt<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0Pages=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0: 24<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 =C2=A0Date=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 : 2014-09-09<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Abstract:<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 The IPv6 unicast addressing format includes a sep=
aration between the<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 prefix used to route packets to a subnet and the =
interface identifier<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 used to specify a given interface connected to th=
at subnet.<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 Currently the interface identifier is defined as =
64 bits long for<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 almost every case, leaving 64 bits for the subnet=
 prefix.=C2=A0 This<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 document describes the advantages of this fixed b=
oundary and analyses<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 the issues that would be involved in treating it =
as a variable<br>
&gt;&gt;&gt;=C2=A0 =C2=A0 boundary.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; The IETF datatracker status page for this draft is:<br>
&gt;&gt;&gt; <a href=3D"https://datatracker.ietf.org/doc/draft-ietf-6man-wh=
y64/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-ietf-6man-wh=
y64/</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; There&#39;s also a htmlized version available at:<br>
&gt;&gt;&gt; <a href=3D"http://tools.ietf.org/html/draft-ietf-6man-why64-04=
" target=3D"_blank">http://tools.ietf.org/html/draft-ietf-6man-why64-04</a>=
<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; A diff from the previous version is available at:<br>
&gt;&gt;&gt; <a href=3D"http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-=
why64-04" target=3D"_blank">http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6=
man-why64-04</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Please note that it may take a couple of minutes from the time=
 of submission<br>
&gt;&gt;&gt; until the htmlized version and diff are available at <a href=
=3D"http://tools.ietf.org" target=3D"_blank">tools.ietf.org</a>.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Internet-Drafts are also available by anonymous FTP at:<br>
&gt;&gt;&gt; <a href=3D"ftp://ftp.ietf.org/internet-drafts/" target=3D"_bla=
nk">ftp://ftp.ietf.org/internet-drafts/</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt; I-D-Announce mailing list<br>
&gt;&gt;&gt; <a href=3D"mailto:I-D-Announce@ietf.org">I-D-Announce@ietf.org=
</a><br>
&gt;&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/i-d-announce"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/i-d-announce</a><b=
r>
&gt;&gt;&gt; Internet-Draft directories: <a href=3D"http://www.ietf.org/sha=
dow.html" target=3D"_blank">http://www.ietf.org/shadow.html</a><br>
&gt;&gt;&gt; or <a href=3D"ftp://ftp.ietf.org/ietf/1shadow-sites.txt" targe=
t=3D"_blank">ftp://ftp.ietf.org/ietf/1shadow-sites.txt</a><br>
&gt;&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; ------------------------------------------------------------------=
--<br>
&gt;&gt; IETF IPv6 working group mailing list<br>
&gt;&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt;&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/l=
istinfo/ipv6" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6<=
/a><br>
&gt;&gt; ------------------------------------------------------------------=
--<br>
&gt;&gt;<br>
&gt;<br>
&gt; --------------------------------------------------------------------<b=
r>
&gt; IETF IPv6 working group mailing list<br>
&gt; <a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
&gt; Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listi=
nfo/ipv6" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><=
br>
&gt; --------------------------------------------------------------------<b=
r>
<br>
--------------------------------------------------------------------<br>
IETF IPv6 working group mailing list<br>
<a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>
Administrative Requests: <a href=3D"https://www.ietf.org/mailman/listinfo/i=
pv6" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ipv6</a><br>
--------------------------------------------------------------------<br>
</div></div></blockquote></div><br></div>

--90e6ba2122c130edae0504f46436--


From nobody Thu Oct  9 01:36:19 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C7EB1A00F6 for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 01:36:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 BLjK3gbUnCsA for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 01:36:15 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 922401A90ED for <ipv6@ietf.org>; Thu,  9 Oct 2014 01:36:11 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAEAJ1HNlStJssW/2dsb2JhbABf10gCgR0Be4QEAQEDATo/BQsLRlcGiEkIxXgBF5ARMweDLYEeAQSec5Bgg3+DZTuCeQEBAQ
X-IronPort-AV: E=Sophos;i="5.04,683,1406592000"; d="scan'208";a="200726343"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 09 Oct 2014 08:36:10 +0000
Received: from dhcp-10-61-103-225.cisco.com (dhcp-10-61-103-225.cisco.com [10.61.103.225]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s998a8DL019183 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Oct 2014 08:36:09 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com>
Date: Thu, 9 Oct 2014 10:36:08 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/8qSrfj8K0PRU630Xg6NMW4LUn2Q
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 08:36:17 -0000

Lorenzo,

> Another reason why you might not want to set =
accept_ra_rt_info_max_plen in the real wold is that doing so creates a =
DoS scenario where an attacker can consume all your routing table slots =
by sending you tens of thousands of RIOs.
>=20
> The kernel has protections against configuring too many autoconf =
addresses (defaults to max 16), but nothing against configuring too many =
routes.
>=20
> I suppose an attacker who can mount such an attack can already send =
you RAs from ulimited link-local addresses, so perhaps there's no =
additional risk here?

a router should only send 17 RIOs in any RA per link (RFC4191). I would =
hope any host implementation would have also an upper bound on the =
number of routers it accepts on a link. given that I don't see much of =
an attack here.

with regards to NOT-SUPor not, if it isn't on by default it might as =
well not be implemented.

cheers,
Ole=


From nobody Thu Oct  9 03:28:52 2014
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 661421ACD3A for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 03:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level: 
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 z_YCttkCycCN for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 03:28:49 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F13501ACD19 for <ipv6@ietf.org>; Thu,  9 Oct 2014 03:28:48 -0700 (PDT)
Received: by mail-ig0-f174.google.com with SMTP id a13so6464096igq.13 for <ipv6@ietf.org>; Thu, 09 Oct 2014 03:28:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=LvlemGfso+lctmyMzh2p+UKhCPvrPsflLnCVISVieig=; b=BdIxCDgJ9aEMDsyvee4NuqnCbl4yekevxDqsswoOkhO4lsyjYbI0OYnpzf9W9ULi2T qgvZ+WwFyO8zoAm6CtVo0ebw/t8SABVh55fsOF2A6nc0ybVzXLAOs6QbPSD3XVPx3TK+ BdimhCKao5r+gwFArL0YsrNVjSMzSTHuYo10BAeL79/JzRuE9mh4nKnSQo0ZUKgC4Ci5 MpIV/t9pZIEm5CYNlF9xJHVzm2rbGQmS6QJUbnU6eSApmwv0xtrTK78RG1thmC4u6xdY hJeN3pMmwl3SA9tOWMlSpJvkv5IdDVk6GsY0WhNqrLffZOQbLLF9aWNVYJlxNLwH0tzS BB5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=LvlemGfso+lctmyMzh2p+UKhCPvrPsflLnCVISVieig=; b=EuObry4TmCPSAQaXZ+I3GDudgaBf4n34OQzcwAhGhzmVj9X15bIpfD1Qmf3Wa5wyBY 2oHfRmJY/Bipkw4JjvgMHFgAn89BxklUgkNdWuCLn43U2j+QiW3w6bk7uWOnODkF2WBX RQ3TqrMj82AHiLk2rMrqdkx6UprkuM3amPhtfMOYSwAvFmBiIBeAwERPiKViHCK+viKq Glfg94tQM8XFNFdBfKD84gQWiMfdcF+lUSbNNjUiIQC/Lg0Mn1fu/t+Vvs8h5f59Jj82 xs8BVMUFq+UzXFt2ETOQZaIX6mkag0hS2xBZu7A4eG33yQeCc7pWdUANp8FRvORM+asW AGKg==
X-Gm-Message-State: ALoCoQnCveg1B5o53puwz3sXKeVkpy6BYWCnWv+/zh1bJ9juMnjogzzljsiUporifkARwrGC/EjS
X-Received: by 10.43.1.135 with SMTP id nq7mr6320965icb.95.1412850528219; Thu, 09 Oct 2014 03:28:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.24.144 with HTTP; Thu, 9 Oct 2014 03:28:27 -0700 (PDT)
In-Reply-To: <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com> <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Oct 2014 19:28:27 +0900
Message-ID: <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=bcaec50fe6cddb2d6e0504fae5b7
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/N7UivlELgjZipUWIev7u3D8ajX8
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 10:28:50 -0000

--bcaec50fe6cddb2d6e0504fae5b7
Content-Type: text/plain; charset=UTF-8

On Thu, Oct 9, 2014 at 5:36 PM, Ole Troan <otroan@employees.org> wrote:

> a router should only send 17 RIOs in any RA per link (RFC4191). I would
> hope any host implementation would have also an upper bound on the number
> of routers it accepts on a link. given that I don't see much of an attack
> here.
>

The router can only send 17 RIOs per packet, but it can send you 100 pps or
1000 pps of them. There's no limit on the number of routers that I can see.


> with regards to NOT-SUPor not, if it isn't on by default it might as well
> not be implemented.
>

It doesn't matter what the Linux default is, it matters what the default is
on products that use Linux.

--bcaec50fe6cddb2d6e0504fae5b7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Oct 9, 2014 at 5:36 PM, Ole Troan <span dir=3D"ltr">&lt;<a href=3D"mail=
to:otroan@employees.org" target=3D"_blank">otroan@employees.org</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">a router should only send 17 R=
IOs in any RA per link (RFC4191). I would hope any host implementation woul=
d have also an upper bound on the number of routers it accepts on a link. g=
iven that I don&#39;t see much of an attack here.<br></blockquote><div><br>=
</div><div>The router can only send 17 RIOs per packet, but it can send you=
 100 pps or 1000 pps of them. There&#39;s no limit on the number of routers=
 that I can see.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">with =
regards to NOT-SUPor not, if it isn&#39;t on by default it might as well no=
t be implemented.<br></blockquote><div><br></div><div>It doesn&#39;t matter=
 what the Linux default is, it matters what the default is on products that=
 use Linux.</div></div></div></div>

--bcaec50fe6cddb2d6e0504fae5b7--


From nobody Thu Oct  9 03:46:36 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CD461ACD3F for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 03:46:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 kfqRLHDKNw_U for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 03:46:32 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAFAF1ACD3B for <ipv6@ietf.org>; Thu,  9 Oct 2014 03:46:31 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAEAAtmNlStJssW/2dsb2JhbABf1x4CgR4Be4QEAQEDATo/BQsLRlcGiEkIxggBF49tJDMHgy2BHgEEnnOGcY1ug2U7gTaBQwEBAQ
X-IronPort-AV: E=Sophos;i="5.04,684,1406592000"; d="scan'208";a="200830216"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 09 Oct 2014 10:46:30 +0000
Received: from dhcp-10-61-103-225.cisco.com (dhcp-10-61-103-225.cisco.com [10.61.103.225]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id s99AkTm6000383 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 9 Oct 2014 10:46:30 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com>
Date: Thu, 9 Oct 2014 12:46:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com> <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org> <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/KklRKXbroZTiSUkT0vuzJin3KuA
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 10:46:34 -0000

Lorenzo,

> a router should only send 17 RIOs in any RA per link (RFC4191). I =
would hope any host implementation would have also an upper bound on the =
number of routers it accepts on a link. given that I don't see much of =
an attack here.
>=20
> The router can only send 17 RIOs per packet, but it can send you 100 =
pps or 1000 pps of them. There's no limit on the number of routers that =
I can see.

RFC4191 says:
   Routers SHOULD NOT send more than 17 Route Information Options in
   Router Advertisements per link.  This arbitrary bound is meant to
   reinforce that relatively few and carefully selected routes should be
   advertised to hosts.

following that a host implementation shouldn't accept an arbitrary large =
number of RIOs from a single router.
if you re-read what I say above, a robust host implementation should =
also have a limit of the number of routers it accepts on a link. and =
obviously also the rate of RAs it receive.

> =20
> with regards to NOT-SUPor not, if it isn't on by default it might as =
well not be implemented.
>=20
> It doesn't matter what the Linux default is, it matters what the =
default is on products that use Linux.

to get back on topic. RIO isn't directly relevant to the why64 draft, so =
if the text if contentious I'd suggest you'd just remove the RIO column.

cheers,
Ole=


From nobody Thu Oct  9 03:52:23 2014
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 40B361ACD45 for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 03:52:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level: 
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 VIFvxGwVoR47 for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 03:52:21 -0700 (PDT)
Received: from mail-ig0-x22b.google.com (mail-ig0-x22b.google.com [IPv6:2607:f8b0:4001:c05::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1BCE1ACD3C for <ipv6@ietf.org>; Thu,  9 Oct 2014 03:52:20 -0700 (PDT)
Received: by mail-ig0-f171.google.com with SMTP id h15so11971968igd.10 for <ipv6@ietf.org>; Thu, 09 Oct 2014 03:52:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=UQtmaw2o5Jyv1TWTL8SLJ1b90hIpiwl3h5AzGLHxAFo=; b=LWuC2LG8L1S0TRyf+PrkSFy0eDXcrgQP53VbVoUTAz+zI+vGENXxwn8cUVFbnap+1l KGbOLzVRKuASjlu2C2K7DMiKOq+Kj58pQOL5P3OkaERu8rsrSW/bxhjkBrTLPXi8Rd1p umPr1UhX4B/9qKxU1wAzKkxBRjgdnoJZslsYDor38IANWoIgW2/YfzMzJWv0EYogXVN3 401lM4X2YO4Ue3I1GZOCRpI7LxlJJFgwONUrvIo22fyOVe0RHcNfZvTmfcMiYWzDiiLJ g0BXKUiM9bvLjgbzO8N8j033GfACuIkb7og1pP+ya/YBxDitQNdRWPgnIBcPlrVGS85B Ez8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=UQtmaw2o5Jyv1TWTL8SLJ1b90hIpiwl3h5AzGLHxAFo=; b=m+8WrwsXKERsQNKNJAR7+Ya9GVyDnORgfPpvI71nAvvlwwApg/u+j+BxImPpe8Ed7i Ys70e6N8epubDOF7eft8Bx7O+ve1wx2KZyq2dX5c8XkUX9QXpF3tf0CgX8G3RvxeX9NB pTQfQNZkuo58ddWxbSSD4IOjhAHrvwR+P6kzoy38b2Pswx9xPlxiP5+cohhQGWkW1wSF U45Dq1C8oNlF1Ai53LJ+APNEb73+2WMvzIZ+me4QbL9VCitlsUR6MEmLmrJW702ctYWC hHSrRZFvIm4GXXfNQdb7NSSHSaZJYh2ddFOYy4TlPcUQNIASQYyuqDxYSp7dwvoPHMVr eL/w==
X-Gm-Message-State: ALoCoQnGfu7xJbxEIq2WzNTo9TqNllasniaXYkCYNL082dmjosWMh0YnGfNtz3lGq6NDNFIMxRYd
X-Received: by 10.50.66.174 with SMTP id g14mr30341722igt.34.1412851940167; Thu, 09 Oct 2014 03:52:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.24.144 with HTTP; Thu, 9 Oct 2014 03:52:00 -0700 (PDT)
In-Reply-To: <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com> <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org> <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com> <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Thu, 9 Oct 2014 19:52:00 +0900
Message-ID: <CAKD1Yr3Pb7Pd7xWS29Rx_1He71Zx5vnPPdMmc6m=5dYgmeznng@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary=047d7bdc0ee403ce190504fb3a3a
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/AHJmr7GUWxPqaAi575z5sW2PP10
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 10:52:22 -0000

--047d7bdc0ee403ce190504fb3a3a
Content-Type: text/plain; charset=UTF-8

On Thu, Oct 9, 2014 at 7:46 PM, Ole Troan <otroan@employees.org> wrote:

> RFC4191 says:
>    Routers SHOULD NOT send more than 17 Route Information Options in
>    Router Advertisements per link.  This arbitrary bound is meant to
>    reinforce that relatively few and carefully selected routes should be
>    advertised to hosts.
>
> following that a host implementation shouldn't accept an arbitrary large
> number of RIOs from a single router.
> if you re-read what I say above, a robust host implementation should also
> have a limit of the number of routers it accepts on a link. and obviously
> also the rate of RAs it receive.
>

Sounds like a reasonable assertion. Do you know of a robust host
implementation?

--047d7bdc0ee403ce190504fb3a3a
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Oct 9, 2014 at 7:46 PM, Ole Troan <span dir=3D"ltr">&lt;<a href=3D"mail=
to:otroan@employees.org" target=3D"_blank">otroan@employees.org</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex">RFC4191 says:<br>
=C2=A0 =C2=A0Routers SHOULD NOT send more than 17 Route Information Options=
 in<br>
=C2=A0 =C2=A0Router Advertisements per link.=C2=A0 This arbitrary bound is =
meant to<br>
=C2=A0 =C2=A0reinforce that relatively few and carefully selected routes sh=
ould be<br>
=C2=A0 =C2=A0advertised to hosts.<br>
<br>
following that a host implementation shouldn&#39;t accept an arbitrary larg=
e number of RIOs from a single router.<br>
if you re-read what I say above, a robust host implementation should also h=
ave a limit of the number of routers it accepts on a link. and obviously al=
so the rate of RAs it receive.<br></blockquote><div><br></div><div>Sounds l=
ike a reasonable assertion. Do you know of a robust host implementation?</d=
iv></div></div></div>

--047d7bdc0ee403ce190504fb3a3a--


From nobody Thu Oct  9 04:41:34 2014
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 790F81ACDA0 for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 04:41:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 k8LWFyBOCKH3 for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 04:41:31 -0700 (PDT)
Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B2E31A028A for <ipv6@ietf.org>; Thu,  9 Oct 2014 04:41:31 -0700 (PDT)
Received: by mail-la0-f47.google.com with SMTP id pv20so968261lab.20 for <ipv6@ietf.org>; Thu, 09 Oct 2014 04:41:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=Lq9w35/FtZFHK0LBdWRwiu4sayI3aj6q++nnXK7ZSK8=; b=A8vtWCWoQtQmvKgdlhemhxBOxRAguuXFDGE5Ks73IvQBgATacWi7QTHzg6u3gcZXhd iXIkJN0gCohXi/+xedgWm4hXJo6Q1qJiGXP/64b39/k2rETFPYHQIyU14RiWcWjXd9GB uhmoecu2iNOKNNK74iXW9Nbx/3dtc/xsanv9wTfKvr3lzjEbJVermUCxi8+3pzwj054s sbZIm3ZwyUrfukKD8qpDISyht0XQ5RyHUChxNOUP5pLE6G/Wa7WVC/h09evIZvEliNKM IkZ4Jh7Ie039bpoFP9uDyYNpBqEEJizRtCkmDazUgMo8oqVz/vErHVYIMucKbnk9MqF+ PJOw==
X-Received: by 10.112.13.232 with SMTP id k8mr16763355lbc.81.1412854889592; Thu, 09 Oct 2014 04:41:29 -0700 (PDT)
Received: from [188.117.15.108] ([188.117.15.108]) by mx.google.com with ESMTPSA id n4sm907253lah.2.2014.10.09.04.41.27 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Oct 2014 04:41:28 -0700 (PDT)
Message-ID: <5436746E.9000804@gmail.com>
Date: Thu, 09 Oct 2014 14:41:34 +0300
From: Jouni Korhonen <jouni.nospam@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>,  Lorenzo Colitti <lorenzo@google.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com> <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org> <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com> <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org>
In-Reply-To: <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/BQ1HurHsgUu20kT0uVO49dbxTOI
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 11:41:33 -0000

I would be in favor of removing RIO stuff.. unless there is better 
justification for the current text. We used RIOs successfully in Linuxes 
and *BSDs already around 4-5 years ago in some projects.

- Jouni

10/9/2014 1:46 PM, Ole Troan kirjoitti:
> Lorenzo,
>
>> a router should only send 17 RIOs in any RA per link (RFC4191). I would hope any host implementation would have also an upper bound on the number of routers it accepts on a link. given that I don't see much of an attack here.
>>
>> The router can only send 17 RIOs per packet, but it can send you 100 pps or 1000 pps of them. There's no limit on the number of routers that I can see.
>
> RFC4191 says:
>     Routers SHOULD NOT send more than 17 Route Information Options in
>     Router Advertisements per link.  This arbitrary bound is meant to
>     reinforce that relatively few and carefully selected routes should be
>     advertised to hosts.
>
> following that a host implementation shouldn't accept an arbitrary large number of RIOs from a single router.
> if you re-read what I say above, a robust host implementation should also have a limit of the number of routers it accepts on a link. and obviously also the rate of RAs it receive.
>
>>
>> with regards to NOT-SUPor not, if it isn't on by default it might as well not be implemented.
>>
>> It doesn't matter what the Linux default is, it matters what the default is on products that use Linux.
>
> to get back on topic. RIO isn't directly relevant to the why64 draft, so if the text if contentious I'd suggest you'd just remove the RIO column.
>
> cheers,
> Ole
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Thu Oct  9 12:04:51 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 068CF1A1A8B for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:04:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 CNLu_VygC1vN for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:04:43 -0700 (PDT)
Received: from mail-pd0-x231.google.com (mail-pd0-x231.google.com [IPv6:2607:f8b0:400e:c02::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 84FEA1A1AC4 for <ipv6@ietf.org>; Thu,  9 Oct 2014 12:04:42 -0700 (PDT)
Received: by mail-pd0-f177.google.com with SMTP id v10so254494pde.8 for <ipv6@ietf.org>; Thu, 09 Oct 2014 12:04:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=hrxFwygR+G69iY6VpoQiawxfGtd7BGAAuHeHMJg8ThU=; b=Mx83wUPUvOOBoddQds3J1grIm2zlyqAvvtID2dKbes58kDcmmRQcrEYGzejSoJYRnr CGRxniNTiIX3kBe11MJ3HXnhRmmsiPquyC8MjusIMm+ixv9bRSEFqZW7nAV6Vqgm/ZgE dVdl3kJlcxS6I7JYXlL3v7l2RsW/4r/DvU84pFATRTUO6b5ocxPd87dqxqne/JXW20ed XC117WFtnBqB94M8LUl6CM3xrqiwN1TZkR5nQvoT4ez42Rwr9DsNeBNUJbww4Fx4bbGs H5kDYcfmeRpPKftN3cehFTMKY1we7gGc4HIfFgK3kg2TGDjSI5X/Loa5l2f1Rc0NYCC1 2Caw==
X-Received: by 10.68.57.134 with SMTP id i6mr1401267pbq.157.1412881473335; Thu, 09 Oct 2014 12:04:33 -0700 (PDT)
Received: from [192.168.178.23] (247.192.69.111.dynamic.snap.net.nz. [111.69.192.247]) by mx.google.com with ESMTPSA id t9sm1251563pdo.37.2014.10.09.12.04.28 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Oct 2014 12:04:32 -0700 (PDT)
Message-ID: <5436DC43.1060004@gmail.com>
Date: Fri, 10 Oct 2014 08:04:35 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Jouni Korhonen <jouni.nospam@gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt (Fernando, please reply)
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com> <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org> <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com> <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org> <5436746E.9000804@gmail.com>
In-Reply-To: <5436746E.9000804@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/CrzCdRBN5na-0JCbARFQ3oPUgVo
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 19:04:45 -0000

On 10/10/2014 00:41, Jouni Korhonen wrote:
> I would be in favor of removing RIO stuff.. unless there is better
> justification for the current text. We used RIOs successfully in Linuxes
> and *BSDs already around 4-5 years ago in some projects.

I don't see any justification for removing the text at this late stage.
What I do need (as document editor) is clarification from Fernando
about what this NOT-SUP actually relates to. If it means the shipped
default Linux configuration that is what the document should say.

    Brian

> 
> - Jouni
> 
> 10/9/2014 1:46 PM, Ole Troan kirjoitti:
>> Lorenzo,
>>
>>> a router should only send 17 RIOs in any RA per link (RFC4191). I
>>> would hope any host implementation would have also an upper bound on
>>> the number of routers it accepts on a link. given that I don't see
>>> much of an attack here.
>>>
>>> The router can only send 17 RIOs per packet, but it can send you 100
>>> pps or 1000 pps of them. There's no limit on the number of routers
>>> that I can see.
>>
>> RFC4191 says:
>>     Routers SHOULD NOT send more than 17 Route Information Options in
>>     Router Advertisements per link.  This arbitrary bound is meant to
>>     reinforce that relatively few and carefully selected routes should be
>>     advertised to hosts.
>>
>> following that a host implementation shouldn't accept an arbitrary
>> large number of RIOs from a single router.
>> if you re-read what I say above, a robust host implementation should
>> also have a limit of the number of routers it accepts on a link. and
>> obviously also the rate of RAs it receive.
>>
>>>
>>> with regards to NOT-SUPor not, if it isn't on by default it might as
>>> well not be implemented.
>>>
>>> It doesn't matter what the Linux default is, it matters what the
>>> default is on products that use Linux.
>>
>> to get back on topic. RIO isn't directly relevant to the why64 draft,
>> so if the text if contentious I'd suggest you'd just remove the RIO
>> column.
>>
>> cheers,
>> Ole
>> --------------------------------------------------------------------
>> 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
> --------------------------------------------------------------------
> 


From nobody Thu Oct  9 12:05:25 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD1171A1AAF for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:04:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 7hybuFq3akAq for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:04:47 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ED651A1A8B for <ipv6@ietf.org>; Thu,  9 Oct 2014 12:04:47 -0700 (PDT)
Received: from [2001:5c0:1400:a::7e5] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1XcJ0r-0004Il-Mo; Thu, 09 Oct 2014 21:04:34 +0200
Message-ID: <5436DB6C.8040507@si6networks.com>
Date: Thu, 09 Oct 2014 16:01:00 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <5435953A.7010904@gmail.com>
In-Reply-To: <5435953A.7010904@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/6vIAMmo-J3bUXpTBpZmeaUWFr7Y
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 19:04:53 -0000

Hi, Brian,

On 10/08/2014 04:49 PM, Brian E Carpenter wrote:
> Fernando - this text originally came from you, can you clarify please?
> If this needs a wording change, we need to know quickly.

For Linux, it turns out that this is supported, but "disabled by default".

So I'm not sure whether we should add a new tag such as "DISABLED", or
mark the corresponding entries as "ROUTE".

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Oct  9 12:09:55 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96B851A1ACC for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:09:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 QdZg2EHdRpAp for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:09:52 -0700 (PDT)
Received: from mail-pd0-x232.google.com (mail-pd0-x232.google.com [IPv6:2607:f8b0:400e:c02::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5937B1A1AC8 for <ipv6@ietf.org>; Thu,  9 Oct 2014 12:09:52 -0700 (PDT)
Received: by mail-pd0-f178.google.com with SMTP id y10so257688pdj.23 for <ipv6@ietf.org>; Thu, 09 Oct 2014 12:09:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=5DMjaE/sGRjevgTC5u11yPd4jWZkajHzXkrzXHpnsmc=; b=0o657JKk7sarwXKW/IBkVuGRPErGrKzAeaqEpFBd6s9rmvoLPRPtlLc6S+kro/fb1J n1OsI8NswcJNEBksvT+BX9wojKzpCfLBe1RJJhUEUQ/js2FyKde81m9FVt0Hb4WE231+ 754fSKCpftw655VgcduANng3KOOklss7oaK7NrUiUH3DP/r4AhTGpncgU7XGMAUeb3Qb GprrfhLn04UZGX/OxNqtEwsqFrfEc+1TW93xFrt7t4A91LRLJAXJ/HHopUaUtYy2PapV fwY9TkKPMsX8gZ9M0SqCziYD82g2/jWqX+1DRcE5X9Uk2WXLcq8DDZ1d9w6Ior128CcB mDTA==
X-Received: by 10.68.112.193 with SMTP id is1mr44442pbb.35.1412881792048; Thu, 09 Oct 2014 12:09:52 -0700 (PDT)
Received: from [192.168.178.23] (247.192.69.111.dynamic.snap.net.nz. [111.69.192.247]) by mx.google.com with ESMTPSA id iq3sm1221768pbb.71.2014.10.09.12.09.47 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Oct 2014 12:09:51 -0700 (PDT)
Message-ID: <5436DD82.9080308@gmail.com>
Date: Fri, 10 Oct 2014 08:09:54 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <5435953A.7010904@gmail.com> <5436DB6C.8040507@si6networks.com>
In-Reply-To: <5436DB6C.8040507@si6networks.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/e1DZi7dgs_JHy-tliYL5EGzgnoU
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 19:09:53 -0000

Hey, that was quick - my mail agent received it simultaneously
with sending my message saying "please reply" ;-).

Can you send me an exact text change please? This is on the
IESG agenda for 2014-10-16 so it would be good to clear this
up immediately.

Regards
   Brian

On 10/10/2014 08:01, Fernando Gont wrote:
> Hi, Brian,
> 
> On 10/08/2014 04:49 PM, Brian E Carpenter wrote:
>> Fernando - this text originally came from you, can you clarify please?
>> If this needs a wording change, we need to know quickly.
> 
> For Linux, it turns out that this is supported, but "disabled by default".
> 
> So I'm not sure whether we should add a new tag such as "DISABLED", or
> mark the corresponding entries as "ROUTE".
> 
> Thanks,


From nobody Thu Oct  9 12:12:41 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A34B1A1B20 for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:12:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 C8gxfcm_vgDl for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:12:38 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 744F61A1AEC for <ipv6@ietf.org>; Thu,  9 Oct 2014 12:12:38 -0700 (PDT)
Received: from [2001:5c0:1400:a::7e5] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1XcJ8b-0004M3-Ft; Thu, 09 Oct 2014 21:12:33 +0200
Message-ID: <5436DDA1.1030605@si6networks.com>
Date: Thu, 09 Oct 2014 16:10:25 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>,  Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com>
In-Reply-To: <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/22rWg5R5SYEhFBuOr6TXQw2yj2U
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 19:12:39 -0000

On 10/08/2014 11:42 PM, Lorenzo Colitti wrote:
> Another reason why you might not want to set accept_ra_rt_info_max_plen
> in the real wold is that doing so creates a DoS scenario where an
> attacker can consume all your routing table slots by sending you tens of
> thousands of RIOs.

I think that what you want is really a limit on the number of routing
table entries, Actually, by by setting a small "max prefix len" to
mitigate the DoS attack, RIOs become useless (you'd probably only allow
/16s or the like, which renders RIOs pretty useless).

Implmentations such as OpenBSD enforce the kind of limit that I'm
referring to.



> The kernel has protections against configuring too many autoconf
> addresses (defaults to max 16), but nothing against configuring too many
> routes.
> 
> I suppose an attacker who can mount such an attack can already send you
> RAs from ulimited link-local addresses, so perhaps there's no additional
> risk here?

Many implementations already enforce a limit on the maximum number of
routers, too.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Oct  9 12:12:58 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 656D21A1B35 for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:12:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 aRgqo1gaWCVc for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:12:49 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51DD61A1B2D for <ipv6@ietf.org>; Thu,  9 Oct 2014 12:12:49 -0700 (PDT)
Received: from [2001:5c0:1400:a::7e5] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1XcJ8i-0004MC-6h; Thu, 09 Oct 2014 21:12:40 +0200
Message-ID: <5436DE14.6000104@si6networks.com>
Date: Thu, 09 Oct 2014 16:12:20 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>,  Ole Troan <otroan@employees.org>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com> <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org> <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com> <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org> <CAKD1Yr3Pb7Pd7xWS29Rx_1He71Zx5vnPPdMmc6m=5dYgmeznng@mail.gmail.com>
In-Reply-To: <CAKD1Yr3Pb7Pd7xWS29Rx_1He71Zx5vnPPdMmc6m=5dYgmeznng@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/gMI97YY4oGvUXESCW9dMJTqVzZM
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 19:12:56 -0000

On 10/09/2014 07:52 AM, Lorenzo Colitti wrote:
> On Thu, Oct 9, 2014 at 7:46 PM, Ole Troan <otroan@employees.org
> <mailto:otroan@employees.org>> wrote:
> 
>     RFC4191 says:
>        Routers SHOULD NOT send more than 17 Route Information Options in
>        Router Advertisements per link.  This arbitrary bound is meant to
>        reinforce that relatively few and carefully selected routes should be
>        advertised to hosts.
> 
>     following that a host implementation shouldn't accept an arbitrary
>     large number of RIOs from a single router.
>     if you re-read what I say above, a robust host implementation should
>     also have a limit of the number of routers it accepts on a link. and
>     obviously also the rate of RAs it receive.
> 
> 
> Sounds like a reasonable assertion. Do you know of a robust host
> implementation?

OpenBSD.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Oct  9 12:14:56 2014
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AD98D1A1B6D for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:14:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 Yc11c0F09s_f for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:14:53 -0700 (PDT)
Received: from mail-la0-x235.google.com (mail-la0-x235.google.com [IPv6:2a00:1450:4010:c03::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9AB0B1A1B59 for <ipv6@ietf.org>; Thu,  9 Oct 2014 12:14:52 -0700 (PDT)
Received: by mail-la0-f53.google.com with SMTP id gq15so1838487lab.40 for <ipv6@ietf.org>; Thu, 09 Oct 2014 12:14:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=0iNYRW992zidYDt7P0Qroe56zLE26NtE6zfK57wBH2U=; b=wFJoJyZNrxX1OPTPLBq59VbHff8ZAAUT3QGqKa/s7zLwccdq+sqQgTUgfUwNKIdPlF B/SIKTw5ELTacG8wsJO9sifVwLKE6SkN/sRn7JNCkaJzH3Aykz/Cg0OgeFcUSBvl+eXl OcAFSrsrfxEkIn1PevxLIBTWY3Y5jLx+yTf8ca00QugK971rfh7fljUBtwLF2CuWgSxE L+ksmteiGRbe8Mr90cCKNrE+u8+zPAPQWOU2E3HMgTQeI8lq2PdaeudByHUSMEwSuHKJ UbL0TBuU3D5tecCNbcXt6yDp5EXhlFt/4xjX1rRyJ1fsYMjrTj5uGjgcM4gTPgxuuivZ jMVA==
X-Received: by 10.152.87.146 with SMTP id ay18mr9303416lab.72.1412882090914; Thu, 09 Oct 2014 12:14:50 -0700 (PDT)
Received: from [188.117.15.109] ([188.117.15.109]) by mx.google.com with ESMTPSA id eg2sm1187794lbb.29.2014.10.09.12.14.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Oct 2014 12:14:50 -0700 (PDT)
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Jouni <jouni.nospam@gmail.com>
In-Reply-To: <5436DB6C.8040507@si6networks.com>
Date: Thu, 9 Oct 2014 22:14:47 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <ED4F7579-3048-46A4-9D5D-22ACE8C261CB@gmail.com>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <5435953A.7010904@gmail.com> <5436DB6C.8040507@si6networks.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/jyQcTufXSuvPnvrTDf666PBoHxc
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 19:14:54 -0000

Please recheck *BSDs support as well.. I have used RFC4191 stuff =
successfully on *BSDs years ago.

- Jouni

On Oct 9, 2014, at 10:01 PM, Fernando Gont wrote:

> Hi, Brian,
>=20
> On 10/08/2014 04:49 PM, Brian E Carpenter wrote:
>> Fernando - this text originally came from you, can you clarify =
please?
>> If this needs a wording change, we need to know quickly.
>=20
> For Linux, it turns out that this is supported, but "disabled by =
default".
>=20
> So I'm not sure whether we should add a new tag such as "DISABLED", or
> mark the corresponding entries as "ROUTE".
>=20
> Thanks,
> --=20
> Fernando Gont
> SI6 Networks
> e-mail: fgont@si6networks.com
> PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492
>=20
>=20
>=20
>=20


From nobody Thu Oct  9 12:18:15 2014
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C15E21A1B9A for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 Kq-XhCyFjer6 for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 12:18:12 -0700 (PDT)
Received: from mail-lb0-x22b.google.com (mail-lb0-x22b.google.com [IPv6:2a00:1450:4010:c04::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C08261A1BAC for <ipv6@ietf.org>; Thu,  9 Oct 2014 12:18:11 -0700 (PDT)
Received: by mail-lb0-f171.google.com with SMTP id z12so1780560lbi.2 for <ipv6@ietf.org>; Thu, 09 Oct 2014 12:18:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=HejRZQHy+GMCtqjRbTL0FvqE9DgKwJyV3uou6oI1eyg=; b=Dz/f/nRZjwvbE6RAAC9JuM0VuCvtzZzSP/wn5n20c+3UQ/6t6Hvzd7KtsVo728XXiZ pnRuenRi+N0thphg0OiSLkQajCoLKcy5HwtR3kWG+O+qiLKDz5EyFJlfECtH9ZV9DdJs u1fsFmHkQIcYJGoatNx2X48ignvi9rvzcp2VYvxw/cZtDhmmTCV5YrugKRn1BCqbXUgn 9S0HkyCOK3ru+X5GwfuBdn7cxaTMhDCxpPx6hj8+nd3PlNTJfiGLSlGDRx874tnlyzA4 UMFTEv0qhR+k96UwlOdK2uw/nrB/AJHd5YtPAAwTB4yElwYW4cTfWbrOBHbAVIrilwze e59A==
X-Received: by 10.112.52.74 with SMTP id r10mr19776052lbo.3.1412882289989; Thu, 09 Oct 2014 12:18:09 -0700 (PDT)
Received: from [188.117.15.109] ([188.117.15.109]) by mx.google.com with ESMTPSA id qg4sm1187038lbb.36.2014.10.09.12.18.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Oct 2014 12:18:09 -0700 (PDT)
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt (Fernando, please reply)
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=us-ascii
From: Jouni <jouni.nospam@gmail.com>
In-Reply-To: <5436DC43.1060004@gmail.com>
Date: Thu, 9 Oct 2014 22:18:07 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <AEEBF81F-0C15-4AFC-9D52-CD91DD079349@gmail.com>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com> <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org> <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com> <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org> <5436746E.9000804@gmail.com> <5436DC43.1060004@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1283)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/CEOwyBzEkroZxD26TOBzkV8u504
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 19:18:13 -0000

On Oct 9, 2014, at 10:04 PM, Brian E Carpenter wrote:

> On 10/10/2014 00:41, Jouni Korhonen wrote:
>> I would be in favor of removing RIO stuff.. unless there is better
>> justification for the current text. We used RIOs successfully in Linuxes
>> and *BSDs already around 4-5 years ago in some projects.
> 
> I don't see any justification for removing the text at this late stage.

Like claiming bogus stuff?

> What I do need (as document editor) is clarification from Fernando
> about what this NOT-SUP actually relates to. If it means the shipped
> default Linux configuration that is what the document should say.

This would serve as "better justification" I refer to in my previous mail.

- Jouni


> 
>    Brian
> 
>> 
>> - Jouni
>> 
>> 10/9/2014 1:46 PM, Ole Troan kirjoitti:
>>> Lorenzo,
>>> 
>>>> a router should only send 17 RIOs in any RA per link (RFC4191). I
>>>> would hope any host implementation would have also an upper bound on
>>>> the number of routers it accepts on a link. given that I don't see
>>>> much of an attack here.
>>>> 
>>>> The router can only send 17 RIOs per packet, but it can send you 100
>>>> pps or 1000 pps of them. There's no limit on the number of routers
>>>> that I can see.
>>> 
>>> RFC4191 says:
>>>    Routers SHOULD NOT send more than 17 Route Information Options in
>>>    Router Advertisements per link.  This arbitrary bound is meant to
>>>    reinforce that relatively few and carefully selected routes should be
>>>    advertised to hosts.
>>> 
>>> following that a host implementation shouldn't accept an arbitrary
>>> large number of RIOs from a single router.
>>> if you re-read what I say above, a robust host implementation should
>>> also have a limit of the number of routers it accepts on a link. and
>>> obviously also the rate of RAs it receive.
>>> 
>>>> 
>>>> with regards to NOT-SUPor not, if it isn't on by default it might as
>>>> well not be implemented.
>>>> 
>>>> It doesn't matter what the Linux default is, it matters what the
>>>> default is on products that use Linux.
>>> 
>>> to get back on topic. RIO isn't directly relevant to the why64 draft,
>>> so if the text if contentious I'd suggest you'd just remove the RIO
>>> column.
>>> 
>>> cheers,
>>> Ole
>>> --------------------------------------------------------------------
>>> 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
>> --------------------------------------------------------------------
>> 


From nobody Thu Oct  9 16:17:07 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D51F1A908D for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 16:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 LFXyF-TsdVnE for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 16:17:01 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7EDA31A1BC6 for <ipv6@ietf.org>; Thu,  9 Oct 2014 16:17:01 -0700 (PDT)
Received: from [2001:5c0:1400:a::257] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1XcMx4-0006Rn-O6; Fri, 10 Oct 2014 01:16:55 +0200
Message-ID: <543714D2.1010401@si6networks.com>
Date: Thu, 09 Oct 2014 20:05:54 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Jouni Korhonen <jouni.nospam@gmail.com>, Ole Troan <otroan@employees.org>,  Lorenzo Colitti <lorenzo@google.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com> <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org> <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com> <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org> <5436746E.9000804@gmail.com>
In-Reply-To: <5436746E.9000804@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/8C2GA10ey1reIL2BXXH-uf1IAnc
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 09 Oct 2014 23:17:04 -0000

On 10/09/2014 08:41 AM, Jouni Korhonen wrote:
> I would be in favor of removing RIO stuff.. unless there is better
> justification for the current text. We used RIOs successfully in Linuxes
> and *BSDs already around 4-5 years ago in some projects.

Can you advice how you got it to work?  I've just checked FreeBSD 9.2
and FreeBSD 10.0, and they don't seem to enable RIO by default, and
there doesn't seem to be a sysctl to enable it.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Thu Oct  9 17:08:09 2014
Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C073D1A908F for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 17:08:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.164
X-Spam-Level: 
X-Spam-Status: No, score=-2.164 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 RHG-2ZKSt8AI for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 17:08:05 -0700 (PDT)
Received: from mail-ig0-x22e.google.com (mail-ig0-x22e.google.com [IPv6:2607:f8b0:4001:c05::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 402C91A6F2D for <ipv6@ietf.org>; Thu,  9 Oct 2014 17:08:05 -0700 (PDT)
Received: by mail-ig0-f174.google.com with SMTP id a13so770599igq.1 for <ipv6@ietf.org>; Thu, 09 Oct 2014 17:08:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=PlMEfB4EvT0DZasdWhvbWo8jaj1ArzhPyxDRTSwLqBY=; b=chOQLl3JpCuCzxY5eBO/burOkUpyHLat0kvsTxgZuzLbsDWAxTNU/hdcRKMMVK44G3 bRHs7HDOCxnIzc5+UTsGHZQcT22cktCyNNVg7aj64xuizZb4+vB7zE3zqEmSL7KF7u8s 6KtzD67sb41929ceMMnHKSRRJqqFNZkv3GSYYUandsCnFYryVY2f2fBJ5qUDfLLtNHE0 qnx1H4yCT4cPtv6RcerhWXMbkbKgAljKxnPAnC+YF1LYGWDzEkJEv+uf85DESVZELwe3 pJlVt/AM/a2Y/OnUIP3OYeHWo6CPnRd8Ea/RuqY4JP1l5sxcgxp1W3oys+zuBM/fQ6yj 4FfQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=PlMEfB4EvT0DZasdWhvbWo8jaj1ArzhPyxDRTSwLqBY=; b=K9WLJ6FjOFEjSdYP3lehLHwCfKTa6TA/XKzY6b3k1YjFdAQU5v44H8vRzoe26vODGW NhiDJ7rqJfYMdQGGH8r6g4UE2S2iVrEZ7cLstHHeVJLcReIGoKNZkuE+iAXSoWtLYKMq PeFS7PA3F7R/fBdvIlJlGzGz8c6HNeoCjPaq+iLtb25s5WURaOsSr/wDFeiyvrY0mIl0 LqOEp6XUNy16Db8P7dhFv95ybqFHfMD0qAZJ1jEtUicK4TZ9xoqLRagTIJ34dv4P3XGE r5XhIKy2JpbEXmKm82eCYStURKYXeeG5nbk1iRFKVrR3+PP87kwkbpfZrB9NXrSLAh5n UrBg==
X-Gm-Message-State: ALoCoQnqVq06RuzJZOMDBDYPvrL4NttnoLVXi9r3vYCQJlkHaE2c8wjFeLwGJVQN6SuPq5kSsgY2
X-Received: by 10.50.122.1 with SMTP id lo1mr1833845igb.5.1412899684573; Thu, 09 Oct 2014 17:08:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.64.24.144 with HTTP; Thu, 9 Oct 2014 17:07:39 -0700 (PDT)
In-Reply-To: <5436DB6C.8040507@si6networks.com>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <5435953A.7010904@gmail.com> <5436DB6C.8040507@si6networks.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 10 Oct 2014 09:07:39 +0900
Message-ID: <CAKD1Yr0gMgayJ+Z7NJvmHaCKpvAkH7sJR3mQF7uo73fmN_-KbA@mail.gmail.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=089e01536c54cd8ef60505065764
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/ITOi1ZTN_B6siIaBrn7ZZlOdw84
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 10 Oct 2014 00:08:07 -0000

--089e01536c54cd8ef60505065764
Content-Type: text/plain; charset=UTF-8

On Fri, Oct 10, 2014 at 4:01 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> On 10/08/2014 04:49 PM, Brian E Carpenter wrote:
> > Fernando - this text originally came from you, can you clarify please?
> > If this needs a wording change, we need to know quickly.
>
> For Linux, it turns out that this is supported, but "disabled by default".
>
> So I'm not sure whether we should add a new tag such as "DISABLED", or
> mark the corresponding entries as "ROUTE".


Why not just test again with the feature enabled? After all the purpose of
the draft is to verify what implementations do with prefix lengths, not
verify if they support certain features or not.

--089e01536c54cd8ef60505065764
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On F=
ri, Oct 10, 2014 at 4:01 AM, Fernando Gont <span dir=3D"ltr">&lt;<a href=3D=
"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On 10/=
08/2014 04:49 PM, Brian E Carpenter wrote:<br>
&gt; Fernando - this text originally came from you, can you clarify please?=
<br>
&gt; If this needs a wording change, we need to know quickly.<br>
<br>
</span>For Linux, it turns out that this is supported, but &quot;disabled b=
y default&quot;.<br>
<br>
So I&#39;m not sure whether we should add a new tag such as &quot;DISABLED&=
quot;, or<br>
mark the corresponding entries as &quot;ROUTE&quot;.</blockquote><div><br><=
/div><div>Why not just test again with the feature enabled? After all the p=
urpose of the draft is to verify what implementations do with prefix length=
s, not verify if they support certain features or not.</div></div></div></d=
iv>

--089e01536c54cd8ef60505065764--


From SRS0=VMUL=7B=darou.fr=pierre.pfister@bounces.m4x.org  Thu Oct  9 23:23:50 2014
Return-Path: <SRS0=VMUL=7B=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D98E81A030C for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 23:23:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 wTwebLP9HZ5j for <ipv6@ietfa.amsl.com>; Thu,  9 Oct 2014 23:23:47 -0700 (PDT)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7833A1A02FA for <ipv6@ietf.org>; Thu,  9 Oct 2014 23:23:46 -0700 (PDT)
Received: from dhcp-10-61-101-131.cisco.com (173-38-208-169.cisco.com [173.38.208.169]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 27B171408EEFC; Fri, 10 Oct 2014 08:23:41 +0200 (CEST)
Content-Type: multipart/alternative; boundary="Apple-Mail=_51C2B02F-2DE4-434A-8E57-F16613965DDA"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <CAKD1Yr0gMgayJ+Z7NJvmHaCKpvAkH7sJR3mQF7uo73fmN_-KbA@mail.gmail.com>
Date: Fri, 10 Oct 2014 08:23:50 +0200
Message-Id: <F3D6FDE4-FB66-4C8D-8426-572D48A7A6FE@darou.fr>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <5435953A.7010904@gmail.com> <5436DB6C.8040507@si6networks.com> <CAKD1Yr0gMgayJ+Z7NJvmHaCKpvAkH7sJR3mQF7uo73fmN_-KbA@mail.gmail.com>
To: Fernando Gont <fgont@si6networks.com>
X-Mailer: Apple Mail (2.1878.6)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Fri Oct 10 08:23:42 2014 +0200 (CEST))
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/UJIvjBvLR-VpYJNPGWLYgPC1NdI
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 10 Oct 2014 06:24:46 -0000

--Apple-Mail=_51C2B02F-2DE4-434A-8E57-F16613965DDA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

I did the test on a netkit environment with a kernel 3.10. It works for =
both smaller and larger prefixes.

You have to set sysctl net.ipv6.conf.all.accept_ra_rt_info_max_plen=3D128 =
in order to allow any prefix length.
You must as well compile the kernel with CONFIG_IPV6_ROUTER_PREF. That =
may have been why you didn=92t get the sysctls. But I think this is by =
default.
At least I can see it in my very-default Ubunutus and Debians.

But you can as well just look at the code. The feature is quite simple =
and is located in Linux net/ipv6/ndisc.c - ndisc_router_discovery.
All code related to that is between CONFIG_IPV6_ROUTER_PREF ifdefs.

Which is defined since (at least) 2.6.25: =
http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/net/ipv6/ndisc.=
c?v=3D2.6.25.8

Cheers

- Pierre



Le 10 oct. 2014 =E0 02:07, Lorenzo Colitti <lorenzo@google.com> a =E9crit =
:

> On Fri, Oct 10, 2014 at 4:01 AM, Fernando Gont <fgont@si6networks.com> =
wrote:
> On 10/08/2014 04:49 PM, Brian E Carpenter wrote:
> > Fernando - this text originally came from you, can you clarify =
please?
> > If this needs a wording change, we need to know quickly.
>=20
> For Linux, it turns out that this is supported, but "disabled by =
default".
>=20
> So I'm not sure whether we should add a new tag such as "DISABLED", or
> mark the corresponding entries as "ROUTE".
>=20
> Why not just test again with the feature enabled? After all the =
purpose of the draft is to verify what implementations do with prefix =
lengths, not verify if they support certain features or not.
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


--Apple-Mail=_51C2B02F-2DE4-434A-8E57-F16613965DDA
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>I =
did the test on a netkit environment with a kernel 3.10. It works for =
both smaller and larger prefixes.</div><div><br></div><div>You have to =
set sysctl net.ipv6.conf.all.accept_ra_rt_info_max_plen=3D128 in order =
to allow any prefix length.</div><div>You must as well compile the =
kernel with CONFIG_IPV6_ROUTER_PREF. That may have been why you didn=92t =
get the sysctls. But I think this is by default.</div><div>At least I =
can see it in my very-default Ubunutus and =
Debians.</div><div><br></div><div>But you can as well just look at the =
code. The feature is quite simple and is located in Linux =
net/ipv6/ndisc.c - ndisc_router_discovery.</div><div>All code related to =
that is between CONFIG_IPV6_ROUTER_PREF =
ifdefs.</div><div><br></div><div>Which is defined since (at least) =
2.6.25:&nbsp;<a =
href=3D"http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/net/ipv=
6/ndisc.c?v=3D2.6.25.8">http://www.cs.fsu.edu/~baker/devices/lxr/http/sour=
ce/linux/net/ipv6/ndisc.c?v=3D2.6.25.8</a></div><div><br></div><div>Cheers=
</div><div><br></div><div>- =
Pierre</div><div><br></div><div><br></div><br><div><div>Le 10 oct. 2014 =
=E0 02:07, Lorenzo Colitti &lt;<a =
href=3D"mailto:lorenzo@google.com">lorenzo@google.com</a>&gt; a =E9crit =
:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div dir=3D"ltr"><div class=3D"gmail_extra"><div =
class=3D"gmail_quote">On Fri, Oct 10, 2014 at 4:01 AM, Fernando Gont =
<span dir=3D"ltr">&lt;<a href=3D"mailto:fgont@si6networks.com" =
target=3D"_blank">fgont@si6networks.com</a>&gt;</span> =
wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">On =
10/08/2014 04:49 PM, Brian E Carpenter wrote:<br>
&gt; Fernando - this text originally came from you, can you clarify =
please?<br>
&gt; If this needs a wording change, we need to know quickly.<br>
<br>
</span>For Linux, it turns out that this is supported, but "disabled by =
default".<br>
<br>
So I'm not sure whether we should add a new tag such as "DISABLED", =
or<br>
mark the corresponding entries as =
"ROUTE".</blockquote><div><br></div><div>Why not just test again with =
the feature enabled? After all the purpose of the draft is to verify =
what implementations do with prefix lengths, not verify if they support =
certain features or not.</div></div></div></div>
=
--------------------------------------------------------------------<br>IE=
TF IPv6 working group mailing list<br><a =
href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a><br>Administrative =
Requests: =
https://www.ietf.org/mailman/listinfo/ipv6<br>----------------------------=
----------------------------------------<br></blockquote></div><br></body>=
</html>=

--Apple-Mail=_51C2B02F-2DE4-434A-8E57-F16613965DDA--


From nobody Fri Oct 10 01:19:35 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B8911A1BB7 for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 01:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 9tIQDW05aP_c for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 01:19:31 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B3161A1BAA for <ipv6@ietf.org>; Fri, 10 Oct 2014 01:19:30 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtYEAFeVN1StJssW/2dsb2JhbABgFoNLWAHLNIdLAoEeAXuEBAEBAwF5BQsLRlcGiEkIDcJ2AQEBAQEBAQEBAQEBAQEBAQEBAQEBF5ARMweDLYEeAQSYfZpfg3k7LwEBAQGCRgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,690,1406592000"; d="scan'208";a="205342963"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 10 Oct 2014 08:19:28 +0000
Received: from dhcp-10-61-103-184.cisco.com (dhcp-10-61-103-184.cisco.com [10.61.103.184]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s9A8JS9h002750 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 10 Oct 2014 08:19:28 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
From: Ole Troan <otroan@employees.org>
In-Reply-To: <F3D6FDE4-FB66-4C8D-8426-572D48A7A6FE@darou.fr>
Date: Fri, 10 Oct 2014 10:19:28 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <C08E49E4-9686-420A-958B-FF028459AE12@employees.org>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <5435953A.7010904@gmail.com> <5436DB6C.8040507@si6networks.com> <CAKD1Yr0gMgayJ+Z7NJvmHaCKpvAkH7sJR3mQF7uo73fmN_-KbA@mail.gmail.com> <F3D6FDE4-FB66-4C8D-8426-572D48A7A6FE@darou.fr>
To: Pierre Pfister <pierre.pfister@darou.fr>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/qjHYQ1RoRp8C4DQVTD3rCPas954
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 10 Oct 2014 08:19:32 -0000

[mostly off topic warning]

Pierre,

> I did the test on a netkit environment with a kernel 3.10. It works =
for both smaller and larger prefixes.
>=20
> You have to set sysctl =
net.ipv6.conf.all.accept_ra_rt_info_max_plen=3D128 in order to allow any =
prefix length.
> You must as well compile the kernel with CONFIG_IPV6_ROUTER_PREF. That =
may have been why you didn=92t get the sysctls. But I think this is by =
default.
> At least I can see it in my very-default Ubunutus and Debians.
>=20
> But you can as well just look at the code. The feature is quite simple =
and is located in Linux net/ipv6/ndisc.c - ndisc_router_discovery.
> All code related to that is between CONFIG_IPV6_ROUTER_PREF ifdefs.
>=20
> Which is defined since (at least) 2.6.25: =
http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/net/ipv6/ndisc.=
c?v=3D2.6.25.8

you meant CONFIG_IPV6_ROUTE_INFO?

any idea of the rationale for accept_ra_rt_info_max_plen?
that just doesn't seem like something that has a sensible use case.

cheers,
Ole


From nobody Fri Oct 10 01:29:58 2014
Return-Path: <SRS0=VMUL=7B=darou.fr=pierre.pfister@bounces.m4x.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A35D31A6F1D for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 01:29:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 yXBGxLRhK-Am for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 01:29:54 -0700 (PDT)
Received: from mx1.polytechnique.org (mx1.polytechnique.org [129.104.30.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70FD51A6EF4 for <ipv6@ietf.org>; Fri, 10 Oct 2014 01:29:54 -0700 (PDT)
Received: from [192.168.0.15] (roo49-3-88-173-49-87.fbx.proxad.net [88.173.49.87]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ssl.polytechnique.org (Postfix) with ESMTPSA id 4AA81140C5BA2; Fri, 10 Oct 2014 10:29:51 +0200 (CEST)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
From: Pierre Pfister <pierre.pfister@darou.fr>
In-Reply-To: <C08E49E4-9686-420A-958B-FF028459AE12@employees.org>
Date: Fri, 10 Oct 2014 10:29:58 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB5BF339-3C35-4A38-B216-92E6E661AFAF@darou.fr>
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <5435953A.7010904@gmail.com> <5436DB6C.8040507@si6networks.com> <CAKD1Yr0gMgayJ+Z7NJvmHaCKpvAkH7sJR3mQF7uo73fmN_-KbA@mail.gmail.com> <F3D6FDE4-FB66-4C8D-8426-572D48A7A6FE@darou.fr> <C08E49E4-9686-420A-958B-FF028459AE12@employees.org>
To: Ole Troan <otroan@employees.org>
X-Mailer: Apple Mail (2.1878.6)
X-AV-Checked: ClamAV using ClamSMTP at svoboda.polytechnique.org (Fri Oct 10 10:29:52 2014 +0200 (CEST))
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/MSxImZSSeeDmSngGiC5yOCue7DY
Cc: Fernando Gont <fgont@si6networks.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 10 Oct 2014 08:29:56 -0000

Le 10 oct. 2014 =E0 10:19, Ole Troan <otroan@employees.org> a =E9crit :

> [mostly off topic warning]
>=20
> Pierre,
>=20
>> I did the test on a netkit environment with a kernel 3.10. It works =
for both smaller and larger prefixes.
>>=20
>> You have to set sysctl =
net.ipv6.conf.all.accept_ra_rt_info_max_plen=3D128 in order to allow any =
prefix length.
>> You must as well compile the kernel with CONFIG_IPV6_ROUTER_PREF. =
That may have been why you didn=92t get the sysctls. But I think this is =
by default.
>> At least I can see it in my very-default Ubunutus and Debians.
>>=20
>> But you can as well just look at the code. The feature is quite =
simple and is located in Linux net/ipv6/ndisc.c - =
ndisc_router_discovery.
>> All code related to that is between CONFIG_IPV6_ROUTER_PREF ifdefs.
>>=20
>> Which is defined since (at least) 2.6.25: =
http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/net/ipv6/ndisc.=
c?v=3D2.6.25.8
>=20
> you meant CONFIG_IPV6_ROUTE_INFO?

Indeed, wrong copy/paste.

>=20
> any idea of the rationale for accept_ra_rt_info_max_plen?
> that just doesn't seem like something that has a sensible use case.

I agree.
It seems they were concerned by possible attacks. Redirecting some part =
of the traffic.
Of course you can redirect all the traffic with basic RAs.=20
I think they saw that as an even wider open door for man-in-the-middle =
attacks.

Cheers,

- PIerre

>=20
> cheers,
> Ole
>=20


From nobody Fri Oct 10 02:30:00 2014
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5094F1A86E5 for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 02:29:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 y-rZSHR_FRMS for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 02:29:54 -0700 (PDT)
Received: from mail-la0-x22e.google.com (mail-la0-x22e.google.com [IPv6:2a00:1450:4010:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94EA11A86DD for <ipv6@ietf.org>; Fri, 10 Oct 2014 02:29:53 -0700 (PDT)
Received: by mail-la0-f46.google.com with SMTP id gi9so2864284lab.33 for <ipv6@ietf.org>; Fri, 10 Oct 2014 02:29:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=C3PPIKuMAkd4QuYXqvHeETC5HqVWYLaGB8BQRMUTJEo=; b=xbHLvZA/887R1XX4yeKwiH0WflZDgDp2Aq+DraHCunHqKF6RyPMGpbw8lCnVt5eJGO iMsTqszciIkIBDTLRVCFs1MV9eCMCuYvfuHzxzykJ3WedkPJa5jzIP9uDob3EfowL6tb zsSSKWHj/M/Y5wY/+lkDLQi1ckowG/DL2p0iZLIM1Zl7CGTPW1gBQ57REGt5/rTsoYEB +7Yp3ZQu9HYqfezIdgNXvm4FWd1hA9XZuOll8CrKWj2JWaVhPUzd2XIla65azmZUMUnu MB2muuVpuziuQ4yejVjB9pZ+PMjkzCvTk84Z1UE3EwB/J0uAsJ47CxqPRhKk9glf6Q0+ +zbA==
X-Received: by 10.152.9.37 with SMTP id w5mr3501172laa.28.1412933391707; Fri, 10 Oct 2014 02:29:51 -0700 (PDT)
Received: from [10.17.0.23] ([83.150.126.201]) by mx.google.com with ESMTPSA id zt1sm1661084lbc.31.2014.10.10.02.29.50 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 10 Oct 2014 02:29:50 -0700 (PDT)
Message-ID: <5437A716.7030205@gmail.com>
Date: Fri, 10 Oct 2014 12:29:58 +0300
From: Jouni Korhonen <jouni.nospam@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Fernando Gont <fgont@si6networks.com>, Ole Troan <otroan@employees.org>, Lorenzo Colitti <lorenzo@google.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com> <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org> <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com> <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org> <5436746E.9000804@gmail.com> <543714D2.1010401@si6networks.com>
In-Reply-To: <543714D2.1010401@si6networks.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/GOQ5ppzRVfq6jORlrrV0pixjoCI
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 10 Oct 2014 09:29:55 -0000

Fernando,

Linux was straight forward (enable the experimental feature, compile 
kernel, and config). If I recall that was very early 3.x kernel or even 
2.x stuff.

*BSD I have very little memory. It *might* have been that we only used 
router preferences in the host (and not RIO). rtadvd on *BSD might have 
been the thing we used RIOs..

- jouni


10/10/2014 2:05 AM, Fernando Gont kirjoitti:
> On 10/09/2014 08:41 AM, Jouni Korhonen wrote:
>> I would be in favor of removing RIO stuff.. unless there is better
>> justification for the current text. We used RIOs successfully in Linuxes
>> and *BSDs already around 4-5 years ago in some projects.
>
> Can you advice how you got it to work?  I've just checked FreeBSD 9.2
> and FreeBSD 10.0, and they don't seem to enable RIO by default, and
> there doesn't seem to be a sysctl to enable it.
>
> Thanks,
>


From nobody Fri Oct 10 06:26:19 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E9351ACDFC for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 06:26:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 6UBMIRTKL20Q for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 06:26:03 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDBB11A19FF for <ipv6@ietf.org>; Fri, 10 Oct 2014 06:26:02 -0700 (PDT)
Received: from [2001:5c0:1400:a::313] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1XcaCg-0001Zb-70; Fri, 10 Oct 2014 15:25:54 +0200
Message-ID: <5437DE54.2000907@si6networks.com>
Date: Fri, 10 Oct 2014 10:25:40 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>, Pierre Pfister <pierre.pfister@darou.fr>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <5435953A.7010904@gmail.com> <5436DB6C.8040507@si6networks.com> <CAKD1Yr0gMgayJ+Z7NJvmHaCKpvAkH7sJR3mQF7uo73fmN_-KbA@mail.gmail.com> <F3D6FDE4-FB66-4C8D-8426-572D48A7A6FE@darou.fr> <C08E49E4-9686-420A-958B-FF028459AE12@employees.org>
In-Reply-To: <C08E49E4-9686-420A-958B-FF028459AE12@employees.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/E1YWWtEg1Eom0gD-5b5zi29d7UU
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 10 Oct 2014 13:26:06 -0000

Hi, Ole,

On 10/10/2014 05:19 AM, Ole Troan wrote:
>>
>> You have to set sysctl net.ipv6.conf.all.accept_ra_rt_info_max_plen=128 in order to allow any prefix length.
>> You must as well compile the kernel with CONFIG_IPV6_ROUTER_PREF. That may have been why you didn’t get the sysctls. But I think this is by default.
>> At least I can see it in my very-default Ubunutus and Debians.
>>
>> But you can as well just look at the code. The feature is quite simple and is located in Linux net/ipv6/ndisc.c - ndisc_router_discovery.
>> All code related to that is between CONFIG_IPV6_ROUTER_PREF ifdefs.
>>
>> Which is defined since (at least) 2.6.25: http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/net/ipv6/ndisc.c?v=2.6.25.8
> 
> you meant CONFIG_IPV6_ROUTE_INFO?
> 
> any idea of the rationale for accept_ra_rt_info_max_plen?
> that just doesn't seem like something that has a sensible use case.

The use case, if any, is to prevent, say, RAs advertising very long
prefixes. For example, such a thing could be leveraged to insert
lobger-matching rules that could e.g. make traffic meant to go over a
VPN tunnel to go somewhere else in the clear. (Yes, you need to take
care of ICMPv6 Redirects, too).

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Fri Oct 10 06:27:06 2014
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3B481ACDCF for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 06:27:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 3q9DuvqCC3wM for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 06:26:59 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [37.72.100.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C126C1ACE0A for <ipv6@ietf.org>; Fri, 10 Oct 2014 06:26:53 -0700 (PDT)
Received: from [2001:5c0:1400:a::313] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fernando@gont.com.ar>) id 1XcaCa-0001ZU-3g; Fri, 10 Oct 2014 15:25:48 +0200
Message-ID: <5437DDBA.3080002@gont.com.ar>
Date: Fri, 10 Oct 2014 10:23:06 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Jouni Korhonen <jouni.nospam@gmail.com>, Ole Troan <otroan@employees.org>,  Lorenzo Colitti <lorenzo@google.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <CAKD1Yr1LO5=Y_y7WcT9iFhdSs5OP9KAvdTt64Ma_JWu2+Aqqbg@mail.gmail.com> <C615F33C-27A1-4CAC-A80C-ED6B5D8F584E@employees.org> <CAKD1Yr14sxEupQbmM1EioRiJu+2VAKo6mLpo8E-UvCs35V1dRw@mail.gmail.com> <2A50C29E-EB23-4A77-AEB8-E3FC492FAB63@employees.org> <5436746E.9000804@gmail.com> <543714D2.1010401@si6networks.com> <5437A716.7030205@gmail.com>
In-Reply-To: <5437A716.7030205@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/QRhot_-0j_I5yTi4beo6mq-kyJk
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 10 Oct 2014 13:27:01 -0000

Hi, Jouni,

On 10/10/2014 06:29 AM, Jouni Korhonen wrote:
> 
> *BSD I have very little memory. It *might* have been that we only used
> router preferences in the host (and not RIO). rtadvd on *BSD might have
> been the thing we used RIOs..

That sounds like a possible case -- however, in ur case we were
assessing host support.. and *BSD doesn't seem to support RIO.

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Fri Oct 10 06:28:24 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E97721ACDFE for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 06:28:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Qi5cYoVaRJCt for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 06:28:20 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [37.72.100.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B19DA1ACDCF for <ipv6@ietf.org>; Fri, 10 Oct 2014 06:28:20 -0700 (PDT)
Received: from [2001:5c0:1400:a::313] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1XcaEy-0001aZ-8f; Fri, 10 Oct 2014 15:28:16 +0200
Message-ID: <5437DEEC.6000808@si6networks.com>
Date: Fri, 10 Oct 2014 10:28:12 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
Subject: Re: I-D Action: draft-ietf-6man-why64-04.txt
References: <20140910024842.5686.92961.idtracker@ietfa.amsl.com> <540FBDB8.4010701@gmail.com> <5433A5C9.9060203@gmail.com> <6FCA1EAA-158B-4FC5-97E2-E11B2D2A1CE7@darou.fr> <5435953A.7010904@gmail.com> <5436DB6C.8040507@si6networks.com> <CAKD1Yr0gMgayJ+Z7NJvmHaCKpvAkH7sJR3mQF7uo73fmN_-KbA@mail.gmail.com>
In-Reply-To: <CAKD1Yr0gMgayJ+Z7NJvmHaCKpvAkH7sJR3mQF7uo73fmN_-KbA@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/5vkj_V2mSIWe0Sl8i7ih5vf8tBc
Cc: IETF IPv6 Mailing List <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 10 Oct 2014 13:28:22 -0000

On 10/09/2014 09:07 PM, Lorenzo Colitti wrote:
> 
>     So I'm not sure whether we should add a new tag such as "DISABLED", or
>     mark the corresponding entries as "ROUTE".
> 
> 
> Why not just test again with the feature enabled? After all the purpose
> of the draft is to verify what implementations do with prefix lengths,
> not verify if they support certain features or not.

That's why I said that we might just flag Linux as "ROUTE", if we don't
care about the fact that such support is disabled by default.

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Fri Oct 10 14:09:13 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AACF41AD3F3; Fri, 10 Oct 2014 14:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 ik2X5-6BUfmb; Fri, 10 Oct 2014 14:09:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E552F1AD3F8; Fri, 10 Oct 2014 14:09:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-ipv6-address-generation-privacy-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141010210900.2288.20552.idtracker@ietfa.amsl.com>
Date: Fri, 10 Oct 2014 14:09:00 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/WsgI-nB4Kqn2eq4bFVzsEzVkRz8
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 10 Oct 2014 21:09:09 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Privacy Considerations for IPv6 Address Generation Mechanisms
        Authors         : Alissa Cooper
                          Fernando Gont
                          Dave Thaler
	Filename        : draft-ietf-6man-ipv6-address-generation-privacy-02.txt
	Pages           : 16
	Date            : 2014-10-10

Abstract:
   This document discusses privacy and security considerations for
   several IPv6 address generation mechanisms, both standardized and
   non-standardized.  It evaluates how different mechanisms mitigate
   different threats and the trade-offs that implementors, developers,
   and users face in choosing different addresses or address generation
   mechanisms.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-ipv6-address-generation-privacy/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-ipv6-address-generation-privacy-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-ipv6-address-generation-privacy-02


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Fri Oct 10 23:54:22 2014
Return-Path: <dale.carder@wisc.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 729C41A1B27 for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 23:54:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.987
X-Spam-Level: 
X-Spam-Status: No, score=-4.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 O432AcMVz0er for <ipv6@ietfa.amsl.com>; Fri, 10 Oct 2014 23:54:20 -0700 (PDT)
Received: from smtpauth3.wiscmail.wisc.edu (wmauth3.doit.wisc.edu [144.92.197.226]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0CCB11A1B20 for <ipv6@ietf.org>; Fri, 10 Oct 2014 23:54:19 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 8BIT
Content-disposition: inline
Content-type: text/plain; charset=utf-8
Received: from avs-daemon.smtpauth3.wiscmail.wisc.edu by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) id <0ND900800PG8UM00@smtpauth3.wiscmail.wisc.edu> for ipv6@ietf.org; Sat, 11 Oct 2014 01:54:18 -0500 (CDT)
X-Spam-PmxInfo: Server=avs-3, Version=6.1.1.2430161, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.10.11.64221, SenderIP=0.0.0.0
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1lp0140.outbound.protection.outlook.com [207.46.163.140]) by smtpauth3.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) with ESMTPS id <0ND9002KIPUH7900@smtpauth3.wiscmail.wisc.edu>; Sat, 11 Oct 2014 01:54:17 -0500 (CDT)
Received: from havarti.local (68.185.171.106) by DM2PR06MB688.namprd06.prod.outlook.com (10.141.179.156) with Microsoft SMTP Server (TLS) id 15.0.1039.15; Sat, 11 Oct 2014 06:54:14 +0000
Date: Sat, 11 Oct 2014 01:54:07 -0500
From: "Dale W. Carder" <dwcarder@wisc.edu>
To: Tore Anderson <tore@fud.no>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
Message-id: <20141011065407.GA14879@havarti.local>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no>
In-reply-to: <542FB7A2.6060208@fud.no>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Originating-IP: [68.185.171.106]
X-ClientProxiedBy: BL2PR05CA0030.namprd05.prod.outlook.com (10.255.226.30) To DM2PR06MB688.namprd06.prod.outlook.com (10.141.179.156)
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR06MB688;
X-Exchange-Antispam-Report-Test: UriScan:;
X-Forefront-PRVS: 0361212EA8
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6009001)(199003)(189002)(4396001)(88552001)(46102003)(19580395003)(76176999)(122386002)(90282001)(50466002)(33656002)(31966008)(98436002)(54356999)(110136001)(76482002)(50986999)(77096002)(89122001)(99396003)(101416001)(120916001)(85852003)(102836001)(92726001)(97736003)(21056001)(92566001)(95666004)(19580405001)(83506001)(85306004)(107046002)(23676002)(47776003)(66066001)(105586002)(42186005)(87976001)(20776003)(93886004)(64706001)(80022003)(106356001)(75432002)(40100003); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR06MB688; H:havarti.local; FPR:; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
X-OriginatorOrg: wisc.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/wI-sRkDR2NQ3TPgRAP8C-pvBDvE
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, ipv6@ietf.org, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 11 Oct 2014 06:54:21 -0000

Thus spake Tore Anderson (tore@fud.no) on Sat, Oct 04, 2014 at 11:02:26AM +0200:
> * Tim Chown
> 
> > A problem is we simply donâ€™t know who relies on it.
> > 
> > The Google stats have 6to4/Teredo traffic at 0.01%, and native
> > approaching 5%.
> 
> When we realised that the IETF wasn't ready to deprecate 6to4, we went
> straight to the software vendors instead, who *did* listen and took the
> necessary steps to deprecate/disable it in their products. So we
> fortunately succeeded in killing it without the IETF's help.

Many public relay operators also joined in and terminated service
in 2011 due to draft-ietf-v6ops-6to4-to-historic, including our relay
which at its peak was likely among the most heavily used in North America.  

Today, my route to 192.88.99.1 is in Australia (209ms) and nobody cares.

6to4 was elegantly sunsetted by implementations of rfc6724 and happy 
eyeballs despite draft-ietf-v6ops-6to4-to-historic expiring.

Dale


From nobody Sat Oct 11 00:54:01 2014
Return-Path: <rogerj@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 176ED1A005A for <ipv6@ietfa.amsl.com>; Sat, 11 Oct 2014 00:54:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.454
X-Spam-Level: 
X-Spam-Status: No, score=0.454 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FRT_BELOW2=2.154, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 iohG3rYM7Ce6 for <ipv6@ietfa.amsl.com>; Sat, 11 Oct 2014 00:53:58 -0700 (PDT)
Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A31361A0059 for <ipv6@ietf.org>; Sat, 11 Oct 2014 00:53:58 -0700 (PDT)
Received: by mail-oi0-f43.google.com with SMTP id u20so8755463oif.16 for <ipv6@ietf.org>; Sat, 11 Oct 2014 00:53:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=5gPA3t3eSJkV+9XT8ueNi2bf9pBQAlOMOzGEeanZuKQ=; b=MCpQTVTLkkTa5+sB9FelvipyjgO983+Qdhda/NsPfCMsRa9HewZ+OVmrN7DFMkC6HI Ok2HL9gusPDtwihpOhw/atNWbxen8QS1vFNGrRQpGDBEnnv1/nyDiPBgDaQwHgUOeo4/ /D8zlEVvmROdlQQ88QlvCgzhqvPkKqWipvCKjHbaPwC3PCh5SCPrlP/rMsYdx8JFD+oe A4KzhcT1edQ2Kpea6UsoTI9RlNg3h/TME1Obu1OQ5fBcZBfqx7b5RJgqweMtEnXYev9g Y5Dqzomr1vYrHTREWSph6K1WH7oYLUGDdulbQ55dhpS1sFAiVRPxtkWIob3pTaUEV2nV kgaw==
MIME-Version: 1.0
X-Received: by 10.202.196.214 with SMTP id u205mr8781353oif.48.1413014038126;  Sat, 11 Oct 2014 00:53:58 -0700 (PDT)
Received: by 10.202.60.2 with HTTP; Sat, 11 Oct 2014 00:53:58 -0700 (PDT)
In-Reply-To: <54317DCD.90907@gont.com.ar>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <A31ABF24-A05A-40C4-8648-785CA691B072@steffann.nl> <CAKC-DJiSmrzV5UNUkv3Ow+wRBzLG=JuHKkndqt4w+4VoGt0etQ@mail.gmail.com> <543047A2.8020804@gmail.com> <54317DCD.90907@gont.com.ar>
Date: Sat, 11 Oct 2014 09:53:58 +0200
Message-ID: <CAKFn1SGQDaYqkPA1kn=87AtZLYCLXGnXgMJUabJrcwgH-ydCkA@mail.gmail.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
From: =?UTF-8?Q?Roger_J=C3=B8rgensen?= <rogerj@gmail.com>
To: Fernando Gont <fernando@gont.com.ar>, 6man <ipv6@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/1m267m7KLotbjluKS8Yi1LcxrtY
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 11 Oct 2014 07:54:00 -0000

On Sun, Oct 5, 2014 at 7:20 PM, Fernando Gont <fernando@gont.com.ar> wrote:
>
> Hi, Brian,
>
> On 10/04/2014 04:16 PM, Brian E Carpenter wrote:
>> There's another issue here that I see from time to time in under-informed
>> discussion forums such as www.theregister.co.uk/ :
>>
>> Some people believe that anybody can get an IPv6 address by sticking
>> their IPv4 address after a magic prefix. ::/96 is a popular choice
>> for that magic prefix, and judging by the azdes.gov some people
>> believe that 2002::/96 is equally magic.
>
> Question: Any ideas of what's the reasoning behind this belief?

I've heard it several places over the year and I guess it's lack of
knowledge, they don't understand (or want to understand) how things
work. That people do write it out as shown bellow don't help

"IPv6 address is calculated from IPv4 (2002:192.168.100.1::/48) "
Page 9 on https://www.ripe.net/ripe/meetings/regional-meetings/dubrovnik-2011/presentations/IPv6_Transition_Mechanisms_Ripe_07092011_v1.2.pdf


I expected to find 2002::IPv4Address in clear text on
technet.Microsoft but they seem to have not written it anywhere, only
IPv4 and then the correct representation of it on 2002:: format. Very
good:)



-- 

Roger Jorgensen           | ROJO9-RIPE
rogerj@gmail.com          | - IPv6 is The Key!
http://www.jorgensen.no   | roger@jorgensen.no


From nobody Sat Oct 11 12:25:30 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA9791A8760 for <ipv6@ietfa.amsl.com>; Sat, 11 Oct 2014 12:25:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 vjInCrUTWLnb for <ipv6@ietfa.amsl.com>; Sat, 11 Oct 2014 12:25:27 -0700 (PDT)
Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A8AF1A875E for <ipv6@ietf.org>; Sat, 11 Oct 2014 12:25:27 -0700 (PDT)
Received: by mail-pd0-f180.google.com with SMTP id fp1so3408737pdb.25 for <ipv6@ietf.org>; Sat, 11 Oct 2014 12:25:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=teyDfZdjNGdJ54K/eGeC8hziWZkOgliZp/cmr5rGBn8=; b=zWkN6MUnARU+IkgINt96wyT2AO7ynkl+fo0tOavHmJt4FARgxBlIG31/0uEjM4pzkA fem5ZI0X/0iTGEoLdPpZ6vuNrNmAN5mkLKppHd6rYWw969jVKPoN0Sqh8gZPXyYcSIZH XyQz9boFXbF9ZazH14CCNmhEqxqp4lT5O34EuPKx4FRwnO8IDHeE7weRehF7fkjn2XR3 ecp1xCo0/C4ChphZfrg2r9bHJH0xukT6VeKzBI2KMWjw63nkAUEb1fZPZo1d8V0K6qJX NqQ3ylWPqMK6R5763yIItX2f9MKDv4Z9Da+WEVRTqpKIGVUuUdL2jvt8ttySCIO2Wk/f E7Gw==
X-Received: by 10.70.10.37 with SMTP id f5mr13399551pdb.5.1413055526893; Sat, 11 Oct 2014 12:25:26 -0700 (PDT)
Received: from [192.168.178.23] (104.198.69.111.dynamic.snap.net.nz. [111.69.198.104]) by mx.google.com with ESMTPSA id po6sm6791731pbb.56.2014.10.11.12.25.22 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 11 Oct 2014 12:25:25 -0700 (PDT)
Message-ID: <54398420.3030608@gmail.com>
Date: Sun, 12 Oct 2014 08:25:20 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: "Dale W. Carder" <dwcarder@wisc.edu>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <20141011065407.GA14879@havarti.local>
In-Reply-To: <20141011065407.GA14879@havarti.local>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/r0UKDkF6kRTcP2UMDc38kxbmGUI
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Tore Anderson <tore@fud.no>, ipv6@ietf.org, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 11 Oct 2014 19:25:28 -0000

On 11/10/2014 19:54, Dale W. Carder wrote:
> Thus spake Tore Anderson (tore@fud.no) on Sat, Oct 04, 2014 at 11:02:26=
AM +0200:
>> * Tim Chown
>>
>>> A problem is we simply don=E2=80=99t know who relies on it.
>>>
>>> The Google stats have 6to4/Teredo traffic at 0.01%, and native
>>> approaching 5%.
>> When we realised that the IETF wasn't ready to deprecate 6to4, we went=

>> straight to the software vendors instead, who *did* listen and took th=
e
>> necessary steps to deprecate/disable it in their products. So we
>> fortunately succeeded in killing it without the IETF's help.
>=20
> Many public relay operators also joined in and terminated service
> in 2011 due to draft-ietf-v6ops-6to4-to-historic, including our relay
> which at its peak was likely among the most heavily used in North Ameri=
ca. =20

Many !=3D all though.

> Today, my route to 192.88.99.1 is in Australia (209ms) and nobody cares=
=2E
>=20
> 6to4 was elegantly sunsetted by implementations of rfc6724 and happy=20
> eyeballs despite draft-ietf-v6ops-6to4-to-historic expiring.

Yes, but there are still certainly millions of people running XP and the
like with old browsers, and we simply don't know how many of them are
still suffering as a result (especially if they have to go via Australia
to discover black holes). So I don't think we can assert that nobody care=
s.
Therefore, I think it's useful now to take the next step. (It's in
Ole's inbox.)

   Brian



From nobody Sun Oct 12 23:27:59 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B59DF1ACCD9 for <ipv6@ietfa.amsl.com>; Sun, 12 Oct 2014 23:27:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 7HfwPZS8EDGV for <ipv6@ietfa.amsl.com>; Sun, 12 Oct 2014 23:27:55 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25B2A1ACCC7 for <ipv6@ietf.org>; Sun, 12 Oct 2014 23:27:54 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqkEAL1wO1StJssW/2dsb2JhbABbg2FYgwa+MYlMCodNAoEoAX2EAgEBAQMBAQEBGgZLCwULCxgCAiYCAicwBhOINggNrl+UbAEBAQEBAQEBAQEBAQEBAQEBAQEBAReBLI5mMweCdzaBHgWGLZAOiD48gwqRHYN5Oy+CSgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,708,1406592000"; d="scan'208";a="209328069"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 13 Oct 2014 06:27:52 +0000
Received: from dhcp-10-61-101-249.cisco.com (dhcp-10-61-101-249.cisco.com [10.61.101.249]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s9D6Rpcd003020 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Oct 2014 06:27:51 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
From: Ole Troan <otroan@employees.org>
In-Reply-To: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>
Date: Mon, 13 Oct 2014 08:28:01 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/gtzPKQR_6wNd1N9Cefr7kdJb1q0
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 06:27:56 -0000

All,

The adoption call for draft-boucadair-6man-prefix-routing-reco for ended =
October 10th.
With only two replies, none of them in support, I can only conclude that =
there is no support to adopt this document in 6MAN.

Best regards,
Ole


> On 03 Oct 2014, at 9:28 , Ole Troan <otroan@employees.org> wrote:
>=20
> All,
>=20
> The authors have requested an adoption call for this document as a =
standards track document.
>=20
> Please provide a view with reasons as to whether the WG should adopt =
this or not.
>=20
> This message starts a one week 6MAN Working Group call on adopting:
>=20
> 	Title           : IPv6 Prefix Length Recommendation for =
Forwarding
> 	Author(s)    : M. Boucadair, A. Petrescu
> 	Filename    : draft-boucadair-6man-prefix-routing-reco-02
> 	Pages        : 4
> 	Date          : 2014-09-24
>=20
> http://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02
>=20
> The call ends on October 10th, 2014.
>=20
> Regards,
>=20
> Bob Hinden & Ole Tr=C3=B8an
>=20
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Sun Oct 12 23:30:15 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A76E1ACCDC for <ipv6@ietfa.amsl.com>; Sun, 12 Oct 2014 23:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 pW8fMoU8pEkk for <ipv6@ietfa.amsl.com>; Sun, 12 Oct 2014 23:30:12 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 071FE1A889E for <ipv6@ietf.org>; Sun, 12 Oct 2014 23:30:10 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqcEAEZwO1StJssW/2dsb2JhbABbg2FYgwa+MYlMDIdLgSoBfYQEBgEBGgZLCzUCJgIpNhOIPg2uX5RrAQEBAQEBAQECAQEBAQEBAQEBAQEXgSyPGYJ+NoEeBYYtkA6IPjyDCpEdg3k7L4JKAQEB
X-IronPort-AV: E=Sophos;i="5.04,708,1406592000"; d="scan'208";a="204569386"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 13 Oct 2014 06:30:09 +0000
Received: from dhcp-10-61-101-249.cisco.com (dhcp-10-61-101-249.cisco.com [10.61.101.249]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s9D6U8nx020570 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 13 Oct 2014 06:30:09 GMT
From: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: Adoption call of draft-gont-6man-deprecate-atomfrag-generation for 6MAN
Date: Mon, 13 Oct 2014 08:30:18 +0200
Message-Id: <2742D96E-1538-4ECF-BB3A-6A194D9DBB96@employees.org>
To: 6man WG <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/XDO3JoVZYwO2lICbDuZSHdaaAM4
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 06:30:13 -0000

All,

The authors have requested an adoption call for this document as a =
standards track document.

Please provide a view with reasons as to whether the WG should adopt =
this or not.

This message starts a one week 6MAN Working Group call on adopting:

	Title           : Deprecating the Generation of IPv6 Atomic =
Fragments
	Author(s)    : F. Gont, W. Liu
	Filename    : draft-gont-6man-deprecate-atomfrag-generation-00
	Pages        : 6
	Date          : 2014-08-19

=
http://tools.ietf.org/html/draft-gont-6man-deprecate-atomfrag-generation-0=
0

The call ends on October 20th, 2014.

Regards,

Bob Hinden & Ole Tr=C3=B8an


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


From nobody Mon Oct 13 00:15:58 2014
Return-Path: <swmike@swm.pp.se>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9D761A1AC2 for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 00:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.223
X-Spam-Level: 
X-Spam-Status: No, score=-3.223 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, URIBL_RHS_DOB=1.514] autolearn=ham
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 B9WtACPgEEDl for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 00:15:55 -0700 (PDT)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB65B1A88D7 for <ipv6@ietf.org>; Mon, 13 Oct 2014 00:15:55 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 517B9A2; Mon, 13 Oct 2014 09:15:54 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1413184554; bh=9AvaMUMRsgzogTUX2WZ2odFPD/DuP/8NI8yXn5/3El8=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=qWsCsXEWA5/i/MR7CJecLuzZcRKEMZfG3j5aFY+45EtOuc0HrTNJIHt32X0mdLLlw qvtOHckuucaGQ7na0hOgvu5viM9qtSKzCFPmzvmbRpmrQzp8ZNtFcWvxBZNhU+eK6Y uUcJzaXmYnPct7rVmd5jqeB3ZFIFlzdCzyvl/v6g=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 42B7AA1; Mon, 13 Oct 2014 09:15:54 +0200 (CEST)
Date: Mon, 13 Oct 2014 09:15:54 +0200 (CEST)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Ole Troan <otroan@employees.org>
Subject: Re: Adoption call of draft-gont-6man-deprecate-atomfrag-generation for 6MAN
In-Reply-To: <2742D96E-1538-4ECF-BB3A-6A194D9DBB96@employees.org>
Message-ID: <alpine.DEB.2.02.1410130914060.14735@uplift.swm.pp.se>
References: <2742D96E-1538-4ECF-BB3A-6A194D9DBB96@employees.org>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/4c7LzNZiCDm6wyYnQpm9JYS2yFw
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 07:15:56 -0000

On Mon, 13 Oct 2014, Ole Troan wrote:

> All,
>
> The authors have requested an adoption call for this document as a standards track document.
>
> Please provide a view with reasons as to whether the WG should adopt this or not.

I support that we're taking a good look at this problem.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se


From nobody Mon Oct 13 07:45:19 2014
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 705351A011F for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 07:45:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 Fzbmk8hAHwuO for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 07:45:09 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2097C1A0144 for <ipv6@ietf.org>; Mon, 13 Oct 2014 07:45:06 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s9DEj1ZJ003852; Mon, 13 Oct 2014 16:45:01 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 01C6B20C242; Mon, 13 Oct 2014 16:46:14 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id E719F20C108; Mon, 13 Oct 2014 16:46:13 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s9DEitdx017439; Mon, 13 Oct 2014 16:45:01 +0200
Message-ID: <543BE567.50509@gmail.com>
Date: Mon, 13 Oct 2014 16:44:55 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org>
In-Reply-To: <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/QzOt0vPhQ07GUiqMulQ-m3g08tQ
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 14:45:12 -0000

Hello,

I am surprised there is no support in favor of 
draft-boucadair-6man-prefix-routing-reco?

https://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02

Its main recommendation is:
>    Forwarding decision-making processes MUST NOT restrict by design the
>    length of IPv6 prefixes.  In particular, forwarding processes MUST be
>    designed to process prefixes of any length up to /128, by increments
>    of 1.

What do you think?

Alex

Le 13/10/2014 08:28, Ole Troan a Ã©crit :
> All,
>
> The adoption call for draft-boucadair-6man-prefix-routing-reco for
> ended October 10th. With only two replies, none of them in support, I
> can only conclude that there is no support to adopt this document in
> 6MAN.
>
> Best regards, Ole
>
>
>> On 03 Oct 2014, at 9:28 , Ole Troan <otroan@employees.org> wrote:
>>
>> All,
>>
>> The authors have requested an adoption call for this document as a
>> standards track document.
>>
>> Please provide a view with reasons as to whether the WG should
>> adopt this or not.
>>
>> This message starts a one week 6MAN Working Group call on
>> adopting:
>>
>> Title           : IPv6 Prefix Length Recommendation for Forwarding
>> Author(s)    : M. Boucadair, A. Petrescu Filename    :
>> draft-boucadair-6man-prefix-routing-reco-02 Pages        : 4 Date
>> : 2014-09-24
>>
>> http://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02
>>
>>
>>
The call ends on October 10th, 2014.
>>
>> Regards,
>>
>> Bob Hinden & Ole TrÃ¸an
>>
>>
>> --------------------------------------------------------------------
>>
>>
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
> --------------------------------------------------------------------
>



From nobody Mon Oct 13 08:17:41 2014
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20EE51A036E for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 08:17:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.583
X-Spam-Level: 
X-Spam-Status: No, score=-3.583 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 WRNBrvFARLeA for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 08:17:28 -0700 (PDT)
Received: from oxalide-out.extra.cea.fr (oxalide-out.extra.cea.fr [132.168.224.8]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0C421A01C6 for <ipv6@ietf.org>; Mon, 13 Oct 2014 08:17:27 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by oxalide.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s9DFHP8I008702 for <ipv6@ietf.org>; Mon, 13 Oct 2014 17:17:25 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 158F020C2CD for <ipv6@ietf.org>; Mon, 13 Oct 2014 17:18:38 +0200 (CEST)
Received: from muguet1.intra.cea.fr (muguet1.intra.cea.fr [132.166.192.6]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 0CFDF203D76 for <ipv6@ietf.org>; Mon, 13 Oct 2014 17:18:38 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet1.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s9DFHGch016746 for <ipv6@ietf.org>; Mon, 13 Oct 2014 17:17:25 +0200
Message-ID: <543BECFC.2000400@gmail.com>
Date: Mon, 13 Oct 2014 17:17:16 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: more reasons for 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch>
In-Reply-To: <542E8110.5050906@massar.ch>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/jPous_cFqbhkdN3JPrDFCte7iF8
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 15:17:37 -0000

Hello,

This is an end user experience, at the edge of the network.

The reasons I invoke at our local site to migrate to native IPv6 from 
currently 6to4 are the following:

- we currently depend on the well functioning of a publicly available 
6to4 Relay.  This Relay has no commitment of service whatsoever, it can 
turn down anytime.

- all our  IPv6 traffic is subject to scrutiny at these Relays.

- we depend extensively on DNSv6 of google, being incapable of creating 
our own full DNSv6, because impossible to offer reverse resolution.

- we may risk being considered as spammers as some email spam filters on 
some servers try reverse resolution before accepting emails (IIRC).

- the IP paths IPv6 packets take outwards our setting differ 
systematically from the in-bounds. (triangular routing is not an 
exception but the norm).  This has negative impact on some applications.

- strong security risks have been identified with a particular 6to4 
implementation in a particular brand.  It led to false positives on 
sensitive traffic identification.

Alex

Le 03/10/2014 12:57, Jeroen Massar a écrit :
> As some .gov agency is reminding us[1], it might be time to finally lay
> 6to4 to rest by making it historic.
>
> Can we revive:
>   http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>
> and finally make it into a BCP, marking 6to4 historic.
>
> That way, we can also get operators to wind down on 2002::/16 relays and
> give a clear signal that folks really should have native in 2014.
>
> Greets,
>   Jeroen
>
> [1] www.azdes.gov = 2002::cf6c:8846
>
> -------- Forwarded Message --------
> Subject: Re: 6to4 in Internet aaaa records
> Date: Fri, 03 Oct 2014 17:06:27 +1300
> From: Brian E Carpenter <brian.e.carpenter@gmail.com>
> CC: Jeroen Massar <jeroen@massar.ch>, IPv6 operators forum
> <ipv6-ops@lists.cluenet.de>
>
> [..]
>>> and of course also:
>>>   http://tools.ietf.org/html/draft-ietf-v6ops-6to4-to-historic-05
>>>   (though that technically expired).
>
> 3 years ago that seemed premature. With recent progress in real IPv6,
> I'm wondering whether it isn't time to revive it. If so it should be
> changed to be a BCP that says "Don't do this" and also makes
> the proposed standard drafts Historic.
>
> But we do hear persistently that there are happy hobbyist and peer to peer
> users of 6to4. Using it offer web service for the Arizona Department of
> Economic Security is so wrong, though.
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>
>



From nobody Mon Oct 13 11:49:41 2014
Return-Path: <jinmei.tatuya@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 70D191A88C9 for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 11:49:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.978
X-Spam-Level: 
X-Spam-Status: No, score=-0.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001] autolearn=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 6EEw-FrLtFmU for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 11:49:38 -0700 (PDT)
Received: from mail-wg0-x234.google.com (mail-wg0-x234.google.com [IPv6:2a00:1450:400c:c00::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C0F251A88C4 for <ipv6@ietf.org>; Mon, 13 Oct 2014 11:49:37 -0700 (PDT)
Received: by mail-wg0-f52.google.com with SMTP id a1so9241827wgh.23 for <ipv6@ietf.org>; Mon, 13 Oct 2014 11:49:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=EluebaybyUjycxGw+cGZNOiW9En8BXHr2zWuo4d14L8=; b=HuOHO+SFj6GGVtclOdYzY9/d1eLrkrKrPYNKGWDPicPVDFOYUJT5x0y38OEI9zYs7p /y1ZywGABUlS4x6Hl2JZ8y76skGFQrajutAXaDrFKQ40mkIxvj535h6XwhHooHIQSOHm uRSeDulKaF7BLpB1nhLVfod47BlCrZcLoNhf5Br+8h65zXxMJZiD3IXwuml/mN+bVvZ/ 1Bjw1adhR5+mi7OdlouSrm466GMBBrz/vMVEq2wtLWA4lecZ59qToHC2GupEFPwG+gPy n78OM/XeWpMI2xw5JxJ91FzOoN/cwD20FnOYAf+B8ktOmj3V4mdfbTROzSwP0WfOCSmG Y10Q==
MIME-Version: 1.0
X-Received: by 10.180.149.130 with SMTP id ua2mr798315wib.31.1413226176391; Mon, 13 Oct 2014 11:49:36 -0700 (PDT)
Sender: jinmei.tatuya@gmail.com
Received: by 10.195.13.83 with HTTP; Mon, 13 Oct 2014 11:49:36 -0700 (PDT)
In-Reply-To: <543BE567.50509@gmail.com>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com>
Date: Mon, 13 Oct 2014 11:49:36 -0700
X-Google-Sender-Auth: PVwaSOdJn_doiNK2Q_QpFLidCHA
Message-ID: <CAJE_bqd+BnnFf9X42fGHRAyPtDSrfjLyDTrQB76Bq425uOX-RA@mail.gmail.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
From: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/ZFNq75BZ5KRI6h4PERVJUtTMSe8
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 18:49:39 -0000

At Mon, 13 Oct 2014 16:44:55 +0200,
Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:

> I am surprised there is no support in favor of
> draft-boucadair-6man-prefix-routing-reco?
>
> https://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02
>
> Its main recommendation is:
> >    Forwarding decision-making processes MUST NOT restrict by design the
> >    length of IPv6 prefixes.  In particular, forwarding processes MUST be
> >    designed to process prefixes of any length up to /128, by increments
> >    of 1.
>
> What do you think?

I've been busier for the last couple of weeks and couldn't respond to
the adoption call before the deadline, but I agree this topic is worth
discussing.  I don't have a strong opinion on whether this should
belong to 6man or v6ops (or somewhere else), although v6ops seems to
be slightly better than 6man.

--
JINMEI, Tatuya


From nobody Mon Oct 13 12:27:38 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C3031A8BC0 for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 12:27:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 7g-mbTqzOY_i for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 12:27:32 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B35BF1A8BC5 for <ipv6@ietf.org>; Mon, 13 Oct 2014 12:27:23 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id bj1so6383520pad.15 for <ipv6@ietf.org>; Mon, 13 Oct 2014 12:27:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=bMykmTzts1J/VEh8MTpI+uW2w1iVRHgFRBWnhZK9jmo=; b=ZQBNFel/hBjyakh/Ds4bIVxaCXkG6d1rbUtvwRvw5rT/+3gWxdDQcef+Lu7hfncttY xjwRWBzenUXYQHfGWH8UTv1YE1cuL4tj04q9U0HA6Rs0whfPg4GJWsqrluor5mvMmg70 LY8f2s4RpN8lSctgEepV6rcxlEjmfQxchtlB++aIHXypWryzyacIUoR1TEYRWz/q2KJ5 FxPP+VqfV05YPk9JfJX2BvGyOqjkQt5hH7XanyTDG8C0NHzdgedMm7Q6BMKsJz3BPVYH uJ6qxkE3SxqavxCZfyhbx2soKX5aPAgTrOu2R0j4/ZBkC4py/ppdou3yHrO5sr64g0G+ B3Aw==
X-Received: by 10.70.96.4 with SMTP id do4mr203389pdb.133.1413228443473; Mon, 13 Oct 2014 12:27:23 -0700 (PDT)
Received: from [192.168.178.23] (75.196.69.111.dynamic.snap.net.nz. [111.69.196.75]) by mx.google.com with ESMTPSA id oh5sm7645900pbc.76.2014.10.13.12.27.19 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 Oct 2014 12:27:22 -0700 (PDT)
Message-ID: <543C2797.8030607@gmail.com>
Date: Tue, 14 Oct 2014 08:27:19 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Mikael Abrahamsson <swmike@swm.pp.se>
Subject: Re: Adoption call of draft-gont-6man-deprecate-atomfrag-generation for 6MAN
References: <2742D96E-1538-4ECF-BB3A-6A194D9DBB96@employees.org> <alpine.DEB.2.02.1410130914060.14735@uplift.swm.pp.se>
In-Reply-To: <alpine.DEB.2.02.1410130914060.14735@uplift.swm.pp.se>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/cuMuRMQahZv2X4KW-8BNGNwLs5g
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 19:27:35 -0000

On 13/10/2014 20:15, Mikael Abrahamsson wrote:
> On Mon, 13 Oct 2014, Ole Troan wrote:
> 
>> All,
>>
>> The authors have requested an adoption call for this document as a
>> standards track document.
>>
>> Please provide a view with reasons as to whether the WG should adopt
>> this or not.
> 
> I support that we're taking a good look at this problem.

Yes. This is (another) case where our standards allow bad things
to happen, so we should try to fix it, and I think this draft
heads in the direction of a fix.

   Brian


From nobody Mon Oct 13 12:50:41 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 745241A86DE for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 12:50:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 b3eO76QLHa2G for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 12:50:37 -0700 (PDT)
Received: from mail-pa0-x232.google.com (mail-pa0-x232.google.com [IPv6:2607:f8b0:400e:c03::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB5201A7D80 for <ipv6@ietf.org>; Mon, 13 Oct 2014 12:50:37 -0700 (PDT)
Received: by mail-pa0-f50.google.com with SMTP id kx10so6269259pab.23 for <ipv6@ietf.org>; Mon, 13 Oct 2014 12:50:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=OBkgkprf1+7z96xdw9ZeXyhFDfwIm1yh/feuAEQWeMA=; b=MifHjuYKiqaQL0dEckabgYrzUCiWCdyXSa0r8YChadYQejg3JtrRoDMQwccH9G9lUU manmgsi9J1KxmNDKw3IbdnBuoglT/D6qM/s+q9z3YTUzTfFBOy0zjrUubEH3LtHWslaM Gn9rct3xfDMvu8kVTKMV5rxszUg17K1gwiYyTj8YcAPHh0RbfDQH90C39puRS9mcQhGf cAw8IXV3u6viRmY0QtNPTZW2tgE7bn2P9EHjcI6xv8qNail8tUKhliq9qm/eRPYvXRV5 mbudKmM0KB2wfDgEYMJwAC04OnMRMK9gJEAhnFCc7bPpXq1mCzYTgIuaWCmCHt3BrTEe a7Pw==
X-Received: by 10.68.87.227 with SMTP id bb3mr616465pbb.118.1413229837493; Mon, 13 Oct 2014 12:50:37 -0700 (PDT)
Received: from [192.168.178.23] (75.196.69.111.dynamic.snap.net.nz. [111.69.196.75]) by mx.google.com with ESMTPSA id w4sm11964613pdr.72.2014.10.13.12.50.32 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 13 Oct 2014 12:50:36 -0700 (PDT)
Message-ID: <543C2D08.5080204@gmail.com>
Date: Tue, 14 Oct 2014 08:50:32 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com>
In-Reply-To: <543BE567.50509@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/zmTPZwFBovEuOLVbc-hD1CMocRo
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 19:50:40 -0000

On 14/10/2014 03:44, Alexandru Petrescu wrote:
> Hello,
>=20
> I am surprised there is no support in favor of
> draft-boucadair-6man-prefix-routing-reco?
>=20
> https://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02=

>=20
> Its main recommendation is:
>>    Forwarding decision-making processes MUST NOT restrict by design th=
e
>>    length of IPv6 prefixes.  In particular, forwarding processes MUST =
be
>>    designed to process prefixes of any length up to /128, by increment=
s
>>    of 1.
>=20
> What do you think?

My view is that this draft is totally correct but that it states the
obvious. (BTW, it's taken for granted in draft-ietf-6man-why64.)

It is pretty clear in the IPv6 addressing architecture (RFC 4291):

"IPv6 unicast addresses are aggregatable with prefixes of arbitrary
 bit-length, similar to IPv4 addresses under Classless Inter-Domain
 Routing."

I suspect the reason for the lack of replies is that people
don't think it's necessary to publish a new standards track RFC
for this.

   Brian

>=20
> Alex
>=20
> Le 13/10/2014 08:28, Ole Troan a =C3=A9crit :
>> All,
>>
>> The adoption call for draft-boucadair-6man-prefix-routing-reco for
>> ended October 10th. With only two replies, none of them in support, I
>> can only conclude that there is no support to adopt this document in
>> 6MAN.
>>
>> Best regards, Ole
>>
>>
>>> On 03 Oct 2014, at 9:28 , Ole Troan <otroan@employees.org> wrote:
>>>
>>> All,
>>>
>>> The authors have requested an adoption call for this document as a
>>> standards track document.
>>>
>>> Please provide a view with reasons as to whether the WG should
>>> adopt this or not.
>>>
>>> This message starts a one week 6MAN Working Group call on
>>> adopting:
>>>
>>> Title           : IPv6 Prefix Length Recommendation for Forwarding
>>> Author(s)    : M. Boucadair, A. Petrescu Filename    :
>>> draft-boucadair-6man-prefix-routing-reco-02 Pages        : 4 Date
>>> : 2014-09-24
>>>
>>> http://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-0=
2
>>>
>>>
>>>
> The call ends on October 10th, 2014.
>>>
>>> Regards,
>>>
>>> Bob Hinden & Ole Tr=C3=B8an



From nobody Mon Oct 13 13:13:10 2014
Return-Path: <albert.e.manfredi@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 37D341A0037 for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 13:13:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.987
X-Spam-Level: 
X-Spam-Status: No, score=-4.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 jdY-OONKNppS for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 13:13:07 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (slb-mbsout-02.boeing.com [130.76.64.129]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4DE31A000E for <ipv6@ietf.org>; Mon, 13 Oct 2014 13:13:07 -0700 (PDT)
Received: from slb-mbsout-02.boeing.com (localhost [127.0.0.1]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with ESMTP id s9DKD6uD004456 for <ipv6@ietf.org>; Mon, 13 Oct 2014 13:13:07 -0700
Received: from XCH-PHX-305.sw.nos.boeing.com (xch-phx-305.sw.nos.boeing.com [137.136.239.28]) by slb-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id s9DKD6xm004445 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 13 Oct 2014 13:13:06 -0700
Received: from XCH-PHX-503.sw.nos.boeing.com ([169.254.6.97]) by XCH-PHX-305.sw.nos.boeing.com ([169.254.5.126]) with mapi id 14.03.0181.006; Mon, 13 Oct 2014 13:13:05 -0700
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
Subject: RE: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
Thread-Topic: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
Thread-Index: AQHP5q7gf1QAPFbK8kWC7Y9n3ObMbpwukHyA///ltjA=
Date: Mon, 13 Oct 2014 20:13:04 +0000
Message-ID: <021E64FECA7E5A4699562F4E6671648133A66034@XCH-PHX-503.sw.nos.boeing.com>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com>
In-Reply-To: <543BE567.50509@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [137.136.248.6]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/t5NziylXQ5E3Iny-UsfLv4_EN1A
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 20:13:09 -0000

PiAtLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPiBGcm9tOiBpcHY2IFttYWlsdG86aXB2Ni1i
b3VuY2VzQGlldGYub3JnXSBPbiBCZWhhbGYgT2YgQWxleGFuZHJ1IFBldHJlc2N1DQo+IA0KPiBI
ZWxsbywNCj4gDQo+IEkgYW0gc3VycHJpc2VkIHRoZXJlIGlzIG5vIHN1cHBvcnQgaW4gZmF2b3Ig
b2YNCj4gZHJhZnQtYm91Y2FkYWlyLTZtYW4tcHJlZml4LXJvdXRpbmctcmVjbz8NCj4gDQo+IGh0
dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1ib3VjYWRhaXItNm1hbi1wcmVmaXgtcm91
dGluZy1yZWNvLTAyDQo+IA0KPiBJdHMgbWFpbiByZWNvbW1lbmRhdGlvbiBpczoNCj4gPiAgICBG
b3J3YXJkaW5nIGRlY2lzaW9uLW1ha2luZyBwcm9jZXNzZXMgTVVTVCBOT1QgcmVzdHJpY3QgYnkg
ZGVzaWduIHRoZQ0KPiA+ICAgIGxlbmd0aCBvZiBJUHY2IHByZWZpeGVzLiAgSW4gcGFydGljdWxh
ciwgZm9yd2FyZGluZyBwcm9jZXNzZXMgTVVTVCBiZQ0KPiA+ICAgIGRlc2lnbmVkIHRvIHByb2Nl
c3MgcHJlZml4ZXMgb2YgYW55IGxlbmd0aCB1cCB0byAvMTI4LCBieSBpbmNyZW1lbnRzDQo+ID4g
ICAgb2YgMS4NCj4gDQo+IFdoYXQgZG8geW91IHRoaW5rPw0KDQpJIGFncmVlIGZ1bGx5IHdpdGgg
dGhlIHJlY29tbWVuZGF0aW9uIG9mIHRoaXMgZHJhZnQsIGJ1dCBJJ20gbm90IHN1cmUgd2hhdCBp
dCBpcyBjb250cmFkaWN0aW5nLCBpZiBhbnl0aGluZy4gT3IgaXMgaXQgbWVhbnQganVzdCBmb3Ig
ZW1waGFzaXM/DQoNCkJlcnQNCg0K


From nobody Mon Oct 13 14:40:48 2014
Return-Path: <dale.carder@wisc.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A86421A016F for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 14:40:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.987
X-Spam-Level: 
X-Spam-Status: No, score=-4.987 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 wyRbvP0PCZts for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 14:40:45 -0700 (PDT)
Received: from smtpauth2.wiscmail.wisc.edu (wmauth2.doit.wisc.edu [144.92.197.222]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A0581A017C for <ipv6@ietf.org>; Mon, 13 Oct 2014 14:40:44 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-disposition: inline
Content-type: text/plain; CHARSET=US-ASCII
Received: from avs-daemon.smtpauth2.wiscmail.wisc.edu by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) id <0NDE00600JYZFU00@smtpauth2.wiscmail.wisc.edu> for ipv6@ietf.org; Mon, 13 Oct 2014 16:40:44 -0500 (CDT)
X-Spam-PmxInfo: Server=avs-2, Version=6.1.1.2430161, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2014.10.13.213320, SenderIP=0.0.0.0
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2lp0207.outbound.protection.outlook.com [207.46.163.207]) by smtpauth2.wiscmail.wisc.edu (Oracle Communications Messaging Server 7.0.5.33.0 64bit (built Aug 27 2014)) with ESMTPS id <0NDE00555K7VGS00@smtpauth2.wiscmail.wisc.edu>; Mon, 13 Oct 2014 16:40:44 -0500 (CDT)
Received: from ricotta.doit.wisc.edu (2607:f388:e:100:217:f2ff:fe0a:bdf6) by CO2PR06MB684.namprd06.prod.outlook.com (10.141.226.149) with Microsoft SMTP Server (TLS) id 15.0.1049.19; Mon, 13 Oct 2014 21:40:41 +0000
Date: Mon, 13 Oct 2014 16:40:34 -0500
From: "Dale W. Carder" <dwcarder@wisc.edu>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
Message-id: <20141013214034.GB87778@ricotta.doit.wisc.edu>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <20141011065407.GA14879@havarti.local> <54398420.3030608@gmail.com>
In-reply-to: <54398420.3030608@gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Originating-IP: [2607:f388:e:100:217:f2ff:fe0a:bdf6]
X-ClientProxiedBy: CY1PR12CA0036.namprd12.prod.outlook.com (25.160.137.46) To CO2PR06MB684.namprd06.prod.outlook.com (10.141.226.149)
X-Microsoft-Antispam: UriScan:;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:CO2PR06MB684;
X-Exchange-Antispam-Report-Test: UriScan:;
X-Forefront-PRVS: 03630A6A4A
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6009001)(189002)(199003)(76482002)(93886004)(54356999)(85306004)(76176999)(50986999)(31966008)(85852003)(120916001)(83506001)(46406003)(92566001)(46102003)(4396001)(92726001)(87976001)(75432002)(19580395003)(97736003)(19580405001)(50466002)(89122001)(21056001)(64706001)(90282001)(95666004)(40100003)(23726002)(20776003)(47776003)(106356001)(105586002)(33656002)(122386002)(77096002)(101416001)(88552001)(80022003)(110136001)(102836001)(42186005)(97756001)(107046002); DIR:OUT; SFP:1101; SCL:1; SRVR:CO2PR06MB684; H:ricotta.doit.wisc.edu; FPR:; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
X-OriginatorOrg: wisc.edu
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/dOfOaM40GgR944frvI4bIFvoTcU
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Tore Anderson <tore@fud.no>, ipv6@ietf.org, Mark Andrews <marka@isc.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 21:40:46 -0000

Thus spake Brian E Carpenter (brian.e.carpenter@gmail.com) on Sun, Oct 12, 2014 at 08:25:20AM +1300:
> Yes, but there are still certainly millions of people running XP and the
> like with old browsers

XP has ipv6 off by default, no?  I think the only users who would be
materially affected might be apple <= 10.6 who only use safari as their
browser and have a home router that will send 6to4 RA's, but can't/won't 
do 6rd when available.  So, maybe my mom ;-)

> and we simply don't know how many of them are
> still suffering as a result (especially if they have to go via Australia
> to discover black holes). So I don't think we can assert that nobody cares.

To be clear, my "nobody cares" was in reference to my ~1M end-users, with
zero trouble tickets that resulted from disabling our local relays and bgp 
choosing the one 209ms away (looks like anyone who localpref's prefixes 
from as11537 might also choose this particular relay).

My guess without even looking at the data is that the remaining 6to4 
traffic that one would see at an IX would be bittorrent.  If possible it
may be better to get clarification from google et. al as to what browser
strings they are seeing?

Dale


From nobody Mon Oct 13 16:07:13 2014
Return-Path: <marka@isc.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E2691A1A42 for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 16:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.687
X-Spam-Level: 
X-Spam-Status: No, score=-7.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001] autolearn=ham
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 HJV8zxVx-0a0 for <ipv6@ietfa.amsl.com>; Mon, 13 Oct 2014 16:06:58 -0700 (PDT)
Received: from mx.ams1.isc.org (mx.ams1.isc.org [199.6.1.65]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A158A1A1A3A for <ipv6@ietf.org>; Mon, 13 Oct 2014 16:06:58 -0700 (PDT)
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id C37C61FCB2D; Mon, 13 Oct 2014 23:06:55 +0000 (UTC)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id A6038160052; Mon, 13 Oct 2014 23:09:58 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 746F9160032; Mon, 13 Oct 2014 23:09:58 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id D0EC1215E816; Tue, 14 Oct 2014 10:06:52 +1100 (EST)
To: "Dale W. Carder" <dwcarder@wisc.edu>
From: Mark Andrews <marka@isc.org>
References: <542E20C3.1060404@gmail.com> <542E8110.5050906@massar.ch> <542EA35C.2080606@gmail.com> <20141003140519.8661420BC158@rock.dv.isc.org> <4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <EMEW3|ad61ef9f476228514903edf9e53a0c7dq92FMQ03tjc|ecs.soton.ac.uk|4A56907F-C226-4879-9033-61B65DF35CF6@ecs.soton.ac.uk> <542FB7A2.6060208@fud.no> <20141011065407.GA14879@havarti.local> <54398420.3030608@gmail.com> <20141013214034.GB87778@ricotta.doit.wisc.edu>
Subject: Re: 6to4 to Historic (ipv6-ops@cluenet Re: 6to4 in Internet aaaa records)
In-reply-to: Your message of "Mon, 13 Oct 2014 16:40:34 -0500." <20141013214034.GB87778@ricotta.doit.wisc.edu>
Date: Tue, 14 Oct 2014 10:06:52 +1100
Message-Id: <20141013230652.D0EC1215E816@rock.dv.isc.org>
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/slqzTPlzyvfeV8HbOYmMPUGz0ms
Cc: Tim Chown <tjc@ecs.soton.ac.uk>, Tore Anderson <tore@fud.no>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 13 Oct 2014 23:07:02 -0000

In message <20141013214034.GB87778@ricotta.doit.wisc.edu>, "Dale W. Carder" writes:
> Thus spake Brian E Carpenter (brian.e.carpenter@gmail.com) on Sun, Oct 12, 2014 at 08:25:20AM +1300:
> > Yes, but there are still certainly millions of people running XP and the
> > like with old browsers
> 
> XP has ipv6 off by default, no?  I think the only users who would be
> materially affected might be apple <= 10.6 who only use safari as their
> browser and have a home router that will send 6to4 RA's, but can't/won't 
> do 6rd when available.  So, maybe my mom ;-)
> 
> > and we simply don't know how many of them are
> > still suffering as a result (especially if they have to go via Australia
> > to discover black holes). So I don't think we can assert that nobody cares.
> 
> To be clear, my "nobody cares" was in reference to my ~1M end-users, with
> zero trouble tickets that resulted from disabling our local relays and bgp 
> choosing the one 209ms away (looks like anyone who localpref's prefixes 
> from as11537 might also choose this particular relay).
> 
> My guess without even looking at the data is that the remaining 6to4 
> traffic that one would see at an IX would be bittorrent.  If possible it
> may be better to get clarification from google et. al as to what browser
> strings they are seeing?
> 
> Dale

Also while gatewaying packets on the other side of the world is not
optimal, it does work.  Most things don't care about a extra 200 odd
ms.

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org


From nobody Tue Oct 14 02:27:26 2014
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CBE51A7007 for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 02:27:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 9ALwsy3nbOSM for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 02:27:10 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD99C1A6FEC for <ipv6@ietf.org>; Tue, 14 Oct 2014 02:27:09 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s9E9R5pj030719; Tue, 14 Oct 2014 11:27:05 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 9B503204D38; Tue, 14 Oct 2014 11:28:18 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 8B1AE204C91; Tue, 14 Oct 2014 11:28:18 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s9E9QwUw019887; Tue, 14 Oct 2014 11:27:04 +0200
Message-ID: <543CEC62.3080005@gmail.com>
Date: Tue, 14 Oct 2014 11:26:58 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com> <543C2D08.5080204@gmail.com>
In-Reply-To: <543C2D08.5080204@gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/uj0VYd9_MBLpWETMe1W0i1FDLnw
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 14 Oct 2014 09:27:12 -0000

Le 13/10/2014 21:50, Brian E Carpenter a Ã©crit :
> On 14/10/2014 03:44, Alexandru Petrescu wrote:
>> Hello,
>>
>> I am surprised there is no support in favor of
>> draft-boucadair-6man-prefix-routing-reco?
>>
>> https://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02
>>
>> Its main recommendation is:
>>>     Forwarding decision-making processes MUST NOT restrict by design the
>>>     length of IPv6 prefixes.  In particular, forwarding processes MUST be
>>>     designed to process prefixes of any length up to /128, by increments
>>>     of 1.
>>
>> What do you think?
>
> My view is that this draft is totally correct but that it states the
> obvious.

Yes, it states the obvious.  What easier to get through than the obvious.

It sticks to this obvious even in corner cases such as when longer than 
64 prefixes may induce performance hits.

> (BTW, it's taken for granted in draft-ietf-6man-why64.)

Contrary to the why64 draft where we abstained from making any 
recommendations, this draft does.

> It is pretty clear in the IPv6 addressing architecture (RFC 4291):
>
> "IPv6 unicast addresses are aggregatable with prefixes of arbitrary
>   bit-length, similar to IPv4 addresses under Classless Inter-Domain
>   Routing."

I could guess the intention of this paragraph; but because it uses that 
'aggregatable' word I think it may loose substance - it may lead to 
interpretations which dont disallow the 64bit limits.

Besides, the paragraph is about how addresses are aggregated with 
prefixes, whereas the reco draft is about the forwarding. (aggregation 
is opaque to forwarding mechanisms).

> I suspect the reason for the lack of replies is that people
> don't think it's necessary to publish a new standards track RFC
> for this.

Noted.

Alex

>
>     Brian
>
>>
>> Alex
>>
>> Le 13/10/2014 08:28, Ole Troan a Ã©crit :
>>> All,
>>>
>>> The adoption call for draft-boucadair-6man-prefix-routing-reco for
>>> ended October 10th. With only two replies, none of them in support, I
>>> can only conclude that there is no support to adopt this document in
>>> 6MAN.
>>>
>>> Best regards, Ole
>>>
>>>
>>>> On 03 Oct 2014, at 9:28 , Ole Troan <otroan@employees.org> wrote:
>>>>
>>>> All,
>>>>
>>>> The authors have requested an adoption call for this document as a
>>>> standards track document.
>>>>
>>>> Please provide a view with reasons as to whether the WG should
>>>> adopt this or not.
>>>>
>>>> This message starts a one week 6MAN Working Group call on
>>>> adopting:
>>>>
>>>> Title           : IPv6 Prefix Length Recommendation for Forwarding
>>>> Author(s)    : M. Boucadair, A. Petrescu Filename    :
>>>> draft-boucadair-6man-prefix-routing-reco-02 Pages        : 4 Date
>>>> : 2014-09-24
>>>>
>>>> http://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02
>>>>
>>>>
>>>>
>> The call ends on October 10th, 2014.
>>>>
>>>> Regards,
>>>>
>>>> Bob Hinden & Ole TrÃ¸an
>
>
>
>



From nobody Tue Oct 14 02:29:26 2014
Return-Path: <alexandru.petrescu@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5932E1A6FFD for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 02:29:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.983
X-Spam-Level: 
X-Spam-Status: No, score=-4.983 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, HELO_EQ_FR=0.35, NML_ADSP_CUSTOM_MED=0.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 9albuQFrusPI for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 02:29:23 -0700 (PDT)
Received: from cirse-out.extra.cea.fr (cirse-out.extra.cea.fr [132.167.192.142]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5DC21A6FEC for <ipv6@ietf.org>; Tue, 14 Oct 2014 02:29:22 -0700 (PDT)
Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse.extra.cea.fr (8.14.2/8.14.2/CEAnet-Internet-out-2.3) with ESMTP id s9E9TIVq031847; Tue, 14 Oct 2014 11:29:18 +0200
Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id ADBCF204C7A; Tue, 14 Oct 2014 11:30:31 +0200 (CEST)
Received: from muguet2.intra.cea.fr (muguet2.intra.cea.fr [132.166.192.7]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 9605A204C48; Tue, 14 Oct 2014 11:30:31 +0200 (CEST)
Received: from [127.0.0.1] (is010446-4.intra.cea.fr [10.8.33.116]) by muguet2.intra.cea.fr (8.13.8/8.13.8/CEAnet-Intranet-out-1.2) with ESMTP id s9E9THr4021884; Tue, 14 Oct 2014 11:29:17 +0200
Message-ID: <543CECED.5010806@gmail.com>
Date: Tue, 14 Oct 2014 11:29:17 +0200
From: Alexandru Petrescu <alexandru.petrescu@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>, 6man WG <ipv6@ietf.org>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com> <021E64FECA7E5A4699562F4E6671648133A66034@XCH-PHX-503.sw.nos.boeing.com>
In-Reply-To: <021E64FECA7E5A4699562F4E6671648133A66034@XCH-PHX-503.sw.nos.boeing.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/u1jRAtEWV7ChvYDJ4wKml1KE0o4
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 14 Oct 2014 09:29:25 -0000

Le 13/10/2014 22:13, Manfredi, Albert E a Ã©crit :
>> -----Original Message----- From: ipv6
>> [mailto:ipv6-bounces@ietf.org] On Behalf Of Alexandru Petrescu
>>
>> Hello,
>>
>> I am surprised there is no support in favor of
>> draft-boucadair-6man-prefix-routing-reco?
>>
>> https://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02
>>
>>
>>
Its main recommendation is:
>>> Forwarding decision-making processes MUST NOT restrict by design
>>> the length of IPv6 prefixes.  In particular, forwarding processes
>>> MUST be designed to process prefixes of any length up to /128, by
>>> increments of 1.
>>
>> What do you think?
>
> I agree fully with the recommendation of this draft, but I'm not sure
> what it is contradicting, if anything. Or is it meant just for
> emphasis?

Yes, it is meant for emphasis.

Alex

>
> Bert
>



From nobody Tue Oct 14 02:39:47 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68D471A7006 for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 02:39:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 St5pKKrj8VmE for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 02:39:43 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6081B1A7000 for <ipv6@ietf.org>; Tue, 14 Oct 2014 02:39:43 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqIEANruPFStJssW/2dsb2JhbABbg2HNBYdNAoErAX2EAwEBAwE6PxALEjRJDgYniCIIDcV0AQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSQEjMHgy2BHgEEljudIYN5O4J5AQEB
X-IronPort-AV: E=Sophos;i="5.04,716,1406592000"; d="scan'208";a="206096994"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP; 14 Oct 2014 09:39:41 +0000
Received: from dhcp-10-61-105-175.cisco.com (dhcp-10-61-105-175.cisco.com [10.61.105.175]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id s9E9ddq4010989 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 14 Oct 2014 09:39:40 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
From: Ole Troan <otroan@employees.org>
In-Reply-To: <543CEC62.3080005@gmail.com>
Date: Tue, 14 Oct 2014 11:39:38 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8FDF830-E404-4604-A2A3-D8A06BE9098E@employees.org>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com> <543C2D08.5080204@gmail.com> <543CEC62.3080005@gmail.com>
To: Alexandru Petrescu <alexandru.petrescu@gmail.com>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/MkbyAj2fAmzDredWTfTSB6ftvFY
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 14 Oct 2014 09:39:45 -0000

Alex,

>>> Hello,
>>>=20
>>> I am surprised there is no support in favor of
>>> draft-boucadair-6man-prefix-routing-reco?
>>>=20
>>> =
https://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02
>>>=20
>>> Its main recommendation is:
>>>>    Forwarding decision-making processes MUST NOT restrict by design =
the
>>>>    length of IPv6 prefixes.  In particular, forwarding processes =
MUST be
>>>>    designed to process prefixes of any length up to /128, by =
increments
>>>>    of 1.
>>>=20
>>> What do you think?
>>=20
>> My view is that this draft is totally correct but that it states the
>> obvious.
>=20
> Yes, it states the obvious.  What easier to get through than the =
obvious.
>=20
> It sticks to this obvious even in corner cases such as when longer =
than 64 prefixes may induce performance hits.
>=20
>> (BTW, it's taken for granted in draft-ietf-6man-why64.)
>=20
> Contrary to the why64 draft where we abstained from making any =
recommendations, this draft does.
>=20
>> It is pretty clear in the IPv6 addressing architecture (RFC 4291):
>>=20
>> "IPv6 unicast addresses are aggregatable with prefixes of arbitrary
>>  bit-length, similar to IPv4 addresses under Classless Inter-Domain
>>  Routing."
>=20
> I could guess the intention of this paragraph; but because it uses =
that 'aggregatable' word I think it may loose substance - it may lead to =
interpretations which dont disallow the 64bit limits.
>=20
> Besides, the paragraph is about how addresses are aggregated with =
prefixes, whereas the reco draft is about the forwarding. (aggregation =
is opaque to forwarding mechanisms).

I've trawled through the IPv6 RFCs, and I can't find anything that =
directly specifies how forwarding is done, apart from the reference to =
CIDR. RFC1812 is more specific on this for IPv4.

that said, it hasn't been a problem. all the routing protocols handle =
arbitrary prefix lengths, and as far as I know all the forwarding =
engines do too.

>> I suspect the reason for the lack of replies is that people
>> don't think it's necessary to publish a new standards track RFC
>> for this.
>=20
> Noted.

taking a document through to RFC publication has a cost. given that =
there hasn't so far been any problems from not having this document, is =
probably good enough reason to not publish it.
even though I'm pretty sure this document reflects the consensus of the =
community. ;-)

cheers,
Ole=


From nobody Tue Oct 14 06:39:01 2014
Return-Path: <farmer@umn.edu>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 50FEC1A886F for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 06:38:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.786
X-Spam-Level: 
X-Spam-Status: No, score=-4.786 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.786] autolearn=ham
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 SitSykfjoEqQ for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 06:38:46 -0700 (PDT)
Received: from vs-w.tc.umn.edu (vs-w.tc.umn.edu [134.84.135.88]) by ietfa.amsl.com (Postfix) with ESMTP id 1DA731A8865 for <ipv6@ietf.org>; Tue, 14 Oct 2014 06:38:44 -0700 (PDT)
Received: from mail-ig0-f178.google.com (mail-ig0-f178.google.com [209.85.213.178]) by vs-w.tc.umn.edu (UMN smtpd) with ESMTP for <ipv6@ietf.org>; Tue, 14 Oct 2014 08:38:42 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ig0-f178.google.com [209.85.213.178] #+LO+TS+TR
X-Umn-Classification: local
Received: by mail-ig0-f178.google.com with SMTP id h3so14597670igd.11 for <ipv6@ietf.org>; Tue, 14 Oct 2014 06:38:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=message-id:date:from:reply-to:organization:user-agent:mime-version :to:cc:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=8loU7jQwg6kwoonal4KoPHgVsGRSIN4akT+zwyyYMrA=; b=JFx7Ec2I0eikaSnBbahhZre7BOYFCgBCJj7bzfGjgz94Bz6wpIzyhYq0ku2QH5d33X +I7ev0Oe0Lcb03b2jaDnnNbc6BNvmVVwbRtMTxB6s97jc1ruCbm6e/NecGEC1ga+5ffe sqclNuCQwysOPj7N/g/16mBIAZvDORRJ7uN1U=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:reply-to:organization :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=8loU7jQwg6kwoonal4KoPHgVsGRSIN4akT+zwyyYMrA=; b=dMfrErvoGlij113tXEljhPNZuqMpHT4e40xFzC+vwuLfnruEpl1Wx9xjiVJP6cGvKB Vn1INg3oXkMOMKy4sBXZmGJz6F/Pv/4F6cf00AfeI01F8G763yJgVU7KsTZ0ZgRoWTfW hCVIyzayObmaucAKgaj2o+l/aeViOPQnmd2iqKDB9K4ya98cjkJt+FLACgTG6B0b9g1o odd6AlQaDNTvaY+ZsK/CKfT9pPUqCaJmY7XEOckGjqnP3dA5KEseF4D7urW7Ja+i9emB KX2lUq57Pl1KN7eWEutET1yGccx/tJhjKW0a9FW0f/GMZFTMO7qbkmaqm0QoyUcmETpZ ak3w==
X-Received: by 10.50.6.100 with SMTP id z4mr6740617igz.37.1413293922083; Tue, 14 Oct 2014 06:38:42 -0700 (PDT)
X-Gm-Message-State: ALoCoQkMN3f+NMa1Ufn7OqJ5dtqIdNpF7mxARjKtTQqHsCsleeVKqa6hJWNNCuHfv22ICTerrxvMulX1cPSskJLHiuvvzVHHSudK0hVJ7MyLu/rB0fdZ9YdStEUKNRVf9atR1NNM5Qyf
X-Received: by 10.50.6.100 with SMTP id z4mr6740590igz.37.1413293921877; Tue, 14 Oct 2014 06:38:41 -0700 (PDT)
Received: from oit201651646.local ([2601:2:5b00:675:e0d8:fc6e:3329:1ebc]) by mx.google.com with ESMTPSA id qo8sm11523832igb.7.2014.10.14.06.38.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 14 Oct 2014 06:38:35 -0700 (PDT)
Message-ID: <543D2759.3030302@umn.edu>
Date: Tue, 14 Oct 2014 08:38:33 -0500
From: David Farmer <farmer@umn.edu>
Organization: University of Minnesota
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: =?UTF-8?B?56We5piO6YGU5ZOJ?= <jinmei@wide.ad.jp>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com> <CAJE_bqd+BnnFf9X42fGHRAyPtDSrfjLyDTrQB76Bq425uOX-RA@mail.gmail.com>
In-Reply-To: <CAJE_bqd+BnnFf9X42fGHRAyPtDSrfjLyDTrQB76Bq425uOX-RA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/vqop8QPE5oqzt_sdeGNdyTjFJzA
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: David Farmer <farmer@umn.edu>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 14 Oct 2014 13:38:52 -0000

On 10/13/14, 13:49 , ç¥žæ˜Žé�”å“‰ wrote:
> At Mon, 13 Oct 2014 16:44:55 +0200,
> Alexandru Petrescu <alexandru.petrescu@gmail.com> wrote:
>
>> I am surprised there is no support in favor of
>> draft-boucadair-6man-prefix-routing-reco?
>>
>> https://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02
>>
>> Its main recommendation is:
>>>     Forwarding decision-making processes MUST NOT restrict by design the
>>>     length of IPv6 prefixes.  In particular, forwarding processes MUST be
>>>     designed to process prefixes of any length up to /128, by increments
>>>     of 1.
>>
>> What do you think?
>
> I've been busier for the last couple of weeks and couldn't respond to
> the adoption call before the deadline, but I agree this topic is worth
> discussing.  I don't have a strong opinion on whether this should
> belong to 6man or v6ops (or somewhere else), although v6ops seems to
> be slightly better than 6man.

Last week was NANOG and ARIN, the call for adoption came out Friday just 
before, well within its shadow and ended the same day as the ARIN 
meeting finished.

I think this is an important issue and needs work.  I also don't have a 
strong opinion if it should be in 6man or v6ops.

In my opinion the 64 bit netmask is an operational or at best an 
operational design issue that has been inappropriately promoted to an 
architectural issue without ever having a clear justification why it 
needs to be considered from architectural point of view.  The Why64 
draft at least provides some real reasons, but even in this draft it is 
clear that IPv6 is schizophrenic about the issue.  More clarity is 
needed, this draft might be that depending where we end up with it.

Thanks.

-- 
================================================
David Farmer               Email: farmer@umn.edu
Office of Information Technology
University of Minnesota
2218 University Ave SE     Phone: 1-612-626-0815
Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
================================================


From nobody Tue Oct 14 06:47:20 2014
Return-Path: <pthubert@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF97E1A8783 for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 06:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.287
X-Spam-Level: 
X-Spam-Status: No, score=-15.287 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.786, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 R5CiVrap3ODt for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 06:47:17 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D4081A874D for <ipv6@ietf.org>; Tue, 14 Oct 2014 06:47:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2174; q=dns/txt; s=iport; t=1413294437; x=1414504037; h=from:to:cc:subject:date:message-id: content-transfer-encoding:mime-version; bh=GVEuGBZraM/60bvYKv25mzk7AW4CdSYkK/rOtYKWieM=; b=AiBqqXSNM3t/qS63dQOz+amYnAnKib+TBol5eztpNE8PV6i5R/9cOOeT +lxS7BxlXXhYyDu4z57Vj3Yi3y2iYu1ChNB+ORCX4QBqzSPNmcrR/2LFN M/rxrZUN8CwMstHzE7Hns+pQ2DsKnGBHdVke7wdpxOO9HhUZQhUL43u7h 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ag8FAHAoPVStJV2S/2dsb2JhbABbgw5TWATMKgqHTQKBFBYBfYQCAQEBBAEBARodNAsMBgEIDgMEAQELFAkuCxQJCQEEAQ0FCIg2DcV7AQEBAQEBAQEBAQEBAQEBAQEBAQEBEwSPYxEBHzENgyeBHgWGLYtMjQCDRo0fg36Dd2yBDzmBAgEBAQ
X-IronPort-AV: E=Sophos;i="5.04,717,1406592000"; d="scan'208";a="363319353"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by rcdn-iport-2.cisco.com with ESMTP; 14 Oct 2014 13:47:16 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id s9EDlGZr018627 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 14 Oct 2014 13:47:16 GMT
Received: from xmb-rcd-x01.cisco.com ([169.254.1.132]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Tue, 14 Oct 2014 08:47:16 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>
Subject: RE: 6man IETF 91 Call for agenda items
Thread-Topic: 6man IETF 91 Call for agenda items
Thread-Index: Ac/ntTqzhHAAtcbtTM+AOtoMAXkM9g==
Date: Tue, 14 Oct 2014 13:47:15 +0000
Deferred-Delivery: Tue, 14 Oct 2014 13:47:00 +0000
Message-ID: <E045AECD98228444A58C61C200AE1BD842E19165@xmb-rcd-x01.cisco.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.49.80.52]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/TWEIBdx_c0LPTPHKuGD5IZjVw_0
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, "'Brian Haberman' \(brian@innovationslab.net\)" <brian@innovationslab.net>, Michael Richardson <mcr+ietf@sandelman.ca>, "Ines Robles \(mariainesrobles@googlemail.com\)" <mariainesrobles@googlemail.com>, "Ralph Droms \(rdroms\)" <rdroms@cisco.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 14 Oct 2014 13:47:18 -0000

Dear chairs;

Following up on Brian's suggestion, I'd wish to have a slot to discuss draf=
t-thubert-6man-flow-label-for-rpl.

As it stands now, the draft does not standardize the operation by RPL nodes=
 anymore  - this is left to work in the LLN related groups- , but focuses o=
n allowing nodes in the LLN to reset the flow label at the LLN ingress or n=
ot set the flow label at a source node. This is done because transporting 2=
0 bits that are not useful in the LLN is generally not a good idea when we =
scrub every possible bit in the 6LoWPAN compression mechanisms.

Please let me know;

Pascal


> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Ole Troan
> Sent: vendredi 3 octobre 2014 09:31
> To: 6man WG
> Cc: 6man Chairs
> Subject: 6man IETF 91 Call for agenda items
>=20
> We have asked for a two and a half hour slot in Honolulu for the 6MAN
> working group.
>=20
> If you have a draft you would like to discuss, please send your request f=
or
> agenda time to the 6man chairs.
> Please include in the request, the title and file name of the draft, the
> speakers name (and email), and how much time you need.
>=20
> We will prioritise drafts that are working group items and drafts that ha=
ve
> been actively discussed on the list.
>=20
> We expect at least half the presentation time to be used for open
> discussion, please plan your presentation accordingly.
>=20
> New drafts not discussed on the mailing list prior to the meeting, or dra=
fts
> that do not appear to have support from the working group are unlikely to
> get time at the meeting.
>=20
> Please have agenda items to us by 2014-10-27 and also note the draft
> deadline for IETF91:
> 2014-10-27 (Monday): Internet Draft submission cut-off (for all drafts,
> including -00) by UTC 23:59
>=20
> Regards,
>=20
> Bob & Ole
>=20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Tue Oct 14 09:44:36 2014
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2A271A8A9F; Tue, 14 Oct 2014 09:44:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.354
X-Spam-Level: 
X-Spam-Status: No, score=-2.354 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, RP_MATCHES_RCVD=-0.786, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Z_-5w-2kbI5l; Tue, 14 Oct 2014 09:44:32 -0700 (PDT)
Received: from nostrum.com (raven.nostrum.com [69.55.229.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 558611A8A9A; Tue, 14 Oct 2014 09:44:32 -0700 (PDT)
Received: from unnumerable.local ([173.64.248.98]) (authenticated bits=0) by nostrum.com (8.14.9/8.14.7) with ESMTP id s9EGiUYl048481 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=OK); Tue, 14 Oct 2014 11:44:31 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host [173.64.248.98] claimed to be unnumerable.local
Message-ID: <543D52E9.8080601@nostrum.com>
Date: Tue, 14 Oct 2014 11:44:25 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: General Area Review Team <gen-art@ietf.org>, ipv6@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-6man-why64@tools.ietf.org
Subject: Genart Telechat review: draft-ietf-6man-why64-06
References: <5429128A.3090707@nostrum.com>
In-Reply-To: <5429128A.3090707@nostrum.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/-sUKs6uaLf01MiuPUE_tZGSi4pQ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 14 Oct 2014 16:44:34 -0000

I am the assigned Gen-ART reviewer for this draft. For background on
Gen-ART, please see the FAQ at
< http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please wait for direction from your document shepherd
or AD before posting a new version of the draft.

Document: draft-ietf-6man-why64-06
Reviewer: Robert Sparks
Review Date: 14-Oct-2014
IETF LC End Date: 30-Sep-2014
IESG Telechat date: 30-Oct-2014

Summary: Ready for publication as an Informational RFC


On 9/29/14 3:04 AM, Robert Sparks wrote:
>
> I am the assigned Gen-ART reviewer for this draft. For background on
> Gen-ART, please see the FAQ at
>
> <http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
> Document: draft-ietf-6man-why64-05
> Reviewer: Robert Sparks
> Review Date: 29-Sep-2014
> IETF LC End Date: 30-Sep-2014
> IESG Telechat date: (if known)
>
> Summary: Ready for publication as an Informational RFC
>
>


From nobody Tue Oct 14 14:23:17 2014
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB1E01A005E for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 14:23:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 uuGhwTfmFNDe for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 14:23:13 -0700 (PDT)
Received: from mail-yh0-x235.google.com (mail-yh0-x235.google.com [IPv6:2607:f8b0:4002:c01::235]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BABC11ACD29 for <ipv6@ietf.org>; Tue, 14 Oct 2014 14:23:13 -0700 (PDT)
Received: by mail-yh0-f53.google.com with SMTP id b6so5525256yha.26 for <ipv6@ietf.org>; Tue, 14 Oct 2014 14:23:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type; bh=neb6A8KO/ntM0P4hOowQfU+AkbIcaB49IPSYjZzSVCc=; b=UMVPqmXLIz70YHeAiKn9O6LKvf/3ud8AOD4NsY/Mneo/iLnfqwScZ10kq3E5oYsbTD xSfZq3NzlX3iPCWyxl1O4dklCI+DnFHViPAJeBn7sbWSzyV8Gu6gTcCeDstNG9PTyllD XcCVjyhpTarr+B/ssbZ6zb31nUrD9AXytQpM3shVjNSOvRm1u+2ldzHntY04nusXbwbn yA+7KEAdMLRASIUdXBFB5jnLDqJUn0J+yBbT1+bEyfXqetO1Oe6Ip+hK7U5K9ygNXvK/ bcmJLobUDJV/+fFZHaxvH6zTY6U340efdCjkhRrU2zdKoCTneZgbM1B5jtAJ5L0uELhn VrAA==
MIME-Version: 1.0
X-Received: by 10.236.206.11 with SMTP id k11mr5321967yho.185.1413321792920; Tue, 14 Oct 2014 14:23:12 -0700 (PDT)
Received: by 10.170.71.198 with HTTP; Tue, 14 Oct 2014 14:23:12 -0700 (PDT)
Date: Tue, 14 Oct 2014 16:23:12 -0500
Message-ID: <CAC8QAcdBBu-WApH35h819jmj2pb_ffrg+rRQJXPiTH4H2aHiUw@mail.gmail.com>
Subject: Re: 6man IETF 91 Call for agenda items
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/PGveAtflxZJjEQSV4a3Qb6gcFT8
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 14 Oct 2014 21:23:14 -0000

Hi Ole, Bob,

Can I have a slot to discuss
draft-sarikaya-6man-sadr-overview
draft-sarikaya-6man-next-hop-ra
draft-sarikaya-dhc-dhcpv6-raoptions-sadr

Regards,

Behcet


From nobody Tue Oct 14 19:50:27 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A06351A01C6; Tue, 14 Oct 2014 19:50:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 ifnMUjbec0gH; Tue, 14 Oct 2014 19:50:22 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3737A1A01AA; Tue, 14 Oct 2014 19:50:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-resilient-rs-04.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141015025022.2238.45373.idtracker@ietfa.amsl.com>
Date: Tue, 14 Oct 2014 19:50:22 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/wsk9jRm27vXf-EzB3pWB-XgCXSE
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 15 Oct 2014 02:50:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Packet loss resiliency for Router Solicitations
        Authors         : Suresh Krishnan
                          Dmitry Anipko
                          Dave Thaler
	Filename        : draft-ietf-6man-resilient-rs-04.txt
	Pages           : 6
	Date            : 2014-10-14

Abstract:
   When an interface on a host is initialized, the host transmits Router
   Solicitations in order to minimize the amount of time it needs to
   wait until the next unsolicited multicast Router Advertisement is
   received.  In certain scenarios, these router solicitations
   transmitted by the host might be lost.  This document specifies a
   mechanism for hosts to cope with the loss of the initial Router
   Solicitations.  Furthermore, on some links, unsolicited multicast
   Router Advertisements are never sent and the mechanism in this
   document is intended to work even in such scenarios.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-resilient-rs-04

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-resilient-rs-04


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue Oct 14 23:39:07 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5209D1A038F for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 23:39:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.336
X-Spam-Level: 
X-Spam-Status: No, score=-4.336 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 ugTejqB6Fmyq for <ipv6@ietfa.amsl.com>; Tue, 14 Oct 2014 23:39:03 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19A5B1A0382 for <ipv6@ietf.org>; Tue, 14 Oct 2014 23:39:02 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Au8EAKMVPlStJssW/2dsb2JhbABbkhXFeAKBLAF9hAMBAQMBHR0/BQsLRleITwjHcgEBAQEBBQEBAQEBAQEbkBszBxaDF4EeAQSzaoN5O4J5AQEB
X-IronPort-AV: E=Sophos;i="5.04,721,1406592000"; d="scan'208";a="211296248"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 15 Oct 2014 06:39:01 +0000
Received: from dhcp-10-61-104-46.cisco.com (dhcp-10-61-104-46.cisco.com [10.61.104.46]) by aer-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s9F6d0e2025397 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Oct 2014 06:39:00 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: 6man IETF 91 Call for agenda items
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAC8QAcdBBu-WApH35h819jmj2pb_ffrg+rRQJXPiTH4H2aHiUw@mail.gmail.com>
Date: Wed, 15 Oct 2014 08:39:02 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <2D753623-2452-49F1-A7C7-4769D3F06C7A@employees.org>
References: <CAC8QAcdBBu-WApH35h819jmj2pb_ffrg+rRQJXPiTH4H2aHiUw@mail.gmail.com>
To: sarikaya@ieee.org
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/X-w8i3-p5bX37g6NzB230CYPXLg
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 15 Oct 2014 06:39:05 -0000

Behcet,

> Can I have a slot to discuss
> draft-sarikaya-6man-sadr-overview
> draft-sarikaya-6man-next-hop-ra
> draft-sarikaya-dhc-dhcpv6-raoptions-sadr

Thanks for the agenda request, we will add it to our queue and be back =
in touch.

Best regards,
Ole


From nobody Wed Oct 15 11:45:34 2014
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 541DC1A90E3 for <ipv6@ietfa.amsl.com>; Wed, 15 Oct 2014 11:45:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_SOFTFAIL=0.665] autolearn=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 jcyaxc0urWyE for <ipv6@ietfa.amsl.com>; Wed, 15 Oct 2014 11:45:31 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64D6E1A90D5 for <ipv6@ietf.org>; Wed, 15 Oct 2014 11:45:29 -0700 (PDT)
Received: from [172.22.229.45] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s9FIjRkQ001157 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 Oct 2014 11:45:27 -0700
Message-ID: <543EC0C7.4000400@acm.org>
Date: Wed, 15 Oct 2014 11:45:27 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com> <543C2D08.5080204@gmail.com> <543CEC62.3080005@gmail.com> <B8FDF830-E404-4604-A2A3-D8A06BE9098E@employees.org>
In-Reply-To: <B8FDF830-E404-4604-A2A3-D8A06BE9098E@employees.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVbwycVgv4EFuhdcOCBsTZQCC996NmaXaiBMCgNHlcUBSBdLIxNH7byZSa1ZGR58IEiOai0LNktUIWWuu1KSMTkw
X-Sonic-ID: C;JrIfbptU5BGPo3yTE+W37Q== M;gA0ubptU5BGPo3yTE+W37Q==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/H72pkFygw-PZX-I1XxFNUpsXAWg
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 15 Oct 2014 18:45:32 -0000

On 10/14/14 2:39 AM, Ole Troan wrote:
> taking a document through to RFC publication has a cost. given that 
> there hasn't so far been any problems from not having this document, 
> is probably good enough reason to not publish it. even though I'm 
> pretty sure this document reflects the consensus of the community. ;-)

I wonder whether the document would be useful to the larger community.

The folks that have spent the last decade (or two) on this and earlier 
mailing list might have a fairly good grasp on how prefix assignment 
plus routing works in IPv6, but as IPv6 gets deployed more widely there 
is a larger community that needs to understand these aspects.

*If* an RFC provides useful information in this area, then it probably 
make sense for us to get it done, even if it would take some work to get 
the document reviewed.

My 2 cents,
    Erik


From nobody Wed Oct 15 12:14:26 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CDF361A9151 for <ipv6@ietfa.amsl.com>; Wed, 15 Oct 2014 12:14:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.235
X-Spam-Level: 
X-Spam-Status: No, score=-6.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_SOFTFAIL=0.665] autolearn=ham
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 GPordiEA5CZJ for <ipv6@ietfa.amsl.com>; Wed, 15 Oct 2014 12:14:18 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2425D1A1B19 for <ipv6@ietf.org>; Wed, 15 Oct 2014 12:14:17 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AqAEAG7GPlStJssW/2dsb2JhbABb2AkCgS0BfYQDAQEDAW4LEAtGVwYniCIIyHoBAQEBAQEBAQEBAQEBAQEBAQEBGZAbMweDLYEeAQSzboN5O4J5AQEB
X-IronPort-AV: E=Sophos;i="5.04,726,1406592000"; d="scan'208";a="207859224"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 15 Oct 2014 19:14:16 +0000
Received: from dhcp-10-61-106-198.cisco.com (dhcp-10-61-106-198.cisco.com [10.61.106.198]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id s9FJEF5D026385 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 15 Oct 2014 19:14:16 GMT
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
From: Ole Troan <otroan@employees.org>
In-Reply-To: <543EC0C7.4000400@acm.org>
Date: Wed, 15 Oct 2014 21:14:14 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7F9C5EB1-5A9A-4C26-B922-5745DFCC6655@employees.org>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com> <543C2D08.5080204@gmail.com> <543CEC62.3080005@gmail.com> <B8FDF830-E404-4604-A2A3-D8A06BE9098E@employees.org> <543EC0C7.4000400@acm.org>
To: Erik Nordmark <nordmark@acm.org>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/ISk475RbzdFr6aDaLIb8w6VqR-w
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Wed, 15 Oct 2014 19:14:22 -0000

>> taking a document through to RFC publication has a cost. given that =
there hasn't so far been any problems from not having this document, is =
probably good enough reason to not publish it. even though I'm pretty =
sure this document reflects the consensus of the community. ;-)
>=20
> I wonder whether the document would be useful to the larger community.
>=20
> The folks that have spent the last decade (or two) on this and earlier =
mailing list might have a fairly good grasp on how prefix assignment =
plus routing works in IPv6, but as IPv6 gets deployed more widely there =
is a larger community that needs to understand these aspects.
>=20
> *If* an RFC provides useful information in this area, then it probably =
make sense for us to get it done, even if it would take some work to get =
the document reviewed.

OK, so I may be to embedded in this to understand what the possible =
misunderstandings could be.
are these speculations about possible problems in the future, or are =
there actual problems with the documents today that have led other =
designers of protocols or implementors to have got it wrong?

as a slight digression, since we're on the topic of forwarding.
IPv6 uses the CIDR (RFC1519/RFC1812) forwarding algorithm. aka longest =
matching prefix.
if someone is interested there is work in the routing area / homenet on =
modifying this, and including the source address in the algorithm. =
Source Address Dependent Routing.

cheers,
Ole=


From nobody Thu Oct 16 07:18:58 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C2B61A1A69 for <ipv6@ietfa.amsl.com>; Thu, 16 Oct 2014 07:18:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 JaTA9YXwgnVl for <ipv6@ietfa.amsl.com>; Thu, 16 Oct 2014 07:18:53 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 696DB1A1ADE for <ipv6@ietf.org>; Thu, 16 Oct 2014 07:18:21 -0700 (PDT)
Received: from [2001:c08:3700:ffff::48d] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1Xelsc-0002pg-3D; Thu, 16 Oct 2014 16:18:14 +0200
Message-ID: <543FD0D1.4060400@si6networks.com>
Date: Thu, 16 Oct 2014 11:06:09 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>
In-Reply-To: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/3Y1WG4jRSL4sdxl3xwI5wx5S6GA
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Thu, 16 Oct 2014 14:18:55 -0000

Folks,

I have reviewed this document, and support its adoption as a 6man
document provided the following issues are addressed in a next rev:

1) IMO, the document should clearly state what's the problem it is
addressing. My understanding is that this document has been published in
response to 6man discussions where it was noted that some
implementations have performance penalties for prefixes longer than 64.
If that's the case, the very abstract should state that.


2) The current track of this document is "Std Track". But this document
doesn't specify anything new, nor does it formally update any existing
standard. So  would suggest that (either):

 a) The track is changed to "Informational", such that this document
    serves as a kind of "implementation guidance", or,

 b) It clearly states which document it is updating.


Thanks,
Fernando




On 10/03/2014 04:28 AM, Ole Troan wrote:
> All,
> 
> The authors have requested an adoption call for this document as a standards track document.
> 
> Please provide a view with reasons as to whether the WG should adopt this or not.
> 
> This message starts a one week 6MAN Working Group call on adopting:
> 
> 	Title           : IPv6 Prefix Length Recommendation for Forwarding
> 	Author(s)    : M. Boucadair, A. Petrescu
> 	Filename    : draft-boucadair-6man-prefix-routing-reco-02
> 	Pages        : 4
> 	Date          : 2014-09-24
> 
> http://tools.ietf.org/html/draft-boucadair-6man-prefix-routing-reco-02
> 
> The call ends on October 10th, 2014.
> 
> Regards,
> 
> Bob Hinden & Ole TrÃ¸an
> 
> 
> --------------------------------------------------------------------
> 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
> --------------------------------------------------------------------
> 


-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Sun Oct 19 10:50:27 2014
Return-Path: <n.oje.bar@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6060B1A1BE8 for <ipv6@ietfa.amsl.com>; Sun, 19 Oct 2014 09:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.622
X-Spam-Level: 
X-Spam-Status: No, score=0.622 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 SwDuwojvQekc for <ipv6@ietfa.amsl.com>; Sun, 19 Oct 2014 09:25:54 -0700 (PDT)
Received: from mail-yh0-x230.google.com (mail-yh0-x230.google.com [IPv6:2607:f8b0:4002:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 030191A1BC3 for <ipv6@ietf.org>; Sun, 19 Oct 2014 09:25:53 -0700 (PDT)
Received: by mail-yh0-f48.google.com with SMTP id v1so1894574yhn.21 for <ipv6@ietf.org>; Sun, 19 Oct 2014 09:25:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=5k0UoEyGdeIVccpx9Aye33OnjJmZlfi4Tkfr4o3eBm4=; b=v7T4Tb7vP5eQ5TMl4GJHrdfy29OU/Xu1XWhsMUZOMHG2lMZF4Z2jSJqnOjDjNbXU9r aYwvNGHEzft5HTUD6ZNedyOtXp/7f8BbXTo8YBCN0uW78ytVzFKD9UR/ggONV+NV5Q8n RoTOWklYzvw1ltdFF6T0SyL10y7i35UX6Dz4PGCVGPm6cWjxPKDBdEqBvkFLqz+9b8LF DBDcqkLyOpLmCkd6wIW2B7q4mpLgDos+IOrq+qFrXtTAQ60o2+z2YQneWEpygQzDxMWj muKgnQWWk9OiXpe84Zet+V0Zm0kCjODdi9EEEF1OMBxaGIQUXD4XE7xme5RhRzuj/gAf W2pQ==
MIME-Version: 1.0
X-Received: by 10.236.208.103 with SMTP id p67mr30038638yho.35.1413735953319;  Sun, 19 Oct 2014 09:25:53 -0700 (PDT)
Sender: n.oje.bar@gmail.com
Received: by 10.170.82.214 with HTTP; Sun, 19 Oct 2014 09:25:53 -0700 (PDT)
Date: Sun, 19 Oct 2014 17:25:53 +0100
X-Google-Sender-Auth: hFxk1dTIHbruSLMKABTO3qpycZw
Message-ID: <CAPunWhBiZ5xzZYB1EEWZOAqk+A3C7FOy1Wc0t3weNNWTLZ70aQ@mail.gmail.com>
Subject: question on ICMP error packets, RFC 4443, 2.4 e)
From: Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk>
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=089e015388aa4dcf610505c90d03
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/R_D--HWQSTLJyvrWES_y25tz208
X-Mailman-Approved-At: Sun, 19 Oct 2014 10:50:25 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sun, 19 Oct 2014 16:25:55 -0000

--089e015388aa4dcf610505c90d03
Content-Type: text/plain; charset=UTF-8

Hello,

In RFC 4443, 2.4 e.1) it says that ICMP6 errors should not be generated in
response to other ICMP errors. And in 2.4. e.3) it says that one should
generate an ICMP6 error in response to a packet with multicast destination
that has a unrecognized IPv6 option with option type with highest order 2
bits 10.

My question is whether one still has to check that the message considered
e.3) is not an ICMP6 error packet before generating one in response.
Similarly for uni/anycast messages satisfying the condition of e.3).

Please excuse if I have missed something obvious.

Thank you very much!
Nicolas

--089e015388aa4dcf610505c90d03
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello,<div><br></div><div>In RFC 4443, 2.4 e.1) it says th=
at ICMP6 errors should not be generated in response to other ICMP errors. A=
nd in 2.4. e.3) it says that one should generate an ICMP6 error in response=
 to a packet with multicast destination that has a unrecognized IPv6 option=
 with option type with highest order 2 bits 10.</div><div><br></div><div>My=
 question is whether one still has to check that the message considered e.3=
) is not an ICMP6 error packet before generating one in response. Similarly=
 for uni/anycast messages satisfying the condition of e.3).</div><div><br><=
/div><div>Please excuse if I have missed something obvious.</div><div><br><=
/div><div>Thank you very much!</div><div>Nicolas</div></div>

--089e015388aa4dcf610505c90d03--


From nobody Sun Oct 19 12:17:39 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 181781A00FC; Sun, 19 Oct 2014 12:17:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 jpm9HgqPKQJU; Sun, 19 Oct 2014 12:17:29 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B2501A006F; Sun, 19 Oct 2014 12:17:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-why64-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141019191729.12341.86838.idtracker@ietfa.amsl.com>
Date: Sun, 19 Oct 2014 12:17:29 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/e3eUt42FeGZ8bJMr9dpydhPM-DI
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sun, 19 Oct 2014 19:17:36 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Analysis of the 64-bit Boundary in IPv6 Addressing
        Authors         : Brian Carpenter
                          Tim Chown
                          Fernando Gont
                          Sheng Jiang
                          Alexandru Petrescu
                          Andrew Yourtchenko
	Filename        : draft-ietf-6man-why64-07.txt
	Pages           : 24
	Date            : 2014-10-19

Abstract:
   The IPv6 unicast addressing format includes a separation between the
   prefix used to route packets to a subnet and the interface identifier
   used to specify a given interface connected to that subnet.
   Currently the interface identifier is defined as 64 bits long for
   almost every case, leaving 64 bits for the subnet prefix.  This
   document describes the advantages of this fixed boundary and analyses
   the issues that would be involved in treating it as a variable
   boundary.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-why64/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-why64-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-why64-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sun Oct 19 12:23:49 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC231A1ADF for <ipv6@ietfa.amsl.com>; Sun, 19 Oct 2014 12:23:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 Rku0wpazTCRb for <ipv6@ietfa.amsl.com>; Sun, 19 Oct 2014 12:23:46 -0700 (PDT)
Received: from mail-pd0-x22f.google.com (mail-pd0-x22f.google.com [IPv6:2607:f8b0:400e:c02::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEB531A00FC for <ipv6@ietf.org>; Sun, 19 Oct 2014 12:23:46 -0700 (PDT)
Received: by mail-pd0-f175.google.com with SMTP id v10so3631634pde.20 for <ipv6@ietf.org>; Sun, 19 Oct 2014 12:23:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=tomOshd05dNr57Jk1ynHcJNlHLI6SJoXRhwE0YKHqog=; b=yulnej5XJjNTKvh2/b4KRlPFyMGfb9EPvkYCRvPX4SRacjN2vQxuoTjc9SoWJ9ascC upLHRDmAtE5M7Kt9MOrH4U5shb1KNz7AerTQyhvoW19JqCTeICoVAZg/LvmjGyWh532U rE0R0aV+vf41CXwkwOONq5HpcA5FZbtKJhMYNZhBp9LHSLlV19LqBjZ+2gKcuTLeaqhQ sJfjnF1L28FQDIiB5ww7ejyKTuqQhHQZ7Tu6415qHpdbTWF/IHPDgyPcSSqm/XPiAzNd 3QB8PgY/cG48k0gj5pNcnjUHrk1TMXmTkOgJe4suZsetggiPKPpiAS1rFfaJvM9Zys50 hovw==
X-Received: by 10.68.93.228 with SMTP id cx4mr22621888pbb.45.1413746626292; Sun, 19 Oct 2014 12:23:46 -0700 (PDT)
Received: from [192.168.178.23] (237.195.69.111.dynamic.snap.net.nz. [111.69.195.237]) by mx.google.com with ESMTPSA id pj4sm2122553pdb.37.2014.10.19.12.23.43 for <ipv6@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 Oct 2014 12:23:45 -0700 (PDT)
Message-ID: <54440FBF.9090009@gmail.com>
Date: Mon, 20 Oct 2014 08:23:43 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: ipv6@ietf.org
Subject: Re: I-D Action: draft-ietf-6man-why64-07.txt
References: <20141019191729.12341.86838.idtracker@ietfa.amsl.com>
In-Reply-To: <20141019191729.12341.86838.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/QQTzYrPBZy7z5lDRK1WkwwxNxlI
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sun, 19 Oct 2014 19:23:48 -0000

Hi,

To cover the Linux issue, I slightly updated Fernando's tables by
adding a new category "NOT-DEF" to the results (meaning not
enabled by default).


I also fixed a small editorial issue that Benoit Claise noticed.

   Brian

On 20/10/2014 08:17, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
> 
>         Title           : Analysis of the 64-bit Boundary in IPv6 Addressing
>         Authors         : Brian Carpenter
>                           Tim Chown
>                           Fernando Gont
>                           Sheng Jiang
>                           Alexandru Petrescu
>                           Andrew Yourtchenko
> 	Filename        : draft-ietf-6man-why64-07.txt
> 	Pages           : 24
> 	Date            : 2014-10-19
> 
> Abstract:
>    The IPv6 unicast addressing format includes a separation between the
>    prefix used to route packets to a subnet and the interface identifier
>    used to specify a given interface connected to that subnet.
>    Currently the interface identifier is defined as 64 bits long for
>    almost every case, leaving 64 bits for the subnet prefix.  This
>    document describes the advantages of this fixed boundary and analyses
>    the issues that would be involved in treating it as a variable
>    boundary.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-why64/
> 
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-why64-07
> 
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-why64-07
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 


From nobody Sun Oct 19 14:14:16 2014
Return-Path: <n.oje.bar@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 881181A0270 for <ipv6@ietfa.amsl.com>; Sun, 19 Oct 2014 14:14:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level: 
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=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 uy5J1ps_TXlo for <ipv6@ietfa.amsl.com>; Sun, 19 Oct 2014 14:14:09 -0700 (PDT)
Received: from mail-yh0-x233.google.com (mail-yh0-x233.google.com [IPv6:2607:f8b0:4002:c01::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F6FB1A07BE for <ipv6@ietf.org>; Sun, 19 Oct 2014 14:14:09 -0700 (PDT)
Received: by mail-yh0-f51.google.com with SMTP id t59so2093962yho.38 for <ipv6@ietf.org>; Sun, 19 Oct 2014 14:14:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:sender:date:message-id:subject:from:to:content-type;  bh=3D4R2CnOFUTryj/49J9ONbRIy+80pd3jQaWDEsDbWl8=; b=JlDnGyp4kYogK5V/ZSxpPVSIlETVoNWifgjfAdtvpCrpphMOZxxM1R8FxvvtyGN60s MU3qF8bWddkwEpo7Y2YPQV0DiscPJgTRagcgH1DVqkxNbh7TjmyFeAY5A9UYJ5j1vm/O Kx56VgJ/8GZWCzqExrK9PbdIlJIzthZbn69z35UrNEFd8dm97+RK6G+WKYsMQNuAE50L 5C91kBZ7/B2XkLx3mTeBPxECJJ/IPe2bljmsW74OpI+OIM/uppT4LKPEjecTRSH/HZER 4hX/tFLEZQV1m76T0NHcM1UVUX4aIW2wRchYtC9xxRSs+xwyERkGvJD3TkV0RvTiIIIl tE1A==
MIME-Version: 1.0
X-Received: by 10.236.203.114 with SMTP id e78mr33373256yho.47.1413753248525;  Sun, 19 Oct 2014 14:14:08 -0700 (PDT)
Sender: n.oje.bar@gmail.com
Received: by 10.170.82.214 with HTTP; Sun, 19 Oct 2014 14:14:08 -0700 (PDT)
Date: Sun, 19 Oct 2014 22:14:08 +0100
X-Google-Sender-Auth: 82R_Tkn4lTXVmuGClSi53boeCZ4
Message-ID: <CAPunWhC-ceaSgKXF2qGQPXuRhc9+v0bYt5NRS+tH2WHCH0z_BQ@mail.gmail.com>
Subject: question on ICMP error packets, RFC 4443, 2.4 e)
From: Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk>
To: ipv6@ietf.org
Content-Type: multipart/alternative; boundary=089e0158c7c42db3520505cd1430
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/AKr9pSCdvq-BgXmwI2I7L1LPp3c
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sun, 19 Oct 2014 21:14:10 -0000

--089e0158c7c42db3520505cd1430
Content-Type: text/plain; charset=UTF-8

(apologies if you receive two copies of this message)

Hello,

In RFC 4443, 2.4 e.1) it says that ICMP6 errors should not be generated in
response to other ICMP errors. And in 2.4. e.3) it says that one should
generate an ICMP6 error in response to a packet with multicast destination
that has a unrecognized IPv6 option with option type with highest order 2
bits 10.

My question is whether one still has to check that the message considered
e.3) is not an ICMP6 error packet before generating one in response.
Similarly for uni/anycast messages satisfying the condition of e.3).

Please excuse if I have missed something obvious.

Thank you very much!

Nicolas

--089e0158c7c42db3520505cd1430
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div><span style=3D"font-family:arial,sans-serif;font-size=
:13px">(apologies if you receive two copies of this message)</span></div><d=
iv><span style=3D"font-family:arial,sans-serif;font-size:13px"><br></span><=
/div><span style=3D"font-family:arial,sans-serif;font-size:13px">Hello,</sp=
an><div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><di=
v style=3D"font-family:arial,sans-serif;font-size:13px">In RFC 4443, 2.4 e.=
1) it says that ICMP6 errors should not be generated in response to other I=
CMP errors. And in 2.4. e.3) it says that one should generate an ICMP6 erro=
r in response to a packet with multicast destination that has a unrecognize=
d IPv6 option with option type with highest order 2 bits 10.</div><div styl=
e=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div style=3D"f=
ont-family:arial,sans-serif;font-size:13px">My question is whether one stil=
l has to check that the message considered e.3) is not an ICMP6 error packe=
t before generating one in response. Similarly for uni/anycast messages sat=
isfying the condition of e.3).</div><div style=3D"font-family:arial,sans-se=
rif;font-size:13px"><br></div><div style=3D"font-family:arial,sans-serif;fo=
nt-size:13px">Please excuse if I have missed something obvious.</div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div style=
=3D"font-family:arial,sans-serif;font-size:13px">Thank you very much!</div>=
<div style=3D"font-family:arial,sans-serif;font-size:13px"><br></div><div s=
tyle=3D"font-family:arial,sans-serif;font-size:13px">Nicolas</div></div>

--089e0158c7c42db3520505cd1430--


From nobody Sun Oct 19 15:53:54 2014
Return-Path: <tom.taylor.stds@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D281B1A066C for <ipv6@ietfa.amsl.com>; Sun, 19 Oct 2014 15:53:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 z2jBaDUe9zTB for <ipv6@ietfa.amsl.com>; Sun, 19 Oct 2014 15:53:50 -0700 (PDT)
Received: from mail-ie0-x22a.google.com (mail-ie0-x22a.google.com [IPv6:2607:f8b0:4001:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59E091A19EE for <ipv6@ietf.org>; Sun, 19 Oct 2014 15:53:50 -0700 (PDT)
Received: by mail-ie0-f170.google.com with SMTP id rd18so3685071iec.29 for <ipv6@ietf.org>; Sun, 19 Oct 2014 15:53:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=PPrVS4AESIHJFOfhuQFtz4QeQvh/hMVEKj5j2uU1qKI=; b=iUbe4a4+ZR+9zmAdmdZd8+WsH1xsJfgIvhwdj6SFOJF5tmjHkzHl/PbYNuTzi3LkaO rE9saiccL2lG2SJGKEd3Ze0bUQyLz+6A9Q7FEZfZwBBSX1CpbeoMcik9XZA0H3F9QaEL GBGQ89JOkyisg8IkVWnqE1sIn6yHpvjMmV1spskk9OSrvtJc1MJ3NhjlCu8ule9MH/qM t6s8X4/2QvnES5LV0ozj6OP/4jRNSInsbT+bD1im1HOMlusH8VfcHSnQWq7AwnD3LjWj Y/qBw/ZBbJqKgyTA0ZgWam7npKNOxjqZGy375SUxDRaHWJtJC/SobHP9SYcGwhBUDcl2 wyyw==
X-Received: by 10.50.122.100 with SMTP id lr4mr4852480igb.9.1413759229602; Sun, 19 Oct 2014 15:53:49 -0700 (PDT)
Received: from [192.168.0.102] ([64.56.228.254]) by mx.google.com with ESMTPSA id g7sm3021003igg.1.2014.10.19.15.53.49 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 19 Oct 2014 15:53:49 -0700 (PDT)
Message-ID: <544440F3.5010309@gmail.com>
Date: Sun, 19 Oct 2014 18:53:39 -0400
From: Tom Taylor <tom.taylor.stds@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk>, ipv6@ietf.org
Subject: Re: question on ICMP error packets, RFC 4443, 2.4 e)
References: <CAPunWhC-ceaSgKXF2qGQPXuRhc9+v0bYt5NRS+tH2WHCH0z_BQ@mail.gmail.com>
In-Reply-To: <CAPunWhC-ceaSgKXF2qGQPXuRhc9+v0bYt5NRS+tH2WHCH0z_BQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/6xZC8A7CQB-o2L4iW6ZxRB76I2I
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sun, 19 Oct 2014 22:53:52 -0000

The basic principle is that you never answer an error with an error, or 
you could generate an infinite loop.

Tom Taylor

On 19/10/2014 5:14 PM, Nicolas Ojeda Bar wrote:
> (apologies if you receive two copies of this message)
>
> Hello,
>
> In RFC 4443, 2.4 e.1) it says that ICMP6 errors should not be generated in
> response to other ICMP errors. And in 2.4. e.3) it says that one should
> generate an ICMP6 error in response to a packet with multicast destination
> that has a unrecognized IPv6 option with option type with highest order 2
> bits 10.
>
> My question is whether one still has to check that the message considered
> e.3) is not an ICMP6 error packet before generating one in response.
> Similarly for uni/anycast messages satisfying the condition of e.3).
>
> Please excuse if I have missed something obvious.
>
> Thank you very much!
>
> Nicolas
>
>
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


From nobody Mon Oct 20 06:38:14 2014
Return-Path: <Tina.Tsou.Zouting@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE2A31A8750 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 06:38:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 uFBwCc94wQgB for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 06:38:09 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A84B1A802C for <ipv6@ietf.org>; Mon, 20 Oct 2014 06:36:16 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNV64439; Mon, 20 Oct 2014 13:36:14 +0000 (GMT)
Received: from SZXEML449-HUB.china.huawei.com (10.82.67.192) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 20 Oct 2014 14:36:13 +0100
Received: from szxeml557-mbs.china.huawei.com ([169.254.6.57]) by szxeml449-hub.china.huawei.com ([10.82.67.192]) with mapi id 14.03.0158.001; Mon, 20 Oct 2014 21:35:56 +0800
From: Tina TSOU <Tina.Tsou.Zouting@huawei.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Adoption call of draft-gont-6man-deprecate-atomfrag-generation for 6MAN
Thread-Topic: Adoption call of draft-gont-6man-deprecate-atomfrag-generation for 6MAN
Thread-Index: AQHP5q8uCVl2EA/M90epGXc5KBKGCZwtF5IAgADMW4CACyRAmg==
Date: Mon, 20 Oct 2014 13:35:55 +0000
Message-ID: <C902CD8A-EFF9-43DD-B15C-339E1214C4B5@huawei.com>
References: <2742D96E-1538-4ECF-BB3A-6A194D9DBB96@employees.org> <alpine.DEB.2.02.1410130914060.14735@uplift.swm.pp.se>, <543C2797.8030607@gmail.com>
In-Reply-To: <543C2797.8030607@gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Content-Type: multipart/alternative; boundary="_000_C902CD8AEFF943DDB15C339E1214C4B5huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/70DJByI3NwGPDpL-mcnxTF-iRPo
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 20 Oct 2014 13:38:12 -0000

--_000_C902CD8AEFF943DDB15C339E1214C4B5huaweicom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Dear all,

I support adoption of this document as a WG item.

It addresses a concrete issue with the current specs, offering a straightfo=
rward mitigation.


Thank you,
Tina

On Oct 13, 2014, at 9:27 PM, Brian E Carpenter <brian.e.carpenter@gmail.com=
<mailto:brian.e.carpenter@gmail.com>> wrote:

On 13/10/2014 20:15, Mikael Abrahamsson wrote:
On Mon, 13 Oct 2014, Ole Troan wrote:

All,

The authors have requested an adoption call for this document as a
standards track document.

Please provide a view with reasons as to whether the WG should adopt
this or not.

I support that we're taking a good look at this problem.

Yes. This is (another) case where our standards allow bad things
to happen, so we should try to fix it, and I think this draft
heads in the direction of a fix.

  Brian

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

--_000_C902CD8AEFF943DDB15C339E1214C4B5huaweicom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
</head>
<body dir=3D"auto">
<div><span style=3D"font-size: 13pt;">Dear all,</span></div>
<div><br>
</div>
<div><span style=3D"background-color: rgba(255, 255, 255, 0);">I support ad=
option of this document as a WG item.&nbsp;</span></div>
<div><span style=3D"background-color: rgba(255, 255, 255, 0);"><br>
</span></div>
<div><span style=3D"background-color: rgba(255, 255, 255, 0);">It addresses=
 a concrete issue with the current specs, offering a straightforward mitiga=
tion.</span></div>
<div><br>
<div><br>
</div>
<div>Thank you,</div>
<div>Tina</div>
</div>
<div><br>
On Oct 13, 2014, at 9:27 PM, Brian E Carpenter &lt;<a href=3D"mailto:brian.=
e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a>&gt; wrote:<br>
<br>
</div>
<div><span></span></div>
<blockquote type=3D"cite">
<div><span>On 13/10/2014 20:15, Mikael Abrahamsson wrote:</span><br>
<blockquote type=3D"cite"><span>On Mon, 13 Oct 2014, Ole Troan wrote:</span=
><br>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>All,</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>The authors have requested an adoption call=
 for this document as a</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>standards track document.</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span></span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>Please provide a view with reasons as to wh=
ether the WG should adopt</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite">
<blockquote type=3D"cite"><span>this or not.</span><br>
</blockquote>
</blockquote>
<blockquote type=3D"cite"><span></span><br>
</blockquote>
<blockquote type=3D"cite"><span>I support that we're taking a good look at =
this problem.</span><br>
</blockquote>
<span></span><br>
<span>Yes. This is (another) case where our standards allow bad things</spa=
n><br>
<span>to happen, so we should try to fix it, and I think this draft</span><=
br>
<span>heads in the direction of a fix.</span><br>
<span></span><br>
<span>&nbsp;&nbsp;Brian</span><br>
<span></span><br>
<span>--------------------------------------------------------------------<=
/span><br>
<span>IETF IPv6 working group mailing list</span><br>
<span><a href=3D"mailto:ipv6@ietf.org">ipv6@ietf.org</a></span><br>
<span>Administrative Requests: <a href=3D"https://www.ietf.org/mailman/list=
info/ipv6">
https://www.ietf.org/mailman/listinfo/ipv6</a></span><br>
<span>--------------------------------------------------------------------<=
/span><br>
</div>
</blockquote>
</body>
</html>

--_000_C902CD8AEFF943DDB15C339E1214C4B5huaweicom_--


From nobody Mon Oct 20 09:39:59 2014
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19A4D1A8A86 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 09:39:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level: 
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=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 dULdYcM4hVkA for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 09:39:55 -0700 (PDT)
Received: from mail-yh0-x22c.google.com (mail-yh0-x22c.google.com [IPv6:2607:f8b0:4002:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFA891A8A99 for <6man@ietf.org>; Mon, 20 Oct 2014 09:27:04 -0700 (PDT)
Received: by mail-yh0-f44.google.com with SMTP id i57so3492891yha.3 for <6man@ietf.org>; Mon, 20 Oct 2014 09:27:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:reply-to:date:message-id:subject:from:to:content-type;  bh=g1r+4EvXWgcXkEnb649VNkyxLaWJtSEL540HKeDfvx8=; b=gVEprnrvlC6usb+4+ouCzvSuSl7TUHaltqD3yYbzgEl1MkCUih9ZwVBbdTCMWpBT8j INhYwEEgn1m34D5zSETLSuPjK4XAlnDCkPZ4e+ME+d1kKu95qPUXzLm7G29J2wFnwg/t lgxZZq9feeqrd5e82ANXodPJErqp3nwCTU/RWKmDesWjNGpMuHZ4kWtvX6TI+nboj0wS CYjOhha5xIupPQaVxJFtHBZGHOk9aQcFb00BDMyTYHKmlm6N5hlV7jMA1JphHqnuldIm SS4js7SC9nPao2ApT/HXSvnaHtyZ8nmYGuCJ4WfdYBNuRUlmuWv5XcOwuvx0MPri3XPH eQRQ==
MIME-Version: 1.0
X-Received: by 10.236.0.200 with SMTP id 48mr39813035yhb.79.1413822424012; Mon, 20 Oct 2014 09:27:04 -0700 (PDT)
Received: by 10.170.71.198 with HTTP; Mon, 20 Oct 2014 09:27:03 -0700 (PDT)
Date: Mon, 20 Oct 2014 11:27:03 -0500
Message-ID: <CAC8QAcdYRaxtzngS63xuBA3jnsm2XNFeDo68GQNynoGGXEenQQ@mail.gmail.com>
Subject: New Version Notification for draft-sarikaya-6man-sadr-overview-02.txt
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: "6man@ietf.org" <6man@ietf.org>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/K7nSD55mLr4vLpqwoVieK8MqKQE
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 20 Oct 2014 16:39:56 -0000

A new version of I-D, draft-sarikaya-6man-sadr-overview-02.txt
has been successfully submitted by Behcet Sarikaya and posted to the
IETF repository.

Name:           draft-sarikaya-6man-sadr-overview
Revision:       02
Title:          Overview of Source Address Dependent Routing
Document date:  2014-10-20
Group:          Individual Submission
Pages:          12
URL:
http://www.ietf.org/internet-drafts/draft-sarikaya-6man-sadr-overview-02.txt
Status:
https://datatracker.ietf.org/doc/draft-sarikaya-6man-sadr-overview/
Htmlized:       http://tools.ietf.org/html/draft-sarikaya-6man-sadr-overview-02
Diff:
http://www.ietf.org/rfcdiff?url2=draft-sarikaya-6man-sadr-overview-02

Abstract:
   This document presents an overview of source address dependent
   routing from the host perspective.  Multihomed hosts and hosts with
   multiple interfaces are considered.  Different architectures are
   introduced and with their help, why source address selection and next
   hop resolution in view of source address dependent routing is needed
   is explained.  The document concludes with a discussion on the
   standardization work that is needed.


From nobody Mon Oct 20 09:52:14 2014
Return-Path: <randy@psg.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C38BD1A0047 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 09:52:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 5hNQ9muB6vfR for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 09:52:12 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A63EC1A8780 for <ipv6@ietf.org>; Mon, 20 Oct 2014 09:37:29 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1XgFxW-0004sp-FC; Mon, 20 Oct 2014 16:37:27 +0000
Date: Tue, 21 Oct 2014 01:37:24 +0900
Message-ID: <m2fvei8zp7.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ole Troan <otroan@employees.org>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
In-Reply-To: <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/OLN90kuoT-WzSOIs7jq3_8sTIHg
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 20 Oct 2014 16:52:12 -0000

> The adoption call for draft-boucadair-6man-prefix-routing-reco for ended October 10th.
> With only two replies, none of them in support, I can only conclude
> that there is no support to adopt this document in 6MAN.

yikes.  that would be a damned shame.  this is a simple doc, to the
point, and sadly seems to be needed.

randy


From nobody Mon Oct 20 09:53:28 2014
Return-Path: <randy@psg.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B7CF1A6F5A for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 09:53:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 WLTLD6DLapu9 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 09:53:25 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E080B1A8A79 for <ipv6@ietf.org>; Mon, 20 Oct 2014 09:38:43 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1XgFyj-0004tY-7C; Mon, 20 Oct 2014 16:38:41 +0000
Date: Tue, 21 Oct 2014 01:38:39 +0900
Message-ID: <m2egu28zn4.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
In-Reply-To: <543C2D08.5080204@gmail.com>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com> <543C2D08.5080204@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/6Yvd-Pt5mXr1P8bZlzSk4WESHhs
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 20 Oct 2014 16:53:26 -0000

> I suspect the reason for the lack of replies is that people don't
> think it's necessary to publish a new standards track RFC for this.

sadly, the whack-a-mole of short compares is very much alive

randy


From nobody Mon Oct 20 12:02:47 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 529A71A9106 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 12:02:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 FpDDtJJLOEoA for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 12:02:45 -0700 (PDT)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 588091A8AF1 for <ipv6@ietf.org>; Mon, 20 Oct 2014 12:02:45 -0700 (PDT)
Received: by mail-pa0-f42.google.com with SMTP id bj1so5775646pad.15 for <ipv6@ietf.org>; Mon, 20 Oct 2014 12:02:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=/Xle6lWmrbKLdOr3W6U2H+/EgfW1AdR1Rj6gDfM+KRc=; b=qgHgMMOw44ruapMn8x+0Sm8CEvrD9isJ534QpsR+9+7IJA25aV7AJXY8oraI1gEUUZ KFwzwUjh3DblTAGnHADWXIXllCkm5ZVz94p6d0hjH1ftIkf9JgXRWp9gx+Q78KNtB1pZ 6lKRNjt+9khqIWKVdwtpIdG7qmVIFYyQ5g1FGmeE+Hr7u9gT8qrJPq9tPlpCFmY5L2jr W+IuQDeRwtLccGRd/TDltm5d7TIOUN7zV4yETtYUgOO06W2jmvzFUktVEBOXjRZ4KGOp f5ItWT5yYOZFRWPeB/i3oZR3CZUFGnIuRb2AEnMPHVDDKR1b3VTL6XtNNAToJ3/VquUX J5UQ==
X-Received: by 10.69.31.107 with SMTP id kl11mr29554521pbd.79.1413831764970; Mon, 20 Oct 2014 12:02:44 -0700 (PDT)
Received: from [192.168.178.23] (87.192.69.111.dynamic.snap.net.nz. [111.69.192.87]) by mx.google.com with ESMTPSA id ei1sm9792070pbd.46.2014.10.20.12.02.41 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Oct 2014 12:02:43 -0700 (PDT)
Message-ID: <54455C53.9080004@gmail.com>
Date: Tue, 21 Oct 2014 08:02:43 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>	<511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org>	<543BE567.50509@gmail.com>	<543C2D08.5080204@gmail.com> <m2egu28zn4.wl%randy@psg.com>
In-Reply-To: <m2egu28zn4.wl%randy@psg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/j2xxaUZMgP_KTf8SQzE-JZVCrDw
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 20 Oct 2014 19:02:46 -0000

On 21/10/2014 05:38, Randy Bush wrote:
>> I suspect the reason for the lack of replies is that people don't
>> think it's necessary to publish a new standards track RFC for this.
> 
> sadly, the whack-a-mole of short compares is very much alive

Ack. So is an RFC going to help? (Not being sarcastic: it's a genuine question.)

   Brian


From nobody Mon Oct 20 13:04:15 2014
Return-Path: <jean-francois.tremblay@viagenie.ca>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FC7F1ACDAC for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 13:04:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 5tL5U78XxvhW for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 13:04:11 -0700 (PDT)
Received: from jazz.viagenie.ca (jazz.viagenie.ca [IPv6:2620:0:230:8000::2]) by ietfa.amsl.com (Postfix) with ESMTP id AC68D1A6F61 for <ipv6@ietf.org>; Mon, 20 Oct 2014 13:04:11 -0700 (PDT)
Received: from h200.viagenie.ca (h200.viagenie.ca [206.123.31.200]) by jazz.viagenie.ca (Postfix) with ESMTPSA id 5E922410E8; Mon, 20 Oct 2014 16:04:10 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_303F9009-2392-42B6-8CE4-8742BC5BACBB"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Adoption call of draft-gont-6man-deprecate-atomfrag-generation for 6MAN
From: JF Tremblay <jean-francois.tremblay@viagenie.ca>
In-Reply-To: <543C2797.8030607@gmail.com>
Date: Mon, 20 Oct 2014 16:04:08 -0400
Message-Id: <44E91414-B4D6-4F34-8BA3-BAADC2BBD5D1@viagenie.ca>
References: <2742D96E-1538-4ECF-BB3A-6A194D9DBB96@employees.org> <alpine.DEB.2.02.1410130914060.14735@uplift.swm.pp.se> <543C2797.8030607@gmail.com>
To: 6man WG <ipv6@ietf.org>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/W0uzX95nRwF7MMkPji7Z1hDwd8Y
Cc: 6man Chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 20 Oct 2014 20:04:13 -0000

--Apple-Mail=_303F9009-2392-42B6-8CE4-8742BC5BACBB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252


On Oct 13, 2014, at 3:27 PM, Brian E Carpenter =
<brian.e.carpenter@gmail.com> wrote:

> On 13/10/2014 20:15, Mikael Abrahamsson wrote:
>> On Mon, 13 Oct 2014, Ole Troan wrote:
>>=20
>>> All,
>>>=20
>>> The authors have requested an adoption call for this document as a
>>> standards track document.
>>>=20
>>> Please provide a view with reasons as to whether the WG should adopt
>>> this or not.
>>=20
>> I support that we're taking a good look at this problem.
>=20
> Yes. This is (another) case where our standards allow bad things
> to happen, so we should try to fix it, and I think this draft
> heads in the direction of a fix.
>=20
>   Brian


I second this, and support adoption of this document by the wg.=20

Btw, is it usual to have a wg adoption call over one week only? Just =
wondering.=20

-------------------
To the authors:=20

The following sentence in section 3, page 3, struck me as weirdly =
constructed.=20

 Once the attack packet has been fired, it
   will be the aforementioned routers themselves the ones dropping their
   own traffic.

Beside behing fairly hard to parse, I=92m not sure it=92s right. If only =
inbound ACLs are configured to drop atomic fragments, the packets might =
not get dropped locally, if this was the intended meaning.

JF
=20=

--Apple-Mail=_303F9009-2392-42B6-8CE4-8742BC5BACBB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div =
apple-content-edited=3D"true"><br></div><div><div>On Oct 13, 2014, at =
3:27 PM, Brian E Carpenter &lt;<a =
href=3D"mailto:brian.e.carpenter@gmail.com">brian.e.carpenter@gmail.com</a=
>&gt; wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite">On 13/10/2014 20:15, Mikael Abrahamsson =
wrote:<br><blockquote type=3D"cite">On Mon, 13 Oct 2014, Ole Troan =
wrote:<br><br><blockquote type=3D"cite">All,<br><br>The authors have =
requested an adoption call for this document as a<br>standards track =
document.<br><br>Please provide a view with reasons as to whether the WG =
should adopt<br>this or not.<br></blockquote><br>I support that we're =
taking a good look at this problem.<br></blockquote><br>Yes. This is =
(another) case where our standards allow bad things<br>to happen, so we =
should try to fix it, and I think this draft<br>heads in the direction =
of a fix.<br><br> =
&nbsp;&nbsp;Brian<br></blockquote></div><br><div><br></div><div>I second =
this, and support adoption of this document by the =
wg.&nbsp;</div><div><br></div><div>Btw, is it usual to have a wg =
adoption call over one week only? Just =
wondering.&nbsp;</div><div><br></div><div>-------------------</div><div>To=
 the authors:&nbsp;</div><div><br></div><div>The following sentence in =
section 3, page 3, struck me as weirdly =
constructed.&nbsp;</div><div><br></div><div><pre class=3D"newpage" =
style=3D"font-size: 1em; margin-top: 0px; margin-bottom: 0px; =
page-break-before: always;"> Once the attack packet has been fired, it
   will be the aforementioned routers themselves the ones dropping their
   own traffic.</pre><div><br></div></div><div>Beside behing fairly hard =
to parse, I=92m not sure it=92s right. If only inbound ACLs are =
configured to drop atomic fragments, the packets might not get dropped =
locally, if this was the intended =
meaning.</div><div><br></div><div>JF</div><div>&nbsp;</div></body></html>=

--Apple-Mail=_303F9009-2392-42B6-8CE4-8742BC5BACBB--


From nobody Mon Oct 20 15:34:45 2014
Return-Path: <randy@psg.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 608F51ACF87 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 15:34:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 qZPfcAyOt19c for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 15:34:43 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2B5841ACE99 for <ipv6@ietf.org>; Mon, 20 Oct 2014 15:34:43 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1XgLXC-00073S-HW; Mon, 20 Oct 2014 22:34:38 +0000
Date: Tue, 21 Oct 2014 07:34:36 +0900
Message-ID: <m2r3y274lf.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
In-Reply-To: <54455C53.9080004@gmail.com>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <543BE567.50509@gmail.com> <543C2D08.5080204@gmail.com> <m2egu28zn4.wl%randy@psg.com> <54455C53.9080004@gmail.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/fJBm7NAnqh_zv6r5moMMbR0MGmE
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 20 Oct 2014 22:34:44 -0000

>>> I suspect the reason for the lack of replies is that people don't
>>> think it's necessary to publish a new standards track RFC for this.
>> sadly, the whack-a-mole of short compares is very much alive
> Ack. So is an RFC going to help? (Not being sarcastic: it's a genuine
> question.)

first, do no harm

and yes a very simple clear statement will help

randy


From nobody Mon Oct 20 15:59:04 2014
Return-Path: <randy@psg.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 103021ACF99 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 15:59:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 lVOX3mMJIQ_J for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 15:59:02 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE3C01ACF5E for <ipv6@ietf.org>; Mon, 20 Oct 2014 15:59:01 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1XgLum-0007Cp-6q; Mon, 20 Oct 2014 22:59:00 +0000
Date: Tue, 21 Oct 2014 07:58:57 +0900
Message-ID: <m2lhoa73gu.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ole Troan <otroan@employees.org>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
In-Reply-To: <3818C3F8-3B40-4801-9A3C-B2BA4C1056D1@employees.org>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <m2fvei8zp7.wl%randy@psg.com> <3818C3F8-3B40-4801-9A3C-B2BA4C1056D1@employees.org>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/JjPImeOLFZrEc4wkMEoCuzUkXDU
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 20 Oct 2014 22:59:03 -0000

>> yikes.  that would be a damned shame.  this is a simple doc, to the
>> point, and sadly seems to be needed.
> please explain.

[ omg, i need to justify my clearly stated opinion.  because it goes
  against two decades of ipv6 ivory towerism? ]

for example:

i know this will be hard to believe in this wonderous day and age of
universal ipv6 deployment, but some vendors actually go around the tcam
twice for long prefixes, creating a non-trivial performance penalty.
some take the slow path.

and about once a month, this discussion swirls around ops groups.
"don't do this because vendor support may not exist or, if it does, it
sucks."

the current documentation is muddy, possibly related to years of muddy
thinking on this issue.  a simple statement making it unequivocally
clear would be quite helpful.

randy


From nobody Mon Oct 20 16:30:25 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06FB71ACE4F for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 16:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.041
X-Spam-Level: *
X-Spam-Status: No, score=1.041 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DATE_IN_PAST_06_12=1.543, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=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 P9_PSKLJ0U8B for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 16:30:12 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B0FB1ACE8F for <ipv6@ietf.org>; Mon, 20 Oct 2014 16:30:09 -0700 (PDT)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1XgMOo-0007Zp-4z; Tue, 21 Oct 2014 01:30:02 +0200
Message-ID: <54454517.4070000@si6networks.com>
Date: Mon, 20 Oct 2014 15:23:35 -0200
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Tom Taylor <tom.taylor.stds@gmail.com>,  Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk>, ipv6@ietf.org
Subject: Re: question on ICMP error packets, RFC 4443, 2.4 e)
References: <CAPunWhC-ceaSgKXF2qGQPXuRhc9+v0bYt5NRS+tH2WHCH0z_BQ@mail.gmail.com> <544440F3.5010309@gmail.com>
In-Reply-To: <544440F3.5010309@gmail.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/2Icn3x6AI7hj73kbpfp-TN6B-QA
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 20 Oct 2014 23:30:14 -0000

Hi, Tom,

On 10/19/2014 08:53 PM, Tom Taylor wrote:
> The basic principle is that you never answer an error with an error, or
> you could generate an infinite loop.

Agreed. That said, I recall a system generating ICMPv6 unreachables in
response to some ICMPv6 error messages (I guess the router in question
just didn't bother to check the message type, and sent the error message
rightaway).

However, at least in theory, ICMPv6 error could use IPv6 EHs.. at which
point the obvious question arises "Can we really require routers to
figure out what's the ICMP message type?"

Thanks,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492





From nobody Mon Oct 20 16:57:14 2014
Return-Path: <randy@psg.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E16191ACEEC for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 16:57:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 a7JrOKFFEpL8 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 16:57:11 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B849F1ACF69 for <ipv6@ietf.org>; Mon, 20 Oct 2014 16:57:11 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1XgMp4-0007XB-1X; Mon, 20 Oct 2014 23:57:10 +0000
Date: Tue, 21 Oct 2014 08:57:08 +0900
Message-ID: <m2bnp670rv.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Ole Troan <otroan@employees.org>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
In-Reply-To: <m2lhoa73gu.wl%randy@psg.com>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <m2fvei8zp7.wl%randy@psg.com> <3818C3F8-3B40-4801-9A3C-B2BA4C1056D1@employees.org> <m2lhoa73gu.wl%randy@psg.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/UNAasX7qL-0La6kIcsjY45X9qxU
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 20 Oct 2014 23:57:13 -0000

[ rant continues ]

just to be a bit clearer.  to me, slaac is a misspelling of a well known
accelerator north of palo attitude.  you want a full on colonoscopy from
a traceroute through my network?

and an enterprise is used to far more control, i.e. dhcp.  but the ietf
faught against dhcpv4 [0], so this is a long story.  look at how long
and hard we denied nats, and how well that worked out.

otoh, slaac might work in most home invironments.  or mobile phones.

randy

--

[0] - would not allow/provide dhcp on the ietf meeting network.  so in
      stockholm, i ran a dhcp server on my laptop in the corner of the
      terminal room.  and that was the end of that.


From nobody Mon Oct 20 17:05:46 2014
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 758D91ACF91 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 17:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 C9PKdjplPGnF for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 17:05:42 -0700 (PDT)
Received: from mail-pd0-x22a.google.com (mail-pd0-x22a.google.com [IPv6:2607:f8b0:400e:c02::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B69CC1ACF8F for <ipv6@ietf.org>; Mon, 20 Oct 2014 17:05:42 -0700 (PDT)
Received: by mail-pd0-f170.google.com with SMTP id z10so136143pdj.1 for <ipv6@ietf.org>; Mon, 20 Oct 2014 17:05:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=3bLyaJUtLNyYFGz9sYuRprEiXo3TUFRXaOdCj6aBjEY=; b=KLWb6EQL79C/MyFyc9vYqq/XvLTDPud8iqk4Eww9KDZ5fY73K6yolEH2A/3tEUOPop WH7Bfn4SgbjJr0uQ8BB5N2mIXtHsz+v8b5BiHnfWHNfS6XQJZA+Nd2diM0+b+ubnIxoI wwkAiiqHnAJhgNtWkqBFFju7jILqAtHbiTE4CxdwbH2nx1fqGNPrT53EoBhhluR3NNfS m3ohKbwDFoeDX1SVyCO3mfnePyUtE8XS2Vc7rsB0xz84F4gKjPHHmsCk1Opi2zSrVMoa VAzWrTl82jaGrUWP+7/KTMeI9E9ocXTODzZNcnbHXSebeVz8/QVLlzZAshwggiI5tNqP yn8w==
X-Received: by 10.66.90.230 with SMTP id bz6mr6849517pab.125.1413849942248; Mon, 20 Oct 2014 17:05:42 -0700 (PDT)
Received: from [172.24.24.171] (wireless-nat-20.auckland.ac.nz. [130.216.30.131]) by mx.google.com with ESMTPSA id yk3sm10115246pbb.60.2014.10.20.17.05.37 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 20 Oct 2014 17:05:41 -0700 (PDT)
Message-ID: <5445A355.2080803@gmail.com>
Date: Tue, 21 Oct 2014 13:05:41 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Randy Bush <randy@psg.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org>	<511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org>	<543BE567.50509@gmail.com>	<543C2D08.5080204@gmail.com>	<m2egu28zn4.wl%randy@psg.com>	<54455C53.9080004@gmail.com> <m2r3y274lf.wl%randy@psg.com>
In-Reply-To: <m2r3y274lf.wl%randy@psg.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/AfhvC99063DmaFXU9MrHpjiAihQ
Cc: "<6man-chairs@tools.ietf.org>" <6man-chairs@tools.ietf.org>, Alexandru Petrescu <alexandru.petrescu@gmail.com>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 21 Oct 2014 00:05:44 -0000

On 21/10/2014 11:34, Randy Bush wrote:
>>>> I suspect the reason for the lack of replies is that people don't
>>>> think it's necessary to publish a new standards track RFC for this.
>>> sadly, the whack-a-mole of short compares is very much alive
>> Ack. So is an RFC going to help? (Not being sarcastic: it's a genuine
>> question.)
> 
> first, do no harm
> 
> and yes a very simple clear statement will help

OK, I will +1 for WG adoption then.

   Brian


From nobody Mon Oct 20 17:25:53 2014
Return-Path: <slblake@petri-meat.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C73D61ACF5F for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 17:25:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.101
X-Spam-Level: 
X-Spam-Status: No, score=-0.101 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham
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 KICEMwgKgCri for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 17:25:49 -0700 (PDT)
Received: from elom.tchmachines.com (elom.tchmachines.com [208.76.80.198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 202921ACE74 for <ipv6@ietf.org>; Mon, 20 Oct 2014 17:25:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=petri-meat.com; s=default;  h=Content-Transfer-Encoding:Mime-Version:Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID; bh=m8OBE1EgZHwTMUbbiKPmTzss+sMadcIbL9E2wFabdkY=;  b=NZ2Rp9aABq6l9F/P+qAWrppB6j4xaJzYM6nBK3TDvA5hAntRsHYTB4NC/BY4FqHczrVZgdO8UDdIB/OPOrQKBjpmexdGYAC5AJLd47qZkt6ArNMeOyg6N1228PtBB+z3;
Received: from cpe-098-027-048-172.nc.res.rr.com ([98.27.48.172]:53779 helo=[192.168.144.57]) by elom.tchmachines.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from <slblake@petri-meat.com>) id 1XgNGe-0004QB-34; Mon, 20 Oct 2014 20:25:40 -0400
Message-ID: <1413851147.25177.4.camel@tachyon.blake>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
From: Steven Blake <slblake@petri-meat.com>
To: Randy Bush <randy@psg.com>
Date: Mon, 20 Oct 2014 20:25:47 -0400
In-Reply-To: <m2lhoa73gu.wl%randy@psg.com>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <m2fvei8zp7.wl%randy@psg.com> <3818C3F8-3B40-4801-9A3C-B2BA4C1056D1@employees.org> <m2lhoa73gu.wl%randy@psg.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.6.4 (3.6.4-3.fc18) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - elom.tchmachines.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - petri-meat.com
X-Get-Message-Sender-Via: elom.tchmachines.com: authenticated_id: slblake+petri-meat.com/only user confirmed/virtual account not confirmed
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/yRCBBvaYYoYAjz1aGaKncTzkj-g
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 21 Oct 2014 00:25:51 -0000

On Tue, 2014-10-21 at 07:58 +0900, Randy Bush wrote:
> >> yikes.  that would be a damned shame.  this is a simple doc, to the
> >> point, and sadly seems to be needed.
> > please explain.
> 
> [ omg, i need to justify my clearly stated opinion.  because it goes
>   against two decades of ipv6 ivory towerism? ]
> 
> for example:
> 
> i know this will be hard to believe in this wonderous day and age of
> universal ipv6 deployment, but some vendors actually go around the tcam
> twice for long prefixes, creating a non-trivial performance penalty.
> some take the slow path.

And an IETF document will change this?

There is no free lunch.  Tradeoff is FIB prefix capacity vs. lookup
rate/latency vs. $$.  TCAMs are hot & !cheap.

// Steve


From nobody Mon Oct 20 17:28:39 2014
Return-Path: <randy@psg.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 670DA1ACE8F for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 17:28:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 S4gRHghIpP_0 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 17:28:37 -0700 (PDT)
Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:8006::18]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 087F61ACE74 for <ipv6@ietf.org>; Mon, 20 Oct 2014 17:28:37 -0700 (PDT)
Received: from localhost ([127.0.0.1] helo=ryuu.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.82) (envelope-from <randy@psg.com>) id 1XgNJT-0007pK-2F; Tue, 21 Oct 2014 00:28:35 +0000
Date: Tue, 21 Oct 2014 09:28:32 +0900
Message-ID: <m24muy6zbj.wl%randy@psg.com>
From: Randy Bush <randy@psg.com>
To: Steven Blake <slblake@petri-meat.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
In-Reply-To: <1413851147.25177.4.camel@tachyon.blake>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <m2fvei8zp7.wl%randy@psg.com> <3818C3F8-3B40-4801-9A3C-B2BA4C1056D1@employees.org> <m2lhoa73gu.wl%randy@psg.com> <1413851147.25177.4.camel@tachyon.blake>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue")
Content-Type: text/plain; charset=US-ASCII
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/gnkvwzsPEHnRf42AdjvJ15gHBCg
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 21 Oct 2014 00:28:38 -0000

> There is no free lunch.  Tradeoff is FIB prefix capacity vs. lookup
> rate/latency vs. $$.  TCAMs are hot & !cheap.

thanks for your email from the mid-'90s cidr wars.  it reminds me of the
ethernet vendors explaining why 100mb, no 1g, no 10g, no 100g, is too
expensive.

randy


From nobody Mon Oct 20 17:37:26 2014
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 103131ACE81 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 17:37:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 k6X0oXJqEAwk for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 17:37:20 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 431C51A1A62 for <ipv6@ietf.org>; Mon, 20 Oct 2014 17:37:20 -0700 (PDT)
Received: from cl-1071.udi-01.br.sixxs.net ([2001:1291:200:42e::2]) by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fernando@gont.com.ar>) id 1XgNRt-0007mR-SP; Tue, 21 Oct 2014 02:37:18 +0200
Message-ID: <5445AA5E.1040301@gont.com.ar>
Date: Mon, 20 Oct 2014 21:35:42 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
To: Steven Blake <slblake@petri-meat.com>, Randy Bush <randy@psg.com>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <m2fvei8zp7.wl%randy@psg.com> <3818C3F8-3B40-4801-9A3C-B2BA4C1056D1@employees.org> <m2lhoa73gu.wl%randy@psg.com> <1413851147.25177.4.camel@tachyon.blake>
In-Reply-To: <1413851147.25177.4.camel@tachyon.blake>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/BDWQUcVDD-vvHgcKJJ9q2XP_B6I
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 21 Oct 2014 00:37:23 -0000

On 10/20/2014 09:25 PM, Steven Blake wrote:
> On Tue, 2014-10-21 at 07:58 +0900, Randy Bush wrote:
>>>> yikes.  that would be a damned shame.  this is a simple doc, to the
>>>> point, and sadly seems to be needed.
>>> please explain.
>>
>> [ omg, i need to justify my clearly stated opinion.  because it goes
>>   against two decades of ipv6 ivory towerism? ]
>>
>> for example:
>>
>> i know this will be hard to believe in this wonderous day and age of
>> universal ipv6 deployment, but some vendors actually go around the tcam
>> twice for long prefixes, creating a non-trivial performance penalty.
>> some take the slow path.
> 
> And an IETF document will change this?

One could expect that if a clear statement is made on the topic, this
might make a difference for e.g. compliance suites?

Thanks,
-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Mon Oct 20 18:22:15 2014
Return-Path: <slblake@petri-meat.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 461041ACE25 for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 18:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1] autolearn=ham
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 PhxEjUyEXL3c for <ipv6@ietfa.amsl.com>; Mon, 20 Oct 2014 18:22:12 -0700 (PDT)
Received: from elom.tchmachines.com (elom.tchmachines.com [208.76.80.198]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C598F1A1A62 for <ipv6@ietf.org>; Mon, 20 Oct 2014 18:22:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=petri-meat.com; s=default;  h=Content-Transfer-Encoding:Mime-Version:Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID; bh=bplqIMxgS2o3HdFuq/f4//vZicm5WEmvmGehVkXewDg=;  b=zM7nyTcdMN+SKiD1AmGlfLG098UpTRc9agwBQSsH/KML5WrHUs5bIRKuOYphsfqRKcKOxsmkfvGICHv5HBmxZfWAXE+SkD6xN0kZ/aqvRIsTOUeblFNWcB+8Z88IN0ty;
Received: from cpe-098-027-048-172.nc.res.rr.com ([98.27.48.172]:53834 helo=[192.168.144.57]) by elom.tchmachines.com with esmtpsa (TLSv1:DHE-RSA-AES256-SHA:256) (Exim 4.82) (envelope-from <slblake@petri-meat.com>) id 1XgO9C-00040w-80; Mon, 20 Oct 2014 21:22:02 -0400
Message-ID: <1413854529.25177.25.camel@tachyon.blake>
Subject: Re: Adoption call of draft-boucadair-6man-prefix-routing-reco for 6MAN
From: Steven Blake <slblake@petri-meat.com>
To: Fernando Gont <fernando@gont.com.ar>
Date: Mon, 20 Oct 2014 21:22:09 -0400
In-Reply-To: <5445AA5E.1040301@gont.com.ar>
References: <1D964922-16F1-46C7-86D7-515F3A136904@employees.org> <511A0743-3331-4B6F-80D3-7EECF0DEB686@employees.org> <m2fvei8zp7.wl%randy@psg.com> <3818C3F8-3B40-4801-9A3C-B2BA4C1056D1@employees.org> <m2lhoa73gu.wl%randy@psg.com> <1413851147.25177.4.camel@tachyon.blake> <5445AA5E.1040301@gont.com.ar>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.6.4 (3.6.4-3.fc18) 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - elom.tchmachines.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - petri-meat.com
X-Get-Message-Sender-Via: elom.tchmachines.com: authenticated_id: slblake+petri-meat.com/only user confirmed/virtual account not confirmed
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/fL6kLP23E-2YaGGndlcZyj8IGS8
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 21 Oct 2014 01:22:14 -0000

On Mon, 2014-10-20 at 21:35 -0300, Fernando Gont wrote:
> On 10/20/2014 09:25 PM, Steven Blake wrote:
> > On Tue, 2014-10-21 at 07:58 +0900, Randy Bush wrote:
> >>>> yikes.  that would be a damned shame.  this is a simple doc, to the
> >>>> point, and sadly seems to be needed.
> >>> please explain.
> >>
> >> [ omg, i need to justify my clearly stated opinion.  because it goes
> >>   against two decades of ipv6 ivory towerism? ]
> >>
> >> for example:
> >>
> >> i know this will be hard to believe in this wonderous day and age of
> >> universal ipv6 deployment, but some vendors actually go around the tcam
> >> twice for long prefixes, creating a non-trivial performance penalty.
> >> some take the slow path.
> > 
> > And an IETF document will change this?
> 
> One could expect that if a clear statement is made on the topic, this
> might make a difference for e.g. compliance suites?
> 
> Thanks,

Compliance to what?  The complaint was not about allowed prefix lengths,
it was about forwarding performance.

Here is the meat of draft-boucadair-6man-prefix-routing-reco-03:

---

2.  Recommendation

   Forwarding decision-making processes MUST NOT restrict by design the
   length of IPv6 prefixes.  In particular, forwarding processes MUST be
   designed to process prefixes of any length up to /128, by increments
   of 1.

   Obviously, policies can be enforced to restrict the length of IP
   prefixes advertised within a given domain or in a given
   interconnection link.  These policies are deployment-specific and/or
   driven by administrative (interconnection) considerations.

   This recommendation does not conflict with the 64-bit boundary
   involved when IPv6 stateless address autoconfiguration (SLAAC,
   [RFC4862]) is used on links such as Ethernet [RFC2464].

   Some lookup algorithm implementations (find the prefix matching a
   given destination address) may be affected by this recommendation,
   even more so for IPv6 than IPv4.  The performance of some
   implementations may be degraded when prefix lengths are longer than
   /64.

---

How is *this recommendation* going to dissuade a vendor from
implementing an algorithm that is "faster" for <= 64-bit prefixes,
especially if it allows greater total prefix capacity or lower
cost/power?


Regards,

// Steve


From nobody Tue Oct 21 00:03:33 2014
Return-Path: <chenycmx@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E88C51A6FC1 for <ipv6@ietfa.amsl.com>; Tue, 21 Oct 2014 00:03:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 X3gqVC_ZIt-J for <ipv6@ietfa.amsl.com>; Tue, 21 Oct 2014 00:03:28 -0700 (PDT)
Received: from mail-pd0-x22e.google.com (mail-pd0-x22e.google.com [IPv6:2607:f8b0:400e:c02::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 105E41AD084 for <ipv6@ietf.org>; Tue, 21 Oct 2014 00:03:26 -0700 (PDT)
Received: by mail-pd0-f174.google.com with SMTP id y13so730638pdi.5 for <ipv6@ietf.org>; Tue, 21 Oct 2014 00:03:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=date:from:to:cc:reply-to:subject:mime-version:message-id :content-type:content-transfer-encoding; bh=s8LfUzGjBj/nSkreOc+j1Ud/28YoGsmVWGJcFgjVtZE=; b=BrF+7xQuzPiHAl7G6eD9cPypl9N1tm0i4F4RzhXigu20nxPi0JhXNS+Vtr23GSXQtk LPbSKZSFLyIqBNPtf9S2MfQZLpRT1vkv2hLkUFxnIt21hOYAVC/3ykLFf59pRiBYHm5D sP+m6yuUdypb/4iv+pbO8ktQA3m34xKW/H4RelkeOsnTJsc0Oa7Z/+u62lp/Y2C8VNCX kE21217X78RZqz203kAoDJe6nMYijmC9MUFPMS5NSJgjcMZ7wskCcQpHDaLfHTkKQk8i rRhjxeiKgEc8YzrTLqT2UlIgD9s6L6nLwpDCbGcHTylYM4CM5H9TpseG9bCVjVsI7Sed LtYw==
X-Received: by 10.66.219.38 with SMTP id pl6mr32599293pac.43.1413875005999; Tue, 21 Oct 2014 00:03:25 -0700 (PDT)
Received: from netlab-PC ([166.111.68.231]) by mx.google.com with ESMTPSA id fk10sm10980900pdb.49.2014.10.21.00.03.21 for <multiple recipients> (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 21 Oct 2014 00:03:25 -0700 (PDT)
Date: Tue, 21 Oct 2014 15:03:18 +0800
From: "Yuchi Chen" <chenycmx@gmail.com>
To: ipv6 <ipv6@ietf.org>
Subject: Re: Adoption call of draft-gont-6man-deprecate-atomfrag-generation for 6MAN
X-Priority: 3
X-GUID: B22AB327-9635-4A88-850D-58D96E804022
X-Has-Attach: no
X-Mailer: Foxmail 7.0.1.92[cn]
Mime-Version: 1.0
Message-ID: <2014102115031429842116@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/GsJ7eWpt6azmK5uSlt5z_PVjpjY
Cc: 6man-chairs <6man-chairs@tools.ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: chenycmx <chenycmx@gmail.com>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 21 Oct 2014 07:03:31 -0000

SGkgYWxsLA0KDQpJIHN1cHBvcnQgdGhlIGFkb3B0aW9uIG9mIHRoZSBkcmFmdCAoc29ycnkgaWYg
dGhpcyBtZXNzYWdlIGlzIGxhdGUpLg0KDQpPbmUgc3VzcGVjdGVkIHR5cG8gOiBJbiBzZWN0aW9u
IDYgKG9uIHBhZ2UgOCksIGl0IHNlZW1zIHRoYXQgdGhlIHBhcmFncmFwaCANCicgSWYgdGhlcmUg
aXMgYSBuZWVkIHRvIGFkZCBhIEZyYWdtZW50IEhlYWRlciAodGhlIHBhY2tldCBpcyBhIGZyYWdt
ZW50KSwgdGhlIGhlYWRlciANCmZpZWxkcyBhcmUgc2V0IGFzIGFib3ZlIHdpdGggdGhlIGZvbGxv
d2luZyBleGNlcHRpb25zOicgaGFzIGEgZGlmZmVyZW50IGluZGVudGF0aW9uIHN0eWxlIA0KZnJv
bSB0aGUgcmVzdCBvZiB0aGUgcGFyYWdyYXBoLiBJcyB0aGVyZSBhbnkgcGFydGljdWxhciByZWFz
b24/DQoNCkJlc3QgcmVnYXJkcyENCi0tLS0tLS0tLS0tLS0tDQpZdWNoaSBDaGVuDQoNCg0KLS0t
LS0tLS0gRm9yd2FyZGVkIE1lc3NhZ2UgLS0tLS0tLS0NClN1YmplY3Q6IEFkb3B0aW9uIGNhbGwg
b2YgZHJhZnQtZ29udC02bWFuLWRlcHJlY2F0ZS1hdG9tZnJhZy1nZW5lcmF0aW9uDQpmb3IgNk1B
Tg0KRGF0ZTogTW9uLCAxMyBPY3QgMjAxNCAwODozMDoxOCArMDIwMA0KRnJvbTogT2xlIFRyb2Fu
IDxvdHJvYW5AZW1wbG95ZWVzLm9yZz4NClRvOiA2bWFuIFdHIDxpcHY2QGlldGYub3JnPg0KQ0M6
IDZtYW4gQ2hhaXJzIDw2bWFuLWNoYWlyc0B0b29scy5pZXRmLm9yZz4NCiANCkFsbCwNCiANClRo
ZSBhdXRob3JzIGhhdmUgcmVxdWVzdGVkIGFuIGFkb3B0aW9uIGNhbGwgZm9yIHRoaXMgZG9jdW1l
bnQgYXMgYSBzdGFuZGFyZHMgdHJhY2sgZG9jdW1lbnQuDQogDQpQbGVhc2UgcHJvdmlkZSBhIHZp
ZXcgd2l0aCByZWFzb25zIGFzIHRvIHdoZXRoZXIgdGhlIFdHIHNob3VsZCBhZG9wdCB0aGlzIG9y
IG5vdC4NCiANClRoaXMgbWVzc2FnZSBzdGFydHMgYSBvbmUgd2VlayA2TUFOIFdvcmtpbmcgR3Jv
dXAgY2FsbCBvbiBhZG9wdGluZzoNCiANClRpdGxlICAgICAgICAgICA6IERlcHJlY2F0aW5nIHRo
ZSBHZW5lcmF0aW9uIG9mIElQdjYgQXRvbWljIEZyYWdtZW50cw0KQXV0aG9yKHMpICAgIDogRi4g
R29udCwgVy4gTGl1DQpGaWxlbmFtZSAgICA6IGRyYWZ0LWdvbnQtNm1hbi1kZXByZWNhdGUtYXRv
bWZyYWctZ2VuZXJhdGlvbi0wMA0KUGFnZXMgICAgICAgIDogNg0KRGF0ZSAgICAgICAgICA6IDIw
MTQtMDgtMTkNCiANCmh0dHA6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWdvbnQtNm1hbi1k
ZXByZWNhdGUtYXRvbWZyYWctZ2VuZXJhdGlvbi0wMA0KIA0KVGhlIGNhbGwgZW5kcyBvbiBPY3Rv
YmVyIDIwdGgsIDIwMTQuDQogDQpSZWdhcmRzLA0KIA0KQm9iIEhpbmRlbiAmIE9sZSBUcsO4YW4N
CiANCiANCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tDQpJRVRGIElQdjYgd29ya2luZyBncm91cCBtYWlsaW5nIGxpc3QN
CmlwdjZAaWV0Zi5vcmcNCkFkbWluaXN0cmF0aXZlIFJlcXVlc3RzOiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2lwdjYNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQogDQotLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0K
SUVURiBJUHY2IHdvcmtpbmcgZ3JvdXAgbWFpbGluZyBsaXN0DQppcHY2QGlldGYub3JnDQpBZG1p
bmlzdHJhdGl2ZSBSZXF1ZXN0czogaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9pcHY2DQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLQ0KIA==


From nobody Tue Oct 21 00:43:17 2014
Return-Path: <ot@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FCF41AD080 for <ipv6@ietfa.amsl.com>; Tue, 21 Oct 2014 00:43:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.235
X-Spam-Level: 
X-Spam-Status: No, score=-1.235 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_SOFTFAIL=0.665] autolearn=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 AX1u6ueKeVj6 for <ipv6@ietfa.amsl.com>; Tue, 21 Oct 2014 00:43:10 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [198.137.202.19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAECD1AD0A3 for <ipv6@ietf.org>; Tue, 21 Oct 2014 00:43:10 -0700 (PDT)
Received: from [192.168.10.6] (unknown [195.159.143.154]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id B86AA61C5; Tue, 21 Oct 2014 00:43:08 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
Subject: Re: Adoption call of draft-gont-6man-deprecate-atomfrag-generation for 6MAN
From: Ole Troan <ot@cisco.com>
In-Reply-To: <44E91414-B4D6-4F34-8BA3-BAADC2BBD5D1@viagenie.ca>
Date: Tue, 21 Oct 2014 09:43:06 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7AB8357A-53FA-42A5-8673-15C8F855B315@cisco.com>
References: <2742D96E-1538-4ECF-BB3A-6A194D9DBB96@employees.org> <alpine.DEB.2.02.1410130914060.14735@uplift.swm.pp.se> <543C2797.8030607@gmail.com> <44E91414-B4D6-4F34-8BA3-BAADC2BBD5D1@viagenie.ca>
To: JF Tremblay <jean-francois.tremblay@viagenie.ca>
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/_TnytFqsBnK3-lygsF59-YgaSIc
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 21 Oct 2014 07:43:15 -0000

JF,

>> On 13/10/2014 20:15, Mikael Abrahamsson wrote:
>>> On Mon, 13 Oct 2014, Ole Troan wrote:
>>>=20
>>>> All,
>>>>=20
>>>> The authors have requested an adoption call for this document as a
>>>> standards track document.
>>>>=20
>>>> Please provide a view with reasons as to whether the WG should =
adopt
>>>> this or not.
>>>=20
>>> I support that we're taking a good look at this problem.
>>=20
>> Yes. This is (another) case where our standards allow bad things
>> to happen, so we should try to fix it, and I think this draft
>> heads in the direction of a fix.
>>=20
>>   Brian
>=20
>=20
> I second this, and support adoption of this document by the wg.=20
>=20
> Btw, is it usual to have a wg adoption call over one week only? Just =
wondering.=20

the main question we're trying to get answered in an adoption call is =
"Is there strong working group support for working on the draft?".=20

we often let the discussion run over the dead-line if required. and =
there is as you have seen ample opportunity to argue over the chair's =
judgement of what consensus is afterwards.

in this case we wanted to run through about 4 adoption calls in series, =
if others think one week is too short as well, I'm sure we can do two =
weeks calls in the future.

cheers,
Ole



>=20
> -------------------
> To the authors:=20
>=20
> The following sentence in section 3, page 3, struck me as weirdly =
constructed.=20
>=20
>  Once the attack packet has been fired, it
>    will be the aforementioned routers themselves the ones dropping =
their
>    own traffic.
>=20
>=20
> Beside behing fairly hard to parse, I=92m not sure it=92s right. If =
only inbound ACLs are configured to drop atomic fragments, the packets =
might not get dropped locally, if this was the intended meaning.
>=20
> JF
> =20
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------


From nobody Tue Oct 21 03:39:28 2014
Return-Path: <bingxuere@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9C5C91A03A6 for <ipv6@ietfa.amsl.com>; Tue, 21 Oct 2014 03:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 49dNoSETc-2n for <ipv6@ietfa.amsl.com>; Tue, 21 Oct 2014 03:39:22 -0700 (PDT)
Received: from mail-yh0-x236.google.com (mail-yh0-x236.google.com [IPv6:2607:f8b0:4002:c01::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C4A7A1A01BA for <ipv6@ietf.org>; Tue, 21 Oct 2014 03:39:22 -0700 (PDT)
Received: by mail-yh0-f54.google.com with SMTP id 29so1286554yhl.13 for <ipv6@ietf.org>; Tue, 21 Oct 2014 03:39:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ZzRrzPCf0SHwob7HwH6THGLMKzZ7fGDjUXjwQDTzRKs=; b=jYXfgdDpBih0XrV8hUstW0E49ypH0tTx+dWY7zXceFmeBAbV5YhTgdpTMZqeCGKudf UlJiwDgeigZZicy1Gwn4KVL+XzGAKnm/MrUPVbVaI3KmY6PksDcp47+NPz1EtV+gtBIN hcWONjzzQvvZPxfyjq2atyFHtwT81qWJcB8/E+Xmk+5TrGeF+MKtm7xYubpmsLQX5Xre R6FWWpuxnposVsSq62DO/BuJREdSQPdYt/U3mLG6SL0WHsAau1FJyfIIoodVKGTyE2ml 1O78JUsJpx2QBOlkbW4e+NzA1r+d/ONPZ1Mc+B//11trE79tPUVVPHSBEr8sWf+cEhW/ WO8Q==
X-Received: by 10.236.222.198 with SMTP id t66mr13556974yhp.125.1413887962008;  Tue, 21 Oct 2014 03:39:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.170.111.211 with HTTP; Tue, 21 Oct 2014 03:38:41 -0700 (PDT)
In-Reply-To: <7AB8357A-53FA-42A5-8673-15C8F855B315@cisco.com>
References: <2742D96E-1538-4ECF-BB3A-6A194D9DBB96@employees.org> <alpine.DEB.2.02.1410130914060.14735@uplift.swm.pp.se> <543C2797.8030607@gmail.com> <44E91414-B4D6-4F34-8BA3-BAADC2BBD5D1@viagenie.ca> <7AB8357A-53FA-42A5-8673-15C8F855B315@cisco.com>
From: Qiong <bingxuere@gmail.com>
Date: Tue, 21 Oct 2014 18:38:41 +0800
Message-ID: <CAH3bfAD6bZ0oDMG_m-LL_CbnPz-6o03hY26qmO8cbhMW9_fRgg@mail.gmail.com>
Subject: Re: Adoption call of draft-gont-6man-deprecate-atomfrag-generation for 6MAN
To: "ipv6@ietf.org" <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary=001a11c2071cba518f0505ec71eb
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/h_yWKSm2aNbNaklKBgFp5Nbi1MU
Cc: 6man-chairs@tools.ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 21 Oct 2014 10:39:25 -0000

--001a11c2071cba518f0505ec71eb
Content-Type: text/plain; charset=UTF-8

Hi all,

I reviewed this draft and support adoption of this document as a wg draft.
Some comments below (editorial).
  Page 1, Abstract:
> The core IPv6 specification requires that when a host receives an
> ICMPv6 "Packet Too Big" message reporting a "Next-Hop MTU" smaller
> than 1280, the host includes a Fragment Header in all subsequent
 In IPv6, the corresponding field is called just "MTU".
  Page 2:
> Section 5 of [RFC2460] states that, when a host receives an ICMPv6
> "Packet Too Big" message [RFC4443] advertising a "Next-Hop MTU"
> smaller than 1280 (the minimum IPv6 MTU), the host is not required
> to
 Same as above.
 Page 3, Section 1:
> Section 6 formally
> updates RFC6145 such that it does not relies on the generation of
> IPv6 atomic fragments.
 Please replace "relies" with "rely".
 Page 6, Section 4:
> 3. ECMP routing [RFC2992] with more than one translator are employed
> for e.g., redundancy purposes
 Please replace "are" with "is".
 Page 11, Section 6:
> This approach allows Path MTU Discovery to operate end-to-end for
> paths whose MTU are not smaller than minimum IPv6 MTU of 1280 (which
> corresponds to MTU of 1260 in the IPv4 domain).
 Please replace "minimum IPv6 MTU" with "the minimum IPv6 MTU".


-- 
==============================================
Qiong Sun
China Telecom Beijing Research Institude


Open source code:
lightweight 4over6: *http://sourceforge.net/projects/laft6/
<http://sourceforge.net/projects/laft6/>*
PCP-natcoord:* http://sourceforge.net/projects/pcpportsetdemo/
<http://sourceforge.net/projects/pcpportsetdemo/> *
===============================================

--001a11c2071cba518f0505ec71eb
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all,<br><br>
<div>I reviewed this draft and support adoption of this document as a wg dr=
aft.=20
Some comments below (editorial).</div>
<div> </div>
<div> </div>
<div>Page 1, Abstract:</div>
<div>&gt;    The core IPv6 specification requires that when a host receives=
=20
an</div>
<div>&gt;    ICMPv6 &quot;Packet Too Big&quot; message reporting a &quot;Ne=
xt-Hop MTU&quot;=20
smaller</div>
<div>&gt;    than 1280, the host includes a Fragment Header in all=20
subsequent</div>
<div> </div>
<div>In IPv6, the corresponding field is called just &quot;MTU&quot;.</div>
<div> </div>
<div> </div>
<div>Page 2:</div>
<div>&gt;    Section 5 of [RFC2460] states that, when a host receives an=20
ICMPv6</div>
<div>&gt;    &quot;Packet Too Big&quot; message [RFC4443] advertising a &qu=
ot;Next-Hop=20
MTU&quot;</div>
<div>&gt;    smaller than 1280 (the minimum IPv6 MTU), the host is not requ=
ired=20
</div>
<div>&gt; to</div>
<div> </div>
<div>Same as above.</div>
<div> </div>
<div>Page 3, Section 1:</div>
<div>&gt; Section 6 formally</div>
<div>&gt;    updates RFC6145 such that it does not relies on the generation=
=20
of</div>
<div>&gt;    IPv6 atomic fragments.</div>
<div> </div>
<div>Please replace &quot;relies&quot; with &quot;rely&quot;.</div>
<div> </div>
<div>Page 6, Section 4:</div>
<div>&gt;    3.  ECMP routing [RFC2992] with more than one translator are=
=20
employed</div>
<div>&gt;        for e.g., redundancy purposes</div>
<div> </div>
<div>Please replace &quot;are&quot; with &quot;is&quot;.</div>
<div> </div>
<div>Page 11, Section 6:</div>
<div>&gt;     This approach allows Path MTU Discovery to operate end-to-end=
=20
for</div>
<div>&gt;     paths whose MTU are not smaller than minimum IPv6 MTU of 1280=
=20
(which</div>
<div>&gt;     corresponds to MTU of 1260 in the IPv4 domain). </div>
<div> </div>
<div>Please replace &quot;minimum IPv6 MTU&quot; with &quot;the minimum IPv=
6 MTU&quot;.<br><br><br>-- <br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D<br>Qiong Sun<br>China Telecom Beijing Research Instit=
ude<br><br><br>Open source code:<br>lightweight 4over6: <i><a href=3D"http:=
//sourceforge.net/projects/laft6/" target=3D"_blank">http://sourceforge.net=
/projects/laft6/</a></i><br>PCP-natcoord:<i> <a href=3D"http://sourceforge.=
net/projects/pcpportsetdemo/" target=3D"_blank">http://sourceforge.net/proj=
ects/pcpportsetdemo/</a> </i><br>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D<br></div>
<div> </div>
<div> </div>
<div> </div></div>

--001a11c2071cba518f0505ec71eb--


From nobody Tue Oct 21 07:36:13 2014
Return-Path: <sperreault@jive.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 026C61A6D3F for <ipv6@ietfa.amsl.com>; Tue, 21 Oct 2014 07:36:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level: 
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 x6bVMIQ0Libb for <ipv6@ietfa.amsl.com>; Tue, 21 Oct 2014 07:36:09 -0700 (PDT)
Received: from mail-la0-f52.google.com (mail-la0-f52.google.com [209.85.215.52]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28F351A6F67 for <ipv6@ietf.org>; Tue, 21 Oct 2014 07:36:07 -0700 (PDT)
Received: by mail-la0-f52.google.com with SMTP id hz20so1160880lab.39 for <ipv6@ietf.org>; Tue, 21 Oct 2014 07:36:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=vm1Pa6G0LYAMKfO38ge6CS1qHPTTdVdaidA31Rv7+wE=; b=Kthn+1PXLINUX4c2+C1k3YgYvrThADSVbyWyriB37OaGm4PhIcRE49GD4EWT7OsVYx nzn5cK0es4q1D0vPSTiBLdYdGXi5Gxc8vkq6w7fjaybflQQUuUpgy7Twah78rTkpf/Eq VP0Rob64T2mwwdZVlN0jZoTcm3RT2dMFLtjdlJemfVD1ZTOmJRXYe9/CWbrlHsOHEPY8 j72XSMF7HLN9wy4So2cQ9NXMkpvbjtdDz5o436jmNvLu/1J7tXlIg8ce/A9o7f3ndy/z miS44va5aGcETsmkEjdK4gpGf2UNyXkvpQ29PSzBmHUjs1UCTbXTamGr8YJobK129kdi vXhg==
X-Gm-Message-State: ALoCoQnrSfa9juNI+5WCc2rc69kbV4kY6rXL1mzNSpKityC4ROEtH+BJ7kQSBDFSaZYtTmnhZCQe
MIME-Version: 1.0
X-Received: by 10.112.54.162 with SMTP id k2mr35015293lbp.63.1413902165994; Tue, 21 Oct 2014 07:36:05 -0700 (PDT)
Received: by 10.25.137.9 with HTTP; Tue, 21 Oct 2014 07:36:05 -0700 (PDT)
In-Reply-To: <54454517.4070000@si6networks.com>
References: <CAPunWhC-ceaSgKXF2qGQPXuRhc9+v0bYt5NRS+tH2WHCH0z_BQ@mail.gmail.com> <544440F3.5010309@gmail.com> <54454517.4070000@si6networks.com>
Date: Tue, 21 Oct 2014 08:36:05 -0600
Message-ID: <CANO7kWAJLhjAJGV6hCF75sjTOb5DkSkasb5TKpEh1jcJOgks=w@mail.gmail.com>
Subject: Re: question on ICMP error packets, RFC 4443, 2.4 e)
From: Simon Perreault <sperreault@jive.com>
To: Fernando Gont <fgont@si6networks.com>
Content-Type: multipart/alternative; boundary=001a11c3eeee5a09b20505efc0d6
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/4TbeXx31nbMT39PgHrOn4xG4oe8
Cc: Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk>, ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 21 Oct 2014 14:36:11 -0000

--001a11c3eeee5a09b20505efc0d6
Content-Type: text/plain; charset=UTF-8

On Mon, Oct 20, 2014 at 11:23 AM, Fernando Gont <fgont@si6networks.com>
wrote:

> However, at least in theory, ICMPv6 error could use IPv6 EHs.. at which
> point the obvious question arises "Can we really require routers to
> figure out what's the ICMP message type?"
>

Sending an error is never actually required, to allow for things like ICMP
rate limiting. My interpretation is that if a router doesn't have the
resources necessary to figure out if it is ok to send an error, then the
sensible thing to do is assume that it's not ok, and send nothing.

Simon

--001a11c3eeee5a09b20505efc0d6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Oct 20, 2014 at 11:23 AM, Fernando Gont <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:fgont@si6networks.com" target=3D"_blank">fgont@si6networks.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=3D":31p" c=
lass=3D"a3s" style=3D"overflow:hidden">However, at least in theory, ICMPv6 =
error could use IPv6 EHs.. at which<br>
point the obvious question arises &quot;Can we really require routers to<br=
>
figure out what&#39;s the ICMP message type?&quot;</div></blockquote></div>=
<br>Sending an error is never actually required, to allow for things like I=
CMP rate limiting. My interpretation is that if a router doesn&#39;t have t=
he resources necessary to figure out if it is ok to send an error, then the=
 sensible thing to do is assume that it&#39;s not ok, and send nothing.</di=
v><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Simon</di=
v></div>

--001a11c3eeee5a09b20505efc0d6--


From nobody Thu Oct 23 17:22:16 2014
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 966411AD3CE; Thu, 23 Oct 2014 17:22:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 jf9knk-Svn_U; Thu, 23 Oct 2014 17:22:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FF2C1A87A4; Thu, 23 Oct 2014 17:22:07 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-6man-enhanced-dad-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.4.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141024002207.11608.55425.idtracker@ietfa.amsl.com>
Date: Thu, 23 Oct 2014 17:22:07 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/JtjfvyVk32Ig4ZI-wJMBoOG4f2Y
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 24 Oct 2014 00:22:09 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

        Title           : Enhanced Duplicate Address Detection
        Authors         : Rajiv Asati
                          Hemant Singh
                          Wes Beebee
                          Carlos Pignataro
                          Eli Dart
                          Wes George
	Filename        : draft-ietf-6man-enhanced-dad-07.txt
	Pages           : 12
	Date            : 2014-10-23

Abstract:
   IPv6 Loopback Suppression and Duplicate Address Detection (DAD) are
   discussed in Appendix A of [RFC4862].  That specification mentions a
   hardware-assisted mechanism to detect looped back DAD messages.  If
   hardware cannot suppress looped back DAD messages, a software
   solution is required.  Several service provider communities have
   expressed a need for automated detection of looped backed Neighbor
   Discovery (ND) messages used by DAD.  This document includes
   mitigation techniques and outlines the Enhanced DAD algorithm to
   automate the detection of looped back IPv6 ND messages used by DAD.
   For network loopback tests, the Enhanced DAD algorithm allows IPv6 to
   self-heal after a loopback is placed and removed.  Further, for
   certain access networks the document automates resolving a specific
   duplicate address conflict.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-enhanced-dad-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-enhanced-dad-07


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Thu Oct 23 17:26:02 2014
Return-Path: <shemant@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F5531AD41D; Thu, 23 Oct 2014 17:25:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Uq94eJQ4Tmzf; Thu, 23 Oct 2014 17:25:57 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C639B1AD3A4; Thu, 23 Oct 2014 17:25:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2883; q=dns/txt; s=iport; t=1414110357; x=1415319957; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=F3Cck+AM79ACI5XdbBO5smcu1etc69Z3hJ5FUv1KWaE=; b=Rgge1p1EX76YHLlbNMdGRR5vQ4lZBySSK6RrgMP3CnTzBXHGVbkfpELs RNO4D+Zx5UCVdAfPnAjrDtFZP8dtUQzfrNORe3ge7wdaCHHWmvQqcr1Ot qi3jslM9uHSSugpV9vQKj6n8WgjKZ+mbdLXcOFYIfIaSIPOo1V1fK8h+5 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AkYFAEObSVStJA2J/2dsb2JhbABcgw5UUwnMdQqHTQKBDBYBcguEAgEBAQQBAQE3NAsMBAIBCBEEAQELFAkHJwsUCQgCBA4FCAESiCYIBclxAQEBAQEBAQEBAQEBAQEBAQEBAQEBF5AnMQcGgyeBHgWGLYk6gh6ERohDPIMNkTODeGyBSIEDAQEB
X-IronPort-AV: E=Sophos;i="5.04,778,1406592000"; d="scan'208";a="365943151"
Received: from alln-core-4.cisco.com ([173.36.13.137]) by rcdn-iport-5.cisco.com with ESMTP; 24 Oct 2014 00:25:56 +0000
Received: from xhc-rcd-x15.cisco.com (xhc-rcd-x15.cisco.com [173.37.183.89]) by alln-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s9O0Puia012511 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Fri, 24 Oct 2014 00:25:56 GMT
Received: from xmb-rcd-x06.cisco.com ([169.254.6.134]) by xhc-rcd-x15.cisco.com ([173.37.183.89]) with mapi id 14.03.0195.001; Thu, 23 Oct 2014 19:25:55 -0500
From: "Hemant Singh (shemant)" <shemant@cisco.com>
To: "internet-drafts@ietf.org" <internet-drafts@ietf.org>
Subject: RE: I-D Action: draft-ietf-6man-enhanced-dad-07.txt
Thread-Topic: I-D Action: draft-ietf-6man-enhanced-dad-07.txt
Thread-Index: AQHP7yCVKXt0OiaTsEa8zQLzo02hP5w+Ywvw
Date: Fri, 24 Oct 2014 00:25:55 +0000
Message-ID: <75B6FA9F576969419E42BECB86CB1B89155E7D8B@xmb-rcd-x06.cisco.com>
References: <20141024002207.11608.55425.idtracker@ietfa.amsl.com>
In-Reply-To: <20141024002207.11608.55425.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.86.250.241]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/emkIh_ibZCEY7mJqIevFoEF-xYI
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 24 Oct 2014 00:25:59 -0000

This version has taken care of comments from Bernie Volz. =20

The Abstract has been revised as well.  Bob (co-chair), please see if the r=
evised Abstract works for you.  =20

Thanks to Wes Beebee and Carlos for their help putting this version togethe=
r.=20

Regards.

Hemant

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of internet-drafts@ietf=
.org
Sent: Thursday, October 23, 2014 8:22 PM
To: i-d-announce@ietf.org
Cc: ipv6@ietf.org
Subject: I-D Action: draft-ietf-6man-enhanced-dad-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IPv6 Maintenance Working Group of the IET=
F.

        Title           : Enhanced Duplicate Address Detection
        Authors         : Rajiv Asati
                          Hemant Singh
                          Wes Beebee
                          Carlos Pignataro
                          Eli Dart
                          Wes George
	Filename        : draft-ietf-6man-enhanced-dad-07.txt
	Pages           : 12
	Date            : 2014-10-23

Abstract:
   IPv6 Loopback Suppression and Duplicate Address Detection (DAD) are
   discussed in Appendix A of [RFC4862].  That specification mentions a
   hardware-assisted mechanism to detect looped back DAD messages.  If
   hardware cannot suppress looped back DAD messages, a software
   solution is required.  Several service provider communities have
   expressed a need for automated detection of looped backed Neighbor
   Discovery (ND) messages used by DAD.  This document includes
   mitigation techniques and outlines the Enhanced DAD algorithm to
   automate the detection of looped back IPv6 ND messages used by DAD.
   For network loopback tests, the Enhanced DAD algorithm allows IPv6 to
   self-heal after a loopback is placed and removed.  Further, for
   certain access networks the document automates resolving a specific
   duplicate address conflict.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-6man-enhanced-dad/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-6man-enhanced-dad-07

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-enhanced-dad-07


Please note that it may take a couple of minutes from the time of submissio=
n until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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


From nobody Thu Oct 23 22:45:29 2014
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC8051A88A9 for <ipv6@ietfa.amsl.com>; Thu, 23 Oct 2014 22:45:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 TFJWEbbOe2Xe for <ipv6@ietfa.amsl.com>; Thu, 23 Oct 2014 22:45:25 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB1531A888D for <ipv6@ietf.org>; Thu, 23 Oct 2014 22:45:24 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BNZ43620; Fri, 24 Oct 2014 05:45:23 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 24 Oct 2014 06:45:22 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.22]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Fri, 24 Oct 2014 13:45:19 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: 6man WG <ipv6@ietf.org>
Subject: FW: New Version Notification for draft-wang-6man-flow-label-reflection-00.txt
Thread-Topic: New Version Notification for draft-wang-6man-flow-label-reflection-00.txt
Thread-Index: AQHP7Qm736RRsjN+Xky5Y3nD/Ags7pw+wAOw
Date: Fri, 24 Oct 2014 05:45:18 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AF68BD0@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/ZjuE1a27hv7NXaYmAGqGgWCiifA
Cc: Aijun Wang <wangaijun@tsinghua.org.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 24 Oct 2014 05:45:28 -0000

SGksIDZtYW4sDQoNCldlIGhhdmUgc3VibWl0dGVkIGEgbmV3IGRyYWZ0IHRvIDZtYW4gV0cuIEl0
IHByb3Bvc2VzIGEgZmxvdyBsYWJlbCByZWZsZWN0aW9uIG1lY2hhbmlzbSB0aGF0IG5ldHdvcmsg
ZGV2aWNlcyBjb3B5IHRoZSBmbG93IGxhYmVsIHZhbHVlIGZyb20gcmVjZWl2ZWQgcGFja2V0cyB0
byB0aGUgY29ycmVzcG9uZGluZyBmbG93IGxhYmVsIGZpZWxkIGluIHJldHVybiBwYWNrZXRzLiBX
aXRoIHRoaXMgbWVjaGFuaXNtLCBuZXR3b3JrIG9wZXJhdG9ycyB3b3VsZCBlYXNpbHkgY29ycmVs
YXRlIGFuIHVwc3RyZWFtIHNlc3Npb24gYW5kIHRoZSBjb3JyZXNwb25kaW5nIGRvd25zdHJlYW0g
c2Vzc2lvbiB0b2dldGhlci4gVGhpcyBtZWNoYW5pc20gY291bGQgc2ltcGxpZnkgdGhlIG5ldHdv
cmsgdHJhZmZpYyByZWNvZ25pdGlvbiBwcm9jZXNzIGluIG5ldHdvcmsgb3BlcmF0aW9ucyBhbmQg
bWFrZSB0aGUgcG9saWN5IGZvciBib3RoIGRpcmVjdGlvbnMgb2YgdHJhZmZpYyBvZiBvbmUgc2Vz
c2lvbiBjb25zaXN0ZW50Lg0KDQpodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC13YW5n
LTZtYW4tZmxvdy1sYWJlbC1yZWZsZWN0aW9uDQoNClBsZWFzZSByZXZpZXcgdGhpcyBkcmFmdC4g
QW55IGNvbW1lbnRzIGFyZSBhcHByZWNpYXRlZC4NCg0KQmVzdCByZWdhcmRzLA0KDQpTaGVuZyAr
IEFpanVuDQoNCj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KPkZyb206IGludGVybmV0LWRy
YWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10NCj5TZW50OiBU
dWVzZGF5LCBPY3RvYmVyIDIxLCAyMDE0IDQ6MTAgUE0NCj5UbzogQWlqdW4gV2FuZzsgQWlqdW4g
V2FuZzsgU2hlbmcgSmlhbmc7IFNoZW5nIEppYW5nDQo+U3ViamVjdDogTmV3IFZlcnNpb24gTm90
aWZpY2F0aW9uIGZvcg0KPmRyYWZ0LXdhbmctNm1hbi1mbG93LWxhYmVsLXJlZmxlY3Rpb24tMDAu
dHh0DQo+DQo+DQo+QSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LXdhbmctNm1hbi1mbG93LWxh
YmVsLXJlZmxlY3Rpb24tMDAudHh0DQo+aGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBi
eSBTaGVuZyBKaWFuZyBhbmQgcG9zdGVkIHRvIHRoZQ0KPklFVEYgcmVwb3NpdG9yeS4NCj4NCj5O
YW1lOgkJZHJhZnQtd2FuZy02bWFuLWZsb3ctbGFiZWwtcmVmbGVjdGlvbg0KPlJldmlzaW9uOgkw
MA0KPlRpdGxlOgkJSVB2NiBGbG93IExhYmVsIFJlZmxlY3Rpb24NCj5Eb2N1bWVudCBkYXRlOgky
MDE0LTEwLTIxDQo+R3JvdXA6CQlJbmRpdmlkdWFsIFN1Ym1pc3Npb24NCj5QYWdlczoJCTkNCj5V
Ukw6DQo+aHR0cDovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtd2FuZy02bWFu
LWZsb3ctbGFiZWwtcmVmbGVjdGlvbi0wDQo+MC50eHQNCj5TdGF0dXM6DQo+aHR0cHM6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtd2FuZy02bWFuLWZsb3ctbGFiZWwtcmVmbGVjdGlv
bi8NCj5IdG1saXplZDoNCj5odHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC13YW5nLTZt
YW4tZmxvdy1sYWJlbC1yZWZsZWN0aW9uLTAwDQo+DQo+DQo+QWJzdHJhY3Q6DQo+ICAgVGhlIGN1
cnJlbnQgZGVmaW5pdGlvbiBvZiB0aGUgSVB2NiBGbG93IExhYmVsIGZvY3VzZXMgbWFpbmx5IG9u
IGhvdw0KPiAgIHRoZSBwYWNrZXQgc291cmNlIGZvcm1zIHRoZSB2YWx1ZSBvZiB0aGlzIGZpZWxk
IGFuZCBob3cgdGhlIGZvcndhcmRlcg0KPiAgIGluLXBhdGggdHJlYXRzIGl0LiAgSW4gbmV0d29y
ayBvcGVyYXRpb25zLCB0aGVyZSBhcmUgbmVlZHMgdG8NCj4gICBjb3JyZWxhdGUgYW4gdXBzdHJl
YW0gc2Vzc2lvbiBhbmQgdGhlIGNvcnJlc3BvbmRpbmcgZG93bnN0cmVhbQ0KPiAgIHNlc3Npb24g
dG9nZXRoZXIuICBUaGlzIGRvY3VtZW50IHByb3Bvc2UgYSBmbG93IGxhYmVsIHJlZmxlY3Rpb24N
Cj4gICBtZWNoYW5pc20gdGhhdCBuZXR3b3JrIGRldmljZXMgY29weSB0aGUgZmxvdyBsYWJlbCB2
YWx1ZSBmcm9tDQo+ICAgcmVjZWl2ZWQgcGFja2V0cyB0byB0aGUgY29ycmVzcG9uZGluZyBmbG93
IGxhYmVsIGZpZWxkIGluIHJldHVybg0KPiAgIHBhY2tldHMuICBUaGlzIG1lY2hhbmlzbSBjb3Vs
ZCBzaW1wbGlmeSB0aGUgbmV0d29yayB0cmFmZmljDQo+ICAgcmVjb2duaXRpb24gcHJvY2VzcyBp
biBuZXR3b3JrIG9wZXJhdGlvbnMgYW5kIG1ha2UgdGhlIHBvbGljeSBmb3INCj4gICBib3RoIGRp
cmVjdGlvbnMgb2YgdHJhZmZpYyBvZiBvbmUgc2Vzc2lvbiBjb25zaXN0ZW50Lg0KPg0KPlRoZSBJ
RVRGIFNlY3JldGFyaWF0DQoNCg==


From nobody Fri Oct 24 06:32:14 2014
Return-Path: <fernando@gont.com.ar>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 97BFE1A008A for <ipv6@ietfa.amsl.com>; Fri, 24 Oct 2014 06:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.003
X-Spam-Level: 
X-Spam-Status: No, score=-0.003 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 Z3oAILnjKiRC for <ipv6@ietfa.amsl.com>; Fri, 24 Oct 2014 06:32:07 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 110251A00FF for <6man@ietf.org>; Fri, 24 Oct 2014 06:32:07 -0700 (PDT)
Received: from [2001:5c0:1000:a::d7] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fernando@gont.com.ar>) id 1XheyK-0005hh-Gb; Fri, 24 Oct 2014 15:32:05 +0200
Message-ID: <544A549E.6070606@gont.com.ar>
Date: Fri, 24 Oct 2014 10:31:10 -0300
From: Fernando Gont <fernando@gont.com.ar>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "6man@ietf.org" <6man@ietf.org>
Subject: draft-gont-6man-nd-opt-validation-01 (and e.g. Fwd: FreeBSD Security Advisory FreeBSD-SA-14:20.rtsold)
References: <20141021211219.97FD2545B@nine.des.no>
In-Reply-To: <20141021211219.97FD2545B@nine.des.no>
X-Forwarded-Message-Id: <20141021211219.97FD2545B@nine.des.no>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/DM3W7k6iSexAWeNX2OalPLyyIg8
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 24 Oct 2014 13:32:11 -0000

Folks,

This was published a few days ago. FWIW, our I-D
draft-gont-6man-nd-opt-validation is essentially meant to avoid this
sort of issue.

P.S.: Thought this was a valuable datapoint to offer to this wg.

Thanks,
Fernando




-------- Forwarded Message --------
Subject: FreeBSD Security Advisory FreeBSD-SA-14:20.rtsold
Date: Tue, 21 Oct 2014 23:12:19 +0200 (CEST)
From: FreeBSD Security Advisories <security-advisories@freebsd.org>
Reply-To: freebsd-security@freebsd.org
To: Bugtraq <bugtraq@securityfocus.com>

=============================================================================
FreeBSD-SA-14:20.rtsold                                     Security
Advisory
                                                          The FreeBSD
Project

Topic:          rtsold(8) remote buffer overflow vulnerability

Category:       core
Module:         rtsold
Announced:      2014-10-21
Credits:        Florian Obser, Hiroki Sato
Affects:        FreeBSD 9.1 and later.
Corrected:      2014-10-21 20:20:07 UTC (stable/10, 10.1-PRERELEASE)
                2014-10-21 20:20:36 UTC (releng/10.1, 10.1-RC2-p1)
                2014-10-21 20:20:36 UTC (releng/10.1, 10.1-RC1-p1)
                2014-10-21 20:20:36 UTC (releng/10.1, 10.1-BETA3-p1)
                2014-10-21 20:21:10 UTC (releng/10.0, 10.0-RELEASE-p10)
                2014-10-21 20:20:17 UTC (stable/9, 9.3-STABLE)
                2014-10-21 20:21:10 UTC (releng/9.3, 9.3-RELEASE-p3)
                2014-10-21 20:21:10 UTC (releng/9.2, 9.2-RELEASE-p13)
                2014-10-21 20:21:10 UTC (releng/9.1, 9.1-RELEASE-p20)
CVE Name:       CVE-2014-3954

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

I.   Background

As part of the stateless addess autoconfiguration (SLAAC) mechanism,
IPv6 routers periodically broadcast router advertisement messages on
attached networks to inform hosts of the correct network prefix,
router address and MTU, as well as additional network parameters such
as the DNS servers (RDNSS), DNS search list (DNSSL) and whether a
stateful configuration service is available.  Hosts that have recently
joined the network can broadcast a router solicitation message to
solicit an immediate advertisement instead of waiting for the next
periodic advertisement.

The router solicitation daemon, rtsold(8), broadcasts router
solicitation messages at startup or when the state of an interface
changes from passive to active.  Incoming router advertisement
messages are first processed by the kernel and then passed on to
rtsold(8), which handles the DNS and stateful configuration options.

II.  Problem Description

Due to a missing length check in the code that handles DNS parameters,
a malformed router advertisement message can result in a stack buffer
overflow in rtsold(8).

III. Impact

Receipt of a router advertisement message with a malformed DNSSL
option, for instance from a compromised host on the same network, can
cause rtsold(8) to crash.

While it is theoretically possible to inject code into rtsold(8)
through malformed router advertisement messages, it is normally
compiled with stack protection enabled, rendering such an attack
extremely difficult.

When rtsold(8) crashes, the existing DNS configuration will remain in
force, and the kernel will continue to receive and process periodic
router advertisements.

IV.  Workaround

No workaround is available, but systems that do not run rtsold(8) are
not affected.

As a general rule, SLAAC should not be used on networks where trusted
and untrusted hosts coexist in the same broadcast domain.

V.   Solution

Perform one of the following:

1) Upgrade your vulnerable system to a supported FreeBSD stable or
release / security branch (releng) dated after the correction date.

2) To update your vulnerable system via a binary patch:

Systems running a RELEASE version of FreeBSD on the i386 or amd64
platforms can be updated via the freebsd-update(8) utility:

# freebsd-update fetch
# freebsd-update install

3) To update your vulnerable system via a source code patch:

The following patches have been verified to apply to the applicable
FreeBSD release branches.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/SA-14:20/rtsold.patch
# fetch http://security.FreeBSD.org/patches/SA-14:20/rtsold.patch.asc
# gpg --verify rtsold.patch.asc

b) Apply the patch.  Execute the following commands as root:

# cd /usr/src
# patch < /path/to/rtsold.patch

c) Recompile rtsold.  Execute the following commands as root:

# cd /usr/src/usr.sbin/rtsold
# make && make install

4) Restart the affected service

To restart the affected service after updating the system, either
reboot the system or execute the following command as root:

# service rtsold restart

VI.  Correction details

The following list contains the correction revision numbers for each
affected branch.

Branch/path                                                      Revision
-------------------------------------------------------------------------
stable/9/                                                         r273412
releng/9.1/                                                       r273415
releng/9.2/                                                       r273415
releng/9.3/                                                       r273415
stable/10/                                                        r273411
releng/10.0/                                                      r273415
releng/10.1/                                                      r273414
-------------------------------------------------------------------------

To see which files were modified by a particular revision, run the
following command, replacing NNNNNN with the revision number, on a
machine with Subversion installed:

# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base

Or visit the following URL, replacing NNNNNN with the revision number:

<URL:http://svnweb.freebsd.org/base?view=revision&revision=NNNNNN>

VII. References

<URL:http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-3954>

The latest revision of this advisory is available at
<URL:http://security.FreeBSD.org/advisories/FreeBSD-SA-14:20.rtsold.asc>

-- 
Fernando Gont
e-mail: fernando@gont.com.ar || fgont@si6networks.com
PGP Fingerprint: 7809 84F5 322E 45C7 F1C9 3945 96EE A9EF D076 FFF1




From nobody Fri Oct 24 06:42:21 2014
Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4C6A1A0065 for <ipv6@ietfa.amsl.com>; Fri, 24 Oct 2014 06:42:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 KBh2zF2SDaEE for <ipv6@ietfa.amsl.com>; Fri, 24 Oct 2014 06:42:10 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:8240:6:a::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCF811A00E2 for <6man@ietf.org>; Fri, 24 Oct 2014 06:41:56 -0700 (PDT)
Received: from [2001:5c0:1000:a::d7] by web01.jbserver.net with esmtpsa (TLSv1.2:DHE-RSA-AES128-SHA:128) (Exim 4.84) (envelope-from <fgont@si6networks.com>) id 1Xhf7m-0005lA-Tz; Fri, 24 Oct 2014 15:41:51 +0200
Message-ID: <544A55CD.5050002@si6networks.com>
Date: Fri, 24 Oct 2014 10:36:13 -0300
From: Fernando Gont <fgont@si6networks.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "6man@ietf.org" <6man@ietf.org>
Subject: Fwd: New Version Notification for draft-gont-6man-nd-opt-validation-01.txt
References: <20141024132841.15047.19204.idtracker@ietfa.amsl.com>
In-Reply-To: <20141024132841.15047.19204.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20141024132841.15047.19204.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/0ZkQLV6v75Vziu-Zsg_D6v0L_NE
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 24 Oct 2014 13:42:17 -0000

Folks,

FYI, we have posted a revision that addresses the comments we've
received so far.

Thanks!

Best regards,
Fernando




-------- Forwarded Message --------
Subject: New Version Notification for
draft-gont-6man-nd-opt-validation-01.txt
Date: Fri, 24 Oct 2014 06:28:41 -0700
From: internet-drafts@ietf.org
To: Shucheng LIU (Will) <liushucheng@huawei.com>, Will (Shucheng) Liu
<liushucheng@huawei.com>, Fernando Gont <fgont@si6networks.com>, Ron
Bonica <rbonica@juniper.net>, Fernando Gont <fgont@si6networks.com>,
Ronald P. Bonica <rbonica@juniper.net>


A new version of I-D, draft-gont-6man-nd-opt-validation-01.txt
has been successfully submitted by Fernando Gont and posted to the
IETF repository.

Name:		draft-gont-6man-nd-opt-validation
Revision:	01
Title:		Validation of IPv6 Neighbor Discovery Options
Document date:	2014-10-21
Group:		Individual Submission
Pages:		15
URL:
http://www.ietf.org/internet-drafts/draft-gont-6man-nd-opt-validation-01.txt
Status:
https://datatracker.ietf.org/doc/draft-gont-6man-nd-opt-validation/
Htmlized:
http://tools.ietf.org/html/draft-gont-6man-nd-opt-validation-01
Diff:
http://www.ietf.org/rfcdiff?url2=draft-gont-6man-nd-opt-validation-01

Abstract:
   This memo specifies validation rules for IPv6 Neighbor Discovery (ND)
   Options.  In order to avoid pathological outcomes, IPv6
   implementations validate incoming ND options using these rules.





Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat





From nobody Fri Oct 24 13:37:14 2014
Return-Path: <bob.hinden@gmail.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5BEF1A883F for <ipv6@ietfa.amsl.com>; Fri, 24 Oct 2014 13:37:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 wjfnaTo72SX5 for <ipv6@ietfa.amsl.com>; Fri, 24 Oct 2014 13:37:11 -0700 (PDT)
Received: from mail-lb0-x22a.google.com (mail-lb0-x22a.google.com [IPv6:2a00:1450:4010:c04::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EC8B1A6EDA for <ipv6@ietf.org>; Fri, 24 Oct 2014 13:36:58 -0700 (PDT)
Received: by mail-lb0-f170.google.com with SMTP id u10so3447976lbd.1 for <ipv6@ietf.org>; Fri, 24 Oct 2014 13:36:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=from:content-type:subject:date:message-id:cc:to:mime-version;  bh=n7J3ExcOhPcMDKVPCq3W/Dw4cgLRSh/G5TtwDxDQYgY=; b=P+52qIvC6jVWwriYOjIXuFlr0jnWDAmKE7X2FkmRcSvCPU54f4F+hJ65G8A15QH/EW ZVKjiqsOHDImB5AyZ6OgdNvHuxtM0shiAdWmafHehz4lHvtdgBI70TMzS7VCBlK1ltaU AP8L/9CcweEmszpgefqJLK1qeG5qQ9VTRChrjsnTd068QUVv94J59bjg/qJlwy+p1Koi OBWvsHdsfF63ycwWAidAQhRXjelldDpe1e6olFxRiPB/UPN5q1wvi/PT+XryD8E5qjLK /RK4+nep5BqzwirWdZQ8GCaAqQZoJSGMMRYZBU5O8k3+bZZ4uuXSv2MK/LVUSvggtX+k XJgw==
X-Received: by 10.152.116.102 with SMTP id jv6mr6909099lab.40.1414183016735; Fri, 24 Oct 2014 13:36:56 -0700 (PDT)
Received: from [10.0.0.25] ([98.234.222.98]) by mx.google.com with ESMTPSA id c6sm2196281lah.43.2014.10.24.13.36.54 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 24 Oct 2014 13:36:55 -0700 (PDT)
From: Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_5A0078AA-11D7-46E8-BBA5-7F3020473A23"; protocol="application/pgp-signature"; micalg=pgp-sha512
Subject: 6MAN Draft Agenda for the Honolulu IETF
Date: Fri, 24 Oct 2014 13:36:48 -0700
Message-Id: <E00182A0-83D8-4CC4-8F74-F67BA660EF3F@gmail.com>
To: IPv6 List <ipv6@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
X-Mailer: Apple Mail (2.1510)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/Pev2yXtEmMO_p4IKOe0EcjHjyPU
Cc: Bob Hinden <bob.hinden@gmail.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 24 Oct 2014 20:37:12 -0000

--Apple-Mail=_5A0078AA-11D7-46E8-BBA5-7F3020473A23
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

The draft agenda can be found at

 http://www.ietf.org/proceedings/91/agenda/agenda-91-6man

We tried to accommodate all of the requests we received, hopefully we =
did not miss any.  Please let us know if that was the case.

It is organized in three sections, Working Group drafts, Active =
Individual drafts, and New Individual drafts.  We priority to the =
requests in that order.  Active individual drafts are drafts that have =
seen active discussion on the IPv6 list, and the New Individual drafts =
are ones that are new and/or have not seen a lot of discussion.  There =
is only enough time to give the last category five minutes to allow the =
authors to do a introduction to the work and then start a discussion on =
the mailing list.

We also need a minute taker and a jabber scribe.  Please volunteer.

Thanks,
Bob & Ole



--Apple-Mail=_5A0078AA-11D7-46E8-BBA5-7F3020473A23
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQEcBAEBCgAGBQJUSrhhAAoJEK7rdBF357uolw4IAIP33HkFHQoZiLIUVTszEGo5
w8wpCecOu6ZIEDOAGuQ55qu9B/9ypC8cfb+ApAZh5d9CCBsXLQWSPwCv70/f7FbC
MZrzbCfioDq1gP0fkzA6D3SUP2slXuP9pDL8T7Bc1aTknWXPmJZe5iO7Jpl2k5Nv
QxEKalW6td3RGvvBahebpCu0RprtRKn8PDqiEHVP/VNkN8OUHMwLUfSZskgQsU/n
4IGFuuLBm9Z5snLbkRlfzTMJ+0AWdvvNc+cNvbTFk7idt+RDW4NRdodTnmQCzdpf
1iqnFP20ibKkQ+JfS5QQjJv+LgkH9uKJx0Fr8f7EoDmdh6zwtB89EQ7RHDyloMk=
=IfLF
-----END PGP SIGNATURE-----

--Apple-Mail=_5A0078AA-11D7-46E8-BBA5-7F3020473A23--


From nobody Sat Oct 25 07:05:23 2014
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1F241A0024 for <ipv6@ietfa.amsl.com>; Sat, 25 Oct 2014 07:05:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 pTgYNWFmsb8m for <ipv6@ietfa.amsl.com>; Sat, 25 Oct 2014 07:05:19 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id B645A1A0023 for <ipv6@ietf.org>; Sat, 25 Oct 2014 07:05:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 3686B871612; Sat, 25 Oct 2014 16:05:18 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p3icg6hpJUcz; Sat, 25 Oct 2014 16:05:18 +0200 (CEST)
Received: from Rays-iMac.local (092-111-140-211.static.chello.nl [92.111.140.211]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id EB80A871611; Sat, 25 Oct 2014 16:05:17 +0200 (CEST)
Message-ID: <544BAE03.4020302@globis.net>
Date: Sat, 25 Oct 2014 16:04:51 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: draft-ietf-6man-resilient-rs@tools.ietf.org
Subject: Re: I-D Action: draft-ietf-6man-resilient-rs-04.txt
References: <20141015025022.2238.45373.idtracker@ietfa.amsl.com>
In-Reply-To: <20141015025022.2238.45373.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/osfMxVHuCHOE0WYkKmXoBYc-HyQ
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 25 Oct 2014 14:05:22 -0000

internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>   This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
>
>          Title           : Packet loss resiliency for Router Solicitations
>          Authors         : Suresh Krishnan
>                            Dmitry Anipko
>                            Dave Thaler
> 	Filename        : draft-ietf-6man-resilient-rs-04.txt
> 	Pages           : 6
> 	Date            : 2014-10-14
>
> Abstract:
>     When an interface on a host is initialized, the host transmits Router
>     Solicitations in order to minimize the amount of time it needs to
>     wait until the next unsolicited multicast Router Advertisement is
>     received.  In certain scenarios, these router solicitations
>     transmitted by the host might be lost.  This document specifies a
>     mechanism for hosts to cope with the loss of the initial Router
>     Solicitations.  Furthermore, on some links, unsolicited multicast
>     Router Advertisements are never sent and the mechanism in this
>     document is intended to work even in such scenarios.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/
>
> There's also a htmlized version available at:
> http://tools.ietf.org/html/draft-ietf-6man-resilient-rs-04
>
> A diff from the previous version is available at:
> http://www.ietf.org/rfcdiff?url2=draft-ietf-6man-resilient-rs-04
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>
I'm unsure of the exact status of this document as I can't recall 
reading it before, and it has been substantially revised in the last diff.

Whilst I recognise that some early packet loss may result in a delay in 
discovering a default router on a network, I remain to be convinced that 
this draft is not harmful in its current form.

Resistance to DHCP(v6) drafts often cite infinite solicitations as being 
a "bad thing", and this draft is effectively repeating the same 
behaviour for links where either no IPv6 has been configured, or for 
situations where no IPv6 router providing a default route is two-way 
reachable.

An upper cap on how long these additional RS retransmissions should be 
repeated is therefore advisable IMHO e.g. 3 * the maximum time between 
unsolicited multicast Router Advertisements (MaxRtrAdvInterval) (or 
absolute max of 5400 seconds).

This is different to DHCPv6, where there is no possibility for DHCPv6 
servers to send unsolicited multicast announcements of the ADVERTISE 
state AFAIK.

-- 
Regards,
RayH


From nobody Sat Oct 25 07:56:20 2014
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F7701A0076 for <ipv6@ietfa.amsl.com>; Sat, 25 Oct 2014 07:56:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 Nh37Ra7b-0_t for <ipv6@ietfa.amsl.com>; Sat, 25 Oct 2014 07:56:16 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id A70161A00CF for <ipv6@ietf.org>; Sat, 25 Oct 2014 07:56:16 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 0B763871613; Sat, 25 Oct 2014 16:56:16 +0200 (CEST)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HOQ1CowtyPJW; Sat, 25 Oct 2014 16:56:15 +0200 (CEST)
Received: from Rays-iMac.local (092-111-140-211.static.chello.nl [92.111.140.211]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id B8542870049; Sat, 25 Oct 2014 16:56:15 +0200 (CEST)
Message-ID: <544BB9F5.4090306@globis.net>
Date: Sat, 25 Oct 2014 16:55:49 +0200
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Sheng Jiang <jiangsheng@huawei.com>
Subject: Re: FW: New Version Notification for draft-wang-6man-flow-label-reflection-00.txt
References: <5D36713D8A4E7348A7E10DF7437A4B923AF68BD0@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AF68BD0@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/A5RVoyWT4NloWju9yREjaJs_Z-4
Cc: 6man WG <ipv6@ietf.org>, Aijun Wang <wangaijun@tsinghua.org.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Sat, 25 Oct 2014 14:56:18 -0000

Sheng Jiang wrote:
> 
>> Hi, 6man,
>>
>> We have submitted a new draft to 6man WG. It proposes a flow label reflection mechanism that network devices copy the flow label value from received packets to the corresponding flow label field in return packets. With this mechanism, network operators would easily correlate an upstream session and the corresponding downstream session together. This mechanism could simplify the network traffic recognition process in network operations and make the policy for both directions of traffic of one session consistent.
>>
>> http://tools.ietf.org/html/draft-wang-6man-flow-label-reflection
>>
>> Please review this draft. Any comments are appreciated.
>>
>> Best regards,
>>
>> Sheng + Aijun
This is an interesting draft, especially for monitoring and debugging.

Another possible applicable scenario could be efficiently switching 
return packets of flows where policy based routing has been applied, 
thus ensuring symmetric return paths (one of the great challenges of 
PBR), although obviously the security considerations would need updating.

-- 
Regards,
RayH


From nobody Sun Oct 26 19:55:15 2014
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84F1A1A6F44 for <ipv6@ietfa.amsl.com>; Sun, 26 Oct 2014 19:55:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham
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 UXj6b45v5JVE for <ipv6@ietfa.amsl.com>; Sun, 26 Oct 2014 19:55:12 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E8261A1B5B for <ipv6@ietf.org>; Sun, 26 Oct 2014 19:55:12 -0700 (PDT)
X-AuditID: c618062d-f79206d0000014d2-0b-544d5c247d43
Received: from EUSAAHC001.ericsson.se (Unknown_Domain [147.117.188.75]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 9C.63.05330.42C5D445; Sun, 26 Oct 2014 21:40:05 +0100 (CET)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC001.ericsson.se ([147.117.188.75]) with mapi id 14.03.0174.001; Sun, 26 Oct 2014 22:55:00 -0400
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: Ray Hunter <v6ops@globis.net>, "draft-ietf-6man-resilient-rs@tools.ietf.org" <draft-ietf-6man-resilient-rs@tools.ietf.org>
Subject: Re: I-D Action: draft-ietf-6man-resilient-rs-04.txt
Thread-Topic: I-D Action: draft-ietf-6man-resilient-rs-04.txt
Thread-Index: AQHP8Fy+XUKejaRvHEyrVU4cpNGBZw==
Date: Mon, 27 Oct 2014 02:54:59 +0000
Message-ID: <E87B771635882B4BA20096B589152EF6288E2A14@eusaamb107.ericsson.se>
References: <20141015025022.2238.45373.idtracker@ietfa.amsl.com> <544BAE03.4020302@globis.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [147.117.188.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrHLMWRmVeSWpSXmKPExsUyuXSPt65qjG+IwdE1bBanv01gsXh59j2T xZ6r9Q7MHk/OXmfzWLLkJ5PHl8uf2QKYo7hsUlJzMstSi/TtErgyTi7ZxlbwWq7i9qRpzA2M KyS6GDk5JARMJP583MoGYYtJXLi3Hsjm4hASOMIosa15OwuEs5xR4sHuk6wgVWxAHRt2fmYC SYgINDFKXG24xgSSYBZQlrhzfyZjFyMHh7CAjcTfJ1wgYREBW4nNTV+YIGw9iQ0N19hBbBYB VYnb62Ywg9i8Ar4SSy89BIsLCSRILN3wH+wiRqCLvp9aAzVeXOLWk/lMEJcKSCzZc54ZwhaV ePn4HyuErSTx8fd8doh6HYkFuz+xQdjaEssWvobaJShxcuYTlgmMorOQjJ2FpGUWkpZZSFoW MLKsYuQoLU4ty003MtjECIyQYxJsujsY97y0PMQowMGoxMO7wcU3RIg1say4MvcQozQHi5I4 76zaecFCAumJJanZqakFqUXxRaU5qcWHGJk4OKUaGOc5qRT96kpglve9ZPCtPOovi4T6s843 LqE6WnNcVx9+wnLr3LT9z2X2XD6yOSxmv6RVHNOGotsbT34Vu/3+YvWPdTb8nv5/A3YJFymd WJ3QIhYU+LborvGeDOcd24UeLE67kSfj+S6pR5ct76BZVOZ6+U+z1RoPx8VdXXljbeiOn+t2 al+fsk+JpTgj0VCLuag4EQAHQEwQcQIAAA==
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/LOdhIgFrij6noS7mzTK1OhEsgcI
Cc: "ipv6@ietf.org" <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 27 Oct 2014 02:55:14 -0000

Hi Ray,=0A=
   Thanks for your comments. Please find responses inline.=0A=
=0A=
On 10/25/2014 10:05 AM, Ray Hunter wrote:=0A=
>=0A=
>=0A=
> internet-drafts@ietf.org wrote:=0A=
>> A New Internet-Draft is available from the on-line Internet-Drafts direc=
tories.=0A=
>>    This draft is a work item of the IPv6 Maintenance Working Group of th=
e IETF.=0A=
>>=0A=
>>           Title           : Packet loss resiliency for Router Solicitati=
ons=0A=
>>           Authors         : Suresh Krishnan=0A=
>>                             Dmitry Anipko=0A=
>>                             Dave Thaler=0A=
>> 	Filename        : draft-ietf-6man-resilient-rs-04.txt=0A=
>> 	Pages           : 6=0A=
>> 	Date            : 2014-10-14=0A=
>>=0A=
>> Abstract:=0A=
>>      When an interface on a host is initialized, the host transmits Rout=
er=0A=
>>      Solicitations in order to minimize the amount of time it needs to=
=0A=
>>      wait until the next unsolicited multicast Router Advertisement is=
=0A=
>>      received.  In certain scenarios, these router solicitations=0A=
>>      transmitted by the host might be lost.  This document specifies a=
=0A=
>>      mechanism for hosts to cope with the loss of the initial Router=0A=
>>      Solicitations.  Furthermore, on some links, unsolicited multicast=
=0A=
>>      Router Advertisements are never sent and the mechanism in this=0A=
>>      document is intended to work even in such scenarios.=0A=
>>=0A=
>>=0A=
>> The IETF datatracker status page for this draft is:=0A=
>> https://datatracker.ietf.org/doc/draft-ietf-6man-resilient-rs/=0A=
>>=0A=
>> There's also a htmlized version available at:=0A=
>> http://tools.ietf.org/html/draft-ietf-6man-resilient-rs-04=0A=
>>=0A=
>> A diff from the previous version is available at:=0A=
>> http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-6man-resilient-rs-04=0A=
>>=0A=
>>=0A=
>> Please note that it may take a couple of minutes from the time of submis=
sion=0A=
>> until the htmlized version and diff are available at tools.ietf.org.=0A=
>>=0A=
>> Internet-Drafts are also available by anonymous FTP at:=0A=
>> ftp://ftp.ietf.org/internet-drafts/=0A=
>>=0A=
>>=0A=
> I'm unsure of the exact status of this document as I can't recall=0A=
> reading it before, and it has been substantially revised in the last diff=
.=0A=
=0A=
The diff is based on the results of the WGLC.=0A=
=0A=
http://www.ietf.org/mail-archive/web/ipv6/current/msg21227.html=0A=
=0A=
=0A=
>=0A=
> Whilst I recognise that some early packet loss may result in a delay in=
=0A=
> discovering a default router on a network, I remain to be convinced that=
=0A=
> this draft is not harmful in its current form.=0A=
>=0A=
> Resistance to DHCP(v6) drafts often cite infinite solicitations as being=
=0A=
> a "bad thing", and this draft is effectively repeating the same=0A=
> behaviour for links where either no IPv6 has been configured, or for=0A=
> situations where no IPv6 router providing a default route is two-way=0A=
> reachable.=0A=
=0A=
Yes. This has been discussed in the WG before and Section 4 of the draft =
=0A=
has been essentially unchanged since adoption two years ago. The rate =0A=
limiting was put in place to ensure that the load on such networks is =0A=
not excessive.=0A=
=0A=
>=0A=
> An upper cap on how long these additional RS retransmissions should be=0A=
> repeated is therefore advisable IMHO e.g. 3 * the maximum time between=0A=
> unsolicited multicast Router Advertisements (MaxRtrAdvInterval) (or=0A=
> absolute max of 5400 seconds).=0A=
=0A=
One of the issues we are trying to address is the case where LAN =0A=
connectivity for a host is established before WAN connectivity as =0A=
described in the introduction. Setting a hard upper bound will not help. =
=0A=
Also the rate limiting will limit the RSs to approximately 1RS/hr/host.=0A=
=0A=
Thanks=0A=
Suresh=0A=
=0A=


From nobody Mon Oct 27 02:46:21 2014
Return-Path: <jiangsheng@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CAC21A8AFB for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 02:46:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4Kt_BhpegA68 for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 02:46:18 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1E4881A701D for <ipv6@ietf.org>; Mon, 27 Oct 2014 02:46:16 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml404-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BKZ02414; Mon, 27 Oct 2014 09:46:15 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com (10.98.56.37) by lhreml404-hub.china.huawei.com (10.201.5.218) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 27 Oct 2014 09:46:14 +0000
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.22]) by nkgeml406-hub.china.huawei.com ([10.98.56.37]) with mapi id 14.03.0158.001; Mon, 27 Oct 2014 17:46:03 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Ray Hunter <v6ops@globis.net>
Subject: RE: FW: New Version Notification for draft-wang-6man-flow-label-reflection-00.txt
Thread-Topic: FW: New Version Notification for draft-wang-6man-flow-label-reflection-00.txt
Thread-Index: AQHP7Qm736RRsjN+Xky5Y3nD/Ags7pw+wAOwgAGnVICAA1IkYA==
Date: Mon, 27 Oct 2014 09:46:02 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B923AF69D4C@nkgeml512-mbx.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AF68BD0@nkgeml512-mbx.china.huawei.com> <544BB9F5.4090306@globis.net>
In-Reply-To: <544BB9F5.4090306@globis.net>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.111.98.145]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/9EjE_bNEAenRZvfgbpP1-oShLA0
Cc: 6man WG <ipv6@ietf.org>, Aijun Wang <wangaijun@tsinghua.org.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 27 Oct 2014 09:46:20 -0000

Pj4+IFdlIGhhdmUgc3VibWl0dGVkIGEgbmV3IGRyYWZ0IHRvIDZtYW4gV0cuIEl0IHByb3Bvc2Vz
IGEgZmxvdyBsYWJlbA0KPnJlZmxlY3Rpb24gbWVjaGFuaXNtIHRoYXQgbmV0d29yayBkZXZpY2Vz
IGNvcHkgdGhlIGZsb3cgbGFiZWwgdmFsdWUgZnJvbQ0KPnJlY2VpdmVkIHBhY2tldHMgdG8gdGhl
IGNvcnJlc3BvbmRpbmcgZmxvdyBsYWJlbCBmaWVsZCBpbiByZXR1cm4gcGFja2V0cy4gV2l0aA0K
PnRoaXMgbWVjaGFuaXNtLCBuZXR3b3JrIG9wZXJhdG9ycyB3b3VsZCBlYXNpbHkgY29ycmVsYXRl
IGFuIHVwc3RyZWFtDQo+c2Vzc2lvbiBhbmQgdGhlIGNvcnJlc3BvbmRpbmcgZG93bnN0cmVhbSBz
ZXNzaW9uIHRvZ2V0aGVyLiBUaGlzIG1lY2hhbmlzbQ0KPmNvdWxkIHNpbXBsaWZ5IHRoZSBuZXR3
b3JrIHRyYWZmaWMgcmVjb2duaXRpb24gcHJvY2VzcyBpbiBuZXR3b3JrIG9wZXJhdGlvbnMNCj5h
bmQgbWFrZSB0aGUgcG9saWN5IGZvciBib3RoIGRpcmVjdGlvbnMgb2YgdHJhZmZpYyBvZiBvbmUg
c2Vzc2lvbiBjb25zaXN0ZW50Lg0KPj4+DQo+Pj4gaHR0cDovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtd2FuZy02bWFuLWZsb3ctbGFiZWwtcmVmbGVjdGlvbg0KPj4+DQo+Pj4gUGxlYXNlIHJl
dmlldyB0aGlzIGRyYWZ0LiBBbnkgY29tbWVudHMgYXJlIGFwcHJlY2lhdGVkLg0KPj4+DQo+Pj4g
QmVzdCByZWdhcmRzLA0KPj4+DQo+Pj4gU2hlbmcgKyBBaWp1bg0KPg0KPlRoaXMgaXMgYW4gaW50
ZXJlc3RpbmcgZHJhZnQsIGVzcGVjaWFsbHkgZm9yIG1vbml0b3JpbmcgYW5kIGRlYnVnZ2luZy4N
Cj4NCj5Bbm90aGVyIHBvc3NpYmxlIGFwcGxpY2FibGUgc2NlbmFyaW8gY291bGQgYmUgZWZmaWNp
ZW50bHkgc3dpdGNoaW5nDQo+cmV0dXJuIHBhY2tldHMgb2YgZmxvd3Mgd2hlcmUgcG9saWN5IGJh
c2VkIHJvdXRpbmcgaGFzIGJlZW4gYXBwbGllZCwNCj50aHVzIGVuc3VyaW5nIHN5bW1ldHJpYyBy
ZXR1cm4gcGF0aHMgKG9uZSBvZiB0aGUgZ3JlYXQgY2hhbGxlbmdlcyBvZg0KPlBCUiksIGFsdGhv
dWdoIG9idmlvdXNseSB0aGUgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMgd291bGQgbmVlZCB1cGRh
dGluZy4NCg0KSGksIFJheSwNCg0KVGhhbmtzIGZvciB5b3VyIGVtYWlsLiBXZSBkaWQgY29uc2lk
ZXIgdGhlIHN5bW1ldHJpYyByZXR1cm4gcGF0aHMsIGJ1dCBmaW5kIHRoYXQgdGVjaG5pY2FsbHkg
dmVyeSBkaWZmaWN1bHQgdG8gcmVhbGl6ZSwgZXZlbiB0aGUgZmxvdyBsYWJlbCBoYXMgYmVlbiBy
ZWZsZWN0ZWQuIFRoZSBsb2FkLWJhbGFuY2luZyBwb2ludHMgZm9yIG9yaWdpbmFsIHBhY2tldHMg
YW5kIHJldHVybiBwYWNrZXRzIGFyZSBhY3R1YWxseSBkaWZmZXJlbnQgZGV2aWNlcyBhbmQgZGlm
ZmVyZW50IGxvY2F0aW9uIGluIHRoZSBuZXR3b3JrLiBTbyBldmVuIHRoZSByZXR1cm4gcGFja2V0
cyBoYXZlIHRoZSBzYW1lIDMtdHVwbGUgKG9mIGNvdXJzZSwgZGVzdCBhZGRyIGFuZCBzb3VyY2Ug
YWRkciBhcmUgcmV2ZXJzZWQpLiBUaGVyZSBpcyBubyBvYnZpb3VzIG1lY2hhbmlzbSB0byBtYWtl
IHRoZW0gYmUgcm91dGVkIGludG8gdGhlIHNhbWUgcGF0aHMuDQoNCkJlc3QgcmVnYXJkcywNCg0K
U2hlbmcNCg0KPi0tDQo+UmVnYXJkcywNCj5SYXlIDQoNCg==


From nobody Mon Oct 27 11:04:23 2014
Return-Path: <rdroms@cisco.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A6161A890F for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 11:03:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 sBChgMBBPsvD for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 11:03:40 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A271E1A8734 for <ipv6@ietf.org>; Mon, 27 Oct 2014 11:03:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3359; q=dns/txt; s=iport; t=1414433020; x=1415642620; h=from:to:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=gor0Dw4TLwYo/h0OA8iY/lpz35U+YbGoKlCp0F5fs/g=; b=KNFca9tZ4NEKxVYUEB2PD875/mPuHubJWCjYpe0owKZKRDX101+pbFwz fKuYezroPgP7U4Jq4I5Hcnbs9bcBYZZAswO9VWQkE9XbXYoNIGmMwpUQ/ DD+HwWf6J0xYA51TIuTiKxtNafLcn+GuB45q4+InACBZx1mhEtcDQbBcs g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgMFACiITlStJV2c/2dsb2JhbABcgw6BMNYmFgF9hAk6NB0BPkInBIhUpx+kKAEBAQEGAQEBAQEBARuUPIEeBY9pgh6GP4UbgTGDSYoVhx+DeII0gQMBAQE
X-IronPort-AV: E=Sophos;i="5.04,797,1406592000"; d="scan'208";a="366855656"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-3.cisco.com with ESMTP; 27 Oct 2014 18:03:40 +0000
Received: from xhc-aln-x11.cisco.com (xhc-aln-x11.cisco.com [173.36.12.85]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id s9RI3dWj026655 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for <ipv6@ietf.org>; Mon, 27 Oct 2014 18:03:40 GMT
Received: from xmb-aln-x04.cisco.com ([169.254.9.212]) by xhc-aln-x11.cisco.com ([173.36.12.85]) with mapi id 14.03.0195.001; Mon, 27 Oct 2014 13:03:39 -0500
From: "Ralph Droms (rdroms)" <rdroms@cisco.com>
To: 6man WG <ipv6@ietf.org>
Subject: Comments on draft-ietf-6man-default-iids-01.txt
Thread-Topic: Comments on draft-ietf-6man-default-iids-01.txt
Thread-Index: AQHP8hBVXrq0mSKkskuqlQqDNp1aBg==
Date: Mon, 27 Oct 2014 18:03:38 +0000
Message-ID: <8676AC11-85F1-4E58-9871-43FD04C89AB8@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.131.65.118]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7903E8D48E3C8E409E5B9905BF66BC4A@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/cFO4R1zNM4iNNNWn1Rf9IhuOOT4
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 27 Oct 2014 18:03:43 -0000

I have a few comments on the new rev of draft-ietf-6man-default-iids.  This=
 message is posted to the 6man WG mailing list, with a bcc to the 6lo WG ma=
iling list.  The draft is of interest to the 6lo WG; please post responses =
to the 6man WG mailing list.

In this document, I think it is important to be explicit about the consider=
ations that might lead to a decision not to follow the RFC 2119 language re=
commendations in this document.  My immediate concern is the 6LoWPAN standa=
rds, which use IIDs based on hardware addresses as a method for IPv6 header=
 compression.

I also think that some of the wording is too strong, which may lead to conf=
usion in the cases where the recommendations in this document are not follo=
wed.

In particular, I think the wording in the "Future Work" section is too stro=
ng, and does not allow for continued use of IIDs based on hardware addresse=
s in 6LoWPAN and similar standards.

As an editorial detail, the document lists the various RFCs that are update=
, but does not explicitly state what is to be updated in those documents.  =
While the updates could be reasonably inferred, seems to me an explicit sta=
tement about what is to be updated would be good.

With those comments in mind, I'll suggest the following text changes:

In section 1, add this paragraph before the "NOTE":

  In some network technologies and adaptation layers, the use of an
  IID based on a hardware address offers some advantages.  For
  example, the IP-over-IEEE802.15.4 standard in RFC6775 allows for
  compression of IPv6 addresses when the IID the address is based
  on the corresponding hardware address.  The design and engineering
  tradeoffs between security and privacy, and network efficiency
  should be considered in any decision about the use of an IID based
  on a hardware address.

Replace section 3 with:

  It is RECOMMENDED by this document that nodes implement and employ
  RFC 7217 as the default scheme for generating stable IPv6 addresses
  with SLAAC.  Some specifications MAY use a an IID based on a node's
  hardware address if design and engineering considerations warrant.

  It is RECOMMENDED by this document that nodes do not employ IPv6
  address generation schemes that embed the underlying hardware
  address in the Interface Identifier.  In particular, this document
  RECOMMENDS that nodes do not generate Interface Identifiers with
  the schemes specified in [RFC2464], [RFC2467], [RFC2470],
  [RFC2491], [RFC2492], [RFC2497], [RFC2590], [RFC3146], [RFC3572],
  [RFC4338], [RFC4391], [RFC5121], and [RFC5072], and updates those
  documents with this recommendation.

  It is RECOMMENDED by this document that future specifications no
  not specify IPv6 address generation schemes that embed the
  underlying hardware address in the Interface Identifier. Future
  specifications MAY use a an IID based on a node's hardware address
  if design and engineering considerations warrant.

In section 4, replace the last paragraph with:

  Future revisions or updates of these documents should take the
  issues of privacy and security mentioned in section 1 and explain
  any design and engineering considerations that lead to the use of
  IIDs based on a node's hardware address.


I hope this input is helpful.

- Ralph


From nobody Mon Oct 27 12:38:36 2014
Return-Path: <nordmark@acm.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0B611ACD23 for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 12:38:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=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 uQpuZ7SCwFCV for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 12:38:14 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 881301A19EC for <ipv6@ietf.org>; Mon, 27 Oct 2014 12:38:14 -0700 (PDT)
Received: from [172.22.227.199] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.14.9/8.14.9) with ESMTP id s9RJcBEk029836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 27 Oct 2014 12:38:11 -0700
Message-ID: <544E9F23.8080508@acm.org>
Date: Mon, 27 Oct 2014 12:38:11 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: IETF IPv6 <ipv6@ietf.org>
Subject: Fwd: New Version Notification for draft-nordmark-6man-rs-refresh-01.txt
References: <20141027193436.3705.21519.idtracker@ietfa.amsl.com>
In-Reply-To: <20141027193436.3705.21519.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20141027193436.3705.21519.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVYAqMxxNjCLmxPQper+Nro+qUplVYSmo07mjGdaN+Uqgz8wcKB82aITQ5Mb9cxHDfWKrcY/1SolmoxrFqHQCL0I
X-Sonic-ID: C;BCX/yBBe5BGi9gAb/FJGkA== M;SpwUyRBe5BGi9gAb/FJGkA==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/aqWARflTq3-aYRdmau5I0k-aSlQ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 27 Oct 2014 19:38:16 -0000

This is a new draft that allows existing networks to continue to use 
periodic multicast RA, but on networks where that is inefficient the 
router advertisements can instruct (modified) hosts to instead do 
unicast RS/RA exchanges to refresh the information in the RAs.

    Erik


-------- Forwarded Message --------
Subject: 	New Version Notification for 
draft-nordmark-6man-rs-refresh-01.txt
Date: 	Mon, 27 Oct 2014 12:34:36 -0700
From: 	internet-drafts@ietf.org
To: 	Andrew Yourtchenko <ayourtch@cisco.com>, Suresh Krishnan 
<suresh.krishnan@ericsson.com>, Andrew Yourtchenko <ayourtch@cisco.com>, 
Suresh Krishnan <suresh.krishnan@ericsson.com>, Erik Nordmark 
<nordmark@acm.org>, Erik Nordmark <nordmark@acm.org>



A new version of I-D, draft-nordmark-6man-rs-refresh-01.txt
has been successfully submitted by Erik Nordmark and posted to the
IETF repository.

Name:		draft-nordmark-6man-rs-refresh
Revision:	01
Title:		IPv6 Neighbor Discovery Optional Unicast RS/RA Refresh
Document date:	2014-10-27
Group:		Individual Submission
Pages:		12
URL:            http://www.ietf.org/internet-drafts/draft-nordmark-6man-rs-refresh-01.txt
Status:         https://datatracker.ietf.org/doc/draft-nordmark-6man-rs-refresh/
Htmlized:       http://tools.ietf.org/html/draft-nordmark-6man-rs-refresh-01
Diff:           http://www.ietf.org/rfcdiff?url2=draft-nordmark-6man-rs-refresh-01

Abstract:
    IPv6 Neighbor Discovery relies on periodic multicast Router
    Advertisement messages to update timer values and to distribute new
    information (such as new prefixes) to hosts.  On some links the use
    of periodic multicast messages to all host becomes expensive, and in
    some cases it results in hosts waking up frequently.  Many
    implementations of RFC 4861 also use multicast for solicited Router
    Advertisement messages, even though that behavior is optional.

    This specification provides an optional mechanism for hosts and
    routers where instead of periodic multicast Router Advertisements the
    hosts are instructed (by the routers) to use unicast Router
    Solicitations to request refreshed Router Advertisements.  This
    mechanism is enabled by configuring the router to include a new
    option in the Router Advertisement in order to allow the network
    administrator to choose host behavior based on whether periodic
    multicast are more efficient on their link or not.  The routers can
    also tell whether the hosts are capable of the new behavior through a
    new flag in the Router Solicitations.

                                                                                   


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat




From nobody Mon Oct 27 12:59:17 2014
Return-Path: <otroan@employees.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 331341AD3DF for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 12:58:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 L-QaOHlxVu4W for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 12:58:50 -0700 (PDT)
Received: from banjo.employees.org (banjo.employees.org [IPv6:2001:1868:205::19]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 174BD1AD3C6 for <ipv6@ietf.org>; Mon, 27 Oct 2014 12:58:33 -0700 (PDT)
Received: from [192.168.10.30] (cm-84.215.22.20.getinternet.no [84.215.22.20]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: otroan) by banjo.employees.org (Postfix) with ESMTPSA id 2E9D262D7 for <ipv6@ietf.org>; Mon, 27 Oct 2014 12:58:32 -0700 (PDT)
From: Ole Troan <otroan@employees.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Subject: Fwd: Meetecho coverage at IETF91
Date: Mon, 27 Oct 2014 20:58:28 +0100
References: <544981D8.5030004@meetecho.com>
To: 6man WG <ipv6@ietf.org>
Message-Id: <C0235C7D-6A56-47CE-B132-EBACB813B11D@employees.org>
Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\))
X-Mailer: Apple Mail (2.1990.1)
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/PH8Vezfav3ADSDy_Omixu4UiQIQ
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 27 Oct 2014 19:58:52 -0000

Hi,

if anyone attending the 6man session at the IETF meeting plan to be =
remote, please let Bob and myself know.

Best regards,
Ole


> Begin forwarded message:
>=20
> Message-Id: <544981D8.5030004@meetecho.com>
> Date: 24 Oct 2014 0:31:52 CEST
> From: Meetecho IETF support <ietf@meetecho.com>
> To: wgchairs@ietf.org
> Subject: Meetecho coverage at IETF91
>=20
> Dear chairs,
>=20
> as you probably know, Meetecho will cover all WG meeting session in =
Honolulu.
>=20
> If you plan to have remote _presentations_, you're kindly requested to =
inform us in proper advance, since this needs a special set-up and a =
preliminary test with the remote speakers.
>=20
> *Please be aware that the deadline for requesting remote presentation =
support is November 6.*
>=20
> Thanks,
> the Meetecho team
>=20
>=20
> --=20
> Meetecho s.r.l.
> Web Conferencing and Collaboration Tools
> www.meetecho.com


From nobody Mon Oct 27 15:49:56 2014
Return-Path: <v6ops@globis.net>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6B01A1B51 for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 15:49:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 qqg4Ramt7GWb for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 15:49:52 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5E08C1A1B42 for <ipv6@ietf.org>; Mon, 27 Oct 2014 15:49:52 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id A2E1E871613; Mon, 27 Oct 2014 23:49:51 +0100 (CET)
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yTR9kkPA7ex0; Mon, 27 Oct 2014 23:49:51 +0100 (CET)
Received: from Rays-iMac.local (092-111-140-211.static.chello.nl [92.111.140.211]) (Authenticated sender: Ray.Hunter@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 799A0871611; Mon, 27 Oct 2014 23:49:51 +0100 (CET)
Message-ID: <544ECBE5.1010203@globis.net>
Date: Mon, 27 Oct 2014 23:49:09 +0100
From: Ray Hunter <v6ops@globis.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: Sheng Jiang <jiangsheng@huawei.com>
Subject: Re: FW: New Version Notification for draft-wang-6man-flow-label-reflection-00.txt
References: <5D36713D8A4E7348A7E10DF7437A4B923AF68BD0@nkgeml512-mbx.china.huawei.com> <544BB9F5.4090306@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AF69D4C@nkgeml512-mbx.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B923AF69D4C@nkgeml512-mbx.china.huawei.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/WhpSYrZ2LX8U4JnGCyXHd1YjLLg
Cc: 6man WG <ipv6@ietf.org>, Aijun Wang <wangaijun@tsinghua.org.cn>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Mon, 27 Oct 2014 22:49:54 -0000

> Sheng Jiang <mailto:jiangsheng@huawei.com>
> 27 October 2014 10:46
>>>> We have submitted a new draft to 6man WG. It proposes a flow label
>> reflection mechanism that network devices copy the flow label value from
>> received packets to the corresponding flow label field in return packets. With
>> this mechanism, network operators would easily correlate an upstream
>> session and the corresponding downstream session together. This mechanism
>> could simplify the network traffic recognition process in network operations
>> and make the policy for both directions of traffic of one session consistent.
>>>> http://tools.ietf.org/html/draft-wang-6man-flow-label-reflection
>>>>
>>>> Please review this draft. Any comments are appreciated.
>>>>
>>>> Best regards,
>>>>
>>>> Sheng + Aijun
>> This is an interesting draft, especially for monitoring and debugging.
>>
>> Another possible applicable scenario could be efficiently switching
>> return packets of flows where policy based routing has been applied,
>> thus ensuring symmetric return paths (one of the great challenges of
>> PBR), although obviously the security considerations would need updating.
>
> Hi, Ray,
>
> Thanks for your email. We did consider the symmetric return paths, but find that technically very difficult to realize, even the flow label has been reflected. The load-balancing points for original packets and return packets are actually different devices and different location in the network. So even the return packets have the same 3-tuple (of course, dest addr and source addr are reversed). There is no obvious mechanism to make them be routed into the same paths.
>
> Best regards,
>
> Sheng
Indeed.

You'd have to perform "previous hop discovery", possibly based on 
caching a combination of inbound physical interface and L2 source 
address of the inbound packet (mapped to flow label).

Whether you think it's a good idea or not is a different discussion.

-- 
Regards,
RayH


From nobody Mon Oct 27 19:43:44 2014
Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A2391A70E2 for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 19:43:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 GHCE_30eo9Z7 for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 19:43:41 -0700 (PDT)
Received: from tsinghua.org.cn (mail.tsinghua.org.cn [211.151.65.103]) by ietfa.amsl.com (Postfix) with ESMTP id 808F41A6EF0 for <ipv6@ietf.org>; Mon, 27 Oct 2014 19:43:40 -0700 (PDT)
Received: from ctbriwangaij (unknown [219.142.69.77]) by app1 (Coremail) with SMTP id Z0GX06CrIQEA8k5UByZzAA==.62179S4; Tue, 28 Oct 2014 09:32:02 +0800 (CST)
From: "Aijun Wang" <wangaijun@tsinghua.org.cn>
To: "'6man WG'" <ipv6@ietf.org>
References: <5D36713D8A4E7348A7E10DF7437A4B923AF68BD0@nkgeml512-mbx.china.huawei.com> <544BB9F5.4090306@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AF69D4C@nkgeml512-mbx.china.huawei.com> <544ECBE5.1010203@globis.net> 
In-Reply-To: 
Subject: RE: FW: New Version Notification for draft-wang-6man-flow-label-reflection-00.txt
Date: Tue, 28 Oct 2014 10:43:23 +0800
Message-ID: <008c01cff258$f98c0260$eca40720$@org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac/yOF9rcV6X4fVxR/a2kiY8SlkdLQAEFZ/wAALcjLAAAIFQYAAArd9w
Content-Language: zh-cn
X-CM-TRANSID: Z0GX06CrIQEA8k5UByZzAA==.62179S4
X-Coremail-Antispam: 1U3129KBjvJXoWxGFy5CryDuF1xWry5Zw1UWrg_yoW5CrykpF W3GFy3Kr1DCr1fJ3s2yw1UW34Fv3ykJw43Aw13tw1vkwn8AryUKF4DKw18uFyUGryDJ3s0 qrW5tws8Z3WDZrJanT9S1TB71UUUUUDv73VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjHmb7 Iv0xC_Jr1l5I8CrVACY4xI64kE6c02F40Ex7xfM7kC6x804xWl14x267AKxVWUJVW8JwAF xVCF77xC6IxKo4kEV4yl1I0EscIYIxCEI4klw4CSwwAv7VCjz48v1sIEY20_GF1lc7CjxV Aaw2AFwI0_JF0_Jw1lx4CE17CEb7AF67AKxVWUJVWUXwCI42IY6I8E87Iv67AKxVWUJVW8 JwCI42IY6I8E87Iv6xkF7I0E14v26r1j6r4U0xZFpf9x0JU9J5rUUUUU=
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/paJ6TXYPoW45XIUwmDKREtrIsfE
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 28 Oct 2014 02:43:42 -0000

Hi, Ray:

Previously, we have discussed the solution of symmetric path for upstream
and downstream packets of one session, just based on the 5-tuple information
of this session. If there is additional information can be used, such
requirement can be met more perfectly.
Anyway, there are scenarios that require the upstream and downstream of one
session pass the same device, or even same link, the flow label mechanism
can assist/accelerate such aim to be accomplished.

Aijun 

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Ray Hunter
Sent: Tuesday, October 28, 2014 6:49 AM
To: Sheng Jiang
Cc: 6man WG; Aijun Wang
Subject: Re: FW: New Version Notification for
draft-wang-6man-flow-label-reflection-00.txt

> Sheng Jiang <mailto:jiangsheng@huawei.com>
> 27 October 2014 10:46
>>>> We have submitted a new draft to 6man WG. It proposes a flow label
>> reflection mechanism that network devices copy the flow label value 
>> from received packets to the corresponding flow label field in return 
>> packets. With this mechanism, network operators would easily 
>> correlate an upstream session and the corresponding downstream 
>> session together. This mechanism could simplify the network traffic 
>> recognition process in network operations and make the policy for both
directions of traffic of one session consistent.
>>>> http://tools.ietf.org/html/draft-wang-6man-flow-label-reflection
>>>>
>>>> Please review this draft. Any comments are appreciated.
>>>>
>>>> Best regards,
>>>>
>>>> Sheng + Aijun
>> This is an interesting draft, especially for monitoring and debugging.
>>
>> Another possible applicable scenario could be efficiently switching 
>> return packets of flows where policy based routing has been applied, 
>> thus ensuring symmetric return paths (one of the great challenges of 
>> PBR), although obviously the security considerations would need updating.
>
> Hi, Ray,
>
> Thanks for your email. We did consider the symmetric return paths, but
find that technically very difficult to realize, even the flow label has
been reflected. The load-balancing points for original packets and return
packets are actually different devices and different location in the
network. So even the return packets have the same 3-tuple (of course, dest
addr and source addr are reversed). There is no obvious mechanism to make
them be routed into the same paths.
>
> Best regards,
>
> Sheng
Indeed.

You'd have to perform "previous hop discovery", possibly based on caching a
combination of inbound physical interface and L2 source address of the
inbound packet (mapped to flow label).

Whether you think it's a good idea or not is a different discussion.

--
Regards,
RayH

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




From nobody Tue Oct 28 06:09:17 2014
Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F43B1A87EB for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 19:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 4rOD6ifW8gNK for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 19:11:07 -0700 (PDT)
Received: from tsinghua.org.cn (mail.tsinghua.org.cn [211.151.65.103]) by ietfa.amsl.com (Postfix) with ESMTP id 55AFF1A87AC for <ipv6@ietf.org>; Mon, 27 Oct 2014 19:11:05 -0700 (PDT)
Received: from ctbriwangaij (unknown [219.142.69.77]) by app1 (Coremail) with SMTP id Z0GX06B7pQRS6k5U+iF5AA==.61347S4; Tue, 28 Oct 2014 08:59:16 +0800 (CST)
From: "Aijun Wang" <wangaijun@tsinghua.org.cn>
To: "'Ray Hunter'" <v6ops@globis.net>, "'Sheng Jiang'" <jiangsheng@huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B923AF68BD0@nkgeml512-mbx.china.huawei.com> <544BB9F5.4090306@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AF69D4C@nkgeml512-mbx.china.huawei.com> <544ECBE5.1010203@globis.net> 
In-Reply-To: 
Subject: RE: FW: New Version Notification for draft-wang-6man-flow-label-reflection-00.txt
Date: Tue, 28 Oct 2014 10:10:37 +0800
Message-ID: <007a01cff254$661ff9e0$325feda0$@org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac/yOF9rcV6X4fVxR/a2kiY8SlkdLQAEFZ/wAALcjLA=
Content-Language: zh-cn
X-CM-TRANSID: Z0GX06B7pQRS6k5U+iF5AA==.61347S4
X-Coremail-Antispam: 1U3129KBjvJXoWxGFy5CryDuF1xWry5Zw1UWrg_yoW5CrykpF W3GFy3Kr1DCr1fJ3s2yw1UW34Fv3ykJw43Aw13tw1vkwn8AryUKF4DKw18uFyUGryDJ3s0 qrW5tws8Z3WDZrJanT9S1TB71UUUUUUv73VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjQqb7 Iv0xC_Jr1l5I8CrVACY4xI64kE6c02F40Ex7xfM7kC6x804xWl14x267AKxVW8JVW5JwAF xVCF77xC6IxKo4kEV4yl1I0EscIYIxCEI4klw4CSwwAv7VCjz48v1sIEY20_GF1lx4CE17 CEb7AF67AKxVWUAVWUtwCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E 14v26r1j6r4U0xZFpf9x0JUHKZXUUUUU=
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/2QJMTSgdNxycnG6gwHjg5mcJ778
X-Mailman-Approved-At: Tue, 28 Oct 2014 01:08:42 -0700
Cc: '6man WG' <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 28 Oct 2014 02:11:11 -0000

Hi, Ray:

Previously, we have discussed the solution of symmetric path for upstream
and downstream packets of one session, just based on the 5-tuple information
of this session. If there is additional information can be used, such
requirement can be met more perfectly.
Anyway, there are scenarios that require the upstream and downstream of one
session pass the same device, or even same link, the flow label mechanism
can assist/accelerate such aim to be accomplished.

Aijun 

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Ray Hunter
Sent: Tuesday, October 28, 2014 6:49 AM
To: Sheng Jiang
Cc: 6man WG; Aijun Wang
Subject: Re: FW: New Version Notification for
draft-wang-6man-flow-label-reflection-00.txt

> Sheng Jiang <mailto:jiangsheng@huawei.com>
> 27 October 2014 10:46
>>>> We have submitted a new draft to 6man WG. It proposes a flow label
>> reflection mechanism that network devices copy the flow label value 
>> from received packets to the corresponding flow label field in return 
>> packets. With this mechanism, network operators would easily 
>> correlate an upstream session and the corresponding downstream 
>> session together. This mechanism could simplify the network traffic 
>> recognition process in network operations and make the policy for both
directions of traffic of one session consistent.
>>>> http://tools.ietf.org/html/draft-wang-6man-flow-label-reflection
>>>>
>>>> Please review this draft. Any comments are appreciated.
>>>>
>>>> Best regards,
>>>>
>>>> Sheng + Aijun
>> This is an interesting draft, especially for monitoring and debugging.
>>
>> Another possible applicable scenario could be efficiently switching 
>> return packets of flows where policy based routing has been applied, 
>> thus ensuring symmetric return paths (one of the great challenges of 
>> PBR), although obviously the security considerations would need updating.
>
> Hi, Ray,
>
> Thanks for your email. We did consider the symmetric return paths, but
find that technically very difficult to realize, even the flow label has
been reflected. The load-balancing points for original packets and return
packets are actually different devices and different location in the
network. So even the return packets have the same 3-tuple (of course, dest
addr and source addr are reversed). There is no obvious mechanism to make
them be routed into the same paths.
>
> Best regards,
>
> Sheng
Indeed.

You'd have to perform "previous hop discovery", possibly based on caching a
combination of inbound physical interface and L2 source address of the
inbound packet (mapped to flow label).

Whether you think it's a good idea or not is a different discussion.

--
Regards,
RayH

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




From nobody Tue Oct 28 06:09:21 2014
Return-Path: <wangaijun@tsinghua.org.cn>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C3011A8861 for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 19:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 YJe136HskkTA for <ipv6@ietfa.amsl.com>; Mon, 27 Oct 2014 19:25:03 -0700 (PDT)
Received: from tsinghua.org.cn (mail.tsinghua.org.cn [211.151.65.103]) by ietfa.amsl.com (Postfix) with ESMTP id 102E31A885F for <ipv6@ietf.org>; Mon, 27 Oct 2014 19:25:02 -0700 (PDT)
Received: from ctbriwangaij (unknown [219.142.69.77]) by app1 (Coremail) with SMTP id Z0GX06CbCQKg7U5UiDdvAA==.61606S4; Tue, 28 Oct 2014 09:13:24 +0800 (CST)
From: "Aijun Wang" <wangaijun@tsinghua.org.cn>
To: "'6man WG'" <ipv6@ietf.org>
References: <5D36713D8A4E7348A7E10DF7437A4B923AF68BD0@nkgeml512-mbx.china.huawei.com> <544BB9F5.4090306@globis.net> <5D36713D8A4E7348A7E10DF7437A4B923AF69D4C@nkgeml512-mbx.china.huawei.com> <544ECBE5.1010203@globis.net> 
In-Reply-To: 
Subject: RE: FW: New Version Notification for draft-wang-6man-flow-label-reflection-00.txt
Date: Tue, 28 Oct 2014 10:24:42 +0800
Message-ID: <007f01cff256$5fa56da0$1ef048e0$@org.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac/yOF9rcV6X4fVxR/a2kiY8SlkdLQAEFZ/wAALcjLAAAIFQYA==
Content-Language: zh-cn
X-CM-TRANSID: Z0GX06CbCQKg7U5UiDdvAA==.61606S4
X-Coremail-Antispam: 1U3129KBjvJXoWxGFy5CryDuF1xWry5Zw1UWrg_yoW5CrykpF W3GFy3Kr1DCr1fJ3s2yw1UW34Fv3ykJw43Aw13tw1vkwn8AryUKF4DKw18uFyUGryDJ3s0 qrW5tws8Z3WDZrJanT9S1TB71UUUUU7v73VFW2AGmfu7bjvjm3AaLaJ3UjIYCTnIWjllb7 Iv0xC_Jr1l5I8CrVACY4xI64kE6c02F40Ex7xfM7kC6x804xWl14x267AKxVWUJVW8JwAF xVCF77xC6IxKo4kEV4yl1I0EscIYIxCEI4klw4CSwwAv7VCjz48v1sIEY20_GF1lx4CE17 CEb7AF67AKxVWUJVWUXwCI42IY6xIIjxv20xvE14v26r1j6r1xMIIF0xvE2Ix0cI8IcVCY 1x0267AKxVWUJVW8JwCI42IY6I8E87Iv67AKxVWUJVW8JwCI42IY6I8E87Iv6xkF7I0E14 v26r1j6r4U0xZFpf9x0JUd8nOUUUUU=
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/EuEHWhvM4jKhPApMIaDIHn_pvE0
X-Mailman-Approved-At: Tue, 28 Oct 2014 01:08:46 -0700
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 28 Oct 2014 02:25:05 -0000

Hi, Ray:

Previously, we have discussed the solution of symmetric path for upstream
and downstream packets of one session, just based on the 5-tuple information
of this session. If there is additional information can be used, such
requirement can be met more perfectly.
Anyway, there are scenarios that require the upstream and downstream of one
session pass the same device, or even same link, the flow label mechanism
can assist/accelerate such aim to be accomplished.

Aijun 

-----Original Message-----
From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Ray Hunter
Sent: Tuesday, October 28, 2014 6:49 AM
To: Sheng Jiang
Cc: 6man WG; Aijun Wang
Subject: Re: FW: New Version Notification for
draft-wang-6man-flow-label-reflection-00.txt

> Sheng Jiang <mailto:jiangsheng@huawei.com>
> 27 October 2014 10:46
>>>> We have submitted a new draft to 6man WG. It proposes a flow label
>> reflection mechanism that network devices copy the flow label value 
>> from received packets to the corresponding flow label field in return 
>> packets. With this mechanism, network operators would easily 
>> correlate an upstream session and the corresponding downstream 
>> session together. This mechanism could simplify the network traffic 
>> recognition process in network operations and make the policy for both
directions of traffic of one session consistent.
>>>> http://tools.ietf.org/html/draft-wang-6man-flow-label-reflection
>>>>
>>>> Please review this draft. Any comments are appreciated.
>>>>
>>>> Best regards,
>>>>
>>>> Sheng + Aijun
>> This is an interesting draft, especially for monitoring and debugging.
>>
>> Another possible applicable scenario could be efficiently switching 
>> return packets of flows where policy based routing has been applied, 
>> thus ensuring symmetric return paths (one of the great challenges of 
>> PBR), although obviously the security considerations would need updating.
>
> Hi, Ray,
>
> Thanks for your email. We did consider the symmetric return paths, but
find that technically very difficult to realize, even the flow label has
been reflected. The load-balancing points for original packets and return
packets are actually different devices and different location in the
network. So even the return packets have the same 3-tuple (of course, dest
addr and source addr are reversed). There is no obvious mechanism to make
them be routed into the same paths.
>
> Best regards,
>
> Sheng
Indeed.

You'd have to perform "previous hop discovery", possibly based on caching a
combination of inbound physical interface and L2 source address of the
inbound packet (mapped to flow label).

Whether you think it's a good idea or not is a different discussion.

--
Regards,
RayH

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




From nobody Tue Oct 28 10:51:58 2014
Return-Path: <stig@venaas.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 241A91A90E3 for <ipv6@ietfa.amsl.com>; Tue, 28 Oct 2014 10:51:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 PEK1I_7Q83iS for <ipv6@ietfa.amsl.com>; Tue, 28 Oct 2014 10:51:50 -0700 (PDT)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2::152:127]) by ietfa.amsl.com (Postfix) with ESMTP id ECDE21A90E0 for <ipv6@ietf.org>; Tue, 28 Oct 2014 10:49:44 -0700 (PDT)
Received: from [IPv6:2001:420:301:1258:1cc1:7bd7:b166:83a1] (unknown [IPv6:2001:420:301:1258:1cc1:7bd7:b166:83a1]) by ufisa.uninett.no (Postfix) with ESMTPSA id 1291B80B9; Tue, 28 Oct 2014 18:49:34 +0100 (CET)
Message-ID: <544FD727.5010103@venaas.com>
Date: Tue, 28 Oct 2014 10:49:27 -0700
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Tom Taylor <tom.taylor.stds@gmail.com>,  Nicolas Ojeda Bar <no263@dpmms.cam.ac.uk>, ipv6@ietf.org
Subject: Re: question on ICMP error packets, RFC 4443, 2.4 e)
References: <CAPunWhC-ceaSgKXF2qGQPXuRhc9+v0bYt5NRS+tH2WHCH0z_BQ@mail.gmail.com> <544440F3.5010309@gmail.com>
In-Reply-To: <544440F3.5010309@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/EGTifczxkCju3j3-Fv-HavMy0NU
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Tue, 28 Oct 2014 17:51:53 -0000

Hi

On 10/19/2014 3:53 PM, Tom Taylor wrote:
> The basic principle is that you never answer an error with an error, or
> you could generate an infinite loop.

You are supposed to send ICMP6 errors in response to some multicast
packets though. E.g. packet too big.

Stig

> Tom Taylor
>
> On 19/10/2014 5:14 PM, Nicolas Ojeda Bar wrote:
>> (apologies if you receive two copies of this message)
>>
>> Hello,
>>
>> In RFC 4443, 2.4 e.1) it says that ICMP6 errors should not be
>> generated in
>> response to other ICMP errors. And in 2.4. e.3) it says that one should
>> generate an ICMP6 error in response to a packet with multicast
>> destination
>> that has a unrecognized IPv6 option with option type with highest order 2
>> bits 10.
>>
>> My question is whether one still has to check that the message considered
>> e.3) is not an ICMP6 error packet before generating one in response.
>> Similarly for uni/anycast messages satisfying the condition of e.3).
>>
>> Please excuse if I have missed something obvious.
>>
>> Thank you very much!
>>
>> Nicolas
>>
>>
>>
>> --------------------------------------------------------------------
>> 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
> --------------------------------------------------------------------


From nobody Fri Oct 31 08:46:10 2014
Return-Path: <Internet-Drafts@ietf.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A3301ACD05; Fri, 31 Oct 2014 08:46:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_TVD_MIME_NO_HEADERS=0.01] autolearn=ham
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 LHwbj1oNa_Yt; Fri, 31 Oct 2014 08:46:07 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5921C1ACD0D; Fri, 31 Oct 2014 08:46:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D ACTION:draft-ietf-6man-why64-08.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 5.7.1.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141031154606.32150.47873.idtracker@ietfa.amsl.com>
Date: Fri, 31 Oct 2014 08:46:06 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ipv6/zkciTbl0QaN5iDPSGwCT9jqGs74
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
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>
X-List-Received-Date: Fri, 31 Oct 2014 15:46:08 -0000

--NextPart

A new Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Maintenance Working Group of the IETF.

    Title         : Analysis of the 64-bit Boundary in IPv6 Addressing
    Author(s)     : B. Carpenter, et al
    Filename      : draft-ietf-6man-why64
    Pages         : 24 
    Date          : 2014-10-31 
    
   The IPv6 unicast addressing format includes a separation between the
   prefix used to route packets to a subnet and the interface identifier
   used to specify a given interface connected to that subnet.
   Currently the interface identifier is defined as 64 bits long for
   almost every case, leaving 64 bits for the subnet prefix.  This
   document describes the advantages of this fixed boundary and analyses
   the issues that would be involved in treating it as a variable
   boundary.



A URL for this Internet-Draft is:
https://www.ietf.org/internet-drafts/draft-ietf-6man-why64-08.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body; name="draft-ietf-6man-why64";
 site="ftp.ietf.org"; access-type="anon-ftp";
 directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2014-10-31084606.I-D@ietf.org>


--NextPart--

